AccountPolicy: Current Configuration Does Not Exist

Details of the scenario you tried and the problem that is occurring

I'm attempting to test an AccountPolicy resource ahead of a deployment to Azure VM using Automanage Machine Configration. When I test locally with Get-GuestConfigurationPackageComplianceStatus I get the following error:

Write-Error: Job 282f4638-4d1f-41f4-97a0-54415c840d9a : MIResult: 6 Error Message: Current configuration does not exist. Execute Start-DscConfiguration command with -Path parameter to specify a configuration file and create a current configuration first. Message ID: MI RESULT 6 Error Category: 13 Error Code: 6 Error Type: MI

Running the suggested Start-DscConfiguration with the path to the MOF extracted from the guest configuration .zip provides no output. Running Get-DscConfiguration afterwards returns a similar error to above.

Configurations using AuditPolicyDsc or PsDscResources are okay. This error also pops up when a xPsDesiredStateConfiguration resource is used.

Verbose logs showing the problem

N/A

The DSC configuration that is used to reproduce the issue (as detailed as possible)

Configuration SecurityPolicyDSCSingleConfig {
    Import-DscResource -ModuleName 'SecurityPolicyDSC'
    AccountPolicy AccountPolicies {
        Name = 'PasswordPolicies'
        Enforce_password_history = 24
        Maximum_Password_Age = 42
        Minimum_Password_Age = 1
        Minimum_Password_Length = 8
        Password_must_meet_complexity_requirements = 'Enabled'
        Store_passwords_using_reversible_encryption = 'Disabled'
        Account_lockout_duration = 15
        Account_lockout_threshold = 5
        Reset_account_lockout_counter_after = 15
    }
}

SecurityPolicyDSCSingleConfig

The operating system the target node is running

OsName : Microsoft Windows Server 2022 Datacenter Azure Edition OsOperatingSystemSKU : 407 OsArchitecture : 64-bit WindowsVersion : 2009 WindowsBuildLabEx : 20348.1.amd64fre.fe_release.210507-1500 OsLanguage : en-US OsMuiLanguages : {en-US}

Version and build of PowerShell the target node is running

v7.3.8

Version of the DSC module that was used

v2.10.0.0

dsccommunity / SecurityPolicyDsc