I'm trying Surebackup jobs to test certain appliations and upgrade scenereos and needless to say it takes a very long time. If I do not give enough "power on time" for the virtual domain controller that starts up first, and I don't log into that DC and change it to DHCP from its original static IP... the Surebackup tests will fail and the whole session will be torn down, despite things actually working.
So to mitigate that I have to change the power on time for the first VM in the SureBackup job (a Server 2012 R2 Domain Controller) to 1800 seconds, which is a half hour. This is quite a while. In fact Everything should be reachable now 19 minutes in from initially kicking off the job, but I have to sit here and wait another 11 mintues until it runs some test scripts and then moves on to powering up the next machine.
I noticed in the Sure Backup job properties you can right click any of the machines in the list and the option of "Start" comes up in the menu but its greyed out. Isn't there a way to get this to move on a little faster?
The DC takes the longest because it boots up, and you can't log in right away (Says no login servers available for your request), but then it automatically reboots itself and then you can log in. Its pretty slow, average disk read latency on VeeamBackup_veeam.domain.com is 331.273 ms, maximum of 3463 minimum 0. But once logged in I have to go into network properties and change it to DHCP, as it will get an address from the Veeam_SureBackup_Lab_Proxy VM, and then since its a DC I specify 127.0.0.1 as the DNS, and in all subsequent machines in the SureBackup job I will specify the IP that the SureBackup Lab Proxy gave the DC as their DNS, which appears to be 10.0.0.1 oddly when the network masquerade address is 10.11.0.0/16.