Client installation in secondary site
Hi there,Before anything else, this issue is related to the following post: http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/b47dde25-b14e-4f05-be65-422a426b14ef although it is another part of a more wide-ranging problem I may have.I have one central primary site and 15 or so secondary sites, all SCCM 2007 SP1 (apart from one secondary site which is RTM.)All secondary sites have been set up with boundaries, senders, etc and I can see them from the central site.I am trying to troubleshoot some client installation failures - basically clients are correctly assigned to secondary sites, and show up as being client = yes in collections, although reports show another story (see the other post.)My doubt about secondary sites is how discovery and client push will work.I have seen that Client Push should be enabled with the site code of the connected primary site (not the secondary site.) However, what about heartbeat discovery and AD System Discovery? At the moment each secondary site has an AD discovery method for their individual OU in the domain, however at the primary site discovery has been enabled for the entire domain (including the OU's which correspond to each secondary site.) Is there a possible dentrimental impact on this?Also, should I enable heartbeat discovery on each individual site?Finally, where should I troubleshoot client installation failures in secondary sites? In the ccm.log directly on 2ry site servers, or can I just be checking the ccm.log and the reports in the central site?All secondary site servers are DP's and PMP - I think it may be a good idea to install them as FSP also - any opinions?Thanks for the help!!!
October 14th, 2009 8:21am
Hi,In a client push scenario clients will be "pushed" from the site that orignally received the ddr. For that reason you should enable discovery at the secondary sites. Having a FSP a the central site should be enough. To troubleshoot client install check the reports as they should always contain the information you are looking for.Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
October 14th, 2009 9:19am
You should have a look at ccm.log of the secondary site (if this is the site that initiated the push installation). Logfiles are not replicated up. Status messages are replicated up and reports can be viewed on the central site. Enabling or configuring client agent settings at the secondary site is not necessary (because clients can only be assigned to primaries and that's where the agents settings come from). Discovery should only be enabled so that each resource will only be discovered once.
October 14th, 2009 9:38am
check out following:http://myitforum.com/cs2/blogs/jgilbert/archive/2007/02/22/sms-2003-client-push-installation-method-explained.aspxHTH.Jie-Feng Ren - MSFT
October 14th, 2009 12:39pm
One thing Jeff's blog doesn't mention is the scenario of having a central site server without boundaries. In this scenario things work differently. If all discovery is done at a central site where the central does not have any boundaries the ddr will be passed down to the site that has the boundaries in which the client resides. This is just another great reason to have a central without boundaries. ;-)John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
October 14th, 2009 5:01pm
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as Answered as the previous steps should be helpful for many similar scenarios. If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. In addition, wed love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks!Jie-Feng Ren - MSFT
November 12th, 2009 2:42pm
May 15th, 2011 1:53pm