CLIENT PUSH INSTALLATION PROBLEM

From: Ivan P (IvanP_at_discussions.microsoft.com)
Date: 02/08/05

Next message: Mark Morrell: "Re: Legacy clients can't send back confirmation of install"
Previous message: Madan: "Manual addition's to collection"
Next in thread: William: "RE: CLIENT PUSH INSTALLATION PROBLEM"
Reply: William: "RE: CLIENT PUSH INSTALLATION PROBLEM"
Messages sorted by: [ date ] [ thread ]

Date: Tue, 8 Feb 2005 05:37:06 -0800

Hi, I need help

I have recently installed SMS 2003. One central site with advanced security
and seven primary child sites with standar security.
The fact is that I have manually installed SMS clients (Workstations)
without problems but when I wanna use Client Push Installation to deploy
other clients (servers and DC's) and nothing seems to be wrong.
I have reviewed the settings and I don't find anything that could help me to
find out what happen.
In Client Push Installation Properties I have enable Client Push to servers
and domain controlers, Platform dependent. I have several accounts with local
and domain administrative credentials and the sms service account. How can I
give the SMS service account local administrative rights on a DC?
When I launch Client Push Installation wizard only checks the machines that
have SMS client installed. Please, how can I do to resolve this?

I send part of the ccm.log if it can help

Submitted request successfully $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8
14:05:27.861 2005 Romance Standard Time><thread=5568 (0x15C0)>
Getting a new request from queue "Incoming" after 100 millisecond delay.
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:05:27.861 2005 Romance Standard
Time><thread=5568 (0x15C0)>
Waiting for change in directory "D:\SMS\inboxes\ccr.box" for queue
"Incoming", (30 minute backup timeout). $$<SMS_CLIENT_CONFIG_MANAGER><Tue
Feb 8 14:05:27.861 2005 Romance Standard Time><thread=5568 (0x15C0)>
CCR count in queue "Incoming" is 0. $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8
14:07:49.754 2005 Romance Standard Time><thread=4316 (0x10DC)>
CCR count in queue "Processing" is 0. $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb
8 14:07:49.754 2005 Romance Standard Time><thread=4316 (0x10DC)>
Sleeping for 279 seconds... $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8
14:07:49.754 2005 Romance Standard Time><thread=4316 (0x10DC)>
Sleeping for 60 minutes for queue "Retry".
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:10:46.857 2005 Romance Standard
Time><thread=5716 (0x1654)>
The Site Control File has not changed since the last parameter update.
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:12:28.941 2005 Romance Standard
Time><thread=4316 (0x10DC)>
Updating Site Parameters $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8
14:12:30.411 2005 Romance Standard Time><thread=4316 (0x10DC)>
MP Port: 80 $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:12:30.411 2005
Romance Standard Time><thread=4316 (0x10DC)>
Default MP: SPSCSMSWINTEL $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8
14:12:30.411 2005 Romance Standard Time><thread=4316 (0x10DC)>
-*- Normal Security Mode detected -*- $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb
8 14:12:30.411 2005 Romance Standard Time><thread=4316 (0x10DC)>
Checking configuration information for server: \\SPSCSMSWINTEL\.
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:12:30.411 2005 Romance Standard
Time><thread=4316 (0x10DC)>
Install on DC: True $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:12:30.427
2005 Romance Standard Time><thread=4316 (0x10DC)>
Sleeping for 11 seconds... $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8
14:12:33.866 2005 Romance Standard Time><thread=4316 (0x10DC)>
CCR count in queue "Retry" is 0. $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8
14:12:44.874 2005 Romance Standard Time><thread=4316 (0x10DC)>
Sleeping for 1189 seconds... $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8
14:12:44.874 2005 Romance Standard Time><thread=4316 (0x10DC)>
Thread has been inactive too long. Closing thread
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:15:25.655 2005 Romance Standard
Time><thread=552 (0x228)>
--- This thread is terminating due to inactivity
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:15:25.655 2005 Romance Standard
Time><thread=552 (0x228)>
----- Terminated CCR processing thread. There are now 3 processing threads
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:15:25.655 2005 Romance Standard
Time><thread=552 (0x228)>
Thread has been inactive too long. Closing thread
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:15:25.686 2005 Romance Standard
Time><thread=516 (0x204)>
--- This thread is terminating due to inactivity
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:15:25.686 2005 Romance Standard
Time><thread=516 (0x204)>
----- Terminated CCR processing thread. There are now 2 processing threads
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:15:25.686 2005 Romance Standard
Time><thread=516 (0x204)>
Thread has been inactive too long. Closing thread
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:15:26.702 2005 Romance Standard
Time><thread=4996 (0x1384)>
--- This thread is terminating due to inactivity
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:15:26.702 2005 Romance Standard
Time><thread=4996 (0x1384)>
----- Terminated CCR processing thread. There are now 1 processing threads
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:15:26.702 2005 Romance Standard
Time><thread=4996 (0x1384)>
Thread has been inactive too long. Closing thread
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:15:27.312 2005 Romance Standard
Time><thread=4324 (0x10E4)>
--- This thread is terminating due to inactivity
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:15:27.312 2005 Romance Standard
Time><thread=4324 (0x10E4)>
----- Terminated CCR processing thread. There are now 0 processing threads
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:15:27.312 2005 Romance Standard
Time><thread=4324 (0x10E4)>
The Site Control File has not changed since the last parameter update.
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:32:34.680 2005 Romance Standard
Time><thread=4316 (0x10DC)>
Updating Site Parameters $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8
14:32:34.680 2005 Romance Standard Time><thread=4316 (0x10DC)>
MP Port: 80 $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:32:34.680 2005
Romance Standard Time><thread=4316 (0x10DC)>
Default MP: SPSCSMSWINTEL $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8
14:32:34.680 2005 Romance Standard Time><thread=4316 (0x10DC)>
-*- Normal Security Mode detected -*- $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb
8 14:32:34.680 2005 Romance Standard Time><thread=4316 (0x10DC)>
Checking configuration information for server: \\SPSCSMSWINTEL\.
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:32:34.680 2005 Romance Standard
Time><thread=4316 (0x10DC)>
Install on DC: True $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8 14:32:34.680
2005 Romance Standard Time><thread=4316 (0x10DC)>
Sleeping for 1200 seconds... $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 8
14:32:34.774 2005 Romance Standard Time><thread=4316 (0x10DC)>

Thanks in advance,

Ivan P

Next message: Mark Morrell: "Re: Legacy clients can't send back confirmation of install"
Previous message: Madan: "Manual addition's to collection"
Next in thread: William: "RE: CLIENT PUSH INSTALLATION PROBLEM"
Reply: William: "RE: CLIENT PUSH INSTALLATION PROBLEM"
Messages sorted by: [ date ] [ thread ]

Relevant Pages

Re: sms advanced client installation problem
... > client machines to the SMS site. ... > installion of Advanced Client on machines. ... > The user configured for push installation is a domain administrator. ... > India Standard Time> ...
(microsoft.public.sms.admin)
Re: Advanced Client installation problem
... > client machines to the SMS site. ... > installion of Advanced Client on machines. ... > The user configured for push installation is a domain administrator. ... > India Standard Time> ...
(microsoft.public.sms.setup)
Re: Advanced Client installation problem
... it looks like that the client was still installing. ... > The network discovery detects my domain name and also assignes the> client machines to the SMS site. ... The installation goes> successfully and the client is installed on the machines but the sms ... > Standard Time> ...
(microsoft.public.sms.misc)
Re: After reinstallation
... If you manually install the client and open the system manager in control ... See Ccm.log on site server ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... The MP installation was succesful, ...
(microsoft.public.sms.setup)
Re: Please help - SMS service on the target workstation does not h
... > I have make a MSI with a shortcut pointing to a networkdrive> The problem is in my original MSI the shortcut Destination looks like this ... > and when I´m installing the MSI manually on the locally it works fine, but> when i use SMS ... > have network privileges so cannot see the I: ... During installation of a>> program you can specify SMS to map a specific or any drive letter to a DP>> and run program from a mapped drive. ...
(microsoft.public.sms.swdist)