{"id":248,"date":"2020-09-05T17:36:55","date_gmt":"2020-09-05T21:36:55","guid":{"rendered":"http:\/\/blog.jamesblakeley.ca\/?p=248"},"modified":"2021-09-05T17:37:19","modified_gmt":"2021-09-05T21:37:19","slug":"vcenter-server-6-7-upgrade-this-vcenter-server-has-extensions-registered-that-cannot-be-upgraded-to-or-may-not-work-with-the-new-vcenter-server","status":"publish","type":"post","link":"http:\/\/blog.jamesblakeley.ca\/?p=248","title":{"rendered":"vCenter Server 6.7 Upgrade: This vCenter Server has extensions registered that cannot be upgraded to or may not work with the new vCenter Server."},"content":{"rendered":"<div id=\"post-body-4113088012464081697\" class=\"post-body entry-content\">\n<p>While running the vSphere 6.7 VMware Migration Assistant I received the following error:<\/p>\n<p>This vCenter Server has extensions registered that cannot be upgraded to or may not work with the new vCenter Server.<\/p>\n<p>In my case, the extensions were no longer being used. \u00a0So, I chose to just remove the offending extensions.<\/p>\n<p>1. \u00a0Create a snapshot or backup of your vCenter server.<br \/>\n2. \u00a0Log into the Managed Object Browser (MOB).<br \/>\n<a href=\"https:\/\/www.blogger.com\/goog_1156247956\"><br \/>\n<\/a><a href=\"https:\/\/myvcenterserver.mycompany.com\/mob\">https:\/\/vcenterfqdn\/mob<\/a><\/p>\n<p>3. Select\u00a0<u>Content.<\/u><\/p>\n<div class=\"separator\"><a href=\"https:\/\/3.bp.blogspot.com\/-0wR6-xLmJqc\/WNl_pYdU99I\/AAAAAAAAA9w\/mTQHD0Tk1ZUl4bugsDgpZWRKyz7mZH85wCLcB\/s1600\/extensioncontentv1.JPG\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/3.bp.blogspot.com\/-0wR6-xLmJqc\/WNl_pYdU99I\/AAAAAAAAA9w\/mTQHD0Tk1ZUl4bugsDgpZWRKyz7mZH85wCLcB\/s320\/extensioncontentv1.JPG\" width=\"320\" height=\"198\" border=\"0\" \/><\/a><\/div>\n<p>4. Select\u00a0<u>ExtensionManager.<\/u><\/p>\n<div class=\"separator\"><a href=\"https:\/\/3.bp.blogspot.com\/-PDW3fw7ZHi4\/WNl_zsaUEQI\/AAAAAAAAA98\/tlxUaCGsXawKXqXi3fjotQjXItmpqB5eACEw\/s1600\/extensionmanagerv1.JPG\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/3.bp.blogspot.com\/-PDW3fw7ZHi4\/WNl_zsaUEQI\/AAAAAAAAA98\/tlxUaCGsXawKXqXi3fjotQjXItmpqB5eACEw\/s320\/extensionmanagerv1.JPG\" width=\"320\" height=\"211\" border=\"0\" \/><\/a><\/div>\n<div class=\"separator\"><\/div>\n<p>5. Capture the\u00a0<u>VALUE<\/u>\u00a0of the Extension you wish to remove. \u00a0(ex.com.vmware.vcHms):<\/p>\n<div class=\"separator\"><a href=\"https:\/\/1.bp.blogspot.com\/-TXWQFoG-PJQ\/WNmAqBoCo_I\/AAAAAAAAA-A\/5VTd-oXlz-UbbizMovrByOZexIbRi8J4gCLcB\/s1600\/extensionvaluev2.JPG\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/1.bp.blogspot.com\/-TXWQFoG-PJQ\/WNmAqBoCo_I\/AAAAAAAAA-A\/5VTd-oXlz-UbbizMovrByOZexIbRi8J4gCLcB\/s320\/extensionvaluev2.JPG\" width=\"320\" height=\"169\" border=\"0\" \/><\/a><\/div>\n<p>6. Select UnregisterExtension<\/p>\n<div class=\"separator\"><a href=\"https:\/\/1.bp.blogspot.com\/-yoL9MGF6GIc\/WNmBRRZcJzI\/AAAAAAAAA-I\/3VY_QX_o1ukmxHchSpp9eGbSGg6I154UQCLcB\/s1600\/extensionunregisterv1.JPG\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/1.bp.blogspot.com\/-yoL9MGF6GIc\/WNmBRRZcJzI\/AAAAAAAAA-I\/3VY_QX_o1ukmxHchSpp9eGbSGg6I154UQCLcB\/s320\/extensionunregisterv1.JPG\" width=\"320\" height=\"179\" border=\"0\" \/><\/a><\/div>\n<div class=\"separator\"><\/div>\n<p>7. Enter the Value of the extension you wish to remove. \u00a0Then, select\u00a0<u>Invoke Method<\/u>. \u00a0Confirm that \u00a0you receive the Result of\u00a0<u>Void<\/u>.<\/p>\n<div class=\"separator\"><a href=\"https:\/\/3.bp.blogspot.com\/-eDKNnhkirFI\/WNmB92KR1rI\/AAAAAAAAA-Q\/mBs4hrDGRaACSZHg69bH-I33sBXUzA0lQCLcB\/s1600\/extensionunregister2v2.JPG\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/3.bp.blogspot.com\/-eDKNnhkirFI\/WNmB92KR1rI\/AAAAAAAAA-Q\/mBs4hrDGRaACSZHg69bH-I33sBXUzA0lQCLcB\/s320\/extensionunregister2v2.JPG\" width=\"320\" height=\"188\" border=\"0\" \/><\/a><\/div>\n<p>8. Confirm the extension is no longer in the extension list. \u00a0If so, delete the VM snapshot created earlier.<\/p>\n<p><u><i><b><br \/>\n<\/b><\/i><\/u><u><i><b>Common vCenter extensions:<\/b><\/i><\/u><\/p>\n<table cellspacing=\"0\" cellpadding=\"0\">\n<tbody>\n<tr>\n<td><strong>Extension Name<\/strong><\/td>\n<td><strong>Service Description<\/strong><\/td>\n<\/tr>\n<tr>\n<td>com.vmware.vim.eam<\/td>\n<td>vSphere ESX Agent Manager<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.vim.inventoryservice<\/td>\n<td>vCenter Inventory Service<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.vim.ls<\/td>\n<td>Licensing Services<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.vim.sms<\/td>\n<td>VMware vCenter Storage Monitoring Service<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.vim.sps<\/td>\n<td>VMware vSphere Profile-drive Storage Service<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.vim.stats.report<\/td>\n<td>Performance charts built-in extension<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.vim.stats.vsm<\/td>\n<td>Service Manager<\/td>\n<\/tr>\n<tr>\n<td>cim-ui<\/td>\n<td>vCenter Hardware Status<\/td>\n<\/tr>\n<tr>\n<td>health-ui<\/td>\n<td>vCenter Service Status<\/td>\n<\/tr>\n<tr>\n<td>hostdiag<\/td>\n<td>Internal extension to declare diagnostic events from VMware Host systems<\/td>\n<\/tr>\n<tr>\n<td>VirtualCenter<\/td>\n<td>VirtualCenter dynamic events and tasks<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.orchestrator<\/td>\n<td>VMware vRealize Orchestrator plugin (formerly known as VMware vCenter Orchestrator plug-in)<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.rbd<\/td>\n<td>Auto Deploy<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.syslog<\/td>\n<td>VMware Syslog Collector Configuration<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.vcDr<\/td>\n<td>VMware vCenter Site Recovery Manager Extension<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.vcHms<\/td>\n<td>vSphere Replication Management (VRM)<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.vcIntegrity<\/td>\n<td>VMware vSphere Update Manager Extension<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.vShieldManager<\/td>\n<td>vShield Manager<\/td>\n<\/tr>\n<tr>\n<td>vCloud Director-1<\/td>\n<td>vCloud Director<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.vcops<\/td>\n<td>vRealize Operations Manager (formerly known as vCenter Operations Manager)<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.vadm<\/td>\n<td>VMware vRealize Infrastructure Navigator (formerly known as vCenterInfrastructure Navigator)<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.vdp<\/td>\n<td>vSphere Data Protection 5.1<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.vdp2<br \/>\ncom.vmware.vdp2.config<\/td>\n<td>vSphere Data Protection 5.5\/5.8<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.vsan.health<\/td>\n<td>vSAN Health Check Plug-in<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.heartbeattasks<\/td>\n<td>vCenter Server Heartbeat<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.hbwc<\/td>\n<td>vCenter Server Heartbeat<\/td>\n<\/tr>\n<tr>\n<td>com.vmware.heartbeat<\/td>\n<td>vCenter Server Heartbeat<\/td>\n<\/tr>\n<tr>\n<td>com.neverfail.heartbeat<\/td>\n<td>vCenter Server Heartbeat<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n\n<div class=\"twitter-share\"><a href=\"https:\/\/twitter.com\/intent\/tweet?via=mad_manc\" class=\"twitter-share-button\">Tweet<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"<p>While running the vSphere 6.7 VMware Migration Assistant I received the following error: This vCenter Server has extensions registered that cannot be upgraded to or may not work with the new vCenter Server. In my case, the extensions were no longer being used. \u00a0So, I chose to just remove the offending extensions. 1. \u00a0Create a snapshot or backup of your vCenter server. 2. \u00a0Log into the Managed Object Browser (MOB). https:\/\/vcenterfqdn\/mob 3. Select\u00a0Content. 4. Select\u00a0ExtensionManager. 5. Capture the\u00a0VALUE\u00a0of the Extension you wish to remove. \u00a0(ex.com.vmware.vcHms): 6. Select UnregisterExtension 7. Enter the Value of the extension you wish to remove. \u00a0Then, select\u00a0Invoke Method. \u00a0Confirm that \u00a0you receive the Result of\u00a0Void. 8. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-248","post","type-post","status-publish","format-standard","hentry","category-vmware"],"_links":{"self":[{"href":"http:\/\/blog.jamesblakeley.ca\/index.php?rest_route=\/wp\/v2\/posts\/248","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/blog.jamesblakeley.ca\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/blog.jamesblakeley.ca\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/blog.jamesblakeley.ca\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/blog.jamesblakeley.ca\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=248"}],"version-history":[{"count":2,"href":"http:\/\/blog.jamesblakeley.ca\/index.php?rest_route=\/wp\/v2\/posts\/248\/revisions"}],"predecessor-version":[{"id":250,"href":"http:\/\/blog.jamesblakeley.ca\/index.php?rest_route=\/wp\/v2\/posts\/248\/revisions\/250"}],"wp:attachment":[{"href":"http:\/\/blog.jamesblakeley.ca\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=248"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/blog.jamesblakeley.ca\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=248"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/blog.jamesblakeley.ca\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=248"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}