This issue is scheduled to be addressed in a future Windows 10 release. This is a known issue in all versions of Windows 10 up to and including Windows 10, version 1809. Another possible explanation is that the settings regarding TLS. If you create a standard profile, Intune does not generate the error message that is described in the Symptoms section. The solution to this particular problem is to upgrade the client software to the latest version. You can safely ignore this error because the connection works as expected.Īlternatively, you can create a standard VPN device configuration profile instead of using a custom profile that uses OMA-URI settings. If the XML differs between the policy and the client response, Intune interprets the mismatch as a remediation failure. This is how Intune verifies that the policy has been applied correctly. If the policy is applied successfully, the XML in the response should exactly match the XML in the policy. Contact the system administrator of the remote access server and. This issue occurs because, in certain scenarios, the response that is sent by the Windows 10 client includes XML that is formatted differently than the XML that is sent through the Intune policy. If it is running and the error message still appears, another VPN application on the workstation may need to be disabled or even uninstalled. I would also suggest you to change the DNS and check if webpages load. However, the profile reports a 2016281112 (Remediation Failed) error message in the Microsoft Endpoint Manager admin center. SymptomsĪfter you create and assign a device configuration profile that defines a custom VPN connection by using OMA-URI settings, Windows 10 clients receive the profile and can connect to the VPN endpoint successfully. This article discusses a 2016281112 (Remediation Failed) error message in Intune.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |