We created an image for Windows 7 64bit, but when we are trying to deploy the client to a PC it keeps failing on the Task Sequence step Setup windows and ConfigMgr. These are the errors that I see in the logs in the console: The task sequence execution engine failed executing the action (Setup windows and ConfigMgr) in the group () with the error code 16389 Action output: . The operating system reported error 2147500037: Unspecified error The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of 16389 was returned. The operating system reported error 2147500037: Unspecified error When I look at the ccmsetup.log file on the PC, this is what I see: ==========[ ccmsetup started in process 1388 ]========== ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) Version: 4.0.6487.2000 ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /source:"\\sccm01\SCCM_Client" SMSSITECODE=NUH ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) CCMHTTPPORT: 80 ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) CCMHTTPSPORT: 443 ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) CCMHTTPSSTATE: 2147483648 ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) CCMHTTPSCERTNAME: ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) FSP: ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) Config file: ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) Retry time: 10 minute(s) ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) MSI log file: ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) MSI properties: SMSSITECODE="NUH" CCMHTTPPORT="80" CCMHTTPSPORT="443" ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) Source List: ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) \\sccm01\SCCM_Client ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) MPs: ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) None ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) Updated security on object C:\Windows\ccmsetup\. ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 8/11/2011 10:28:29 AM 1392 (0x0570) Running as user "SYSTEM" ccmsetup 8/11/2011 10:28:29 AM 1452 (0x05AC) Detected 141636 MB free disk space on system drive. ccmsetup 8/11/2011 10:28:29 AM 1452 (0x05AC) DetectWindowsEmbeddedFBWF() Detecting OS Version ccmsetup 8/11/2011 10:28:29 AM 1452 (0x05AC) Client OS Version is 6.1, Service Pack Version 0 ccmsetup 8/11/2011 10:28:29 AM 1452 (0x05AC) Client OS is not a supported Windows Embedded Platform ccmsetup 8/11/2011 10:28:29 AM 1452 (0x05AC) Successfully ran BITS check. ccmsetup 8/11/2011 10:28:34 AM 1452 (0x05AC) Downloading file ccmsetup.cab ccmsetup 8/11/2011 10:28:34 AM 1452 (0x05AC) Determining source location... ccmsetup 8/11/2011 10:28:34 AM 1452 (0x05AC) Source \\sccm01\SCCM_Client is inaccessible (5) ccmsetup 8/11/2011 10:28:34 AM 1452 (0x05AC) Failed to find accessible source. Waiting for retry. ccmsetup 8/11/2011 10:28:34 AM 1452 (0x05AC) Next retry in 10 minute(s)... ccmsetup 8/11/2011 10:28:34 AM 1452 (0x05AC) ==========[ ccmsetup started in process 2060 ]========== ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) Version: 4.0.6487.2000 ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) Command line: "C:\_SMSTaskSequence\OSD\NUH00019\ccmsetup.exe" /useronly /config:MobileClient.TCF ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) CCMHTTPPORT: 80 ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) CCMHTTPSPORT: 443 ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) CCMHTTPSSTATE: 0 ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) CCMHTTPSCERTNAME: ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) FSP: ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) CCMFIRSTCERT: 0 ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) No MP or source location has been explicitly specified. Trying to discover a valid content location... ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) Current directory is a valid source location. ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) Config file: C:\_SMSTaskSequence\OSD\NUH00019\MobileClient.TCF ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) Retry time: 10 minute(s) ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) MSI log file: ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) MSI properties: INSTALL="ALL" SMSPROVISIONINGMODE="1" SMSSITECODE="NUH" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" CCMFIRSTCERT="0" ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) Source List: ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) C:\_SMSTaskSequence\OSD\NUH00019 ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) MPs: ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) None ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) Updated security on object C:\Windows\ccmsetup\. ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) Waiting for existing instances of ccmsetup to exit. ccmsetup 8/11/2011 10:28:43 AM 2064 (0x0810) An instance of ccmsetup is running as a service. The current instance will be terminated. ccmsetup 8/11/2011 10:28:48 AM 2064 (0x0810) A Fallback Status Point has not been specified. Message with STATEID='306' will not be sent. ccmsetup 8/11/2011 10:28:48 AM 2064 (0x0810) Source \\sccm01\SCCM_Client is inaccessible (5) ccmsetup 8/11/2011 10:38:34 AM 1452 (0x05AC) Failed to find accessible source. Waiting for retry. ccmsetup 8/11/2011 10:38:34 AM 1452 (0x05AC) Next retry in 10 minute(s)... ccmsetup 8/11/2011 10:38:34 AM 1452 (0x05AC) The command line for the client install is just a simple: CCMSETUP.EXE /noservice SMSSITECODE=AUTO Anyone have any ideas or experience would thing? TIA

"Source \\sccm01\SCCM_Client is inaccessible (5)" How did you create your ConfigMgr Client Agent package specified in that task?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Created a package from definition -> Configuration Manager Client Upgrade -> Always optain files from source directory -> d:\sms\client (this is where the client folder is) -> Created distribution points. That is a new package that I created. I have one that I have been using with all of my x86 clients without any issues for years now, but that one was failing in the same manner.

