Best Practice Analyser on Server 2022 failing to set execution policy

[PurpleTentacle]

On any/all servers running Microsoft Windows [Version 10.0.20348.1607] the BPA scans fail due to the execution policy being overridden by one on a more specific scope.

 

I've checked Group Policy, and Local Policy, neither set anything for Windows PowerShell in either the computer settings or the user settings. As further proof that it's not Group Policy, servers in the same OU (same user logged in) run the BPA without issue.

 

Has anyone else experienced this? Searches haven't turn up anything useful. (This was particularly useless.)

[free780]

Is the failure that the setting is not defined. In an ideal world Restricted should be set for all scopes but unsure what would break.

[PurpleTentacle]

Setting Restricted across the board would murder the ability to use Server Manager let alone the BPA.

 

 

Server 2022 (unless someone other than me changed the defaults) has the defaults like so:

Scope ExecutionPolicy

----- ---------------

MachinePolicy Undefined

UserPolicy Unrestricted

Process Undefined

CurrentUser Undefined

LocalMachine RemoteSigned

 

Server 2016 (unless someone other than me changed the defaults) has the defaults like so:

Scope ExecutionPolicy

----- ---------------

MachinePolicy Undefined

UserPolicy Undefined

Process Undefined

CurrentUser Undefined

LocalMachine Bypass