Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Timeout Error Waiting for Active Directory to Start on Domain Controller #1606

Open
danielfal opened this issue Feb 8, 2024 · 1 comment
Assignees
Labels
Question The issue is a question. Solution Delivered We think that a solution has been provided but waiting for response

Comments

@danielfal
Copy link

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

# 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 exist
if (-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 stored
New-LabDefinition  -VmPath $labPath -Name $labName -DefaultVirtualizationEngine HyperV

#make the network definition
Add-LabVirtualNetworkDefinition -Name $labName -AddressSpace 192.168.60.0/24

#and the domain definition with the domain admin account
Add-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 controller
Add-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-Lab

Show-LabDeploymentSummary -Detailed

PowerShell Version

5.1.20348.2227

AutomatedLab Version

5.50.0
@raandree raandree self-assigned this Apr 1, 2024
@raandree raandree added the Question The issue is a question. label Apr 1, 2024
@raandree
Copy link
Member

raandree commented Apr 1, 2024

The lab deployment finished on my notebook in about 20 minutes without a timeout. But, I have a quite fast SSD.

The lab expects a lot of the disk. How fast is the your are trying to deploy the machines to?

Hou can start with the DC deployment first and the start the machines with a slight delay:

Install-Lab -NetworkSwitches -BaseImages -VMs -Domains

Install-Lab -StartRemainingMachines -DelayBetweenComputers 60

@raandree raandree added the Solution Delivered We think that a solution has been provided but waiting for response label Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question The issue is a question. Solution Delivered We think that a solution has been provided but waiting for response
Projects
None yet
Development

No branches or pull requests

2 participants