USMT Capture Failing only on 64-bit XP
I have an SCCM 2012 primary site server setup as a state migration point. I have a simple task sequence that runs a USMT capture with these steps:
* request state store
* Capture user state
* release state store
That task sequence works perfectly on 32-bit Windows XP, but fails on 64-bit XP.
In the SMSTS.log, I see this over and over:
CryptSignAndEncryptMessage failed.
SignAndEncrypt failed with error (0x80091002)
ClientRequestToSMP::ClientRootShareReuqestToSMP failed. error = (0x80091002)
ClientRequestToSMP::DoRequest failed. error = (0x80091002)
Request to SMP 'http://myserver.my.domain' failed with error (Code 0x80091002). Trying next SMP.
Why does the task sequence fail on 64 bit XP but not 32-bit?
November 2nd, 2012 2:14am
when you created the USMT package, did you point at the root of the folder (%programfiles%\windows aik\tools\usmt ) ?
also, with CM'07 you could have problems if the source machine had the kb 974571 installed, is that the case?
November 2nd, 2012 9:51am
which version of USMT are you using for the 64 bit XP ? (you need USMT 4, for X86 XP you need USMT 3 if migrating to XP or USMT 4 if migrating to Windows 7)
November 2nd, 2012 11:51am
when you created the USMT package, did you point at the root of the folder (%programfiles%\windows aik\tools\usmt ) ?
also, with CM'07 you could have problems if the source machine had the kb 974571 installed, is that the case?
Yes, that is the directory I packaged. We are not using CM 07. We are on SCCM 2012.
November 2nd, 2012 3:52pm
which version of USMT are you using for the 64 bit XP ? (you need USMT 4, for X86 XP you need USMT 3 if migrating to XP or USMT 4 if migrating to
November 2nd, 2012 3:52pm
Here is a longer expert from smsts.log:
Client joined to the XYZ domain. OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Client is a member of the ABC site. OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
DHCP entry points already initialized. OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Begin checking Alternate Network Configuration OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Finished checking Alternate Network Configuration OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Adapter {68E71F66-8661-4685-AC8A-5E9777D2FF24} is DHCP enabled. Checking quarantine status. OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Loading client certificates. OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Setting the client certificate provider to Microsoft Enhanced RSA and AES Cryptographic Provider. OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Successfully set the client certificate provider to Microsoft Enhanced RSA and AES Cryptographic Provider OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Successfully set the client certificate provider to Microsoft Enhanced RSA and AES Cryptographic Provider OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Requesting public key information from http://MyMP.My.Domain:0. OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Received 2188 byte response. OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Verifying certificate signature. OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Signature matches OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Certificate is a self signed certificate. It will not be checked for revocation or expiration. OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Successfuly retrieved public key and verified signature. OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Sending share info request message: <RequestStateStore><ClientID>GUID:1D67413A-E358-474B-826E-97CF332D313A</ClientID><Reserved2>308202EC308201D8A00302010202101D8B54098DFF9E8F44A3051DDAD079B1300906052B0E03021D05003028311830160603550403130F484F5532444D584C30313631364453310C300A06035504031303534D533020170D3132313033313231303734305A180F32313132313030383231303734305A3028311830160603550403130F484F5532444D584C30313631364453310C300A06035504031303534D5330820122300D06092A864886F70D01010105000382010F003082010A0282010100B8D1A3F2B09F9431FBC2EB96875C949953BF5EAE5BFAED87DFE9F6E0AF55ACA00863A0578FD9F9E7709E486BB2B0D0C051BA7599088933EE931F1ECAED83E695BB0DD6A427EB45D32066864C808621D394D26C357E1528A9BE60C40280E604BB75A9AE01DA20148EEFBACE12ED73088CE1771C2061A3B93403B8E84B5D57F4AA5A22E876EA94668ADEA03B2C2532F32D5CA69717A89396F86AA1BCE25B9483C83E5F71B26412D28DB1FEE211F32FCB3EC7667B959A0E0039956C2159014231C688D172FA261E160D6B5FCBB0F0967F497B2B8EF819F4D6EEB8F7724BE77C60FFF8C547AD3654366A9F54621C052D3FF90462E956350D6A78938B62855A9B350B0203010001A318301630140603551D25040D300B06092B0601040182376502300906052B0E03021D0500038201010036630BCF6A4C8D0AA9E761AC8E6773D5A34BD08A2DA5890D7CB1102682E5A99B010A78F23796FBE2A614BB603996A7531623A74F0BB2A97005FB530CC8AB1BC0381866F8C876953E85576287D86652BE32FE0EAB488CD40E6E540B15F8D84DCF34028FB838148816E1C95462DB73EA64F32271B24F230179EB9D7F7827F88FA58C16A3305995DBFFE238FFC45546C7166D3D79EE2511F1A73AF29197C9D9BAF117C242DEB75E5A074546AC3F63F212D3CED98D154C48E30491509CB569BF2EC2D0FC790D42702DEAAE93F4430CFCC574237B9F8FA9E3FEC96EA22CF7D59A7E9D7324BF620C4417CB2436EB1405040DCAAD682AC4D709A449E41212D622D9A5F0</Reserved2></RequestStateStore> OSDSMPClient 11/1/2012
5:55:14 PM 3656 (0x0E48)
CryptSignAndEncryptMessage failed. OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
SignAndEncrypt failed with error (0x80091002). OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
ClientRequestToSMP::ClientRootShareRequestToSMP failed. error = (0x80091002). OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
ClientRequestToSMP::DoRequest failed. error = (0x80091002). OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Request to SMP 'http://MyMP.My.Domain' failed with error (Code 0x80091002). Trying next SMP. OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Failed to find an SMP that can serve request after trying 4 attempts. OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
ExecuteCaptureRequestSMP failed (0x80004005). OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
ExecuteCaptureRequest failed (0x80004005). OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
OSDSMPClient finished: 0x00004005 OSDSMPClient 11/1/2012 5:55:14 PM 3656 (0x0E48)
Process completed with exit code 16389 TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
!--------------------------------------------------------------------------------------------! TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
Failed to run the action: Request State Store.
Unknown error (Error: 00004005; Source: Unknown) TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
Set authenticator in transport TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
e*ppCert != NULL failed; 0x80090008 TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
failed to send the request TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
Failed to send status message (80090008) TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
Error calling message lib Send(). Code 0x80090008 TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
Non fatal error 0x80090008 in sending task sequence execution status message to MP TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
Set a global environment variable _SMSTSLastActionRetCode=16389 TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
Clear local default environment TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
Let the parent group (Capture Files & Settings) decides whether to continue execution TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
The execution of the group (Capture Files & Settings) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
Failed to run the last action: Request State Store. Execution of task sequence failed.
Unknown error (Error: 00004005; Source: Unknown) TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
Set authenticator in transport TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
e*ppCert != NULL failed; 0x80090008 TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
failed to send the request TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
Failed to send status message (80090008) TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
Error calling message lib Send(). Code 0x80090008 TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
Non fatal error 0x80090008 in sending task sequence execution status message to MP TSManager 11/1/2012 5:55:14 PM 3800 (0x0ED8)
Task Sequence Engine failed! Code: enExecutionFail TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
**************************************************************************** TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
Task sequence execution failed with error code 80004005 TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
Cleaning Up. TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
Removing Authenticator TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
Cleaning up task sequence folder TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing. TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
Failed to delete directory 'C:\_SMSTaskSequence' TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
Successfully unregistered Task Sequencing Environment COM Interface. TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
Executing command line: "C:\WINDOWS\CCM\TsProgressUI.exe" /Unregister TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
==========[ TsProgressUI started in process 1544 ]========== TsProgressUI 11/1/2012 5:55:33 PM 620 (0x026C)
Unregistering COM classes TsProgressUI 11/1/2012 5:55:33 PM 620 (0x026C)
Shutdown complete. TsProgressUI 11/1/2012 5:55:33 PM 620 (0x026C)
Process completed with exit code 0 TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
Successfully unregistered TS Progress UI. TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
Start to cleanup TS policy TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
End TS policy cleanup TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
Error executing Task Sequence Manager service. Code 0x80004005 TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
Sending error status message TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
Set authenticator in transport TSManager 11/1/2012 5:55:33 PM 3800 (0x0ED8)
e*ppCert != NULL failed; 0x80090008 TSManager 11/1/2012 5:55:34 PM 3800 (0x0ED8)
failed to send the request TSManager 11/1/2012 5:55:34 PM 3800 (0x0ED8)
Failed to send status message (80090008) TSManager 11/1/2012 5:55:34 PM 3800 (0x0ED8)
Error calling message lib Send(). Code 0x80090008 TSManager 11/1/2012 5:55:34 PM 3800 (0x0ED8)
Non fatal error 0x80090008 in sending task sequence execution status message to MP TSManager 11/1/2012 5:55:34 PM 3800 (0x0ED8)
November 2nd, 2012 6:22pm
Any progress on this? Running into exact same issue myself on XP 64-bit. (SCCM 2012)
November 14th, 2012 8:00pm
What have you configured within your State Migration Point properties? Have you specified just a drive letter or a path to a folder? Have you checked that the SMP is healthy and that the MP is healthy? Are your XP systems within the boundaries
of the site system providing the SMP role?
November 15th, 2012 1:52am
I have a support case opened with Microsoft. I'll let you know what we find.
November 16th, 2012 11:27pm
State migration point has drive letter and folder specified. SMP is healthy (no warnings/errors), and so is MP. XP systems are within the boundaries.
The logs are pointing to a cryptography problem. I have an open support case with Microsoft, and they agree with it being cryptography related on the client, but they haven't been able to pin-point the issue.
November 16th, 2012 11:30pm
Try installing KB 968730. I have not tried this myself, but my guess is that the signing is failing because
of the missing SHA-256 support. In the 32-bit XP, SHA-256 was added in SP3, but there is no SP3 for the 64-bit XP.
November 17th, 2012 3:14am
Resolved! I opened a case with MS and in short, KB2661254 needs to be installed. This is due to an older version of Crypt32.dll on the system. I tested this on two XP 64-bit machines having the issue and I was able to then complete the task sequence successfully.
This is the patch:
http://www.microsoft.com/downloads/details.aspx?familyid=9f558bfa-6e97-4f59-8969-6fd98026f3a0
Needs to be installed with this command line:
WindowsServer2003.WindowsXP-KB2661254-x64-ENU.exe /b:SP2QFE
November 26th, 2012 11:32pm
Resolved! I opened a case with MS and in short, KB2661254 needs to be installed. This is due to an older version of Crypt32.dll on the system. I tested this on two XP 64-bit machines having the issue and I was able to then complete the task sequence successfully.
This is the patch:
http://www.microsoft.com/downloads/details.aspx?familyid=9f558bfa-6e97-4f59-8969-6fd98026f3a0
Needs to be installed with this command line:
WindowsServer2003.WindowsXP-KB2661254-x64-ENU.exe /b:SP2QFE
KB2661254 is also what fixed it for me!
November 29th, 2012 4:52pm
thank you! the fix woked like a charm for me as well
July 3rd, 2013 11:05am