Re: Legacy Client won't install on NT4?
From: Evan [MSFT] (esc_at_online.microsoft.com)
Date: 06/17/04
- Next message: Scott: "Network discovery and NT domains"
- Previous message: Stan White [MS]: "Re: SQL Connection error"
- In reply to: Phillip Windell: "Re: Legacy Client won't install on NT4?"
- Next in thread: Kerwin Medina [MSFT]: "Re: Legacy Client won't install on NT4?"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 17 Jun 2004 09:54:19 -0700
Machines won't appear in collection until the collection is updated and
refreshed. The default update interval is 1 day, as you can see by looking
in a collection's properties, Membership Rules tab. You can also manually
update it by right clicking the collection (or the Collections node to do
all collections at once) \ All Tasks \ Update Collection Membership. Then
right click again and choose Refresh.
I'm sure you would find it helpful to spend time browsing the overview
section of the docs which explain the basics of how to use sms and what to
expect.
-- This posting is provided "AS IS" with no warranties, and confers no rights. "Phillip Windell" <@.> wrote in message news:uvUHaHHVEHA.1164@tk2msftngp13.phx.gbl... > "Evan [MSFT]" <esc@online.microsoft.com> wrote in message > news:OV1GGavUEHA.2408@tk2msftngp13.phx.gbl... > > Hi, Evan. Thanks for replying. It toke me longer to get back to this than I > expected,...things got busy around here the last couple days. > > > NT4 sp6 is definitely supported for legacy client and it installs fine for > > me. If legacy client won't install on nt4 sp6, check ccim.log on client > box > > to see why not (for instance, if it doesn't have at least IE5, it won't > > install since requires IE5 or higher as stated in the docs). > > The version on IE is older I'm pretty sure, so that is proabably what my > problem is. > > > 4.0" and there is no information if it is a server or a workstation. DDM > > doesn't create ccr for it since it needs to know whether server, > > workstation, dc in order to know whether it should have client pushed to > it > > (the Push dialog lets you choose whether to push to servers, wksta, or > DCs). > > So you can't use AD system discovery to create CCRs for nt4. Network > > discovery does include that info, so use it for nt4. > > Ok. I'll try to check into these things more when I get back to it, but if I > can at least manually install the Client, that would be acceptable to me, > and the IE thing may be the cause of that problem. The last part of the > problems is that even after the client is installed, I never see the > machines show up in any of the "querys" except for the "All Systems" Query. > But, on the good side of things, the Collections are starting to show things > although I don't know how consistantly because I haven't had time to "pick" > thorugh all of it. > > Perhaps part of my problem is just not knowing what to expect and where to > expect it. The last SMS I ever used was way back in BackOffice4.5 and even > then we didn't get too deep into it or ever really "depend" on it for > anything. > > -- > > Phillip Windell [MCP, MVP, CCNA] > www.wandtv.com > >
- Next message: Scott: "Network discovery and NT domains"
- Previous message: Stan White [MS]: "Re: SQL Connection error"
- In reply to: Phillip Windell: "Re: Legacy Client won't install on NT4?"
- Next in thread: Kerwin Medina [MSFT]: "Re: Legacy Client won't install on NT4?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
