Closed JohnLudlow closed 1 year ago
BTW, if any more information is required, please just ask
Thanks!
CC @grayzu @nanalakshmanan
For others reference, perhaps your own, but, given the elapsed, time... try disabling the Analytic or Debug log first:
wevtutil.exe set-log "Microsoft-Windows-Dsc/Analytic" /q:true /e:false wevtutil.exe set-log "Microsoft-Windows-Dsc/Debug" /q:True /e:false
wevtutil.exe set-log "Microsoft-Windows-Dsc/Analytic" /q:true /e:true wevtutil.exe set-log "Microsoft-Windows-Dsc/Debug" /q:True /e:true
Th NA
@StevenBucher98 can this issue be closed since the LCM isn't in this repository?
Steps to reproduce
Define a configuration which
Compile and apply the configuration using
Start-DscConfiguration -Path .\Path\To\MOFs\ -Force -Verbose -Wait
Expected behavior
The domain is configured, and the DC machine is rebooted because the resource sets
$global:DSCMachineStatus = 1
. DSC waits for the reboot to complete before continuingThe other machine is joined to the domain and is rebooted because the resource sets
$global:DSCMachineStatus = 1
. DSC waits for the reboot to complete before continuingThe final resource is triggered to prove that DSC waited for the reboots to complete
Actual behavior
The domain is configured, and the DC machine is rebooted because the resource sets
$global:DSCMachineStatus = 1
. DSC waits for the reboot to complete before continuingThe other machine is joined to the domain but is not rebooted immediately. DSC declares the machine 'configured' and carries on.
If I log onto this machine and check the state of the LCM, it will be in one of these states:
However, the overall configuration does not wait for this to complete
The final resource is skipped, though after a while (15 minutes, I guess) the machine is rebooted, the consistency check is performed and the configuration is applied.
Some things to note
OK, technically I am not actually using xADDomain - it installs DNS which we need it to not do. I created a class-based resource which does something very similar, but specfies
-InstallDns:$false
. However, this is the bit that works.I was unable to make the analytic log work. I looked up this article and got this error:
That sort of threw me and I wasn't sure how to proceed. However, I have attached the Operational log (actually the .zip you can get from xDscDiagnostics)
cvtdmofh.zge-20161125065616.zip
Environment data
The DSC resources available on that system: