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
After extracting a policy of type IntuneDeviceConfigurationPolicyMacOS from one tenant and applying it to another it givens the error message below. In fact using the example file 1-ConfigureIntuneDeviceConfigurationPolicyMacOS.ps1 from the project gives exactly the same problem, so that's the one I'm sharing here.
Verbose logs showing the problem
[ModelValidationFailure] : An unexpected 'StartArray' node was found when reading from the JSON reader. A 'PrimitiveValue' node was expected. Error found near: ice restriction","@odata.type":"#microsoft.management.services.api.macOSGeneralDeviceConfiguration"} <---+ CategoryInfo : InvalidOperation: ({ body = Micros...Configuration }:) [], CimException
+ FullyQualifiedErrorId: ModelValidationFailure,Microsoft.Graph.Beta.PowerShell.Cmdlets.NewMgBetaDeviceManagementDeviceConfiguration_Create
+ PSComputerName : localhost
Suggested solution to the issue
It looks like almost all of the properties of this resource should be sent nested inside of AdditionalProperties, instead they are being sent as main and independent properties of their own which the backend receives as JSON and doesn't know how to parse them.
That being said the solution would be to send those properties inside AdditionalProperties
The DSC configuration that is used to reproduce the issue (as detailed as possible)
Details of the scenario you tried and the problem that is occurring
After extracting a policy of type IntuneDeviceConfigurationPolicyMacOS from one tenant and applying it to another it givens the error message below. In fact using the example file 1-ConfigureIntuneDeviceConfigurationPolicyMacOS.ps1 from the project gives exactly the same problem, so that's the one I'm sharing here.
Verbose logs showing the problem
Suggested solution to the issue
It looks like almost all of the properties of this resource should be sent nested inside of AdditionalProperties, instead they are being sent as main and independent properties of their own which the backend receives as JSON and doesn't know how to parse them.
That being said the solution would be to send those properties inside AdditionalProperties
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
OsName : Microsoft Windows 10 Enterprise OsOperatingSystemSKU : EnterpriseEdition OsArchitecture : 64-bit WindowsVersion : 2009 WindowsBuildLabEx : 19041.1.amd64fre.vb_release.191206-1406 OsLanguage : en-US OsMuiLanguages : {en-US}
Version of the DSC module that was used ('dev' if using current dev branch)
1.23.726.1
The text was updated successfully, but these errors were encountered: