client push installation failure sccm 2007
client push installation failure sccm 2007
(OP)
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
im having issues with client push installation. i have a snippet of the ccm.log file and want to know what im doing wrong
CODE
======>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)
---> 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)
RE: client push installation failure sccm 2007
Simon
The real world is not about exam scores, it's about ability.
RE: client push installation failure sccm 2007
btw, this is as far as ive got...running the client on the server works without a problem.
trying client push installation on the workstation leaves me with this in the log.
CODE
Stored request "DPYMDKXX", machine name "C2", in queue "Processing". SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:01 PM 3652 (0x0E44)
======>Begin Processing request: "DPYMDKXX", machine name: "C2" SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:01 PM 652 (0x028C)
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:01 PM 652 (0x028C)
---> Warning: no remote client installation account found SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:01 PM 652 (0x028C)
---> Attempting to connect to administrative share '\\c2.topdog.net\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:01 PM 652 (0x028C)
---> Failed to connect to \\c2.topdog.net\admin$ using machine account (5) SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:01 PM 652 (0x028C)
---> ERROR: Failed to connect to the \\c2.topdog.net\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:01 PM 652 (0x028C)
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:01 PM 652 (0x028C)
---> Warning: no remote client installation account found SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:01 PM 652 (0x028C)
---> Attempting to connect to administrative share '\\C2\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:01 PM 652 (0x028C)
---> Failed to connect to \\C2\admin$ using machine account (5) SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:01 PM 652 (0x028C)
---> ERROR: Failed to connect to the \\C2\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:01 PM 652 (0x028C)
---> ERROR: Unable to access target machine for request: "DPYMDKXX", machine name: "C2", error code: 5 SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:01 PM 652 (0x028C)
Retry request id for "DPYMDKXX" set to "c2_topdog_net" SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:01 PM 652 (0x028C)
Stored request "c2_topdog_net", machine name "C2", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:01 PM 652 (0x028C)
<======End request: "c2_topdog_net", machine name: "C2". SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:01 PM 652 (0x028C)
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:03 PM 3652 (0x0E44)
Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:03 PM 3652 (0x0E44)
Waiting for change in directory "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 3/23/2009 2:20:03 PM 3652 (0x0E44)
it connects to the client using an admin account...that is why i don't comprehend this message.
please advise
RE: client push installation failure sccm 2007
Simon
The real world is not about exam scores, it's about ability.
RE: client push installation failure sccm 2007
i had problems with my dns. but i think i have solved those as nslookup no longer brings up
i have installed a client on the server successfully.
trying to install a client on the workstation brings this up in the ccm.log
CODE
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:33 PM 6436 (0x1924)
---> Warning: no remote client installation account found SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:33 PM 6436 (0x1924)
---> Attempting to connect to administrative share '\\c2.topdog.net\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:33 PM 6436 (0x1924)
---> Failed to connect to \\c2.topdog.net\admin$ using machine account (5) SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:33 PM 6436 (0x1924)
---> ERROR: Failed to connect to the \\c2.topdog.net\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:33 PM 6436 (0x1924)
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:33 PM 6436 (0x1924)
---> Warning: no remote client installation account found SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:33 PM 6436 (0x1924)
---> Attempting to connect to administrative share '\\C2\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:33 PM 6436 (0x1924)
---> Failed to connect to \\C2\admin$ using machine account (5) SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:33 PM 6436 (0x1924)
---> ERROR: Failed to connect to the \\C2\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:33 PM 6436 (0x1924)
---> ERROR: Unable to access target machine for request: "REJAAOBA", machine name: "C2", error code: 5 SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:33 PM 6436 (0x1924)
Retry request id for "REJAAOBA" set to "c2_topdog_net" SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:33 PM 6436 (0x1924)
Stored request "c2_topdog_net", machine name "C2", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:33 PM 6436 (0x1924)
<======End request: "c2_topdog_net", machine name: "C2". SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:33 PM 6436 (0x1924)
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:35 PM 4440 (0x1158)
Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:35 PM 4440 (0x1158)
Waiting for change in directory "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:06:35 PM 4440 (0x1158)
RE: client push installation failure sccm 2007
Simon
The real world is not about exam scores, it's about ability.
RE: client push installation failure sccm 2007
CODE
---> Attempting to connect to administrative share '\\c2.topdog.net\admin$' using account 'topdog\administrator' SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:32:23 PM 6372 (0x18E4)
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:32:23 PM 4440 (0x1158)
Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:32:23 PM 4440 (0x1158)
Waiting for change in directory "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:32:23 PM 4440 (0x1158)
---> Connected to administrative share on machine c2.topdog.net using account 'topdog\administrator' SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:32:23 PM 6372 (0x18E4)
---> Attempting to make IPC connection to share <\\c2.topdog.net\IPC$> SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:32:23 PM 6372 (0x18E4)
---> Searching for SMSClientInstall.* under '\\c2.topdog.net\admin$\' SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:32:23 PM 6372 (0x18E4)
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x80070057 SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:32:24 PM 6372 (0x18E4)
---> Unable to connect to WMI on remote machine "C2", error = 0x80070057. SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:32:24 PM 6372 (0x18E4)
---> Deleting SMS Client Install Lock File '\\c2.topdog.net\admin$\SMSClientInstall.TDS' SMS_CLIENT_CONFIG_MANAGER 3/23/2009 5:32:24 PM 6372 (0x18E4)
RE: client push installation failure sccm 2007
Simon
The real world is not about exam scores, it's about ability.
RE: client push installation failure sccm 2007
RE: client push installation failure sccm 2007
You may well have to do a sfc /scannow to fix things
Simon
The real world is not about exam scores, it's about ability.
RE: client push installation failure sccm 2007
[client machine]
1) when i connect wmi to server computer works like a charm.
2) when i connect to local computer it fails!!!!
[server machine]
1)when i connect to local computer it works.
2)when i connect to client computer it fails saying rpc server is unavailable!!
RE: client push installation failure sccm 2007
CODE
(C) Copyright 1985-2003 Microsoft Corp.
E:\Documents and Settings\Administrator>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 190.200.200.248
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 190.200.200.1
E:\Documents and Settings\Administrator>ipconfig /renew
Windows IP Configuration
The operation failed as no adapter is in the state permissible for
this operation.
E:\Documents and Settings\Administrator>
RE: client push installation failure sccm 2007
If it says that the RPC Server is not working on the client machine then I would check the RPC Server service on that machine.
Have you run the sfc /scannow
Simon
The real world is not about exam scores, it's about ability.
RE: client push installation failure sccm 2007
how do i fix wmi on the client computer?
RE: client push installation failure sccm 2007
Also have a look here as this may also help... http://windowsxp.mvps.org/repairwmi.htm
Simon
The real world is not about exam scores, it's about ability.
RE: client push installation failure sccm 2007
i have run the tool and fixed all the problems it suggested. i ran wbemtest.exe and everything seemed fine.
i can even connect and view both computers and their properties in wmimgmt.msc.
this is the new error wmi gives me notice the difference in error number
CODE
---> Unable to connect to WMI (r) on remote machine "CLIENT", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 3/25/2009 3:16:32 PM 7120 (0x1BD0)
---> Creating \ VerifyingCopying exsistance of destination directory \\CLIENT\admin$\system32\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 3/25/2009 3:16:32 PM 7120 (0x1BD0)
---> Copying client files to \\CLIENT\admin$\system32\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 3/25/2009 3:16:32 PM 7120 (0x1BD0)
---> Copying file "E:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "\\CLIENT\admin$\system32\ccmsetup\MobileClient.tcf" SMS_CLIENT_CONFIG_MANAGER 3/25/2009 3:16:32 PM 7120 (0x1BD0)
---> Updated service "ccmsetup" on machine "CLIENT". SMS_CLIENT_CONFIG_MANAGER 3/25/2009 3:16:33 PM 7120 (0x1BD0)
---> ERROR: Unable to start service "ccmsetup" on machine "CLIENT", error = 1053. SMS_CLIENT_CONFIG_MANAGER 3/25/2009 3:16:33 PM 7120 (0x1BD0)
---> Failed to install CCM Client Bootstrap component on client (1053) SMS_CLIENT_CONFIG_MANAGER 3/25/2009 3:16:33 PM 7120 (0x1BD0)
---> Deleting SMS Client Install Lock File '\\CLIENT\admin$\SMSClientInstall.TDS' SMS_CLIENT_CONFIG_MANAGER 3/25/2009 3:16:33 PM 7120 (0x1BD0)
Retry request id for "XWSFZEGN" set to "CLIENT" SMS_CLIENT_CONFIG_MANAGER 3/25/2009 3:16:33 PM 7120 (0x1BD0)
RE: client push installation failure sccm 2007
Go to Site Systems -> Site Settings -> \\your_sccm_server, bring up the properties for "ConfigMgr site system". Double-check if you entered the right FQDN (including the server name, not only the domain name!)
btw, is this install on 2003 or 2008 server?
Simon
The real world is not about exam scores, it's about ability.
RE: client push installation failure sccm 2007
my fqdn is correct. its jordahsrv.topdog.net. this is the latest snippet from ccmlog
CODE
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:02 PM 3564 (0x0DEC)
---> Attempting to connect to administrative share '\\CLIENT\admin$' using account 'topdog\administrator' SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:02 PM 3564 (0x0DEC)
---> Connected to administrative share on machine CLIENT using account 'topdog\administrator' SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:02 PM 3564 (0x0DEC)
---> Attempting to make IPC connection to share <\\CLIENT\IPC$> SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:02 PM 3564 (0x0DEC)
---> Searching for SMSClientInstall.* under '\\CLIENT\admin$\' SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:02 PM 3564 (0x0DEC)
---> System OS version string "5.2.3790" converted to 5.20 SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:03 PM 3564 (0x0DEC)
---> Service Pack version from machine "CLIENT" is 2 SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:03 PM 3564 (0x0DEC)
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:03 PM 3564 (0x0DEC)
---> Unable to connect to WMI (r) on remote machine "CLIENT", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:03 PM 3564 (0x0DEC)
---> Creating \ VerifyingCopying exsistance of destination directory \\CLIENT\admin$\system32\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:03 PM 3564 (0x0DEC)
---> Copying client files to \\CLIENT\admin$\system32\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:03 PM 3564 (0x0DEC)
---> Copying file "E:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "\\CLIENT\admin$\system32\ccmsetup\MobileClient.tcf" SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:03 PM 3564 (0x0DEC)
---> Updated service "ccmsetup" on machine "CLIENT". SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:03 PM 3564 (0x0DEC)
---> ERROR: Unable to start service "ccmsetup" on machine "CLIENT", error = 1053. SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:04 PM 3564 (0x0DEC)
---> Failed to install CCM Client Bootstrap component on client (1053) SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:04 PM 3564 (0x0DEC)
---> Deleting SMS Client Install Lock File '\\CLIENT\admin$\SMSClientInstall.TDS' SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:04 PM 3564 (0x0DEC)
Retry request id for "NSJTSOCW" set to "CLIENT" SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:04 PM 3564 (0x0DEC)
Stored request "CLIENT", machine name "CLIENT", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:04 PM 3564 (0x0DEC)
<======End request: "CLIENT", machine name: "CLIENT". SMS_CLIENT_CONFIG_MANAGER 3/25/2009 5:30:04 PM 3564 (0x0DEC)
RE: client push installation failure sccm 2007
Simon
The real world is not about exam scores, it's about ability.
RE: client push installation failure sccm 2007
also, it seems to create /system32/ccmsetup on the client machine before it fails. i'll keep trying....
RE: client push installation failure sccm 2007
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.
RE: client push installation failure sccm 2007
how do you install thru GPO?
RE: client push installation failure sccm 2007
Your are in mixed mode not native?