It says no such file or directory when running the command even though wizardssl.hzn is there under secure. For the gateway-va  <FQDN> part do I want to put the name that I chose during setup for the FQDN I assume?

So the command would look like

./wizardssl.hzn --makesslcert horizon.xxxx.com since I changed the name of the gateway-va during the initial setup.

I still get the same error when trying to do Step 2a: Database Connection Setup.

The other one is still running but has different IPs of course and a different DNS suffix for each installation. I just have the working\original installation up just in case people are still using it. Once I get the new one up and running I will get the data off the old one and then shut it down. We are only using the data sharing feature at the moment.

The first one is tied to a local\internal domain for all the VMs and the second one was setup using our external domain for all the VMs. I just setup the VMs IP addresses (internal) in DNS in our external zone. Then we will use a public DNS name which will be the same FQDN as the gateway-va VM for external access.

So yes all the VMs have the same domain name for this installation.

All the VMs for the new install have a different FQDN than the other install and all have reverse lookups configured.

I think I may try to shut off the other one and see what happens or I may just delete it since its not being widely used at the moment.

I shut down the first Horizon instance and rebooted the new vApp. When I run the database setup this time I get a different message. It says:

Error creating admin user.

No route to host

I found another post on it but with no real solution.

Database Connection Setup - Error creating admin user. No Route to host

I removed and then redeployed the vApp with the old one still shut down and got the same error. Do you think if I removed the DNS records for the original installation that would do the trick?

I even tried shutting off the working Horizon and installing a new one with the same IP addresses and DNS names so it would match the working one. The only thing I changed is the FQDN to a different one during setup besides gateway-va.xxxx.com and still get the same error.