Summary
The Setup will ask you to add the Publisher to the Trusted Publishers store before continuing, this will only place it in the store for the current user, for the certificate to be valid across all accounts of the local machine please follow the instructions in this article.
Symptoms
Spider setup detects PowerShell execution policy being detected to "AllSigned"
Cause
In case of the PowerShell execution policy being set to "AllSigned", it is necessary to add the publisher of the signing certificate to the trusted publishers store of the local machine.
The Setup will ask you to add the Publisher to the Trusted Publishers store before continuing, this will only place it in the store for the current user, for the certificate to be valid across all accounts of the local machine please follow the instructions below.
Resolution
Warning: It is important that the certificate is imported to the Trusted Publishers of the local machine, not only the user! If it is only imported into the user store it will not be available if the service is running under another account other than the user the Data Collector was installed with.
- Navigate to the file GetExecutionPolicy.ps1 file (placed in the same directory the installer was started from), right klick and choose Properties
- Choose Tab Digital Signatures
- Click Details
- Click View Certificate
- Click Install Certificate
- Choose Local Machine and click Next
- Choose Place all certificates in the following store and click Browse...
- Choose Trusted Publishers and click OK
- Click Next
- Click Finish
- Done
Additional Information
The command "Get-ExecutionPolicy -List" executed in a PowerShell window, will tell you which policies are activated.
Products
Spider Data Collector (SDC)
on - edited on by
jborchers
