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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SMS 2.0 Client problem

Status
Not open for further replies.

bengoa

MIS
Nov 17, 2003
2
US
Scenario: I had a domaim setup with SMS. All computer in
the defined boundary had the clients installed. I needed
to move client to a new AD domiain (from scratch not
migration). I also setup a new SMS server on the new
domain. I went ahead and unistalled the client using a tool
found it the SMS cd "20clicln.bat".

Problem: Computers that had the old SMS client installed
are not getting the client from the new site installation. New computer that are added to the domain receive the SMS
client.

I am running SMS 2.0 SP 5 (1493).

Can anyone recommend how I should go about to installing
the client on these computer. I have LOGON DISCOVERY ON.

Thanks in advance for you help!
Alex

I tried to install the SMS Manually using the SMSMAN.exe and nothing happens.

HERE IS A COPY OF WN_LOG:
======= Logging initialized for module &quot;SMSBOOT1.EXE&quot; ======= $$<><<Tue Nov 04 16:03:45.390 2003><>

iCodePageMBCS is 0 now $$<SMSBOOT1.EXE><<Tue Nov 04 16:03:45.390 2003><>

argv[0]=&quot;\\CAEPH-NS1\NETLOGON\SMSBOOT1.EXE&quot; $$<SMSBOOT1.EXE><<Tue Nov 04 16:03:45.390 2003><>

argv[1]=&quot;-S&quot; $$<SMSBOOT1.EXE><<Tue Nov 04 16:03:45.390 2003><>

argv[2]=&quot;\\CAEPH-NS1\NETLOGON\login.bat\..\smsls&quot; $$<SMSBOOT1.EXE><<Tue Nov 04 16:03:45.390 2003><>

argv[3]=&quot;-N&quot; $$<SMSBOOT1.EXE><<Tue Nov 04 16:03:45.390 2003><>

argv[4]=&quot;-WINDIR=C:\WINNT&quot; $$<SMSBOOT1.EXE><<Tue Nov 04 16:03:45.390 2003><>

Retrieved szClientPath &quot;C:\WINNT&quot; from GetPathFromEnvironmentString(SMS_LOCAL_DIR_VARIABLE), dwRet = 0 $$<SMSBOOT1.EXE><<Tue Nov 04 16:03:45.390 2003><>

szClientPath=&quot;C:\WINNT\&quot; $$<SMSBOOT1.EXE><<Tue Nov 04 16:03:45.390 2003><>

szClientExe=&quot;C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe&quot; $$<SMSBOOT1.EXE><<Tue Nov 04 16:03:45.390 2003><>

szServerPath=&quot;\\CAEPH-NS1\SMSLOGON&quot;~ $$<SMSBOOT1.EXE><<Tue Nov 04 16:03:45.440 2003><>

szServerExe=&quot;\\CAEPH-NS1\SMSLOGON\x86.bin\Boot32wn.exe&quot; $$<SMSBOOT1.EXE><<Tue Nov 04 16:03:45.440 2003><>

Copied &quot;\\CAEPH-NS1\SMSLOGON\x86.bin\Boot32wn.exe&quot; to &quot;C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe&quot; $$<SMSBOOT1.EXE><<Tue Nov 04 16:03:45.880 2003><>

Wrote &quot;SMSServerPath=\\CAEPH-NS1\SMSLOGON&quot; into file &quot;C:\WINNT\TEMP\SMSBOOT1.INI&quot;, iRet = 1 $$<SMSBOOT1.EXE><<Tue Nov 04 16:03:45.880 2003><>

Wrote &quot;Bootstrap2Parameters=-S \\CAEPH-NS1\NETLOGON\login.bat\..\smsls -N -WINDIR=C:\WINNT &quot; into file &quot;C:\WINNT\TEMP\SMSBOOT1.INI&quot;, iRet = 1 $$<SMSBOOT1.EXE><<Tue Nov 04 16:03:45.990 2003><>

Wrote &quot;SMSClientPath=C:\WINNT\&quot; into file &quot;C:\WINNT\TEMP\SMSBOOT1.INI&quot;, iRet = 1 $$<SMSBOOT1.EXE><<Tue Nov 04 16:03:46.050 2003><>

Calling _spawnl(&quot;C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe&quot;, &quot;C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe&quot;, &quot;-NT&quot;, &quot;-OC:\WINNT\TEMP\SMSBOOT1.INI&quot;, NULL, NULL) $$<SMSBOOT1.EXE><<Tue Nov 04 16:03:46.050 2003><>

