From 040c63c112e201579f76b78e2b714b02af2ee7a8 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 8 Nov 2016 10:12:37 -0800 Subject: [PATCH] Fixing formatting --- windows/keep-secure/create-vpn-and-wip-policy-using-intune.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/keep-secure/create-vpn-and-wip-policy-using-intune.md b/windows/keep-secure/create-vpn-and-wip-policy-using-intune.md index 6a00cb0511..45ed365fe2 100644 --- a/windows/keep-secure/create-vpn-and-wip-policy-using-intune.md +++ b/windows/keep-secure/create-vpn-and-wip-policy-using-intune.md @@ -91,7 +91,7 @@ The final step to making your VPN configuration work with WIP, is to link your t - **Data type.** Pick the **String** data type. - - **OMA-URI.** Type `./Vendor/MSFT/VPNv2/VPNProfileName/EDPModeId`, replacing *VPNProfileName* with the name you gave to your VPN policy. For example, `./Vendor/MSFT/VPNv2/W10-Checkpoint-VPN1/EDPModeId`. + - **OMA-URI.** Type `./Vendor/MSFT/VPNv2//EDPModeId`, replacing <*VPNProfileName*> with the name you gave to your VPN policy. For example, `./Vendor/MSFT/VPNv2/W10-Checkpoint-VPN1/EDPModeId`. - **Value.** Your fully-qualified domain that should be used by the OMA-URI setting.