windows-itpro-docs/windows/deployment/update/update-compliance-v2-configuration-script.md

title, ms.reviewer, manager, description, ms.prod, author, ms.author, ms.localizationpriority, ms.collection, ms.topic, ms.date

title	ms.reviewer	manager	description	ms.prod	author	ms.author	ms.localizationpriority	ms.collection	ms.topic	ms.date
Update Compliance (preview) Configuration Script		dougeby	Downloading and using the Update Compliance (preview) Configuration Script	w10	mestew	mstewart	medium	M365-analytics	article	06/16/2022

Configuring devices through the Update Compliance (preview) Configuration Script

(Applies to: Windows 11 & Windows 10)

Important

• As of August 17, 2022, a new step needs to be taken to ensure access to the preview version of Update Compliance and the CommercialID is no longer required. For more information, see Configure Update Compliance settings through the Microsoft 365 admin center.
• This information relates to a preview feature that's available for early testing and use in a production environment. This feature is fully supported but it's still in active development and may receive substantial changes until it becomes generally available.

The Update Compliance Configuration Script is the recommended method of configuring devices to send data to Microsoft for use with Update Compliance. The script configures the registry keys backing policies, ensures required services are running, and more. This script is a recommended complement to configuring the required policies documented in Manually configured devices for Update Compliance, as it can provide feedback on whether there are any configuration issues outside of policies being configured.

About the script

The configuration script configures registry keys directly. Be aware that registry keys can potentially be overwritten by policy settings like Group Policy or MDM. Reconfiguring devices with the script doesn't reconfigure previously set policies, both in the case of Group Policy and MDM. If there are conflicts between your Group Policy or MDM configurations and the required configurations listed in Manually configuring devices for Update Compliance, device data might not appear in Update Compliance correctly.

You can download the script from the Microsoft Download Center. Keep reading to learn how to configure the script and interpret error codes that are output in logs for troubleshooting.

How this script is organized

This script's two primary files are ConfigScript.ps1 and RunConfig.bat. You configure RunConfig.bat according to the directions in the .bat itself, which will then run ConfigScript.ps1 with the parameters entered to RunConfig.bat. There are two ways of using the script: in Pilot mode or Deployment mode.

• In Pilot mode (runMode=Pilot), the script will enter a verbose mode with enhanced diagnostics, and save the results in the path defined with logpath in RunConfig.bat. Pilot mode is best for a pilot run of the script or for troubleshooting configuration.
• In Deployment mode (runMode=Deployment), the script will run quietly.

Important

PsExec is used to run the script in the system context. Once the device is configured, remove PsExec.exe from the device.

How to use this script

Open RunConfig.bat and configure the following (assuming a first-run, with runMode=Pilot):

1. Define logPath to where you want the logs to be saved. Ensure that runMode=Pilot.
2. Don't modify the Commercial ID values since they're used for the earlier version of Update Compliance. Leave setCommercialID=false and the commercialIDValue=Unknown.
3. Run the script.
4. Examine the logs for any issues. If there are no issues, then all devices with a similar configuration and network profile are ready for the script to be deployed with runMode=Deployment.
5. If there are issues, gather the logs and provide them to Microsoft Support.

Verify device configuration

[!INCLUDE Endpoints for Update Compliance]

Script errors

[!INCLUDE Update Compliance script error codes]

Next steps

Use Update Compliance