About PowerShell execution policy
The PowerShell execution policy determines if PowerShell can run scripts. The installer sets the execution policy to Remote Signed which allows scripts to run. Problems are encountered if this step of the installer fails or the execution policy is changed after install. This appendix describes diagnosing and solving execution policy issues.
Log on to the website
Click the Primary servers tab.
Click the icon
If you receive the error message shown, there may be an execution policy issue. If Check Connectivity does not generate an error, the execution policy is set correctly.
To confirm there is an execution policy issue, navigate to the error log. Select %ProgramData%\Veritas\NetBackupSelfService and examine the errors. An example of an execution policy issue is shown.
"CreateRequest failed with error: File C:\Temp\NetBackupAdapter\NetBackupAdapterServices\PowerShellScripts\ ValidationHook\Initial.p s1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170. File C:\Temp \NetBackupAdapter\NetBackupAdapterServices\PowerShellScripts\ValidationHook\ Initial.p s1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170."
- Log on to the web server
- Open a PowerShell command prompt as administrator.
- Type: Get-ExecutionPolicy - List
The list of the current execution policies is shown
- If the Local Machine Scope is not set to Remote Signed, type the command:
Set-ExecutionPolicy -Scope LocalMachine -ExecutionPolicy RemoteSigned
Execution policy scope treats items higher up the list as higher priority, overriding those lower in the list. If the scope MachinePolicy is set to Restricted, then even though LocalMachine is set to RemoteSigned you are still unable to run scripts. This Stack Overflow post describes how to solve such problems.