VM /ETC

Posts Tagged ‘vcenter’

This post is just a quick how to reference for manually changing the VMware Update Manager (VUM) patch repository download location. Admins usually need to do this when the vCenter server is low on disk space on the partition that VUM was originally installed on, but there is a second partition that has enough capacity. To move the VUM patch repository follow the following steps found in the VUM Administrators Guide:

When you install Update Manager, you can select the location for downloading patches. To change the location after installation, you must manually edit the vci-integrity.xml
file.

Procedure

1. Log in to the Update Manager server as an administrator.
   
2. Stop the Update Manager service.
   
   1. Right-click My Computer and click Manage.
      
   2. In the left pane, expand Services and Applications and click Services.
      
   3. In the right pane, right-click the VMware Update Manager Service and click Stop.
      
3. Navigate to the Update Manager installation directory and locate the vci-integrity.xml file.
   
   1. The default location is C:\Program Files\VMware\Infrastructure\Update Manager.
      
4. Create a backup copy of this file in case you need to revert to the previous configuration.
   
5. Edit the file by changing the following fields:
   
   1. yournewlocation
   2. The default patch download location is: C:\Documents and Settings\All Users\Application Data\VMware\VMware Update Manager\Data\
      
   3. The directory path must end with \.
      
6. Save the file in UTF-8 format, replacing the existing file.
   
7. Copy the contents from the old patchstore directory to the new folder.
   
8. Restart the Update Manager service.
   

This VMworld 2009 session took place Thurs at 9:30 am in room 134

Points made by the presenter worth remembering.

• Physical failure is unavoidable, and an ounce of prevention is worth a pound of cure
• There is a 50% chance that pieces of an ESX Cluster will fail and take down critical services and servers.
• You’re not usually staring at a monitoring screen, and you want to be notified as the hardware degrades not afterwards.
• You want as much hardware info about a host, from multiple different vendor platforms, and on a single screen
• Physical failure is a fact of virtual life
• Be proactive about hardware failure and use DRS + hardware monitoring + Alarms

An interesting demo in this session showed the use of  the built in vCenter 4 host hardware temperature status alarm generating SNMP traps as well as automatically putting a host in maintenance mode so an administrator can investigate. This action instigated a VMotion evacuation of the VMs on the impacted host and effectively isolated the hardware issue in the environment with minimal or zero impact.

My key take away of this session is that numerous “out of the box” vCenter event based alarms can be leveraged during the warning phase of hardware failures. This includes alerts covering power, fans, cpus, memory, batteries, etc. The ESX host hardware monitoring feature is detected and available automtically in vSphere 4.

My notes: Read the rest of this entry »

In order to create customized Windows 2003 and earlier virtual machines (VMs) the Microsoft Sysprep tools need to be added to VMware vCenter (also formerly known as VirtualCenter). Doing so is not a difficult process, but can be a bit confusing if an administrator has never used Sysprep before. Fortunately, VMware has a helpful KB article on the topic that explains where to download the Sysprep files from Microsoft and then where to put the extracted contents of those downloads on the vCenter Server. I’m going to high lite the instructions from VMware for downloading from Microsoft, but then I’ll explain how to get Sysprep from an alternate and arguably easier source – the Windows install CD.

Note that integrating the Sysprep files are still required in all versions of vCenter to customize VMs. This includes vCenter 4 for vSphere. Sysprep is no longer used for Server 2008, however, but VMware has added native customization of Server 2008 VMs in vCenter 4 without adding any additional files.

KB Article 1005593 titled Sysprep file locations and versions not only provides download links and extract to locations but also explains the common symptoms when Sysprep is not installed correctly on vCenter.

• When attempting to customize the deployment of a virtual machine the radio buttons are disabled (greyed out).
• When a virtual machine (VM) is deployed from a Template, you find that the SID is always the same, despite the fact that you chose the option to generate a new SID during Template deployment and guest operating system customization.
• When attempting to create a new virtual machine from a Template in ESX v3.5 you receive the following error message

Warning: Windows customization resources were not found on this server

