Skip to content

Commit

Permalink
Add execution policy to prereqs documentation
Browse files Browse the repository at this point in the history
  • Loading branch information
FabienTschanz committed Oct 7, 2024
1 parent 9e9aad1 commit b4e6a22
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions docs/docs/user-guide/get-started/prerequisites.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,10 @@ For Microsoft365DSC to function, you need to arrange the following components:

Microsoft365DSC is supported for PowerShell version 5.1 and 7.3+. For additional details on how to leverage it with PowerShell 7, please refer to our [PowerShell 7+ Guide for Microsoft365DSC](https://microsoft365dsc.com/user-guide/get-started/powershell7-support/).

### PowerShell Execution Policy

Microsoft365DSC consists of its own module and various PowerShell submodules. Allowing scripts to run is necessary for the successful execution of the functions. The command `Get-ExecutionPolicy` retrieves the current execution policy. Usually, it is enough if the value is set to RemoteSigned. If you encounter issues while loading scripts, set it to Unrestricted: `Set-ExecutionPolicy -ExecutionPolicy Unrestricted`

### Windows Remote Management (WinRM)

Microsoft365DSC uses the Local Configuration Manager (LCM). This requires PowerShell Remoting to be enabled. Please run either `winrm quickconfig -force` or `Enable-PSRemoting -Force -SkipNetworkProfileCheck` to enable it.
Expand Down

0 comments on commit b4e6a22

Please sign in to comment.