Suggestions for new SCCM 2007 deployment
Posted on 2009-02-17
We are in the early stages of deploying SCCM 2007. There is a lot to take in when learning about SCCM, and I wanted to get some suggestions on setting up primary and/or secondary sites.
* Each campus has 45 users
* Each campus has a domain controller (Windows server 2003) and a personal file server. The primary campus hosts a Citrix server.
* Two satelliate campuses connect to the primary campus via T-1 link. The bandwidth involves email, two citrix applications, and normal AD replication.
* Each site has one person responsible for I.T. support, and will often remote control the desktops on campus (via remote tools), and occasionally deploy packages (software updates to existing software mainly).
We want to conserve WAN bandwidth, and help make remote access/package deployment speedy.
Should we create primary SCCM sites for each campus for these goals?
What about making the primary campus a primary (central) site, and making the two remote campuses secondary sites? Would these secondary sites be effective in isolating day to day SCCM tasks (package deployment/remote tools), or would they still communicate this over the WAN links?
Thank you for your assistance. If there are other factors I should consider, I would appreciate the help.