So, ladies and gents,
it's up to me to go to vSphere 4.1, now. While reading through the documentation I found that:
Create a 64-Bit DSN
The vCenter Server system must have a 64-bit DSN. This requirement applies to all supported databases. By default, any DSN created on a 64-bit system is 64 bit.
Procedure
1. Install the 64-bit database ODBC drivers on your Microsoft Windows system.
The default installation location is C:\Program Files\VMware\Infrastructure\VirtualCenter Server.
2. Click Control Panel > Administrative Tools > Data Sources (ODBC).
3. Use the application to create a system DSN and test the connectivity.
The system now has a DSN that is compatible with vCenter Server. When the vCenter Server installer prompts you for a DSN, select the 64-bit DSN.
(http://pubs.vmware.com/vsphere-esxi-4-1-installable/wwhelp/wwhimpl/js/html/wwhelp.htm#href=setup_guide/t_create_a_32-bit_dsn_on_a_64-bit_operating_system.html)
Creating a 64 bit DSN is called a requirement, here. But a) it is stated that a DSN created on a 64 bit system is by default a 64 bit DSN, however, I should install the 64 bit drivers before and b) I can find the drivers in the vCenter installation folder but that doesn't exist before I install the vCenter Server (which needs a 64 bit DSN for installation).
Sounds like a dead lock to me....especially because if I create a DSN on that 64 bit 2008 R2 server it uses a 32 bit DLL and is not accepted by the VMware installer.
AWo
AWo
VCP 3 & 4
\[:o]===\[o:]
=Would you like to have this posting as a ringtone on your cell phone?=
=Send "Posting" to 911 for only $999999,99!=
Hello Andreas.
When using a full SQL Server (not Express), I install the SQL Native Client on the vCenter server first, then create the 64-bit DSN and finally run the vCenter installer.
Good Luck!
I didn't face any problem, I just saw this part of the documentation and IMHO it is missleading. Or do I understand that section wrong?
AWo
VCP 3 & 4
\[:o]===\[o:]
=Would you like to have this posting as a ringtone on your cell phone?=
=Send "Posting" to 911 for only $999999,99!=
It does sound a little confusing. To be honest I don't remember seeing #1 at all when I did my migration to X64 on a new build. Of course I could have just read it and skipped.
If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points
Twitter: http://twitter.com/mittim12
IMHO it is missleading.
Totally agree.