Re: strange behavior installing legacy clients
From: map000 (map000_at_discussions.microsoft.com)
Date: 11/25/04
- Next message: Chris Ong: "Re: Possible to deploy images"
- Previous message: Kim Oppalfens: "Re: strange behavior installing legacy clients"
- In reply to: Kim Oppalfens: "Re: strange behavior installing legacy clients"
- Next in thread: Kim Oppalfens: "Re: strange behavior installing legacy clients"
- Reply: Kim Oppalfens: "Re: strange behavior installing legacy clients"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 25 Nov 2004 02:01:05 -0800
yes, they appear assigned
but the clients are unninstalled after some time
"Kim Oppalfens" wrote:
>
> That should be fine, to be sure could you verify the assigned column in
> the all systems collection for the problem machines? Does the console
> show them as assigned yes?
>
>
> In article <ED6645D4-3027-4E2F-87A3-2256D6AC8F30@microsoft.com>, map000
> @discussions.microsoft.com says...
> > sorry
> > the workstations are like 172.16.x.1 and network boundaries is set
> > 172.16.0.0/255.255.0.0
> >
> > "Kim Oppalfens" wrote:
> >
> > >
> > > We don't have enough info to determine whether it's ok or not.
> > > What subnet mask are the clients on the remote networks using?
> > > If it is 255.255.0.0 than you should be fine. (Assuming your post
> > > contained a type since you first mention the remote networks as
> > > 172.16.X.1 and a line later you refer to them as 172.17.X.Y.
> > >
> > > My guess is that you have multiple networks in this 172.17.x.Y range, so
> > > you will have to add more boundaries. But without more info on these
> > > networks (Ip range & subnet mask) that is all we can do, guess.
> > >
> > > In article <D4F1468A-957A-4A2B-ACF3-B4502388F767@microsoft.com>, map000
> > > @discussions.microsoft.com says...
> > > > the NT workstation are assigned
> > > > the server it in a 192.168 network (class C) and the workstations are like
> > > > 172.16.x.1 on remote networks
> > > > in site boundaries I defined 172.17.0.0, 192.168.0.0 (172.17.x.y are on slow
> > > > links)
> > > > it's not ok?
> > > >
> > > >
> > > >
> > > > "Jeff Harbaugh [MSFT]" wrote:
> > > >
> > > > > It is because your site boundaries and not set correctly. You need to have
> > > > > IP Subnets defined for NT4 machines to get assigned. You are installing the
> > > > > client then one hour later when ccim wakes up it determines you are not
> > > > > assigned and so the legacy client is de-installed. Check the discovery
> > > > > properties of the NT4 machines and add the IP Subnet to your site
> > > > > boundaries.
> > > > >
> > > > > --
> > > > > Thanks,
> > > > > Jeff Harbaugh [MSFT]
> > > > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > > > >
> > > > > "map000" <map000@discussions.microsoft.com> wrote in message
> > > > > news:1579ADCA-E039-4B75-BFF4-C7480CE8AC49@microsoft.com...
> > > > > > sms 2003 server; NT clients need SMS legacy clients to be installed
> > > > > > when I push a client to a workstation, it installs it (I can see it in
> > > > > > control panel, SMS on the clients) but after some time (several minutes)
> > > > > > it
> > > > > > disapears from the client
> > > > > > can't understand why
>
> --
> Kim Oppalfens
> Proud father of Lennart Oppalfens
> Since 05/11/2004 08.53 GMT+1
>
- Next message: Chris Ong: "Re: Possible to deploy images"
- Previous message: Kim Oppalfens: "Re: strange behavior installing legacy clients"
- In reply to: Kim Oppalfens: "Re: strange behavior installing legacy clients"
- Next in thread: Kim Oppalfens: "Re: strange behavior installing legacy clients"
- Reply: Kim Oppalfens: "Re: strange behavior installing legacy clients"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
