Samohteb
Contributor
Contributor

If update manager is not installed (or is broken) on my Windows vcenter environment (version 6.5.0), will migrating to VCSA 7.0 fix the issue?

Jump to solution

I am attempting to migrate to VCSA 7.0 from a Windows vCenter running on 6.5.  I have not been able to get Update Manager working on this windows environment, although I do believe it had been working (in the distant past), but that was while vCenter was running on version 6.0.
I was of the belief that migrating to VCSA 7.0, would be the magic bullet that would not only get me on the appliance, but also get me on a new version of vCenter AND resolve my Update Manager issues.  Instead, the Migration Assistant is throwing an error during the prechecks and will not allow me to proceed.  The error is as follows.

Error: Migration Assistant is not running on Update Manager host machine <servername>.

Resolution: The Update Manager installed on <servername> will be upgraded as part of the vCenter Server upgrade process and will be migrated on the new vCenter Server Appliance. Run Migration Assistant on Update Manager host machine <servername>, and keep the migration assistant window open until the (vCenter Server) migration process completes.

Since I'm not able to proceed without resolving this, I logged onto <servername> and started the Migration Assistant, and started the Migration Assistant afresh on the vCenter server, but I got the same error.

Should I assume I must resolve my Update Manager issue before I'm allowed to migrate?

Is there some way around spending time on resolving an issue on a version that I'm leaving behind?

Thank you much, in advance, for any assistance you might offer to me.

0 Kudos
1 Solution

Accepted Solutions
sudeshnas
VMware Employee
VMware Employee

Hi Samohteb,

Yes you can definitely proceed with the vcenter migration from 6.7 to 7.0 and the newly deployed vcsa vm will have the embeddded VUM.

Additional deployement of the update manager is not required.

Moreover before procedding with the upgrade just validate the following to check if there are no stale entries of the vum.

In a web browser, navigate to http://vCenter_Server_name_or_IP/mob.

Where vCenter_Server_name_or_IP/mob is the name of your vCenter Server or its IP address.

Click Content.

Click ExtensionManager.

Check if there is any extension available with "com.vmware.vcIntegrity"

If present Select and copy the name of the plug-in.

Click UnregisterExtension. A new window appears.

Paste the key of the plug-in and click Invoke Method. This removes the plug-in and results in void.

Close the window.

Refresh the Managed Object Type:ManagedObjectReference:ExtensionManager window to verify that the plug-in is removed successfully.

Then proceed with the Migration.

Regards,

Sudeshna Sarkar

Install-Upgrade Specialist

_______________________________________________________________________________________________________

"Did you find this helpful? Let us know by completing this survey (takes 1 minute!)"

View solution in original post

0 Kudos
3 Replies
IRIX201110141
Virtuoso
Virtuoso

Yes, its normaly a easy fix and a common problem. You have to remove the extension within vCenter which cause the trouble. You need to use the MorefID Obeject Browser Smiley Happy

Check VMware Knowledge Base

Regards,
Joerg

0 Kudos
sudeshnas
VMware Employee
VMware Employee

Hi Samohteb,

Yes you can definitely proceed with the vcenter migration from 6.7 to 7.0 and the newly deployed vcsa vm will have the embeddded VUM.

Additional deployement of the update manager is not required.

Moreover before procedding with the upgrade just validate the following to check if there are no stale entries of the vum.

In a web browser, navigate to http://vCenter_Server_name_or_IP/mob.

Where vCenter_Server_name_or_IP/mob is the name of your vCenter Server or its IP address.

Click Content.

Click ExtensionManager.

Check if there is any extension available with "com.vmware.vcIntegrity"

If present Select and copy the name of the plug-in.

Click UnregisterExtension. A new window appears.

Paste the key of the plug-in and click Invoke Method. This removes the plug-in and results in void.

Close the window.

Refresh the Managed Object Type:ManagedObjectReference:ExtensionManager window to verify that the plug-in is removed successfully.

Then proceed with the Migration.

Regards,

Sudeshna Sarkar

Install-Upgrade Specialist

_______________________________________________________________________________________________________

"Did you find this helpful? Let us know by completing this survey (takes 1 minute!)"

View solution in original post

0 Kudos
Samohteb
Contributor
Contributor

sudeshnas,

Thank you much.  This worked perfectly.

Much obliged.

0 Kudos