Release date: February 22th 2022
Welcome to my VMware App Volumes series. This session will cover the basics around setting up an additional App Volumes Manager. I will be adding a load balancer in front of the App Volumes Managers later on.
Prerequisites for completing these tasks are:
- Firewall Port opening between the new App Volumes Manager and the SQL server
- Firewall Port opening between the new App Volumes Manager and the vCenter server
- OpenSSL to convert certificates for Nginx
The steps I have to take to complete this session are the following:
- Prepare a domain joined Windows Server sized accordingly to VMware’s recommendations.
- Install App Volumes Manager
- Configure CA Certificate for Nginx, as described here: VMware App Volumes – Replace App Volumes Manager self-signed certificate with Domain CA signed certificate
- Configure Anti-Affinity rule in vCenter to ensure that the two App Volume Managers never reside on the same ESXi-server, thereby providing High Availability.
- Reconfigure VMware OSOT Task Sequence to point App Volumes Agent to new App Volumes Manager Load Balancer URL
My current App Volumes Manager is v. 2111 (22.214.171.124) so this is also the version I will install on my new manager.
Before I proceed, I make sure to have a current backup of the existing App Volumes Manager. I also shut down my current App Volumes Manager and take a snapshot before I proceed. As an extra precaution, I document my settings and the ODBC configuration.
A final preparation is to verify that the SQL port is open between the new App Volumes server and the SQL server
Once the preparations are done, I start out by downloading the installation media from VMware Customer Connect and unpack the ISO-file. I start by launching the setup.msi.
The App Volumes Installer Setup Wizard launches, Next…
I accept the License Agreement, Next…
From the App Volumes Component Selection I choose Install App Volumes Manager, Install…
The above selection now launches the App Volumes Manager Setup Wizard, Next…
As I already have a database, I select “Connect to an existing SQL Server Database”, Next…
I provide the necessary database server and authentication information, make sure to DESELECT “Overwrite existing database….”, Next…
The Network ports and security options I leave as default, Next…
I also leave the features and installation location as default, Next…
Everything looks correct, so I go ahead and hit Install…
When the installer finishes, I click Finish and reboot the server for good measure…
Once the new App Volumes server is rebooted, I check the status in App Volumes Manager and can see that my new App Volumes Manager is reporting in as “Unregistered“
Before I continue with registering the new App Volumes Manager, I will request a certificate and configure this for Nginx, as described here: VMware App Volumes – Replace App Volumes Manager self-signed certificate with Domain CA signed certificate. The only change I have to make is to add the FQDN of the Load Balanser as DNS to the Alternative Name on the certificate.
I can now proceed with registering the new App Volumes Server following VMware’s documentation about this here: Register App Volumes Manager Server, however, when doing this I get the following error: “Failed to connect Manager Service with guid……”
After some troubleshooting and Googling, I found the solution here: Strange issues with new App Volumes Manager registration I need to edit nginx.conf on primary App Volumes Manager and reboot
I can now restart registration, but make sure to use primary App Volumes Manager FQDN with port 80 as Registered Manager Address
The registration of my secondary App Volumes Manager is now successful
I can now continue with establishing a load balancer in front of my two App Volumes Manager server, which I have posted here:
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.