Archive for March, 2010
Just a quick note about the new Microsoft desktop licensing for virtual desktops that I blatantly copied from here but wanted to post so I would remember.
- PCs covered under SA will no longer need a separate VECD license, instead this usage right will be included in SA thus eliminating the separate $23 per device fee.
- PCs not covered under SA, thin clients or other clients that cannot run a full Windows OS, customers can purchase VDA for $100 per device/year, a $10 decrease from the previous VECD license price.
- Roaming use rights allows users to be able to access their virtual desktops from secondary devices like home PCS, kiosks and internet cafes without additional licensing costs.
There are a couple of small gotchas to be aware of when installing vCenter on a Windows 2008 R2. The main reason for this is that R2 is 64-bit only. The issues arn’t with the installation of vCenter as much as issues with getting the installation to recognise the connection to the SQL backend server.
vCenter requires a 32-bit DSN. The problem on R2 is that if you setup a DSN through Start > Administrative Tools > Data Sources (ODBC) the vSphere installer won’t be able to see it as the created DSN will be a 64-bit connection.
In addition to a 32-bit DSN vCenter also requires the SQL (2005 or 2008) native client. The confusing part is you need to download and install the 64x version of the native client and then use the procedure below to setup the connection.
So here is a quick guide on installing vCenter 4.0 on a Windows 2008 R2 server.
- Download the native client from the above link
- Install the SQL 2008 native client with default settings
- From the run command – %systemdrive%\Windows\SysWoW64\Odbcad32.exe
- Select the System DSN Tab
- Choose the Native SQL Client
- Run through the rest of the setup of the DSN connection as normal.
- Run the vCenter installation as normal and the installation program should show you DSN as a Database connection option.
Note – If you go back to Start > Administrative Tools > Data Sources (ODBC) no DSN’s will appear. This is normal as they have been created using the 32-bit tool and so will only show up when you launch it from %systemdrive%\Windows\SysWoW64\Odbcad32.exe
Quick guide on installing the HP ESXi CIM providers
- Download the HP ESXi Offine bundle (Zip File)
- Vmware vSphere CLI
Note – Bold text should be replace with relevant information.
- Copy bundle to c:\temp
- Place the target host in maintenance mode
- Open the vsphere CLI command line
- Change to bin directory by typing CD bin
- Run vihostupdate.pl –server ESXiHOST –install –bundle c:/temp/bundle.zip
- Reboot the host
- Check it installation – Run vihostupdate.pl –server ESXiHOST –query
You should now have additional information on hardware status in the vSphere hardware status tab.