Automated VMware Cloud Foundation Lab (VCF) 9.x Fleet Deployment

Description

This script makes it very easy for anyone to deploy a "basic" VMware Cloud Foundation (VCF) 9.x Fleet OR VMware vSphere Foundation (VVF) in a Nested Lab environment for learning and educational purposes.

Changelog

08/13/2026
- Related Blog Post
- Added in sample-abbed-vcf-9.0.2-vlan.ps1 variable $VCFWorkloadDomainVCSASSODomainName replaced hardcoded "vsphere.local" to allow Isolated Workload Domain
- Added in vcf-automated-wld-vlan-deployment-9.0.ps1 VM_MANAGEMENT DVPG for NSX Edge VMs and all VMs inside Workload Domain
```
								@{  
                                    "name" = "${VCFWorkloadDomainVCSAClusterName}-vds01-vm-management"  
                                    "transportType" = "VM_MANAGEMENT"  
								}  
```
  - Note This portgroup after Workload Domain creation should be created manually (from the workbook notes), but since we include it in the json, we only to have change manually its VLAN on VDS DVPG (to 1310 in this case which is set as $NestedVMNetworkWldVLanId at deployment).
- Added $setupEntropy for optimization in Nested ESX VMs https://williamlam.com/2026/04/quick-tip-high-cpu-utilization-on-esx-due-to-slow-entropy-from-amd-zen-4-cpus.html
- reusing Lab vApp Deployment ID ($random_string value) for Day-2 Workload Domain deployment
05/24/2026
- Related Blog Post
- Created vlan branch of this fork to avoid PR merge conflict
- Updated to support VLAN for VCF 9.1
- For VVF/VCF 9.0.x VLAN deployments, please use VCF 9.0 directory
- VLANs with reference taken from new vcf-9.1-planning-and-preparation-workbook.xlsx
- Using 4 nested ESX, using even number nested host here to spread the load on even physical host (I am still using 2 physical host 24threads 128GB of RAM each)
- Using Minimal VM resources $noVCFAutomation = 1, $NestedESXiMGMTvCPU = "20", $NestedESXiMGMTvMEM = "56" #GB, (80vCPU 224GBvMEM) x 80 / 100 = 64vCPU 179vMEM as shown in the UI the recommended much needed extra 20%
- Offline Depot Configurations (optional) keeping 9.0 config logic with https workaround $VCFInstallerDepotHttps = $false
- VVF 9.1 VLAN and VCF 9.1 WLD VLAN not yet present in this commit, notably $VCSASize cannot be Tiny much less further reducing Memory workaound haven't tested, similarly $VCFOperationsSize cannot be xsmall
- Related Blog Post with Kubernetes troubleshooting and workaround (typical Platform Engineering tasks from my experiences), in case it get stuck for more than an hour, to complete the deployment successfully...
05/12/2026
- Updated to support VVF/VCF 9.1
- For VVF/VCF 9.0.x deployments, please use VCF 9.0 directory
01/04/2026
- Related Blog Post
- Fixed shared storage datastore
- Added EVC variable if needed: $VCSAclusterEvcMode = "" #One among: INTEL_MEROM, INTEL_PENRYN, INTEL_NEALEM, INTEL_WESTMERE, INTEL_SANDYBRIDGE, INTEL_IVYBRIDGE, INTEL_HASWELL, INTEL_BROADWELL, INTEL_SKYLAKE, INTEL_CASCADELAKE, INTEL_ICELAKE, INTEL_SAPPHIRERAPIDS, AMD_REV_E, AMD_REV_F, AMD_GREYHOUND_NO3DNOW, AMD_GREYHOUND, AMD_BULLDOZER, AMD_PILEDRIVER, AMD_STREAMROLLER, AMD_ZEN, AMD_ZEN2, AMD_ZEN3, AMD_ZEN4
- Added comment on variable $NestedESXiMGMTvMEM: Tips: 122GB for VCF single node with Wld VMs or 114GB for 2 nodes and with VCF automation enabled "$noVCFAutomation = 0" in sample but without Wld VMs "$deployNestedESXiVMsForWLD = 0" in deployment script
27/03/2026
- Related Blog Post
- VLANs with reference taken from vcf-9.0-planning-and-preparation-workbook.xlsx
- Gateways
- Network subnets
- Added separate datastore for Management Domain and Workload Domain, also using local vmfs
- Added variable $VCFWorkloadDomainNSXManagerSize = "small"
- Added creation of network pool for VSAN and VMOTION on Workload Domain based on network subnets
- Added variables $VCFInstallerVMvCPU and $VCFInstallerVMvMEM of VCF Installer VM, reducing by half from 4vCPU+16GBvMEM to 2vCPU+8GBvMEM
- Added variables $vGuestOS and $vHardwareVersion of vESXi VMs, increasing it from vmkernel8Guest+vmx-20 to vmkernel9Guest+vmx-22 default vmx-20, vmx-21 nvme 1.3c, vmx-22 nvme 1.4 ref.
- Added variable $noVCFAutomation to skip it in the deployment by setting it to 1 (default reducing by 24vCPU+96vMEM less the lab footprint)
- Added missing variables under "VCF Installer Setup" to allow 1 host VSAN cluster and, help in VSAN ESA deployment usecase, the code was already present
- Added check if vApp exist to run the script multiple times on the same vApp just by commenting the value of $random_string and replace its value with the deployment id generated in previous run
- Added ability to run multiple vApp while using the same VMs name by fixing $moveVMsIntovApp with trick previously shared by fellow vExpert LucD
- Changed default $VCSASize = "tiny" # default is small, tiny is good enough for LAB/POC seeing the number of VMs. ref. configmax
- Changed default $VCFOperationsSize = "xsmall" # default is small, xsmall is for under 700 objects, that's good enough for POC/LAB. ref. vcf-operations-90-sizing-guidelines
09/02/2025
- Updated documentation for VVF deployment
09/01/2025
- Initial Release

