mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-20 21:03:42 +00:00
Merge branch 'main' of https://github.com/MicrosoftDocs/windows-docs-pr into recall-optin-9067947
This commit is contained in:
@ -1,18 +0,0 @@
|
||||
param(
|
||||
[string]$buildCorePowershellUrl = "https://opbuildstoragesandbox2.blob.core.windows.net/opps1container/.openpublishing.buildcore.ps1",
|
||||
[string]$parameters
|
||||
)
|
||||
# Main
|
||||
$errorActionPreference = 'Stop'
|
||||
|
||||
# Step-1 Download buildcore script to local
|
||||
echo "download build core script to local with source url: $buildCorePowershellUrl"
|
||||
$repositoryRoot = Split-Path -Parent $MyInvocation.MyCommand.Definition
|
||||
$buildCorePowershellDestination = "$repositoryRoot\.openpublishing.buildcore.ps1"
|
||||
Invoke-WebRequest $buildCorePowershellUrl -OutFile $buildCorePowershellDestination
|
||||
|
||||
# Step-2: Run build core
|
||||
echo "run build core script with parameters: $parameters"
|
||||
$arguments = "-parameters:'$parameters'"
|
||||
Invoke-Expression "$buildCorePowershellDestination $arguments"
|
||||
exit $LASTEXITCODE
|
@ -73,3 +73,5 @@ In the following example:
|
||||
## Minimize user disruption due to updates
|
||||
|
||||
Windows Autopatch understands the importance of not disrupting end users but also updating the devices quickly. To achieve this goal, updates are automatically downloaded and installed at an optimal time determined by the device. By default, [Active hours](/windows/client-management/mdm/policy-csp-update#activehoursstart) are configured dynamically based on device usage patterns. Device restarts occur outside of active hours until the deadline is reached.
|
||||
|
||||
Windows Autopatch doesn't modify the existing Windows Update notifications. If you wish to modify the end-user update notification experience, see [Use CSPs and MDMs to configure Windows Update for Business](/windows/deployment/update/waas-wufb-csp-mdm).
|
||||
|
@ -2,7 +2,7 @@
|
||||
title: Configure Windows Hello for Business
|
||||
description: Learn about the configuration options for Windows Hello for Business and how to implement them in your organization.
|
||||
ms.topic: how-to
|
||||
ms.date: 04/23/2024
|
||||
ms.date: 11/05/2024
|
||||
---
|
||||
|
||||
# Configure Windows Hello for Business
|
||||
@ -109,7 +109,7 @@ Configuration type| Details |
|
||||
| CSP (user)|**Key path**: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Policies\PassportForWork\<Tenant-ID>\UserSid\Policies`<br>**Key name**: `UsePassportForWork`<br>**Type**: `REG_DWORD`<br>**Value**:<br> `1` to enable<br> `0` to disable |
|
||||
| CSP (device)|**Key path**: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Policies\PassportForWork\<Tenant-ID>\Device\Policies`<br>**Key name**: `UsePassportForWork`<br>**Type**: `REG_DWORD`<br>**Value**:<br> `1` to enable<br> `0` to disable |
|
||||
| GPO (user)|**Key path**: `HKEY_USERS\<UserSID>\SOFTWARE\Policies\Microsoft\PassportForWork`<br>**Key name**: `Enabled`<br>**Type**: `REG_DWORD`<br>**Value**:<br> `1` to enable<br> `0` to disable |
|
||||
| GPO (user)|**Key path**: `KEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork`<br>**Key name**: `Enabled`<br>**Type**: `REG_DWORD`<br>**Value**:<br> `1` to enable<br> `0` to disable |
|
||||
| GPO (device)|**Key path**: `KEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork`<br>**Key name**: `Enabled`<br>**Type**: `REG_DWORD`<br>**Value**:<br> `1` to enable<br> `0` to disable |
|
||||
|
||||
> [!NOTE]
|
||||
> If there's a conflicting device policy and user policy, the user policy takes precedence. It's not recommended to create Local GPO or registry settings that could conflict with an MDM policy. This conflict could lead to unexpected results.
|
||||
|
Reference in New Issue
Block a user