Re: Legacy Client won't install on NT4?

From: Evan [MSFT] (esc_at_online.microsoft.com)
Date: 06/15/04

  • Next message: Brandon Everhardt: "Virtual PC and SMS Lab" 
    Date: Tue, 15 Jun 2004 09:33:08 -0700

    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 machines must appear in collections before you can push using the push
    wizard. Check the logs of the discovery methods you used to see what they
    say.
    As for using the option to automatically push to newly discovered boxes, if
    you're using AD or network discovery:
    AD stores the Operating System and version for NT4 systems as "Windows NT
    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. 

    -- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"Phillip Windell" <@.> wrote in message
news:%23F7BYilUEHA.3988@tk2msftngp13.phx.gbl...
> I'll state first that this is a SMS2003 test lab. I would never install
> something this "intrusive" into a production system without being
> comfortable with it,  but the lab is still important,...without it being
> successfull, the production version will never happen.
>
> The SMS Server is a Server2003 box. I haven't noticed any thing looking
> wrong on it, it seems fine.
>
> When attempting a manual install of the Legacy Client with an NT4 machine
it
> claims that the OS (NT4.0 SP6a) is not compatible. Why is it doing that?
> The whole point of there being a Legacy Client is to be able to work with
> these older OS's. It did install on a Win98ME OS, however in both cases it
> could not "auto find" the SMS Server and I had to point it to the CAP_*
> folder using the UNC path.
>
> None of the client machines show up at the server in any Querys or
> Collections, its as if they don't exist. I have enabled all forms of
> Discovery and all forms of "pushing" and have even tried to force them the
> execute immediately.  The client never gets installed (ever) by pushing,
and
> nothing is ever discovered.  Yet all the normal Domain and Windows
> Networking stuff work perfectly fine and there is not any other problems
> with these machines interacting with each other.
>
> I am completely discouraged by this version of SMS (2003). I am not a
> "newbe" and spend most of my days helping others in other Groups, but
> this...this *thing* is just hoplessly over-complex and totally
undependable
> from what I have seen so far. It *shouldn't  be* this difficult just to
get
> it up and running at a basic level.  But none-the-less, in spite of my
> grumblings, I'd like to "defeat" this thing and get it working, and would
be
> greatfull for any help.
>
> Thanks guys.
>
> -- 
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
  • Next message: Brandon Everhardt: "Virtual PC and SMS Lab"

    Relevant Pages

    • Re: DNS replication when installing new DC in domain
      ... > and a Broadcom ethernet NIC is impossible, as there are no drivers for NT4 ... "promote offline to PDC" that is from this line of your original ... then upgrade to Win2k3 SP1 on that temp machine. ... prefer -- either right after install or later. ...
      (microsoft.public.windows.server.dns)
    • Should I install win2k?
      ... I was happily co-existing with NT4 Sp6a Workstation for about the last ... to install) Win2K from that. ... won't run under XP (they run fine under NT and Win2K). ... Win2K upgrade but that's a huge amount of work and I'm now dealing ...
      (microsoft.public.win2000.setup)
    • Re: Fax Server Information Cannot be Retrieved
      ... The error message is the same as others have posted. ... servers on SBS2003 with the fax client installed on NT4 and WinXP ... we avoided to install via the standard Control ...
      (microsoft.public.windowsxp.print_fax)
    • Re: Operating Systems (was:Re: Compu-Pro Disk1 & Disk1A Controllers...
      ... the install CD to remove all the undesired crud. ... 98Lite doesn't work on NT4, ... and reinstall, I've seen installs that werent right lime along as ...
      (comp.os.cpm)
    • Migrating from NT4 to 2000 AD
      ... I just did this migration last night and it went very ... I did leave one of the BDC's at NT4 because it is ... install of w2k on the old PDC? ... Is your NT4 server with the mission critcal ...
      (microsoft.public.win2000.active_directory)