Matt Baumann

I would test this by setting up an image with out using the OSOT tool to see if there are still issues with the windows updates? I do not think that Horizon controls where the updates are loaded from.

I just ran into this KB discussing thin client issues. https://kb.omnissa.com/s/article/83096

Have you verified the compatibility of the thin clients with your thin client vendor? If the issue does not present itself with full Windows clients then it is likely a thin client firmware issue.

Please verify the version you are on and perhaps provide a screenshot.

@Holly Lehman I think I automatically follow content that I post to? If this is not the case let me know how to do this.

I am sorry, what Omnissa application is causing this issue?

Guy, I did some testing on this and it looks like it may be the mouse pointer being a little bigger than the information icon. Does this happen if you change the browser scale to make the icon lager to point at?

Collin, There may be information in the Horizon logging. c:\ProgramData\Omnissa\Horizon\logs or in the older vmware versions c:\programdata\vmware\DCT\logs look in the debug logs and search for the vCenter name. There might be info there. As a test try to toggle the vCenter account from the service account to [email protected] and then back to the service account. If all that does not help you may need to submit a SR to the Omnissa team.

The 2406 Mac client is available through the Omnissa customer connect page as described in this KB https://kb.omnissa.com/s/article/6000691

@Abe Here is the relevant line that I find. M S I ( c ) ( 0 0 : F C ) [ 0 3 : 1 5 : 3 7 : 3 0 9 ] : P r o d u c t : O m n i s s a H o r i z o n C l i e n t - - O m n i s s a H o r i z o n C l i e n t c a n o n l y b e i n s t a l l e d b y t h e s y s t e m a d m i n i s t r a t o r . A c t i o n e n d e d 3 : 1 5 : 3 7 : L a u n c h C o n d i t i o n s . R e t u r n v a l u e 3 . M S I ( c ) ( 0 0 : F C ) [ 0 3 : 1 5 : 3 7 : 3 0 9 ] : D o i n g a c t i o n : F a t a l E r r o r

Omnissa does not have access to any of the Aria code. From what I have found the VVF for VDI licensing is not allowed to use Aria either. Omnissa DEX https://www.omnissa.com/platform/digital-employee-experience/ and Omnissa DEEM https://docs.omnissa.com/bundle/Intelligence/page/IntelExperienceManagement.html are the replacements.

If the clients are not on your network you cannot control the induvial client settings. You can manage redirection at the agent level with GPO to not allow what you don't want.

If the behavior changed with image then it is something in the image causing the issue. Perhaps some security is blocking communication to the connection server. You might be able to see this in the agent debug logs "C:\ProgramData\Omnissa\Horizon\logs\debug-####-##-##-######" Search for the connection server name.

Rick, I do not believe that this tool is publicly available. You should check with your account team and perhaps you will need to engage PSO to access it.

@Guy Leech According to https://kb.omnissa.com/s/article/58543 this is a part of the installation intentionally. I believe that it is related to ensuring that off loading is managed correctly. My guess is for simple VDI access it is not necessary but our documentation says i is required.