@ -79,7 +79,14 @@ For a local account, the domain name should be the device name. When Get is exec
The supported operations are Add, Delete, Get and Replace. When there's no configuration, the Get and Delete methods fail. When there's already a configuration for kiosk mode app, the Add method fails. The data pattern for Add and Replace is the same.
Added in Windows 10, version 1709. Specifies the settings that you can configure in the kiosk or device. This node accepts an AssignedAccessConfiguration xml as input to configure the device experience. For details about the configuration settings in the XML, see [Create a Windows 10 kiosk that runs multiple apps](/windows/configuration/lock-down-windows-10-to-specific-apps). Here's the schema for the [AssignedAccessConfiguration](#assignedaccessconfiguration-xsd).
Added in Windows 10, version 1709. Specifies the settings that you can configure in the kiosk or device. This node accepts an AssignedAccessConfiguration xml as input to configure the device experience. For more information about the configuration settings in the XML, see [Create a Windows 10 kiosk that runs multiple apps](/windows/configuration/lock-down-windows-10-to-specific-apps). For more information on the schema, see [AssignedAccessConfiguration](#assignedaccessconfiguration-xsd).
Updated in Windows 10, version 1909. Added Microsoft Edge kiosk mode support. This allows Microsoft Edge to be the specified kiosk application. For details about configuring Microsoft Edge kiosk mode, see [Configure a Windows 10 kiosk that runs Microsoft Edge](/DeployEdge/microsoft-edge-configure-kiosk-mode). Windows 10, version 1909 also allows for configuration of the breakout sequence. The breakout sequence specifies the keyboard shortcut that returns a kiosk session to the lock screen. The breakout sequence is defined with the format modifiers + keys. An example breakout sequence would look something like "shift+alt+a", where "shift" and "alt" are the modifiers and "a" is the key.
> [!Note]
> In Windows 10, version 1803 the Configuration node introduces single app kiosk profile to replace KioskModeApp CSP node. KioskModeApp node will be deprecated soon, so you should use the single app kiosk profile in config xml for Configuration node to configure public-facing single app Kiosk.
>
> Starting in Windows 10, version 1803 the KioskModeApp node becomes No-Op if Configuration node is configured on the device. That Add/Replace/Delete command on KioskModeApp node always returns SUCCESS to the MDM server if Configuration node is set, but the data of KioskModeApp will not take any effect on the device. Get command on KioskModeApp will return the configured JSON string even it’s not effective.
Enterprises can use this to easily configure and manage the curated lockdown experience.
@ -248,7 +255,7 @@ KioskModeApp Replace
## AssignedAccessConfiguration XSD
Below schema is for AssignedAccess Configuration up to Windows 10 1803 release.
The schema below is for AssignedAccess Configuration up to Windows 10 20H2 release.
```xml
<?xml version="1.0" encoding="utf-8"?>
@ -259,11 +266,13 @@ Below schema is for AssignedAccess Configuration up to Windows 10 1803 release.
@ -384,6 +411,7 @@ Below schema is for AssignedAccess Configuration up to Windows 10 1803 release.
<xs:simpleTypename="specialGroupType_t">
<xs:restrictionbase="xs:string">
<xs:enumerationvalue="Visitor"/>
<xs:enumerationvalue="DeviceOwner"/>
</xs:restriction>
</xs:simpleType>
@ -422,7 +450,7 @@ Below schema is for AssignedAccess Configuration up to Windows 10 1803 release.
</xs:all>
</xs:complexType>
</xs:element>
</xs:schema>
</xs:schema>);
```
Here's the schema for new features introduced in Windows 10 1809 release
@ -501,7 +529,32 @@ Schema for Windows 10 prerelease
</xs:schema>
```
To authorize a compatible configuration XML that includes 1809 or prerelease elements and attributes, always include the namespace of these add-on schemas, and decorate the attributes and elements accordingly with the namespace alias. For example, to configure auto-launch feature that is added in 1809 release, use below sample, notice an alias r1809 is given to the 201810 namespace for 1809 release, and the alias is tagged on AutoLaunch and AutoLaunchArguments inline.
The schema below is for features introduced in Windows 10, version 1909 which has added support for Microsoft Edge kiosk mode and breakout key sequence customization.
To authorize a compatible configuration XML that includes 1809 or prerelease elements and attributes, always include the namespace of these add-on schemas, and decorate the attributes and elements accordingly with the namespace alias. For example, to configure the auto-launch feature that's added in the 1809 release, use the below sample. Notice an alias r1809 is given to the 201810 namespace for the 1809 release, and the alias is tagged on AutoLaunch and AutoLaunchArguments inline.
```xml
<AssignedAccessConfiguration
@ -517,6 +570,7 @@ To authorize a compatible configuration XML that includes 1809 or prerelease ele
@ -568,6 +622,53 @@ To authorize a compatible configuration XML that includes 1809 or prerelease ele
</AssignedAccessConfiguration>
```
Example XML configuration for a Microsoft Edge kiosk. This Microsoft Edge kiosk is configured to launch www.bing.com on startup in a public browsing mode.
XML encoding (escaped) and CDATA of the XML in the Data node will both ensure that DM client can properly interpret the SyncML and send the configuration xml as string (in original format, unescaped) to AssignedAccess CSP to handle.
@ -22,8 +22,7 @@ You can download the DDF files from the links below:
- [Download all the DDF files for Windows 10, version 1703](https://download.microsoft.com/download/C/7/C/C7C94663-44CF-4221-ABCA-BC895F42B6C2/Windows10_1703_DDF_download.zip)
- [Download all the DDF files for Windows 10, version 1607](https://download.microsoft.com/download/2/3/E/23E27D6B-6E23-4833-B143-915EDA3BDD44/Windows10_1607_DDF.zip)
The XML below is for Windows 10, version 1803.
The XML below is for Windows 10, version 1909.
```xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE MgmtTree PUBLIC " -//OMA//DTD-DM-DDF 1.2//EN"
@ -50,7 +49,7 @@ The XML below is for Windows 10, version 1803.
<Permanent/>
</Scope>
<DFType>
<MIME>com.microsoft/2.0/MDM/AssignedAccess</MIME>
<MIME>com.microsoft/4.0/MDM/AssignedAccess</MIME>
</DFType>
</DFProperties>
<Node>
@ -208,4 +207,3 @@ This node supports Add, Delete, Replace and Get methods. When there's no configu
> The DeviceLock CSP utilizes the [Exchange ActiveSync Policy Engine](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn282287(v=ws.11)). When password length and complexity rules are applied, all the local user and administrator accounts are marked to change their password at the next sign in to ensure complexity requirements are met. For additional information, see [Password length and complexity supported by account types](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn282287(v=ws.11)#password-length-and-complexity-supported-by-account-types)).
Allows the IT admin (when used with **Update/ActiveHoursStart**) to manage a range of active hours where update reboots aren't scheduled. This value sets the end time. there's a 12-hour maximum from start time.
> [!NOTE]
>The default maximum difference from start time has been increased to 18 in Windows 10, version 1703. In this version of Windows 10, the maximum range of active hours can now be configured. See **Update/ActiveHoursMaxRange** below for more information.
>The default maximum difference from start time has been increased to 18 in Windows 10, version 1703. In this version of Windows 10, the maximum range of active hours can now be configured. See **Update/ActiveHoursMaxRange** below for more information.
Supported values are 0-23, where 0 is 12 AM, 1 is 1 AM, etc.
@ -361,7 +361,7 @@ ADMX Info:
Allows the IT admin (when used with **Update/ActiveHoursEnd**) to manage a range of hours where update reboots aren't scheduled. This value sets the start time. There's a 12-hour maximum from end time.
> [!NOTE]
>The default maximum difference from end time has been increased to 18 in Windows 10, version 1703. In this version of Windows 10, the maximum range of active hours can now be configured. See **Update/ActiveHoursMaxRange** above for more information.
>The default maximum difference from end time has been increased to 18 in Windows 10, version 1703. In this version of Windows 10, the maximum range of active hours can now be configured. See **Update/ActiveHoursMaxRange** above for more information.
Supported values are 0-23, where 0 is 12 AM, 1 is 1 AM, etc.
@ -426,12 +426,12 @@ ADMX Info:
<!--SupportedValues-->
The following list shows the supported values:
- 0 – Notify the user before downloading the update. This policy is used by the enterprise who wants to enable the end users to manage data usage. With these option users are notified when there are updates that apply to the device and are ready for download. Users can download and install the updates from the Windows Update control panel.
- 0 - Notify the user before downloading the update. This policy is used by the enterprise who wants to enable the end users to manage data usage. With these option users are notified when there are updates that apply to the device and are ready for download. Users can download and install the updates from the Windows Update control panel.
- 1 - Auto install the update and then notify the user to schedule a device restart. Updates are downloaded automatically on non-metered networks and installed during "Automatic Maintenance" when the device isn't in use and isn't running on battery power. If automatic maintenance is unable to install updates for two days, Windows Update will install updates immediately. If the installation requires a restart, the end user is prompted to schedule the restart time. The end user has up to seven days to schedule the restart and after that, a restart of the device is forced. Enabling the end user to control the start time reduces the risk of accidental data loss caused by applications that don't shut down properly on restart. For more information, see [Automatic maintenance](/windows/win32/taskschd/task-maintenence).
- 2 (default) - Auto install and restart. Updates are downloaded automatically on non-metered networks and installed during "Automatic Maintenance" when the device isn't in use and isn't running on battery power. If automatic maintenance is unable to install updates for two days, Windows Update will install updates right away. If a restart is required, then the device is automatically restarted when the device isn't actively being used. Automatic restarting when a device isn't being used is the default behavior for unmanaged devices. Devices are updated quickly, but it increases the risk of accidental data loss caused by an application that doesn't shut down properly on restart. For more information, see [Automatic maintenance](/windows/win32/taskschd/task-maintenence).
- 3 – Auto install and restart at a specified time. The IT specifies the installation day and time. If no day and time are specified, the default is 3 AM daily. Automatic installation happens at this time and device restart happens after a 15-minute countdown. If the user is logged in when Windows is ready to restart, the user can interrupt the 15-minute countdown to delay the restart.
- 4 – Auto install and restart without end-user control. Updates are downloaded automatically on non-metered networks and installed during "Automatic Maintenance" when the device isn't in use and isn't running on battery power. If automatic maintenance is unable to install updates for two days, Windows Update will install updates right away. If a restart is required, then the device is automatically restarted when the device isn't actively being used. This setting option also sets the end-user control panel to read-only.
- 5 – Turn off automatic updates.
- 3 - Auto install and restart at a specified time. The IT specifies the installation day and time. If no day and time are specified, the default is 3 AM daily. Automatic installation happens at this time and device restart happens after a 15-minute countdown. If the user is logged in when Windows is ready to restart, the user can interrupt the 15-minute countdown to delay the restart.
- 4 - Auto install and restart without end-user control. Updates are downloaded automatically on non-metered networks and installed during "Automatic Maintenance" when the device isn't in use and isn't running on battery power. If automatic maintenance is unable to install updates for two days, Windows Update will install updates right away. If a restart is required, then the device is automatically restarted when the device isn't actively being used. This setting option also sets the end-user control panel to read-only.
- 5 - Turn off automatic updates.
> [!IMPORTANT]
@ -536,8 +536,8 @@ ADMX Info:
<!--SupportedValues-->
The following list shows the supported values:
- 0 – Not configured.
- 1 – Allowed. Accepts updates received through Microsoft Update.
- 0 - Not configured.
- 1 - Allowed. Accepts updates received through Microsoft Update.
> [!NOTE]
> Setting this policy back to **0** or **Not configured** doesn't revert the configuration to receive updates from Microsoft Update automatically. In order to revert the configuration, you can run the PowerShell commands that are listed below to remove the Microsoft Update service:.
@ -588,8 +588,8 @@ This policy is specific to desktop and local publishing via WSUS for third-party
<!--SupportedValues-->
The following list shows the supported values:
- 0 – Not allowed or not configured. Updates from an intranet Microsoft update service location must be signed by Microsoft.
- 1 – Allowed. Accepts updates received through an intranet Microsoft update service location, if they're signed by a certificate found in the "Trusted Publishers" certificate store of the local computer.
- 0 - Not allowed or not configured. Updates from an intranet Microsoft update service location must be signed by Microsoft.
- 1 - Allowed. Accepts updates received through an intranet Microsoft update service location, if they're signed by a certificate found in the "Trusted Publishers" certificate store of the local computer.
<!--/SupportedValues-->
<!--/Policy-->
@ -629,7 +629,7 @@ Even when Windows Update is configured to receive updates from an intranet updat
Enabling this policy will disable that functionality, and may cause connection to public services such as the Microsoft Store to stop working.
> [!NOTE]
>This policy applies only when the desktop or device is configured to connect to an intranet update service using the "Specify intranet Microsoft update service location" policy.
>This policy applies only when the desktop or device is configured to connect to an intranet update service using the "Specify intranet Microsoft update service location" policy.
<!--/Description-->
<!--ADMXMapped-->
@ -643,8 +643,8 @@ ADMX Info:
<!--SupportedValues-->
The following list shows the supported values:
- 0 – Update service isn't allowed.
- 1 (default) – Update service is allowed.
- 0 - Update service isn't allowed.
- 1 (default) - Update service is allowed.
<!--/SupportedValues-->
<!--/Policy-->
@ -856,8 +856,8 @@ ADMX Info:
<!--SupportedValues-->
The following list shows the supported values:
- 1 (default) – Auto Dismissal.
- 2 – User Dismissal.
- 1 (default) - Auto Dismissal.
- 2 - User Dismissal.
<!--/SupportedValues-->
<!--/Policy-->
@ -1306,7 +1306,7 @@ Defers Feature Updates for the specified number of days.
Supported values are 0-365 days.
> [!IMPORTANT]
>The default maximum number of days to defer an update has been increased from 180 (Windows 10, version 1607) to 365 in Windows 10, version 1703.
>The default maximum number of days to defer an update has been increased from 180 (Windows 10, version 1607) to 365 in Windows 10, version 1703.
<!--/Description-->
<!--ADMXMapped-->
@ -1393,7 +1393,7 @@ ADMX Info:
<!--/Scope-->
<!--Description-->
> [!NOTE]
> Don't use this policy in Windows10, version 1607 devices, instead use the new policies listed in [Changes in Windows 10, version 1607 for update management](device-update-management.md#windows10version1607forupdatemanagement). You can continue to use DeferUpdatePeriod for Windows10, version 1511 devices.
> Don't use this policy in Windows10, version 1607 devices, instead use the new policies listed in [Changes in Windows 10, version 1607 for update management](device-update-management.md#windows10version1607forupdatemanagement). You can continue to use DeferUpdatePeriod for Windows10, version 1511 devices.
Allows IT Admins to specify update delays for up to four weeks.
@ -1471,7 +1471,7 @@ ADMX Info:
<!--/Scope-->
<!--Description-->
> [!NOTE]
> Don't use this policy in Windows10, version 1607 devices, instead use the new policies listed in [Changes in Windows 10, version 1607 for update management](device-update-management.md#windows10version1607forupdatemanagement). You can continue to use DeferUpgradePeriod for Windows10, version 1511 devices.
> Don't use this policy in Windows10, version 1607 devices, instead use the new policies listed in [Changes in Windows 10, version 1607 for update management](device-update-management.md#windows10version1607forupdatemanagement). You can continue to use DeferUpgradePeriod for Windows10, version 1511 devices.
Allows IT Admins to specify other upgrade delays for up to eight months.
@ -1616,18 +1616,18 @@ The following list shows the supported values:
<!--/Scope-->
<!--Description-->
Available in Windows Update for Business (WUfB) devices running Windows 10, version 1809 and above and installed with October 2020 security update. This policy setting specifies that a WUfB device should skip safeguards.
Available in Windows Update for Business devices running Windows 10, version 1809 and above and installed with October 2020 security update. This policy setting specifies that a Windows Update for Business device should skip safeguards.
Safeguard holds prevent a device with a known compatibility issue from being offered a new OS version. The offering will proceed once a fix is issued and is verified on a held device. The aim of safeguards is to protect the device and user from a failed or poor upgrade experience.
The safeguard holds protection is provided by default to all the devices trying to update to a new Windows 10 Feature Update version via Windows Update.
IT admins can, if necessary, opt devices out of safeguard protections using this policy setting or via the “Disable safeguards for Feature Updates” Group Policy.
IT admins can, if necessary, opt devices out of safeguard protections using this policy setting or via the "Disable safeguards for Feature Updates" Group Policy.
> [!NOTE]
> Opting out of the safeguards can put devices at risk from known performance issues. We recommend opting out only in an IT environment for validation purposes. Further, you can leverage the Windows Insider Program for Business Release Preview Channel in order to validate the upcoming Windows 10 Feature Update version without the safeguards being applied.
>
> The disable safeguards policy will revert to “Not Configured” on a device after moving to a new Windows 10 version, even if previously enabled. This ensures the admin is consciously disabling Microsoft’s default protection from known issues for each new feature update.
> The disable safeguards policy will revert to "Not Configured" on a device after moving to a new Windows 10 version, even if previously enabled. This ensures the admin is consciously disabling Microsoft's default protection from known issues for each new feature update.
>
> Disabling safeguards doesn't guarantee your device will be able to successfully update. The update may still fail on the device and will likely result in a bad experience post upgrade as you're bypassing the protection given by Microsoft pertaining to known issues.
@ -2069,8 +2069,8 @@ ADMX Info:
<!--SupportedValues-->
The following list shows the supported values:
- 0 (default) – Allow Windows Update drivers.
- 1 – Exclude Windows Update drivers.
- 0 (default) - Allow Windows Update drivers.
- 1 - Exclude Windows Update drivers.
<!--/SupportedValues-->
<!--/Policy-->
@ -2121,8 +2121,8 @@ ADMX Info:
<!--SupportedValues-->
The following list shows the supported values:
- 0 (default) – Disabled.
- 1 – Enabled.
- 0 (default) - Disabled.
- 1 - Enabled.
<!--/SupportedValues-->
<!--/Policy-->
@ -2164,8 +2164,8 @@ Specifies whether to ignore the MO download limit (allow unlimited downloading)
<!--SupportedValues-->
The following list shows the supported values:
- 0 (default) – Don't ignore MO download limit for apps and their updates.
- 1 – Ignore MO download limit (allow unlimited downloading) for apps and their updates.
- 0 (default) - Don't ignore MO download limit for apps and their updates.
- 1 - Ignore MO download limit (allow unlimited downloading) for apps and their updates.
<!--/SupportedValues-->
<!--Validation-->
@ -2217,8 +2217,8 @@ Specifies whether to ignore the MO download limit (allow unlimited downloading)
<!--SupportedValues-->
The following list shows the supported values:
- 0 (default) – Don't ignore MO download limit for OS updates.
- 1 – Ignore MO download limit (allow unlimited downloading) for OS updates.
- 0 (default) - Don't ignore MO download limit for OS updates.
- 1 - Ignore MO download limit (allow unlimited downloading) for OS updates.
<!--/SupportedValues-->
<!--Validation-->
@ -2312,7 +2312,7 @@ The following list shows the supported values:
<!--/Scope-->
<!--Description-->
> [!NOTE]
> Don't use this policy in Windows10, version 1607 devices, instead use the new policies listed in [Changes in Windows 10, version 1607 for update management](device-update-management.md#windows10version1607forupdatemanagement). You can continue to use PauseDeferrals for Windows10, version 1511 devices.
> Don't use this policy in Windows10, version 1607 devices, instead use the new policies listed in [Changes in Windows 10, version 1607 for update management](device-update-management.md#windows10version1607forupdatemanagement). You can continue to use PauseDeferrals for Windows10, version 1511 devices.
Allows IT Admins to pause updates and upgrades for up to five weeks. Paused deferrals will be reset after five weeks.
@ -2333,8 +2333,8 @@ ADMX Info:
<!--SupportedValues-->
The following list shows the supported values:
- 0 (default) – Deferrals aren't paused.
- 1 – Deferrals are paused.
- 0 (default) - Deferrals aren't paused.
- 1 - Deferrals are paused.
<!--/SupportedValues-->
<!--/Policy-->
@ -2383,8 +2383,8 @@ ADMX Info:
<!--SupportedValues-->
The following list shows the supported values:
- 0 (default) – Feature Updates aren't paused.
- 1 – Feature Updates are paused for 35 days or until value set to back to 0, whichever is sooner.
- 0 (default) - Feature Updates aren't paused.
- 1 - Feature Updates are paused for 35 days or until value set to back to 0, whichever is sooner.
<!--/SupportedValues-->
<!--/Policy-->
@ -2476,8 +2476,8 @@ ADMX Info:
<!--SupportedValues-->
The following list shows the supported values:
- 0 (default) – Quality Updates aren't paused.
- 1 – Quality Updates are paused for 35 days or until value set back to 0, whichever is sooner.
- 0 (default) - Quality Updates aren't paused.
- 1 - Quality Updates are paused for 35 days or until value set back to 0, whichever is sooner.
<!--/SupportedValues-->
<!--/Policy-->
@ -2580,7 +2580,7 @@ ADMX Info:
<!--/ADMXMapped-->
<!--SupportedValues-->
Value type is a string containing a Windows product, for example, “Windows 11” or “11” or “Windows 10”.
Value type is a string containing a Windows product, for example, "Windows 11" or "11" or "Windows 10".
<!--/SupportedValues-->
<!--Example-->
@ -2624,7 +2624,7 @@ By using this Windows Update for Business policy to upgrade devices to a new pro
<!--/Scope-->
<!--Description-->
> [!NOTE]
> Don't use this policy in Windows10, version 1607 devices, instead use the new policies listed in [Changes in Windows 10, version 1607 for update management](device-update-management.md#windows10version1607forupdatemanagement). You can continue to use RequireDeferUpgrade for Windows10, version 1511 devices.
> Don't use this policy in Windows10, version 1607 devices, instead use the new policies listed in [Changes in Windows 10, version 1607 for update management](device-update-management.md#windows10version1607forupdatemanagement). You can continue to use RequireDeferUpgrade for Windows10, version 1511 devices.
Allows the IT admin to set a device to General Availability Channel train.
@ -2640,8 +2640,8 @@ ADMX Info:
<!--SupportedValues-->
The following list shows the supported values:
- 0 (default) – User gets upgrades from General Availability Channel (Targeted).
- 1 – User gets upgrades from General Availability Channel.
- 0 (default) - User gets upgrades from General Availability Channel (Targeted).
- 1 - User gets upgrades from General Availability Channel.
<!--/SupportedValues-->
<!--/Policy-->
@ -2675,7 +2675,7 @@ The following list shows the supported values:
<!--/Scope-->
<!--Description-->
> [!NOTE]
>If you previously used the **Update/PhoneUpdateRestrictions** policy in previous versions of Windows, it has been deprecated. Please use this policy instead.
>If you previously used the **Update/PhoneUpdateRestrictions** policy in previous versions of Windows, it has been deprecated. Please use this policy instead.
Allows the IT admin to restrict the updates that are installed on a device to only those on an update approval list. It enables IT to accept the End User License Agreement (EULA) associated with the approved update on behalf of the end user. EULAs are approved once an update is approved.
@ -2686,8 +2686,8 @@ Supported operations are Get and Replace.
<!--SupportedValues-->
The following list shows the supported values:
- 0 – Not configured. The device installs all applicable updates.
- 1 – The device only installs updates that are both applicable and on the Approved Updates list. Set this policy to 1 if IT wants to control the deployment of updates on devices, such as when testing is required prior to deployment.
- 0 - Not configured. The device installs all applicable updates.
- 1 - The device only installs updates that are both applicable and on the Approved Updates list. Set this policy to 1 if IT wants to control the deployment of updates on devices, such as when testing is required prior to deployment.
<!--/SupportedValues-->
<!--/Policy-->
@ -2769,7 +2769,7 @@ Supported values are 15, 30, or 60 (minutes).
<!--/Scope-->
<!--Description-->
> [!NOTE]
>This policy is available on Windows10 Pro, Windows10 Enterprise, and Windows10 Education
>This policy is available on Windows10 Pro, Windows10 Enterprise, and Windows10 Education
Allows the IT Admin to specify the period for autorestart warning reminder notifications.
@ -2839,14 +2839,14 @@ ADMX Info:
<!--SupportedValues-->
The following list shows the supported values:
- 0 (default) – Every day
- 1 – Sunday
- 2 – Monday
- 3 – Tuesday
- 4 – Wednesday
- 5 – Thursday
- 6 – Friday
- 7 – Saturday
- 0 (default) - Every day
- 1 - Sunday
- 2 - Monday
- 3 - Tuesday
- 4 - Wednesday
- 5 - Thursday
- 6 - Friday
- 7 - Saturday
<!--/SupportedValues-->
<!--/Policy-->
@ -3110,7 +3110,7 @@ ADMX Info:
<!--/Scope-->
<!--Description-->
> [!NOTE]
>This policy is available on Windows10 Pro, Windows10 Enterprise, and Windows10 Education
>This policy is available on Windows10 Pro, Windows10 Enterprise, and Windows10 Education
Enables the IT admin to schedule the time of the update installation.
@ -3178,8 +3178,8 @@ ADMX Info:
<!--SupportedValues-->
The following list shows the supported values:
- 0 (default) – Enabled
- 1 – Disabled
- 0 (default) - Enabled
- 1 - Disabled
<!--/SupportedValues-->
<!--/Policy-->
@ -3675,9 +3675,9 @@ Display options for update notifications. This policy allows you to define what
Options:
- 0 (default) – Use the default Windows Update notifications
- 1 – Turn off all notifications, excluding restart warnings
- 2 – Turn off all notifications, including restart warnings
- 0 (default) - Use the default Windows Update notifications
- 1 - Turn off all notifications, excluding restart warnings
- 2 - Turn off all notifications, including restart warnings
> [!IMPORTANT]
> If you choose not to get update notifications and also define other Group policies so that devices aren't automatically getting updates, neither you nor device users will be aware of critical security, quality, or feature updates, and your devices may be at risk.
@ -560,7 +560,7 @@ The XML below is for Windows 10, version 1803.
</AccessType>
<Description>
Roll back Latest Quality Update, if the machine meets the following conditions:
Condition 1: Device must be WUfB Connected
Condition 1: Device must be Windows Update for Business connected
Condition 2: Device must be in a Paused State
Condition 3: Device must have the Latest Quality Update installed on the device (Current State)
If the conditions are not true, the device will not Roll Back the Latest Quality Update.
@ -588,7 +588,7 @@ The XML below is for Windows 10, version 1803.
</AccessType>
<Description>
Roll Back Latest Feature Update, if the machine meets the following conditions:
Condition 1: Device must be WUfB Connected
Condition 1: Device must be Windows Update for Business connected
Condition 2: Device must be in Paused State
Condition 3: Device must have the Latest Feature Update Installed on the device (Current State)
Condition 4: Machine should be within the uninstall period
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Shesh