This post is an update to Using Microsoft Security Baselines with System Center Configuration Manager. The Microsoft Security Compliance Manager is no longer supported or updated. Microsoft no longer releases baselines for Windows 10 using this tool.
This blog will go over a method of converting the Microsoft security baselines to configuration items in MEMCM.
I completed this blog using MEMCM 2002.
The computer for where you complete this must of the Active Directory PowerShell module and the MEMCM console installed.
To complete this post, you will need to download the security baseline from the Microsoft Security Compliance Toolkit, available here: https://www.microsoft.com/en-us/download/details.aspx?id=55319. Be sure to select the operating system or product you’re working on.
Once downloaded, extract the ZIP file. Make sure to shorten the name.
Next, we need the Convert-GPOtoCI PowerShell script by Sam Roberts, found here: https://github.com/SamMRoberts/Convert-GPOtoCI. Download the code-base by clicking the green Code button.
Extract the downloaded ZIP file.
Convert GPO to MEMCM Configuration Baselines
There are two processes to do to get this to work. First we need to import the Group Policy Object in Group Policy.
- Launch the Group Policy Management console.
- Right-click on Group Policy Objects and select New.
- Name the object for the product you’re configuring, like MSFT Baseline – Windows 2004.
- Right-click on the new object and select Import Settings.
- Click next until the Backup location screen. Click Browse and find the baseline folder you extracted.
- Select the GPOs folder, click OK, then click Next.
- Select the product to import and click Next.
- Click Next through the rest of the wizard.
Now that we have a GPO, we can export it into MEMCM.
- Launch PowerShell window (not ISE) and cd to the folder you downloaded/extracted from GitHub.
- Run this Powershell command, inputting the name of your GPO, domain, and MEMCM site code.
.\Convert-GPOtoCI.ps1 -gpotarget "<name of GPO>" -domaintarget "<domain name>" -sitecode "<site code>"
.\Convert-GPOtoCI.ps1 -gpotarget "MSFT Baseline - Windows 2004" -domaintarget "contoso.com" -sitecode "TST"
If you view the properties of the configuration item, you can see the settings and compliance rules have been created.
You can now add this configuration item to a baseline and deploy it.
All content provided on this blog is for information purposes only. Windows Management Experts, Inc makes no representation as to accuracy or completeness of any information on this site. Windows Management Experts, Inc will not be liable for any errors or omission in this information nor for the availability of this information. It is highly recommended that you consult one of our technical consultants, should you need any further assistance.