VCF

Below is a diagram of what is deployed as part of the solution and you will need to have an existing vSphere 8.x or 9.x environment running that is managed by vCenter Server and with enough resources (CPU, Memory and Storage) to deploy this "Nested" lab.

VCF Requirements

VCF subscription entitlement to download VCF 9.x software binaries
VCF Online or Offline Depot
Nested ESXi 9.1.0.0 OVA
- ESXi 9.1 is only available as part of VMware Cloud Foundation (VCF) or VMware vSphere Foundation (VVF) subscription, you will need an active VVF/VCF entitlement to download the Nested ESXi 9.x Virtual Appliance. For VMUG Advantage members who have obtained the new VCP-VCF certification, you will be entitled to the download.
vCenter Server running at least vSphere 8.0 or later
- If your physical storage is vSAN, please ensure you've applied the following setting as mentioned here
ESXi Networking
- Enable either MAC Learning or Promiscuous Mode and also enable Forged transmits on your physical ESXi host networking to ensure proper network connectivity for Nested ESXi workloads
Resource Requirements
- Compute
  - Ability to provision VMs with up to 24 vCPU
  - Ability to provision up to 275 GB of memory
  - DRS-enabled Cluster (not required but vApp creation will not be possible)
- Network
  - 1 x Standard or Distributed Portgroup (routable) to deploy all VMs
    - 17 x FQDN/IP Addresses for initial VCF 9 Fleet
    - 6 x FQDN/IP Addresses for Workload Domain Deployment
- Storage
  - Ability to provision up to 1.25 TB of storage (thin provisioned)
Desktop (Windows, Mac or Linux) with latest PowerShell Core and PowerCLI 13 Core or later installed. See instructions here for more details

VCF Management Domain Configuration

Before deploying a VCF Fleet, which includes a VCF Management Domain, you will need to edit the deployment configuration file that contains all the relevant variables that are used by the deployment scripts. With the variables externalized from the deployment script, you can now have different configuration files for different environments or deployments, which are then passed to the deployment script.

See sample-william-vcf-9.1.0.ps1 for an example.

This section describes the credentials to your physical vCenter Server in which the VCF lab environment will be deployed to:

