From 44f94289d734a85a3cdd31c7ca86646a8c5e386e Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 27 Jul 2016 09:32:10 -0700 Subject: [PATCH] Updated the important note so it doesn't have to be changed with each version --- 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 3ae03d160b..e8b8dbf122 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 WIP policy using System Center Configuration Manager version 1511 or 1602 in the Insider Preview program, you’ll need to recreate it using version 1605 Tech Preview or later. Editing an WIP policy created in version 1511 or 1602 is not supported in version 1605 Tech Preview. There is no migration path between WIP policies across these versions. +If you previously created an EDP policy using System Center Configuration Manager version 1511 or 1602, you’ll need to recreate it using version 1605 Tech Preview 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. ## 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.