vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 – Part 2
In the second post of vCenter installation on Windows Server 2012 R2 with Microsoft SQL Server 2014, I will cover vCenter Databases creation and ODBC connectivity.
In the second post of vCenter installation on Windows Server 2012 R2 with Microsoft SQL Server 2014, I will cover vCenter Databases creation and ODBC connectivity.
It has been a while since I was dealing with vCenter on SQL Server simply because I used vCenter Server appliance. In series of post, I would like to guide you through the installation of Microsoft SQL Server 2014, vCenter database creation and preparation and vCenter 5.5 Update 2 installation.
Yesterday VMware announced VMware vSphere 6 beta publicly available. In order to participate you have to follow this link on VMware Community pages https://www.vmware.com/publicbeta/VMware_vSphere.
In the second part of Auto Deploy configuration guide, we will continue with setup and we will boot ESXi.
vSphere Auto Deploy is tool released with version 5.0 of vSphere suite. It is used to deploy vSphere hosts using network boot (PXE) with DHCP and TFTP in standard and automated way. With Auto Deploy you eliminate configuration mismatch, deployment of servers is centralized and you can benefit from stateless deployment. In the first part, I will focus on installing and configuring infrastructure components - TFTP, DHCP and Auto Deploy.
In third and last part of vCenter Server 5.5 installation I will cover vCenter Server installation with all bits and pieces around it.
In the second post of vCenter 5.5 installation, I will cover following topics.
In the first post, I will show you how to install Microsoft SQL Server 2012 to use it by vCenter Server 5.5 on Windows Server 2012. Next posts will cover Databases preparation and vCenter Server 5.5 installation.
Today I was working on problem related to VMware Update Manager pointing to wrong database and I managed to find the solution to this problem.
In my case SQL server was running on Windows Server 2008 R2 so I had to check 32 bit DSN located in %SystemRoot%\syswow64\odbcad32.exe
Of course DSN was pointing to correct database on correct DB server but VUM was still not working. Also it is important to mention that two days before vCenter Server was migrated from one host to another with vCenter Server version upgrade. I knew previous SQL database names so I knew what I was looking for. On new SQL server I created new databases - the one which was VUM referring to.