Re: Legacy Clients not installing on NT 4.0 during push

From: Jeff Harbaugh [MSFT] (jeffharb_at_online.microsoft.com)
Date: 07/26/04

Next message: Stan White [MS]: "Re: sender issues"

Previous message: Mark Scott [MSFT]: "Re: Advanced Client not Discovering MP"
In reply to: anonymous_at_discussions.microsoft.com: "Re: Legacy Clients not installing on NT 4.0 during push"
Messages sorted by: [ date ] [ thread ]

Date: Mon, 26 Jul 2004 09:17:06 -0700

You can also setup IP subnet ranges so that you do not have to enter every
IP subnet.

-- 
Thanks,
Jeff Harbaugh [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
<anonymous@discussions.microsoft.com> wrote in message 
news:410e01c47312$92b09c70$a401280a@phx.gbl...
>I got it! It was a Site Boundary issue. Apparently SMS
> doesn't like it when you summarize your subnets for the
> Site Boundaries. I had entered 192.168.0.0 for the site
> boundary, thinking this would cover all my subnets. But
> SMS wants the actual network ID of every subnet you want
> to include in the SMS Site. So I had to explicity enter
> 192.168.1.0, 192.168.2.0, ...., etc., and then everything
> worked like a charm. Hope this will help someone else...
>
> Thanks,
> Jeff
>
>>-----Original Message-----
>>Dave,
>>
>>Thanks for the reply.
>>
>>1. I did register the SLP in WINS as SMS_SLP, 1A, Unique.
>>2. The Client Connection Accounts exist.
>>3. When I push, I select the Legacy Client.
>>
>>Any other ideas?
>>
>>Thanks!
>>Jeff
>>
>>>-----Original Message-----
>>>Not sure about this, but here goes.  First, you said
> that
>>the SLP is set up,
>>>is it registered in WINS?  It should have been doen the
>>following way:
>>>To manually add the server locator point entry to WINS
>>>
>>>      1.
>>>     At the command prompt, type netsh, and then press
>>ENTER.
>>>
>>>      2.
>>>     Type wins, and then press ENTER.
>>>
>>>      3.
>>>     Type server, and then press ENTER. To manage a
>>remote WINS server, type
>>>server [\\servername or XXX.XXX.XXX.XXX].
>>>
>>>      4.
>>>     Type the appropriate command, as in the following
>>example:
>>>
>>>add name Name=SMS_SLP endchar=1A rectype=0 ip={static IP
>>of your SLP}
>>>
>>>
>>>To verify that the server locator point WINS entry was
>>added correctly
>>>
>>>      1.
>>>     At the command prompt, type netsh, and then press
>>ENTER.
>>>
>>>      2.
>>>     Type wins, and then press ENTER.
>>>
>>>      3.
>>>     Type server, and then press ENTER. To manage a
>>remote WINS server, type
>>>server [\\servername or XXX.XXX.XXX.XXX].
>>>
>>>      4.
>>>     Type the appropriate command, as in the following
>>example:
>>>
>>>show Name name=SMS_SLP endchar=1A
>>>
>>>
>>>Second,  What account are you using for the client
>>install?  It should be
>>>listed in : Site Heirarchy>Site Settings>Client
>>Installation Methods>Client
>>>Push> Accounts tab.  Also there, check which client is
>>set to push on the
>>>General tab, since they are NT 4,0 clients , it needs to
>>be set to Legacy or
>>>platform dependent if yo uhave a mixed environment.
>>>
>>>Then again, I may be totally wrong :-).
>>>
>>>
>>>
>>>"Jeff" <anonymous@discussions.microsoft.com> wrote in
>>message
>>>news:2bbb01c470bb$a7e89790$a401280a@phx.gbl...
>>>> Hello,
>>>>
>>>> We've just installed SMS 2003, and are having problems
>>>> with the Legacy Clients. When we try to push the Legacy
>>>> Clients to NT 4.0 machines, the install never begins.
> We
>>>> have no problems pushing the advanced client to W2K
>>>> machines. I've verified the following in our
>>environment:
>>>>
>>>> 1. The AD Schema is extended, and the entry for the
> SLP
>>is
>>>> present.
>>>>
>>>> 2. Both the SMS server and the client are registered in
>>>> WINS.
>>>>
>>>> 3. The Client Connection Account is configured and
>>working.
>>>>
>>>> What's confusing is according to the CCM.log, the SMS
>>>> server connects to the NT 4.0 workstation, uploads all
>>the
>>>> files, but the client install never starts. Here is an
>>>> example from the CCM.log...
>>>>
>>>> Started a new CCR processing thread. Thread ID is
> 0x5b4.
>>>> There are now 1 processing threads
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:12.410
>>2004
>>>> Central Daylight Time><thread=2572 (0xA0C)>
>>>> ======>Begin Processing request: "CGBBYHXR", machine
>>>> name: "SMSTEST"  $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul
>>22
>>>> 17:31:12.410 2004 Central Daylight Time><thread=1460
>>>> (0x5B4)>
>>>> Submitted request successfully
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:12.410
>>2004
>>>> Central Daylight Time><thread=2572 (0xA0C)>
>>>> ---> Trying each entry in the SMS Client Remote
>>>> Installation account list~
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:12.410
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> Getting a new request from queue "Incoming" after 100
>>>> millisecond delay.  $$<SMS_CLIENT_CONFIG_MANAGER><Thu
>>Jul
>>>> 22 17:31:12.410 2004 Central Daylight Time><thread=2572
>>>> (0xA0C)>
>>>> ---> Attempting to connect to administrative
>>>> share '\\SMSTEST\admin$' using
>>>> account 'gtl\administrator'~
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:12.410
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> Waiting for change in
> directory "D:\SMS\inboxes\ccr.box"
>>>> for queue "Incoming", (30 minute backup timeout).
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:12.410
>>2004
>>>> Central Daylight Time><thread=2572 (0xA0C)>
>>>> ---> Connected to administrative share on machine
>>SMSTEST
>>>> using account 'gtl\administrator'~
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:12.442
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> ---> Attempting to make IPC connection to share
>>>> <\\SMSTEST\IPC$> ~  $$<SMS_CLIENT_CONFIG_MANAGER><Thu
>>Jul
>>>> 22 17:31:12.473 2004 Central Daylight Time><thread=1460
>>>> (0x5B4)>
>>>> ---> System OS version string "4.0" converted to 4.00
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:12.473
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> ---> Service Pack version from machine "SMSTEST" is 6
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:12.489
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> ---> Could not retrieve the heartbeat time from the
>>client
>>>> (2)~  $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22
>>>> 17:31:12.489 2004 Central Daylight Time><thread=1460
>>>> (0x5B4)>
>>>> ---> Unable to retrieve a sites list from
>>>> machine "SMSTEST".  $$<SMS_CLIENT_CONFIG_MANAGER><Thu
>>Jul
>>>> 22 17:31:12.489 2004 Central Daylight Time><thread=1460
>>>> (0x5B4)>
>>>> ---> Unable to retrieve travel mode switch from
>>>> machine "SMSTEST".  $$<SMS_CLIENT_CONFIG_MANAGER><Thu
>>Jul
>>>> 22 17:31:12.489 2004 Central Daylight Time><thread=1460
>>>> (0x5B4)>
>>>> ---> Unable to retrieve pending command value for sms
>>>> client base components from machine "SMSTEST".
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:12.489
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> ---> Could not retrieve the site config timestamp from
>>the
>>>> client (2)~  $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22
>>>> 17:31:12.504 2004 Central Daylight Time><thread=1460
>>>> (0x5B4)>
>>>> ---> Unable to retrieve the mobile client version from
>>>> machine "SMSTEST".  $$<SMS_CLIENT_CONFIG_MANAGER><Thu
>>Jul
>>>> 22 17:31:12.504 2004 Central Daylight Time><thread=1460
>>>> (0x5B4)>
>>>> ---> Client type to be installed on SMSTEST: Desktop
>>>> client  $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22
>>>> 17:31:12.504 2004 Central Daylight Time><thread=1460
>>>> (0x5B4)>
>>>> ---> Copying client files to
> \\SMSTEST\admin$\sms_temp.~
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:12.504
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> ---> Copying file "D:\SMS\inboxes\clicomp.src\base\I386
>>>> \CCMCore.exe"
> to "\\SMSTEST\admin$\sms_temp\CCMCore.exe"
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:12.598
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> ---> Copying
>>>> file "D:\SMS\inboxes\clicomp.src\base\compver.ini"
>>>> to "\\SMSTEST\admin$\sms_temp\compver.ini"
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:13.223
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> ---> Copying
>>>> file "D:\SMS\inboxes\clidata.src\cli_inst.cfg"
>>>> to "\\SMSTEST\admin$\sms_temp\cli_inst.cfg"
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:13.254
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> ---> Copying
>>file "D:\SMS\inboxes\clidata.src\caplist.ini"
>>>> to "\\SMSTEST\admin$\sms_temp\caplist.ini"
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:13.270
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> ---> Copying file "D:\SMS\bin\I386\CCMData.tcf"
>>>> to "\\SMSTEST\admin$\sms_temp\CCMData.tcf"
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:13.285
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> ---> Copying file "D:\SMS\bin\I386\CCMBtLdr.exe"
>>>> to "\\SMSTEST\admin$\sms_temp\CCMBtLdr.exe"
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:13.317
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> ---> Copying file "D:\SMS\bin\I386\clilog.dll"
>>>> to "\\SMSTEST\admin$\sms_temp\clilog.dll"
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:13.489
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> Found Remote Connection Called before
>>>> CreateCCMBootInstallAccount <\\SMSTEST\admin$>.~
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:13.520
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> Found Remote Connection Called before
>>>> CreateCCMBootInstallAccount <\\SMSTEST\IPC$>.~
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:13.520
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> Found Remote Connection Called After
>>>> CreateCCMBootInstallAccount <\\SMSTEST\admin$>.~
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:13.739
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> Found Remote Connection Called After
>>>> CreateCCMBootInstallAccount <\\SMSTEST\IPC$>.~
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:13.739
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> ---> Created service "CCMBoot" on machine "SMSTEST".
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:13.832
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> ---> Started service "CCMBoot" on machine "SMSTEST".
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:15.457
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> ---> Waiting for service to stop
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:31:15.457
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> ---> Service stopped  $$<SMS_CLIENT_CONFIG_MANAGER><Thu
>>>> Jul 22 17:32:45.787 2004 Central Daylight
>>>> Time><thread=1460 (0x5B4)>
>>>> ---> Successfully Started the CCM Client Bootstrap
>>service
>>>> on SMSTEST  $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22
>>>> 17:32:45.787 2004 Central Daylight Time><thread=1460
>>>> (0x5B4)>
>>>> Deleting file
>>>> \\SMSTEST\admin$\profiles\SMSCCMBootAcct&\NTUSER.DAT,
>>>> failed but ignored, Win32 Error = 122
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:32:52.912
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> Deleting file
>>>>
>>\\SMSTEST\admin$\profiles\SMSCCMBootAcct&\ntuser.dat.LOG,
>>>> failed but ignored, Win32 Error = 0
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:32:54.943
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> Deleting \\SMSTEST\admin$\profiles\SMSCCMBootAcct&,
>>failed
>>>> but ignored, Win32 Error = 145
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:32:54.959
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> --->  Success Deleting user profile
>>>> \\SMSTEST\admin$\profiles\SMSCCMBootAcct&
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:32:54.959
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> ---> Service "CCMBoot" on machine "SMSTEST"
> successfully
>>>> deleted.  $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22
>>>> 17:32:55.068 2004 Central Daylight Time><thread=1460
>>>> (0x5B4)>
>>>> ---> Completed (Not verifying as it's a forced CCR)
>>>> request "CGBBYHXR", machine name "SMSTEST".
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:32:55.084
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> Deleted request "CGBBYHXR", machine name "SMSTEST"
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:32:55.084
>>2004
>>>> Central Daylight Time><thread=1460 (0x5B4)>
>>>> <======End request: "CGBBYHXR", machine
> name: "SMSTEST".
>>>> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Jul 22 17:32:55.084
>>2004
>>>> Cent
>>>>
>>>> Any ideas?
>>>>
>>>> Thanks!
>>>> Jeff
>>>
>>>
>>>.
>>>
>>.
>>

Next message: Stan White [MS]: "Re: sender issues"

Previous message: Mark Scott [MSFT]: "Re: Advanced Client not Discovering MP"
In reply to: anonymous_at_discussions.microsoft.com: "Re: Legacy Clients not installing on NT 4.0 during push"
Messages sorted by: [ date ] [ thread ]

Relevant Pages

Re: VERY frustrating 2000 server RRAS/VPN problem
... Your client machine receives an address when connecting, ... therefore it is already in the same subnet, ... >> the server is mostlikely trying to use the domain admin account. ...
(microsoft.public.windows.server.networking)
RE: Cant install Windows Small Business 2003 Client
... Make sure that the Small Business Server ... that if the client computer is asking for the user and password is because is ... Try deleting one computer and create a new user account and recreate the ... computer object to see if that account can be use connectcomputer then. ...
(microsoft.public.windows.server.sbs)
Re: Using EFS with Network Shares and SFU 3.5
... It does not take EFS into account. ... could again use the sharing server audit logs to see if success ... Read extended attribute and Read data, since the NFS client may ... Windows and *nix clients. ...
(microsoft.public.windows.server.security)
RE: SBS client updates over WAN remote sites
... User Wizard for the remote users on the SBS 2003 server, ... client applications such as Internet Explorer 6.0, Microsoft Office Outlook ... You can apply the following software on the subnet 10.0.2.0 using Group ...
(microsoft.public.windows.server.sbs)
RE: configuring client users
... This newsgroup only focuses on SBS technical issues. ... | Thread-Topic: configuring client users ... |> computer to SBS server while we need use "set up computer wizard" to ... |> For user account issue, please understand that if you join the client ...
(microsoft.public.windows.server.sbs)