You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When starting a complex lab (10+ machines total), I am receiving a timeout error. All of the machines are created and started successfully, then the Root Domain Controller is restarted after installing AD and I get the error. The FullyQualifiedErrorId is "Microsoft.Powershell.Commands.WriteErrorException,Wait-LabADReady". I have iteratively reduced the number of machines and received the same error each time. Newbie to AutomatedLab as well.
Steps to reproduce the issue
# lab configs$labSources='C:\LabSources'#here are the lab sources$vmDrive='C:'#this is the drive where to create the virtual machines$labName='DarkTower'#the name of the lab#create the folder path for the lab using Join-Path$labPath=Join-Path-Path $vmDrive-ChildPath $labName#create the target directory if it does not existif (-not (Test-Path$labPath)) { New-Item$labPath-ItemType Directory |Out-Null }
#once this is done , The base image of windows server 2019 will start#or if you have a base image of the OS , just copy it to the BADBLOOD directory this will save time.#create an empty lab template and define where the lab XML files and the VMs will be storedNew-LabDefinition-VmPath $labPath-Name $labName-DefaultVirtualizationEngine HyperV
#make the network definitionAdd-LabVirtualNetworkDefinition-Name $labName-AddressSpace 192.168.60.0/24#and the domain definition with the domain admin accountAdd-LabDomainDefinition-Name Gilead.LOCAL -AdminUser RandallFlagg -AdminPassword Allthingsservethebeam
Set-LabInstallationCredential-Username RandallFlagg -Password Allthingsservethebeam
#The below code will be used for all vms as the default and base $PSDefaultParameterValues=@{
'Add-LabMachineDefinition:Network'=$labName'Add-LabMachineDefinition:ToolsPath'="$labSources\Tools"'Add-LabMachineDefinition:DnsServer1'='192.168.60.10''Add-LabMachineDefinition:Memory'=2096MB
}
#the first machine is the root domain controllerAdd-LabMachineDefinition-Name DarkTower-DC -IpAddress 192.168.60.10-Memory 6000MB-OperatingSystem 'Windows Server 2016 Standard (Desktop Experience)'-DomainName Gilead.LOCAL -Roles RootDC
#-----------------here we add our servers and whatever else we want.-----------#Add-LabMachineDefinition-Name Rhea -IpAddress 192.168.60.50-OperatingSystem 'Windows Server 2022 Datacenter'Add-LabMachineDefinition-Name Eldred -IpAddress 192.168.60.51-OperatingSystem 'Windows Server 2016 Standard'#Add-LabMachineDefinition -Name Mordred -IpAddress 192.168.60.52 -OperatingSystem 'Windows Server 2016 Standard'Add-LabMachineDefinition-Name Tet -IpAddress 192.168.60.53-OperatingSystem 'Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish"'Add-LabMachineDefinition-Name Eld -IpAddress 192.168.60.54-OperatingSystem 'Ubuntu-Server 20.04.4 LTS "Focal Fossa"'Add-LabMachineDefinition-Name Jake -OperatingSystem 'Windows 11 Pro'Add-LabMachineDefinition-Name Eddie -OperatingSystem 'Windows 11 Pro'#Add-LabMachineDefinition -Name Susanah -OperatingSystem 'Windows 11 Pro'#Add-LabMachineDefinition -Name Oy -OperatingSystem 'Windows 11 Pro'#Add-LabMachineDefinition -Name Cuthbert -OperatingSystem 'Windows 11 Pro'Add-LabMachineDefinition-Name Alain -OperatingSystem 'Windows 10 Enterprise'Add-LabMachineDefinition-Name Susan -OperatingSystem 'Windows 10 Enterprise'#Add-LabMachineDefinition -Name Jamie -OperatingSystem 'Windows 10 Enterprise'#Add-LabMachineDefinition -Name Cort -OperatingSystem 'Windows 10 Enterprise'#Add-LabMachineDefinition -Name SKing -OperatingSystem 'Windows 10 Enterprise'Add-LabMachineDefinition-Name JohnFarson -OperatingSystem 'Windows 7 Enterprise'Add-LabMachineDefinition-Name CrimsonKing -OperatingSystem 'Windows 7 Enterprise'Add-LabMachineDefinition-Name JackMort -OperatingSystem 'Windows 7 Enterprise'#Add-LabMachineDefinition -Name Blaine -OperatingSystem 'Windows 7 Enterprise'#Add-LabMachineDefinition -Name Shardik -OperatingSystem 'Windows 7 Enterprise'#Now the actual work begins.Install-LabShow-LabDeploymentSummary-Detailed
PowerShell Version
5.1.20348.2227
AutomatedLab Version
5.50.0
The text was updated successfully, but these errors were encountered:
Description
When starting a complex lab (10+ machines total), I am receiving a timeout error. All of the machines are created and started successfully, then the Root Domain Controller is restarted after installing AD and I get the error. The FullyQualifiedErrorId is "Microsoft.Powershell.Commands.WriteErrorException,Wait-LabADReady". I have iteratively reduced the number of machines and received the same error each time. Newbie to AutomatedLab as well.
Steps to reproduce the issue
PowerShell Version
AutomatedLab Version
The text was updated successfully, but these errors were encountered: