cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

AWS connector fails to execute due to PowerShell execution policy

AWS connector fails to execute due to PowerShell execution policy

When connecting the FlexNet beacon to AWS, it will fail to execute if the PowerShell execution policy isn’t set to RemoteSigned. If the policy is set to something else, you will see the following error message in the importer log and on the System Tasks page after starting the AWS connector.

The following error occurred while loading the extended type data file:
Microsoft.PowerShell, C:\Program Files\WindowsPowerShell\Modules\AWSPowerShell\<version>\AWSPowerShell.TypeExtensions.ps1xml: The file was skipped because of the following validation exception: AuthorizationManager check failed.

This PowerShell execution policy is one of the prerequisites for establishing an AWS connection with the FlexNet inventory beacon. You can find more details on prerequisites in the help article, AWS Connections.

Changing the execution policy

  • You can check the PowerShell execution policy by using the following command:

 Get-ExectutionPolicy

If it returns something other than RemoteSigned, you must update the policy.

  • Change the PowerShell execution policy to RemoteSigned by running the following command as an administrator:

 Set-ExecutionPolicy RemoteSigned

Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Sep 01, 2022 03:38 PM
Updated by:
Contributors