Wednesday , June 10 2020

vCenter Server Appliance Upgrade from 6.0 to 6.5

Lets see how to get the vCenter Server Appliance update from 6.0 to 6.5

image

Run the Installer.exe from the ISO if its a Windows Machine.

D:\vcsa-ui-installer\win32\installer.exe

image

Choose Upgrade –

image

Two Stage Process

Stage 1  – Deploy New vcenter Temp

image

Stage 1  – Enter Source and target info.

If its a same cluster . Mention the esxi info.

image

Enter Target Info –

image

Security Untrusted SSL Prompt – Say Yes.

Enter Temporary vcentername.

image

Choose vcenter Size

image

Enter Temporary IP info. Same VLAN preferred.

image

Choose Finish

image

image

Now you can choose Stage 2- or continue stage 2 using  https://temp-ip:5480

image

Temporary Appliance booted up and ready. _Just _ Good_To_know

image

Take Backups/snapshots of old appliances

image

image

Ignore DRS warnings.

 

image

Vcenter 6.5 is up and ready.

image

 

Known Issue – 1 –

Issue  –  Using same vcenter creds for source and target

Error –

Encountered an internal error. Traceback (most recent call last): File “/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py”, line 2018, in main vmidentityFB.boot() File “/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py”, line 349, in boot self.configureSTS(self.__stsRetryCount, self.__stsRetryInterval) File “/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py”, line 1479, in configureSTS self.startSTSService() File “/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py”, line 1141, in startSTSService returnCode = self.startService(self.__sts_service_name, self.__stsRetryCount * self.__stsRetryInterval) File “/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py”, line 88, in startService return service_start(svc_name, wait_time) File “/usr/lib/vmware/site-packages/cis/utils.py”, line 784, in service_start raise ServiceStartException(svc_name) ServiceStartException: { “resolution”: null, “detail”: [ { “args”: [ “vmware-stsd” ], “id”: “install.ciscommon.service.failstart”, “localized”: “An error occurred while starting service ‘vmware-stsd'”, “translatable”: “An error occurred while starting service ‘%(0)s'” } ], “componentKey”: null, “problemId”: null }

Solution –

If you use vcenter credentials for Source and Target in the same Cluster.

It will turn of the Source

It will try doing the job on the target using the specified Creds.

Means . Use Esxi Creds for Target creds if its a same cluster.

Known Issue – 2  –

Vcenter Appliance password will Expire.

https://vcenterIP:5480

image

 

Note :

Goodbye vSphere Client for Windows (C#) – Hello HTML5

C# client (Desktop Client/thick client/vSphere Client,vi Client for Windows) will not be available from vcenter 6.5 Onwards

image

[ :ShowExcp:M: 6] 2016-12-05 09:56:31.231 Error: An internal error occurred in the vSphere Client.
Details: Object reference not set to an instance of an object.

Contact VMware support if necessary.
System.NullReferenceException: Object reference not set to an instance of an object.
at VimSearchUI.Services.Impl.SearchSpecBuilderImpl.GetSimpleProperties(PropertyOwner owner, Type parentType)
at VimSearchUI.Services.Impl.SearchSpecBuilderImpl.BuildTypes()
at VimSearchUI.Services.SearchServiceAdaptor.CreateSearchSpec()
at VimSearchUI.Controllers.Impl.SearchController`1.CreateSearchSpec()
at VpxClient.Home.ChromeView.InitializeChromeView()
at VpxClient.Home.ChromeView.OnFirstVimContext()
at VpxClient.Home.ChromeView.set_VimContext(VimContext value)
at VpxClient.Form1.OnFirstVimContext()
at VpxClient.Form1.set_VimContext(VimContext value)
at VpxClient.UI.OnSuccessfulLogin()
at VpxClient.UI.OnLoginEvent(String message, Object[] args)

About Satheshwaran Manoharan

Satheshwaran Manoharan is an Microsoft Office Server and Services MVP , Publisher of Azure365pro.com. Specialized in Office365 / Microsoft Exchange / Virtualization , Sathesh is an Messaging Expert supporting/Designing/Deploying many medium size businesses to large enterprises when it comes to Corporate messaging and Virtualization Infrastructure

Check Also

Database availability group must have quorum error

Decommissioning set of old Exchange 2013 servers had to export few mailboxes and decommission them.But …

One comment

  1. Hi,
    I was trying to upgrade but got the same error.
    By using on another host i am facing problem because we are using VDS.
    On the same host we can deploy but on stage2 we are facing that error.
    Please help if you have any solutions.

Leave a Reply

Your email address will not be published.