Managing new SCCM client from trusted domain
Hello Every One, We are going to add one new domain to our existing environment located in different site (WAN Link). We want few 100 clients from this new domain to be managed by our primary site server (SCCM 2007). Once this test is successful (application deployment, patching and OSD) in the future we will have more than1000 clients. Is it advisable to have secondary site server on the new domain environment or manage this 100 client directly in the site server?How do I prevent the other clients from this new domain not to be discovered except the test clients (100 clients)SLP and fallback status point are already installed. Anything that I have to consider in advance? SCCM 2007 R2 Thanks
June 27th, 2012 11:36am

A secondary site server can easily handle a 100 users and will be far less diffiuclt to manage than a second primary server. This may help you finalize your decision. http://technet.microsoft.com/en-us/library/bb693570.aspx By using either AD or IP subnet boundaries you can control what site server the sccm clients use. http://technet.microsoft.com/en-us/library/bb633084.aspx If SLP and fallback points are already installed and working your set. However, I would consider extending the AD schema to support SCCM so you can eliminate the SLP. http://technet.microsoft.com/en-us/library/bb694066.aspx
Free Windows Admin Tool Kit Click here and download it now
June 27th, 2012 11:51am

A secondary site server can easily handle a 100 users and will be far less diffiuclt to manage than a second primary server. This may help you finalize your decision. http://technet.microsoft.com/en-us/library/bb693570.aspx By using either AD or IP subnet boundaries you can control what site server the sccm clients use. http://technet.microsoft.com/en-us/library/bb633084.aspx If SLP and fallback points are already installed and working your set. However, I would consider extending the AD schema to support SCCM so you can eliminate the SLP. http://technet.microsoft.com/en-us/library/bb694066.aspx I would recommend a secondary unless you needed an administration point (Primary) at the location containing the 100 odd clients.
June 27th, 2012 4:56pm

Thanks Chad/ Marshall. As I mentioned after these 100 clients tested and everything works as planned, We will add the rest over 1000 clients. We dont need administration point (Primary) on the new domain unless it is a final option. Is it good to go with secondary site?? Thanks
Free Windows Admin Tool Kit Click here and download it now
June 27th, 2012 5:26pm

Thanks Chad/ Marshall. As I mentioned after these 100 clients tested and everything works as planned, We will add the rest over 1000 clients. We dont need administration point (Primary) on the new domain unless it is a final option. Is it good to go with secondary site?? Thanks Yes the Secondary is just a Distribution Point and a Proxy Management Point which is used by the Clients for retrieving cached policy (advertisements), for reporting their Inventory reports and for returning Status\State messages which means the Secondary can scale to 1000's of Clients easily. http://technet.microsoft.com/en-us/library/bb680869.aspx http://technet.microsoft.com/en-us/library/gg682077.aspx - Site and Site System Role Scalability http://myitforum.com/cs2/blogs/cstauffer/archive/2008/09/08/sccm-2007-maximum-recommended-number-per-site.aspx
July 9th, 2012 9:27am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics