From 4e0b7166a370691f6f185f1bc4d730c1501d30af Mon Sep 17 00:00:00 2001 From: Jonathan Haddock Date: Sat, 27 Oct 2018 11:21:22 +0100 Subject: [PATCH] Add troubleshooting suggestions to README --- README.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/README.md b/README.md index fd00b00..3ad72b3 100644 --- a/README.md +++ b/README.md @@ -30,5 +30,28 @@ Get-ExchangeProductName 15.0.1156.6 Update-ExchangeBuildNumberDefinition ~~~ +## Problems running the script +By default, PowerShell restricts script execution to help protect against script based attacks. It does this via the _execution policy_. To validate your system's current policy setting use the `Get-ExecutionPolicy` cmdlet: + + ~~~powershell +Get-ExecutionPolicy + ~~~ + +If you receive a result of _Restricted_ you'll need to either set a new policy (one of _AllSigned_, _RemoteSigned_ or _Unrestricted_ (*not recommended*)) or bypass the policy for this script. _AllSigned_ will run any signed script whereas _RemoteSigned_ only requires a script to be signed it if comes from a remote system (downloaded from the Internet or via a file share). _Unrestricted_ is not recommended as all scripts would be permitted to run, including those from malicious actors. + +__Note:__ This script is not signed. + +To change your execution policy (adjust the level to suit): + + ~~~powershell +Set-ExecutionPolicy RemoteSigned + ~~~ + +Alternatively, start a `PowerShell` session (from the run prompt) in execution policy bypass mode, then run script as above: + +~~~ +powershell –ExecutionPolicy Bypass +~~~ + --- This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.