Search the Community

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