You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Details of the scenario you tried and the problem that is occurring
When managing IntuneDeviceEnrollmentPlatformRestriction, on module versions greater than 1.23.510.1 the Test-TargetResource returns false - it should be true.
Setting the properties still works as expected, but every run will set it (rather than only in case of config drift/change) because the test function doesn't return true.
Verbose logs showing the problem
1.23.614.1:
VERBOSE: [fv-az804-154]: LCM: [ Start Set ]
VERBOSE: [fv-az804-154]: LCM: [ Start Resource ]
[[IntuneDeviceEnrollmentPlatformRestriction]Default_Device_Enrollment_Platform_Restriction]
VERBOSE: [fv-az804-154]: LCM: [ Start Test ]
[[IntuneDeviceEnrollmentPlatformRestriction]Default_Device_Enrollment_Platform_Restriction]
VERBOSE: [fv-az804-154]:
[[IntuneDeviceEnrollmentPlatformRestriction]Default_Device_Enrollment_Platform_Restriction] Testing configuration of
Device Enrollment Platform Restriction {All users and all devices}
VERBOSE: [fv-az804-154]:
[[IntuneDeviceEnrollmentPlatformRestriction]Default_Device_Enrollment_Platform_Restriction] Checking for the Intune
Device Enrollment Restriction {All users and all devices}
VERBOSE: [fv-az804-154]:
[[IntuneDeviceEnrollmentPlatformRestriction]Default_Device_Enrollment_Platform_Restriction] Found Device Enrollment
Platform Restriction with Name {All users and all devices}
VERBOSE: [fv-az804-154]:
[[IntuneDeviceEnrollmentPlatformRestriction]Default_Device_Enrollment_Platform_Restriction] Configuration drift -
Complex object: {Target is null}
VERBOSE: [fv-az804-154]:
[[IntuneDeviceEnrollmentPlatformRestriction]Default_Device_Enrollment_Platform_Restriction] Test-TargetResource
returned False
1.23.510.1:
VERBOSE: [fv-az876-32]: LCM: [ Start Set ]
VERBOSE: [fv-az876-32]: LCM: [ Start Resource ]
[[IntuneDeviceEnrollmentPlatformRestriction]Default_Device_Enrollment_Platform_Restriction]
VERBOSE: [fv-az876-32]: LCM: [ Start Test ]
[[IntuneDeviceEnrollmentPlatformRestriction]Default_Device_Enrollment_Platform_Restriction]
VERBOSE: [fv-az876-32]:
[[IntuneDeviceEnrollmentPlatformRestriction]Default_Device_Enrollment_Platform_Restriction] Testing configuration of
Device Enrollment Platform Restriction {All users and all devices}
VERBOSE: [fv-az876-32]:
[[IntuneDeviceEnrollmentPlatformRestriction]Default_Device_Enrollment_Platform_Restriction] Checking for the Intune
Device Enrollment Restriction {All users and all devices}
VERBOSE: [fv-az876-32]:
[[IntuneDeviceEnrollmentPlatformRestriction]Default_Device_Enrollment_Platform_Restriction] Found Device Enrollment
Platform Restriction with Name {All users and all devices}
VERBOSE: [fv-az876-32]:
[[IntuneDeviceEnrollmentPlatformRestriction]Default_Device_Enrollment_Platform_Restriction] Test-TargetResource
returned True
Details of the scenario you tried and the problem that is occurring
When managing
IntuneDeviceEnrollmentPlatformRestriction
, on module versions greater than1.23.510.1
theTest-TargetResource
returns false - it should be true.Setting the properties still works as expected, but every run will set it (rather than only in case of config drift/change) because the test function doesn't return true.
Verbose logs showing the problem
1.23.614.1:
1.23.510.1:
Suggested solution to the issue
There were some changes to prevent sending windows mobile data to the api - perhaps this has broken the test function? https://github.com/microsoft/Microsoft365DSC/blob/9777ebc0fc0506edea3ec7f8042edfb7db4d24f9/Modules/Microsoft365DSC/DSCResources/MSFT_IntuneDeviceEnrollmentPlatformRestriction/MSFT_IntuneDeviceEnrollmentPlatformRestriction.psm1
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
Tested on Azure DevOps
windows-2022
runner, and the belowVersion of the DSC module that was used ('dev' if using current dev branch)
Broken on 1.23.614.1, 1.23.607.1, 1.23.524.1 and 1.23.517.1
Working on 1.23.510.1
The text was updated successfully, but these errors were encountered: