Office 365 Apps cannot be activated or print if they are published from Windows Server 2019-2022 (80351) (omnissa.com)

I finally found this article after trying all kinds of different steps to make it work but alas it doesn't.  Has anyone found a way around this to make Office 365 work via RDSH on Windows server versions 2019 or 2022?  If I use 2016 it works flawlessly but with support running out of this server version very quickly and app owners wanting to move to the newer server OS versions, we need an answer to this.  Using the workaround is not an option for an RDSH farm with 100 users in it and 20 hosts, it's completely insane to try to do this.  Any help would be great.  

It's still in working with MSFT to get it addressed in product.

 

Try to disable vmware-view-unity-shell.exe may helpful. 

Cleared the value of the following registry key in RDSH.
HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM\Agent\AppSessionShellReplacement

* It is a workaround for activating Office 365 in published App. But it may have some known side effect on iOS client(launch desktop unexpectally during connecting the published App).

Welp, that worked.  I have emailed my SE to ask him the same thing and he is getting conflicting answers from Engineering.  Also sent him this, hopefully something gets put out about it or they update the article with this workaround at least.  Thanks for the help

Hello Omnissa team,

Any updates on this? If I remember correctly there used to be a KB on this that had more information, but I can't find it (could be wrong).