Re: Advanced Client Install on Secondary Site

From: Jeff Harbaugh [MSFT] (jeffharb_at_online.microsoft.com)
Date: 01/14/05 

Date: Fri, 14 Jan 2005 13:23:44 -0800

When you use push installation it installs the client from the site which
you did the push from. You would have to enable push at the secondary site
to have the clients use the proxy MP for installation. 

-- 
Thanks,
Jeff Harbaugh [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"G. Moores" <GMoores@discussions.microsoft.com> wrote in message 
news:BA2F6CE2-B3A8-45AB-AF9E-E80F7A2D1D58@microsoft.com...
>I have an SMS 2003 primary and secondary site set up in a test network, and 
>I
> have been testing advanced client installation. I have been having 
> problems
> installing the advanced client on workstations that are in the secondary 
> site.
>
> Using:
> Advanced Security
> Advanced Client
> SMS sites defined by AD sites
> Advanced Client Network Access Account - Yes
> Proxy Management Point on Secondary - Yes
> Using AD System Discovery - Working
> Client Push Installation - Configured and not enabled.
>
>
> Pushed to client using Client Push Installation Wizard. Client did not
> install.
> No system32\ccmsetup folder created on client and nothing in CCM.log on
> server.
>
>
> Made following changes when using the Client Push Installation Wizard
> Installation Options:
> Unselected "Site Default" and selected "Advanced Client"
> Client Installation:
> Unselected "Include only clients assigned to this site"
>
> Workstation in the secondary site installed the client and is assigned to
> primary (as it should be). However, looking at the CCMsetup.log on the
> workstation, it downloaded and installed the client.msi file from the
> SMSClient share on the primary (assume this is part of the MP on the
> primary), and not the Proxy MP on the secondary site server.
>
> Am I correct in thinking that the client installation point in the 
> secondary
> site should be the Proxy MP. This would seem to make sense to avoid
> unnecessary traffic across a WAN which will connect our primary to our
> secondary sites.
>
> To confirm the proper functioning of the PMP I looked at:
>
> LocationServices.log (on secondary site workstations) It shows primary 
> site
> server as the default MP and the secondary site server as the proxy and 
> local
> management point.
>
> PolicyAgent.log (on secondary site workstations) . Download source for
> policy downloads is the secondary site server/SMS_MP, and policies are
> downloading successfully and working.
>
> Any suggestions on why the install didn't work at first, and when I got it
> to work, it appears the clients are installing from the primary instead of
> the secondary site server.
>
> Thanks
> -- 
> G. Moores

Relevant Pages

  • Re: Issue with Advanced Client installation
    ... The problem now is the Collation displays No on both Client and Assigned after I installed Advanced client on both windows 2000 and XP. ... How do you configure Client Push Installation? ...
    (microsoft.public.sms.setup)
  • Re: Client push question - the plot thickens
    ... for clients within the site boundaries of a secondary site are disseminated ... If Client Push is enabled at that site then the ... SMS 2003 and Advanced Client push installation behavior. ... secondary site unless the secondary site has both initiated discovery of the ...
    (microsoft.public.sms.admin)
  • Re: Office Installation Not Syncing to AIP
    ... We want to replace all files since we are reaching to a brand new AIP. ... To answer your question about whether or not you can tell how the client ... patches got installed. ... If the installation is in a "mixed state" the symptom that you usually see ...
    (microsoft.public.officeupdate)
  • Re: Advanced client install!
    ... That log snippet would indicate where the ccmclean was running. ... > that it utility installs the SMS client on the DC too. ... >> account you have supplied in the push installation accounts tab. ...
    (microsoft.public.sms.admin)
  • Re: Advanced Client install nightmare
    ... I have previously successfully installed a client over the network, ... I can succesfully connect to the remote registry using the account. ... MVP Windows Server System - SMS ... account specified in the Client push installation properties. ...
    (microsoft.public.sms.admin)
Loading