CTS2370C – Virtual Infrastructure: Installation and Configuration is a 3-credit course on server virtualization: installing, configuring, and managing a hypervisor-based virtual infrastructure, typically VMware vSphere. The C suffix reflects a required laboratory, which is where the entire course actually happens.
Virtualization is the technology the modern data center is built on, and understanding it explains a great deal else. Before it, one physical server ran one operating system and one workload, at perhaps ten percent utilization. A hypervisor abstracts the hardware so that many virtual machines share one physical host — which consolidates hardware, makes machines portable, and makes possible the features that follow from portability: live migration, high availability, snapshots, and rapid provisioning. Cloud computing is virtualization plus automation plus a billing system.
Content covers virtualization concepts — hypervisor types, the virtual machine abstraction, and the business case; installation — deploying the hypervisor to physical hosts and the management server; virtual machines — creation, hardware configuration, guest tools, templates, cloning, and snapshots; virtual networking — standard and distributed switches, port groups, VLANs, uplinks, and network policies; storage — datastores, block and file protocols, iSCSI and NFS, multipathing, and storage policies; resource management — CPU and memory allocation, shares, reservations, limits, and resource pools; availability and mobility — live migration, high availability clustering, fault tolerance, and load balancing; access control — roles, permissions, and integration with directory services; backup and recovery; monitoring and performance — metrics, alarms, and troubleshooting resource contention; updates and lifecycle; and the relationship to containers and cloud.
Offered at Florida institutions with network and systems technology programs.
Florida's demand concentrates in Tampa, Orlando, Miami, and Jacksonville, with substantial employment in managed service providers, health systems, financial services, government, universities, and the defense and simulation sector in Central Florida. Data center construction in the state has grown markedly. Much of this work is also partly remote-eligible, though data center roles generally are not.
Another instance of the pattern worth checking before registering. The same number runs at 3 credits (Seminole State, Eastern Florida State) and 4 credits (Florida State College at Jacksonville, which also requires CTS1334C with a C or higher), and the title shifts with the emphasis: "Virtual Infrastructure: Installation and Configuration" at most institutions, "Virtual Infrastructure — Planning and Design" at Eastern Florida State, which is a meaningfully different course. SCNS equivalency applies to the same number at the same level, never across numbers — the number transfers, the credit value and emphasis may not. Read your own institution's description and prerequisite.
The most actionable advice attached to this course. Virtualization cannot be learned from reading, and classroom lab time is limited and shared. A personal lab lets you break things, which is where the learning happens.
Three practical routes, in increasing order of cost. Nested virtualization — run hypervisors as virtual machines on a single workstation; this works for most concepts and costs nothing but RAM. Free hypervisors — Proxmox VE, XCP-ng, or Hyper-V run real workloads with no licensing cost and teach the same concepts vSphere does. Used enterprise hardware — older servers are inexpensive on the secondary market, though they are loud and use real electricity.
The constraint is almost always RAM: 32 GB is a workable minimum for a nested lab and 64 GB is comfortable. And say the lab out loud in interviews — a candidate who can describe what they built, what broke, and how they fixed it is markedly more convincing than one reciting features.
The single most common and most damaging misunderstanding in virtualization administration, and worth learning correctly the first time. A snapshot preserves a point in time by writing all subsequent changes to a delta file, leaving the original disk frozen. It is designed as a short-term safety net — take one before a patch, remove it after verifying.
What goes wrong: snapshots left in place grow continuously, sometimes to the size of the original disk or larger; performance degrades as the delta chain lengthens; consolidating a large old snapshot can take hours and requires the datastore to have room; and a full datastore stops every virtual machine on it. Administrators have caused production outages this way, and it is a recurring finding in environment health checks.
The rules: snapshots are temporary, they are not backups (they live on the same storage and depend on the original disk), monitor for old ones, and take a real backup before anything consequential.
A concept that separates an administrator from an operator. Hypervisors allow allocating more virtual resources than physically exist, on the sound assumption that not every workload peaks simultaneously. That overcommitment is much of the economic case for virtualization.
It also has limits, and the failure modes differ by resource. CPU overcommitment produces scheduling contention — measured as ready time — where machines wait for physical cores. Memory is less forgiving: when hosts run short, reclamation techniques such as ballooning and ultimately swapping engage, and swapping degrades performance severely. Storage overcommitment through thin provisioning risks the datastore filling.
The practical skill is diagnosing which resource is actually constrained rather than adding CPU to a machine that is memory-starved — which is what inexperienced administrators do. Learn the metrics that distinguish them; this is exactly what a troubleshooting interview question tests.
Practical career guidance with a caveat. VMware certifications — VCTA at entry level and VCP as the recognized professional credential — are well regarded by employers. The VCP has historically required an official training course in addition to the exam, which is a real cost, so check the current requirement and ask whether your institution is an authorized academic partner, which can substantially reduce it.
Note also that the VMware product and licensing landscape has changed significantly since the Broadcom acquisition, with consequences for pricing and for which editions organizations run. Some employers have begun evaluating alternatives such as Proxmox, Hyper-V, and Nutanix. The concepts in this course transfer across all of them, which is the argument for learning the principles rather than one vendor's menus — and it is worth being able to discuss the alternatives in an interview.
Worth understanding as career context. Every major cloud provider runs virtualization underneath: an EC2 instance or an Azure VM is a virtual machine on a hypervisor in someone else's data center. A student who understands hypervisors, virtual networking, and shared storage learns cloud platforms substantially faster, because the concepts are the same with different names and a billing meter attached.
The practical pairing is with CTS2375C Cloud+ and with Linux administration (CTS2321C). Virtualization plus Linux plus some scripting is a strong and durable combination in the Florida infrastructure job market, and it is the standard route into the better-paid platform and reliability engineering roles.
Generated September 1, 2026 · Updated September 1, 2026