Author Posts

September 10, 2015 at 11:07 pm

Update-DscConfiguration -ComputerName $myserver -Wait -Verbose

In POSH5 this results in "check if a new MOF is available on the pull server, and if so apply that MOF"
In POSH4 this results in "check if a new MOF is available on the pull server, and if so apply that MOF OR if there is no new MOF, reapply the current MOF"

You guessed it: I liked the behavior of POSH4 better. Is this change "by design"? And if so, what is the reasoning behind this?

My workaround, prior to the Update-DscConfiguration command, run:
Remove-DscConfigurationDocument -CimSession $myserver -Stage Current

September 11, 2015 at 12:41 am

It's by design, yes. I can't comment on the thinking since I'm not on the team 🙂 but the behavior was noted in early release notes.

September 11, 2015 at 4:35 am

Probably because they gave you finer control over the "re-apply existing" functionality with the new Start-DscConfiguration -UseExisting switch.

September 11, 2015 at 5:09 am

Start-DscConfiguration -UseExisting
Seems to be the simplest method.
Thanks Don & Dave