HI ALL, newbie here so go easy one me! I ahve been tasked with designing and setting up a sccm 2007 r2 or r3 environment. I have two main sites (about 300 users) and about 8 WAN locations (100 users each) My main datacenter location has 300 users. do i need a central and a primary site here, or can i add 300 users to my central site? i know MS best practice advises against this, but my setup is pretty small. If i have to segment them, this is my plan. please let me know if you see any issues. Central Site (no users, location 1) 1 Server with SMS, RP, MP. WSUS and Active SUP 1 server with SQL backend Primary Site (300 users, Location 1) 1 Server with SMS, MP, PDP, SMP, WSUS and Active SUP, PXE, Primary Site (300 users, Location 2) 1 Server with SMS, MP, PDP, SMP, WSUS and Active SUP, PXE, This server will also run SQL Secondary Sites ( 100 users, this setup replicated for each of my WAN locations_ 1 Server running, PDP, PMP, PXE and SMP 1st primary site will be a child of central site. 2nd primary site will be a child of 1st primary and then the 8 WAN lcoations will be be split up as child objects of both primary sites (4 on each) As my central site and 1st primary site are in the same lcoation do i need WSUS and Active SUP on both (they will be in different SCCM boundaries). i would like all down stream clients to go to the primary sites rather than the central site. only management and reporting should take place fromt he central site. If i have the OSD roles installed on the primary sites (should it only be on one, 1st primary)can it still be setup and managed from the central site (or a client management console poiting to the central site)? I hope this has been clear. Thanks in advance.

Is there a reason you are doing multiple primary sites at all? Primary sites should only be used in extreme scale out situations (100,000+ clients), de-centralized delegation, or because spearate site policies are required for legal or other non-technical reasons. For what you've described above, I would only create a single primary site with secondary site for your remote locations. Depending on the number of secondary sites, WAN topology, client count, and server availability, I would even consider a third-party peer-to-peer technology instead of secondary sites.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I would just have one Central Site which is your primary site and then have the others as secondary sites. Depending on traffic and bandwidth you could also remove the secondary sites and have standard distribution points with the roles you require such as PXE Blair Muller

Hello - See, some recommendation from technet and experts in the business. http://technet.microsoft.com/en-us/library/bb680869.aspx http://blogs.technet.com/b/deploymentguys/archive/2008/05/20/sccm-for-deployment-rough-sizing-guidelines.aspxAnoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks for all the information guys - Blair - are you that i can have clients in my central site? - and then secondary site's with PDP, MP, PCE and SMP roles at all the remote sites? for arguments sake say i have 200 cleints at each of my remote wan sites. what type of traffic loads would i be seeing goign to my central site? im not concerned about images and updates being pushed to the DP ( i can schedule to do this at night) i am more concenred with bandwidth saturation from administrative overhead with having all services located at the central site. thanks

Normal policy traffic is trivial -- usually about 10kb per policy interval for a single client. HW and SW inv traffic varies but is also usually quite small -- less than 100K per client per inventory cycle and often far smaller because these are almost always deltas. For 200 total clients at a site, you will not impact a normal WAN link unless it is already saturated. I would still put a secondary site at thse remote locations however because that is the only way to throttle content distribution to those sites -- BDPs can do it also but very few people actually recommend BDPs. Alternatively, a third-party peer-to-peer solution works even better or if you are entirely Windows 7 you can use Branch Cache. As for putting clients at a "Central" site, of course you can. There is no such thing as a formal role called a central site in a CM07 hierarchy. The term is used to describe the top-most primary site in a hierarchy of primary sites. It is often used as a reporting only site, but this is by no means a technical requirment -- it is a full primary site with all the capabilites of a primary site. Do note that calling a site a central site when you only have a single primary site is not realy "correct" as it implies other child primary sites exist. If your hiearchy consists of a single primary site, you don't have a central site by the standard terminology.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I think Jason has covered everything?Regards, Blair Muller Check Out My Blog: http://blair-muller.blogspot.com/

Thank you very much for your help. It is very much appreciated.