Holorouter Version
9.1
VCF Version
VCF 9.1
Target Type
Standalone ESX Host
Describe the bug
When trying to deploy v9.1 using -DeveloperMode, there is no proper way to have the Service ID/ Activation code for the Software Depot.
Reproduction steps
Do a new deployment for 9.1 with -DeveloperMode
Expected behavior
To install correctly.
Relevant logs
Additional context
Workarround/Fix:
This does go against the unattended setup of DeveloperMode, (using a offline depot might make more sense for a unattended setup..)
Holodeck.psm1:
-424 $Global:BroadcomBuildToken = ConvertTo-SecureString -AsPlainText -Force -String $env:brcm_build_token
+424 # For VCF 9.1+, skip token request here - it will be done after VCF Installer deployment
+425 if($Version_site_a -like "9.1*"){
+426 Write-Log -Message "VCF 9.1+ detected. Online depot token will be requested after VCF Installer deployment." -Level "INFO"
+427 }
+428 else{
+429 # For VCF 9.0 and earlier, keep existing behavior
-610 $Global:BroadcomBuildToken = ConvertTo-SecureString -AsPlainText -Force -String $env:brcm_build_token
+610 # For VCF 9.1+, skip token request here - it will be done after VCF Installer deployment
+611 if($Version_site_a -like "9.1*"){
+612 Write-Log -Message "VCF 9.1+ detected. Online depot token will be requested after VCF Installer deployment." -Level "INFO"
+613 }
+614 else{
+615 # For VCF 9.0 and earlier, keep existing behavior
Holorouter Version
9.1
VCF Version
VCF 9.1
Target Type
Standalone ESX Host
Describe the bug
When trying to deploy v9.1 using -DeveloperMode, there is no proper way to have the Service ID/ Activation code for the Software Depot.
Reproduction steps
Do a new deployment for 9.1 with -DeveloperMode
Expected behavior
To install correctly.
Relevant logs
Additional context
Workarround/Fix:
This does go against the unattended setup of DeveloperMode, (using a offline depot might make more sense for a unattended setup..)
Holodeck.psm1: