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 16 hours 41 minutes ago