SOLVED SCCM Upgrade Task Sequence Issues

[mdlister]

Evening, I have recently upgraded to SCCM 1706 and am experiencing some issues with the Task Sequences. None appear to be working, I have done lots of testing on this and if i create a new task sequence with just a boot image and the OS applied it still wanted to check other applications for Pre Reqs that it failed on.
I was able to get past this by updating the content for the applications it complained about. But it would then fall over Joining the domain and installing drivers.

The upgrade was a bit of a mammoth, we went from Windows Server 2008, SCCM 2012 SP1 to Windows 2008 SCCM 1606, then did an inplace OS Upgrade to 2012 R2. From there we went to 1702 and then finally to 1706.

Everything else works in SCCM and sending existing applications to clients works but not through the TS.

Has anyone had any experience with this before? I thought it might be something to do with the Hash on the DP and will check that out tomorrow when i am back in work. We are also still only using Windows 7 so our universal boot image is still using the ADK 8.1 and not the new ADK10 for Win10 Support.

 

[Prajwal Desai]

So you mean to say that OSD is successful but only the app installs are failing ?.

 

[mdlister]

yes correct, the TS does the following

• format disk
• Install OS
• Apply Auto Drivers
• Windows Settings
• Network Settings
• Setup ConfigMgr - Restarts computer and sits on Ctrl Alt Del
• Then it has a long list of Applications to install

The _SMSTaskSequence folder is still in the root of the OS Partition.

We had issues with the driver packages but were able to get around it with auto drivers instead. I'm wondering if anything needs updating on the application packages for it to continue?

 

[Prajwal Desai]

Why not troubleshoot which app is failing by looking into the appenforce.log and smsts.log files ?.

 

[mdlister]

After the reboot from Setup Windows and ConfigMrg step it just reboots to Ctrl Alt Del.

I've been through the logs in smsts.log and I can't see any errors. It thinks it's just finished. We have reloaded the Wim file and installed Dot Net 4.5.2 and a load of windows updates to offset the patches required after it is built. I will check the appenforce.log and smsts.log when its complete.

Thanks

 

[mdlister]

I have been through the smsts.log and I can see it walk through each step, the last entry is at 08:49, the AppEnforce.log doesn't start until 09:04 and picks up software that is policed to all machines. but nothing that was in the task sequence like MS Office for instance.

a few errors we are getting the in the log are

Failed to load policies from XML.
Not found (Error: 80041002; Source: WMI)

Error compiling client config policies. code 80041002
Task Sequence Manager could not initialize Task Sequence Environment. code 80041002

Attached is a copy of the log file.

We found other articles that referenced the Network service account for the Distribution point, removing it and restarting the server and then adding it back in again hasn't had any effect.

 

[mdlister]

For anyone reading this and following along, I had to do a few things to get the task sequence moving along through the applications.

1. Created a new boot image using https://docs.microsoft.com/en-us/wi...dows-pe-boot-image-with-configuration-manager
2. The current x86 and x64 boot images were old and needed updating using https://www.scconfigmgr.com/2014/02...ot-updated-after-a-configmgr-2012-r2-upgrade/
3. The powershell to register the WMI Method to get the boot images set back so the client version updated failed. In the comments it suggests it was the drivers assigned to the boot images. Removing them all and then running the command worked a treat.
4. Redistribute the x86, x64 and the custom boot image appears to have moved us on to the application part of the task sequence.

The task sequence has still fallen over complaining about Adobe Flash, looking in the AppEnforce.log it reports back a 1603 error code which is a standard MSI error code. I am thinking this is then causing the task sequence to fail and then it resets back to Windows on the Ctrl Alt Del screen.

 

[Prajwal Desai]

1603 error code means fatal error, i suggest to check the command line used to deploy Adobe flash.

 

[mdlister]

Thanks, we have resolved the issues with this and are able to build machines again now! hopefully this will help others when they make the upgrade to make sure they don't fall in to the same trap as me.