======= Logging initialized for module &quot;C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe&quot; ======= $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:46.895 2003><thread=2284 (0x8EC)>
SMSClientPath (from &quot;C:\WINNT\TEMP\SMSBOOT1.INI&quot;) is &quot;C:\WINNT\&quot; $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:46.895 2003><thread=2284 (0x8EC)>
SMSTempClientPath (from &quot;C:\WINNT\TEMP\SMSBOOT1.INI&quot;) is &quot;&quot; $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:46.911 2003><thread=2284 (0x8EC)>
SMSServerPath (from &quot;C:\WINNT\TEMP\SMSBOOT1.INI&quot;) is &quot;\\CAEPH-NS1\SMSLOGON&quot; $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:46.927 2003><thread=2284 (0x8EC)>
Boot2 options specified: &quot;-S \\CAEPH-NS1\NETLOGON\login.bat\..\smsls -N -WINDIR=C:\WINNT&quot; $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:46.927 2003><thread=2284 (0x8EC)>
Computer name is PRODUCER $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:46.927 2003><thread=2284 (0x8EC)>
Altered console properties $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:46.942 2003><thread=2284 (0x8EC)>
Running on Windows NT 5 or above $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:46.942 2003><thread=2284 (0x8EC)>
osvie.wProductType = 3 $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:46.942 2003><thread=2284 (0x8EC)>
osvie.wSuiteMask = 274 $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:46.942 2003><thread=2284 (0x8EC)>
Building local list of site versions on logon point (\\CAEPH-NS1\SMSLOGON) $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:46.974 2003><thread=2284 (0x8EC)>
Clicore version on logon point (from site CAE) is 2.00.1493.5011 $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:47.020 2003><thread=2284 (0x8EC)>
Client has not been assigned to a site... $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:47.052 2003><thread=2284 (0x8EC)>
Reading TCF file \\CAEPH-NS1\SMSLOGON\CONFIG\winnt.tcf $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:47.067 2003><thread=2284 (0x8EC)>
File to copy : \\CAEPH-NS1\SMSLOGON\x86.bin\smsboot1.exe to C:\WINNT\MS\SMS\CORE\BIN\smsboot1.exe~ $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:47.099 2003><thread=2284 (0x8EC)>
Copying file &quot;\\CAEPH-NS1\SMSLOGON\x86.bin\smsboot1.exe&quot; to &quot;C:\WINNT\MS\SMS\CORE\BIN\smsboot1.exe&quot; $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:47.224 2003><thread=2284 (0x8EC)>
... File copied $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:47.333 2003><thread=2284 (0x8EC)>
File to copy : \\CAEPH-NS1\SMSLOGON\x86.bin\clicore.exe to C:\WINNT\MS\SMS\CORE\BIN\clicore.exe~ $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:47.333 2003><thread=2284 (0x8EC)>
Copying file &quot;\\CAEPH-NS1\SMSLOGON\x86.bin\clicore.exe&quot; to &quot;C:\WINNT\MS\SMS\CORE\BIN\clicore.exe&quot; $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:47.817 2003><thread=2284 (0x8EC)>
... File copied $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:48.677 2003><thread=2284 (0x8EC)>
File to copy : \\CAEPH-NS1\SMSLOGON\x86.bin\SlwNt32.exe to C:\WINNT\MS\SMS\CORE\BIN\SlowNet.exe~ $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:48.677 2003><thread=2284 (0x8EC)>
File Doesn't need copying~ $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:48.896 2003><thread=2284 (0x8EC)>
Writing local TCF file C:\WINNT\MS\SMS\CORE\DATA\temp.tcf $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:48.911 2003><thread=2284 (0x8EC)>
~Checking for client config file \\CAEPH-NS1\SMSLOGON\sites\CAE\cli_inst.cfg $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:48.927 2003><thread=2284 (0x8EC)>
Waiting up to one minute for sites subtree mutex $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:48.927 2003><thread=2284 (0x8EC)>
~Reading client installation base registry settings from \\CAEPH-NS1\SMSLOGON\sites\CAE\cli_inst.cfg $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:48.942 2003><thread=2284 (0x8EC)>
~Writing shared config items out to registry under site CAE subtree $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:49.083 2003><thread=2284 (0x8EC)>
~Config items written to registry successfully $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:49.161 2003><thread=2284 (0x8EC)>
Environment variable SMS_LOCAL_DIR set to C:\WINNT $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:49.161 2003><thread=2284 (0x8EC)>
Current environment variable SMS_LOCAL_DIR_USER set to C:\WINNT $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:49.177 2003><thread=2284 (0x8EC)>
Successfully launched &quot;C:\WINNT\MS\SMS\CORE\BIN\CliCore.exe /S DISC &quot;, Process ID: 0x604 $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:49.208 2003><thread=2284 (0x8EC)>
Waiting for Process &quot;C:\WINNT\MS\SMS\CORE\BIN\CliCore.exe /S DISC &quot; to finish... $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:49.224 2003><thread=2284 (0x8EC)>
Process &quot;C:\WINNT\MS\SMS\CORE\BIN\CliCore.exe /S DISC &quot; finished. $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:58.755 2003><thread=2284 (0x8EC)>
Begin CliEx processing. $$<C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe><Tue Nov 04 16:03:58.755 2003><thread=2284 (0x8EC)>
======= Logging initialized for module &quot;CliEx32.dll&quot; ======= $$<CliEx32.dll><Tue Nov 04 16:03:58.896 2003><thread=2284 (0x8EC)>
Loaded by executable C:\WINNT\MS\SMS\CORE\BIN\Boot32wn.exe $$<CliEx32.dll><Tue Nov 04 16:03:58.896 2003><thread=2284 (0x8EC)>
Found Local SMS Path in the registry: &quot;C:\WINNT\MS\SMS&quot; $$<CliEx32.dll><Tue Nov 04 16:04:00.162 2003><thread=2284 (0x8EC)>
Local path set to C:\WINNT\MS\SMS; local data directory set to C:\WINNT\MS\SMS\CORE\DATA. $$<CliEx32.dll><Tue Nov 04 16:04:00.177 2003><thread=2284 (0x8EC)>
 
