Closed jimchurches closed 3 years ago
Did you use Set-DscLocalConfigurationManager
to configure the LCM on the target node with the meta configuration? See how to write the configuration here https://docs.microsoft.com/en-us/powershell/scripting/dsc/managing-nodes/metaconfig?view=powershell-5.1.
Doh!
That will be it!
I'm use to that being handled in my automation (I think the DSC extension takes care of that for me?) and messing around at the command prompt I have missed the step.
I will check tomorrow when back in the office. Feeling dumb.
So as @johlju points out, I've missed a step with Set-DscLocalConfigurationManager
. This step is done for you via the Azure DSC Extension so I'd forgotten about it from my pre-Azure days. Thanks for the help.
I have updated my config in the original post above just so my fully working configuration is included in the post.
No worries. Glad I could help 😃
@jimchurches Excuse me for bothering you, would you mind explaining exactly what we are supposed to do with Set-DscLocalConfigurationManager to make DSC restart the system as part of the configuration ?
Details of the scenario you tried and the problem that is occurring
What am I missing? Help!
Installing a brand new forest on a Windows Server 2019 server the DSC configuration seems to install ADDS without issue, however, the system does not reboot to complete installation/configuration. A reboot is required to complete the installation and configuration of the new ADDS forest.
The DSC configuration I'm using is included below.
I am running this configuration at the PowerShell command prompt interactively and not via a pull server or via the Azure DSC extension. I'm just checking my work before attempting to build into my larger build pipeline in Azure DevOps and Azure ARM templates.
For testing, along with the configuration further below, I just use this code to apply the configuration:
Verbose logs showing the problem
Suggested solution to the issue
Target node reboots after Active Directory is installed/configured.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
OsName : Microsoft Windows Server 2019 Datacenter OsOperatingSystemSKU : DatacenterServerEdition OsArchitecture : 64-bit WindowsVersion : 1809 WindowsBuildLabEx : 17763.1.amd64fre.rs5_release.180914-1434 OsLanguage : en-US OsMuiLanguages : {en-US}
Version and build of PowerShell the target node is running
Name Value
PSVersion 5.1.17763.1852
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17763.1852
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Version of the DSC module that was used
6.0.1