mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Merging changes synced from https://github.com/MicrosoftDocs/windows-docs-pr (branch live)
This commit is contained in:
commit
88157fe22c
@ -19,7 +19,7 @@ Use **Privacy** to configure settings for app activation with voice.
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| All settings | X | X | X | | X |
|
||||
| All settings | ✔️ | ✔️ | ✔️ | | ✔️ |
|
||||
|
||||
## LetAppsActivateWithVoice
|
||||
|
||||
|
@ -21,7 +21,7 @@ Use ProvisioningCommands settings to install Windows desktop applications using
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| All settings | X | | | | |
|
||||
| All settings | ✔️ | | | | |
|
||||
|
||||
For instructions on adding apps to provisioning packages, see [Provision PCs with apps](../provisioning-packages/provision-pcs-with-apps.md).
|
||||
|
||||
|
@ -21,7 +21,7 @@ Use these settings to configure RcsPresence.
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| All settings | | X | | | |
|
||||
| All settings | | ✔️ | | | |
|
||||
|
||||
Setting | Description
|
||||
--- | ---
|
||||
|
@ -22,7 +22,7 @@ Use SharedPC settings to optimize Windows 10 for shared use scenarios, such as t
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| All settings | X | | | | |
|
||||
| All settings | ✔️ | | | | |
|
||||
|
||||
## AccountManagement
|
||||
|
||||
@ -30,19 +30,19 @@ Use these settings to configure settings for accounts allowed on the shared PC.
|
||||
|
||||
| Setting | Value | Description |
|
||||
| --- | --- | --- |
|
||||
| AccountModel | - Only guest</br>- Domain-joined only</br>- Domain-joined and guest | This option controls how users can sign-in on the PC. Choosing domain-joined will enable any user in the domain to sign-in. Specifying the guest option will add the Guest option to the sign-in screen and enable anonymous guest access to the PC. </br></br>- Only guest allows anyone to use the PC as a local standard (non-admin) account.</br>- Domain-joined only allows users to sign in with an Active Directory or Azure AD account.</br>- Domain-joined and guest allows users to sign in with an Active Directory, Azure AD, or local standard account. |
|
||||
| DeletionPolicy | - Delete immediately </br>- Delete at disk space threshold</br>- Delete at disk space threshold and inactive threshold | - Delete immediately will delete the account on sign-out.</br>- Delete at disk space threshold will start deleting accounts when available disk space falls below the threshold you set for DiskLevelDeletion, and it will stop deleting accounts when the available disk space reaches the threshold you set for DiskLevelCaching. Accounts are deleted in order of oldest accessed to most recently accessed.</br>- Delete at disk space threshold and inactive threshold will apply the same disk space checks as noted above, but also delete accounts if they have not signed in within the number of days specified by InactiveThreshold |
|
||||
| AccountModel | - Only guest</br>- Domain-joined only</br>- Domain-joined and guest | This option controls how users can sign in on the PC. Choosing domain-joined will enable any user in the domain to sign in. Specifying the guest option will add the Guest option to the sign in screen and enable anonymous guest access to the PC. </br></br>- Only guest allows anyone to use the PC as a local standard (non-admin) account.</br>- Domain-joined only allows users to sign in with an Active Directory or Azure AD account.</br>- Domain-joined and guest allows users to sign in with an Active Directory, Azure AD, or local standard account. |
|
||||
| DeletionPolicy | - Delete immediately </br>- Delete at disk space threshold</br>- Delete at disk space threshold and inactive threshold | - **Delete immediately** deletes the account on sign out.</br>- **Delete at disk space threshold** starts deleting accounts when available disk space falls below the threshold you set for `DiskLevelDeletion`. It stops deleting accounts when the available disk space reaches the threshold you set for `DiskLevelCaching`. Accounts are deleted in order of oldest accessed to most recently accessed.</br>- **Delete at disk space threshold and inactive threshold** applies the same disk space checks as noted above. It also deletes accounts if they haven't signed in within the number of days in `InactiveThreshold`. |
|
||||
| DiskLevelCaching | A number between 0 and 100 | If you set **DeletionPolicy** to **Delete at disk space threshold**, set the percent of total disk space to be used as the disk space threshold for account caching. |
|
||||
| DiskLevelDeletion | A number between 0 and 100 | If you set **DeletionPolicy** to **Delete at disk space threshold**, set the percent of total disk space to be used as the disk space threshold for account deletion. |
|
||||
| EnableAccountManager | True or false | Set as **True** to enable automatic account management. If this is not set to true, no automatic account management will be done. |
|
||||
| InactiveThreshold | Number | If you set **DeletionPolicy** to **Delete at disk space threshold and inactive threshold**, set the number of days after which an account that has not signed in will be deleted. |
|
||||
| KioskModeAUMID | String | Set an Application User Model ID (AUMID) to enable the kiosk account on the sign-in screen. A new account will be created and will use assigned access to only run the app specified by the AUMID. Note that the app must be installed on the PC. Set the name of the account using **KioskModeUserTileDisplayText**, or a default name will be used. [Find the Application User Model ID of an installed app](/previous-versions/windows/embedded/dn449300(v=winembedded.82)) |
|
||||
| EnableAccountManager | True or false | Set as **True** to enable automatic account management. When set to **False**, no automatic account management will be done. |
|
||||
| InactiveThreshold | Number | If you set **DeletionPolicy** to **Delete at disk space threshold and inactive threshold**, set the number of days after which an account that hasn't signed in will be deleted. |
|
||||
| KioskModeAUMID | String | Set an Application User Model ID (AUMID) to enable the kiosk account on the sign in screen. A new account will be created and will use assigned access to only run the app specified by the AUMID. The app must be installed on the PC. Set the name of the account using **KioskModeUserTileDisplayText**, or a default name will be used. [Find the Application User Model ID of an installed app](/previous-versions/windows/embedded/dn449300(v=winembedded.82)) |
|
||||
| KioskModeUserTileDisplayText | String | Sets the display text on the kiosk account if **KioskModeAUMID** has been set. |
|
||||
|
||||
|
||||
## EnableSharedPCMode
|
||||
|
||||
Set as **True**. If this is not set to **True**, shared PC mode is not turned on and none of the other settings apply. This setting controls this API: [IsEnabled](/uwp/api/windows.system.profile.sharedmodesettings).
|
||||
Set as **True**. When set to **False**, shared PC mode isn't turned on and none of the other settings apply. This setting controls this API: [IsEnabled](/uwp/api/windows.system.profile.sharedmodesettings).
|
||||
|
||||
Some of the remaining settings in SharedPC are optional, but we strongly recommend that you also set **EnableAccountManager** to **True**.
|
||||
|
||||
@ -53,13 +53,13 @@ Use these settings to configure policies for shared PC mode.
|
||||
| Setting | Value | Description |
|
||||
| --- | --- | --- |
|
||||
| MaintenanceStartTime | A number between 0 and 1440 | By default, the maintenance start time (which is when automatic maintenance tasks run, such as Windows Update) is midnight. You can adjust the start time in this setting by entering a new start time in minutes from midnight. For example, if you want maintenance to begin at 2 AM, enter `120` as the value. |
|
||||
| MaxPageFileSizeMB | A number between 1024 and 2048 | Adjusts the maximum page file size in MB. This can be used to fine-tune page file behavior, especially on low end PCs. |
|
||||
| MaxPageFileSizeMB | A number between 1024 and 2048 | Adjusts the maximum page file size in MB. This setting can be used to fine-tune page file behavior, especially on low end PCs. |
|
||||
| RestrictLocalStorage | True or false | Set as **True** to restrict the user from saving or viewing local storage when using File Explorer. This setting controls this API: [ShouldAvoidLocalStorage](/uwp/api/windows.system.profile.sharedmodesettings) |
|
||||
| SetEduPolicies | True or false | Set to **True** for PCs that will be used in a school. For more information, see [Windows 10 configuration recommendations for education customers](/education/windows/configure-windows-for-education). This setting controls this API: [IsEducationEnvironment](/uwp/api/windows.system.profile.educationsettings) |
|
||||
| SetPowerPolicies | True or false | When set as **True**:</br></br>- Prevents users from changing power settings</br>- Turns off hibernate</br>- Overrides all power state transitions to sleep (e.g. lid close) |
|
||||
| SetPowerPolicies | True or false | When set as **True**:</br></br>- Prevents users from changing power settings</br>- Turns off hibernate</br>- Overrides all power state transitions to sleep, such as a lid close. |
|
||||
| SignInOnResume | True or false | This setting specifies if the user is required to sign in with a password when the PC wakes from sleep. |
|
||||
| SleepTimeout | Number | Specifies all timeouts for when the PC should sleep. Enter the amount of idle time in seconds. If you don't set sleep timeout, the default of 1 hour applies. |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [Set up shared or guest PC](../set-up-shared-or-guest-pc.md)
|
@ -15,12 +15,12 @@ manager: dansimp
|
||||
|
||||
# Shell (Windows Configuration Designer reference)
|
||||
|
||||
Do not use. Use [Start > StartLayout](wcd-start.md#startlayout)
|
||||
Don't use. Use [Start > StartLayout](wcd-start.md#startlayout).
|
||||
|
||||
## Applies to
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| All settings | | X | | | |
|
||||
| All settings | | ✔️ | | | |
|
||||
|
||||
|
||||
|
@ -21,19 +21,19 @@ Use SMISettings settings to customize the device with custom shell, suppress Win
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| All settings | X | | | | |
|
||||
| All settings | ✔️ | | | | |
|
||||
|
||||
## All settings in SMISettings
|
||||
|
||||
The following table describes the settings in SMISettings. Some settings have additional details in sections after the table.
|
||||
The following table describes the settings in SMISettings. Some settings have more details in sections after the table.
|
||||
|
||||
| Setting | Value | Description |
|
||||
| --- | --- | --- |
|
||||
| AutoLogon | Enable</br>Domain name</br>Password</br>UserName | Allows automatic sign-in at startup so that the user does not need to enter a user name and password. |
|
||||
| AutoLogon | Enable</br>Domain name</br>Password</br>UserName | Allows automatic sign-in at startup. Users don't need to enter a user name and password. |
|
||||
| BrandingNeutral | See [BrandingNeutral values](#brandingneutral-values) | Specifies which UI elements display on the Welcome screen. |
|
||||
| CrashDumpEnabled | See [CrashDumpEnabled values](#crashdumpenabled-values) | Specifies the type of information to be saved in the event of a crash. |
|
||||
| CrashDumpEnabled | See [CrashDumpEnabled values](#crashdumpenabled-values) | Specifies the type of information to be saved if there's a crash. |
|
||||
| DisableBootMenu | True or false | Disables the F8 and F10 keys during startup to prevent access to the **Advanced Startup Options** menu. |
|
||||
| DisplayDisabled | True or false | Configures the device to display a blank screen when the OS encounters an error that it cannot recover from. |
|
||||
| DisplayDisabled | True or false | Configures the device to display a blank screen if the OS has an error that it can't recover from. |
|
||||
| HideAllBootUI | True or false | Suppresses all Windows UI elements (logo, status indicator, and status message) during startup. |
|
||||
| HideAutologonUI | True or false | Hides the Welcome screen when automatic sign-in (AutoLogon) is enabled. |
|
||||
| HideBootLogo | True or false | Suppresses the default Windows logo that displays during the OS loading phase. |
|
||||
@ -43,7 +43,7 @@ The following table describes the settings in SMISettings. Some settings have ad
|
||||
| KeyboardFilter | See [KeyboardFilter settings](#keyboardfilter-settings) | Use these settings to configure devices to suppress key presses or key combinations. |
|
||||
| NoLockScreen | True or false | Disables the lock screen functionality and UI elements |
|
||||
| ShellLauncher | See [ShellLauncher settings](#shelllauncher-settings) | Settings used to specify the application or executable to use as the default custom shell. |
|
||||
| UIVerbosityLevel | Suppress or do not suppress | Disables the Windows status messages during device startup, sign-in, and shut down. |
|
||||
| UIVerbosityLevel | Suppress or don't suppress | Disables the Windows status messages during device startup, sign-in, and shut down. |
|
||||
|
||||
## BrandingNeutral values
|
||||
|
||||
@ -58,11 +58,11 @@ The default value is **17**, which disables all Welcome screen UI elements and t
|
||||
| 4 | Disables the Language button |
|
||||
| 8 | Disables the Ease of access button |
|
||||
| 16 | Disables the Switch user button |
|
||||
| 32 | Disables the blocked shutdown resolver (BSDR) screen so that restarting or shutting down the system causes the OS to immediately force close any applications that are blocking system shut down. No UI is displayed and users are not given a chance to cancel the shutdown process. This can result in a loss of data if any open applications have unsaved data. |
|
||||
| 32 | Disables the blocked shutdown resolver (BSDR) screen. Restarting or shutting down the system causes the OS to immediately force close any applications that are blocking the system shutdown. No UI is displayed, and users aren't given a chance to cancel the shutdown process. This value can result in a loss of data if any open applications have unsaved data. |
|
||||
|
||||
## CrashDumpEnabled values
|
||||
|
||||
Contains an integer that specifies the type of information to capture in a dump (.dmp) file that is generated when the system stops unexpectedly.
|
||||
If the system stops unexpectedly, choose the type of information to capture in a dump (.dmp) file.
|
||||
|
||||
The .dmp file is typically saved in %SystemRoot% as Memory.dmp.
|
||||
|
||||
@ -71,22 +71,22 @@ Set CrashDumpEnabled to one of the following values:
|
||||
| Value | Description |
|
||||
| --- | --- |
|
||||
| 1 | Records all the contents of system memory. This dump file may contain data from processes that were running when the information was collected. |
|
||||
| 2 | Records only the kernel memory. This dump file includes only memory that is allocated to the kernel, kernel-mode drivers, and other kernel-mode programs. It does not include unallocated memory or any memory that is allocated to user-mode programs.</br></br>For most purposes, this kind of dump file is the most useful because it is significantly smaller than the complete memory dump file, but it contains information that is most likely to have been involved in the issue.</br></br>If a second problem occurs, the dump file is overwritten with new information. |
|
||||
| 3 | Records the smallest amount of useful information that may help identify why the device stopped unexpectedly. This type of dump file includes the following information:</br></br>- A list of loaded drivers</br></br>- The processor context (PRCB) for the processor that stopped</br></br>- The process information and kernel context (EPROCESS) for the process that stopped</br></br>- The process information and kernel context (ETHREAD) for the thread that stopped</br></br>- The kernel-mode call stack for the thread that stopped</br></br></br>This kind of dump file can be useful when space is limited. However, because of the limited information included, errors that were not directly caused by the thread that was running at the time of the problem may not be discovered by analyzing this file.</br></br>The date is encoded in the file name. If a second problem occurs, the previous file is preserved and the new file is given a distinct name. A list of all small memory dump files is kept in the %SystemRoot%\Minidump folder. |
|
||||
| 2 | Records only the kernel memory. This dump file includes only memory that's allocated to the kernel, kernel-mode drivers, and other kernel-mode programs. It doesn't include unallocated memory, or any memory that's allocated to user-mode programs.</br></br> For most purposes, this kind of dump file is the most useful because it's smaller than the complete memory dump file. It also includes information that's most likely involved in the issue.</br></br> If a second problem occurs, the dump file is overwritten with new information. |
|
||||
| 3 | Records the smallest amount of useful information that may help identify why the device stopped unexpectedly. This type of dump file includes the following information:</br></br>- A list of loaded drivers</br>- The processor context (PRCB) for the processor that stopped</br>- The process information and kernel context (EPROCESS) for the process that stopped</br>- The process information and kernel context (ETHREAD) for the thread that stopped</br>- The kernel-mode call stack for the thread that stopped</br></br>This dump file can be useful when space is limited. Because of the limited information, errors that aren't directly caused by the running thread at the time of the problem may not be discovered by analyzing this file.</br></br> The date is encoded in the file name. If a second problem occurs, the previous file is preserved and the new file is given a distinct name. A list of all small memory dump files is kept in the %SystemRoot%\Minidump folder. |
|
||||
| 4 | Records the smallest amount of useful information. This value produces the same results as entering a value of 3. |
|
||||
| 7 | Records only the kernel memory. This value produces the same results as entering a value of 2. This is the default value. |
|
||||
| Any other value | Disables crash dump and does not record anything. |
|
||||
| Any other value | Disables crash dump and doesn't record anything. |
|
||||
|
||||
## KeyboardFilter settings
|
||||
|
||||
You can use KeyboardFilter to suppress undesirable key presses or key combinations. KeyboardFilter works with physical keyboards, the Windows on-screen keyboard, and the touch keyboard.
|
||||
Use these settings to suppress undesirable key presses or key combinations. KeyboardFilter works with physical keyboards, the Windows on-screen keyboard, and the touch keyboard.
|
||||
|
||||
When you **enable** KeyboardFilter, a number of other settings become available for configuration.
|
||||
When you **enable** KeyboardFilter, many other settings become available for configuration.
|
||||
|
||||
| Setting | Value | Description |
|
||||
| --- | --- | --- |
|
||||
| CustomKeyFilters | Allow or block | Add your own key filters to meet any special requirements that you may have that are not included in the predefined key filters. </br></br>Enter a custom key combination in **CustomKeyFilter**, and then select it to allow or block it. The format to add custom filter combinations is "Alt+F9." This also appears as the CustomKey name, which is specified without "+". For more information, see [WEKF_CustomKey](/windows-hardware/customize/enterprise/wekf-customkey). |
|
||||
| CustomScancodeFilters | Allow or block | Blocks the list of custom scan codes. When a key is pressed on a physical keyboard, the keyboard sends a scan code to the keyboard driver. The driver then sends the scan code to the OS and the OS converts the scan code into a virtual key based on the current active layout.</br></br>Enter a custom scancode in **CustomScancodeFilter**, and then select it to allow or block it. For more information, see [WEKF_Scancode](/windows-hardware/customize/enterprise/wekf-scancode). |
|
||||
| CustomKeyFilters | Allow or block | Add your own key filters to meet any special requirements that aren't included in the predefined key filters. </br></br>Enter a custom key combination in **CustomKeyFilter**, and then select it to allow or block it. The format to add custom filter combinations is "Alt+F9." This also appears as the CustomKey name, which is specified without "+". For more information, see [WEKF_CustomKey](/windows-hardware/customize/enterprise/wekf-customkey). |
|
||||
| CustomScancodeFilters | Allow or block | Blocks the list of custom scan codes. When a key is pressed on a physical keyboard, the keyboard sends a scan code to the keyboard driver. The driver then sends the scan code to the OS and the OS converts the scan code into a virtual key based on the current active layout.</br></br>Enter a custom scan code in **CustomScancodeFilter**, and then select it to allow or block it. For more information, see [WEKF_Scancode](/windows-hardware/customize/enterprise/wekf-scancode). |
|
||||
| DisableKeyboardFilterForAdministrators | True or false | Disables the keyboard filter for administrators. |
|
||||
| ForceOffAccessibility | True or false | Disables all Ease of Access features and prevents users from enabling them. |
|
||||
| PredefinedKeyFilters | Allow or block | Specifies the list of predefined keys. For each key, the value will default to **Allow**. Specifying **Block** will suppress the key combination. |
|
||||
@ -107,7 +107,7 @@ You can also configure ShellLauncher to launch different shell applications for
|
||||
>
|
||||
>You cannot use ShellLauncher to launch a Windows app as a custom shell. However, you can use Windows 10 application launcher to launch a Windows app at startup.
|
||||
|
||||
ShellLauncher processes the Run and RunOnce registry keys before starting the custom shell, so your custom shell doesn't need to handle the automatic startup of other applications or services. ShellLauncher also handles the behavior of the system when your custom shell exits. You can configure the shell exit behavior if the default behavior does not meet your needs.
|
||||
ShellLauncher processes the Run and RunOnce registry keys before starting the custom shell. So, your custom shell doesn't need to handle the automatic startup of other applications or services. ShellLauncher also handles the behavior of the system when your custom shell exits. You can configure the shell exit behavior if the default behavior doesn't meet your needs.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>A custom shell is launched with the same level of user rights as the account that is signed in. This means that a user with administrator rights can perform any system action that requires administrator rights, including launching other applications with administrator rights, while a user without administrator rights cannot. If your shell application requires administrator rights and needs to be elevated, and User Account Control (UAC) is present on your device, you must disable UAC in order for ShellLauncher to launch the shell application.
|
@ -21,6 +21,6 @@ Use StartupApp settings to configure the default app that will run on start for
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| Default | | | | | X |
|
||||
| Default | | | | | ✔️ |
|
||||
|
||||
Enter the [Application User Model ID (AUMID)](/windows-hardware/customize/enterprise/find-the-application-user-model-id-of-an-installed-app) for the default app.
|
@ -21,5 +21,5 @@ Documentation not available at this time.
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| All settings | | | | | X |
|
||||
| All settings | | | | | ✔️ |
|
||||
|
||||
|
@ -13,7 +13,10 @@ manager: dansimp
|
||||
|
||||
# StorageD3InModernStandby (Windows Configuration Designer reference)
|
||||
|
||||
Use **StorageD3InModernStandby** to enable or disable low power state (D3) during standby. When this setting is configured to **Enable Storage Device D3**, SATA and NVMe devices will be able to enter the D3 state when the system transits to modern standby state, if they are using a Microsoft inbox driver such as StorAHCI, StorNVMe.
|
||||
Use **StorageD3InModernStandby** to enable or disable low-power state (D3) during standby. When set to **Enable Storage Device D3**, SATA and NVMe devices can enter the D3 state when:
|
||||
|
||||
- The system transits to modern standby state.
|
||||
- If they're using a Microsoft inbox driver such as StorAHCI, StorNVMe
|
||||
|
||||
[Learn more about device power states.](/windows-hardware/drivers/kernel/device-power-states)
|
||||
|
||||
@ -21,4 +24,4 @@ Use **StorageD3InModernStandby** to enable or disable low power state (D3) durin
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| All settings | X | X | X | | X |
|
||||
| All settings | ✔️ | ✔️ | ✔️ | | ✔️ |
|
@ -26,7 +26,7 @@ Use SurfaceHubManagement settings to set the administrator group that will manag
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| All settings | | | X | | |
|
||||
| All settings | | | ✔️ | | |
|
||||
|
||||
|
||||
## GroupName
|
||||
|
@ -21,7 +21,7 @@ Use TabletMode to configure settings related to tablet mode.
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| All settings | X | X | X | | |
|
||||
| All settings | ✔️ | ✔️ | ✔️ | | |
|
||||
|
||||
## ConvertibleSlateModePromptPreference
|
||||
|
||||
|
@ -21,11 +21,11 @@ Use TakeATest to configure the Take A Test app, a secure browser for test-taking
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| All settings | X | | | | |
|
||||
| All settings | ✔️ | | | | |
|
||||
|
||||
## AllowScreenMonitoring
|
||||
|
||||
When set to True, students are able to record and take screen captures in the Take A Test app.
|
||||
When set to True, students can record and take screen captures in the Take A Test app.
|
||||
|
||||
## AllowTextSuggestions
|
||||
|
||||
@ -43,9 +43,8 @@ When set to True, students can print in the Take A Test app.
|
||||
|
||||
Enter the account to use when taking a test.
|
||||
|
||||
To specify a domain account, enter **domain\user**. To specify an AAD account, enter <strong>username@tenant.com</strong>. To specify a local account, enter the username.
|
||||
To specify a domain account, enter **domain\user**. To specify an Azure AD account, enter `username@tenant.com`. To specify a local account, enter the username.
|
||||
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [SecureAssessment configuration service provider (CSP)](/windows/client-management/mdm/secureassessment-csp)
|
@ -21,8 +21,8 @@ Use TextInput settings to configure text intelligence and keyboard for mobile de
|
||||
|
||||
| Setting groups | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| Intelligence > DisablePredictions | | X | | | |
|
||||
| PreEnabledKeyboard | | X | | | |
|
||||
| Intelligence > DisablePredictions | | ✔️ | | | |
|
||||
| PreEnabledKeyboard | | ✔️ | | | |
|
||||
|
||||
## Intelligence
|
||||
|
||||
@ -30,16 +30,16 @@ Set **DisablePredictions** to the locale or alternative input language that must
|
||||
|
||||
## PreEnabledKeyboard
|
||||
|
||||
In addition to the automatically-enabled default keyboard, OEMs may choose to pre-enable more keyboards for a particular market.
|
||||
OEMs can use the default keyboard that's automatically enabled. They can also pre-enable more keyboards for a particular market.
|
||||
|
||||
During phone bring-up, OEMs must set the boot locale, or default locale, for the phone. During first boot, Windows Phone reads the locale setting and automatically enables a default keyboard based on the locale to keyboard mapping table in Set languages and locales.
|
||||
During phone bring-up, OEMs must set the boot locale, or default locale, for the phone. During first boot, Windows Phone reads the locale setting. It automatically enables a default keyboard based on the locale to keyboard-mapping table in Set languages and locales.
|
||||
|
||||
The mapping works for almost all regions and additional customizations are not needed unless specified in the pre-enabled keyboard column in Set languages and locales. If an OEM chooses to pre-enable more keyboards for a particular market, they can do so by specifying the setting. Pre-enabled keyboards will automatically be enabled during boot. Microsoft recommends that partners limit the number of pre-enabled keyboards to those languages that correspond to the languages spoken within the market.
|
||||
The mapping works for almost all regions. More customizations aren't needed unless specified in the pre-enabled keyboard column in Set languages and locales. If an OEM chooses to pre-enable more keyboards for a particular market, they enter the setting. Pre-enabled keyboards will automatically be enabled during boot. Microsoft recommends limiting the number of pre-enabled keyboards to the languages that correspond to the languages spoken within the market.
|
||||
|
||||
|
||||
PreEnabledKeyboard must be entered once for each keyboard you want to pre-enable. As shown below, the format to specify a particular keyboard must be: Locale code.Locale value. See the following table for more information on the locale codes and values that you can use. The setting Value must be set to 1 to enable the keyboard.
|
||||
PreEnabledKeyboard must be entered once for each keyboard you want to pre-enable. As shown below, the format to specify a particular keyboard must be: `Locale code.Locale value`. For more information on the locale codes and values that you can use, see the following table. The setting Value must be set to 1 to enable the keyboard.
|
||||
|
||||
The following table shows the values that you can use for the Locale code.Locale value part of the setting name.
|
||||
The following table shows the values that you can use for the `Locale code.Locale value` part of the setting name.
|
||||
|
||||
>[!NOTE]
|
||||
>The keyboards for some locales require additional language model files: am-ET, bn-IN, gu-IN, hi-IN, ja-JP, kn-IN, ko-KR, ml-IN, mr-IN, my-MM, or-IN, pa-IN, si-LK, ta-IN, te-IN, zh-TW, zh-CN, and zh-HK.
|
||||
|
@ -19,7 +19,7 @@ Use **Time** to configure settings for time zone setup for Windows 10, version (
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| [ProvisionSetTimeZone](#provisionsettimezone) | X | | | | |
|
||||
| [ProvisionSetTimeZone](#provisionsettimezone) | ✔️ | | | | |
|
||||
|
||||
## ProvisionSetTimeZone
|
||||
|
||||
|
@ -15,14 +15,22 @@ manager: dansimp
|
||||
# UnifiedWriteFilter (reference)
|
||||
|
||||
|
||||
Use UnifiedWriteFilter to configure settings for the Unified Write Filter (UWF) in your device to help protect your physical storage media, including most standard writable storage types that are supported by the OS, such as physical hard disks, solidate-state drives, internal USB devices, external SATA devices, and so on. You can also use UWF to make read-only media appear to the OS as a writeable volume.
|
||||
Use UnifiedWriteFilter to configure settings for the Unified Write Filter (UWF). It helps protect your physical storage media, including most standard writable storage types that are supported by the OS, such as:
|
||||
|
||||
- Physical hard disks
|
||||
- Solidate-state drives
|
||||
- Internal USB devices
|
||||
- External SATA devices
|
||||
- And so on
|
||||
|
||||
You can also use UWF to make read-only media appear to the OS as a writeable volume.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>You cannot use UWF to protect external USB devices or flash drives.
|
||||
>You can't use UWF to protect external USB devices or flash drives.
|
||||
|
||||
UWF intercepts all write attempts to a protected volume and redirects those write attempts to a virtual overlay. This improves the reliability and stability of your device and reduces the wear on write-sensitive media, such as flash memory media like solid-state drives.
|
||||
UWF intercepts all write attempts to a protected volume and redirects these write attempts to a virtual overlay. This feature improves the reliability and stability of your device. It also reduces the wear on write-sensitive media, such as flash memory media like solid-state drives.
|
||||
|
||||
The overlay does not mirror the entire volume, but dynamically grows to keep track of redirected writes. Generally the overlay is stored in system memory, although you can cache a portion of the overlay on a physical volume.
|
||||
The overlay doesn't mirror the entire volume. It dynamically grows to keep track of redirected writes. Generally, the overlay is stored in system memory. You can cache a portion of the overlay on a physical volume.
|
||||
|
||||
>[!NOTE]
|
||||
>UWF fully supports the NTFS system; however, during device startup, NTFS file system journal files can write to a protected volume before UWF has loaded and started protecting the volume.
|
||||
@ -34,7 +42,7 @@ The overlay does not mirror the entire volume, but dynamically grows to keep tra
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| All settings | X | | | | X |
|
||||
| All settings | ✔️ | | | | ✔️ |
|
||||
|
||||
## FilterEnabled
|
||||
|
||||
@ -42,9 +50,9 @@ Set to **True** to enable UWF.
|
||||
|
||||
## OverlayFlags
|
||||
|
||||
OverlayFlags specifies whether to allow writes to unused space on the volume to pass through, and not be redirected to the overlay file. Enabling this setting helps conserve space on the overlay file.
|
||||
OverlayFlags specifies whether to allow writes to unused space on the volume to pass through, and not redirect to the overlay file. Enabling this setting helps conserve space on the overlay file.
|
||||
|
||||
- Value `0` (default value when [OverlayType](#overlaytype) is not **Disk**): writes are redirected to the overlay file
|
||||
- Value `0` (default value when [OverlayType](#overlaytype) isn't **Disk**): writes are redirected to the overlay file
|
||||
- Value `1`(default value when [OverlayType](#overlaytype) is **Disk**): writes to unused space on the volume are allowed to pass through without being redirected to the overlay file.
|
||||
|
||||
## OverlaySize
|
||||
@ -60,7 +68,7 @@ OverlayType specifies where the overlay is stored. Select between **RAM** (defau
|
||||
|
||||
## RegistryExclusions
|
||||
|
||||
You can add or remove registry entries that will be excluded from UWF filtering. When a registry key is in the exclusion list, all writes to that registry key bypass UWF filtering and are written directly to the registry and persist after the device restarts.
|
||||
You can add or remove registry entries that will be excluded from UWF filtering. When a registry key is in the exclusion list, all writes to that registry key bypass UWF filtering. They're written directly to the registry and persist after the device restarts.
|
||||
|
||||
Use **Add** to add a registry entry to the exclusion list after you restart the device.
|
||||
|
||||
|
@ -24,15 +24,15 @@ Use UniversalAppInstall settings to install Windows apps from the Microsoft Stor
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| [DeviceContextApp](#devicecontextapp) | X | | X | | |
|
||||
| [DeviceContextAppLicense](#devicecontextapplicense) | X | | X | | |
|
||||
| [StoreInstall](#storeinstall) | X | X | X | | X |
|
||||
| [UserContextApp](#usercontextapp) | X | X | X | | X |
|
||||
| [UserContextAppLicense](#usercontextapplicense) | X | X | X | | X |
|
||||
| [DeviceContextApp](#devicecontextapp) | ✔️ | | ✔️ | | |
|
||||
| [DeviceContextAppLicense](#devicecontextapplicense) | ✔️ | | ✔️ | | |
|
||||
| [StoreInstall](#storeinstall) | ✔️ | ✔️ | ✔️ | | ✔️ |
|
||||
| [UserContextApp](#usercontextapp) | ✔️ | ✔️ | ✔️ | | ✔️ |
|
||||
| [UserContextAppLicense](#usercontextapplicense) | ✔️ | ✔️ | ✔️ | | ✔️ |
|
||||
|
||||
## DeviceContextApp
|
||||
|
||||
Enter an app package family name to install an app for all users of the device. You can use the [Get-AppxPackage cmdlet](/powershell/module/appx/get-appxpackage) to get the package family name for an installed app.
|
||||
Enter an app package family name to install an app for all device users. You can use the [Get-AppxPackage cmdlet](/powershell/module/appx/get-appxpackage) to get the package family name for an installed app.
|
||||
|
||||
>[!NOTE]
|
||||
>For XAP files, enter the product ID.
|
||||
@ -41,11 +41,11 @@ For each app that you add to the package, configure the settings in the followin
|
||||
|
||||
| Setting | Value | Description |
|
||||
| --- | --- | --- |
|
||||
| ApplicationFile | .appx or .appxbundle | Set the value to the app file that you want to install on the device. In addition, you must also enable the [AllowAllTrustedApps setting](wcd-policies.md#applicationmanagement) and add a root certificate or license file. |
|
||||
| DependencyAppxFiles | any required frameworks | In Microsoft Store for Business, any dependencies for the app are listed in the **Required frameworks** section of the download page. |
|
||||
| DeploymentOptions | - None</br>-Force application shutdown: If this package, or any package that depends on this package, is currently in use, the processes associated with the package are shut down forcibly so that registration can continue</br>- Development mode: do not use</br>- Install all resources: When you set ths option, the app is instructed to skip resource applicability checks.</br>- Force target application shutdown: If this package is currently in use, the processes associated with the package are shut down forcibly so that registration can continue | Select a deployment option. |
|
||||
| LaunchAppAtLogin | - Do not launch app</br>- Launch app | Set the value for app behavior when a user signs in. |
|
||||
| OptionalPackageFiles | additional files required by the package | Browse to, select, and add the optional package files. |
|
||||
| ApplicationFile | `.appx` or `.appxbundle` | Set the value to the app file that you want to install on the device. Also enable the [AllowAllTrustedApps setting](wcd-policies.md#applicationmanagement) and add a root certificate or license file. |
|
||||
| DependencyAppxFiles | Any required frameworks | In Microsoft Store for Business, any dependencies for the app are listed in the **Required frameworks** section of the download page. |
|
||||
| DeploymentOptions | - None</br>-Force application shutdown: If this package, or any package that depends on this package is currently in use, then the processes associated with the package are forcibly shut down. The registration can continue. </br>- Development mode: Don't use. </br>- Install all resources: When you set this option, the app is instructed to skip resource applicability checks.</br>- Force target application shutdown: If this package is currently in use, the processes associated with the package are shut down forcibly so that registration can continue | Select a deployment option. |
|
||||
| LaunchAppAtLogin | - Don't launch app</br>- Launch app | Set the value for app behavior when a user signs in. |
|
||||
| OptionalPackageFiles | Additional files required by the package | Browse to, select, and add the optional package files. |
|
||||
|
||||
For more information on deployment options, see [DeploymentOptions Enum](/uwp/api/windows.management.deployment.deploymentoptions).
|
||||
|
||||
@ -53,7 +53,7 @@ For more information on deployment options, see [DeploymentOptions Enum](/uwp/ap
|
||||
|
||||
Use to specify the license file for the provisioned app.
|
||||
|
||||
1. Specify a **LicenseProductId** for the app. You can find the license ID in the root header of the license file. Here is an example, `LicenseID="aaaaaaaa-dddd-8848-f8d0-7d6a93dfcccc"`. Enter it in the LicenseProductId field, and click **Add**.
|
||||
1. Specify a **LicenseProductId** for the app. You can find the license ID in the root header of the license file. For example, enter `LicenseID="aaaaaaaa-dddd-8848-f8d0-7d6a93dfcccc"`. Enter it in the LicenseProductId field, and select **Add**.
|
||||
|
||||
2. Select the LicenseProductId in the Available Customizations pane, and then browse to and select the app license file.
|
||||
|
||||
@ -62,7 +62,7 @@ Use to specify the license file for the provisioned app.
|
||||
|
||||
Use to install an app from the Microsoft Store for Business.
|
||||
|
||||
1. Enter a package family name, and then click **Add**.
|
||||
1. Enter a package family name, and then select **Add**.
|
||||
2. Configure the following required settings for the app package.
|
||||
|
||||
Setting | Description
|
||||
@ -75,21 +75,21 @@ SkuID | Enter the SKU ID. [Learn how to find the SKU ID.](/microsoft-store/micro
|
||||
|
||||
Use to add a new user context app.
|
||||
|
||||
1. Specify a **PackageFamilyName** for the app, and then click **Add**.
|
||||
1. Specify a **PackageFamilyName** for the app, and then select **Add**.
|
||||
2. Select the PackageFamilyName in the Available Customizations pane, and then configure the following settings.
|
||||
|
||||
Setting | Value | Description
|
||||
--- | --- | ---
|
||||
ApplicationFile | app file | Browse to, select, and add the application file,
|
||||
DependencyAppxFiles | additional files required by the app | Browse to, select, and add dependency files.
|
||||
ApplicationFile | App file | Browse to, select, and add the application file,
|
||||
DependencyAppxFiles | Additional files required by the app | Browse to, select, and add dependency files.
|
||||
DeploymentOptions | - None</br></br>- Force application shutdown</br></br>- Development mode</br></br>- Install all resources</br></br>- Force target application shutdown | Select a deployment option.
|
||||
LaunchAppAtLogin | - Do not launch app</br></br>- Launch app | Select whether the app should be started when a user signs in.
|
||||
LaunchAppAtLogin | - Don't launch app</br></br>- Launch app | Select whether the app should be started when a user signs in.
|
||||
|
||||
|
||||
## UserContextAppLicense
|
||||
|
||||
Use to specify the license file for the user context app.
|
||||
|
||||
1. Specify a **LicenseProductId** for the app. You can find the license ID in the root header of the license file. Here is an example, `LicenseID="aaaaaaaa-dddd-8848-f8d0-7d6a93dfcccc"`. Enter it in the LicenseProductId field, and click **Add**.
|
||||
1. Specify a **LicenseProductId** for the app. You can find the license ID in the root header of the license file. For example, enter `LicenseID="aaaaaaaa-dddd-8848-f8d0-7d6a93dfcccc"`. Enter it in the LicenseProductId field, and select **Add**.
|
||||
|
||||
2. Select the LicenseProductId in the Available Customizations pane, and then browse to and select the app license file.
|
@ -22,21 +22,21 @@ Use UniversalAppUninstall settings to uninstall or remove Windows apps.
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| [RemoveProvisionedApp](#removeprovisionedapp) | X | | | | |
|
||||
| [Uninstall](#uninstall) | X | X | X | | X |
|
||||
| [RemoveProvisionedApp](#removeprovisionedapp) | ✔️ | | | | |
|
||||
| [Uninstall](#uninstall) | ✔️ | ✔️ | ✔️ | | ✔️ |
|
||||
|
||||
## RemoveProvisionedApp
|
||||
|
||||
Universal apps can be *provisioned*, which means that they are available on the device for installation in user context. When a user runs the provisioned app, the app is then installed for that user.
|
||||
Universal apps can be *provisioned*. Provisioned means that they're available on the device for installation in user context. When a user runs the provisioned app, the app is then installed for that user.
|
||||
|
||||
Use **RemoveProvisionedApp** to remove app packages that are available on the device. Any instances of the app that have already been installed by a user are not uninstalled. To uninstall provisioned apps that have been installed by a user, use the [Uninstall](#uninstall) setting.
|
||||
Use **RemoveProvisionedApp** to remove app packages that are available on the device. Any instances of the app that have already been installed by a user aren't uninstalled. To uninstall provisioned apps that have been installed by a user, use the [Uninstall](#uninstall) setting.
|
||||
|
||||
1. Enter the PackageFamilyName for the app package, and then click **Add**.
|
||||
1. Enter the PackageFamilyName for the app package, and then select **Add**.
|
||||
2. Select the PackageFamilyName in the Available Customizations pane, and then select **RemoveProvisionedApp**.
|
||||
|
||||
## Uninstall
|
||||
|
||||
Use **Uninstall** to remove provisioned apps that have been installed by a user.
|
||||
|
||||
1. Enter the PackageFamilyName for the app package, and then click **Add**.
|
||||
1. Enter the PackageFamilyName for the app package, and then select **Add**.
|
||||
2. Select the PackageFamilyName in the Available Customizations pane, and then select **Uninstall**.
|
||||
|
@ -22,7 +22,7 @@ Allows an OEM to hide the USB option UI in Settings and all USB device errors.
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| [HideUsbErrorNotifyOptionUI](#hideusberrornotifyoptionui) | X | X | X | X | |
|
||||
| [HideUsbErrorNotifyOptionUI](#hideusberrornotifyoptionui) | ✔️ | ✔️ | ✔️ | ✔️ | |
|
||||
|
||||
## HideUsbErrorNotifyOptionUI
|
||||
|
||||
|
@ -22,8 +22,8 @@ Use WeakCharger settings to configure the charger notification UI.
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| [HideWeakChargerNotifyOptionUI](#hideweakchargernotifyoptionui) | X | X | X | | |
|
||||
| [NotifyOnWeakCharger](#notifyonweakcharger) | X | X | X | | |
|
||||
| [HideWeakChargerNotifyOptionUI](#hideweakchargernotifyoptionui) | ✔️ | ✔️ | ✔️ | | |
|
||||
| [NotifyOnWeakCharger](#notifyonweakcharger) | ✔️ | ✔️ | ✔️ | | |
|
||||
|
||||
|
||||
## HideWeakChargerNotifyOptionUI
|
||||
@ -34,12 +34,15 @@ Select between **Show Weak Charger Notifications UI** and **Hide Weak Charger No
|
||||
|
||||
## NotifyOnWeakCharger
|
||||
|
||||
This setting displays a warning when the user connects the device to an incompatible charging source. This warning is intended to notify users that their device may take longer to charge or may not charge at all with the current charging source.
|
||||
This setting shows a warning when the user connects the device to an incompatible charging source. This warning is intended to notify users that their device may take longer to charge. Or, it may not charge at all.
|
||||
|
||||
An incompatible charging source is one that doesn't behave like one of the following port types:
|
||||
|
||||
An incompatible charging source is one that does not behave like one of the following port types as defined by the USB Battery Charging Specification, Revision 1.2, available on the USB.org website:
|
||||
- Charging downstream port
|
||||
- Standard downstream port
|
||||
- Dedicated charging port
|
||||
|
||||
The port types are defined by the USB Battery Charging Specification, Revision 1.2, available at `USB.org`.
|
||||
|
||||
Select between **Disable Weak Charger Notifications UI** and **Enable Weak Charger Notifications UI**.
|
||||
|
||||
|
@ -15,17 +15,17 @@ manager: dansimp
|
||||
# WindowsHelloForBusiness (Windows Configuration Designer reference)
|
||||
|
||||
|
||||
Use WindowsHelloForBusiness settings to specify whether [FIDO2 security keys for Windows Hello](https://blogs.windows.com/business/2018/04/17/windows-hello-fido2-security-keys/) can be used to sign in to Windows on a device configured for [Shared PC mode](wcd-sharedpc.md).
|
||||
Use WindowsHelloForBusiness settings to specify whether [FIDO2 security keys for Windows Hello](https://blogs.windows.com/business/2018/04/17/windows-hello-fido2-security-keys/) can be used to sign in to a Windows device configured for [Shared PC mode](wcd-sharedpc.md).
|
||||
|
||||
## Applies to
|
||||
|
||||
| Setting groups | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| [SecurityKeys](#securitykeys) | X | | | | |
|
||||
| [SecurityKeys](#securitykeys) | ✔️ | | | | |
|
||||
|
||||
## SecurityKeys
|
||||
|
||||
Select the desired value:
|
||||
Select the value:
|
||||
|
||||
- `0`: security keys for Windows Hello are disabled.
|
||||
- `1`: security keys for Windows Hello are enabled on [Shared PCs](wcd-sharedpc.md).
|
||||
- `0`: Security keys for Windows Hello are disabled.
|
||||
- `1`: Security keys for Windows Hello are enabled on [Shared PCs](wcd-sharedpc.md).
|
||||
|
@ -22,31 +22,31 @@ Use WindowsTeamSettings settings to configure Surface Hub.
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| All settings | | | X | | |
|
||||
| All settings | | | ✔️ | | |
|
||||
|
||||
## Connect
|
||||
|
||||
| Setting | Value | Description |
|
||||
| --- | --- | --- |
|
||||
| AutoLaunch | True or false | Open the Connect app automatically when someone projects. |
|
||||
| Channel | - 1, 3, 4, 5, 6, 7, 8, 9, 10, 11 (works with all Miracast senders in all regions)</br>- 36, 40, 44, 48 (works with all 5ghz band Miracast senders in all regions)</br>- 149, 153, 157, 161, 165 (works with all 5ghz band Miracast senders in all regions except Japan) | Wireless channel to use for Miracast operation. The supported channels are defined by the Wi-Fi Alliance Wi-Fi Direct specification. Integer specifying the channel. The default value is 255. Outside of regulatory concerns, if the channel is configured incorrectly the driver will either not boot, or will broadcast on the wrong channel (which senders won't be looking for). |
|
||||
| Channel | - 1, 3, 4, 5, 6, 7, 8, 9, 10, 11 (works with all Miracast senders in all regions)</br>- 36, 40, 44, 48 (works with all 5ghz band Miracast senders in all regions)</br>- 149, 153, 157, 161, 165 (works with all 5ghz band Miracast senders in all regions except Japan) | Wireless channel to use for Miracast operation. The supported channels are defined by the Wi-Fi Alliance Wi-Fi Direct specification. Integer specifying the channel. The default value is 255. Outside of regulatory concerns, if the channel is configured incorrectly, the driver won't boot. Or, it will broadcast on the wrong channel, which senders won't be looking for. |
|
||||
| Enabled | True or false | Enables wireless projection to the device. |
|
||||
| PINRequired | True or false | Requires presenters to enter a PIN to connect wirelessly to the device. |
|
||||
|
||||
## DeviceAccount
|
||||
|
||||
A device account is a Microsoft Exchange account that is connected with Skype for Business, which allows people to join scheduled meetings, make Skype for Business calls, and share content from the device.
|
||||
A device account is a Microsoft Exchange account that's connected with Skype for Business. It allows people to join scheduled meetings, make Skype for Business calls, and share content from the device.
|
||||
|
||||
| Setting | Value | Description |
|
||||
| --- | --- | --- |
|
||||
| CalendarSyncEnabled | True or false | Specifies whether calendar sync and other Exchange Server services are enabled. |
|
||||
| DomainName | Domain of the device account when you are using Active Directory | To use a device account from Active Directory, you should specify both **DomainName** and **UserName** for the device account. |
|
||||
| DomainName | Domain of the device account when using Active Directory | To use a device account from Active Directory, you should specify both **DomainName** and **UserName** for the device account. |
|
||||
| Email | Email address | Email address of the device account. |
|
||||
| ExchangeServer | Exchange Server | Normally, the device will try to automatically discover the Exchange server. This field is only required if automatic discovery fails. |
|
||||
| Password | Password | Password for the device account. |
|
||||
| PasswordRotationEnabled | 0 = enabled</br>1 = disabled | Specifies whether automatic password rotation is enabled. If you enforce a password expiration policy on the device account, use this setting to allow the device to manage its own password by changing it frequently, without requiring you to manually update the account information when the password expires. You can reset the password at any time using Active Directory or Azure AD. |
|
||||
| PasswordRotationEnabled | 0 = enabled</br>1 = disabled | Specifies whether automatic password rotation is enabled. If you enforce a password expiration policy on the device account, then use this setting to allow the device to manage its own password. It can change the password frequently, without requiring you to manually update the account information when the password expires. You can reset the password at any time using Active Directory or Azure AD. |
|
||||
| SipAddress | Session Initiation Protocol (SIP) address | Normally, the device will try to automatically discover the SIP. This field is only required if automatic discovery fails. |
|
||||
| UserName | User name | Username of the device account when you are using Active Directory. |
|
||||
| UserName | User name | Username of the device account when using Active Directory. |
|
||||
| UserPrincipalName | User principal name (UPN) | To use a device account from Azure Active Directory or a hybrid deployment, you should specify the UPN of the device account. |
|
||||
| ValidateAndCommit | Any text | Validates the data provided and then commits the changes. This process occurs automatically after the other DeviceAccount settings are applied. The text you enter for the ValidateAndCommit setting doesn't matter. |
|
||||
|
||||
@ -62,11 +62,11 @@ Enter the name that users will see when they want to project wirelessly to the d
|
||||
|
||||
## MaintenanceHours
|
||||
|
||||
Maintenance hours are the period of time during which automatic maintenance tasks are performed.
|
||||
Maintenance hours are the period of time when automatic maintenance tasks are run.
|
||||
|
||||
| Setting | Value | Description |
|
||||
| --- | --- | --- |
|
||||
| Duration | Duration in minutes. For example, to set a 3-hour duration, set this value to 180. | The amount of time the device will be in maintenance, when the device will continue to download or install updates. |
|
||||
| Duration | Duration in minutes. For example, to set a three hour duration, set this value to 180. | The amount of time the device will be in maintenance, when the device will continue to download or install updates. |
|
||||
| StartTime | Start time in minutes from midnight. For example, to set a 2:00 am start time, set this value to 120 | Start time for when device is allowed to start downloading and installing updates. |
|
||||
|
||||
## OMSAgent
|
||||
@ -75,7 +75,7 @@ Configures the Operations Management Suite workspace.
|
||||
|
||||
| Setting | Value | Description |
|
||||
| --- | --- | --- |
|
||||
| WorkspaceID | GUID | GUID identifying the Operations Management Suite workspace ID to collect the data. Set this to an empty string to disable the MOM agent. |
|
||||
| WorkspaceID | GUID | GUID identifying the Operations Management Suite workspace ID to collect the data. Set this value to an empty string to disable the MOM agent. |
|
||||
| WorkspaceKey | Key | Primary key for authenticating with the workspace. |
|
||||
|
||||
## Properties
|
||||
@ -85,7 +85,7 @@ Configures the Operations Management Suite workspace.
|
||||
| AllowAutoProxyAuth | True or false | Specifies if the Surface Hub can use the device account to authenticate into proxy servers requiring authentication. |
|
||||
| AllowSessionResume | True or false | Specifies if users are allowed to resume their session after session timeout. |
|
||||
| DefaultVolume | Numeric value between 0 and 100 | Default speaker volume. Speaker volume will be set to this value at every session startup. |
|
||||
| DisableSigninSuggestions | True or false | Specifies if the Surface Hub will not show suggestions when users try to sign in to see their meetings and files. |
|
||||
| DisableSigninSuggestions | True or false | Specifies if the Surface Hub won't show suggestions when users try to sign in to see their meetings and files. |
|
||||
| DoNotShowMyMeetingsAndFiles | True or false | Specifies if users can sign in and have full access to personal meetings and most recently used documents. |
|
||||
| ScreenTimeout | Select minutes from dropdown menu | The time (in minutes) of inactivity after which the Surface Hub will turn off its screen. |
|
||||
| SessionTimeout | Select minutes from dropdown menu | The time (in minutes) of inactivity after which the Surface Hub will time out the current session and return to the welcome screen. |
|
||||
@ -105,6 +105,6 @@ Configures the Operations Management Suite workspace.
|
||||
| CurrentBackgroundPath | Https URL to a PNG file | Background image for the welcome screen. |
|
||||
| MeetingInfoOption | 0 = organizer and time only</br>1 = organizer, time, and subject (subject is hidden for private meetings) | Specifies whether meeting information is displayed on the welcome screen. |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [SurfaceHub configuration service provider (CSP)](/windows/client-management/mdm/surfacehub-csp)
|
@ -22,11 +22,11 @@ Use Workplace settings to configure bulk user enrollment to a mobile device mana
|
||||
|
||||
| Setting | Desktop editions | Mobile editions | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| [Enrollments](#enrollments) | X | X | X | | X |
|
||||
| [Enrollments](#enrollments) | ✔️ | ✔️ | ✔️ | | ✔️ |
|
||||
|
||||
## Enrollments
|
||||
|
||||
Select **Enrollments**, enter a UPN, and then click **Add** to configure the settings for the enrollment. The UPN is a unique identifier for enrollment. For bulk enrollment, this must a service account that is allowed to enroll multiple users. Example, "generic-device@contoso.com"
|
||||
Select **Enrollments**, enter a UPN, and then select **Add** to configure the settings for the enrollment. The UPN is a unique identifier for enrollment. For bulk enrollment, this value must be a service account that's allowed to enroll multiple users. For example, use `generic-device@contoso.com`.
|
||||
|
||||
| Settings | Value | Description |
|
||||
| --- | --- | --- |
|
||||
@ -34,8 +34,8 @@ Select **Enrollments**, enter a UPN, and then click **Add** to configure the set
|
||||
| DiscoveryServiceFullUrl | URL | The full URL for the discovery service |
|
||||
| EnrollmentServiceFullUrl | URL | The full URL for the enrollment service |
|
||||
| PolicyServiceFullUrl | URL | The full URL for the policy service |
|
||||
| Secret | - Password string for on-premises authentication enrollment</br>- Federated security token for federated enrollment</br>- Certificate thumb print for certificate-based enrollment | Enter the appropriate value for the selected AuthPolicy |
|
||||
| Secret | - Password string for on-premises authentication enrollment</br>- Federated security token for federated enrollment</br>- Certificate thumb print for certificate-based enrollment | Enter the appropriate value for the selected AuthPolicy. |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [Provisioning configuration service provider (CSP)](/windows/client-management/mdm/provisioning-csp)
|
@ -208,6 +208,8 @@
|
||||
href: update/update-compliance-security-update-status.md
|
||||
- name: Feature update status report
|
||||
href: update/update-compliance-feature-update-status.md
|
||||
- name: Safeguard holds report
|
||||
href: update/update-compliance-safeguard-holds.md
|
||||
- name: Delivery Optimization in Update Compliance
|
||||
href: update/update-compliance-delivery-optimization.md
|
||||
- name: Data handling and privacy in Update Compliance
|
||||
|
@ -29,6 +29,7 @@ The deployment service is designed for IT Pros who are looking for more control
|
||||
- You can stage deployments over a period of days or weeks by using rich expressions (for example, deploy 20H2 to 500 devices per day, beginning on March 14, 2021).
|
||||
- You can bypass pre-configured Windows Update for Business policies to immediately deploy a security update across your organization when emergencies arise.
|
||||
- You can benefit from deployments with automatic piloting tailored to your unique device population to ensure coverage of hardware and software in your organization.
|
||||
- You can use safeguards against likely update issues that have been identified by Microsoft machine-learning algorithms and automatically hold the deployment for any affected devices.
|
||||
|
||||
The service is privacy focused and backed by leading industry compliance certifications.
|
||||
|
||||
@ -52,7 +53,6 @@ Using the deployment service typically follows a common pattern:
|
||||
2. The chosen tool conveys your approval, scheduling, and device selection information to the deployment service.
|
||||
3. The deployment service processes the content approval and compares it with previously approved content. Final update applicability is determined and conveyed to Windows Update, which then offers approved content to devices on their next check for updates.
|
||||
|
||||
|
||||
The deployment service exposes these capabilities through Microsoft [Graph REST APIs](/graph/overview). You can call the APIs directly, through a Graph SDK, or integrate them with a management tool such as Microsoft Endpoint Manager.
|
||||
|
||||
## Prerequisites
|
||||
@ -74,7 +74,6 @@ Additionally, your organization must have one of the following subscriptions:
|
||||
- Windows Virtual Desktop Access E3 or E5
|
||||
- Microsoft 365 Business Premium
|
||||
|
||||
|
||||
## Getting started
|
||||
|
||||
To use the deployment service, you use a management tool built on the platform, script common actions using PowerShell, or build your own application.
|
||||
@ -87,7 +86,6 @@ Microsoft Endpoint Manager integrates with the deployment service to provide Win
|
||||
|
||||
The Microsoft Graph SDK includes a PowerShell extension that you can use to script and automate common update actions. For more information, see [Get started with the Microsoft Graph PowerShell SDK](/graph/powershell/get-started).
|
||||
|
||||
|
||||
### Building your own application
|
||||
|
||||
Microsoft Graph makes deployment service APIs available through. Get started with these learning paths:
|
||||
@ -113,14 +111,19 @@ This built-in piloting capability complements your existing ring structure and p
|
||||
|
||||
You should continue to use deployment rings as part of the servicing strategy for your organization, but use gradual rollouts to add scheduling convenience and additional protections within each ring.
|
||||
|
||||
### Safeguard holds against likely and known issues
|
||||
|
||||
Microsoft uses [safeguard holds](/windows/deployment/update/safeguard-holds) to protect devices from encountering known quality or compatibility issues by preventing them from installing the update or upgrade. For Windows 11 deployments, the deployment service extends these safeguard holds to also protect devices that Microsoft identifies as being at a higher risk of experiencing problems after an update (such as operating system rollbacks, app crashes, or graphics issues). The service temporarily holds the deployment for these devices while Microsoft investigates the likely issue. Safeguard holds apply to deployments by default, but you can opt out.
|
||||
|
||||
To verify whether a device is affected by a safeguard hold, see [Am I affected by a safeguard hold?](/windows/deployment/update/safeguard-holds#am-i-affected-by-a-safeguard-hold)
|
||||
|
||||
### Monitoring deployments to detect rollback issues
|
||||
|
||||
During deployments of Windows 11 or Windows 10 feature updates, driver combinations can sometimes result in an unexpected update failure that makes the device revert to the previously installed operating system version. The deployment service can monitor devices for such issues and automatically pause deployments when this happens, giving you time to detect and mitigate issues.
|
||||
|
||||
|
||||
### How to enable deployment protections
|
||||
|
||||
Deployment scheduling controls are always available, but to take advantage of the unique deployment protections tailored to your organization, devices must share diagnostic data with Microsoft.
|
||||
Deployment scheduling controls are always available, but to take advantage of the unique deployment protections tailored to your population, devices must share diagnostic data with Microsoft.
|
||||
|
||||
#### Device prerequisites
|
||||
|
||||
|
@ -17,27 +17,27 @@ ms.topic: article
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
Microsoft uses quality and compatibility data to identify issues that might cause a Windows client feature update to fail or roll back. When we find such an issue, we might apply holds to the updating service to prevent affected devices from installing the update in order to safeguard them from these experiences. We also use holds when a customer, a partner, or Microsoft internal validation finds an issue that would cause severe impact (for example, rollback of the update, data loss, loss of connectivity, or loss of key functionality) and when a workaround is not immediately available.
|
||||
Microsoft uses quality and compatibility data to identify issues that might cause a Windows client feature update to fail or roll back. When we find such an issue, we might apply safeguard holds to the updating service to prevent affected devices from installing the update in order to safeguard them from these experiences. We also use safeguard holds when a customer, a partner, or Microsoft internal validation finds an issue that would cause severe impact (for example, rollback of the update, data loss, loss of connectivity, or loss of key functionality) and when a workaround is not immediately available.
|
||||
|
||||
Safeguard holds prevent a device with a known issue from being offered a new operating system version. We renew the offering once a fix is found and verified. We use holds to ensure customers have a successful experience as their device moves to a new version of Windows client.
|
||||
|
||||
The lifespan of holds varies depending on the time required to investigate and fix an issue. During this time Microsoft works diligently to procure, develop, and validate a fix and then offer it to affected devices. We monitor quality and compatibility data to confirm that a fix is complete before releasing the hold. Once we release the hold, Windows Update will resume offering new operating system versions to devices.
|
||||
The lifespan of safeguard holds varies depending on the time required to investigate and fix an issue. During this time, Microsoft works diligently to procure, develop, and validate a fix and then offer it to affected devices. We monitor quality and compatibility data to confirm that a fix is complete before releasing the safeguard hold. Once we release the safeguard hold, Windows Update will resume offering new operating system versions to devices.
|
||||
|
||||
Safeguard holds only affect devices that use the Window Update service for updates. We encourage IT admins who manage updates to devices through other channels (such as media installations or updates coming from Windows Server Update Services) to remain aware of known issues that might also be present in their environments.
|
||||
Safeguard holds only affect devices that use the Windows Update service for updates. We encourage IT admins who manage updates to devices through other channels (such as media installations or updates coming from Windows Server Update Services) to remain aware of known issues that might also be present in their environments.
|
||||
|
||||
IT admins managing updates using the [Windows Update for Business deployment service](/windows/deployment/update/deployment-service-overview) also benefit from safeguard holds on devices that are likely to be affected by an issue. To learn more, see [Safeguard holds against likely and known issues](/windows/deployment/update/deployment-service-overview#safeguard-holds-against-likely-and-known-issues).
|
||||
|
||||
## Am I affected by a safeguard hold?
|
||||
|
||||
IT admins can use [Update Compliance](update-compliance-feature-update-status.md#safeguard-holds) to monitor various update health metrics for devices in their organization, including ones affected by a safeguard hold that prevents them from updating to a newer operating system version.
|
||||
IT admins can use [Update Compliance](update-compliance-monitor.md) to monitor various update health metrics for devices in their organization. Update Compliance provides a [Safeguard Holds report](/windows/deployment/update/update-compliance-safeguard-holds), as well as [queries in the Feature Update Status report](/windows/deployment/update/update-compliance-feature-update-status), to provide you insight into the safeguard holds that are preventing devices from updating or upgrading.
|
||||
|
||||
Queries identify Safeguard IDs for each affected device, giving IT admins a detailed view into the various protections extended to devices. Safeguard IDs for publicly discussed known issues are also included in the [Windows release health](/windows/release-health/) dashboard, where you can easily find information related to publicly available safeguards.
|
||||
The Update Compliance reports identify safeguard holds by their 8-digit identifiers. For safeguard holds associated with publicly discussed known issues, you can find additional details about the issue on the [Windows release health](/windows/release-health/) dashboard by searching for the safeguard hold ID on the **Known issues** page for the relevant release.
|
||||
|
||||
On devices that use Windows Update (but not Windows Update for Business), the **Windows Update** page in the Settings app displays a message stating that an update is on its way, but not ready for the device. Instead of the option to download and install the update, users will see this message:
|
||||
|
||||
|
||||

|
||||
|
||||
If you see this message, it means one or more holds affect your device. When the issue is fixed and the update is safe to install, we’ll release the hold and the update can resume safely.
|
||||
This message means that the device is protected by one or more safeguard holds. When the issue is resolved and the update is safe to install, we will release the safeguard hold and the update can resume safely.
|
||||
|
||||
## What can I do?
|
||||
|
||||
@ -46,4 +46,4 @@ We recommend that you do not attempt to manually update until issues have been r
|
||||
> [!CAUTION]
|
||||
> Opting out of a safeguard hold can put devices at risk from known performance issues. We strongly recommend that you complete robust testing to ensure the impact is acceptable before opting out.
|
||||
|
||||
With that in mind, IT admins who stay informed with [Update Compliance](update-compliance-feature-update-status.md#safeguard-holds) and the [Windows release health](/windows/release-health/) dashboard can choose to temporarily [opt-out of the protection of all safeguard holds](safeguard-opt-out.md) and allow an update to proceed. We recommend opting out only in an IT environment and for validation purposes. If you do opt out of a hold, this condition is temporary. Once an update is complete, the protection of safeguard holds is reinstated automatically.
|
||||
With that in mind, IT admins who stay informed with [Update Compliance](update-compliance-feature-update-status.md#safeguard-holds) and the [Windows release health](/windows/release-health/) dashboard can choose to temporarily [opt-out of the protection of all safeguard holds](safeguard-opt-out.md) and allow an update to proceed. We recommend opting out only in an IT environment and for validation purposes. If you do opt out of a hold, this condition is temporary. Once an update is complete, the protection of safeguard holds is reinstated automatically.
|
||||
|
@ -43,18 +43,21 @@ Refer to the following list for what each state means:
|
||||
|
||||
## Safeguard holds
|
||||
|
||||
Microsoft uses diagnostic data to determine whether devices that use Windows Update are ready for a feature update in order to ensure a smooth experience. When Microsoft determines a device is not ready to update due to a known issue, a *safeguard hold* is generated to delay the device's upgrade and protect the end-user experience. Holds are released over time as diagnostic data is analyzed and fixes are addressed. Details are provided on some, but not all safeguard holds on the Windows client release information pages for any given release.
|
||||
Microsoft uses diagnostic data to determine whether devices that use Windows Update are ready for a feature update in order to ensure a smooth experience. When Microsoft determines a device is not ready to update due to a known issue, a *safeguard hold* is generated to delay the device's upgrade and protect the end-user experience. Safeguard holds are released over time as diagnostic data is analyzed and fixes are addressed. Details are provided on some, but not all safeguard holds on the Windows client release information pages for any given release.
|
||||
|
||||
### Queries for safeguard holds
|
||||
|
||||
Update Compliance reporting offers two queries to help you retrieve data related to safeguard holds. These queries show data for devices that are configured to send diagnostic data at the *Optional* level (previously *Full*). For Windows 10 devices, devices configured to send diagnostic data at *Enhanced* level are also included.
|
||||
> [!TIP]
|
||||
> For a new Update Compliance report with additional information on safeguard holds, try the [Safeguard Holds report](/windows/deployment/update/update-compliance-safeguard-holds).
|
||||
|
||||
The Feature Update Status report offers two queries to help you retrieve data related to safeguard holds. These queries show data for devices that are configured to send diagnostic data at the *Optional* level (previously *Full*). For Windows 10 devices, devices configured to send diagnostic data at *Enhanced* level are also included.
|
||||
|
||||
The first query shows the device data for all devices that are affected by safeguard holds. The second query shows data specific to devices running the target build.
|
||||
|
||||

|
||||
|
||||
Update Compliance reporting will display the Safeguard IDs for known issues affecting a device in the **DeploymentErrorCode** column. Safeguard IDs for publicly discussed known issues are also included in the Windows Release Health dashboard, where you can easily find information related to publicly available safeguards.
|
||||
Update Compliance reporting will display the safeguard hold IDs for known issues affecting a device in the **DeploymentErrorCode** column. Safeguard hold IDs for publicly discussed known issues are also included in the Windows Release Health dashboard, where you can easily find information related to publicly available safeguards.
|
||||
|
||||
### Opt out of safeguard hold
|
||||
### Opt out of safeguard holds
|
||||
|
||||
You can [opt out of safeguard protections](safeguard-opt-out.md) by using the **Disable safeguards for Feature Updates** Group Policy. This policy is available to Windows Update for Business devices running Windows 10, version 1809 or later that have installed the October 2020 security update.
|
||||
You can [opt out of safeguard holds](safeguard-opt-out.md) protecting against known issues by using the **Disable safeguards for Feature Updates** Group Policy. This policy is available to Windows Update for Business devices running Windows 10, version 1809 or later that have installed the October 2020 security update.
|
||||
|
@ -0,0 +1,49 @@
|
||||
---
|
||||
title: Update Compliance - Safeguard Holds report
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: Learn how the Safeguard Holds report provides information about safeguard holds in your population.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.pagetype: deploy
|
||||
audience: itpro
|
||||
itproauthor: jaimeo
|
||||
author: jaimeo
|
||||
ms.author: jaimeo
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Safeguard Holds
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
The Safeguard Holds report provides information about devices in your population that are affected by a [safeguard hold](/windows/deployment/update/safeguard-holds).
|
||||
|
||||
Microsoft uses diagnostic data to determine whether devices that use Windows Update are ready for a feature update in order to ensure a smooth experience. When Microsoft determines a device is not ready to update due to a known issue, a *safeguard hold* is generated to delay the device's upgrade and protect the end-user experience. Safeguard holds are released over time as diagnostic data is analyzed and fixes are addressed. Details are provided on some, but not all safeguard holds on the Windows client release information pages for any given release.
|
||||
|
||||
Update Compliance provides two views into the safeguard holds that apply to devices in your population. The report shows data for devices that are configured to send diagnostic data at the *Optional* level (previously *Full*). For Windows 10 devices, devices configured to send diagnostic data at *Enhanced* level are also included.
|
||||
|
||||
## Safeguard hold view
|
||||
|
||||
The safeguard hold view shows which safeguard holds apply to devices in your population, and how many devices are affected by each safeguard hold. You can use the **Safeguard hold ID(s)** dropdown at the top of the report to filter the chart and corresponding table to show only the selected safeguard hold IDs. Note that a device can be affected by more than one safeguard hold.
|
||||
|
||||
## Device view
|
||||
|
||||
The device view shows which devices are affected by safeguard holds. In the **Safeguard Hold IDs** column of the table, you can find a list of the safeguard holds that apply to each device. You can also use the **Safeguard hold ID(s)** dropdown at the top of the report to filter the table to show only devices affected by the selected safeguard hold IDs.
|
||||
|
||||
## Getting additional information about a safeguard hold
|
||||
|
||||
For safeguard holds protecting devices against publicly discussed known issues, you can find their 8-digit identifier on the [Windows release health](/windows/release-health/) page under **Known issues** corresponding to the relevant release.
|
||||
|
||||
Devices managed by the [Windows Update for Business deployment service](/windows/deployment/update/deployment-service-overview) that are affected by a safeguard hold for a likely issue are listed in the report with the safeguard hold ID value **00000001**.
|
||||
|
||||
## Opt out of safeguard holds
|
||||
|
||||
To opt out of safeguard holds protecting against known issues, see [Opt out of safeguard holds](/windows/deployment/update/safeguard-opt-out).
|
||||
|
||||
To opt out of safeguard holds protecting against likely issues (applicable to devices managed by the deployment service), see [Manage safeguards for a feature update deployment using the Windows Update for Business deployment service](/graph/windowsupdates-manage-safeguards).
|
Loading…
x
Reference in New Issue
Block a user