• Message in the guestcust.log:

deploy doesn’t contain known sysprep files

The KB article explains the cause

Microsoft has a different version of Sysprep for each release and service pack of Windows. According to Microsoft, “You need to use the version of Sysprep specific to the operating system you are deploying”. The differences are not immediately visible in the packaging and documentation of the service packs, so it is necessary to manually investigate.

Use either of the following methods to obtain the appropriate Sysprep files. All instructions in this post assume vCenter has been installed in the default location. Read the rest of this entry »

In my previous post 730 Days Later I pointed out the default VirtualCenter SSL certificate was only good for 2 years. If the untrusted certificate installed with vCenter and ESX was not replaced by the VI admin problems could arise when connecting with the VI Client or via the ESX 3.X web interface. Now with vSphere the default vCenter 4 and ESX 4 SSL certificate still needs to be changed, but it has been updated and is now good for 10 years giving admins a little more breathing room.

VMware has also updated it’s PDF on how to replace the cert. Be sure to download the new guide for Replacing VirtualCenter Server Certificates. Here is some brief info from the first paragraph of this document:

Certificates are automatically generated when you install vCenter Server and ESX/ESXi. These default certificates are not signed by a commercial certificate authority (CA) and may not provide strong security. You can replace default vCenter Server and ESX/ESXi certificates with certificates signed by a commercial CA.

This Technical Note includes the following topics:
“About vCenter Server Certificates” on page 1
“Pre?Trusting Server Certificates” on page 2
“Certificate Specifications” on page 2
“Certificate Locations” on page 2
“Replacing Default Server Certificates with Certificates Signed by a Commercial CA” on page 2
“Replacing Default Server Certificates with Self?Signed Certificates” on page 5
“Related Publications” on page 8

NOTE   If you have replaced the default vCenter Server or ESX/ESXi host certificates with certificates signed by a commercial CA, you do not need to perform the tasks in this document. You can configure server?certificate verification settings using the vSphere Client. See the Basic System Administration Guide for more information.

The vSphere Basic System Administration Guide can be found here.

VMware also has a couple of KB articles about best practices using SSL keys for communicating with VirtualCenter. Go here or here

An administrator can also decide to turn off the verification of SSL certificates. To do this go to the vCenter Settings from the vSphere Client and disable this feature in the SSL Settings section. This is also explained in the System Administration Guide mentioned previously.

When Microsoft released Server 2008 the Windows Automated Installation Kit (WAIK) was introduced and Sysprep could no longer be used for deploying new servers. This meant that VMware needed to modify vCenter to allow for deploying new VMs from a Server 2008 template. The virtualization community quickly found a work around for the process on vCenter 2.5 and ESX 3.x.

When vSphere was released, it was announced that VMware included the necessary .xml file to customize Server 2008 with vCenter 4, thus meaning that VM customization and 2008 Customization Specifications could be used out of the box without any manual modifications (i.e. adding Sysprep files to the designated vCenter directories). For a walk through of the vSphere Server 2008 deploy from template process with screen shots check out: How to Deploy a Windows 2008 Server From a Template with vSphere

However, in my experience so far creating Server 2008 templates and deploying new VMs the process doesn’t work quite right every time. When I’ve deployed a new Server 2008 VM from the template I’ve experienced an incomplete boot on the new VM. Windows prompts from the install DVD and suggests a recovery is needed. I’ve experienced this recently with 64 bit Server 2008, but I can’t recall if my previous issue was ever on a 32 bit server or not.

Fortunately the same work around for VI 3.5 still works for vSphere as well. Check out the link above for more details, but the basic process is as follows:

1. Build your Server 2008 VM until it’s ready to become a template
2. Before changing it to a template change the operating system type in the “Edit Settings” window to Vista 64 bit
3. Turn the VM into a template
4. Create a customization specification, and / or deploy and customize the new VM.
5. Before booting the new VM change the OS type back to Windows Server 2008

updated 081509 – I had the steps above slightly mixed. Fixed the steps so the OS type change occurs before the VM is converted to template

