Hi.
Every test i have run requires a reinstall of DEM after an upgrade to Windows 11.
Anybody with the same problem?
Maybe a solution?

It's not a major issue and it only takes a few seconds, it just stops the upgrade from being completely automated.

Just to elaborate, DEM is still installed and seems 'OK' - it just doesn't do anything.

Uninstall and reinstall solves the issue, reinstalling/repair doesn't.

Hello, is the DEM service auto started when user logs in?  maybe service is down due to change in startup setting for after upgrade 
Another reason might be, AV/Defender blocking the service. 

I will do another testrun asap and collect more info 

Thank you.

The service was set to manual - starting it doesn't solve the issue though.
Will be looking through the logs - hadn't really done much to solve it.

Re-checked, starting the service doesn't fix it.
Theres a driver in the Immedio directory - if that is relevant it might be that the Win11 upgrade disables the driver.

Running the update with /migratedrivers ALL - might fix the issue.

Edited November 26, 2024Nov 26 by itaut

migratedrivers didn't work.

Uninstalling DEM, upgrade to Win11 and reinstall DEM seems to be the only working solution.

Good morning,

I can confirm this behavior after an InplaceUpgrade to Windows 11. I even opened a support ticket with VMware in April 2024. The only solution I was given was to reinstall. I partly understand this attitude, because Microsoft causes this error during the Windows 11 upgrade process.
In the registry, the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Winlogon\Notifications\Components\VMwareUEM is deleted after the OS-Upgrade.

The error with ID 8226 is then found in the Event Viewer and the DEM agent therefore stops the function.

Microsoft itself will not fix this, because a support ticket was also answered there with the statement that you have to reinstall the application 😞

Best regards

The risk with any driver-level applications on Windows has always been that they will be overwritten with newer versions during an in-place upgrade and/or updates -- especially if it's something that replicates or overrides a native function like profiles/etc.

Honestly, that and the many other potential issues that can be left over from a legacy operating system are why best practices have usually stated to build new, even in the physical world where that's usually less of an option than in a virtual environment like Horizon.

I realize that's not the ideal answer, but it's not unique to this suite of software either. You'll encounter less headaches if you build out a new image with any big change like this and then move users over to it once you've worked out the quirks.

Hi,

This behavior is expected and aligns with the official documentation.

Important: Omnissa strongly recommends following these guidelines before performing any in-place Windows upgrade:

1. Uninstall the DEM agent before starting the Windows upgrade.
2. Once the upgrade is complete, reinstall the DEM agent.

This ensures the smooth functioning of the DEM agent after the upgrade.