$VIServer = "FILL_ME_IN"
$VIUsername = "FILL_ME_IN"
$VIPassword = "FILL_ME_IN"

This section describes the general configuration and networking settings that will be applied to both VCF Installer and Nested ESXi VMs on your physical vCenter Server environment.

$VAppLabel = "WilliamLam-VCF9"
$VMDatacenter = "Datacenter"
$VMCluster = "MyCluster"
$VMNetwork = "MyNetwork"
$VMDatastore = "MyDatastore"
$VMNetmask = "255.255.0.0"
$VMGateway = "172.16.1.53"
$VMDNS = "172.16.1.3"
$VMNTP = "172.16.1.53"
$VMPassword = "VMware1!"
$VMDomain = "vcf.lcm"
$VMSyslog = "172.16.1.250"
$VMFolder = "wlam"

This section describes enabling debug option which will produce additional logging of the API request and payload for troubleshooting purposes.

$Debug = $false

This section describes the location of the files required for deployment.

$NestedESXiApplianceOVA = "/data/images/Nested_ESXi9.1.0.0_Appliance_Template_v1.0.ova"
$VCFInstallerOVA = "/data/images/PROD/COMP/SDDC_MANAGER_VCF/VCF-SDDC-Manager-Appliance-9.1.0.0.25371088.ova"

This section describes any override flags thats required to be used on the VCF Installer (/etc/vmware/vcf/domainmanager/application.properties)

$VCFDomainManagerProperties = @{
    "validation.disable.network.connectivity.check" = "true"
    "nsxt.mtu.validation.skip" = "true"
    "vsan.esa.sddc.managed.disk.claim" = "true"
}

This section describes the VCF version to deploy

$VCFInstallerProductVersion = "9.1.0.0"
$VCFInstallerProductSKU = "VCF"

This section describes the VCF Offline Depot configuration which supports both Offline and Online.

For VCF Online Depot, generate Broadcom Download Token and update $VCFInstallerDepotToken variable with the value and change $VCFInstallerSoftwareDepot to online

For VCF Offline Depot, you will need to have all required binaries/metadata downloaded using the new VCF Download Tool. If you are a VMUG Advantage Member with VCP-VCF certification, you can refer to this process for setting up your VCF Offline Depot. Once your VCF Offline Depot is up and running, you can then populate the required fields below.

For VCF Offline Depot, this must be set up in advance

# VCF Software Depot Configuration
$VCFInstallerSoftwareDepot = "offline" #online or offline
$VCFInstallerDepotToken = ""

# Offline Depot Configurations (optional)
$VCFInstallerDepotUrl = "http://172.16.1.54:8888"

💡 For simplicity purposes, only offline depot without basic auth is supported with script. Users can override this behavior by updating the JSON payload

This section describes the VCF Fleet level configuration values. The $DeploymentInstanceName can be a friendly label that is displayed within VCF Operations but the $DeploymentId should be DNS-compliant, no special characters or spaces.

$DeploymentInstanceName = "William VCF 9.1 Instance"
$DeploymentId = "vcf-m01"
$CEIPEnabled = $true

This section describes the VCF Installer configuration which will be deployed onto your physical vCenter Server environment, along side the Nested ESXi VMs. The $VCFInstallerAdminUsername value should be left as the default below.

$VCFInstallerVMName = "inst01"
$VCFInstallerFQDN = "inst01.vcf.lcm"
$VCFInstallerIP = "172.16.30.10"
$VCFInstallerAdminUsername = "admin@local" # do not change
$VCFInstallerAdminPassword = "VMware1!VMware1!"
$VCFInstallerRootPassword = "VMware1!VMware1!"

This section describes the SDDC Manager component that will be deployed as part of the VCF Fleet.

$SddcManagerHostname  = "sddcm01"
$SddcManagerIP = "172.16.30.11"
$SddcManagerRootPassword = "VMware1!VMware1!"
$SddcManagerVcfPassword = "VMware1!VMware1!"
$SddcManagerSSHPassword = "VMware1!VMware1!"
$SddcManagerLocalPassword = "VMware1!VMware1!"

