From 12d7c1ba7bbe49a1bd5afa577276910817ff25d9 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 27 Jul 2016 12:18:09 -0700 Subject: [PATCH] Updated important note with newer version number --- 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 e8b8dbf122..f1bad6a10c 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 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. +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. ## 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.