OSD Task Sequence doesn't continue after (Setup Windows and ConfigMgr)

Hi Everybody,

I just got a very strange situation. Since a few days the Operating System Deployments started to behave very weird.

In most cases the last step of the TS is the :

The task sequence execution engine performed a system reboot initiated by the action (Setup Windows and ConfigMgr) in the group (PostInstall).

But I have some cases, when the deployment is able to finish successfully.

I tried to refresh the packages, which are related to this step, also tried to refresh driver packages, but still the same.

In the ccmsetup.log of one failed client I can see the following:

==========[ ccmsetup started in process 1960 ]==========    ccmsetup    3/31/2015 11:17:17 AM    108 (0x006C)
Running on platform X64    ccmsetup    3/31/2015 11:17:18 AM    108 (0x006C)
Updated security on object C:\WINDOWS\ccmsetup\cache\.    ccmsetup    3/31/2015 11:17:18 AM    108 (0x006C)
Launch from folder D:\_SMSTaskSequence\OSD\A0000003\    ccmsetup    3/31/2015 11:17:18 AM    108 (0x006C)
CcmSetup version: 5.0.7958.1401    ccmsetup    3/31/2015 11:17:18 AM    108 (0x006C)
Failed to open to WMI namespace '\\.\root\cimv2' (80090019)    ccmsetup    3/31/2015 11:17:18 AM    108 (0x006C)
CheckAndLogOSInformation failed with 0x80090019    ccmsetup    3/31/2015 11:17:18 AM    108 (0x006C)
Ccmsetup command line: "D:\_SMSTaskSequence\OSD\A0000003\ccmsetup.exe" /useronly /source:D:\_SMSTaskSequence\OSD\A0000003 /config:MobileClient.TCF /status:532    ccmsetup    3/31/2015 11:17:19 AM    108 (0x006C)
Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.    ccmsetup    3/31/2015 11:17:19 AM    108 (0x006C)
Command line: "D:\_SMSTaskSequence\OSD\A0000003\ccmsetup.exe" /useronly /source:D:\_SMSTaskSequence\OSD\A0000003 /config:MobileClient.TCF /status:532    ccmsetup    3/31/2015 11:17:19 AM    108 (0x006C)
Copying config file from D:\_SMSTaskSequence\OSD\A0000003\MobileClient.TCF to folder C:\WINDOWS\ccmsetup\. Return result: 0x0    ccmsetup    3/31/2015 11:17:19 AM    108 (0x006C)
SslState value: 224    ccmsetup    3/31/2015 11:17:19 AM    108 (0x006C)
CCMHTTPPORT:    80    ccmsetup    3/31/2015 11:17:19 AM    108 (0x006C)
CCMHTTPSPORT:    443    ccmsetup    3/31/2015 11:17:19 AM    108 (0x006C)
CCMHTTPSSTATE:    0    ccmsetup    3/31/2015 11:17:19 AM    108 (0x006C)
CCMHTTPSCERTNAME:        ccmsetup    3/31/2015 11:17:19 AM    108 (0x006C)
Lookup MP:    MYMP.DOMAIN    ccmsetup    3/31/2015 11:17:19 AM    108 (0x006C)
FSP:        ccmsetup    3/31/2015 11:17:19 AM    108 (0x006C)
CCMFIRSTCERT:    1    ccmsetup    3/31/2015 11:17:19 AM    108 (0x006C)
Client is set to use HTTPS when available. The current state is 192.    ccmsetup    3/31/2015 11:17:19 AM    108 (0x006C)
Failed to open to WMI namespace '\\.\root\ccm' (80090019)    ccmsetup    3/31/2015 11:17:19 AM    108 (0x006C)
Failed to open to WMI namespace '\\.\root\ccm' (80090019)    ccmsetup    3/31/2015 11:17:19 AM    108 (0x006C)
Signing Certificate is not available in the store    ccmsetup    3/31/2015 11:17:20 AM    108 (0x006C)
Config file:      C:\WINDOWS\ccmsetup\MobileClientUnicode.tcf    ccmsetup    3/31/2015 11:17:20 AM    108 (0x006C)
Retry time:       10 minute(s)    ccmsetup    3/31/2015 11:17:20 AM    108 (0x006C)
MSI log file:     C:\WINDOWS\ccmsetup\Logs\client.msi.log    ccmsetup    3/31/2015 11:17:20 AM    108 (0x006C)
MSI properties:    INSTALL="ALL" SMSPROVISIONINGMODE="1" SMSSITECODE="A00" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" SMSSLP="MyServer.DOMAIN" CCMFIRSTCERT="1"    ccmsetup    3/31/2015 11:17:20 AM    108 (0x006C)
Source List:    ccmsetup    3/31/2015 11:17:20 AM    108 (0x006C)
                  D:\_SMSTaskSequence\OSD\A0000003    ccmsetup    3/31/2015 11:17:20 AM    108 (0x006C)
