Dec 22, 2009 Blogs
I’ve upgraded my employer’s Lab Manager installation to 4.0.1 last thursday. I followed procedure by disallowing new deployments, undeploying all virtual machines, making sure nobody could login, double-decked that no event were currently running and make backups of the virtual machine and database files.
I commenced the upgrade, and clicked through the installer. The upgrade went smooth as far as I could see. After the upgrade, I went to the webpage of the LM-server to finish the upgrade wizard. Instead of the upgrade wizard, I was welcomed by the initialization wizard. It scared the hell out of me, this was not supposed to happen!
I assumed the installer did a boo-boo with the database, replacing it with a fresh one instead of upgrading the old one. I was right, in the installation directory of SQL I found the ‘old’ database in a *.renamed format. The new database files were smaller and had newer modified dates.
Dec 7, 2009 Blogs
I’m setting up a VMware vSphere environment for a demo and presentation I’m giving later this week on VMware vCenter Lab Manager 4 at the Dutch VMUG Event. I prepared a couple of VM’s on my laptop running VMware Workstation, among wich a vCenter Server installation. I installed two physical servers with ESX4, attached them to vCenter and configured a dvSwitch on both. As these hosts are really simple desktops with just a single NIC, I had to configure the dvUplinks group with one uplink per host. I migrated the Service Console Port (vswif0), created a couple of port groups for Virtual Machine networking and created a VMKernel port for NFS and VMotion. Since there was no need for the standard vSwitch anymore, I simply deleted the associated Port Groups and the vSwitch itself:
Dec 2, 2009 Blogs
I’ve been experiencing a problem with a very small VMware ESXi 4 host on which I run two VM’s for VMware vCenter Lab Manager management (a vCenter VM and a LM VM). I was rebuilding the environment, so I had both VM’s running on this host with (at that time) 3GB of RAM. When adding this host to vCenter, I got weird and cryptic error messages:
Cannot install the vCenter agent service. Unknown installer error.
I Googled my ass off, but never found an explanation or workaround. Finally, I decided to move the VM’s to another host, put it in maintenance mode, reboot it, and tried to add it to vCenter once more. For some reason or another, this worked!