From cbaf7404b7faec2533fb477be770412cf44d37e7 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Thu, 28 Jul 2016 07:28:23 -0700 Subject: [PATCH] Changed EDP to WIP in new note --- windows/keep-secure/create-wip-policy-using-sccm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/keep-secure/create-wip-policy-using-sccm.md b/windows/keep-secure/create-wip-policy-using-sccm.md index f1bad6a10c..373a196ebf 100644 --- a/windows/keep-secure/create-wip-policy-using-sccm.md +++ b/windows/keep-secure/create-wip-policy-using-sccm.md @@ -20,7 +20,7 @@ author: eross-msft System Center Configuration Manager 2016 helps you create and deploy your Windows Information Protection (WIP) policy, including letting you choose your protected apps, your WIP-protection mode, and how to find enterprise data on the network. >**Important**
-If you previously created an EDP policy using System Center Configuration Manager version 1511 or 1602, you’ll need to recreate it using version 1606 or later. Editing an EDP policy created in version 1511 or 1602 is not supported in later versions and there is no migration path between older and newer EDP policies. +If you previously created an WIP policy using System Center Configuration Manager version 1511 or 1602, you’ll need to recreate it using version 1606 or later. Editing a WIP policy created in version 1511 or 1602 is not supported in later versions and there is no migration path between older and newer WIP policies. ## Add an WIP policy After you’ve installed and set up System Center Configuration Manager for your organization, you must create a configuration item for WIP, which in turn becomes your WIP policy.