Re: client install problem in remote sites

From: Kim Oppalfens (kim_at_computacenter.nospam)
Date: 10/24/04 

Date: Sun, 24 Oct 2004 21:36:06 +0200

Check whether you can connect to the admin* share on a client using the
client push installation account for that site.

You could also have a look in the ccm.log file on the site server.

Kim Oppalfens
In article <#isGECeuEHA.1400@TK2MSFTNGP11.phx.gbl>,
mikey@NOSPAMebgames.com says...
> 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
>
>
> 

-- 
Check out the SMS Technical FAQ:
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default
.mspx

Relevant Pages

  • Re: Re-install of SMS 2003
    ... Stan ... I will perform a client push when we get SMS ... Clients will not get overwritten until you push them again, ... >> function with the new site even if the site code is the same because the ...
    (microsoft.public.sms.admin)
  • Re: Secondary site clients
    ... The only problem i have now is that the clients are not being set to the ... code rather than the secondary site, again any help here is appreciated. ... The primary site client push form the site server works fine and there ... >> are no error messages or anything relating to the client install in the logs ...
    (microsoft.public.sms.setup)
  • Re: SMS2003SP1 installation on a Windows 2003 SBS
    ... Are you trying to install via ... If so do the machines show as assigned in the admin console? ... > Check to make sure file and print sharing is enabled on the clients. ...
    (microsoft.public.sms.setup)
  • Re: Client push installation
    ... It looks to me at first glance like you're discovering these systems from the primary site, but they're residing in the secondary site's boundary--you can get around this by enabling client push at the secondary site--which I'm guessing isn't enabled, but i've been wrong before :-) ... have excluded the machine or CCM could not match the target resource to a boundary associated with the site. ... You can override the boundary limitation by clearing the check box in the wizard that limits the push to clients assigned to the site. ...
    (microsoft.public.sms.setup)
  • Re: Client installation frustration.
    ... Your site server cannot resolve the computer names to ip addresses. ... MVP Windows Server System - SMS ... By design advanced clients only assign to primary sites. ... At this secondary site there are nearly ...
    (microsoft.public.sms.admin)