VMware Workspace ONE Access – Add additional Virtual Appliance

Release date: July 22th 2022

Welcome to my VMware Workspace ONE Access series. In this section I’ll describe how to add an additional Workspace One Access Virtual Appliance. VMware recommends using at least 3 nodes in a Workspace One Access Cluster, ref: Recommendations for Workspace ONE Access Cluster In this session I will show how to deploy node number two. Once I have both VA’s up and running I will create an Anti-Affinity rule in DRS to make sure these VM’s never reside on the same physical ESXi-host. This is basically a matter of cloning the primary Virtual Appliance (VA), as shown below, but it is important to make sure the necessary firewall port is open between the new VA and the SQL/DNS servers etc.

As show below, I’m running Build 19010796

Before I start the cloning, I log into the VA Management and check the status of my running VA

I also register host name and IP address in DNS

Shut down existing VA and Clone to Virtual Machine…

I provide a VM name and the folder location in vSphere, Next…

I select my Compute Cluster in vSphere, Next…

I configure the storage settings, Next…

I wont be adjusting any clone options, Next…

I adjust the vApp settings with correct host name and ip-info, Next…

Everything looks correct, Finish…

Before I proceed, I take a snapshot of the original VA before proceeding, in case there arises issues due to missing configuration etc. Next, I power on my primary VA and wait until the blue login screen appears. It is very IMPORTANT to ensure that the primary VA is powered on, before powering on the new VA.

I also log into the VA console in Workspace One Access and verify status.

As everything looks green and good above, I can now power up the secondary VA

After a few minutes I can connect with Putty and check the status of the Elasticsearch cluster

curl -XGET 'http://localhost:9200/_cluster/health?pretty=true'

Verify that the result matches the number of nodes.

This is also verifiable through the GUI, nice and Green on all nodes and services

Finally I connect to my HAProxy and adjust the haproxy.cfg file with my new VA settings as described here: HAProxy

Once done, I power down the primary VA and check that I can still connect. Seeing that this works nicely, I repeat this with the secondary VA, and when I have verified that everything works nicely, I remove the snapshots I created above and calls it a day.

VMware Official documentation:

Recommendations for Workspace ONE Access Cluster

Troubleshooting Elasticsearch Cluster Health (Digital Workspace Tech Zone)

Workspace ONE Access Product Page

VMware Workspace ONE Access Documentation

Disclaimer: Every tips/tricks/posting I have published here, is tried and tested in different it-solutions. It is not guaranteed to work everywhere, but is meant as a tip for other users out there. Remember, Google is your friend and don’t be afraid to steal with pride! Feel free to comment below as needed.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: