Upgrade from vCenter Server 4 to vCenter 5 problems

Similar Questions

• The upgrade from vCenter for 64-bit

  I'm about to upgrade from version 4 to version 4.1 vcenter server and I have a few quick questions. I am a little concerned about the part of the database from the upgrade.  We currently have the database on a server remote windows 2003 and I was curious what, if anything, I have to do to the database if I use the DataMigration tool?  I have a new 64 bit server ready to go, but I'm a little curious what needs to be done to the database and it is ok to point the new 64-bit to 32-bit SQL server vCenter?  any help is appreciated.  Thanks for a great site!

  Perry

  prutter wrote:

  Yes, it is remote.   I have it!  Is the same thing applies to the Bishop of update database?  Thanks again.

  Yes, but Crossover requires a 32-bit DSN

• Upgrade to vcenter OS = problems with ADAM

  I recently improved my OS from 2008 to 2008 R2 vcenter. I created a new virtual machine, stole the name of the former vcenter, vcenter package installed and attached to the database. Everything works fine, however I'm continually getting the following error message in the event viewer for the VMWAREADAMVCMSDS service.

  The following FSMO role owner is set on a server that is deleted or does not exist.

  Operations requiring contact with a master FSMO operation will fail until this problem is corrected.

  Is there an easy fix for this?

  When you deleted it as an instance of bound modes, you crossed the vCenter Installer and chose to "insulate the vCenter Server Instance of the Group of related modes"?  You can do the two vCenter the Instance in question and the one with which he was associated, with as always, they may think that they are related.  Maybe link them again and then go through the process of linking not them

  See also

  http://KB.VMware.com/kb/1025665

• After upgrading from windows and reboot "diagnose the connection problem" rises and won't let me use windows until the removal of updates

  diagnose the connection problem

  You can try to uninstall the update 974455 that came out last Tuesday, removing it seems to have resolved other

• vCenter Storage Monitoring Service Service initialization failed after the upgrade from 5.1 to 5.5

  I recently upgraded from vCenter 5.1 to 5.5. After the upgrade, I started getting health warnings for the VMware vCenter monitoring of Storage Service that say "failed to initialize the Service." I restarted the vCenter server and restart services several times and who has not deleted the question. When I look in the SMS. LOG file there is no activity in it since I did the upgrade (a week or more there). All prior activity in the SMS. JOURNAL seems to be well upward until the upgrade took place though. I found at least half a dozen KB articles that describe the various reasons why this error may occur, but they all relate to older versions of vCenter. Just to be complete, although I saw the symptoms in the articles and none of them really seem to be the same as what I see. My hypothesis is that perhaps the SMS did not get properly re-installed upgrading because I don't see any SMS subdirectory in the directory \Program Files\VMware\Infrastructure\tomcat\webapps but I do not know if this directory must exist on a 5.5 installation.

  If you would be grateful if anyone has any advice for troubleshooting for this type of error.

  Thank you

  Mike

  Change the credentials of the service account for VMware vSphere Profile-Driven Storage Service to those used to start the VMware vCenter Server service and the service of VMware VirtualCenter Management Webservices. By default, the account used Local System.

  Restart the service, the change was made, and then check.

• Upgrade to vcenter server 5.1 without interrupting display connections

  Dear Experts,

  We need to upgrade the server vcenter to 5.1. VMware Server connection view won't

  The ESX servers become 5.1 as well

  Work with

  -vmare vcenter server 5.0

  -connection to the server view vmare 5.0 (no linked clone, automated pool)

  -ESXi 5.0

  Plan:

  -In place move vcenter server 5.0 to vcenter server 5.1

  Question:

  -Could we perform the upgrade from vcenter without interrupting the view vmare machines?

  -Is that I have to restart the server view connection manager

  -During the upgrade, will be the loose connection to their machines?

  -During the upgrade, the user will be able to authenticate, start their machines?

  Thank you for your support

  Wines

  [email protected]

  Dear Experts,

  -Could we perform the upgrade from vcenter without interrupting the view vmare machines?

  -Is that I have to restart the server view connection manager

  -During the upgrade, will be the loose connection to their machines?

  -During the upgrade, the user will be able to authenticate, start their machines?

  Thank you for your support

  Wines

  1: Yes

  2: no

  3: no

  4: depends on what policies of power you are using.  Since vCenter is going to be offline you won't be able to start and stop machines.  The best thing is to change your feeding strategy for always under tension and ensure that all machines are available during the interview of vCenter.

