Re: Legacy Client won't install on NT4?

From: Phillip Windell (_at_.)
Date: 06/17/04 

Date: Thu, 17 Jun 2004 08:49:01 -0500

"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

Relevant Pages

  • Re: SMS2003 Windows NT4 client install error
    ... This is because NT4 machines do not support getting assigned via AD. ... The client gets installed and then de-installed because ccim ... >> client installation with a Domain admin count, ... All my Windows XP and Windows 2000 clients are ...
    (microsoft.public.sms.setup)
  • Re: 9i on NT4
    ... when I try to install 9i client to WNT4 ... Why do you feel the need to install it on that version of Windows? ... IIRC 9.2 was supported on NT4 ... ...
    (comp.databases.oracle.server)
  • Problem installing advanced client - ccmsetup service stays active.
    ... I am having a problem with 1 PCinstalling the advanced client. ... -Pushed client install from console but install ... SMS Advanced Client is not installed. ...
    (microsoft.public.sms.setup)
  • RE: Fax monitor incoming + outgoing calls?
    ... The detail steps to install share fax client as follows: ... Start server management console, locate Client Computers node, click ... To the folder redirection GPO issue: ... How to stop Folder Redirection in Windows Server 2003 and in Windows 2000 ...
    (microsoft.public.windows.server.sbs)
  • Re: FYI for eTrust AV 7.x Users
    ... installed the new remote install utility which works the same as v7 did - ... from the server. ... I think my issues had to do with my first client upgrade - our Windows 2003 ... I think this is why the updates did not go through (although you'd think ...
    (microsoft.public.windows.server.sbs)
Loading