While performing some troubleshooting with a client a few weeks ago on their vCenter 4.1 server, I learned that vCenter 4.1 actually uses a 64-bit DSN. This meant that we no longer have to go into:
- Install the 32-bit client via Microsoft’s downloads
- Run 32-bit ODBC via the WoW64 folder
- Create a 32-bit DSN
…which you had to do for a vCenter 4.0 install.
The following is the difference between the 2 version’s:
vCenter 4.0
Database Options
Select an ODBC data source for vCenter Server.
vCenter Server requires a database.
Use an existing supported database
Data Source Name (DSN): (Please create a 32-bit system (DSN)
vCenter 4.1
Database Options
Select an ODBC data source for vCenter Server.
vCenter Server requires a database.
Use an existing supported database
Data Source Name (DSN): (Please create a 64-bit system (DSN)
Now I’m just waiting for VUM (Update Manager) 4.1 to support a 64-bit ODBC DSN because it’s currently still a requirement for it to be installed on a 64-bit Operating System yet use a 32-bit DSN.
Update
The following might be helpful when configuring the 64-bit DSN:
Make sure you select SQL Server Native Client 10.0 for the System DSN and not the regular SQL Server or the vCenter installation wizard won’t detect it (you can’t just hit the back button then forward again to see the DSN).
No comments:
Post a Comment