Archive : vCenter

Migrating from Windows vCenter to VCSA 6.7

Important Note: Before you start this work make sure you have a full backup of vCenter and backup of Database.

Logon to MyVMware and download VMware-VCSA-all-6.7.0-10244745.iso (latest version).

This image has an empty alt attribute; its file name is image-48.png

Once downloaded Mount iso (by right clicking on file and selecting mount)

Copy migration-assistant to C drive

Goto migration-assistant folder on C drive and double click on VMware-Migration-Assistant.

You should then get the screen above. Then minimise the screen DO NOT CLOSE THIS CONSOLE UNTIL THE MIGRATION IS COMPLETE.

Goto CD drive VMware VCSA – vcsa-ui-installer – win32 – double click on installer.exe

Click on Migrate

Select Deploy appliance and Next

Accept the terms of Licence aggreement and click Next

Enter your Window vCenter FQDN, Username and Password and click Next

Yes

Enter details for ESXi host where you want to install vcsa

Yes

Enter Name for vcsa, root password and confirm root password. Next

Choose deployment size

Selct Datastore for vcsa. Next

Enter network details. Step 4 you will need to provide a tempory IP address for vcsa at the end of the migration vcsa will have the original IP of your vCenter.

Check details are correct before clicking Finish

Progress bar will now show

Click Continue

Next


Next

Enter details to join vcsa to AD Domain. Next

Select Migration Data. Next

This one is up to you, I would recommend you join CEIP. Next


Make sure you have done what step 1 says before you tick this box. Finish

OK

Progress bar for Data transferfro vCenter to new vcsa

Click on Launch VSPher Client (HTML5) to access your new vcsa

vCenter (Windows) not showing any items in inventory.

I had this happen to me 4 times I think on the sam customers vCenter sometimes when we rebooted the Windows server for Microsoft patching the vCenter webpage would load with just headings no configuration or content. Which I must admit the first did make you panic a bit.

Searching the web and talking to other peers only answer people could recommend was to rebuilt vCenter an option, but, not the best solution.

So I logged a ticket with VMware the issue appeared to be with the vCenter Postgres DB having corruption. The engineer to took a backup of DB and VMware investigated this and came back to me and resolved the issue.

To resolve this issue I would recommend you have a backup of your vCenter DB this can be done by following this VMware KB2091961 and logging a ticket with VMware

https://kb.vmware.com/s/article/2091961

VUM Issues on Windows-based vCenter

I was getting an error where I wasn’t able to download patches one day. This was the fix that I found.

On Windows server where VUM is installed Stop VMware vSphere Update Manager Service.

In Windows Services, stop the vSphere Update Manager Service as below:

Open up Windows ODBC 64-bit, select ‘System DSN’ tab and highlight VMware vSphere Update Manager, click Configure.

Then click Next until you reach Finish:

Click Test Data Source

Came back successfully as below:

If OK, go to the next step but if not look at error and resolve the issue:

Launch the VMware vSphere Update Manager Utility (located Program files/ VMware/ Infrastructure/ Update Manager.) Login with vSphere Credentials.

Available options once you login:

First I would normally try to re-register to vCenter Server. Enter the relevant details and click Apply. Restart the VMware vSphere Update Manager Service.

Try patching the hosts again with VUM. If successful, well done, you are finished.

If you still have issues go to the next step.

Launch VMware vSphere Update Manager Utility (located Program files/ VMware/ Infrastructure/ Update Manager.) and login with vSphere Credentials.

Select Database Settings and click Re-intialize Database, and then click Apply. WARNING: This will reset the database back to default! Any HPE / Dell Custom Baselines and Images you had added to downloads will need to be recreated along with custom baselines.