This section defines the number of Nested ESXi VMs to deploy along with their associated IP Address(s). The names are the display name of the VMs when deployed and you should ensure these are added to your DNS infrastructure. A minimum of three hosts is required for VCF deployment.

$NestedESXiHostnameToIPsForManagementDomain = @{
    "esx01"   = "172.16.30.1"
    "esx02"   = "172.16.30.2"
    "esx03"   = "172.16.30.3"
}

This section defines the number of Nested ESXi VMs to deploy along with their associated IP Address(s) for use in a Workload Domain deployment. The names are the display name of the VMs when deployed and you should ensure these are added to your DNS infrastructure. A minimum of three hosts should be used for Workload Domain deployment

$NestedESXiHostnameToIPsForWorkloadDomain = @{
    "esx04"   = "172.16.30.4"
    "esx05"   = "172.16.30.5"
    "esx06"   = "172.16.30.6"
}

This section describes the amount of resources to allocate to either the Nested ESXi VM(s) for use with Management Domain as well as Workload Domain (if you choose to deploy.) Depending on your usage, you may want to increase the resources but for proper functionality, this is the minimum to start with. For Memory and Disk configuration, the unit is in GB.

# Nested ESXi VM Resources for Management Domain
$NestedESXiMGMTvCPU = "32"
$NestedESXiMGMTvMEM = "112" #GB
$NestedESXiMGMTCachingvDisk = "32" #GB
$NestedESXiMGMTCapacityvDisk = "500" #GB
$NestedESXiMGMTBootDisk = "64" #GB

# Nested ESXi VM Resources for Workload Domain
$NestedESXiWLDvCPU = "16"
$NestedESXiWLDvMEM = "32" #GB
$NestedESXiWLDCachingvDisk = "32" #GB
$NestedESXiWLDCapacityvDisk = "250" #GB
$NestedESXiWLDBootDisk = "64" #GB

This section describes the Nested ESXi Networks that will be used for VCF configuration. For the ESXi management network, the CIDR definition should match the network specified in $VMNetwork variable.

$NestedESXiManagementNetworkCidr = "172.16.0.0/16" # should match $VMNetwork configuration
$NestedESXivMotionNetworkCidr = "10.1.32.0/24"
$NestedESXivSANNetworkCidr = "10.1.33.0/24"
$NestedESXiNSXTepNetworkCidr = "10.1.34.0/24"

This section describes the vCenter Server configuration that will be used within the VCF Fleet deployment.

$VCSAName = "vc01"
$VCSAIP = "172.16.30.12"
$VCSARootPassword = "VMware1!VMware1!"
$VCSASSOPassword = "VMware1!VMware1!"
$VCSASize = "medium"
$VCSADatacenterName = "vcf-mgmt-dc"
$VCSAClusterName = "vcf-mgmt-cl01"

This section describes the vSAN configurations that will be used within the VCF Fleet deployment.

$VSANFTT = 0
$VSANDedupe = $false
$VSANESAEnabled = $true
$VSANDatastoreName = "vsanDatastore"

This section describes the NSX Manager configurations that will be used within the VCF Fleet deployment.

$NSXManagerSize = "medium"
$NSXManagerVIPHostname = "nsx01"
$NSXManagerVIPIP = "172.16.30.20"
$NSXManagerNodeHostname = "nsx01a"
$NSXRootPassword = "VMware1!VMware1!"
$NSXAdminPassword = "VMware1!VMware1!"
$NSXAuditPassword = "VMware1!VMware1!"

This section describes the VCF Management Services (VCFMS) configurations that will be used within the VCF Fleet deployment.

$VCFManagementServicesSize = "small"
$VCFManagementServicesRuntimeHostname = "vcf-msr01"
$VCFManagementServicesSystemPassword = "VMware1!VMware1!"
$VCFManagementServicesFleetHostname = "vcf-flt01"
$VCFManagementServicesInstanceHostname = "vcf-int01"
$VCFManagementServicesIPStartRange = "172.16.1.65"
$VCFManagementServicesIPEndRange = "172.16.1.76"
$VCFManagementServicesInternalClusterCidrIpv4 = "198.18.0.0/15"

