diff --git a/wmf/dsc_freqnomultiple.md b/wmf/dsc_freqnomultiple.md index 2e922c41bcb2..df282c798447 100644 --- a/wmf/dsc_freqnomultiple.md +++ b/wmf/dsc_freqnomultiple.md @@ -1,26 +1,16 @@ ### Frequencies for RefreshMode and ConfigurationMode need not be multiple of each other +In the previous version of DSC, LCM would treat RefreshFrequencyMins and ConfigurationModeFrequencyMins as multiple of each other as explained in the blog [here](http://blogs.msdn.com/b/powershell/archive/2013/12/09/understanding-meta-configuration-in-windows-powershell-desired-state-configuration.aspx). In WMF 5.0 RTM, RefreshFrequencyMins and ConfigurationModeFrequencyMins are processed independent of each other. The tables below illustrate this behavior: -There have been some improvements to Windows PowerShell debugging after WMF 5.0 September Preview. +Behaviour in **PULL** mode: -- The Enter-PSHostProcess cmdlet has a new, optional **AppDomainName** parameter. If you specify this parameter, Enter-PSHostProcess tries to connect to the specified app domain in the target process. If you do not specify this parameter, Enter-PSHostProcess tries to connect to the default domain in the process. +|   |**Value in Meta Configuration**|**Value after Meta Configuration is applied**|**How often pull happens (in mins)**|**How often configuration is applied (in mins)**| +|----------------------------------|-------------------------------|---------------------------------------------|------------------------------------|------------------------------------------------| +|**ConfigurationModeFrequencyMins**|70 |70 | |70 | +|**RefreshFrequencyMins** |40 |40 |40 | | -- Get-PSHostProcessInfo now returns AppDomain names along with processes to which you can connect by running the Enter-PSHostProcess cmdlet. +Behavior in **PUSH** mode: -DSC RefreshFrequencyMins and ConfigurationModeFrequencyMins are no longer required to be multiple of each other ---------------------------------------------------------------------------------------------------------------- - -In the previous version of DSC, LCM would treat RefreshFrequencyMins and ConfigurationModeFrequencyMins as multiple of each other as explained in the blog [here](http://blogs.msdn.com/b/powershell/archive/2013/12/09/understanding-meta-configuration-in-windows-powershell-desired-state-configuration.aspx). In WMF 5.0 RTM RefreshFrequencyMins and ConfigurationModeFrequencyMins are processed independent of each other. - -To illustrate this behavior in PULL mode, let us look at the table below: - -|   | **Value in Meta Configuration** | **Value after Meta Configuration is applied** | **How often pull happens \[mins\]** | **How often configuration is applied \[mins\]** | -|------------------------------------|---------------------------------|-----------------------------------------------|-------------------------------------|-------------------------------------------------| -| **ConfigurationModeFrequencyMins** | 70 | 70 | 40 | 70 | -| **RefreshFrequencyMins** | 40 | 40 | | | - -Behavior in PUSH mode in explained below: - -|   | **Value in Meta Configuration** | **Value after Meta Configuration is applied** | **How often configuration is applied \[mins\]** | -|------------------------------------|---------------------------------|-----------------------------------------------|-------------------------------------------------| -| **ConfigurationModeFrequencyMins** | 70 | 70 | 70 | -| **RefreshFrequencyMins** | 40 | 40 | | +| |**Value in Meta Configuration**|**Value after Meta Configuration is applied**|**How often configuration is applied (in mins)**| +|----------------------------------|-------------------------------|---------------------------------------------|------------------------------------------------| +|**ConfigurationModeFrequencyMins**|70 |70 |70 | +|**RefreshFrequencyMins** |40 |40 | |