Hi all, I’ve submitted a bug on Connect (https://connect.microsoft.com/PowerShell/Feedback/Details/1515243). I probably should have checked here to see if anyone else is experiencing it before submitting.
Has anyone else experienced this?
Reproduction Steps
-
Create a 2 partial configurations. The first configuration should contain a resource that requests a reboot.
-
Define the partial configurations a meta MOF and deploy to a computer
When you run Update-DscConfiguration against that computer, the DSC engine will stop configuring after the first partial configuration with a warning saying the computer needs to be rebooted. The DSC engine does NOT continue with the second partial configuration until a reboot is performed or a force consistency check.
Invoke-CimMethod -ComputerName MyComputer -Name PerformRequiredConfigurationChecks -Namespace root/Microsoft/Windows/DesiredStateConfiguration -Arguments @{Flags=[Uint32]2} -ClassName MSFT_DscLocalConfigurationManager
Expected Results
If I configure a meta mof with a normal configuration… (See example A), as per the MS document, the DSC engine runs ResourceA to ResourceD. This is the expected result.
Meta MOF example (A)
Normal Configuration
ResourceA - (Declares reboot required)
ResourceB
ResourceC
ResourceD
However, if I configure a meta mof with a partial configuration… (See example B), the DSC engine runs ResourceA to ResourceB then stops. The configuration is NOT completed.
The expected result should be the DSC engine runs ResourceA to ResourceD if RebootNodeIfNeeded is set to False.
Meta MOF example (B)
Partial Configuration 1
ResourceA - (Declares reboot required)
ResourceB
Partial Configuration 2
ResourceC
ResourceD