This section describes the Identity Broker component that runs within VCFMS

$VCFManagementServicesIdentityHostname = "vcf-idb01"

This section describes the License Server configuration

$VCFLicenseServerHostname = "vcf-lic01"

This section describes the VCF Operation configurations that will be used within the VCF Fleet deployment.

$VCFOperationsSize = "small"
$VCFOperationsHostname = "vcf01"
$VCFOperationsIP = "172.16.30.13"
$VCFOperationsRootPassword = "VMware1!VMware1!"
$VCFOperationsAdminPassword = "VMware1!VMware1!"

This section describes the VCF Operations Collector configurations that will be used within the VCF Fleet deployment.

$VCFOperationsCollectorSize = "small"
$VCFOperationsCollectorHostname = "vcf-proxy01"
$VCFOperationsCollectorRootPassword = "VMware1!VMware1!"

This section describes the VCF Automation configurations that will be used within the VCF Fleet deployment.

$VCFAutomationSize = "small"
$VCFAutomationHostname = "auto01"
$VCFAutomationServicesRuntimeHostname = "vcf-asr01"
$VCFAutomationAdminPassword = "VMware1!VMware1!"
$VCFAutomationIPPool = @("172.16.1.77","172.16.1.78","172.16.1.79","172.16.1.80","172.16.1.81")
$VCFAutomationNodePrefix = "vcf-lamw-auto"
$VCFAutomationClusterCIDR = "198.18.0.0/15"

This section describes the Workload Domain configurations, this is completely optional and is only processed when running the vcf-automated-wld-deployment.ps script is used.

$VCFWorkloadDomainName = "vcf-w01"
$VCFWorkloadDomainOrgName = "vcf-w01"
$VCFWorkloadDomainEnableVCLM = $true
$VCFWorkloadDomainEnableVSANESA = $false

This section describes the vCenter Server configurations for the Workload Domain

$VCFWorkloadDomainVCSAHostname = "vc02"
$VCFWorkloadDomainVCSAIP = "172.16.30.40"
$VCFWorkloadDomainVCSARootPassword = "VMware1!VMware1!"
$VCFWorkloadDomainVCSASSOPassword = "VMware1!VMware1!"
$VCFWorkloadDomainVCSADatacenterName = "vcf-wld-dc"
$VCFWorkloadDomainVCSAClusterName = "vcf-wld-cl01"

This section describes the NSX Manager configurations for the Workload Domain

$VCFWorkloadDomainNSXManagerVIPHostname = "nsx02"
$VCFWorkloadDomainNSXManagerNode1Hostname = "nsx02a"
$VCFWorkloadDomainNSXManagerNode1IP = "172.16.30.42"
$VCFWorkloadDomainNSXAdminPassword = "VMware1!VMware1!"
$VCFWorkloadDomainSeparateNSXSwitch = $false

VCF Sample Execution

In the example below, I am using /16 VLAN (172.16.0.0/16) for all my management VMs with the following DNS entries:

FQDN	IP Address	Function
esx01.vcf.lcm	172.16.30.1	ESX Host 1 for Mgmt
esx02.vcf.lcm	172.16.30.2	ESX Host 2 for Mgmt
esx03.vcf.lcm	172.16.30.3	ESX Host 3 for Mgmt
esx04.vcf.lcm	172.16.30.4	ESX Host 1 for WLD
esx05.vcf.lcm	172.16.30.5	ESX Host 2 for WLD
esx06.vcf.lcm	172.16.30.6	ESX Host 3 for WLD
inst01.vcf.lcm	172.16.30.10	VCF Installer
sddcm01.vcf.lcm	172.16.30.11	SDDC Manager
vc01.vcf.lcm	172.16.30.12	vCenter Server for Mgmt
vcf01.vcf.lcm	172.16.30.13	VCF Operations
vcf-msr01.vcf.lcm	172.16.30.14	VCF Management Services Runtime
vcf-flt01.vcf.lcm	172.16.30.15	VCF Management Services Fleet FQDN
vcf-int01.vcf.lcm	172.16.30.16	VCF Management Services Instance FQDN
vcf-lic01.vcf.lcm	172.16.30.17	License Server
vcf-log01.vcf.lcm	172.16.30.18	Log Management
vcf-idb01.vcf.lcm	172.16.30.18	Identity Broker
nsx01.vcf.lcm	172.16.30.20	NSX Manager VIP for Mgmt
nsx01a.vcf.lcm	172.16.30.21	NSX Manager Node 1 for Mgmt
vcf-proxy01.vcf.lcm	172.16.30.28	VCF Operations Collector
vcf-asr01.vcf.lcm	172.16.30.29	VCF Automation Services Runtime
auto01.vcf.lcm	172.16.30.30	VCF Automation

