Today I upgraded my vCenter Server version 6.0 to 6.5 (UPGRADING FROM VMWARE VCENTER 6.0 TO 6.5 PROCEDURE AND VSPHERE HTML5 WEB CLIENT) and I would like to discuss below two errors I faced while update, Rest everything was smooth. After this vCenter Single sign-on and vCenter Server Credentials screen and I got 2 Errors and not able to proceed ahead.
Error 1
Error: A problem occurred during authentication to the legacy vCenter Server using the provided credentials.
Resolution: Verify that the legacy vCenter Server is up and running. Verify that you provided the correct vCenter Single Sing-on credentials.
As given in first resolution, When checked vCenter server service, I found it is stopped, I started it and Upgrade went Ahead, My typed credentials were correct.
Error 2
Error: User running the upgrade does not have 'Replace a process level token' privilege.
Resolution: Assign 'Replace a process level token' privilege to the user.
To resolve it open local Group Policy editor of the vCenter Server. Open Run and type gpedit.msc.
Collapse Computer configuration and go to Security Settings >> Local Policies >> User Rights Assignment, and in the right hand side find Replace a process level token right click on it, go to properties. Add user or group, Add the service account (Vcenter service will be running using this account as shown in first screenshot). Check the names and click OK to add it.
If everything is successful, you will see message Running pre-upgrade checks. this could take few minutes...
VUM Error 3
VSPHERE UPDATE MANAGER 6.5 UPGRADE AND VSPHERE WEB CLIENT PLUG-IN INTEGRATION
Useful Links
PART 1 : VCENTER SQL DATABASE AND ODBC DSN CREATION
PART 2 : VCENTER SERVER 6.0 INSTALLATION ON WINDOWS 2012 R2
PART 3.1 : VMWARE VSPHERE UPDATE MANAGER INSTALLATION ON WINDOWS 2012 R2
PART 3.2 : VMWARE VSPHERE UPDATE MANAGER PLUG-IN INSTALLATION ON VSPHERE CLIENT
ESXI 6.5 UPGRADE INSTALLATION AND UI HTML WEB CLIENT
