Skip to content

Removing extra unrelated content #95

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
HemantMahawar merged 3 commits into from
Dec 20, 2015
Merged

Removing extra unrelated content #95

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ddf131f
Merge pull request #1 from PowerShell/master
HemantMahawar Dec 20, 2015
2221452
Removing extra unrelated content
Dec 20, 2015
7726903
Removing extra spaces
Dec 20, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 11 additions & 21 deletions wmf/dsc_freqnomultiple.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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 | |