Q: After I install System Center Configuration Manager 2012 RC, what are the key next steps?

A: After you install SCCM 2012 RC, you need to make it functional. This is assuming you followed the instructions in the previous FAQ “ Q: How do I install System Center Configuration Manager 2012 RC?” so your SCCM 2012 is integrated with Active Directory (AD). Perform these steps within the SCCM 2012 console unless otherwise stated.

  1. Select the Administration workspace (Wunderbar), open Hierarchy Configuration, and select Boundaries. Select the Create Boundary action from the Ribbon. Enter a name for the boundary, select the type (typically Active Directory), then enter the details such as AD site name or IP range, and click OK.
  2. Create a Boundary Group at Hierarchy Configuration, Boundary Groups that contains the boundary you defined. Under the References tab, allow the new site boundary group to be used for site assignment.
  3. Specify the network access account for each site. In the Site Configuration, Sites workspace, select the properties of a site, and select Configure Site Components, Software Distribution. (See screen shot below.) Select the Network Access Account tab, then specify the SCCM network access account clients will use to access software: It should not be the client computer account such as for workgroup computers or untrusted domain computers. By default it will use the computer account of the client.

  4. Select Discovery Methods within Hierarchy Configuration, and enable Active Directory System, User, Group, and Forest Discovery. For each you need to add the containers or groups you wish to discover from.
  5. Select Site Configuration, Sites, then right-click your site, and select Client Installation Settings, Client Push Installation. Under the Accounts tab, specify an account that has administrator privileges on the clients you wish to push the SCCM client to, then click OK. This account can be granted local administrator privileges on all clients using Group Policy to set Restricted Groups and include this SCCM client push account.
  6. Set default client agent settings via Client Settings, and modify default client settings and create custom user and device settings, if needed.
  7. Next you need to install Windows Server Update Services (WSUS) and Windows Deployment Services (WDS) roles, and configure Software Updates and OS deployment. Download and install the Microsoft Report Viewer 2008 Redistributable first. You need to enable WSUS and WDS separately through Server Manager, so enable WDS first. (See the screen shot below.) Then go back and add WSUS. This will install WSUS 3.0 SP2. You will be prompted for configuration during the installation, and you can accept the defaults unless you want to change the SQL Server database to use the same server as your SCCM database. When you’re prompted to configure WSUS, hit cancel and SCCM will do the configuration for you!

    This could also be done with a PowerShell command:

    Add-WindowsFeature WDS, WDS-Deployment, WDS-Transport 


    Add-WindowsFeature OOB-WSUS 

    After you add WDS and WSUS, navigate to Site Configuration, Servers and Site System Roles, select your server and select Add System Roles by right-clicking from the servers context menu. Add the software update point role (see the screen shot below), and as this is the first server, select the check box Use this server as the active software update point.

    You should enable synchronization on a schedule, such as once a week, and select the types of updates you wish to deploy and the products you wish to deploy, along with the languages you will support.

In future FAQs, I will cover other features in more detail, such as actually deploying an OS and deploying updates.

Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.