• How to upgrade from Virtual Center 2.5 + SQL Server 2000 to vCenter 4.1 + SQL Server 2008 (R2)?

  I plan the upgrade of an existing VMware Infrastructure 3 (Virtual Center 2.5 + ESX 3.5) to vSphere 4.1, and I'm stuck in the Virtual Center Server upgrade and its back-end database.

  vSphere 4.1 is released only as a 64-bit software, so he needs a x 64 O.S.; This excludes an upgrade the existing server on-site.

  The plan is to install a new Server Windows Server 2008 R2 with SQL Server 2008 (or 2008 R2 if taken in charge), migrate the database and install 4.1 on the server vCenter.

  The question: How can I migrate the database?

  When you perform an upgrade of Virtual Center vCenter 4.0 on-site, the database is automatically upgraded; but this isn't the case when you install a new server.

  VMware provides a utility to clear the existing database and import it into a new server, but it works only for SQL Server Express (which according to VMware must not be used in medium/large production environments); If this is not an option.

  I am unable to find a support procedure to perform this migration.

  Can someone please help?

  Massimo,

  I just went through it and found it to be a little pain simply because I forgot to VMware document simplicity...

  You are right, the 'migration' tool does support SQL Server Express, I don't know why and niether are the two VMware Tech Support Agents I spoke with.

  To anyone reading this. NOTE If you perform the upgrade / migration SQL Server Express via the Migration tool you MUST check the registry DbServerType key FIRST! If it is set on Custom Migration tools will ignore simply stages of database! See this VMware KB article for more information:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1024380

  Yes, it is the States 'failure', what he does not say, it is that the Migration tool will be 'Silencieusement Skip' your database.

  End of Migration tools do call a standard SQL Server T - SQL backup command. YAY! You don't have to upgrade your existing 32-bit vCenter Server, do first just in case backup/snapshot, then run through the upgrade as if you were going to use the 32-bit version in production. This step will apply to any database schema change.

  Build your brilliant new 64-bit server, install all of the bits and then use SQL Server Management Studio to make a backup of SQL Server 32-bit database and then restore it on your new 64-bit server. NOTE: Make sure that all SQL and vCenter services are stopped before proceeding with the backup and restore of the measures.

  After the restoration of the SQL on your new server it reboot and everything will come back to life just as it is only now with all 64 bit!

  Hope this Helps!

  Bill Hilburn, Senior Systems Engineer

  StoneAge, Inc.

  http://StoneAgeTools.com

• vCenter upgrade from 5.0 to 5.5 for the new machine, SRM and dvswitch

  Anyone know if it is possible to do a upgrade to vCenter from a machine under windows server 2008 on a new computer server 2012? The database is located on an external computer. All I can see in the upgrade doc is that there is a tool for migrating data with earlier versions, but not when moving to 5.5.

  Also - what implications are there if there's a dvswitch in the site?

  Thank you very much

  Hello

  I guess you run ESXi and vCenter 5.1?

  If it were me, I'd do the following:

  -Install a new instance of vCenter on a new Server R2 2012

  -Turn off the old server vCenter on 2008.

  -Save the remote SQL database vCenter.

  -Install a new instance of the Web, the inventory Service and SSO client. I remind vCenter to use the SQL remote database existing and chose to 'upgrade' when installing vCenter.

  Then you'd be in vCenter server 2012 R2 with a new facility and using your old database that will get upgraded. You will always retain so your dvSwitch information. I'm not sure of SRM, you probably need to reconfigure it to use the new vCenter Server (unless you use IP records or that you can easily return?).

  There are a few things to think about when you really do. Can you afford any downtime on vCenter? What of SRM and your RPO/RTO? The complexity is your configuration of SSO? Use you things like tags in web client (they would get lost in the reconstruction of the inventory service)? What confidence you are on the side of things RS? It is possible to save these configurations, but I'm not sure restore them on 5.5.

  The main thing to consider is the database really. Worst case, you can restore it and turn back on your old vCenter 2008.

  Happy to be told I'm wrong or answer your questions. If in doubt, contact VMware technical support and ask for help.

  Kind regards

  Ryan

