Trouble Installing System Manager on Windows Server 2022 Datacenter

[jweal8r]

I am having trouble installing System Manager on Windows Server 2022 Datacenter

I just spun up a brand new Windows 2022 Datacenter VM.  I joined it to my domain but have not moved it to an OU yet where any GPO's are applied.  Activated the license.  Rebooted.   Tried to install the SM Agent 3.7.2 and 4.1.1... both installations end with an error.

Meraki Systems Manager Agent Setup Wizard ended prematurely.

If you look at windows Event Viewer it shows Error 1603.

Any other MSI file will install with no issue.

So far, support has no answer and is referring me to Microsoft, which we know is pointless.

I am doing this all logged in as a Domain Admin

[alemabrahao]

Have you tried with versions prior to 3.7 or even 3.8.2?

[jweal8r]

I have only tried the 2 versions mentioned at this point

[alemabrahao]

I suggest you try other versions, otherwise I suggest you open a support case.

[jweal8r]

I do have a support case, they suggested version 4.1.1 which had the same issue

[alemabrahao]

Try the version 3.8.2

[jweal8r]

OK, ill ask support to send me a link for that. I cant find a download

[alemabrahao]

You don't need ask them. You can change it on Meraki dashboard.

 

[jweal8r]

got it, about to try it out

[jweal8r]

Same issue

[alemabrahao]

This appears to be a problem with your Windows server. Do you have another server you can test?

You can also try using a tool to clear cache and fix system registry.

[jweal8r]

This is happening on a brand new 2022 server, I then set up a brand new secondary server (as described in the original post )and the exact same thing happens

I have tried regedits, msiexec /unregister /register, I have tried  sfc /scan now, I have tried the dism tool, 

[alemabrahao]

Error 1603 can be caused by several common issues such as: - Windows Installer is trying to install an application that is already installed. - The installation folder of the application is encrypted. - There are insufficient permissions to access the location where the software is being installed.

I suggest you try to install without joining the server to the domain.

[PhilipDAth]

I think you'll need to open a support case on this one.  My guess is it a bug in the Systems Manager installer.

[jweal8r]

I have a support case, they have not been of any assistance yet, which is why I came to this forum

[jweal8r]

I just launched a third server, brand new, not joined to a domain or anything... will not install.

[jweal8r]

We have determined that the issue has something to do with the new installers.  For example, we can install version 1.0.98 on a 2019 server, and then after that we can install any other version like, 3.8.2.

Not sure exactly why yet but at least I have progress.

To be clear this seems to be specific to people using the Scale Computing hypervisor

[BHC_RESORTS]

FYI, Systems Manager dropped support for Windows Server platform (even 2022, 2025). Look at the changelog for 4.2.0. Last supported version for Windows Server platform is 4.1.1.