RSS .92| RSS 2.0| ATOM 0.3
  • Home

    vCloud Director not generating discreet BIOS UUID by default

    November 14th, 2012

    vCloud Director in the 1.x series does not generate discreet BIOS UUID by default.  This item is documented in two KB’s that I was able to find:

    Prior to running the SQL statement, which must be run against the vCloud Database, dbo.config table (which is not really clearly mentioned), all VM’s deployed in a vApp do not get the discreet BIOS UUID, and at least in the case of Windows 2008, all machines will than generate the same OS GUID.  This may or may not be bad depending on your circumstances.

    You can look at the .vmx of each machine to determine if the BIOS UUID is the same, or run two quick PowerShell commands:

    To show the BIOS UUID inside Windows 2008 guest OS:

    get-wmiobject win32_computersystemproduct

    To show the Windows UUID, run:

    get-wmiobject win32_computersystemproduct |select-object -expandproperty uuid

    When we conducted the change, I shut down the cell to guarantee there were no writes to the database from vCD’s perspective.  We ran the SQL statement, started the cell and deployed new machines.  Each one had a new BIOS UUID and Windows GUID.

    OS X, VMware Fusion, Apple Bootcamp

    August 27th, 2010

    I have been an Apple convert since the second generation iPod and eventually moved to a MacBook Pro over a year ago.  I have been using VMware Fusion on OS X ever since, and it is frankly a “killer app.”  I recently played with Bootcamp to dual boot in to Windows 7.

    Fusion provides the bells and whistles found in VMware Workstation, including Unity mode.   Unity presents your guest OS applications with the look and feel of OS X apps.  All of your app windows are integrated and can be independently min/maximized.  Brilliant.

    Fusion really shines when Bootcamp is employed.  Bootcamp is Apple’s instantiation of multi-boot, and frankly works well.  Fusion will automagically detect a Bootcamp-based OS, in my case Windows 7, and make it available to launch.  There is no need to conduct the import; the machine is simply listed in available machines.  At first run, Fusion will install tools and prep the guest OS to run virtualized hardware.  Booting the OS via Bootcamp will allow the OS to still run on the bare-metal.

    There have been blog posts, and a VMware KB, outlining the requirement to license Windows 7 in bare-metal mode, and then virtualized via Fusion, due to the fact the underlying hardware has technically changed (bare vs virtualized), however I was not prompted.