• Lack of Configuration section in VAMI, vCenter active watch is not Accessible after upgrade from 5.5 to 5.8

  Hi all!  I'm having a bit of a problem that I can't find a solution for anywhere.

  I have a lab with two boxes of vcsa under 5.5 U2d, and wanted to move to 5.8 SRM.  I started the VRA 5.5.1 (I do not remember, real version number which was with MRS 5.5.1), mount the ISO 5.8 on both sides, restarted both, took the update of the CD (following the official update steps), but after the restart, the two vCenters show "enabled (not available)" and still list it as 5.5.1.

  I have validated the RV service is running.  I have been following this thread, regenerated certificates for the TWO vCenters & TWO VRAs: vsphere upgrade from 5.5 to 5.8 Server replication enabled (not accessible) has yet no joy.

  I checked the CROWD and the IP address is correct.  I tried to check /opt/vmware/hms/conf/extension.xml for the thumbprint and the file does not exist on each box, the only thing it is extension - template.xml.

  On the one hand, I have reset the vCenter database (/ usr/sbin/vpxd - d of VMware KB: reset the vCenter Server repository embedded for vCenter Server Appliance 5.x ), deployed a new VRA 5.8, and he had to register very well.  It's then it dawned on me what missed me: almost all the Startup Configuration where you specify the vCenter (see attachment)

  For grins, I recorded the VRA 5.8 of the 'old' vcsa work and tried to save it to the 'new' vcsa, which he could not with a lot of what looked like errors, assuming that because of 'new' vcsa already having a recorded SOAP VRA.  I re-recorded it back to the 'old' vcsa and is happy.  Installed SRM 5.8 (uninstalled 5.5 because I started with a clean database in the vcsa) and all is well on the side of the 'old '.

  I'm trying not to go this route on the 'new' side, as I a VDS, vSAN and twice as many hosts, so I won't recreate the vDC, cluster, add guests, etc.  I copied to /opt/vmware/hms/conf/extension-template.xml /opt/vmware/hms/conf/extension.xml and restarted.  Footprint arises, but still no configuration tips.

  Anyone have any ideas?

  Thanks for your reply. You said that the VRA is on a cluster, East of thatcluster HA-enabled? Because where HA must restart the VRA on another host, it does so through the ESX host and this could have emptied the OVF environment. And to even you'll always a working configuration until you start the upgrade or you try to perform any operation through VAMI configuration page. To be on the safe side, I think before upgrade, you can power off and then turn the unit on (simple restart is not enough) to make sure that the EPS of the FVO is recreated.

