Hello,
I'm trying to install vCenter with with Simple Install on a virtual Windows Server 2012 Standard instance.
But the installation totally hangs when the SQL Server 2008 R2 Setup on the vCenter Single Sign On package installs.
Installation Progress comes to: Install_sql_engine_core_inst_Cpu64_Action and has stand there for a couple of hours now and no cpu activity on that process.
I'll attach a screenshot.
Its not that bad. I did many times. You need to install what is required. Ex: SSO,Inventory Service, vCenter Server and web client is sufficient somecases.
Well, I would consider performing the following if you have an existing VC database.
- Take the DB back up file.
- Install SQL and Restore the DB on new server.
- Install VC and create ODBC links etc..
Welcome to the Communities..
First I would like to point that installing vCenter is NOT supported on running windows server 2012. These are OS which are supported for installing vCenter, Check KB1003882
Look like SQL Compatiable issue with Windows 2012
See if this helps!!
What is the version of vSphere? Is it 5.1?
Windows Server 2012 is supported for vSphere 5.1 only. http://blogs.vmware.com/guestosguide/2012/09/windows-server-2012.html
Make sure that you are running latest packages.
What is the version of vSphere? Is it 5.1?
Windows Server 2012 is supported for vSphere 5.1 only. http://blogs.vmware.com/guestosguide/2012/09/windows-server-2012.html
Make sure that you are running latest packages.
If I am not wrong the link which you have provided is for Guest OS compatiabilty and not the OS compatiabilty for installing vCenter 5.1
Hi,
The vSphere Client is 5.1.0 and the VMware ESXi is version 5.1.0 and the installation of vmWare is the following VMware-VIMSetup-all-5.1.0-947939.iso so all should be 5.1.0. And the bundled version of SQL Server should be 2008 R2 Express SP1 and according to the MS Forum Win2k12 server is supported on the SP1 of that SQL Server.
Sorry. I was wrong. They didn't include support for win 2012. I was talking about the guest OS previously which is irrelavent.
Can you try individual install instead of simple install? It might work some cases. I haven't tried installing vc 5.1 on windows server 2012 personally.
I was hoping to avoid that.
From this guide,
http://derek858.blogspot.se/2012/09/vmware-vcenter-51-installation-part-1.html
It's alot of steps for my little environment. I have a SBS 2008 running to, I could install it on that one, but i don't know for how long i should have that server, is it easy to migrate a vCenter install to another machine later?
Its not that bad. I did many times. You need to install what is required. Ex: SSO,Inventory Service, vCenter Server and web client is sufficient somecases.
Well, I would consider performing the following if you have an existing VC database.
- Take the DB back up file.
- Install SQL and Restore the DB on new server.
- Install VC and create ODBC links etc..
Rajesh Potru wrote:
Its not that bad. I did many times. You need to install what is required. Ex: SSO,Inventory Service, vCenter Server and web client is sufficient somecases.
Well, I would consider performing the following if you have an existing VC database.
- Take the DB back up file.
- Install SQL and Restore the DB on new server.
- Install VC and create ODBC links etc..
Ok, maybe I'll try such an installation tomorrow. But if you see in that guide i linked, It's stuff with OpenSSL and create certificate and stuff, can i skip that part?
Yes. You can implement installing SSL certificates later. But, i would try if the install works or not first.
is it easy to migrate a vCenter install to another machine later?
It is few steps process check Migrating vCenter Server to a different host machine which will walk through the steps to perform
Rajesh Potru wrote:
Its not that bad. I did many times. You need to install what is required. Ex: SSO,Inventory Service, vCenter Server and web client is sufficient somecases.
Well, I would consider performing the following if you have an existing VC database.
- Take the DB back up file.
- Install SQL and Restore the DB on new server.
- Install VC and create ODBC links etc..
Should i create the database "manually" so I can skip that step in the installer?
Yes. You can install the DB manually and point to the existing database and provide credentials during the setup.
Rajesh Potru wrote:
Its not that bad. I did many times. You need to install what is required. Ex: SSO,Inventory Service, vCenter Server and web client is sufficient somecases.
Well, I would consider performing the following if you have an existing VC database.
- Take the DB back up file.
- Install SQL and Restore the DB on new server.
- Install VC and create ODBC links etc..
I did It this way and all working good, but the server is a bit slow now, think i need to install more RAM... :smileysilly:
Glad It worked without any issues