client install problem in remote sites

From: Mike Koch (mikey_at_NOSPAMebgames.com)
Date: 10/24/04


Date: Sun, 24 Oct 2004 11:45:49 -0400

Hi,

All servers are running SMS 2003 w/ SP1.
Primary site is a member server in PA running on Windows 2003.
Secondary site #1 is in Australia, running on Windows 2003 member server.
Secondary site #2 is in Sweden, running on Windows 2003 domain controller.
Secondary site #3 is in Canada, running on Windows 2000 member server.
Secondary site #4 is in Las Vegas, running on Windows 2000 domain
controller.
Secondary site #5 is in Louisville, running on Windows 2000 member server.

All secondary sites are showing up in the primary site's console properly,
and appear to be functioning normally. All site boundaries are configured
appropriately for their respective subnets, discovery has run, and the
clients in each site show in the console as assigned. Client push in all
sites has been confgured to push automatically. All clients are running
either Win2K or WinXP Professional.

Problem: The clients in sites 3, 4, and 5 are not installing. It's been 2
full days since those sites were installed and configured, but no clients
have been installed. I guess I'm asking because sites 1 and 2 worked so well
with no extra work, so I'm not sure where to check or what to look for. The
only obvious difference is that the non-working clients are in sites where
the site server is running on Windows 2000 Server, while the others are
running under Windows 2003.

I'm more than willing to do the work. All I'm asking for is a bit of
troubleshooting guidance.

Thanks,
Mike



Relevant Pages

  • RE: NT4EMulator / NeutralizeNT4Emulator
    ... The reason I am adding 2 keys since I don't want the clients to ... Second server then the windows 2000 or XP client will login to that DC. ... since the member server does ... value on all the Windows 2000/2003 domain controllers. ...
    (microsoft.public.windows.server.migration)
  • RE: NT4EMulator / NeutralizeNT4Emulator
    ... The reason I am adding 2 keys since I don't want the clients to authenticate ... Second server then the windows 2000 or XP client will login to that DC. ... Windows 2003 domain controller, all the Windows 2000/XP clients cannot log ... since the member server does not ...
    (microsoft.public.windows.server.migration)
  • RE: NT4EMulator / NeutralizeNT4Emulator
    ... Windows 2000/XP clients use only Windows 2000-based domain ... Windows 2003 domain controller, all the Windows 2000/XP clients cannot log ... Seconldy the member server which will be upgraded to 2003 DC does it also ...
    (microsoft.public.windows.server.migration)
  • Re: SBS 2000 + windows 2000 server
    ... > How to configure licensing on an additional Windows server in an SBS ... >> when win2000pro clients connect there is no problem. ... >> no licenses are installed on the member server. ...
    (microsoft.public.windows.server.sbs)
  • RE: krb5kdc_err_s_principal_unknown on Windows Kerberos Domain
    ... Install the Microsoft Resource Kit on the member server and/or workstation ... command line with the parameter "tickets". ... krb5kdc_err_s_principal_unknown on Windows Kerberos Domain ... SPN for the domain with SetSPN, but I would like to a) get help determining ...
    (comp.protocols.kerberos)