What's in that directory? Why aren't you using the client folder under your ConfigMgr program files directory? The directory specified should have all the files necessary for installation so that ccmsetup does not have to reach out across the network during OSD to install itself which is what's happening according to the log above. Reaching out to the network during OSD is typically a bad thing because of permissions which is what is happening here.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

My setup was an upgrade from SMS 2003, it was installed on my D: drive in the SMS folder. Inside my d:\SMS\Client folder are the installation files for the SCCM client. The d:\sms\client folder has the following in it: i386 (folder) ia64 (folder) x64 (folder) ccmsetup.cab ccmsetup.exe As I said I have 32bit clients that are and have been working perfectly fine for years with this setup. It just seems to be something special with the x64 (64bit) installation that I am having a problem with.

The only difference between the two would be drivers then. Make sure you have included the proper x64 NIC drivers for use with the deployed OS in whatever fashion you inject drivers. Have you reviewed smsts.log for any errors? Have you dropped to the command-prompt to ensure connectivity?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I made sure that the x64 NIC driver was now applied to the Boot Image and is in the driver packages. I looked int he smsts.log file and did not see any errors, this is the last section with the client install: Successfully complete the action (Setup windows and ConfigMgr) with the exit win32 code 0 TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Sending status message . . . TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Send a task execution status message SMS_TSExecution_ActionCompleteInfo TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) MP server sccm01.enhnet.org and port 80. SSL=false. CRL=false. TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Site code: NUH TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Client machine name: 4901-PC-RM-C TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Client Identity: GUID:71782E2B-C996-4D20-82FF-14027833F87A TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Advertisement ID: NUH200B7 TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Package ID: NUH0003C TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Sending StatusMessage TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Formatted header: TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>98724898-cc62-49aa-ae44-452cd33ac812</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2011-08-12T23:21:06Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="4232"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg> TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) CLibSMSMessageWinHttpTransport::Send: URL: sccm01.enhnet.org:80 CCM_POST /ccm_system/request TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) The request has succeeded. 200 OK TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Expand a string: %_SMSTSMDataPath%\Logs TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Clear local default environment TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) The action (Setup windows and ConfigMgr) requested a retry TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Reboot to local harddisk TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) _OSDGinaIsConfigured variable set to TRUE TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) _SMSTSServiceStartType variable set to TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Calling RebootSystem() TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) OSD type of task sequence. ignore the service window setting TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Path variable _SMSTSBootStagePath converted from C:\_SMSTaskSequence\WinPE to 5A51BCD00000100000000000:\_SMSTaskSequence\WinPE TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Updated security on object C:\_SMSTaskSequence. TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Set a global environment variable _SMSTSNextInstructionPointer=12 TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Set a TS execution environment variable _SMSTSNextInstructionPointer=12 TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Set a global environment variable _SMSTSInstructionStackString=11 TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Set a TS execution environment variable _SMSTSInstructionStackString=11 TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Save the current environment block TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Expand a string: %_SMSTSMDataPath%\Logs TSManager 8/12/2011 3:21:06 PM 1116 (0x045C) Current operating system is Windows PE. Computer will automatically rebooted when the process exits. TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) The action (Setup windows and ConfigMgr) initiated a reboot request TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) Sending status message . . . TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) Send a task execution status message SMS_TSExecution_TaskSequenceRebootInfo TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) MP server sccm01.enhnet.org and port 80. SSL=false. CRL=false. TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) Site code: NUH TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) Client machine name: 4901-PC-RM-C TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) Client Identity: GUID:71782E2B-C996-4D20-82FF-14027833F87A TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) Advertisement ID: NUH200B7 TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) Package ID: NUH0003C TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) Sending StatusMessage TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) Formatted header: TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>98724898-cc62-49aa-ae44-452cd33ac812</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2011-08-12T23:21:36Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="2200"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg> TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) CLibSMSMessageWinHttpTransport::Send: URL: sccm01.enhnet.org:80 CCM_POST /ccm_system/request TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) The request has succeeded. 200 OK TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) **************************************************************************** TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) Execution engine result code: 2 (Success=0, Failure=1, RebootInitiated=2) TSManager 8/12/2011 3:21:36 PM 1116 (0x045C) Process completed with exit code 2147945410 TSMBootstrap 8/12/2011 3:21:36 PM 1076 (0x0434) Exiting with return code 0x80070BC2 TSMBootstrap 8/12/2011 3:21:36 PM 1076 (0x0434) Execution complete. TSBootShell 8/12/2011 3:21:36 PM 816 (0x0330) I had a command prompt open with a ping running to my server and it never dropped connection. After the PC finished sysprep, I logged in and check, and all of the drivers are installed properly. I'm at a loss as to why this keeps failing.

