How to migrate from VMware vCOps to vROps – Part 3

This posting is ~9 years years old. You should keep this in mind. IT is a short living business. This information might be outdated.

I wrote about what’s new in vROps 6 and about the deployment of the virtual appliance. I also described how to migrate the data from the old vCOps vApp. Part 3 covers the decommission of the old vApp.

Enter the IP or FQDN of your UI VM into the browser. Login as admin into the administration UI.


Patrick Terlisten/ Creative Commons CC0

Before the vApp can be removed, the vCOps needs to be unregistered from the vCenter. Click “Unregister”.


Patrick Terlisten/ Creative Commons CC0

A confirmation pop-up appears. Click “Yes”.


Patrick Terlisten/ Creative Commons CC0

The process can take some time, depending on your environment. In my case the unregistration took about 5 minutes.


Patrick Terlisten/ Creative Commons CC0

That’s it. After the successful unregistration, the vApp can be shutdown and removed from the vCenter. Say good bye and enjoy your new vROps 6.0!


Some users complained about the absence of the Health Widget in the vSphere Web Client, after the removal of the old vCOps. Michael White (@mwVme) posted the solution: vSphere Web Client Health State Widget has errors after vR Ops Migration? Thanks to Michael for sharing this!

5/5 - (2 votes)
Patrick Terlisten
Follow me

One thought on “How to migrate from VMware vCOps to vROps – Part 3

  1. Joacim

    You use the admin page at setup and then rarely again, totally forgot about it but found in the manual that it’s: https://IP/admin to unregister.

    Otherwise this guide was helpful. Unfortunately all my machines in vROps is named null, can’t see any machine names in the interface. Some mapping between unique IDs and machine names is not working, bummer.

Comments are closed.