VCF Deploy Nested ESX and VCF Installer VMs

Here is a screenshot of running the script if all basic pre-reqs have been met and the confirmation message before starting the deployment:

Here is an example output of a complete deployment:

💡 Deployment time will vary based on underlying physical infrastructure resources. In my lab, this took ~19min to complete.

Once completed, you will end up with the following VMs placed into a vApp.

VCF Deploy VCF Fleet with Management Domain

By default, the script will auto generate the required VCF Fleet with Management Domain deployment file vcf-mgmt-XXX.json based on your input and save that into the current working directory. Additionally, the VCF deployment file will automatically be submitted to the VCF Installer to begin the VCF deployment and you can monitor the progress by logging into the VCF Installer UI.

💡 If you wish to disable and/or customize the vcf-mgmt-XXX.json spec prior to submitting, you can disable the automatic deployment process by searching for the variable named $startVCFBringup in the script and updating the value to 0.

The deployment can take up to several hours to complete depending on your underlying physical resources. Once completed, you should see the following screen confirming the deployment finished and you can now login to your new VCF 9.0 environment!

When logging into the vCenter Server for the VCF Management Domain, you should see the following in the vSphere Inventory:

VCF Deploy VCF Workload Domain

A supplemental automation script vcf-automated-wld-deployment.ps1 can be used to automatically standup a VCF workload domain. It will assume that the VCF Workload Domain host commission file vcf-commission-host-api.json was automatically generated from running the initial deployment script and this file will contain a "TBD" field because the VCF Installer API expects the Management Domain Network Pool ID, which will be retrieved automatically as part of using the additional automation.

Here is an example of what will be deployed as part of Workload Domain creation:

FQDN	IP Address	Function
vc02.vcf.lcm	172.16.30.40	vCenter Server for WLD
nsx02.vcf.lcm	172.16.30.41	NSX Manager VIP for WLD
nsx02a.vcf.lcm	172.16.30.42	NSX Manager Node 1 for WLD

VCF Example Deployment

Here is a screenshot of running the script, which you will provide the same environment configuration file as the initial VCF Fleet deployment.

As part of deploying the VCF Workload Domain, it will ensure the SDDC Manager is connected to either your VCF Online or Offline Depot and synchronize binaries before deployment can begin. This can take some time depending on your depot method and connectivity.

Once the VCF Workload Domain deployment has begun, you can login to either vCenter Server or VCF Operations to monitor the progress of the deployment.

💡 The deployment progress not show up immediately, so give it some time and once the deployment has successfully completed, you should now see a new VCF Workload Domain connected to your existing VCF Fleet

VVF

Below is a diagram of what is deployed as part of the solution and you will need to have an existing vSphere 8.x or 9.x environment running that is managed by vCenter Server and with enough resources (CPU, Memory and Storage) to deploy this "Nested" lab.

VVF Requirements

VVF subscription entitlement to download VCF 9.x software binaries
VVF Online or Offline Depot
Nested ESX 9.1.0.0 OVA
- ESXi 9.1 is only available as part of VMware Cloud Foundation (VCF) or VMware vSphere Foundation (VVF) subscription, you will need an active VVF/VCF entitlement to download the Nested ESXi 9.x Virtual Appliance. For VMUG Advantage members who have obtained the new VCP-VCF certification, you will be entitled to the download.
vCenter Server running at least vSphere 8.0 or later
- If your physical storage is vSAN, please ensure you've applied the following setting as mentioned here
ESXi Networking
- Enable either MAC Learning or Promiscuous Mode and also enable Forged Transmits on your physical ESXi host networking to ensure proper network connectivity for Nested ESXi workloads
Resource Requirements
- Compute
  - Ability to provision VMs with up to 12 vCPU
  - Ability to provision up to 104 GB of memory
  - DRS-enabled Cluster (not required but vApp creation will not be possible)