As Jason has mentioned, there is a problem in accessing the SCCM_Client share on the MP. Here are a few of my suspicions: 1. The client has not yet joined the domain. 2. The permissions on the 64-bit folder under SCCM_Client are incorrect. 3. The permissions on the SCCM_Client share are incorrect. You could try opening-up the permissions on the SCCM_Client share and its folders. You can also try adding a network access account (I'm not sure if the client setup will use it, but it might be worth the try).

Ok, well it looks like we have slight progress, according to the ccmsetup.log the client has gotten installed properly, however now I see this in the smsts.log after sysprep has run and it trys to continue on with the task sequence: ==============================[ OSDSetupHook.exe ]============================== OSDSetupHook 8/16/2011 4:08:21 PM 1980 (0x07BC) Executing task sequence OSDSetupHook 8/16/2011 4:08:21 PM 1980 (0x07BC) Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat". OSDSetupHook 8/16/2011 4:08:21 PM 1980 (0x07BC) Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created OSDSetupHook 8/16/2011 4:08:21 PM 1980 (0x07BC) Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created OSDSetupHook 8/16/2011 4:08:21 PM 1980 (0x07BC) Debug shell is enabled OSDSetupHook 8/16/2011 4:08:21 PM 1980 (0x07BC) Successfully enabled debug command shell support. OSDSetupHook 8/16/2011 4:08:21 PM 1980 (0x07BC) Configuring local administrator account OSDSetupHook 8/16/2011 4:08:21 PM 1980 (0x07BC) Enabling local administrator account OSDSetupHook 8/16/2011 4:08:21 PM 1980 (0x07BC) Installing SMS client OSDSetupHook 8/16/2011 4:08:22 PM 1980 (0x07BC) Clearing existing client configuration. OSDSetupHook 8/16/2011 4:08:22 PM 1980 (0x07BC) Cleaning existing client certificates from SMS certificate store OSDSetupHook 8/16/2011 4:08:22 PM 1980 (0x07BC) Restoring SMS client identity. OSDSetupHook 8/16/2011 4:08:22 PM 1980 (0x07BC) Successfully restored SMS certificate store. OSDSetupHook 8/16/2011 4:08:22 PM 1980 (0x07BC) Successfully restored the client identity. OSDSetupHook 8/16/2011 4:08:22 PM 1980 (0x07BC) Site in native mode: false OSDSetupHook 8/16/2011 4:08:22 PM 1980 (0x07BC) Using CRL: false OSDSetupHook 8/16/2011 4:08:22 PM 1980 (0x07BC) Executing command line: "C:\Windows\system32\_SMSOSDSetup\TsProgressUI.exe" /Register:WinPE OSDSetupHook 8/16/2011 4:08:22 PM 1980 (0x07BC) Launching command shell. OSDSetupHook 8/16/2011 4:08:22 PM 2036 (0x07F4) executing command: C:\Windows\system32\cmd.exe /k OSDSetupHook 8/16/2011 4:08:22 PM 2036 (0x07F4) executed command: C:\Windows\system32\cmd.exe /k OSDSetupHook 8/16/2011 4:08:22 PM 2036 (0x07F4) ==========[ TsProgressUI started in process 1864 ]========== TsProgressUI 8/16/2011 4:08:22 PM 284 (0x011C) Registering COM classes TsProgressUI 8/16/2011 4:08:22 PM 284 (0x011C) sbModulePath = C:\Windows\system32\_SMSOSDSetup\TsProgressUI.exe TsProgressUI 8/16/2011 4:08:22 PM 284 (0x011C) Shutdown complete. TsProgressUI 8/16/2011 4:08:22 PM 284 (0x011C) Process completed with exit code 0 OSDSetupHook 8/16/2011 4:08:22 PM 1980 (0x07BC) Successfully registered TS Progress UI. OSDSetupHook 8/16/2011 4:08:22 PM 1980 (0x07BC) Failed to create instance of progress UI (0x80070015) OSDSetupHook 8/16/2011 4:08:22 PM 1980 (0x07BC) Executing command line: "C:\_SMSTaskSequence\OSD\NUH0003E\ccmsetup.exe" /useronly /config:MobileClient.TCF OSDSetupHook 8/16/2011 4:08:22 PM 1980 (0x07BC) Process completed with exit code 1 OSDSetupHook 8/16/2011 1:08:27 PM 1980 (0x07BC) Client installation failed, code 1 OSDSetupHook 8/16/2011 1:08:27 PM 1980 (0x07BC) Formatted header: OSDSetupHook 8/16/2011 1:08:27 PM 1980 (0x07BC) <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:929DD95D-840A-4DE1-AEA9-4E68E3A727AD</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2011-08-16T18:08:27Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="1698"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg> OSDSetupHook 8/16/2011 1:08:27 PM 1980 (0x07BC) Formatted header: OSDSetupHook 8/16/2011 1:08:27 PM 1980 (0x07BC) <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:929DD95D-840A-4DE1-AEA9-4E68E3A727AD</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2011-08-16T18:08:27Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="1504"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg> OSDSetupHook 8/16/2011 1:08:27 PM 1980 (0x07BC) Failed to install SMS Client (0x80004005) OSDSetupHook 8/16/2011 1:08:27 PM 1980 (0x07BC) Waiting for command shell to complete. OSDSetupHook 8/16/2011 1:08:27 PM 2036 (0x07F4)