After initial application of a new configuration, if the target node drifts from the desired state, DSC reports the discrepancy in logs. ApplyAndMonitor: This is the default value.Note that DSC will attempt to apply the configuration until it is successful before ApplyOnly takes effect. After initial application of a new configuration, DSC does not check for drift from a previously configured state. ApplyOnly: DSC applies the configuration and does nothing further unless a new configuration is pushed to the target node or when a new configuration is pulled from a service.Possible values are "ApplyOnly", "ApplyAndMonitor", and "ApplyAndAutoCorrect". Specifies how the LCM actually applies the configuration to the target nodes. For more information, see Setting up a pull client with configuration names. Note: If you set this property, registering the node with a pull service by using RegistrationKey does not work. The node will pull configurations on the pull service if the name of the configuration MOF is named ConfigurationID.mof. A GUID that identifies the configuration file to get from a pull service. Use ConfigurationRepositoryWeb and ConfigurationRepositoryShare blocks to define configuration pull service endpoints.įor backwards compatibility with older pull service versions. Note: this is managed automatically if using Azure Automation DSC pull service. For more information see Want to secure credentials in Windows PowerShell Desired State Configuration?. ![]() The thumbprint of a certificate used to secure credentials passed in a configuration. ![]() $TRUE if new configurations downloaded from the pull service are allowed to overwrite the old ones on the target node. StopConfiguration: Stop the current configuration after machine reboot.ContinueConfiguration: Continue applying the current configuration after machine reboot.The possible values are "ContinueConfiguration" and "StopConfiguration". Specifies what happens after a reboot during the application of a configuration. ![]() The following properties are available in a Of the LCM are configured in a Settings block. Other than specifying pull service endpoints/paths and partial configurations, all of the properties PartialConfiguration: provides data to enable partial configurations.ReportServerWeb: specifies an HTTP pull service to which reports are sent.ResourceRepositoryShare: specifies an SMB share for modules.ResourceRepositoryWeb: specifies an HTTP pull service for modules.ConfigurationRepositoryShare: specifies an SMB share for configurations.ConfigurationRepositoryWeb: specifies an HTTP pull service for configurations.In the previousĮxample, the only resource called is Settings. After you enact the LCMĬonfiguration, you can see the properties of the LCM by calling theĪn LCM configuration can contain blocks only for a limited set of resources. Supplying the path to the LCM configuration MOF as a parameter. You do not enact an LCM configuration by calling the You will createĪn LCM configuration, compile it to a MOF file, and apply it to the node. The process of applying settings to LCM is similar to applying a DSC configuration. Shows a simple configuration that sets the LCM to push mode. To specify an LCM configuration, you use the DscLocalConfigurationManager attribute. To configure the LCM, you create and run a special type of configuration that applies LCM settings. ![]() Writing and enacting an LCM configuration Information about configuring the LCM in Windows PowerShell 4.0, seeĬonfiguring the Local Configuration Manager in Previous Versions of Windows PowerShell. Windows PowerShell 5.0 introduced new settings for managing Local Configuration Manager. Theįollowing sections describe how to configure the LCM. You use a special type of configuration to configure the LCM to specify each of these behaviors.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |