×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

*
*
*
*

Thanks. We have received your request and will respond promptly.

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

client push installation failure sccm 2007

thread22-1538244

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

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)

RE: client push installation failure sccm 2007

Out of interest is this a new SCCM installation? Are the SCCM object created successfully in AD (Did you use ADSIEdit to create the System Management Container?)?

Simon

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

 

RE: client push installation failure sccm 2007

(OP)
yes simon, this is the new sccm installation. it was a hustle to get it installed leave alone configuring. i used AD system discovery to get the computers....

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

Received request: "DPYMDKXX" for machine name: "C2" on queue: "Incoming".    SMS_CLIENT_CONFIG_MANAGER    3/23/2009 2:20:01 PM    3652 (0x0E44)
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

OK, if you open up Active Directory Users and Computers, click on Advanced Features (on the View tab), and then go down to the System container, in there do you have a System Management container and does it contain your Management Point and Site AD objects?

 

Simon

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

 

RE: client push installation failure sccm 2007

(OP)
yes simon it does....

i had problems with my dns. but i think i have solved those as nslookup no longer brings up

Quote:

Non-existent domain

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

======>Begin Processing request: "REJAAOBA", machine name: "C2"    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.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

You need to set up the Client Push Account in the Client Distribution Methods tab (Client Push\Accounts tab), it needs to be an account that also has local admin rights on the machine.  

Simon

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

 

RE: client push installation failure sccm 2007

(OP)
thanx, i have done that and now...ccm.log says this

CODE

---> Trying each entry in the SMS Client Remote Installation account list    SMS_CLIENT_CONFIG_MANAGER    3/23/2009 5:32:23 PM    6372 (0x18E4)
---> 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

Is the Windows firewall disabled? Try disabling it and trying again.

Simon

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

 

RE: client push installation failure sccm 2007

(OP)
the windows firewall is disabled. personally, this is my biggest snag WMI failing to connect. lemme try again with uninstalling all firewalls and antivirus. i'll inform you of any outcome in a second

RE: client push installation failure sccm 2007

On one of your machines (not the client you're trying to connect to) run wmimgmt.msc and try connecting to the remote client.

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

(OP)
ok, i only have a lab with two computers for testing purpose.

[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

(OP)
ive tried ipconfig on the server with /renew switch and this is the message i get

CODE

Microsoft Windows [Version 5.2.3790]
(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

Are you running a static address or dhcp? if you're running a static address then the /renew won't do anything for you.

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

(OP)
well, i have a static address...duh. stupid me. i have run sfc /scannow...no problems reported. i wonder if there is a log file for this.

how do i fix wmi on the client computer?

RE: client push installation failure sccm 2007

Have you checked to see if the RPC Server service is running?

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

(OP)
well,
    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

CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e    SMS_CLIENT_CONFIG_MANAGER    3/25/2009 3:16:32 PM    7120 (0x1BD0)
---> 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)
any ideas
  

RE: client push installation failure sccm 2007

error = 0x8004100e is an incorrect namespace error, it's been suggested that the FQDN of the site server could be configured incorrectly.

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

(OP)
hmmm.....im running win2k3 sp2, sccm 2007
my fqdn is correct. its jordahsrv.topdog.net. this is the latest snippet from ccmlog

CODE

======>Begin Processing request: "NSJTSOCW", machine name: "CLIENT"    SMS_CLIENT_CONFIG_MANAGER    3/25/2009 5:30:02 PM    3564 (0x0DEC)
---> 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

To be honest with you, have you tried installing the client locally rather that trying the push method?

Simon

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

 

RE: client push installation failure sccm 2007

(OP)
i can install it locally and ive done this before. i dnt think this is the way to go. if i went to one of our clients and say he had 200 workstations, it would be wierd to suggest manual client installation for all machines. this is supposed to be sccm main advantage.

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

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.

 

RE: client push installation failure sccm 2007

(OP)

Quote:

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?
 

RE: client push installation failure sccm 2007

File and print sharing turned on?

Your are in mixed mode not native?

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login
Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close