Admins of heavily consolidated VMware VI 3 Clusters should make plans as soon as possible to download Update 5 of VMware vCenter Server to take advantage of increased performance and scalability. The latest update to vCenter 2.5 was released on July 10 and boasts improvements to support fail over management of up to 80 VMs per ESX/ESXi host in a HA (High Availability) Cluster.

The following details were taken from the VMware VirtualCenter 2.5 Update 5 Release Notes:

What’s New

Support for High Consolidation in VMware HA Clusters – VirtualCenter 2.5 Update 5 includes significant performance and scalability improvements to VMware HA. Use VirtualCenter 2.5 Update 5 for environments with more than 35 virtual machines (VMs) per host in an HA cluster.

For information on the ESX Server host settings required for this scalability improvement, see ESX Server host settings required for environments with up to 80 virtual machines per host in an HA Cluster (KB 1012002).

Upgrading or Migrating to VirtualCenter 2.5 Update 5

This release supports upgrading from VirtualCenter 1.4.1, VirtualCenter 2.0.2 (including Update 1, Update 2, Update 3, Update 4, and Update 5), VirtualCenter 2.5, VirtualCenter 2.5 Update 1, VirtualCenter 2.5 Update 2, VirtualCenter 2.5 Update 3, or VirtualCenter 2.5 Update 4, to VirtualCenter 2.5 Update 5. Review the detailed upgrade and migration instructions and guidelines that are provided in the Upgrade Guide.

Following the above link to KB 1012002 explains that upgrading vCenter 2.5 to U5 is just the start. VI 3 admins also need to make some additional configurations on ESX/ESXi hosts to achieve the 80 VMs per host improvements.

“Starting with the VirtualCenter 2.5 Update 5 release, an ESX Server host in an HA cluster can support up to 80 virtual machines. For all virtual machines to power on on other hosts in the cluster, if hosts within the failover capacity limit fail, you need to ensure that the following parameters in the ESX Server hosts are set with the following values:

Read the rest of this entry »

VMware has released Update 4 of the VirtualCenter Management Server (also now known as vCenter). The latest Release Notes detail a couple new features, several Plug-In updates, and numerous resolved issues. The current build of ESX/ESXi 3.5 Update 3 has not changed as of this post.

The following cut and pastes were taken while skimming through the release notes and highlight the changes that caught my attention.

What’s New

• Guest Operating System Customization Improvements – VirtualCenter now supports customization of Windows Server 2008 guest operating systems.
• Performance Overview Charts – VirtualCenter 2.5 Update 4 introduces the Performance Overview plug-in, which provides a single view of key performance metrics for CPU, memory, disk, and network without having to navigate through multiple charts. The aggregated charts show high-level summaries of resource distribution.

Plug-Ins Updates

This release of the VMware Infrastructure 3 software suite also includes the following:

• An update to VMware Converter Enterprise. For more information, see the VMware Converter Enterprise Update 4 for VirtualCenter 2.5 Release Notes.
• An update to VMware Update Manager. For more information, see the VMware Update Manager 1.0 Update 4 for VirtualCenter 2.5 Release Notes.
• The Performance Overview plug-in.

Two builds of VMware Infrastructure Management Installer are available for download.

• VMware-VIMSetup-2.5.0-U4-English.iso or VMware-VIMSetup-2.5.0-U4-English.zip – These files include an English-only version of the VI Client, which runs in English regardless of the language of the Windows system. Use this installer to install a VI Client that will run in English on Chinese, German or Japanese versions of the Windows operating system.
• VMware-VIMSetup-2.5.0-U4-localized.iso or VMware-VIMSetup-2.5.0-U4-localized.zip – These files include a localized installer that installs all files needed to run in English, Chinese, German, or Japanese. The VI Client used at runtime will correspond to the locale of the current Windows operating system if the locale is Chinese, German or Japanese. On Windows operating systems set to locales other than Chinese, German, or Japanese, the English version of the VI Client will be used.

I am assuming it is also recommended that you upgrade all instances of the Read the rest of this entry »