Server 2019 Get-DSCConfigurationStatus blank response

Welcome Forums DSC (Desired State Configuration) Server 2019 Get-DSCConfigurationStatus blank response

This topic contains 1 reply, has 1 voice, and was last updated by

 
Participant
2 months, 1 week ago.

  • Author
    Posts
  • #170506

    Participant
    Topics: 4
    Replies: 8
    Points: -5
    Rank: Member

    Hello,

    Upgrading our server farm to 2019 and I've noticed a few occasions when the DSC has applied successfully (i.e. there is a current.mof) that Get-DSCConfigurationStatus returns $null:

    PS C:\Users\Rob> $x = get-dscconfigurationstatus -verbose
    VERBOSE: An LCM method call arrived from computer SVR003 with user sid
    S-1-5-21-0000000000-0000000000-000000000-0000.
    VERBOSE: [SVR003]: LCM: [ End GetStatus] in 0.0000 seconds.
    PS C:\Users\Rob> $x |gm
    gm : You must specify an object for the Get-Member cmdlet.
    PS C:\Users\Rob> Test-Path C:\Windows\System32\Configuration\Current.mof
    True

    The event viewer (Microsoft\Windows\Desired State Configuration\Operational) shows:

    WarningMessage LCM failed to retrieve the configuration status for file: C:\Windows\system32\configuration\ConfigurationStatus\{78D398EF-BDA1-11E9-9782-588A5AACB812}-0.mof

    But I can't see any reason for it. The machine is freshly built, before I started diagnosing nobody had ever logged on, we don't run any AntiVirus or other machine-breaking software.

    I'm not really sure how to debug further! Any ideas?

    Thanks,
    Rob

  • #170509

    Participant
    Topics: 4
    Replies: 8
    Points: -5
    Rank: Member

    Quick follow up, the MOF that it's looking for doesn't actually exist:

    PS C:\Windows\System32\Configuration\ConfigurationStatus> ls

    Directory: C:\Windows\System32\Configuration\ConfigurationStatus

    Mode LastWriteTime Length Name
    —- ————- —— —-
    -a—- 13/08/2019 09:08 614 {78D398EF-BDA1-11E9-9782-588A5AACB812}-0.details.json
    -a—- 13/08/2019 09:23 614 {9147BE40-BDA3-11E9-9782-588A5AACB812}-0.details.json
    -a—- 13/08/2019 09:23 614 {9147BE41-BDA3-11E9-9782-588A5AACB812}-0.details.json
    -a—- 13/08/2019 08:33 2026 {AFDCD936-BD9C-11E9-977F-588A5AACB814}-0.details.json
    -a—- 13/08/2019 08:33 3524 {AFDCD936-BD9C-11E9-977F-588A5AACB814}-0.mof
    -a—- 13/08/2019 08:33 614 {AFDCD937-BD9C-11E9-977F-588A5AACB814}-0.details.json
    -a—- 13/08/2019 08:40 332452 {BB30BF93-BD9C-11E9-977F-588A5AACB814}-0.details.json
    -a—- 13/08/2019 08:40 127240 {BB30BF93-BD9C-11E9-977F-588A5AACB814}-0.mof
    -a—- 13/08/2019 08:47 195572 {BB30BF93-BD9C-11E9-977F-588A5AACB814}-1.details.json
    -a—- 13/08/2019 08:47 132206 {BB30BF93-BD9C-11E9-977F-588A5AACB814}-1.mof
    -a—- 13/08/2019 08:51 209998 {BB30BF93-BD9C-11E9-977F-588A5AACB814}-2.details.json
    -a—- 13/08/2019 08:51 129538 {BB30BF93-BD9C-11E9-977F-588A5AACB814}-2.mof
    -a—- 13/08/2019 08:55 198072 {BB30BF93-BD9C-11E9-977F-588A5AACB814}-3.details.json
    -a—- 13/08/2019 08:55 121660 {BB30BF93-BD9C-11E9-977F-588A5AACB814}-3.mof

    Which seems mighty odd!

    I've got the exact same problem on 2 different servers at the moment, both freshly built on Server 2019 with:

    Source Description HotFixID InstalledBy InstalledOn
    —— ———– ——– ———– ———–
    DEMOIIS003 Update KB4506998 ... 12/08/2019 00:00:00
    DEMOIIS003 Security Update KB4470788 12/03/2019 00:00:00
    DEMOIIS003 Security Update KB4503308 ... 12/08/2019 00:00:00
    DEMOIIS003 Security Update KB4512937 ... 12/08/2019 00:00:00
    DEMOIIS003 Security Update KB4507469 ... 12/08/2019 00:00:00

     

You must be logged in to reply to this topic.