• The upgrade to vCenter Server to vCenter Server 5.1 5.1 update 1 when the SQL database is remote and vCenter Server Heartbeat is installed

  Hi guys,.

  I'm in the middle of an upgrade to vSphere 5.1 5.1 vSphere update 1. I have vCenter protected by HB and SQL on a separate computer (also protected by HB) I also run Syslog, Update Manager and Proxy authentication on vCenter.

  I've successfully upgraded HB on all 4 nodes (2 x vCenter & 2 x SQL) and started the upgrade components on the secondary according to the •vCenter Server Heartbeat 6.5 server and vCenter Update 1 Installation on Windows Server 2008 when the secondary server is virtual (PDF) http://www.vmware.com/pdf/vcenter-server-heartbeat-65-u1-installation-windows-2008-virtual-guide.pdf

  I got to step 3.c

  3. change the primary/active server role:

  a launch of the vCenter Server Heartbeat wizard configure server and click the tab of the Machine to change the server role for the current server (primary) to the active State and click Finish.

  b using the Service Control Manager, start the Server Heartbeat of VMware vCenter service.

  c using the vCenter Server Heartbeat Console, check that all the status icons on the server: summary page are green indicating that the boot process is completed and protected from all the services are started.

  d using the Service Control Manager, stop the service Server Heartbeat of VMware vCenter.

  As the vCenter service does not start, I'm stuck at this point. As far as I'm concerned, the error is quite logical. I've updated vCenter using the secondary server, and then I'm trying to connect (according to the guide) with another version that breaks down.

  If I continue with the services stop and launch the installer SSO, it is trying to perform an uninstall!

  Did I miss something in this upgrade?

  Concerning

  
  Ciaran

  Hi guys, VMware have finally updated the documentation to reflect the right way forward: https://www.vmware.com/support/pubs/heartbeat_pubs.html U1 6.5 Select from the menu drop-down and you'll see the last date of update for each of the documentation is now 10/10/2013. The guide States now specifically to restore the vCenter database before proceeding with any other measure, this is copied below for convenience: "the upgrade of the main server of the upgrade process further guess upgrading the secondary server completed successfully. Procedure 1 before continuing the upgrade process, perform a restore of the database of vCenter Server, Single Sign-On database, VMware Update Manager database and SSL certificates that were backed up in step 4 on the secondary server. regards Ciaran

• Best practices for upgrading from 2.5u5 to vCenter 4.1

  Hello

  We are currently running a vCenter 2.5 5 update on Windows 2003 32-bit Standard that we need to upgrade to vCenter 4. Unfortunately the latest version 4.1 needs a 64 bit OS...

  What is the best practice to update our vCenter 4.1 and keep all performance data? I suppose we ought to do it in severalsteps or not?

  (1) vCenter 4.0 Update 2 update

  (2) a copy of the updated vCenter database backup

  (3) to perform a new installation of Windows 2008 64-bit

  (4) to perform a new installation of vCenter 4.0 Update 2

  (5) to restore the database

  (6) update for vCenter 4.1

  Is this correct or am I missing something? Is there a more easy/better way?

  Any help appreciated.

  Hello.

  KO 1022104 contains best practices, and the Upgrade Guide is also a great resource to use for this upgrade planning.  Follow the steps in the Upgrade Guide and everything should go smoothly.

  This is a really difficult list of steps, confirmed by the Upgrade Guide:

  01 build of new VMS 64-bit for vCenter

  02. prep new vCenter VM for connectivity / SQL dependencies

  03. backup of the existing database.

  04 data backup current vCenter using Data Migration tool

  05 use the data migration tool to start the setup of the vCenter server and restore the configuration of the server vCenter to the destination machine.

  06 turn off from the old server vCenter.

  07 restore the vCenter Server Configuration and installing vCenter Server on the new server

  08 updated vCenter Server name of Plug-Ins (if the new vCenter has a different name)

  09. test cycle

  Good luck!

