IT Consultant Everyday Notes

Just some problems/solutions storage

SCCM: Edge Chromium installation failed with 1(1x)

With SCCM (MEMCM) 1910 we can create Edge deployment directly from SCCM console the same way as O365 (even though the old .MSI is still working).

Sounds like a nice idea. I created a deployment (here is a nice outline: https://stevenbart.com/en/2020/01/09/deployer-microsoft-edge-chromium-au-travers-de-configuration-manager/) and saw a new Application “Edge Deployment” under Applications node in SCCM.

I refreshed computer policies on a Client and manually started “Edge Deployment” Application installation from Software center. It miserably failed.

After digging fresh logs I found:

in AppEnforce.log

Unmatched exit code (1) is considered an execution failure

Long story short: Microsoft uses a PowerShell script for the .msi installation. Even though the script is signed, the default Powershell Execution POlicy (Restricted) does not allow that. So you need either relax the policy to “Remote Signed” at least or add –ExecutionPolicy Bypass clause to the installation command in your deployment type(s) like this:

image

After that update machine policy on your test client and start the installation again. At least that fixed the issue for me.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: