Category: horizon
Using Microsoft Entra ID Guest Accounts (B2B) for Omnissa Horizon SAML authentication provides a clean, elegant solution that eliminates the need to duplicate configurations on your Unified Access Gateways …
To add an extra layer of security on top of standard multi-factor authentication (MFA), you can secure Omnissa Horizon using Microsoft Entra ID 2FA. This allows you to enforce …
The Omnissa Edge Gateway upgrade is a maintenance task that should be performed whenever Omnissa releases a new version to ensure your infrastructure remains aligned with the latest updates. Before proceeding, …
When attempting to remove or upgrade an NVIDIA VIB on VMware ESXi, the operation may fail with a "Device or resource busy" error. This typically occurs during an upgrade …
Migrating from VMware Horizon to Omnissa is more than just a name change but it’s a structural and architectural shift in the VDI landscape. While a direct upgrade (in-place) …
Due to license type changes and new services, the Omnissa Edge Gateway must be installed for the Horizon infrastructure to function properly. Omnissa Edge Gateway is not only used …
When using Omnissa Horizon, the copy and paste operation between the local device and Published Applications may not work. By default, this feature is disabled for security reasons. A …
To enforce the login process, FIDO2 authentication adds an additional layer of security, enabling a robust MFA authentication process. Leveraging Azure authentication methods and Omnissa Horizon True SSO capabilities …
Following the upgrade sequence, the Unified Access Gateway (UAG) is the next component to be upgraded. Currently, there is no direct upgrade for the UAG but instead, the correct …
The Omnissa Connection Server is the most critical component to upgrade, as any issues could significantly impact VDI functionality. This upgrade requires careful planning and after upgrading the App …
