RE: Client Site Assignment
From: Brian Tucker (BrianTucker_at_discussions.microsoft.com)
Date: 08/24/04
- Next message: Evan [MSFT]: "Re: Sitecomp.log Error message. Please Help!"
- Previous message: Marc Bouchard: "RE: Client Site Assignment"
- In reply to: Marc Bouchard: "RE: Client Site Assignment"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 24 Aug 2004 09:19:03 -0700
Does the Windows 2000 server with SMS connect and pull info from the unix
machines? Are your boundaries set properly?
"Marc Bouchard" wrote:
> Nothing really... That's what bothers me...
>
> Marc
>
> "Brian Tucker" wrote:
>
> > Marc,
> >
> > So, what is unique to the machines that are being discovered and assigned?
> > If some are being assigned and discovered, there must be something different.
> >
> > Brian
> >
> > "Marc Bouchard" wrote:
> >
> > > Hi everybody,
> > >
> > > I've been reading about my problem and I can't find a single solution for
> > > it. Here goes.
> > >
> > > Config:
> > > Windows NT4 Domain
> > > SMS 2003 running on a Windows 2000 Server
> > > WINS/DNS/DHCP are unix based
> > > Windows NT4/2000/XP workstations
> > >
> > > Problem:
> > > Network discovery doesnt work for all PCs - only a few machines from various
> > > subnets have been discovered.
> > > Clients are installed thru the login script, and they installed properly. On
> > > 2000/XP machines, the SITE isnt identified and autodiscovery wont work (as I
> > > can't register the MP in WINS).
> > >
> > > WHat I'm looking for:
> > > A way to either make the network discovery work (everything was fine with
> > > v2.0) and a way to assign the SITE to clients already installed (registry
> > > patch, tool, cmd line parameter, etc...)
> > >
> > > Thanks!
> > >
> > > Marc
- Next message: Evan [MSFT]: "Re: Sitecomp.log Error message. Please Help!"
- Previous message: Marc Bouchard: "RE: Client Site Assignment"
- In reply to: Marc Bouchard: "RE: Client Site Assignment"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|