Windows 11: 22H2 · 3.0 to 24H2 · 1.0

Configure this setting to control the specific user or group who is authorized to decrypt encrypted passwords. Configuring this setting has no effect unless password encryption has been enabled. If this setting is enabled, encrypted passwords will be decryptable by the specified group. If this setting is disabled or not configured, encrypted passwords will be decryptable by the Domain Admins group. This setting must be configured with either a [added: domain-qualified name of a group or user, or a ]SID in string [removed: format ("S-1-5-21-2127521184-1604012920-1887927527-35197") or the name of a group][added: format. Valid examples include: contoso\LAPSAdmins [email protected] S-1-5-21-2127521184-1604012920-1887927527-35197 Do not enclose the user\group name] or [removed: user][added: SID] in [removed: "domain\(group][added: enclosing quotes] or [removed: user)" format. ][added: parentheses. ]The specified user or group must be resolvable by the managed device, otherwise passwords will not be backed up.[added: NOTE: this setting is ignored when Directory Services Repair Mode (DSRM) account passwords are backed up on a domain controller. In that scenario, this setting always defaults to the Domain Admins group of the domain controller's domain.] See https://go.microsoft.com/fwlink/?linkid=2188435 for more information.

Configures password parameters Password complexity: which characters are used when generating a new password Default: Large letters + small letters + numbers + special characters Password length Minimum: 8 characters Maximum: 64 characters Default: 14 characters Password age in days Minimum: 1 day (7 days when backup directory is configured to be Azure AD) Maximum: 365 days Default: 30 days [added: Passphrase length Minimum: 3 words Maximum: 10 words Default: 6 words ]See https://go.microsoft.com/fwlink/?linkid=2188435[added: for more information. Passphrase list taken from "Deep Dive: EFF's New Wordlists for Random Passphrases" by Electronic Frontier Foundation, and is used under a CC-BY-3.0 Attribution license. See https://go.microsoft.com/fwlink/?linkid=2255471] for more information.

This policy configures post-authentication actions which will be executed after detecting an authentication by the managed account. Grace period: specifies the amount of time (in hours) to wait after an authentication before executing the specified post-authentication actions. If this setting is enabled and greater than zero, the specified post-authentication actions will be executed upon expir[removed: y][added: ation] of the grace period. If this setting is disabled or not configured, the specified post-authentication actions will be executed after a default 24 hour grace period. If this setting is equal to zero, no post-authentication actions will be executed. Actions: specifies the actions to take upon expir[removed: y][added: ation] of the grace period. Reset password: upon expir[removed: y][added: ation] of the grace period, the managed account password [removed: will be ][added: is ]reset. Reset the password and logoff the managed account: upon expir[removed: y][added: ation] of the grace period, the managed account password [removed: will be][added: is reset and any interactive logon sessions using the managed account are logged off. Reset the password and reboot: upon expiration of the grace period, the managed account password is] reset and [added: the managed device is rebooted. Reset the password, logoff the managed account, and terminate ]any [added: remaining processes: upon expiration of the grace period, the managed account password is reset, any ]interactive logon sessions using the managed account [removed: will][added: are logged off, and any remaining processes are] terminated. (NOTE: after any interactive logon sessions are terminated there may still be other authenticated sessions in use by the managed account. The only robust way to ensure that the previous password is longer in use is to reboot the device.)[removed: Reset the password and reboot: upon expiry of the grace period, the managed account password will be reset and the managed device will be immediately rebooted.] If this setting is disabled or not configured, post-authentication actions will default to "Reset the password and logoff the managed account". Note: the DSRM account on domain controllers cannot be configured for post-authentication actions. This policy has no effect on domain controllers and will be ignored even if configured for a DC. See https://go.microsoft.com/fwlink/?linkid=2188435 for more information.

This policy setting allows you to hide the TaskView button.[removed: ][added: ]If you enable this policy setting, the TaskView button will be hidden and the Settings toggle will be disabled.

Turning off [removed: files from Office.com ][added: this setting ]will prevent File Explorer from requesting [removed: recent ]cloud file metadata and displaying it in the [removed: Quick access view.][added: homepage and other views in File Explorer. Any insights and files available based on account activity will be stopped in views such as Recent, Recommended, Favorites, Details pane, etc.]

This policy setting lets you turn on Content URI Rules to supplement the static Content URI Rules that were defined as part of the app manifest and apply to all [removed: Windows][added: packaged Microsoft] Store apps that use the enterpriseAuthentication capability on a computer. If you enable this policy setting, you can define additional Content URI Rules that all [removed: Windows][added: packaged Microsoft] Store apps that use the enterpriseAuthentication capability on a computer can use. If you disable or don't set this policy setting, [removed: Windows][added: packaged Microsoft] Store apps will only use the static Content URI Rules.

Specifies if the DNS client would use the DDR protocol. The Discovery of Designated Resolvers (DDR) protocol allows Windows to move from unencrypted DNS to encrypted DNS when only the IP address of a resolver is known. If you enable this policy, the DNS client will use the DDR protocol. If you disable this policy setting, or if you do not configure this policy setting, [removed: computers][added: the DNS client] will use locally configured settings.

Specifies if the DNS client will perform name resolution over [removed: DNS over HTTPS (DoH).][added: encrypted protocols.] By default, the DNS client will do classic DNS name resolution (over UDP or [removed: TCP).][added: TCP port 53).] This setting can enhance the DNS client to use [removed: DoH protocol][added: encrypted protocols] to resolve domain names. To use this policy setting, click Enabled, and then select one of the following options from the drop-down list: Prohibit [removed: DoH: No DoH][added: encryption: no encrypted] name resolution will be performed. Allow [removed: DoH: Perform DoH queries][added: encryption: Use encrypted name resolution] if the configured [removed: DNS ]servers support it. If they don't support it, try classic name resolution. Require [removed: DoH:][added: encryption:] Allow only [removed: DoH][added: encrypted] name resolution. If there are no [removed: DoH capable ][added: configured ]DNS servers [removed: configured,][added: that handle encryption,] name resolution will fail. [added: In addition to the generic encryption policy, additional policies can be configured at the individual protocol level. For example, in order to force DoT name resolution only, a combination of "Require encryption" and "Block DoH" would be needed (vice versa to force DoH). For the example above, it is the admin's responsibility to ensure that if DoT is forced, there are valid DoT servers configured on the machine (vice versa for DoH). ]If you disable this policy setting, or if you do not configure this policy setting, [removed: computers][added: the DNS client] will use locally configured settings. DDR (Discovery of Designated Resolvers) plaintext traffic [removed: is][added: will be] allowed as it is necessary for auto-discovering [removed: DoH][added: encryption] settings.