I would first go to the clients and add the &quot;SMS Client Deinstall = true&quot; key to the registry. Bounce the sms client service and then wait about 5 mintues for it to uninstall the client. Once that is done, go in and clean the NAL and the SMS sections out of the registry.

Clients should install.
 
More info:
Thanks to all who have sent me suggestion.

I have check the boundraries and they are ok. I even checked the subnet on the network connections of the DC and SITE SERVER to make sure that the machines I wanted to see were included. When I bring a new computer that has never had SMS it gets assigned with no problem. The problem that I am having are computers which had the installation previosly.

On the SMS server I have now enabled all the discovery agents.

On the machine I provide you the log perviously and I ran the uninstall tool 20clicle.bat. I also read some literature on registry keys associated with SMS. I deleted the HLM\SOFTWARE\MICROSOFT\SMS key. It also mention a NAL key but it looks like the clean utility removed it. (Is there something else I can do to verify that the software is indeed unistalled.)

I restarted and logged in. Nothing happen. I check for the WINNT\MS directory and there was nothing.
So I went to the share on a DC and ran SMSMAN. The install was unsucessful.
Several registries keys under SMS were created on the SMS computer. The applet on the control panel was not there. There were not file in WIN\MS\SMS other than a log folder. I obtained the following log WNMANUAL.log (see below). :
======= Logging initialized for module &quot;\\caeph-ns1\SMSLOGON\x86.bin\00000409\SMSMan.exe&quot; ======= $$<\\caeph-ns1\SMSLOGON\x86.bin\00000409\SMSMan.exe><Tue Nov 18 14:29:10.301 2003><thread=2496 (0x9C0)>
Retrieved szClientPath &quot;C:\WINNT&quot; from GetPathFromEnvironmentString(SMS_LOCAL_DIR_VARIABLE), dwRet = 0~ $$<\\caeph-ns1\SMSLOGON\x86.bin\00000409\SMSMan.exe><Tue Nov 18 14:29:10.316 2003><thread=2496 (0x9C0)>
Client Path=&quot;C:\WINNT\MS\SMS&quot;~ $$<\\caeph-ns1\SMSLOGON\x86.bin\00000409\SMSMan.exe><Tue Nov 18 14:29:10.316 2003><thread=2496 (0x9C0)>
Updated path and root values in the registry~ $$<\\caeph-ns1\SMSLOGON\x86.bin\00000409\SMSMan.exe><Tue Nov 18 14:29:10.332 2003><thread=2496 (0x9C0)>
Terminal services remote session, exiting~ $$<\\caeph-ns1\SMSLOGON\x86.bin\00000409\SMSMan.exe><Tue Nov 18 14:29:10.332 2003><thread=2496 (0x9C0)>


THanks for your help
ALex
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top