My org has recently decided to move to Active Directory and SCCM. I have worked with AD in the past but have not used SCCM. I have been going over these forums and reading the documentation to plan for server resources needed for SCCM. We have 9 separate facilites with various connections. Right now they are all serviced by one PXE point and Zenworks Config so I think we could stick with one "site" managing the rest in SCCM as well. My design plan so far is a Primary Site Server with: SMS Provider Software Update Point Reporting Point Secondary Site Server with: Management Point Distribution Point PXE Point State Migration Point Will I need a secondary site at every facility or would that be recommended because of the traffic across the network? We plan on using VM's for these. What resources should we allocate for these servers? What else should I be considering while planning for this migration? SCOM, SCSM, SCDPM, Forefront?

Jay, Your primary site server sounds about correctly spec'd. Just make sure it's beefy enough to handle the clients. Take a look at the SCCM sizing document http://blogs.technet.com/b/deploymentguys/archive/2008/05/20/sccm-for-deployment-rough-sizing-guidelines.aspx You are correct on secondary sites that they should have those roles. Make sure they have plenty of storage for OS images, applications and such. VM's will be fine, just size them properly. 4 CPU's and 8GB RAM should be a good start. I would definitely recommend integrating Forefront into your SCCM infrastructure. It's already included in most enterprise agreements and is easy to use, reliable and secure. Good luck.

You have not mentioned the number of users. Here is file named SCCM Capacity Planner which can provide some basic suggestions for site design and hardware specifications SCCM 2007 Capacity Planner Tool V2.0 http://myitforum.com/cs2/files/folders/utilities/entry112970.aspx You can have a Distribution Point on a client system rather than Secondary site server if you have few clients at any of the location. Physical Server, running Windows Server 2008 R2 with Hyper-V. Quad Core, Raid 1 for OS disks and Raid 0+1 for SQL disks. If you can, use external Storage to store VMs and packages for Distribution Point, if not think on Raid 0+1 for VMs also. For Alerts and reporting it will be good to go for SCOM and i will definitely recommend you for Forefront.Zulqarnain Ali | MCTS, MCSA | 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.

Hi, You must have a Management Point on the Primary site server as this is the managemet point that the clients will be contacting as the Management Point on the secondaries will act as proxy management points. When hosting SCCM on virtualized servers don't forget that it is very disc intensive and requires a lot of disk IO to operate, I see this in a lot of scenarios that Memory and CPU is all that is beeing discussed when sizing SCCM and disk performance is forgotten. regards, Jörgen-- My System Center blog ccmexec.com --