Ivan de Mes

# Flex config file generated with Omnissa Dynamic Environment Manager Application Profiler version 10.14 [IncludeRegistryTrees] HKCU\Software\RocketSoftware [IncludeFolderTrees] <AppData>\Rocket Remote Desktop Description Contains all settings for Rocket Remote Desktop. Intended use Logon / Logoff Rocket Remote Desktop.zip

# Flex config file generated with Omnissa Dynamic Environment Manager Application Profiler version 10.14 [IncludeRegistryTrees] HKCU\Software\Siber Systems Description Contains all settings for GoodSync. Intended use Logon / Logoff GoodSync.zip

# Flex config file generated with Omnissa Dynamic Environment Manager Application Profiler version 10.14 [IncludeRegistryTrees] HKCU\SOFTWARE\Altova Description Contains all apps within Altova MissionKit, like XMLSpy, DatabaseSpy, etc. Intended use Logon / Logoff Altova MissionKit.zip

Hi Mike, The icon you configure for the shortcut in the DEM Management console should be accessible by the user for which you deliver the shortcut. The icon you configure for a shortcut in DEM is not stored centrally by DEM. So for example, when you have a shortcut in DEM that points to "C:\Path\File.ico", it expects "C:\Path\File.ico" to be locally available on the endpoint on which you deliver the shortcut.

So, if you have 10+ different companies connecting to your environment, that is something you don't have influence on. Centrally configuring/managing the solution by use of the policy that seems to work is the solution than right? Do you want to specifically target the policy to only certain pools/machines?

Thank you. So, if I understand correctly. When you set the "Printing job owner restrictions" policy to "Enabled", that fixes the issue? If so, why would you prefer a client setting? Especially while the endpoints are externally (managed). Just trying to understand what you want to achieve and why. 🤔

Just trying to understand correctly. Let me ask some questions first. 1) The follow-me printer from the local endpoint is being redirected into the Horizon session, right? 2) Does the username of the user within the Horizon has to match the username of the user on the local endpoint (the system that connects to the Horizon session)? 3) What do you mean by "if I change that to local user"? What do you change and where do you change that? 4) Can't you connect directly (without redirection) to the follow-me printer from within the Horizon session? If you can reply inline, it would probably give me a better understanding. Thanks.

Hi Fabio, My bad for the late response. I received the official icons for the Omnissa products/services by Omnissa themselves. There was no specific icon delivered for UAG. I guess you can use the Security Tunnel icon instead.

I've seen this message multiple times at one customer. "Disable Agent Session Cookie" solved the issue in that case. App Volumes Manager Configuration Settings Page

Can you provide a bit more context? What do you mean with increasing in disk size? In de OS disk itself, on storage level, both? Is the master image running? Does it install (Windows) updates automatically? Which Omnissa documentation did you use for optimizations? Etc., etc.

I couldn't find any documentation for this either. However, you might be able to lookup the information by using the developer tools in your browser. Open your developer tools in your browser and setup a new directory configuration. Monitor the URI(s) and payload(s) used. Perhaps you are able to lookup the things you need using this method (?).

An additional log file that may be useful when troubleshooting domain (join) issues, when "internal VM debug mode" is enabled is: %windir%\system32\NetSetup.LOG You may also try to join the domain using the default OU (CN=Computers) or join manually (via GUI) to rule out incorrect credentials or incorrect permissions on OU(s).

Are you able to use the following link and use your Customer Connect account or create/use a new one to download the necessary files? VMware Horizon 2406 - VMware Customer Connect

It's a long shot and maybe not related, but can you checkout/test the following? Maybe it's related... Solving Office 365 Activation problems with VMware UEM

I've seen this once. It was in a more complex AD configuration with multiple DC's in different sites. The reg key from the following article helped us out: Instant Clone provisioning fails intermittently with: Agent Initialization state error(26):Failed to verify domain trust(waited 45 seconds) (93066) I'm not sure if this may help you though, as I do not understand why the behavior in your environment is different between Windows 10 and Windows 11. Looking at the supported DC OS/Domain/Forest levels, I think there's no reason to suspect incompatibility with Windows Server 2025 for your DC's. Unless Omnissa says otherwise...