So far, our Physical-to-Virtual migrations of Exchange 2003 on x86 Server 2003 Enterprise boxes have gone mostly smoothly – until this evening, that is. In the past, a failure soon after the P2V process started was resolved with a reboot or by disabling the TCP Offload Engine on the Broadcom NICs (this was easily accomplished with the cmd.exe command netsh int ip set chimney DISABLED).
This evening’s P2Vs were a bit more challenging.
This is a quickie post to share what I found when installing vCenter Server on a 64-bit Windows Server 2008 Enterprise Edition virtual machine. This VMware KB article is the error we received.
Apparently, during the installation of vCenter Server, Active Directory Lightweight Directory Services is installed. I hadn’t noticed this before. We had no server roles installed prior to installing vCenter, but after clicking through the error boxes that appeared, we saw that AD LDS, sure enough, appeared to be installed.
This post is the third in a series dedicated to helping you set up your update infrastructure in vSphere 4.1. Part I is about installing and configuring Update Manager. Part II shows you how to install and configure the Update Manager Download Service. As the last in this series, this post will explain how to patch your ESX/ESXi hosts.
This walkthrough is part II of a series of guides on installing and configuring VMware’s tools for updating and patching ESXi 4.1 hosts. You can find Part I here and Part III here. The Update Manager Download Service (UMDS) is used in an air-gap environment where the vCenter Update Manager server (VUM) does not have access to the Internet to download patches itself – instead it relies on UMDS to download the patches. Once patches are downloaded, they’re manually copied via removable media, usually a CD/DVD, to VUM. Once VUM has the patches, it then works through the vSphere Client and the Update Manager plug-in to update the hosts. Although VUM can download operating system patches for Windows and metadata for Linux patches, we’re not using this configuration in this guide. We’re assuming the environments are updated via WSUS or SCCM.
So during my first data center virtualization project, I had to write up a series of documents for internal reference. These documents were to help us perform a standard installation at each site we migrate. I thought it would be helpful to post them for anyone else looking to perform these tasks, as well. This series of posts is about VMware Update Manager 4.1U1 and its associated Update Manager Download Service. It appears in three posts because the topic can be logically separated into three steps: installing and configuring VUM, installing and configuring UMDS, and a patching guide once your initial update infrastructure is in place. This post, as you can see, is part I. Let me know if it helps you out or if I missed something. All the best!
At a minimum, you’ll want to perform regular backups of your vCenter, Update Manager, and System databases. You don’t have to be a DBA to perform simple backups. You don’t need to know T-SQL or database programming to perform these steps. There’s an easy wizard that walks you through a standard Windows Next-Next-Finish set up.
There are a couple things to note in the walkthrough below. We’re using SQL Server 2008 Enterprise Edition 64-bit on a 64-bit Windows Server 2008 SP2 Enterprise Edition. The SQL server is also a virtual machine in a vSphere 4.1 environment.