Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Client push problem

Status
Not open for further replies.
Jul 5, 2006
42
US
I am having 2 issues pushing out sms advance clients out.

1. On some 2000 servers, the ccmsetp.exe process is running, but it never turns to ccmexec.exe.


2. On some xp machines, I am getting an error 5, enable to connect to machine registry. I can manually map to the admin$ with no problem.

I have been pushing the client from the sms server for the past month, more than half of my computers got it installed, so I know the push accounts work.

Any suggestions???
 
Did the push account get locked out for any reason? What do the logs say under system32\ccmsetup?
 
The accoounts are still pushing out clients to other computers, so I know it's not locked out. Here is the ccmsetup logs from 1 of the servers:

=== Verbose logging started: 7/10/2006 12:54:07 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:\WINNT\system32\ccmsetup\ccmsetup.exe ===
MSI (c) (E0:DC) [12:54:07:125]: Resetting cached policy values
MSI (c) (E0:DC) [12:54:07:125]: Machine policy value 'Debug' is 0
MSI (c) (E0:DC) [12:54:07:125]: ******* RunEngine:
******* Product: C:\WINNT\system32\ccmsetup\{8E99D25F-47B7-4DF1-AD28-A629730BBFDF}\client.msi
******* Action:
******* CommandLine: **********
MSI (c) (E0:DC) [12:54:07:125]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (E0:DC) [12:54:07:125]: Grabbed execution mutex.
MSI (c) (E0:DC) [12:54:37:155]: Failed to connect to server. Error: 0x80080005

MSI (c) (E0:DC) [12:54:37:155]: Failed to connect to server.
MSI (c) (E0:DC) [12:54:37:155]: MainEngineThread is returning 1601
=== Verbose logging stopped: 7/10/2006 12:54:37 ===
 
on that workstation do this:

msiexec /unregister
msiexec /regserver


then try it :-D
 
Tim has nailed it I think. You always beat me to it. Damn GMT offset, you do your best work while I'm in bed.

Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant
 
ncotton, you still have your chance. I ran the msiexec commands from the prompt, but it didn't work. When I try to manually run the client install, I got a windows installer error.

Also, I found some servers that has the client installed, but on my sms console, they are listed as not installed. They are assigned to the site, so i am pretty sure it's not a problem with the bounderies.
 
You might want to install windows installer 3.1 and see if that helps.
 
On the clients that install but dont have a site, take a look at the clientlocation.logs and locationservices.log and see if that indicates anything useful
 
I also get errors on workstations during the client push, here is an example:

======>Begin Processing request: "VKSHFYTX", machine name: "BMOULD010853" SMS_CLIENT_CONFIG_MANAGER 7/11/2006 2:54:53 PM 7320 (0x1C98)
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 7/11/2006 2:54:53 PM 7320 (0x1C98)
---> Attempting to connect to administrative share '\\BMOULD010853\admin$' using account 'pecs.com\SMSClientPush' SMS_CLIENT_CONFIG_MANAGER 7/11/2006 2:54:53 PM 7320 (0x1C98)
---> Connected to administrative share on machine BMOULD010853 using account 'pecs.com\SMSClientPush' SMS_CLIENT_CONFIG_MANAGER 7/11/2006 2:54:53 PM 7320 (0x1C98)
---> Attempting to make IPC connection to share <\\BMOULD010853\IPC$> SMS_CLIENT_CONFIG_MANAGER 7/11/2006 2:54:53 PM 7320 (0x1C98)
---> Unable to obtain Access Token for machine name "BMOULD010853", error 5. SMS_CLIENT_CONFIG_MANAGER 7/11/2006 2:54:53 PM 7320 (0x1C98)
---> ERROR: Unable to access target machine for request: "VKSHFYTX", machine name: "BMOULD010853", error code: 5 SMS_CLIENT_CONFIG_MANAGER 7/11/2006 2:54:53 PM 7320 (0x1C98)
STATMSG: ID=3014 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_CLIENT_CONFIG_MANAGER" SYS=FL-SMS SITE=NGS PID=1324 TID=7320 GMTDATE=Tue Jul 11 18:54:53.435 2006 ISTR0="BMOULD010853" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_CLIENT_CONFIG_MANAGER 7/11/2006 2:54:53 PM 7320 (0x1C98)
Retry request id for "VKSHFYTX" set to "BMOULD010853" SMS_CLIENT_CONFIG_MANAGER 7/11/2006 2:54:53 PM 7320 (0x1C98)
Stored request "BMOULD010853", machine name "BMOULD010853", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 7/11/2006 2:54:53 PM 7320 (0x1C98)
<======End request: "BMOULD010853", machine name: "BMOULD010853". SMS_CLIENT_CONFIG_MANAGER 7/11/2006 2:54:53 PM 7320 (0x1C98)


What is the IPC$ used for? Firewall is completely off, is there another security setting I need to configure?
 
thats file and print sharing i believe is that turned on?

The IPC$ share must enabled. The IPC$ share is used with temporary connections between clients and servers by using named pipes for communication among network programs.

one more thing to look at:


 
File and print is enabled, and I can connect to admin$ fine. I can't remote to the user's registry and expand hkey_local_machine, the permission is set correctly in regedit. I guess I might have some workstations with corrupted registries.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top