System Center Configuration Manager is a systems management tool by Microsoft that layers on top of the functionality provided by Active Directory to supply a number of features:

  • Software Deployment – Push and Pull
  • Power Management
  • Imaging
  • Inventory – Hardware, Software, and Metering
  • Patching – Microsoft updates, Third-party vendors, and in-house
  • Mobile Device Management of Windows Phones
  • Integration with AD – authentication, authorization, and client targeting
  • Fully Functional API

SCCM and SQL Servers are maintained by OIT.
Feature implementation falls under the auspices of the AD Policy Committee.
SCCM Client licenses cover all university-owned machines.

The SCCM Service teams can be contacted using the following Google Groups:

  • Core Team –
  • Application Team –
  • Imaging Team –
  • Patching Team –

If you need to submit a ServiceNow ticket for issues with SCCM you can email the following:

  • Core Team –
  • Application Team –
  • Imaging Team –
  • Patching Team –

Specific Topics:

Training Materials:

Implementation decisions:

  • Distribution Points will use BITS instead of SMB for data transfer.
  • Support of off-campus clients is a requirement.
  • Management Points will be using NLB for redundancy.
  • Collections will be created following the same delegated OU structure as AD with the “Limit to Collection” setting.
  • SCCM Agent will be installed on all clients in AD. Exceptions will have to be approved by OIT S&C. The install of the agent will either be via a signed powershell script, task in WDS imaging, or via WSUS.