You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: memdocs/configmgr/core/clients/manage/remote-control/prerequisites-for-remote-control.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,8 +55,6 @@ Before you can run reports for remote control, install the reporting services po
55
55
56
56
- Permitted viewers must be given permission to use remote control by adding these users to the **Permitted viewers of Remote Control and Remote Assistance** list in the **Remote Tools** client settings.
57
57
58
-
- If the user account that you use for remote control is joined to Azure Active Directory (Azure AD), you may need to set a group policy setting on the client to be remote-controlled. In the policy path **Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options**, enable the following policy: **Network security: Allow PKU2U authentication requests to this computer to use online identities**. Also add the Azure AD user account to the local **Remote Desktop Users** group on the client.
59
-
60
58
For more information, see [Configure role-based administration](../../../servers/deploy/configure/configure-role-based-administration.md).
Copy file name to clipboardExpand all lines: memdocs/intune/configuration/device-restrictions-android-for-work.md
+21-1Lines changed: 21 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ keywords:
7
7
author: MandiOhlinger
8
8
ms.author: mandia
9
9
manager: dougeby
10
-
ms.date: 03/10/2022
10
+
ms.date: 03/21/2022
11
11
ms.topic: conceptual
12
12
ms.service: microsoft-intune
13
13
ms.subservice: configuration
@@ -97,6 +97,20 @@ For corporate-owned devices with a work profile, some settings only apply in the
97
97
-**Automatic**: Updates are automatically installed without user interaction. Setting this policy immediately installs any pending updates.
98
98
-**Postponed**: Updates are postponed for 30 days. At the end of the 30 days, Android prompts users to install the update. It's possible for device manufacturers or carriers to prevent (exempt) important security updates from being postponed. An exempted update shows a system notification to users on the device.
99
99
-**Maintenance window**: Installs updates automatically during a daily maintenance window that you set in Intune. Installation tries daily for 30 days, and can fail if there's insufficient space or battery levels. After 30 days, Android prompts users to install. This window is also used to install updates for Play apps. Use this option for dedicated devices, such as kiosks, as single-app dedicated device foreground apps can be updated.
100
+
-**Freeze periods for system updates**: Optional. When you set the **System update** setting to **Automatic**, **Postponed**, or **Maintenance window**, use this setting to create a freeze period:
101
+
102
+
-**Start date**: Enter the start date in `MM/DD` format, up to 90 days long. For example, enter `11/15` to start the freeze period on November 15.
103
+
-**End date**: Enter the end date in `MM/DD` format, up to 90 days long. For example, enter `01/15` to end the freeze period on January 15.
104
+
105
+
During this annual freeze period, all incoming system updates and security patches are blocked.
106
+
107
+
When a device's clock is outside the freeze period, the device continues to receive updates based on your **System update** setting.
108
+
109
+
To set multiple annually recurring freeze periods, make sure the freeze periods are separated by at least 60 days.
110
+
111
+
This setting applies to:
112
+
113
+
- Android 9.0 and newer
100
114
101
115
#### Fully managed and dedicated devices
102
116
@@ -354,6 +368,12 @@ Use these settings to configure a kiosk-style experience on your dedicated devic
354
368
-**Number of seconds the device is inactive before showing screen saver**: Choose how long the device is idle before showing the screensaver. Enter a value between 1-9999999 seconds. Default is `30` seconds. You must enter a number greater than zero (`0`).
355
369
-**Detect media before starting screen saver**: **Enable** (default) doesn't show the screen saver if audio or video is playing on the device. When set to **Not configured** (default), Intune doesn't change or update this setting. By default, the OS might show the screen saver, even if audio or video is playing.
356
370
371
+
> [!NOTE]
372
+
> Managed Home Screen starts the screensaver whenever the lock screen appears:
373
+
>
374
+
> - If the system's lock screen timeout is longer than the number of seconds for device to show the screensaver, then the screensaver shows until the lock screen appears.
375
+
> - If the system's lock screen timeout is shorter than the number of seconds the device is inactive, then the screensaver shows as soon as the device's lock screen appears.
376
+
357
377
-**MHS Sign-in screen**: **Enable** shows a sign-in screen on the Managed Home Screen. When set to **Not configured** (default), Intune doesn't change or update this setting. This sign-in screen and related settings are intended for use on dedicated devices enrolled with AAD Shared device mode.
0 commit comments