Skip to main content

Error 2016281112: VPN Profile Remediation Failed

Error Message

Remediation Failed (2016281112)

Error Details​

PropertyValue
Error Code (Dec)2016281112
ComponentDevice Configuration
Profile TypeCustom VPN (OMA-URI)

Description​

info

This error occurs when using custom VPN profiles configured through OMA-URI settings in Windows 10 device configuration profiles. While the VPN connection functions correctly, Intune reports a remediation failure due to XML formatting differences between the policy and client response.

Common Causes​

XML Response Mismatch​

XML formatting discrepancies often trigger remediation failures. Client response XML differs from policy XML. Format variations cause validation issues. Windows 10 response formatting doesn't match Intune policy exactly. Understanding XML matching requirements is crucial for troubleshooting.

Profile Configuration Method​

Configuration approach can affect remediation reporting. Custom OMA-URI profiles trigger format validation. Standard VPN profiles handle formatting differently. Profile type selection impacts error reporting. These configuration factors influence remediation status.

Resolution Steps​

1️⃣ Option A: Ignore Error​

If VPN is functioning:

  1. Verify VPN connection works
  2. Confirm users can access resources
  3. Document working status
  4. Monitor for actual issues

2️⃣ Option B: Use Standard Profile​

Switch to standard configuration:

  1. Create new VPN profile
  2. Use built-in VPN settings
  3. Avoid custom OMA-URI
  4. Test deployment
  5. Verify remediation status

3️⃣ Validation​

After implementing changes:

  1. Monitor profile status
  2. Test VPN functionality
  3. Verify user access
  4. Document resolution

Best Practices​

👨‍💻 For IT Administrators​

When possible, use standard VPN profiles instead of custom OMA-URI configurations. This prevents XML formatting issues and improves profile management. Standard profiles provide better validation and reporting accuracy.

📱 For Deployment​

Consider impact on reporting when choosing profile types. Document known issues for custom profiles. Maintain clear communication about error status. Plan migration to standard profiles where feasible.

Troubleshooting Tips​

Profile Management

When using custom VPN profiles, focus on functionality verification. Don't rely solely on remediation status. Test actual VPN connections. Monitor user experience. Document working configurations.

Version Considerations

This is a known issue in Windows 10 versions up to 1809. Future Windows releases may resolve the XML formatting mismatch. Consider Windows version when troubleshooting.

Additional Notes​

💡 Error can be safely ignored if VPN works

⚙️ Standard profiles avoid this issue

⚠️ Known Windows 10 limitation

📱 Functionality over reporting

Intune Docs

Windows Guide

OMA URI

Profile Configuration Guide​

  1. Status Assessment

    • Check VPN functionality
    • Review error impact
    • Document working state
    • Plan resolution

  2. Profile Selection

    • Evaluate profile types
    • Consider standard options
    • Review requirements
    • Choose approach

  3. Implementation Steps

    • Configure profile
    • Test deployment
    • Verify access
    • Monitor status
Best Practice

Focus on VPN functionality rather than remediation status when using custom OMA-URI profiles, or switch to standard VPN profiles to avoid the error entirely.