• vCenter does not start after the upgrade from 5.1 5.1 U1b (UNIQUE authentication failed)

  Hello

  We have upgrade to vCenter Server (build 880146) 5.1.0a to vCenter Server 5.1. U1b and now vcenter service does not start

  This is the log:

  2013 10-21 T 10: 58:40.221 + 02:00 [02800 info '[OSP]'] [UserDirectorySso] GetUserInfo (Administrators, true)

  2013 10-21 T 10: 58:40.221 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [GetDomains]

  2013 10-21 T 10: 58:40.252 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [LazyInitAdmin] initialization

  2013 10-21 T 10: 58:40.252 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [InitSsoAdminServices]

  2013 10-21 T 10: 58:40.252 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [CreateAdminSsoServiceContent] try to connect to the administration of the SSO server.

  2013 10-21 T 10: 58:40.330 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [InitSsoAdminServices] successfully.

  2013 10-21 T 10: 58:40.330 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [LoginToAdmin]

  2013 10-21 T 10: 58:40.330 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [CheckTokenValidity]

  2013 10-21 T 10: 58:40.330 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [CheckTokenValidity] refreshing SSO token...

  2013 10-21 T 10: 58:40.330 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [RefreshSsoToken]

  2013 10-21 T 10: 58:40.408 + 02:00 [02800 error "[OSP] [SsoAdminFacadeImpl]"] AcquireToken [RefreshSsoToken] exception: failed authentication: authentication failed

  2013 10-21 T 10: 58:40.408 + 02:00 [02800 info '[OSP]'] [UserDirectorySso] GetUserInfo NormalizationException: RemoteGetDomainNames RuntimeServiceFault exception: sso.fault.RuntimeServiceFault

  2013 10-21 T 10: 58:40.408 + 02:00 [02800 error '[OSP]'] [UserDirectorySso] NormalizeUserName AuthException: allow exceptions

  2013 10-21 T 10: 58:40.408 + 02:00 [02800 error '[OSP]'] [UserDirectorySso] GetDefaultPrincipal AuthException: allow exceptions

  2013 10-21 T 10: 58:40.408 + 02:00 [02800 info '[OSP]'] GetDefaultPrincipal(, true) [UserDirectorySso]

  2013 10-21 T 10: 58:40.408 + 02:00 [02800 info '[OSP]'] GetUserInfo(, true) [UserDirectorySso]

  2013 10-21 T 10: 58:40.408 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [GetDomains]

  2013 10-21 T 10: 58:40.408 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [LazyInitAdmin] initialization

  2013 10-21 T 10: 58:40.408 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [InitSsoAdminServices]

  2013 10-21 T 10: 58:40.408 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [CreateAdminSsoServiceContent] try to connect to the administration of the SSO server.

  2013 10-21 T 10: 58:40.439 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [InitSsoAdminServices] successfully.

  2013 10-21 T 10: 58:40.439 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [LoginToAdmin]

  2013 10-21 T 10: 58:40.439 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [CheckTokenValidity]

  2013 10-21 T 10: 58:40.439 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [CheckTokenValidity] refreshing SSO token...

  2013 10-21 T 10: 58:40.439 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [RefreshSsoToken]

  2013 10-21 T 10: 58:40.502 + 02:00 [02800 error "[OSP] [SsoAdminFacadeImpl]"] AcquireToken [RefreshSsoToken] exception: failed authentication: authentication failed

  2013 10-21 T 10: 58:40.502 + 02:00 [02800 info '[OSP]'] [UserDirectorySso] GetUserInfo NormalizationException: RemoteGetDomainNames RuntimeServiceFault exception: sso.fault.RuntimeServiceFault

  2013 10-21 T 10: 58:40.502 + 02:00 [02800 error '[OSP]'] [UserDirectorySso] NormalizeUserName AuthException: allow exceptions

  2013 10-21 T 10: 58:40.502 + 02:00 [02800 info '[OSP]'] GetUserInfo(, true) [UserDirectorySso]

  2013 10-21 T 10: 58:40.502 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [GetDomains]

  2013 10-21 T 10: 58:40.502 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [LazyInitAdmin] initialization

  2013 10-21 T 10: 58:40.502 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [InitSsoAdminServices]

  2013 10-21 T 10: 58:40.502 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [CreateAdminSsoServiceContent] try to connect to the administration of the SSO server.

  2013 10-21 T 10: 58:40.533 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [InitSsoAdminServices] successfully.

  2013 10-21 T 10: 58:40.533 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [LoginToAdmin]

  2013 10-21 T 10: 58:40.533 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [CheckTokenValidity]

  2013 10-21 T 10: 58:40.533 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [CheckTokenValidity] refreshing SSO token...

  2013 10-21 T 10: 58:40.533 + 02:00 [02800 info "[OSP] [SsoAdminFacadeImpl]"] [RefreshSsoToken]

  2013 10-21 T 10: 58:40.595 + 02:00 [02800 error "[OSP] [SsoAdminFacadeImpl]"] AcquireToken [RefreshSsoToken] exception: failed authentication: authentication failed

  2013 10-21 T 10: 58:40.595 + 02:00 [02800 info '[OSP]'] [UserDirectorySso] GetUserInfo NormalizationException: RemoteGetDomainNames RuntimeServiceFault exception: sso.fault.RuntimeServiceFault

  2013 10-21 T 10: 58:40.595 + 02:00 [error 02800 "Default"] cannot add the default permission: user not found

  2013 10-21 T 10: 58:40.595 + 02:00 [error 02800 "Default"] cannot start allow - system has no access rule

  2013 10-21 T 10: 58:40.595 + 02:00 [error 02800 'Default'] [Auth] initialization failed: < class Vmacore::Authorize:AuthException(Authorize_Exception) >

  2013 10-21 T 10: 58:40.595 + 02:00 [02800 error 'authvpxdAuthorize'] could not initialize security

  2013 10-21 T 10: 58:40.595 + 02:00 [02800 WARNING "VpxProfiler"] ServerApp::Start [TotalTime] took ms 27456

  2013 10-21 T 10: 58:40.595 + 02:00 [02800 info 'Default'] judgment of VMware VirtualCenter.

  Hello

  VMware support solve my problem:

  We have seen two issues after the update.

  First of all, there is no user of the solution for the virtual center when I checked the application users with SSO to the webclient service administration page.

  Solve us this problem of repointing Virtual Centre to the next according to the kb SSO instance;

  http://KB.VMware.com/kb/2033620

  1. repoint.cmd configure vc - search server https://vcenter.com:7444/lookupservice/sdk - password "laquesea" - openssl-path of the user "admin@System-Domain"-"C:\Program Files\VMware\Infrastructure\Inventory Service\bin."

  After that, the modules in the vpxd.cfg solution was not properly updated and an operation manual.

  C:\ProgramData\VMware\VMware VirtualCenter\SSL\sso.crt

  vCenterServer_251703

  C:\ProgramData\VMware\VMware VirtualCenter\SSL\sso.key

  Above is the corrected version having replaced "null" with the correct path to the files of certificate and key.

  This allowed vcenter service start successfully.

