:::: MENU ::::

Blog

  • Mar 24 / 2023
  • 0
Azure, Horizon, Microsoft, VMware

VMware Horizon Cloud Next-Gen – Deployment

My previous blog explained the VMware Horizon Cloud Next-Gen – Prerequisites. In this blog, I will explain which steps you need to take to start the Horizon Cloud deployment.

Getting started

First, we will need to log in to the Horizon Universal Console. Once logged in you will see the Get Started page. Select Horizon Cloud Service.

Continue Reading
  • Mar 13 / 2023
  • 0
Azure, Horizon, Microsoft, VMware

VMware Horizon Cloud Next-Gen – Prerequisites

This blog post is part of a series of posts I will be creating regarding the Horizon Cloud Next-Gen deployment. In this post, I will explain the prerequisites for Horizon Cloud deployment. Coming posts in the series will have topics like image deployment, Pool creation, App Deployment, Dynamic Environment Manager integration, and maybe more.

Prerequisites

If you are new to Horizon Cloud on Azure and want to deploy a greenfield environment you will need to configure several items on Microsoft Azure before you can deploy Horizon Cloud. In this blog post, I will explain how to configure these prerequisites in Microsoft Azure but also some other prerequisites for the Horizon Cloud deployment.

Continue Reading
  • Nov 22 / 2022
  • 1
VMware, Workspace ONE

Unable to start all WS ONE Connector services

I recently created a test/development environment for Workspace ONE UEM, Access, and Horizon Cloud (Next-Gen). The goal was to develop Zero Day onboarding. For Zero Day onboarding, an AD group is needed; therefore, I tried to install a Workspace ONE Connector server on Azure resources.

Because the environment is for testing and development I didn’t need a server that was according to VMware’s sizing guidelines for connector servers. See hardware requirements.

I choose a Standard B2s (2 vCPUs, 4 GiB memory) from the Azure marketplace and started the installation. The same steps were used for the installation as shown in How to migrate Workspace ONE Connector.

Continue Reading
  • Oct 27 / 2022
  • 1
9.x, DaaS, EUC, Horizon, Uncategorized, VMware, Workspace ONE

How to migrate Workspace ONE Connector

Until Horizon DaaS 9.1.2 only Identity Manager connector 19.03.0.1 could be used to access the Virtual Apps Collections however Identity Manager connector 19.03.0.1 has been out of general support since 2022-08-31. As of September 27th Workspace ONE Access connector 22.09 has been released (release notes). This version supports Virtual Apps Collections on Horizon DaaS 9.1.4 (released October 2022). Horizon DaaS 9.1.4 and Workspace ONE Access connector 22.09 will create a supported environment again.

In this post, I will show you the steps on how to migrate from the (legacy) connector 19.03.0.1 to Workspace ONE Access connector 22.09.

Migration steps.

Continue Reading
  • Sep 09 / 2022
  • 0
MFA, vExpert, VMware, Workspace ONE

Workspace ONE Access: VMware Verify End-of-Life

Vmware Verify is a multi-factor authentication (MFA) service that allows verification using 3 methods, Push approval with OneTouch notification, Time-based One Time Password, and text messages. VMware Verify was easy to integrate with VMware Workspace ONE Access to create a multifactor authentication.

End of life

VMware Verify will reach end-of-support (EoS) and end-of-availability date (EoA) on October 31st, 2022. The mobile application will be removed from the App Store and Play Store on this date. Current users will also be unable to use the application for any second-factor authentication.

Continue Reading
  • Dec 13 / 2021
  • 0
9.x, DaaS, Uncategorized, VMware

Workaround instructions to address CVE-202144228 in Horizon DaaS 9.0.x and 9.1.x

VMware has released new a critical security advisory, VMSA-2021-0028. This advisory is for multiple VMware products that use the popular open-source log4j Java logging component, which was discovered to have a critical vulnerability in it (CVE-2021-44228)

This needs your immediate attention, not just at the VMware product level, but also for all other software in your environment. The log4j component is used by many vendors and software packages. For more information about the VMware products please visit https://www.vmware.com/security/advisories/VMSA-2021-0028.html

For Horizon DaaS 9.0.x and Horizon DaaS 9.1.x. a workaround is provided in the form of a hotfix. The hotfix should be applied to remediate the CVE-2021-44228.

Continue Reading
  • Sep 07 / 2021
  • 0
Logo
NSX-T, VMware

Load Balancing UAG’s with NSX-T

Unified Access Gateway for end-user computing products and services needs high availability for Workspace ONE and VMware Horizon on-prem deployments. Unified Access Gateway appliances work with standard third-party load balancing solutions that are configured for HTTPS and also has an out-of-the-box High Availability solution. The out-of-the-box HA solution will reduce complexity and lower your TCO but it comes with the following limitations.

  • IPv4 is supported for floating Virtual IP address. IPv6 is not supported. 
  • Only TCP high availability is supported. 
  • UDP high availability is not supported. 
  • With the VMware Horizon use case, only XML API traffic to Horizon Connection Server uses high availability. High availability is not used to distribute load for the protocol (display) traffic such as Blast, PCoIP, RDP. Therefore, the individual IP addresses of Unified Access Gateway nodes must also be accessible to VMware Horizon clients in addition to the Virtual IP address.

To overcome some of the limitations you can use NSX-T Data Center logical load balancer as a load balancing solution in front of the UAG’s.

In this blog post, I would like to show you how to configure a load balancer for UAG’s in NSX-T in front of a Horizon environment.

Continue Reading
Pages:1234