Re: SMS 2003 SP1 not showing legacy clients as clients

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Michael Zhuo (jzhuo_at_microsoft.com)
Date: 03/17/05 

Date: Wed, 16 Mar 2005 16:37:25 -0800

How long has it been since the legacy clients were installed? Did you run
"Update Collection Membership" and refresh the results?

Thanks,

Michael [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.

"Erpara" <Erpara@discussions.microsoft.com> wrote in message
news:F04FA4BD-34DF-4B3A-8B0B-AFDD5A057A8E@microsoft.com...
> In my SMS console, the only clients listed are Advanced clients. I know of
> several Legacy clients that I've verified the services are running on,
> however they are not showing up as clients in SMS. They are listed as
> assigned, however. Any advice on where to go from here?
>
> Thanks in advance.
>

Relevant Pages

  • Re: Hardening CAP Permissions
    ... Cathy is completely correct. ... Legacy clients need the CAPS open, because they have no form of Client ... > can't report DDRs, inventory, or status messages, which means the CAP is ...
    (microsoft.public.sms.setup)
  • Re: Side By Side Upgrade - secondaries with Legacy clients
    ... I could then worry about replacing clients. ... > with legacy clients in secondary sms 2.0 sites. ... > So, basically, install a new central sms 2003 site. ... > reinstalling a 2003 secondary site and dist point. ...
    (microsoft.public.sms.setup)
  • Re: NT Clients in an AD environment
    ... Legacy clients like NT4 work find in an Active Directory environment. ... it tends to be where the domain controllers get a set of ...
    (microsoft.public.windows.server.active_directory)
  • Re: Client Access Account
    ... If you are 100% positive that you don't have legacy clients than yes you ... can remove that account. ... It is just for legacy clients, and advanced clients in a workgroup IIRC. ... >> Kim Oppalfens ...
    (microsoft.public.sms.admin)
  • Re: DNS and Wins Question
    ... computers just communicate via the legacy clients via WINs ... we all know that the xp clients use DNS as their name ... > resolution in a win 2k3 enviornment and legacy clients will use WINs ...
    (microsoft.public.cert.exam.mcse)