client push installation failure sccm 2007

[sirlojik]

hi all,

im having issues with client push installation. i have a snippet of the ccm.log file and want to know what im doing wrong

======>Begin Processing request: "CGFWZADB", machine name: "STN1" SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:23 AM 6532 (0x1984)

---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:23 AM 6532 (0x1984)

---> Attempting to connect to administrative share '\\STN1\admin$' using account 'jordah\administrator' SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:23 AM 6532 (0x1984)

---> The 'best-shot' account has now succeeded 1 times and failed 0 times. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:23 AM 6532 (0x1984)

---> Connected to administrative share on machine STN1 using account 'jordah\administrator' SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:23 AM 6532 (0x1984)

---> Attempting to make IPC connection to share <\\STN1\IPC$> SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:23 AM 6532 (0x1984)

---> Searching for SMSClientInstall.* under '\\STN1\admin$\' SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:23 AM 6532 (0x1984)

Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:25 AM 4820 (0x12D4)

Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:25 AM 4820 (0x12D4)

Waiting for change in directory "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:25 AM 4820 (0x12D4)

CCR count in queue "Retry" is 3. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:37 AM 4672 (0x1240)

Sleeping for 634 seconds... SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:37 AM 4672 (0x1240)

---> System OS version string "5.2.3790" converted to 5.20 SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:50 AM 6532 (0x1984)

---> Service Pack version from machine "STN1" is 2 SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:50 AM 6532 (0x1984)

CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:01 AM 6532 (0x1984)

---> Unable to connect to WMI (r) on remote machine "STN1", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:01 AM 6532 (0x1984)

---> Creating \ VerifyingCopying exsistance of destination directory \\STN1\admin$\system32\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:01 AM 6532 (0x1984)

---> Copying client files to \\STN1\admin$\system32\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:02 AM 6532 (0x1984)

---> Updated service "ccmsetup" on machine "STN1". SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:02 AM 6532 (0x1984)

---> ERROR: Unable to start service "ccmsetup" on machine "STN1", error = 1053. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:34 AM 6532 (0x1984)

---> Failed to install CCM Client Bootstrap component on client (1053) SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:34 AM 6532 (0x1984)

---> Deleting SMS Client Install Lock File '\\STN1\admin$\SMSClientInstall.JFS' SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:34 AM 6532 (0x1984)

Retry request id for "CGFWZADB" set to "STN1" SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:34 AM 6532 (0x1984)

Stored request "STN1", machine name "STN1", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:34 AM 6532 (0x1984)

<======End request: "STN1", machine name: "STN1". SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:34 AM 6532 (0x1984)

Waking up for site control file directory change notification SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

The Site Control File has not changed since the last parameter update. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

Updating Site Parameters SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

MP Ports: 80 SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

MP SSL Ports: 443 SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

IISPreferedPort: 80 SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

IISSSLPreferedPort: 443 SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

Default MP: JORDAH-SRV SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

SSL State: 0 SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

Certificate Selection Criteria: SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

Certificate Store: SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

Select First Certificate: 0 SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

Checking configuration information for server: JORDAH-SRV. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

Checking configuration information for server: JORDAH-SRV. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

Fallback Status Point: jordah-srv.jordah.net SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

Install on DC: True SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

Sleeping for 1200 seconds... SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:24 AM 4672 (0x1240)

Thread has been inactive too long. Closing thread SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:56:15 AM 6436 (0x1924)

--- This thread is terminating due to inactivity SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:56:15 AM 6436 (0x1924)

----- Terminated CCR processing thread. There are now 1 processing threads SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:56:15 AM 6436 (0x1924)

 

[SimonDavies]

You don't have to do it purely by Client Push, you can also do it via GPO (that's why there is an MSI in the client directory as well).

I would also like to point out that just because you're having an issue with one machine in your lab doesn't mean you're going to have an issue on all 200 machines in production.

If I were at your stage now I would be looking at the entire SCCM build just to make sure that I haven't missed anything out, that everything was configured correctly etc.

I have done about 15 SCCM installations in a lab environment, each and everyone of them pushed out the client when I needed them to... once the build itself was correct (WebDev issues, MP issues etc).

It's a fairly forgiving program but if you have issues with your base XP image and issues with the SCCM issues this could be causing you all sorts of headaches.

Simon

The real world is not about exam scores, it's about ability.

 

[sirlojik]

You don't have to do it purely by Client Push, you can also do it via GPO (that's why there is an MSI in the client directory as well).

how do you install thru GPO?

 

[tbrennans]

File and print sharing turned on?

Your are in mixed mode not native?