Asked By
Darren123
200 points
N/A
Posted on - 06/22/2011
Hi,
I have tried without success to install VMware vCenter server on Windows Server 2008 R2 Enterprise for some time now. The installation process has been giving me issues and I don’t have an idea how to solve them. The first issue I encountered was, during the installation where an error screen popped up halfway during the installation saying;
“VMware vCenter Server
Error 28035.Setup failed to copy DSACLS.EXE from System folder to ‘%windir%ADAM’ folder.”
After some research around the issue in the internet, I learnt that I had to install the .Net framework 3.5.1 features. So I downloaded it from the internet and installed it, but now a new issue has arisen where it tells me to use the Role Management Tool to enable .Net Framework 3.5.1 on Windows Server 2008 R2. Does anyone have an idea about this issue? Please help me out.
Thank you.
Answered By
Scot1984
15 points
N/A
#129036
Problem installing vCenter on Windows server 2008 R2
This issue can safely figure it out and its know issue. If you determine well the on the prerequisites it the technology and the components the checklist. You can successfully install the vCenter on Windows Server 2008 R2
Just check the below information…
· 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.
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!