Forum Discussion
Untrusted Certificate when installing Microsoft Edge
forgot to mention
win 10 enterprise was 1909, our SOE is 1809 and home version is 1909, in case it was only made part of a particular Win10 build
also verified not in intermediate CA
PaulKlerkx I ran a quick test in my lab environment, and it appears that the "Microsoft Code Signing PCA 2011" certificate is added to the Intermediate Certification Authorities on the system where the ConfigMgr console was used to create the Edge application. In my environment, this hasn't caused any issues, but application installation policies might be a bit more strict in yours.
What I'd try next is: export the certificate on the ConfigMgr console computer, and then import that into a GPO so it can be distributed to all ConfigMgr client computers. You could probably do the same using ConfigMgr Certificate Profiles. Good luck!
That didn't work, I tried in both intermediate certification authority and trusted publishers, Edge still won't install, the message is
Install-Edge.ps1 is published by CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US and is not trusted on your system. Only run scripts from trusted publishers.
Our Execution policy is set to allsigned.
PaulKlerkx Sorry, I'm out of ideas. I have been unable to reproduce this in my test environment, with or without the code signing certificate installed on the client, and with any one of the PowerShell execution policies configured in the client settings.
Please note that the PowerShell execution policy specified in the ConfigMgr client settings applies to PowerShell scripts run by ConfigMgr only. If you're running the installation command line manually, a different execution policy might apply to your user session. You might want to try again with the policy set to Bypass (in your user session) explicitly.
Michiel Overweel Awesome, thanks, Michiel,, found the cert on the MECM server, will respond here once I have tested.
