Systems with WMF 4 installed are fine.
Confirmed. I had a Server 2012 VM that was behaving the old way, but I’m pretty sure I had installed the WMF 4.0 preview version on that one. I reinstalled it, and everything’s looking good now. Also tested a Server 2008 R2 machine successfully.
The first error I countered (from this Connect post) was also resolved by making sure everything was patched to the GA release levels before trying to apply a configuration.
One other thing I’ve noticed: The ConfigurationModeFrequencyMins and RefreshFrequencyMins settings for the LCM appear to have minimum values of 30 and 15 minutes, respectively. You can set anything you like in the configuration / MOF file and it won’t produce any errors, but the effective values don’t seem to ever go any lower than that when I check them with Get-DscLocalConfigurationManager. Rather than waiting around for 15-30 minutes during my testing, I was able to force the LCM to do a pull configuration by running the scheduled task “\Microsoft\Windows\Desired State Configuration\Consistency”, which just executes the following CIM method:
$params = @{
Namespace = 'root/Microsoft/Windows/DesiredStateConfiguration'
ClassName = 'MSFT_DSCLocalConfigurationManager'
MethodName = 'PerformRequiredConfigurationChecks'
Arguments = @{
Flags = [uint32] 1
}
}
Invoke-CimMethod @params