From 1f039888d74a08f7b7aac0f1474b130473ada5f7 Mon Sep 17 00:00:00 2001 From: Doug Eby Date: Thu, 30 Nov 2017 18:36:16 -0800 Subject: [PATCH] added WM in 1710 and hybrid for 1321366 --- sccm/core/plan-design/changes/whats-new-in-version-1710.md | 6 +++++- .../whats-new-in-hybrid-mobile-device-management.md | 3 +++ 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/sccm/core/plan-design/changes/whats-new-in-version-1710.md b/sccm/core/plan-design/changes/whats-new-in-version-1710.md index 628d1988bb..10460471f2 100644 --- a/sccm/core/plan-design/changes/whats-new-in-version-1710.md +++ b/sccm/core/plan-design/changes/whats-new-in-version-1710.md @@ -62,7 +62,7 @@ Beginning with this release, you can use the Configuration Manager console to id See [How to manage clients in System Center Configuration Manager](/sccm/core/clients/manage/manage-clients#restart-clients) - + ## Application Management @@ -127,6 +127,10 @@ For more information, see [How to configure client settings in System Center Con ## Mobile device management +### Actions for non-compliance + +You can now configure a time-ordered sequence of actions that are applied to devices that fall out of compliance. For example, you can notify users of non-compliant devices via e-mail or mark those devices non-compliant. For details, see [Set up actions for non-compliance](/sccm/mdm/deploy-use/actions-for-noncompliance). + ### Windows 10 ARM64 device support diff --git a/sccm/mdm/understand/whats-new-in-hybrid-mobile-device-management.md b/sccm/mdm/understand/whats-new-in-hybrid-mobile-device-management.md index 00a25d2b6d..dc1cc0d836 100644 --- a/sccm/mdm/understand/whats-new-in-hybrid-mobile-device-management.md +++ b/sccm/mdm/understand/whats-new-in-hybrid-mobile-device-management.md @@ -71,6 +71,9 @@ We have added **Ownership Type** to the Device Details screen on the Company Por ### New in Configuration Manager (current branch) +- **Actions for non-compliance** + You can now configure a time-ordered sequence of actions that are applied to devices that fall out of compliance. For example, you can notify users of non-compliant devices via e-mail or mark those devices non-compliant. For details, see [Set up actions for non-compliance](/sccm/mdm/deploy-use/actions-for-noncompliance). + - **New mobile application management policy settings** The following settings have been added to the mobile application management policy settings: - **Disable contact sync**: Prevents the app from saving data to the native Contacts app on the device.