MPs:    ccmsetup    3/31/2015 11:17:20 AM    108 (0x006C)
                  None    ccmsetup    3/31/2015 11:17:20 AM    108 (0x006C)
Failed to open to WMI namespace '\\.\root\ccm' (80090019)    ccmsetup    3/31/2015 11:17:20 AM    108 (0x006C)
No version of the client is currently detected.    ccmsetup    3/31/2015 11:17:20 AM    108 (0x006C)
Task 'Configuration Manager Client Retry Task' does not exist    ccmsetup    3/31/2015 11:17:20 AM    108 (0x006C)
Updated security on object C:\WINDOWS\ccmsetup\.    ccmsetup    3/31/2015 11:17:20 AM    108 (0x006C)
A Fallback Status Point has not been specified.  Message with STATEID='100' will not be sent.    ccmsetup    3/31/2015 11:17:20 AM    108 (0x006C)
Successfully deleted existing ccmsetup.exe    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)
Downloading file D:\_SMSTaskSequence\OSD\A0000003\ccmsetup.exe    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)
Downloading D:\_SMSTaskSequence\OSD\A0000003\ccmsetup.exe to C:\WINDOWS\ccmsetup\ccmsetup.exe    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)
File download 16% complete (262144 of 1614504 bytes).    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)
File download 32% complete (524288 of 1614504 bytes).    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)
File download 48% complete (786432 of 1614504 bytes).    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)
File download 64% complete (1048576 of 1614504 bytes).    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)
File download 81% complete (1310720 of 1614504 bytes).    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)
File download 97% complete (1572864 of 1614504 bytes).    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)
File download 100% complete (1614504 of 1614504 bytes).    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)
Download complete.    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)
CreateInstance of CLSID_BackgroundCopyManager failed with 80090019. Unable to check BITS version    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)
This operating system does not contain the correct version of BITS. BITS 2.5 or later is required.    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)
A Fallback Status Point has not been specified.  Message with STATEID='321' will not be sent.    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)
Deleted file C:\WINDOWS\ccmsetup\ccmsetup.exe.download    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)
CcmSetup failed with error code 0x80090019    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)

Basically I do not think it is a client related problem, because as I mentioned above, I have some clients where the TS finished successfully. (I tried to delete a client from sccm and reimport it again, but still the same)

What I also noticed, when I have only 1-2 rollouts, the TS can continue this step. Do you think it can be some performance related issue? (sometimes the CPU usage of SCCM goes above 90-95%)

We only have one central site with one MP.

Thank you in advance,

BR,

Zoltn



  • Edited by zolkin 20 hours 56 minutes ago
March 31st, 2015 6:42am

CcmSetup failed with error code 0x80090019

0x80090019 = The keyset is not defined.

What's your client command line in your Task Sequence ?

I see you are using /config:MobileClient.TCF. What's in Mobileclient.tcf ?

Free Windows Admin Tool Kit Click here and download it now
March 31st, 2015 7:54am


CreateInstance of CLSID_BackgroundCopyManager failed with 80090019. Unable to check BITS version    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)
This operating system does not contain the correct version of BITS. BITS 2.5 or later is required.    ccmsetup    3/31/2015 11:17:21 AM    108 (0x006C)

Is the BITS service up and running?
March 31st, 2015 8:07am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics