Virtual Centre

General Configuration

Sysprep Setup

The following Sysprep support directories were created during Virtual Center installation, these need to be populated in order for the VC to be able to sysprep VM's as they are deployed using Guest Customisation:

<ALLUSERSPROFILE>\Application Data\Vmware\VMware VirtualCenter\sysprep
...\1.1\
...\2k\
...\xp\
...\svr2003\
...\xp-64\
...\svr2003-64\

where <ALLUSERSPROFILE> is usually C:\Documents And Settings\All Users\. Windows 2008 (and Vista) don’t need sysprep files as the function is built into the OS.

Download the ‘System Preparation Tool’ or ‘Deployment Tools’ package that contains ‘sysprep’ from the Microsoft download centre. Make sure that you download the correct version for the guest operating system and ‘Service Pack’ that you want to customize.

1.1: In the case of the generic version 1.1 simply run the downloaded executable to extract the files then copy the contents of the Tools directory into the appropriate directory (see below).

Windows 2000: In the case of Windows 2000 simply run the downloaded executable to extract the files into the appropriate directory (see below).

Win XP: In the case of XP run the downloaded executable to create deploy.cab then use something like WinZip to extract the files into the appropriate directory (see below).

Windows 2003: In the case of Windows 2003 the downloaded executable is a Hot Fix which must be run (Installed) on a matching OS to create deploy.cab then use something like WinZip to extract the files into the appropriate directory (see below).

TomCat Memory Throttle

The Tomcat webserver (used to provide VC Web-services), can be very memory hungry (up to 1GB) in comparison to when it ran on VC v2.5 (normally around 50MB). This can be throttled down, though this is only recommended for small, non-production installations (<10 ESX's).

1. Edit the registry to put a ceiling on the Java VM's memory usage
   1. Append --JvmMx=256 (MB) to end of HKLM\SYSTEM\CurrentControlSet\Services\vctomcat\ImagePath
2. Restart the service
   1. VMware VirtualCenter Management Webservices

Update Manager

Import updates from another VC

Useful when you've a isolated VC (without internet access), and another with a full compliment of updates.

1. Copy the updates from to the VC, copy the entire Data directory
   • Default location for updates C:\Documents and Settings\All Users\Application Data\VMware\Vmware Update Manager\Data
2. On the isolated VC, run a version of the following example command to update the Update Manager database
   • vmware-updateDownloadCli -p <path to patches>\Data -f esx -U <user ac>

Scan/Remediate fails

• Error: VMware Update Manager had a failure
• Detail: Patch metadata for <ESX> missing, please download patch metadata first, despite the fact that Update Manager is fully up to date.
• /var/log/vmware/esxupdate.log shows connection errors

1. On the VC, stop the VMware Update Manager Service
2. Edit vci-integrity.xml file
   • Normally found in C:\Program Files\VMware\Infrastructure\Update Manager\
3. Edit the following entry, adding the VC IP address
   • <PatchDepotUrl>http://VC-IP/vci/hostupdates/hostupdate</PatchDepotUrl>
4. Restart the VMware Update Manager Service

SQL Database

Migrate SQL2000 to SQL2005

This should be fairly painless (so long as your DBA knows his stuff!).

Before you start, you must ensure the Virtual Centre is using a SQL Native Client driver to access the database (see VMware KB1003391)...

1. Open up ODBC Data Source Administrator, and go to the System DSN tab
2. Check that the driver you're using is SQL Native Client
3. If not, you'll need to upgrade...
   1. Download from Microsoft and install SQL (see the VMware KB link above)
   2. Stop your Virtual Centre Server service
   3. Rename your existing DSN (eg append "old" to it)
   4. Create a new DSN using the new driver but otherwise exactly the same as the previous (the name MUST be the same)
   5. Restart the Virtual Centre Server service
   6. Login using the VI Client and ensure everything looks good (clusters, ESX's, VM's, Alarms, Guest Customisations etc)

To complete the migration...

1. Stop the Virtual Centre Server service
2. Backup the database (and log files) from your old SQL 2000 server
3. Restore the database (and log files) to your new SQL 2005 server
4. Ensure that your Virtual Centre's database account is the db_owner of the Virtual Centre database on SQL 2005 (as it was on the SQL2000 database)
5. Change the ODBC DSN settings on the VC server so it points to the SQL 2005 server (just change the server name, if you need to specify a non-standard TCP port use <SERVER>, <PORT> rather than <SERVER>:<PORT>)
6. Restart the Virtual Centre Server service
7. Login using the VI Client and ensure everything looks good (clusters, ESX's, VM's, Alarms, Guest Customisations etc)

Troubleshooting

VMware VirtualCentre Server service won't start

Service-specific error 2 (0x2) Caused by the SQL service being unavailable, therefore investigate why this is so.

If SQL is running on the same server, and the service failed after a reboot, its likely that its starting too quickly and SQL isn't ready. Either, make the service automatically restart after X mins (good practise anyway), and/or make the service depend on SQL.

To make the VirtualCentre Server service depend on the SQL service

1. Find the name of the SQL service
   • Find the MSSQL key in the following hive (will probably be MSSQL, MSSQL$SQLEXPRESS, etc)
   • HKLM\System\CurrentControlSet\Services
2. Make VC service dependant on it
   • Browse to HKLM\System\CurrentControlSet\Services\vpxd
   • Add the name of the SQL service to the DependOnService value (there must be a blank line at the end still)