vROPS 6.2 for Horizon: Configuration

This weeks post is a continuation on the vROPS 6.2 for Horizon install I’ve done, focusing mainly on the post configuration tasks after the initial appliance deploy.


1. Once your appliance has been deployed, you will be able to navigate to https://serverip/admin

2. You are presented with a Getting Started page. If you are deploying multiple appliances in a HA configuration then you can expand on your installation. For me, I am doing a new installation of a single instance of vROPS as there is no requirement for HA.


3. Plow through the getting started menu.


4. Enter in some admin credentials for when you need to login later on.


5. If you have a certificate for the service, now is the time. Failing that, use the defaults.


6. Give your cluster node a name (I used FQDN) and enter in your NTP server address(s).


7. Finish at the initial setup finalization screen.


8. You are taken to the admin page where you can see a system status. You need to select to start vROPs.


9. You will receive a prompt which is warning about a cluster configuration with multiple nodes. Click Yes to accept and proceed.


10. This part can take a while, you will notice the node information change and the status as “Going Online” and then to “Online”.


11. At this stage, you can logout of the web interface and go back. Be careful not to go to http:///admin otherwise you’ll end up in the previous setups menu.

12. Login using the admin credentials setup in step 4 and you will be presented with the remaining core vROPS configuration menus.


13. Enter in your product key infromation here unless on evaluation.


14. If you want to enable customer experience, do so here. Then finish.


15. The next stage for me was to add in the rest of our licenses, so on the right hand side, navigate to Licensing and add in your allocations.


I’m going to end the post here as there is a fair bit to do still and it is easier for me to chunk it up as to not have one long mammoth post! The last remaining bits to cover will be installing the View adapter and also the Broker agent on the connection servers to actually collect statistics.

Leave a Reply

Your email address will not be published. Required fields are marked *