- #UPGRADE TO WINDOWS VCENTER 6.5 INSTALL#
- #UPGRADE TO WINDOWS VCENTER 6.5 UPGRADE#
- #UPGRADE TO WINDOWS VCENTER 6.5 PASSWORD#
Since our old VCSA is in the cluster we are migrating our VCSA in, we need to put DRS in manual, and use a host name rather than vC – I will point that out later. Once it completes it looks a little different.
#UPGRADE TO WINDOWS VCENTER 6.5 PASSWORD#
We will need to enter the password to our service account that is used by VUM. We need to double-click on the VMware-Migration-Assistant.exe as seen above.
![upgrade to windows vcenter 6.5 upgrade to windows vcenter 6.5](http://4.bp.blogspot.com/-Z8gM2kXeI-Q/Umjl0brHhOI/AAAAAAAADVI/_SDJ_qENxV0/s1600/vSphere+5.5-Custom+install.jpg)
We need to copy the migration-assistant folder – indicated by the red arrow above – to the local hard drive of the VUM server. So on your VUM server you need to access the vSphere 6.5 bits.
#UPGRADE TO WINDOWS VCENTER 6.5 UPGRADE#
And we need to do this before the upgrade / migration process. One we are ready to start, we need to prepare VUM.
#UPGRADE TO WINDOWS VCENTER 6.5 INSTALL#
![upgrade to windows vcenter 6.5 upgrade to windows vcenter 6.5](https://i1.wp.com/www.provirtualzone.com/wp-content/uploads/2020/06/Upgrade65-67-new-pahse2-04.png)
After that I update the article with anything I learned and then finally I publish. BTW, I do this article, and then with it as a plan I do the upgrade. It is the VMware Infrastructure Navigator (VIN) and I find it most useful. It is here now but there is still one more tool of mine that is not 6.5 capable but I am tired of waiting for it. vSphere 6.5 is a big deal for me, and it has a lot of new stuff in it that I am looking forward to so I have been waiting anxiously for Update 1 for Veeam that supports 6.5. Now that I work at Veeam, and while I have used Veeam products for many years, now I need to work my lab like a Veeam customer. Yes, this has taken me a while to get too.