Running the new wizard version, 2.5.0.0, and we are now getting an exception in the log file but the wizard shows a success message. It does create an XML file, but when we try to import that into Intune, we get an error and it fails to import due to an invalid XML file.
Here is a snippet from the log file - Exception encountered in ConvertPolicyToBinary(): System.Management.Automation.CmdletInvocationException: The 'SignerId' attribute is invalid - The value 'ID_SIGNER_9' is invalid according to its datatype 'urn:schemas-microsoft-com:sipolicy:SignerIdType' - The Pattern constraint failed.
When I uninstalled version 2.5.0.0 and reinstalled version 2.4.4.0, the XML created successfully and we were able to do the import.
Lastly, this invalid XML was only occurring when we added a custom allow or deny rule on the final tab. With no custom rules, the wizard did work as expected.
Running the new wizard version, 2.5.0.0, and we are now getting an exception in the log file but the wizard shows a success message. It does create an XML file, but when we try to import that into Intune, we get an error and it fails to import due to an invalid XML file.
Here is a snippet from the log file - Exception encountered in ConvertPolicyToBinary(): System.Management.Automation.CmdletInvocationException: The 'SignerId' attribute is invalid - The value 'ID_SIGNER_9' is invalid according to its datatype 'urn:schemas-microsoft-com:sipolicy:SignerIdType' - The Pattern constraint failed.
When I uninstalled version 2.5.0.0 and reinstalled version 2.4.4.0, the XML created successfully and we were able to do the import.
Lastly, this invalid XML was only occurring when we added a custom allow or deny rule on the final tab. With no custom rules, the wizard did work as expected.