2.7 Trusting PowerShell Knowledge Scripts

When a PowerShell script is executed under an AllSigned policy, PowerShell verifies that the script contains a digital signature and that the signature is associated with a trusted publisher. NetIQ Corporation signs the AppManager for Windows PowerShell scripts. If you use the AllSigned policy, you must choose to trust NetIQ Corporation by importing the NetIQ Corporation digital certificate into the local certificate store on each Windows server in your environment.

You can import the digital certificate by running one of the AppManager for Windows PowerShell scripts from the command line.

To import the digital certificate:

  1. Open the Command Shell on the agent computer.

  2. Change to the AppManager\bin\PowerShell\Scripts directory.

  3. Type .\PowerShell_RunCommand.ps1.

  4. Press Enter.

  5. Type A at the prompt asking whether the script should be allowed to run.

  6. Press Enter.

These steps allow the NetIQ Corporation digital certificate to be imported into the certificate store for the user running the script. You need to run only one script to establish trust. It does not matter which script you run.

At this point, trust is established only between NetIQ Corporation and the user running the script. Trust is not established for any other user. If the AppManager agent runs under a different user account such as Local System, a domain account, or a local computer account, the agent will not have a trust relationship and will not be allowed to execute the AppManager for Windows PowerShell scripts.

To extend trust to all other user accounts, see Section 2.8, Extending Trust to All User Accounts.

To establish trust between all users accounts and the Microsoft digital certificate, see Section 2.9, Establishing Trust for the Microsoft Certificate.