Replicating VMware vSphere Configuration Profile Desired State
Source: VMware Blog
# vSphere Configuration Profiles
vSphere Configuration Profiles allow VMware Cloud Foundation (VCF) administrators to manage the ESX host configuration at a cluster level. In this article, we discuss how to easily replicate configuration from one cluster to another.
> **Note:** Screenshots and steps described are based on vSphere **9.0.2**. Certain UI elements or verbiage may differ in earlier or later versions.About vSphere Configuration Profiles
vSphere Configuration Profiles is a new feature introduced in vSphere 8.0 that supersedes Host Profiles for managing ESXi host configurations at scale.
Why it matters
| Host Profiles | vSphere Configuration Profiles |
|---|---|
| Requires the entire host configuration to be specified | Only the desired changes to the default configuration need to be defined |
| Complex and hard to maintain | Human‑readable, concise, and easier to manage |
| Increases administrative overhead | Reduces the burden on administrators, allowing them to focus on the specific changes they want to make |
In short, vSphere Configuration Profiles let administrators define only the modifications they need, making the configuration document far more readable and maintainable.
Replicating Configuration to New Clusters
A common use case in configuration management is keeping consistent configuration not only within a vSphere cluster but also across multiple clusters. vSphere Configuration Profiles makes this straightforward.
Tip: You can stage configuration to a cluster even before any ESXi hosts have been added. All you need are the hosts’ BIOS UUIDs.
1. Export Configuration from an Existing Cluster
- Navigate to Cluster > Configure > Configuration under Desired State.
- Export the configuration. The file is JSON‑formatted and contains:
- Agnostic settings (e.g., vSphere Distributed Switch, port groups, datastores)
- Host‑specific attributes (IP address, hostname, BIOS UUID)
Note: You will later edit the host‑specific section with the UUIDs and attributes of the destination cluster.
2. Edit the vSphere Configuration Profile JSON File
JSON structure overview
Below is a simplified view of a typical vSphere Configuration Profile JSON file (opened in Notepad++). Most details are collapsed for readability.
{
"profile": {
"esx": { … } // Host‑agnostic settings
},
"hosts": {
"": { … }, // Host‑specific settings
"": { … },
"": { … }
}
}profile.esx– Settings applied to every host (e.g., distributed switch, port groups, datastores).hosts– Host‑specific section where you’ll replace UUIDs, IPs, subnet masks, and hostnames.
Retrieve Host UUIDs (BIOS UUIDs)
The easiest way to obtain a host’s UUID is with PowerCLI:
# Replace esx-hostname.fqdn with the actual host FQDN
(Get-VMHost -Name esx-hostname.fqdn).ExtensionData.Hardware.SystemInfo.UuidUpdate the JSON file
- Replace each Host UUID with the UUID of the destination host.
- Update IP address(es), subnet mask(s), and hostname as required.
- Add or remove host entries as needed—just keep the JSON syntax valid (pay attention to commas).
3. Import the Updated Configuration to the New Cluster
If the cluster is not yet enabled for vSphere Configuration Profiles
- Use the transition workflow to enable the feature.
- Import the edited JSON file during the transition.
If the cluster is already enabled
Go to the Draft tab of the cluster.
Click Import From File and select the updated JSON file.
Review the pre‑check, remediation settings, and impact:
- Pre‑check – Verifies that each host can enter maintenance mode and that DRS is enabled for VM evacuation.
- Remediation Settings – Shows the settings inherited from vSphere Lifecycle Manager.
Expand each host under Host‑Level Details in the Review Impact window to see the exact changes that will be applied.
Click Remediate to apply the configuration to the cluster.
Quick Reference Checklist
| Step | Action | Details |
|---|---|---|
| Export | Export JSON from source cluster | Cluster > Configure > Configuration > Desired State |
| Gather UUIDs | Retrieve BIOS UUIDs for destination hosts | PowerCLI command above |
| Edit JSON | Update host‑specific section | UUID, IP, subnet, hostname |
| Import | Import JSON into target cluster | Draft tab → Import From File |
| Validate | Run pre‑check & review impact | Ensure maintenance mode & DRS are ready |
| Remediate | Apply configuration | Click Remediate |
Additional Resources
Feel free to reach out on the VMware community forums if you encounter any issues during the transition. Happy configuring!
Summary
We can easily copy standard configuration from one cluster to another using vSphere Configuration Profiles. This helps ensure consistent configuration not only within a single cluster but also across multiple clusters.
Discover more from the VMware Cloud Foundation (VCF) Blog
[Subscribe] to receive the latest posts directly to your email.