Re: Legacy Client won't install on NT4?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Kerwin Medina [MSFT] (kerwinm_at_online.microsoft.com)
Date: 06/18/04 

Date: Fri, 18 Jun 2004 13:41:12 -0700

If you are using capinst or smsman to do the client install, you should
check the wn_manual.log file to see the exact reason why the installation
failed. If you are using "push" to do the client install, you need to look
at the wn_remote.log file.

Cheers...

"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
>
>

Relevant Pages

  • Re: Legacy Client on Windows 98
    ... > attempted to run smsman from two of them with the same result. ... > Install type is DISC ... > Client has not been assigned to a site...~ ... > ~Reading client installation base registry settings from ...
    (microsoft.public.sms.admin)
  • 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)
  • RE: Real Player Working with SBS 2003
    ... > I understand that you encountered problem when using real player on the SBS ... > domain on one of the client computer. ... > Please note that we only need configure the SBS server if you have ISA ... > Install the ISA Firewall client from the Server. ...
    (microsoft.public.windows.server.sbs)