Rico

This problem has fixed for me since MacOS 15.1! 🙂

Hi, I don't know where to configure in KeyCloak. I am using Entra ID, where the default is SHA256 for signing algorithm.

Since the update to MacOS Sequoia, our end users have been experiencing issues connecting to their desktop environment. The Horizon Client gets stuck on "Loading desktop." After a few minutes, a timeout occurs. Only after several attempts does it start working properly. This is not a network issue, as end users on Windows do not experience this problem. The issue affects multiple Horizon environments (Production and Test). Horizon Client version: 2406 (8.13.0 10025792799)

Oh wow let’s hope someone from Omnissa Employee can help us with providing some direct links to both! Fingers crossed.

You’re welcome, good to hear! Unfortunately I don’t have the links for both DEM and AppVolumes, I got the same dreaded Not Entitled message too. Raised a case previous week, still no answer. It’s quiet still now for three days.

When the issue appears I will take a look in to the HZ client log files too.. maybe there is some hint!

Thanks!!! Hmm.. but it’s not a black black screen if you understand what I mean. I can see the mouse cursor and spinning wheel of the Aero theme of Windows. When I quit the desktop window en re-launch the desktop, most of the time it is working. When I have the issue again, I will definitely take a look in to our firewalls.

Can you download it by the following link? I am able to download it only by this URL because of our subscription. https://customerconnect.omnissa.com/downloads/details?downloadGroup=HZN-2406-SUB&productId=716&rPId=118792

Have you completed all the steps like setting up a certificate authority if you don’t have it already and installed the enrollment servers (on separate servers) and linked the these to the connection servers? I believe the SAML authentication is working fine, it’s just a matter of adding an Enterprise Application in Entra or any other identity provider and setting some settings on the connection servers. But this does not cover TrueSSO. Both are completely independent of each other, but both are needed for the best Single Sign On experience. I have done this a few months ago without any issue. We are using UPN.

It is, but we do install the agents in the right order. Thereby this issue does not occurs on Windows devices.

I am not the only one:

Thanks! Have tried both directions without luck. I did create a service request at support today. To be continued.

Hi @Rob Beekmans, I will take a look in it. I think it is caused by the DisplayLink Manager driver, but I don’t know sure. In my case it’s not network related. This issue occurs randomly. For example after unlocking my MacBook.

Voted!

Hi, First of all ADFS is a SAML identity provider. Please check this page which is telling you how to export the SAML metadata of your UAG and import it in to your ADFS server. In this XML file the certificate is included. https://my-virt.alfadir.net/index.php/2022/02/16/adfs-with-vmware-unified-access-gateway-uag/ Do not override or delete your existing relaying party! Always check your claims (User-principal-name to NameID). When the new relaying party is working, you can disable the other one. After a few days without any issue you can consider to delete it. Please note that you don’t have to download the Metadata file of your ADFS server. No changes needed to your UAG configuration this time (at least until your adfs token signing certificate is replaced). If you need some more assistance, please let me know.