This policy setting specifies whether JScript or JScript9Legacy is [removed: loaded for MSHTML/WebOC/MSXML/Cscript based invocations.][added: loaded.] If you enable this policy [removed: setting,][added: setting or not configured,] JScript9Legacy will be loaded in situations where JScript is instantiated. If you disable this policy, then JScript will be utilized.[removed: If this policy is left unconfigured, then MSHTML will use JScript9Legacy and MSXML/Cscript will use JScript.]

This policy controls the configuration under which LSASS is run. If you do not configure this policy and there is no current setting in the registry, LSA will run as protected process for [added: all ]clean installed, HVCI capable, client [removed: SKUs that are domain or cloud domain joined devices.][added: SKUs.] This configuration is not UEFI locked. This can be overridden if the policy is configured. If you configure and set this policy setting to "Disabled", LSA will not run as a protected process. If you configure and set this policy setting to "EnabledWithUEFILock," LSA will run as a protected process and this configuration is UEFI locked. If you configure and set this policy setting to "EnabledWithoutUEFILock", LSA will run as a protected process and this configuration is not UEFI locked.

This policy setting allows users to see [removed: Windows][added: packaged Microsoft] Store apps on the taskbar. If you enable this policy setting, users will see [removed: Windows][added: packaged Microsoft] Store apps on the taskbar. If you disable this policy setting, users won’t see [removed: Windows][added: packaged Microsoft] Store apps on the taskbar. If you don’t configure this policy setting, the default setting for the user’s device will be used, and the user can choose to change it.

This policy setting allows you to specify which protocols can be used for Remote Desktop Protocol (RDP) access to this server. If you enable this policy setting, you must specify if you would like RDP to use UDP. You can select one of the following options: "Use [removed: both][added: either] UDP [removed: and TCP", "Use only TCP" ][added: or TCP (default)" ]or "Use [removed: either UDP or TCP (default)"][added: only TCP"] If you select "Use either UDP or TCP" and the UDP connection is successful, most of the RDP traffic will use UDP. If the UDP connection is not successful or if you select "Use only TCP," all of the RDP traffic will use TCP. If you disable or do not configure this policy setting, RDP will choose the optimal protocols for delivering the best user experience.