From 83d9c2cc178f3fe7031e74bcc83e009f19e57109 Mon Sep 17 00:00:00 2001
From: Charles Inglis <32555877+cinglis-msft@users.noreply.github.com>
Date: Thu, 9 Jul 2020 11:17:16 -0500
Subject: [PATCH] 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.
---
 .../update/update-compliance-configuration-script.md          | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/windows/deployment/update/update-compliance-configuration-script.md b/windows/deployment/update/update-compliance-configuration-script.md
index 2167039e0c..9b0b568dd7 100644
--- a/windows/deployment/update/update-compliance-configuration-script.md
+++ b/windows/deployment/update/update-compliance-configuration-script.md
@@ -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.