In my department we are wanting to deploy out SCCM 2007, I am a newbie but have read a lot of literature on SCCM trough the technet site. I am trying to deploy out a Single Site Server, My goal for this role otu would be Site Server, Seperate SQL Server, and a SMSProvider server during the SCCM Setup. I have 2 more servers with 2k8r2 waiting and I would like to break off some of the Site Roles responsibilities and place them on these idle servers. 1.) Do I need to install SCCM on each of the computers to be able to perform SMS Site Components, or can I just go through the new roles wizard and just point to the servers with windows 2k8 r2 installed only 2.) With a 10 gig back bone to 23 schools with no more than 6000 clients will a single site hierachy work, or will it be better to create secondary sites, or will I need primary sites? 3.) 3 what is the recommendation on breaking roles off on servers. We are generally using it for the new fore front server which will require software distribution. I feel silly that I cannot locate the answer myself, thank you for helping me out.

1) You only install the site server on a single server. The other installation (in the same site) will be using the site systems wizard in the console 2) You should be fine with a single site. If it turns out, not to work, then you can always establish a secondary site 3) Depends on the hardware. I know several installations where SQL and CM is installed on the same box (and with no problems).Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Heck it is even best practice to have SQL on the same box, http://technet.microsoft.com/en-ca/library/bb735870.aspx Best Practices for SQL Server o Use a dedicated SQL Server for each site o Do not use the Configuration Manager site database server to run other SQL Server applications o Configure SQL Server to use Windows authentication o Install Configuration Manager and SQL Server on the same computer Follow security best practices for SQL Server, noting the following issues: o The site server computer account must be a member of the Administrators group on the computer running SQL Server o If you install SQL Server using a domain user account, you must ensure that a Service Principal Name (SPN) is populated to Active Directory Domain Services Plus IMO and experience, using local SQL will save you 10+ days of headaches over remote SQL . http://www.enhansoft.com/

I really do appreciate this, I wasn't sure if I was doing things or not. I will follow up if I run into any more problems :)