Advanced client installation issues

Hi,

We have an SMS 2003 with SP 1 setup running in our enterprise. We have
350 machines spread across 4 VLANs. In the site boundary, we've
specified the IP site container from AD that corresponds to this group
of subnets. In addition, by default, the subnet in which the SMS server
resides is also included as a site boundary.

We have not extended the AD schema, as this setup is for testing
purposes, albeit in our live environment. We have a WINS server in
place and we have run a script to make WINS the entry on Network
Connection Properties on all machines. On the WINS server, we have
added a record of the SMS server using the netsh command.

At the outset, we had a test setup (with a different site code) on most
machines. that was also an SMS 2003 SP1 setup. Some other client
installation issues (fewer than 30 clients reported back to the SMS
server) prompted the removal of that setup. However, before putting up
this new setup, we ran ccmclean.exe via a group policy and ensured the
older agents got removed.

What we see is that out of the 350, 325 clients are being discovered,
but the client shows installed on only a total of 145. We have
repeatedly installed the client using client push installation on the
non client machines, but to no avail. In the non-client machines, upon
opening the systems management icon on the control panel, all the
components show as installed, but none appear enabled or diabled.

Please advise on any steps we may have missed in the configuration, or
why this issue occurs. Also, one common error we find in the ccm.log is
'logon failed' on many machines. We are using enterprise admin
credentials. Also, one other thing we find is the 'install flag is
not turned on' message. Can you please clarify these 2 issues too?

Thanking you in advance,
Sindy

.

Relevant Pages

  • Re: SMS and File/Print Sharing
    ... The only time that SMS would need file and print sharing on the client ... machines is if you choose to install the SMS client agent using push ...
    (microsoft.public.sms.misc)
  • Re: SMS Advanced Clients
    ... Going back to the SMS admin tool, the workstation shows as being assgined ... >> than upgrade for all machines concerned. ... >> client software. ...
    (microsoft.public.sms.setup)
  • Re: Blocking Client install to specific machines
    ... After you have discovered the machines, ... After that you can you use the client push wizard and target ... > to keep SMS away from them. ... >> of systems on which you would like to install the client. ...
    (microsoft.public.sms.setup)
  • Re: Clients not showing in console
    ... Make sure you remove the SMS client completely ... For machines that have already been deployed, ... one showing desktops with SMS Adv Clients (300 ...
    (microsoft.public.sms.inventory)
  • Re: Collections question
    ... I can get a list of machines that have no client installed This ... > We have a sms Primary site and 12 secondary sites - Advanced clients only ... >> the SMS client installed or not. ...
    (microsoft.public.sms.admin)