Welcome to a new series of articles I will be dedicating to VMware and in particular to installing, configuring and managing VMware vSphere environments. We’ll start with VMware vCenter deploy on Windows Server paired with a SQL Cluster. Ideally an easy to follow guide about vSphere deployments to explore about functionalities and learn more about managing our Virtual Data Centers in our testing and production environments. So first things first we start off by running VMware vCenter on a Windows Server.
In this instance I will be using an “Embedded Deployment” of VMware vCenter where essentially the two major components the “Platform Service Controller” and the “vCenter Server” are sitting on the same Host. This is indicated for small environments and up to 100 VMs are supported which is perfect for my home lab. For larger environments it is possible to decouple these two components allowing for a more resilient deployment of the vCenter infrastructure. I’m planning on dedicating a different post on this very topic. For now one Host with one single vCenter server is what we need to start building our virtual data center.
Before proceeding with the vCenter setup it is important to review and satisfy the following prerequisites:
- Host with at least 2 CPUs and 8GB RAM (valid on both Virtual or Physical Hosts)
- If using a dedicated Service Account to run vCenter make sure it has the “LogOn as Service” permission granted
- If using an external Database as repository (in our case we point to a SQL FCI Cluster with AAG ) create a System DSN
- Manually create a Database for vCenter to host the necessary information
VMware vCenter deploy on Windows prerequisites
During the phaseof VMware vCenter deploy on Windows Server the wizard will offer the option to either use the logged in user (local Windows user) running the installation or specify an alternative one. With a local user we cannot point to an external database which is in our case SQL. The local user can only connect to the built-in Database based on Postgres.
For our purpose since we are pointing to an external Database instead of using the built-in Database we can specify an intended Service Account for the purpose and we need to make sure this particular user has the “LogOn as a Service” permission granted in the User Rights Assignments on the local Host. The quickest way would be to issue the following command:
then navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignments > Log on as a service and add the intended Service Account.
SQL 2012 Native Client 64Bit
At this point another prerequisites to satisfy is the creation of a System DSN that will help vCenter connecting with the SQL Server and locate the right Database. In my case I have a SQL 2014 Cluster which does not include the SQL Native Client component. What we can do is to install the equivalent one for the previous version SQL 2012 on the Host where the vCenter Server will be installed. It’s a small msi that can be downloaded directly from here under the section Microsoft® SQL Server® 2012 Native Client. The general link is the one below:
The installation is pretty easy and quick as per screenshots below.
From the list of components it is sufficient to pick the Client ones.
As an extra step now let’s create a Database for vCenter in the intended SQL instance. I have just called mine “VMware_vCenter”
At this point we are ready to satisfy our System DSN requirement by creating the connection string. Let’s navigate to the Control Panel > Administrative Tools > ODBC Data Source 64-Bit and click on System DSN and finally Add..
Let’s take advantage of the SQL Server Native client 11.0 installation..
In my case I’m just calling this ODBC connection string “vCenter”. In the Server field specify the full SQL Server instance name where the intended Database for vCenter is located.
Since Integrated Windows authentication will be used the creation of an Service Principal Name (SPN) is optional.
Change the default Database to connect to. In my example I did create a Database called “VMware_vCenter”.
Let’s leave everything by default as per screenshot below.
Before finishing let’s do a quick test to verify the connection to the Database. Failing this the VMware vCenter deploy wizard will fail.
Verify settings and test connection just to make sure the networking side of things is working as expected.
Installing VMware vCenter will be a breeze. Let’s mount the ISO and click on the autorun and follow the wizard.
Let’s accept the license and continue.
At this point let’s choose how to progress with VMware vCenter deploy on Windows Server. In this case we’ll go for an embedded installation where the VMware Platform Services Controller (PSC) and the vCenter Server will sit on the same Host. In the future there will be more dedicated articles covering the topics related to VMware vCenter components and their installations for scale out deployments.
By default this should the FQDN name of the Host where vCenter is going to be installed. Make sure to DNS forward/reverse queries are working. A quick way of checking this would be issuing the following command:
“nslookup -nosearch -nodefname your_vCenter_Server_FQDN”
At this point in time we are not using IPv6 so we can ignore this message.
Since this is the first installation we need to create a new Single Sign-On (SSO) domain in VMware vCenter. It is better be carefull on the name we choose because it is very difficult to change this one later on.
Specify the intended Service Account to run the vCenter with the “LogOn as a Service” permission granted.
We can now select the ODBC connection string created beforehand in the System DSN.
And now a final review of the ports will be used by vCenter. I did change mine for HTTPS to 8443.
I prefer to use a separate drive for the application installation.
Additionally we can also opt in for the VMware Customer Experience Improvement Program.
And now with the final settings review we should get something similar to this.
The installation doesn’t really take that long and if everything went fine we are greeted with setup completed message like the one in the screenshot below.
And here we are with the vSphere Web Client console.