Windows Server

Installing VMware vCenter prerequisites on Windows Server 2008 R2

Scott Lowe explains how to prepare a Windows Server 2008 R2 server for VMware vCenter and how to tackle two problems that are sure to arise during the installation process.

With Windows Server 2008 R2, Microsoft has finally abandoned the 32-bit world in server land in favor of a 64-bit only operating system. While this is a very good step in the right direction toward solving the 32-bit/64-bit selection dilemma, it can present some installation challenges.

I recently encountered this issue when our organization installed VMware vCenter Server on Windows Server 2008 R2. With older versions of Windows, there is a 32-bit option, so vCenter has no trouble installing; however, once things move in the 64-bit direction, there are two items that you'll need to address before the vCenter installation will be successful:

  • The need for the .NET Framework 3.5.1.
  • The need for a 32-bit Database Source Name (DSN)/ODBC connection pointing to the vCenter database.

I'll outline tips that will help you with the installation process.

Important notes

Before we proceed, you should be aware of these important product and article notes:

  • Although VMware indicates that small organizations can safely run vCenter on a 32-bit OS, it recommends that administrators consider 64-bits for all new installations.
  • If you're installing vCenter on a virtual machine running under vSphere/ESX 4, you should know that support for Windows Server 2008 R2 is currently experimental. Even though everything will probably work just fine, VMware won't provide support if you have problems.
  • This article assumes that you have already followed VMware's guidance as outlined in the documentation and created a database and database user for vCenter. For my purposes, I created a database named VCDB and a SQL Server account named vcenteruser.
  • Bear in mind that VMware does not yet support vCenter on Windows Server 2008 R2. Proceed at your own risk!

.NET Framework 3.5.1

To install the .NET Framework 3.5.1 on Windows Server 2008 R2, follow these steps:

  1. Open Server Manager.
  2. Select the Features navigation item.
  3. On the Feature Summary page, click Add Features.
  4. When you get to the Select Features page of the wizard, expand the .NET Framework 3.5.1 Features option.
  5. Select the .NET Framework 3.5.1 item. (Do not choose to install both the .NET Framework 3.5.1 and WCF Activation together -- doing so will force the installation of IIS 7.5, which will interfere with vCenter's Web services.) Figure A shows you the Select Features window.
  6. Click the Next button.
  7. On the Confirm Installation Selections page, click the Install button to complete the process.

Figure A

32-bit DSN to the vCenter database

When you create a DSN on an out-of-the-box Windows Server 2008 R2 system, the DSN is created as a 64-bit object, whereas the vCenter installer will only be looking for 32-bit DSNs. In order to create a 32-bit DSN on your 64-bit Windows Server 2008 R2 server, you need to download and install the SQL Server Native Client on your server and use the new client's utilities to create the DSN. For this article, I'm using SQL Server 2005 because that is what we're using in production at Westminster College.

The SQL Server Native Client is included as a part of the SQL Server 2005 Feature Pack. From the Feature Pack download page, download the X64 package under the SQL Server 2005 Native Client option. Although you're installing the 64-bit package, this is only because you're installing the tool to a 64-bit operating system; the package includes a method to create 32-bit DSNs. Once you download the package, install it.

Next, go to Start and, in the Search box, type odbcad32. Select the odbcad32 option under the Programs heading to run this utility.

Figure B

This is a 32-bit version of the ODBC Data Source Administrator utility; in this utility, create a System DSN that points to your vCenter database. To do so, follow these steps:

  1. Select the System DSN tab.
  2. Click the Add button.
  3. On the first page of the Create New Data Source wizard, choose SQL Native Client.
  4. When prompted, provide a name and description of the new System DSN and indicate on which SQL Server the vCenter database resides.
  5. For my example, I've used SQL Server authentication. On the authentication page, choose the authentication method most appropriate for your use. If you use SQL Server authentication, use the same login ID and password that you created as per the VMware documentation. This page is shown in Figure C.
  6. When prompted, test the data source to make sure it's set up properly.

Figure C

When you're done, you will see the vCenter DSN appear in the ODBC Data Source Administrator.

Summary

With these two items in place, your vCenter installation should proceed without interruption. The true test will come when you get to the installation step that asks you to provide the 32-bit DSN that you want to use for the vCenter database. If you've set the DSN up properly that DSN will be available to you; if it's not set up properly, make sure that you didn't accidentally create a 64-bit DSN.

Want to keep up with Scott Lowe's posts on TechRepublic?

About

Since 1994, Scott Lowe has been providing technology solutions to a variety of organizations. After spending 10 years in multiple CIO roles, Scott is now an independent consultant, blogger, author, owner of The 1610 Group, and a Senior IT Executive w...

10 comments
Habbass
Habbass

Ever heard of c:\windows\syswow64\odbcad32.exe. This is different than start run odbcad32. Only the first option creates the DB as a proper 32 bit DSN. Regards Richie 0884641688

ctroup
ctroup

It is important to use the correct version of odbcad32.exe. Start -> Run -> odbcad32.exe is the WRONG one. Use this one instead %systemdrive%\Windows\SysWoW64\Odbcad32.exe. Also be sure to select the Native Client option.

cjones
cjones

I recently moved our vCenter to a Windows 2003 x54 VM running on one of our ESXi Clusters, for the added High Availability that the cluster provides. I ran into the same issue with the DSN and it took several attempts and a lot of google searching to find the answers you've just mentioned. It would be nice if VMware actually told you are this little issue, and it's also strange that they do recommend using a 64-bit OS, but can't recognise a 64-bit DSN. Also, with vCenter 4.0 Update 1 and ESX 4.0 Update 1, Windows 2008 R2 is now officially supported so as long as you are using this version you shouldn't have to worry about not getting support from VMware.

jamiepederson1
jamiepederson1

I think it is up to the individual engineer to determine what is and what isn?t supported by doing the necessary reviews of white papers, etc prior to implementation. Therefore there is no such thing as being mislead if you are doing your job properly. I would not view this article as misleading; I view this article as informative and a work around to continue to work with bleeding edge technology. Thanks for the useful information :)

Scott Lowe
Scott Lowe

I don't think I'm misleading anyone here... I clearly stated that R2 support under ESX itself was experimental and did not recommend anywhere here that people deploy vCenter to R2. Remember, it's only a matter of time before R2 *is* supported and there are bleeding edge people out there trying to do this now that need some assistance in getting it to work.

jason
jason

I think you are confused. VMware added 2008 R2 and Windows 7 support as guest VMs, but they did not add 2008 R2 as a supported platform for vCenter Server.

Kevin.Allaway
Kevin.Allaway

2008 R2 has been supported by vSphere in the latest patch release of 19/11/2009 build 4.0.0,208111 of vCenter and 4.0.0,208167 of ESX

Editor's Picks