Hi all,

I've logged a ticket with MS about this, but I thought I'd ask here too...

We've got SCCM 2012 R2 with MDT 2013 integrated.  We have OSD task sequences that install SCCM applications during the build process.  The application list is determined from the MDT database and applications assigned to the usual base variable list for installation through the "Install Applications" task.  The task is set to continue installing if an application fails.

This has all worked fine for 18 months, however we recently upgraded to SP1 and noticed that applications were failing to install.  On further investigation, it seems that the Install Applications task isn't able to recover after any application that returns a 3010 (soft reboot) code has been installed.  The machine reboots and the task sequence moves on to the next step.

I've managed to temporarily work around the issue (to some extent), by modifying the applications to treat 3010 as a success, but that then causes an issue with applications that rely on other applications being pre-installed (ie. the APPV5 client relies on Powershell 3 being available which is applied as a hotfix which returns 3010).

Has anyone else experienced this?  The guy from MS said that it had been a known issue in the early days, but that it had been fixed since then.

Cheers

Simon

• Edited by Simon Funnell Wednesday, July 29, 2015 3:13 PM

Yes we have the same issue since 2012 r2 sp1. Cu1+ fixed this issue but it appears it's back. Very frustrating

Good to hear that I we're not alone, I guess... 

Have you opened a ticket with MS?

Just to confirm that I've had a response from MS now and they've confirmed that they have been able to replicate the issue and have filed it as a bug with the product team.

They couldn't tell me whether this would be fixed as a hotfix / CU or new version or give me any time scales. So I guess we just wait and see...

Cheers

Simon

Is it resolved in CU1?

https://support.microsoft.com/en-us/kb/3074857

Not based on my reading of what's included in the CU.

I don't believe so judging by the release notes.  I don't think there would have been time as I only logged it a couple of weeks ago.

I've escalated to our TAM to see if I can get an idea of when a fix may become available.

I raised a ticket today as well. Maybe a bit more pressure will help speed things up! :)

I've just completed a test in my lab and as expected, no, CU1 doesn't fix it.