LCM on clean Windows 2012R2 with WMF 5.0 Feb preview don't apply configuration.

This topic contains 5 replies, has 3 voices, and was last updated by  Juris Krumins 2 years, 5 months ago.

  • Author
    Posts
  • #26565

    Juris Krumins
    Participant

    LCM on clean Windows 2012R2 with WMF 5.0 Feb preview don't apply configuration. I've also tested with WMF 5.0 April Preview, same issue.
    WMF 5.0 November Preview works fine on Windows 2012R2 and Windows 2012.
    Anybody can comment on that, maybe experienced the same issue or can suggest how-to troubleshot things.

    Thanks in advance.

  • #26572

    Don Jones
    Keymaster

    Have you looked to see what's being logged by the LCM?

    I'd suggest enabling a diagnostics trace (DSCDiagnostics module from the Resource Kit) and seeing if you couldn't get some more detail from the diagnostics log.

  • #26809

    Juris Krumins
    Participant

    I've enabled Analytics and Debug logs, but still nothing. I can get it run only when I reboot machine. That's it. Timer based execution are not triggered. There are no messages in Debug/Analytic/Operational logs. Here is the policy and LCM configuration I try to apply to test machine:

    Configuration dscr2 {
        param (
                [parameter(Mandatory=$true)]
                [string]$MachineName
               )
    
        Import-DscResource –ModuleName 'PSDesiredStateConfiguration'
        Node $MachineName {
            Service Service0
            {
                Name = "BITS"
                State = "Stopped"
            }
    	}
    }
    
    [DscLocalConfigurationManager()]
    Configuration LCMConfiguration {
        param (
                [parameter(Mandatory=$true)]
                [string]$MachineName
               )
    
            Node "$MachineName" {
                #region LocalConfigurationManager
                Settings
                {
                    ConfigurationModeFrequencyMins = 15
                    ConfigurationMode = 'ApplyAndAutoCorrect'
                    RebootNodeIfNeeded = $true
                }
                #endregion LocalConfigurationManager
            }
    }
    
    
    Get-DscLocalConfigurationManager -CimSession $cs
    
    
    ActionAfterReboot              : ContinueConfiguration
    AgentId                        : 0F4FED01-16E6-11E5-80BE-080027FAA18C
    AllowModuleOverWrite           : False
    CertificateID                  : 
    ConfigurationDownloadManagers  : {}
    ConfigurationID                : 
    ConfigurationMode              : ApplyAndAutoCorrect
    ConfigurationModeFrequencyMins : 15
    Credential                     : 
    DebugMode                      : {NONE}
    DownloadManagerCustomData      : 
    DownloadManagerName            : 
    LCMCompatibleVersions          : {1.0, 2.0}
    LCMState                       : Idle
    LCMStateDetail                 : 
    LCMVersion                     : 2.0
    MaxPendingConfigRetryCount     : 
    StatusRetentionTimeInDays      : 10
    PartialConfigurations          : 
    RebootNodeIfNeeded             : True
    RefreshFrequencyMins           : 30
    RefreshMode                    : PUSH
    ReportManagers                 : {}
    ResourceModuleManagers         : {}
    PSComputerName                 : dscr2
    PSComputerName                 : dscr2
    
  • #26810

    Juris Krumins
    Participant

    And by the way, I've also tried cleanly installed machines without any updates installed and with all available updates installed. Same behavior.

  • #26879

    Micky Balladelli
    Participant

    When looking at what is returned by the LCM, the ConfigurationID is empty, are you not missing something like ConfigurationID = $GUID in your configuration file?

  • #26886

    Juris Krumins
    Participant

    As far as I know ConfigurationID indicates a GUID which is used to get a particular configuration file from a server set up as a “pull” server. In my case I use PUSH mode, so it's not applicable.

You must be logged in to reply to this topic.