• Upgrade from 5.1 to 5.5 - problem with VClient and inventory VCenter

  Hi all

  I just upgraded our VCenter of 5.1 to 5.5. All done successfully without warnings or errors. Verify that SSL certificates are still valid.

  Has decided to upgrade the databases too.

  Here's the problem:

  If I use the webclient service I have to use a user name in the format user@domain and then I connect successfully, but connected once the inventory is not empty, no host at all.

  If I use the VClient, it simply doesn't: failed (unable to connect to the remote server (o) connection.

  I tried to fix it by reinstalling the service inventory, but after that the error is the same.

  We have seen, it is because less 5.5 AD inheritance behaves differently, because it does not inherit.

  If you follow the steps on this link it should solve the problem for you.

  vCenter Single Sign-On not grateful 5.5 nested Active Directory groups. VMware vSphere Blog - VMware Blogs

  Kind regards

  Iain

• problems to install the latest plugin from vcenter server 5.0.0.149 on the vco 4.1.1 build 733.

  I have problems to install the latest plugin from vcenter server 5.0.0.149 on the generation of vco 4.1.1 733.

  If I go to the plugins tab I see vCenter Server 5.0.0.149 Installation OK

  I configured a host esx to vCenter Server tab, but as soon as I click on 'Apply' it starts to load forever.

  I tried to restart the server vco and vco configuration services, but the problem remains unchanged. In the server.log I couldn't find anything relevant, but it is still attatched

  Hello!

  Try increasing the memory for the configurator web-tool, as described in the release notes:

  http://www.VMware.com/support/Orchestrator/doc/vCenter-server-plugin-50-release-notes.html

  See you soon,.

  Joerg

• The upgrade to vCenter Server

  Is it possible to manage guests 4.1 with a server vCenter on 4.0?

  What is involved in upgrading to vCenter Server 4.0 to 4.1 and what are the caviats?

  Matrix control to check all the mixed http://www.vmware.com/pdf/vsphere4/r40/vsp_compatibility_matrix.pdf