Update update-compliance-configuration-script.md

Responding to issues customers have with the script because they're not aware of the requirement to run the script in System context.
This commit is contained in:
Charles Inglis 2020-07-09 11:17:16 -05:00 committed by GitHub
parent 4557d29e7b
commit 83d9c2cc17
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -35,6 +35,10 @@ The script is organized into two folders **Pilot** and **Deployment**. Both fold
> [!IMPORTANT]
> If you encounter an issue with Update Compliance, the first step should be to run the script in Pilot mode on a device you are encountering issues with, and save these Logs for reference with Support.
> [!IMPORTANT]
> The script must be run in System context. This is accomplished via the PsExec tool included in the file. To learn more about PsExec, see the documentation here: [PsExec](https://docs.microsoft.com/sysinternals/downloads/psexec).
When using the script in the context of troubleshooting, use `Pilot`. Enter `RunConfig.bat`, and configure it as follows:
1. Configure `logPath` to a path where the script will have write access and a place you can easily access. This specifies the output of the log files generated when the script is in Verbose mode.