Step‑by‑Step Guide to Building a VMware ESXi & vCenter Lab with SQL Server
This tutorial walks you through creating a virtual lab by setting up ESXi hosts, configuring a Windows Server domain controller, installing vCenter Server, deploying the vSphere Web Client, and adding SQL Server services, complete with detailed screenshots and troubleshooting tips.
Topology Overview
Device List
PC1 – ESXi – IP 192.168.0.120
PC2 – ESXi – IP 192.168.0.121
PC3 – Windows Server 2012 (Domain Controller) – IP 192.168.0.130
PC4 – Windows Server 2012 (vCenter) – IP 192.168.0.131
PC5 – Windows Server 2012 (SQL Server 2012) – IP 192.168.0.132
PC6 – Windows 7 (Vsphere) – IP 192.168.0.133
Installation Steps
Install ESXi on PC1 and PC2. Use Workstation 10.0, allocate at least 4 GB RAM, and create a 40 GB virtual disk.
Configure the management network on each ESXi host, set passwords, and verify network connectivity.
Install VMware vSphere Client on a physical machine, connect to the ESXi hosts, and add the hosts to the inventory.
On PC3, install Windows Server 2012, promote it to a domain controller, and set the domain name.
On PC4, install vCenter Server: run the installer, accept defaults, provide the trial license, choose the existing SQL Server database, and configure the SSO credentials (e.g., asd.1234).
On PC5, install SQL Server 2012: mount the ISO, run the setup, select default features, configure mixed‑mode authentication, create a database named sqlserver, and enable the SQL Server Agent service.
On PC6, install Windows 7, join it to the domain, mount the vCenter installation media, and run the vSphere Client installer.
After installation, verify that all services (ESXi, vCenter, SQL Server, domain controller) are running and that the vSphere Web Client can be accessed via HTTPS.
Common Issues & Solutions
Missing Microsoft Visual J# – install the component to resolve vSphere log errors.
Domain join failures – set the client DNS to the domain controller’s IP.
Web Client not loading – use a browser with Flash support and include the correct port in the URL.
SQL Server connection problems – restart the SQL service, ensure the correct server name, and disable the firewall.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Ops Development Stories
Maintained by a like‑minded team, covering both operations and development. Topics span Linux ops, DevOps toolchain, Kubernetes containerization, monitoring, log collection, network security, and Python or Go development. Team members: Qiao Ke, wanger, Dong Ge, Su Xin, Hua Zai, Zheng Ge, Teacher Xia.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.