- Network
  - 1 x Standard or Distributed Portgroup (routable) to deploy all VMs
    - 10 x FQDN/IP Addresses for VVF deployment
- Storage
  - Ability to provision up to 100 GB of storage (thin provisioned)
Desktop (Windows, Mac or Linux) with latest PowerShell Core and PowerCLI 13 Core or later installed. See instructions here for more details

VVF Configuration

For a VVF deployment, the VCFInstallerProductSKU variable needs to change to VVF and only the Management ESXi Hosts, vCenter Server and VCF Operations configuration variables are used. You can refer to the sample-william-vvf-9.1.0.ps1 for an example.

VVF Sample Execution

In the example below, I am using /16 VLAN (172.16.0.0/16) for all my management VMs with the following DNS entries:

FQDN	IP Address	Function
esx01.vcf.lcm	172.16.30.1	ESX Host 1 for Mgmt
esx02.vcf.lcm	172.16.30.2	ESX Host 2 for Mgmt
esx03.vcf.lcm	172.16.30.3	ESX Host 3 for Mgmt
inst01.vcf.lcm	172.16.30.10	VCF Installer
vc01.vcf.lcm	172.16.30.12	vCenter Server for Mgmt
vcf01.vcf.lcm	172.16.30.13	VCF Operations
vcf-msr01.vcf.lcm	172.16.30.14	VCF Management Services Runtime
vcf-flt01.vcf.lcm	172.16.30.15	VCF Management Services Fleet FQDN
vcf-int01.vcf.lcm	172.16.30.16	VCF Management Services Instance FQDN
vcf-lic01.vcf.lcm	172.16.30.17	License Server

Here is a screenshot of running the script if all basic pre-reqs have been met and the confirmation message before starting the deployment:

Here is an example output of a complete deployment:

The deployment should not take too long but will depend on your underlying physical resources. Once completed, you should see the following screen confirming the deployment finished and you can now login to your new VVF 9.0 environment!

Name		Name	Last commit message	Last commit date
9.0		9.0
screenshots		screenshots
README.md		README.md
sample-abbed-vcf-9.1.0-vlan.ps1		sample-abbed-vcf-9.1.0-vlan.ps1
sample-william-vcf-9.1.0.ps1		sample-william-vcf-9.1.0.ps1
sample-william-vvf-9.1.0.ps1		sample-william-vvf-9.1.0.ps1
vcf-automated-fleet-deployment.ps1		vcf-automated-fleet-deployment.ps1
vcf-automated-fleet-vlan-deployment-9.1.ps1		vcf-automated-fleet-vlan-deployment-9.1.ps1
vcf-automated-wld-deployment.ps1		vcf-automated-wld-deployment.ps1

Navigation Menu

Repository files navigation

Automated VMware Cloud Foundation Lab (VCF) 9.x Fleet Deployment

Table of Contents

Description

Changelog

VCF

VCF Requirements

VCF Management Domain Configuration

VCF Sample Execution

VCF Deploy Nested ESX and VCF Installer VMs

VCF Deploy VCF Fleet with Management Domain

VCF Deploy VCF Workload Domain

VCF Example Deployment

VVF

VVF Requirements

VVF Configuration

VVF Sample Execution

About

Releases

Packages

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

Automated VMware Cloud Foundation Lab (VCF) 9.x Fleet Deployment

Table of Contents

Description

Changelog

VCF

VCF Requirements

VCF Management Domain Configuration

VCF Sample Execution

VCF Deploy Nested ESX and VCF Installer VMs

VCF Deploy VCF Fleet with Management Domain

VCF Deploy VCF Workload Domain

VCF Example Deployment

VVF

VVF Requirements

VVF Configuration

VVF Sample Execution

About

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages