From 9db1013471efd5421902d19be7222940d25426ea Mon Sep 17 00:00:00 2001 From: Shujing Zhang Date: Thu, 7 Nov 2024 15:18:39 +0800 Subject: [PATCH 1/7] Delete .openpublishing.build.ps1 --- .openpublishing.build.ps1 | 17 ----------------- 1 file changed, 17 deletions(-) delete mode 100644 .openpublishing.build.ps1 diff --git a/.openpublishing.build.ps1 b/.openpublishing.build.ps1 deleted file mode 100644 index aadef762022..00000000000 --- a/.openpublishing.build.ps1 +++ /dev/null @@ -1,17 +0,0 @@ -param( - [string]$buildCorePowershellUrl = "https://opbuildstorageprod.blob.core.windows.net/opps1container/.openpublishing.buildcore.ps1", - [string]$parameters -) -# Main -$errorActionPreference = 'Stop' - -# Step-1: Download buildcore script to local -echo "download build core script to local with source url: $buildCorePowershellUrl" -$repositoryRoot = Split-Path -Parent $MyInvocation.MyCommand.Definition -$buildCorePowershellDestination = "$repositoryRoot\.openpublishing.buildcore.ps1" -Invoke-WebRequest $buildCorePowershellUrl -OutFile "$buildCorePowershellDestination" - -# Step-2: Run build core -echo "run build core script with parameters: $parameters" -& "$buildCorePowershellDestination" "$parameters" -exit $LASTEXITCODE From 19feb98d49cc39d781dfe04e87404ab5e0229fc8 Mon Sep 17 00:00:00 2001 From: joshg Date: Thu, 7 Nov 2024 08:36:39 -0600 Subject: [PATCH 2/7] Update mde-security-integration.md Article shows Server Core 2019 as unsupported. Changed the line to read Windows Server Core 2016 and earlier --- memdocs/intune/protect/mde-security-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/memdocs/intune/protect/mde-security-integration.md b/memdocs/intune/protect/mde-security-integration.md index e43a6073049..40b3923dadb 100644 --- a/memdocs/intune/protect/mde-security-integration.md +++ b/memdocs/intune/protect/mde-security-integration.md @@ -141,7 +141,7 @@ To confirm the version of the Defender agent, in the Defender portal go to the d Security settings management doesn't work on and isn't supported with the following devices: -- Windows Server Core 2019 and earlier +- Windows Server Core 2016 and earlier - Non-persistent desktops, like Virtual Desktop Infrastructure (VDI) clients - Azure Virtual Desktop (AVD and formerly Windows Virtual Desktop, WVD) - 32-bit versions of Windows From a03b45e75813774ed86a56557a1c666d8d37e36e Mon Sep 17 00:00:00 2001 From: Laura Newsad Date: Thu, 7 Nov 2024 12:56:07 -0500 Subject: [PATCH 3/7] Update encrypt-your-device-android.md Freshness check --- .../user-help/encrypt-your-device-android.md | 37 ++++++++----------- 1 file changed, 15 insertions(+), 22 deletions(-) diff --git a/memdocs/intune/user-help/encrypt-your-device-android.md b/memdocs/intune/user-help/encrypt-your-device-android.md index 16c01c3c75e..4c8de2a40f8 100644 --- a/memdocs/intune/user-help/encrypt-your-device-android.md +++ b/memdocs/intune/user-help/encrypt-your-device-android.md @@ -7,7 +7,7 @@ keywords: author: lenewsad ms.author: lanewsad manager: dougeby -ms.date: 09/23/2020 +ms.date: 11/07/2024 ms.topic: end-user-help ms.service: microsoft-intune ms.subservice: end-user @@ -35,16 +35,16 @@ Device encryption protects your files and folders from unauthorized access if yo Before you can access school or work resources, your organization might require you to: -* [Encrypt your device](#encrypt-device) -* [Enable secure startup](#enable-secure-startup) -* [Set startup passcode, PIN, or other authentication method](#set-startup-passcode) +* Encrypt your device +* Enable secure startup +* Set a lock screen and startup PIN > [!Note] -> Certain Android devices from Huawei, Vivo, and OPPO can't be encrypted. For more information, see [Device encrypted but app says otherwise](your-device-appears-encrypted-but-cp-says-otherwise-android.md). +> Certain Android devices from Huawei, Vivo, and OPPO can't be encrypted. For more information, see [Device encrypted but app says otherwise](your-device-appears-encrypted-but-cp-says-otherwise-android.md). ## Encrypt device -Follow these steps to encrypt your device. Your device may restart several times. The name and location of the encryption option will vary depending on your device manufacturer and Android version. +Follow these steps to encrypt your device. Your device may restart more than once. The name and location of the encryption option varies depending on your device manufacturer and Android version. These steps don't apply to newer Android devices, which are are encrypted by default when you set up a lock screen. 1. Open the **Settings** app. 2. Type **security** or **encrypt** in the search bar to find related settings. @@ -56,9 +56,7 @@ Follow these steps to encrypt your device. Your device may restart several times ## Enable secure startup -Secure startup protects your device by requiring a password or PIN each time the device is turned on. - -The name and location of the secure startup option can vary depending on your device manufacturer and Android version. +Secure startup protects your device by requiring a password or PIN each time the device is turned on. The name and location of the secure startup option can vary depending on your device manufacturer and Android version. 1. Open the **Settings** app. 2. Type **secure startup** in the app's search bar. @@ -69,27 +67,22 @@ The name and location of the secure startup option can vary depending on your de * Company Portal app users: Open the app, select your device, and then tap **Check device settings**. * Microsoft Intune app users: Open the app, wait until the screen loads, and then your encryption status should change to compliant. +## Set lock screen -## Set startup passcode -Once you encrypt your device and enable secure startup, you'll be prompted to set your device PIN, password, or other authentication method (if allowed by your organization). Completing that step will satisfy the startup passcode requirement. - -To set a lock screen on your device or change the type that you're currently using: - -1. Open the **Settings** app. -2. Type **screen lock** in the app's search bar. -3. Tap **Screen lock type**. -4. Tap the screen lock type you want to use and follow the onscreen instructions to confirm. +Add a device PIN, password, or other authentication method (if allowed by your organization) to the device. The lock screen appears and prompts for your credentials when you turn on the device and when the device is idle. To set up a lock screen, go to **Settings** > **Security and privacy** > **Lock screen**. ## Troubleshoot **Issue**: The encryption button is disabled. **Thing to try**: -* Make sure your device is fully charged and plugged in. Encryption may take a while and requires a full battery. + Make sure your device is fully charged and plugged in. Encryption could take a while and requires a full battery. **Issue**: You see a message saying that you still need to encrypt your device. -**Things to try**: - * [Set a lock screen](#set-startup-passcode) on your device. - * [Enable secure startup](#enable-secure-startup). +**Things to try**: + + * Set a lock screen on your device. + * + * Enable secure startup. Still need help? Contact your IT support person. Check the [Company Portal website](https://go.microsoft.com/fwlink/?linkid=2010980) or app for your organization's contact information. From f7584ffc25cdf47737876aa1a396511c6fd946e7 Mon Sep 17 00:00:00 2001 From: Laura Newsad Date: Thu, 7 Nov 2024 12:57:32 -0500 Subject: [PATCH 4/7] Update check-compliance-aosp.md Freshness check --- memdocs/intune/user-help/check-compliance-aosp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/memdocs/intune/user-help/check-compliance-aosp.md b/memdocs/intune/user-help/check-compliance-aosp.md index ceea527c182..e918174513e 100644 --- a/memdocs/intune/user-help/check-compliance-aosp.md +++ b/memdocs/intune/user-help/check-compliance-aosp.md @@ -7,7 +7,7 @@ keywords: author: lenewsad ms.author: lanewsad manager: dougeby -ms.date: 11/15/2023 +ms.date: 11/07/2024 ms.topic: end-user-help ms.service: microsoft-intune ms.subservice: end-user From 1174d45d816b5ed0f5c49d25adb25e8f12c498db Mon Sep 17 00:00:00 2001 From: Laura Newsad Date: Thu, 7 Nov 2024 14:46:51 -0500 Subject: [PATCH 5/7] Update check-compliance-aosp.md remove extra space --- memdocs/intune/user-help/check-compliance-aosp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/memdocs/intune/user-help/check-compliance-aosp.md b/memdocs/intune/user-help/check-compliance-aosp.md index e918174513e..e9ab726065b 100644 --- a/memdocs/intune/user-help/check-compliance-aosp.md +++ b/memdocs/intune/user-help/check-compliance-aosp.md @@ -50,7 +50,7 @@ Complete these steps to check compliance and refresh the device settings status 2. Tap **Devices** and then select your device. -3. Under **Device Settings Status**, tap **Refresh**. Wait while the Intune app checks device settings and updates the device settings status. +3. Under **Device Settings Status**, tap **Refresh**. Wait while the Intune app checks device settings and updates the device settings status. 4. If your device is noncompliant and you're required to make changes, you receive a compliance notification in the Intune app. Tap the notification for more information. From 869cf5f168f108482907a9d5754facecbb1d2b23 Mon Sep 17 00:00:00 2001 From: Laura Newsad Date: Thu, 7 Nov 2024 14:48:16 -0500 Subject: [PATCH 6/7] Update encrypt-your-device-android.md Removed extra word --- memdocs/intune/user-help/encrypt-your-device-android.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/memdocs/intune/user-help/encrypt-your-device-android.md b/memdocs/intune/user-help/encrypt-your-device-android.md index 4c8de2a40f8..005159f5a76 100644 --- a/memdocs/intune/user-help/encrypt-your-device-android.md +++ b/memdocs/intune/user-help/encrypt-your-device-android.md @@ -44,7 +44,7 @@ Before you can access school or work resources, your organization might require ## Encrypt device -Follow these steps to encrypt your device. Your device may restart more than once. The name and location of the encryption option varies depending on your device manufacturer and Android version. These steps don't apply to newer Android devices, which are are encrypted by default when you set up a lock screen. +Follow these steps to encrypt your device. Your device may restart more than once. The name and location of the encryption option varies depending on your device manufacturer and Android version. These steps don't apply to newer Android devices, which are encrypted by default when you set up a lock screen. 1. Open the **Settings** app. 2. Type **security** or **encrypt** in the search bar to find related settings. From c728efefcfbb143f56075b7295b647e067794342 Mon Sep 17 00:00:00 2001 From: Laura Newsad Date: Thu, 7 Nov 2024 15:08:35 -0500 Subject: [PATCH 7/7] Update sync-device-aosp.md Freshness check --- memdocs/intune/user-help/sync-device-aosp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/memdocs/intune/user-help/sync-device-aosp.md b/memdocs/intune/user-help/sync-device-aosp.md index 929b004ee41..9dd057152ec 100644 --- a/memdocs/intune/user-help/sync-device-aosp.md +++ b/memdocs/intune/user-help/sync-device-aosp.md @@ -7,7 +7,7 @@ keywords: author: lenewsad ms.author: lanewsad manager: dougeby -ms.date: 09/20/2022 +ms.date: 11/07/2024 ms.topic: end-user-help ms.service: microsoft-intune ms.subservice: end-user