This site requires JavaScript to be enabled
An updated version of this article is available

Approved Configuration Management Systems at NC State

89 views

6.0 - Last modified on 2026-07-02 Revised by Damon Armour

5.0 - Last modified on 2025-08-22 Revised by Renfrew Bidgood

4.0 - Last modified on 2025-08-22 Revised by Renfrew Bidgood

3.0 - Last modified on 2025-08-22 Revised by Renfrew Bidgood

2.0 - Last modified on 2025-08-22 Revised by Renfrew Bidgood

1.0 - Created on 2025-08-21 Authored by Renfrew Bidgood

The following Configuration Management Systems (CMSs) are approved by the Office of Information Technology Security and Compliance (OIT S&C) unit for use at NC State.

NOTE:  All CMSs must be reviewed and approved by S&C before being used to manage university-owned devices.

Table 1.  Approved CMSs at NC State
Operating System CMS Name CMS Owner
macOS, iOS, iPadOS, and tvOS Jamf Pro Shared Services (OIT SS)
Windows WolfTech AD/SCCM
InTune/SCCM
Shared Services (OIT SS)
Linux Campus Linux Services (CLS) The CLS Community
Linux OIT Linux Services (OLS) OIT Shared Services
Central Services Integration (CSI)
Android OS Intune Shared Services (OIT SS)
ChromeOS Google ChromeOS Management (See NOTE.) Shared Services (OIT SS)

NOTE:  ChromeOS devices will require a per-device licensing fee to be managed by Google.

Requests for CMS Approval

NC State units providing their own CMSs must adhere to RUL 08.00.18 - Endpoint Protection Standard (EPS) security controls.  OIT S&C performs the security reviews for non-OIT CMSs. The security review will assess implementation of the referenced security controls to protect the CMS from vulnerabilities and verify that the CMS provides basic services to help downstream systems comply with RUL 08.00.18 - Endpoint Protection Standard.

To Submit a Request for CMS Approval

Complete the IT Exceptions Request form with CMS Compliance selected as the Exception Type.

If you have questions about the IT Exceptions Request, send email to security@help.ncsu.edu.