The following two lists of knowledge base articles are our top 10 articles that our SysOps Support Engineers are using to solve customer Support Requests during the month of January. The resolution to these problems were already documented, but for some reason customers either didn’t know these articles existed, they did not find them during their search, or they called in anyway for some other reason.
Top 10 Articles (vCenter Server,ESX/ESXi 3.5,4.x and 5.x):
- Installing or upgrading to ESXi 5.1 best practices (2032756)
- Creating a persistent scratch location for ESXi 4.x and 5.x (1033696)
- Purging old data from the database used by vCenter Server (1025914)
- Upgrading to vCenter Server 5.1 best practices (2021193) with video!
- Methods of upgrading to ESXi 5.1 (2032757)
- Repointing and reregistering VMware vCenter Server 5.1.x and components (2033620)
- Installing vCenter Server 5.1 best practices (2021202) with video!
- Methods of upgrading to vCenter Server 5.1 (2021188)
- Enhanced vMotion Compatibility (EVC) processor support (1003212)
- Configuring syslog on ESXi 5.x (2003322)
Top 10 Articles (vSphere 5.x) Troubleshooting and Known issues related:
- Upgrading to VMware Tools 5.1 causes log spew in the Windows Event Log: Error in the RPC receive loop (2036350)
- ESXi 5.1 host becomes unresponsive when attempting a vMotion migration or a configuration change (2040707)
- After making a change or restarting Single Sign On server system, vCenter Server 5.1.x fails to start (2036170)
- Troubleshooting ESX/ESXi virtual machine performance issues (2001003)
- Implementing CA signed SSL certificates with vSphere 5.1 (2034833)
- Storage vMotion fails with the error: The method is disabled by ‘SYMC-INCR dd-mm-yyyy hh:mm’ (2008957)
- Search fails and Hardware Health and Health Status plug-ins are disabled in the vSphere Client (2031053)
- Guest OS customization fails with no errors when deployed from French/Russian Windows template (2042564)
- Adding an ESXi 5.0 host to vCenter Server 5.0 fails with the error: A general system error occurred (2009217)
- After using a service account to configure an Identity Source in vCenter Single Sign-On, users from that domain are unable to log in (2037546)