jvhoof
commented
4 years ago @ErikMogensen Did you find a solution for this issue? I seem to have the same issue. In multiple blogs, it is mentioned you will have a disconnect when the system joins the domain. After connecting via the serial console I could see that my network ip configuration was totally gone and the system was not yet in a domain. Tried multiple options but the only way I could get into the VM again was to change the private IP on the network interface in Azure. This causes Azure to reboot the machine and provision a new network interface on the system. I see the same issue with the previous version 1910.
The final lines in the logs indicate that DSC on the host was run and that's when the disconnect happened. 2020-08-06 13:44:45 Verbose [POC:Configure] Storage Network s-cluster-DC1 was found. 2020-08-06 13:44:45 Verbose [POC:Configure] NextHop for storage NICs to other clusters storage networks is 2020-08-06 13:44:45 Verbose [POC:Configure] Signing C:\Users\Administrator\AppData\Local\Temp\2\hostConfig\JVHAzS-HOST1.mof 2020-08-06 13:44:45 Verbose [POC:Configure] Pushing new DSC configuration, locally. 2020-08-06 13:44:45 Verbose [POC:Configure] Enabling DCOM on target computer JVHAzS-HOST1 by enabling firewall rule 'WMI-WINMGMT-In-TCP'. 2020-08-06 13:44:47 Verbose [POC:Configure] Creating DCOM CIM session to computer name JVHAzS-HOST1. 2020-08-06 13:44:47 Verbose [POC:Configure] Attempt 1 to create DCOM CIM session 2020-08-06 13:44:47 Verbose [POC:Configure] Waiting up to 30 minutes for LCM on JVHAzS-HOST1 to exit the Busy state. 2020-08-06 13:44:47 Verbose [POC:Configure] JVHAzS-HOST1: PendingConfiguration 2020-08-06 13:44:47 Verbose [POC:Configure] Publishing DSC configuration from C:\Users\Administrator\AppData\Local\Temp\2\hostConfig to the following target nodes: JVHAzS-HOST1 2020-08-06 13:44:47 Verbose [POC:Configure] DSC attempt #1. Starting DSC configuration on the following target nodes: JVHAzS-HOST1 2020-08-06 13:44:47 Verbose [POC:Configure] Time taken for configuration job to complete is 0 seconds 2020-08-06 13:44:47 Verbose [POC:Configure] Waiting for up to 1800 seconds for jobs to complete on JVHAzS-HOST1
ErikMogensen
yagmurs
Thanks for the great template and script! I can tell there is a lot of work behind it.
Unfortunately when I tried setting up using the master branch the script was unable to find a ASDK version and quit.
When I tried the development branch I selected the 2002-35 version and AAD but after the script had been running for about one hour the machine got unresponsive. The last thing I saw that it was done with the progress bar for installation of the ASDK and there were multiple progress bars displayed by PowerShell.
I ran this from inside PowerShell ISE.
I tried redploying the machine but it still not responding on port 3389. I waited at least 30 minutes until I redeployed.
I realize that there are multiple moving parts here with new releases of ASDK and Windows updates. What is the best configuration for making this work? I just want a minimal system.