deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-15 14:57:23 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Update update-compliance-configuration-script.md

Browse Source 
Cleaning up language a little.
This commit is contained in:
Jaime Ondrusek 2021-05-07 08:16:37 -07:00 committed by GitHub
parent 748e8e4611
commit c243698d0e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
windows/deployment/update/update-compliance-configuration-script.md
View File

@ -26,22 +26,22 @@ You can download the script from the [Microsoft Download Center](https://www.mic
## Script FAQ ## Script FAQ
1. I manage my devices with MDM. Should I use this script? - I manage my devices with MDM. Should I use this script?
* You should not use this script and instead configure the below policies through your MDM provider. No, you should not use this script. Instead configure the policies through your MDM provider.
2. Does this script configure devices for Delivery Optimization? - Does this script configure devices for Delivery Optimization?
* This script does not configure devices for Delivery Optimization. You must do that separately. No. You must do that separately.
## How this script is organized ## 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 execute `ConfigScript.ps1` with the parameters entered to `RunConfig.bat`. There are two ways of using the script: in **Pilot** mode or **Deployment** mode. 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`. This is intended for a pilot run of the script or for troubleshooting configuration. - 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 quietly execute. - In **Deployment** mode (`runMode=Deployment`), the script will run quietly.
## How to use this script ## How to use this script
Open `RunConfig.bat`, and configure the following (assuming a first-run, with `runMode=Pilot`: 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`. 1. Define `logPath` to where you want the logs to be saved. Ensure that `runMode=Pilot`.
2. Set `commercialIDValue` to your Commercial ID. 2. Set `commercialIDValue` to your Commercial ID.