Friday 23 August 2013

Error building from Windows 2003 media "virtual media session already exists"

Recently I've had to rebuild a 9th Gen III server (PERC6 controller) from scratch over  DRAC connection.  There are a few ways to achieve this.  The recommended way is to use the Dell installation helper CDs which have over the years gone by a few different names:
Dell Server Assistant
Installation and Server Management
System Build & Update Utility
They work by slipstreaming drivers into a Windows 2003 installation off a Windows CD or an ISO presented  over a DRAC connection virtual media session.

Unfortunately I needed to install Windows 2003 (in order to get SP1 installed).  This meant using the ISM version 5.2 and the only version that supported this was for 9th Gen I servers (with a PERC5 controller).  Booting resulted in no hard disks detected.

So the other way to get the OS installed is to boot off Windows media (or DRAC Virtual Media) and press F6 for an OEM driver disk.

The drivers are easily downloadable from the Dell drivers page - you just need the hard disk unzip package which contains the .cat, .sys, .inf and oemsetup.inf files.  These then need to be turned into a floppy image and mounted via the drac.



This is where the "virtual media session already exists" error pops up.  I'm not sure the root cause but a workaround is to use the virtual flash.

In order to do this you need to upload the floppy image to the virtual flash and enable it under the virtual media configuration tab with the tickbox.



Once this is done, you need to change the boot order to the virtual flash is higher than the physical floppy or virtual floppy.

Once you've done all this, the windows setup wizard should find the perc6 driver mapped as A: on the virtual flash when you press F6.

For this guide, I used the latest DRAC version (1.65) and the Java Virtual Media plugin.

Wednesday 7 August 2013

Dell Openmanage Essentials shows cluster name instead of hostname

When you use Openmanage to discover servers that are part of a Microsoft HA cluster, by default it will use the cluster name for the active node instead of the hostname.

To get around this, add an exclusion against the Cluster VIP and Openmanage Essentials should ignore the cluster info and just connect to the host.