Existing Horizon Edge Gateways will continue to use the FQDN configured when they were deployed. Note that when a proxy configuration is changed, the Horizon Edge Gateway is redeployed.Īdministrators no longer need to enter an FQDN or configure a DNS record for the FQDN when deploying new Horizon Edge Gateways. Existing Horizon Edge Gateways can be edited to add a proxy. With privacy mode enabled, users must authenticate to log into Horizon Client and are redirected to the identity provider (IDP) logout page upon disconnecting from the Horizon Portal or exiting the client.Įdge Gateways for Horizon Edges in Microsoft Azure can now have a proxy configured for outbound traffic. The Pool and Pool Group detail pages now display real-time session data.Īdministrators can now configure privacy mode for end users in a VMware Horizon Cloud Service - next-gen environment. Horizon Cloud Service for Windows 365 (Preview) is now available to Horizon Cloud Service next-gen customers. To configure and use the integration, see Horizon Cloud Service next-gen for Windows 365 (Preview). This allows the deployment to succeed in regions where one or more of the SKUs is unavailable. India has been added as a new region to the Horizon Cloud Service Control Plane that you can select while onboarding to the service.Īdditional Microsoft Azure VM SKUs have been configured for fallback use when deploying the Horizon Edge Gateway on Azure Kubernetes Service.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |