Upgrade SCCM 2012 To SP1: OSD failed at "Setup Windows and Configuration Manager"

[gvlaarho]

Hi all,

After one week of investigation, i have discover that if you enable the "Client Push Installation" and/or "Software update-based client installation" in Administartion - Site - your primary site, OSD will failed 9 times on 10 !!!!

This is because if AD discovery is enabled, SCCM try to install (push) the client almost at the same time than the "Setup Windows and Configuration Manager" step from your task sequence.

 

You will see in ccmsetup.log something like this:

MSI: Action 13:19:20: SmsStopUIComponents. This custom action forces all open client UI components to stop and exit. ccmsetup 15/02/2013 13:19:20 2400 (0x0960)
MSI: Action 13:19:20: SmsStopUserComponents. This custom action forces all open client UI and SCNotification components to stop and exit. ccmsetup 15/02/2013 13:19:20 2400 (0x0960)
MSI: Action 13:19:20: CcmUnloadWmiProviders. Enumerates all providers and unloads them, verifies they are unloaded, and then reloads them. ccmsetup 15/02/2013 13:19:20 2400 (0x0960)

Then ....

 

==========[ ccmsetup started in process 2128 ]========== ccmsetup 15/02/2013 13:19:25 1156 (0x0484)

then finally almost at the end of log:

 

An instance of ccmsetup is running as a service. The current instance will be terminated. ccmsetup 15/02/2013 13:19:31 1156 (0x0484)

SO DON'T ENABLE OPTIONS

 

MS should be advised about this because it's a new bug ... SCCM Should see that the station is in provisioning mode then abort or ignore the Push

 

Have a nice experience with SCCM 2012 SP1

[Peter33]

Which account are you using for push installations? The local Administrator?

I have not seen this behaviour yet, but we are using an AD account and the group it belongs to will be added to the local admin group as one of the last steps in the TS. So this might explain that i have not seen this before.

[gvlaarho]

AD Account; once computer joine the domain, SCCM try to push and this with both the two options mentioned. I think that is for that that new option appears in the hierarchy level ....

[Squirre1]

This is correct... I have experienced the same thing as well in our environment which was co-engineered with microsoft... Their solution, instead of actually fixing the problem, was to make sure that when you applied the image to the machine that the firewall is enabled... this will give the setup windows and config manager task enough time to install without the client push affecting the deployment... Then have a GPO that disables the Firewall whenever the machine is attached to the local domain... By the time GPO has disabled the firewall, the SCCM agent is installed and you are good to go. Since turning on the firewall in the unattended.xml for the apply OS task sequence, we have not seen the issue...

 

Give this a try and let me know if it works for you too..

 

Thanks,

Squirre1

 

ORRR. you could just have your first Apply Network Settings task sequence just join you to a workgroup and then later on as a "Image completed successfully" task group put another Apply network Settings that then joins it to the domain...

 

Just a thought...

[gvlaarho]

This is effectively works, but it's just a workaround and this is well a bug. So i have removed for the moment the "Client Push Installation" and "Software update-based client installation" and had activated it at hierarchy level for 25 days; almost all clients are upgraded now (Administration -> sites -> cas or pirmary site -> Hierarchy settings -> Client Upgrade Tab

(for administraion reason, TS can't be modified)

Thanks you