From d046dee742de0e60cc3a3c372b08ae03bda54467 Mon Sep 17 00:00:00 2001 From: Dani Halfin Date: Mon, 23 Jan 2017 18:38:08 -0800 Subject: [PATCH 1/6] manage\waas-restart - Add section Add registry key summary --- windows/manage/waas-restart.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/windows/manage/waas-restart.md b/windows/manage/waas-restart.md index e8a8394d2d..d825aab900 100644 --- a/windows/manage/waas-restart.md +++ b/windows/manage/waas-restart.md @@ -65,11 +65,28 @@ In the Group Policy editor, you will see a number of policy settings that pertai | Reschedule Automatic Updates scheduled installations | ![no](images/crossmark.png) | | >[!NOTE] ->If you set conflicting restart policies, the actual restart behavior may not be what you expected. +>If you set conflicting restart policies, the actual restart behavior may not be what you expected. +## Summary: Registry keys used to manage restarts after updates +Below are quick-reference tables of the supported registry values, that correspond to group policy settings, used to manage restarts after updates in Windows 10. +**HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate** +| Registry key | Key type | Value | +| --- | --- | --- | +| ActiveHoursEnd | REG_DWORD | 0-23: set active hours to end at a specific hour
starts with 12 AM (0) and ends with 11 PM (23) | +| ActiveHoursStart | REG_DWORD | 0-23: set active hours to start at a specific hour
starts with 12 AM (0) and ends with 11 PM (23) | +| SetActiveHours | REG_DWORD | 0: disable automatic restart after updates outside of active hours
1: enable automatic restart after updates outside of active hours | +**HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU** + +| Registry key | Key type | Value | +| --- | --- | --- | +| AlwaysAutoRebootAtScheduledTime | REG_DWORD | TBP | +| AlwaysAutoRebootAtScheduledTimeMinutes | REG_DWORD | TBP | +| AUOptions | REG_DWORD | 2: notify for download and automatically install updates
3: automatically download and notify for instllation of updates
4: Automatically download and schedule installation of updates
5: allow the local admin to configure these settings | +| NoAutoRebootWithLoggedOnUsers | REG_DWORD | 0: disable do not reboot if users are logged on
1: do not reboot after an update installation if a user is logged on
**Note:** If disabled : Automatic Updates will notify the user that the computer will automatically restarts in 5 minutes to complete the installation | +| ScheduledInstallTime | REG_DWORD | 0-23: schedule update installation time to a specific hour
starts with 12 AM (0) and ends with 11 PM (23) | ## Related topics From caa14c62ef3151d7d0905979d7df8171c97780dd Mon Sep 17 00:00:00 2001 From: Dani Halfin Date: Wed, 25 Jan 2017 18:35:39 -0800 Subject: [PATCH 2/6] Adding content as listed in desc - Registry details - Active hours reorg and registry section --- windows/manage/waas-restart.md | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/windows/manage/waas-restart.md b/windows/manage/waas-restart.md index d825aab900..07d0c8ed00 100644 --- a/windows/manage/waas-restart.md +++ b/windows/manage/waas-restart.md @@ -34,17 +34,38 @@ When **Configure Automatic Updates** is enabled, you can enable one of the follo You can configure active hours for devices without setting the **Configure Automatic Updates** policy. *Active hours* identify the period of time when you expect the device to be in use. Automatic restarts after an update will occur outside of the active hours. -By default, active hours are from 8 AM to 5 PM on PCs and from 5 AM to 11 PM on phones. Users can change the active hours manually. Additionally, administrators can use Group Policy or MDM to set active hours for managed devices. +By default, active hours are from 8 AM to 5 PM on PCs and from 5 AM to 11 PM on phones. Users can change the active hours manually. + +Additionally, administrators can use multiple ways to set active hours for managed devices: + +- You can use Group Policy, as described in the procedure that follows. +- You can use MDM, as described in [Configuring active hours with MDM](#configuring-active-hours-with-mdm). +- While not recommended, you can also configure active hours, as descrbied in [Configuring active hours through Registry](#configuring-active-hours-through-registry). + +### Configuring active hours with Group Policy To configure active hours using Group Policy, go to **Computer Configuration\Administrative Templates\Windows Components\Windows Update** and open the **Turn off auto-restart for updates during active hours** policy setting. When the policy is enabled, you can set the start and end times for active hours. ![Use Group Policy to configure active hours](images/waas-active-hours-policy.png) +### Configuring active hours with MDM + MDM uses the [Update/ActiveHoursStart and Update/ActiveHoursEnd](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_ActiveHoursEnd) settings in the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) to configure active hours. -To configure active hours manually on a single device, go to **Settings** > **Update & security** > **Windows Update** and select **Change active hours**. +### Configuring active hours through Registry -![Change active hours](images/waas-active-hours.png) +This method is not recommended, and should be used when neither Group Policy or MDM are available. +Any settings configured through Registry may conflict with any existing configuration that uses any of the methods mentioned above. + +You should set a combination of the following registry values, in order to configure active hours. +Under **HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate** use **SetActiveHours** to enable or disable active hours and **ActiveHoursStart**,**ActiveHoursEnd** to specify the range of active hours. + +For a detailed description of these regsitry keys, see [Summary: Registry keys used to manage restarts after updates](#summary-registry-keys-used-to-manage-restarts-after-updates). + +>[!NOTE] +>To configure active hours manually on a single device, go to **Settings** > **Update & security** > **Windows Update** and select **Change active hours**. +> +>![Change active hours](images/waas-active-hours.png) ## Limit restart delays @@ -68,7 +89,7 @@ In the Group Policy editor, you will see a number of policy settings that pertai >If you set conflicting restart policies, the actual restart behavior may not be what you expected. ## Summary: Registry keys used to manage restarts after updates -Below are quick-reference tables of the supported registry values, that correspond to group policy settings, used to manage restarts after updates in Windows 10. +The following tables list registry values that correspond to the Group Policy settings for controlling restarts after updates in Windows 10. **HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate** @@ -82,8 +103,8 @@ Below are quick-reference tables of the supported registry values, that correspo | Registry key | Key type | Value | | --- | --- | --- | -| AlwaysAutoRebootAtScheduledTime | REG_DWORD | TBP | -| AlwaysAutoRebootAtScheduledTimeMinutes | REG_DWORD | TBP | +| AlwaysAutoRebootAtScheduledTime | REG_DWORD | 0: disable automatic reboot after update installation at scheduled time
1: enable automatic reboot after update installation at ascheduled time | +| AlwaysAutoRebootAtScheduledTimeMinutes | REG_DWORD | 15-180: set automatic reboot to occur after given minutes | | AUOptions | REG_DWORD | 2: notify for download and automatically install updates
3: automatically download and notify for instllation of updates
4: Automatically download and schedule installation of updates
5: allow the local admin to configure these settings | | NoAutoRebootWithLoggedOnUsers | REG_DWORD | 0: disable do not reboot if users are logged on
1: do not reboot after an update installation if a user is logged on
**Note:** If disabled : Automatic Updates will notify the user that the computer will automatically restarts in 5 minutes to complete the installation | | ScheduledInstallTime | REG_DWORD | 0-23: schedule update installation time to a specific hour
starts with 12 AM (0) and ends with 11 PM (23) | From e9f8b71e91b9a13e52f17c5cbe0e9027f2f236f2 Mon Sep 17 00:00:00 2001 From: Dani Halfin Date: Thu, 26 Jan 2017 11:50:28 -0800 Subject: [PATCH 3/6] Adding content - waas-restart - Finished adding registry content in context. - Re-arranged some of the existing content, due to added content. --- windows/manage/waas-restart.md | 33 ++++++++++++++++++++++++--------- 1 file changed, 24 insertions(+), 9 deletions(-) diff --git a/windows/manage/waas-restart.md b/windows/manage/waas-restart.md index 07d0c8ed00..5ad57725e9 100644 --- a/windows/manage/waas-restart.md +++ b/windows/manage/waas-restart.md @@ -18,25 +18,38 @@ localizationpriority: high > **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq) -You can use Group Policy settings or mobile device management (MDM) to configure when devices will restart after a Windows 10 update is installed. You can schedule update installation and set policies for restart, configure active hours for when restarts will not occur, or you can do both. +You can use Group Policy settings, mobile device management (MDM) or Registry (not recommended) to configure when devices will restart after a Windows 10 update is installed. You can schedule update installation and set policies for restart, configure active hours for when restarts will not occur, or you can do both. ## Schedule update installation -When you set the **Configure Automatic Updates** policy to **Auto download and schedule the install**, you also configure the day and time for installation or you specify that installation will occur during the automatic maintenance time (configured using **Computer Configuration\Administrative Templates\Windows Components\Maintenance Scheduler**). +In Group Policy, within **Configure Automatic Updates**, you can configure a forced restart after a specified instllation time. -When **Configure Automatic Updates** is enabled, you can enable one of the following additional policies to manage device restart: +To set the time, you need to go to **Configure Automatic Updates**, select option **4 - Auto download and schedule the instal**, and then enter a time in the **Scheduled install time** dropdown. Alternatively, you can specify that installtion will occur during the automatic maintenance time (configured using **Computer Configuration\Administrative Templates\Windows Components\Maintenance Scheduler**). + +**Always automatically restart at the scheduled time** forces a restart after the specified installation time and lets you configure a timer to warn a signed-in user that a restart is going to occur. + +While not recommended, the same result can be achieved through Registry. Under **HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU**, set **AuOptions** to **4**, set the install time with **ScheduledInstallTime**, enable **AlwaysAutoRebootAtScheduledTime** and specify the delay in minutes through **AlwaysAutoRebootAtScheduledTimeMinutes**. Similar to Group Policy, **AlwaysAutoRebootAtScheduledTimeMinutes** sets the timer to warn a signed-in user that a restart is going to occur. + +For a detailed description of these regsitry keys, see [Registry keys used to manage restart](#registry-keys-used-to-manage-restart). + +## Delay automatic reboot + +When **Configure Automatic Updates** is enabled in Group Policy, you can enable one of the following additional policies to delay an automatic reboot after update installtion: - **Turn off auto-restart for updates during active hours** prevents automatic restart during active hours. -- **Always automatically restart at the scheduled time** forces a restart after the specified installation time and lets you configure a timer to warn a signed-in user that a restart is going to occur. To set the time, you need to go **Configure Automatic Updates**, select option **4 - Auto download and schedule the install**, and then enter a time in the **Scheduled install time** dropdown. - **No auto-restart with logged on users for scheduled automatic updates installations** prevents automatic restart when a user is signed in. If a user schedules the restart in the update notification, the device will restart at the time the user specifies even if a user is signed in at the time. This policy only applies when **Configure Automatic Updates** is set to option **4-Auto download and schedule the install**. +You can also use Registry, to prevent automatic restarts when a user is signed in. Under **HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU**, set **AuOptions** to **4** and enable **NoAutoRebootWithLoggedOnUsers**. As with Group Policy, if a user schedules the restart in the update notification, it will override this setting. + +For a detailed description of these regsitry keys, see [Registry keys used to manage restart](#registry-keys-used-to-manage-restart). + ## Configure active hours -You can configure active hours for devices without setting the **Configure Automatic Updates** policy. *Active hours* identify the period of time when you expect the device to be in use. Automatic restarts after an update will occur outside of the active hours. +*Active hours* identify the period of time when you expect the device to be in use. Automatic restarts after an update will occur outside of the active hours. By default, active hours are from 8 AM to 5 PM on PCs and from 5 AM to 11 PM on phones. Users can change the active hours manually. -Additionally, administrators can use multiple ways to set active hours for managed devices: +Administrators can use multiple ways to set active hours for managed devices: - You can use Group Policy, as described in the procedure that follows. - You can use MDM, as described in [Configuring active hours with MDM](#configuring-active-hours-with-mdm). @@ -54,13 +67,13 @@ MDM uses the [Update/ActiveHoursStart and Update/ActiveHoursEnd](https://msdn.mi ### Configuring active hours through Registry -This method is not recommended, and should be used when neither Group Policy or MDM are available. +This method is not recommended, and should only be used when neither Group Policy or MDM are available. Any settings configured through Registry may conflict with any existing configuration that uses any of the methods mentioned above. You should set a combination of the following registry values, in order to configure active hours. Under **HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate** use **SetActiveHours** to enable or disable active hours and **ActiveHoursStart**,**ActiveHoursEnd** to specify the range of active hours. -For a detailed description of these regsitry keys, see [Summary: Registry keys used to manage restarts after updates](#summary-registry-keys-used-to-manage-restarts-after-updates). +For a detailed description of these regsitry keys, see [Registry keys used to manage restart](#registry-keys-used-to-manage-restart). >[!NOTE] >To configure active hours manually on a single device, go to **Settings** > **Update & security** > **Windows Update** and select **Change active hours**. @@ -86,9 +99,11 @@ In the Group Policy editor, you will see a number of policy settings that pertai | Reschedule Automatic Updates scheduled installations | ![no](images/crossmark.png) | | >[!NOTE] +>You can only choose one path for restart behavior. +> >If you set conflicting restart policies, the actual restart behavior may not be what you expected. -## Summary: Registry keys used to manage restarts after updates +## Registry keys used to manage restart The following tables list registry values that correspond to the Group Policy settings for controlling restarts after updates in Windows 10. **HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate** From e511c0457411ba485d0601a8673c477109b3458d Mon Sep 17 00:00:00 2001 From: JanKeller1 Date: Thu, 26 Jan 2017 18:48:32 -0800 Subject: [PATCH 4/6] Added Failure event to parent topic for 4774 --- windows/keep-secure/audit-credential-validation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/keep-secure/audit-credential-validation.md b/windows/keep-secure/audit-credential-validation.md index 5e54e23875..a6e23ecd47 100644 --- a/windows/keep-secure/audit-credential-validation.md +++ b/windows/keep-secure/audit-credential-validation.md @@ -42,7 +42,7 @@ The main reason to enable this auditing subcategory is to handle local accounts **Events List:** -- [4774](event-4774.md)(S): An account was mapped for logon. +- [4774](event-4774.md)(S, F): An account was mapped for logon. - [4775](event-4775.md)(F): An account could not be mapped for logon. From 055ddd3ec00736edf95be68d1b3b53b366073404 Mon Sep 17 00:00:00 2001 From: Dani Halfin Date: Thu, 26 Jan 2017 20:37:16 -0800 Subject: [PATCH 5/6] Add content - waas-restart - Final changes after PM review - Added a note and instructions summary at the bottom of the registry part --- windows/manage/waas-restart.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/windows/manage/waas-restart.md b/windows/manage/waas-restart.md index 5ad57725e9..33371c4c5f 100644 --- a/windows/manage/waas-restart.md +++ b/windows/manage/waas-restart.md @@ -120,10 +120,16 @@ The following tables list registry values that correspond to the Group Policy se | --- | --- | --- | | AlwaysAutoRebootAtScheduledTime | REG_DWORD | 0: disable automatic reboot after update installation at scheduled time
1: enable automatic reboot after update installation at ascheduled time | | AlwaysAutoRebootAtScheduledTimeMinutes | REG_DWORD | 15-180: set automatic reboot to occur after given minutes | -| AUOptions | REG_DWORD | 2: notify for download and automatically install updates
3: automatically download and notify for instllation of updates
4: Automatically download and schedule installation of updates
5: allow the local admin to configure these settings | +| AUOptions | REG_DWORD | 2: notify for download and automatically install updates
3: automatically download and notify for instllation of updates
4: Automatically download and schedule installation of updates
5: allow the local admin to configure these settings
**Note:** To configure restart behavior, set this value to **4** | | NoAutoRebootWithLoggedOnUsers | REG_DWORD | 0: disable do not reboot if users are logged on
1: do not reboot after an update installation if a user is logged on
**Note:** If disabled : Automatic Updates will notify the user that the computer will automatically restarts in 5 minutes to complete the installation | | ScheduledInstallTime | REG_DWORD | 0-23: schedule update installation time to a specific hour
starts with 12 AM (0) and ends with 11 PM (23) | +There are 3 different registry combination for controlling restart: + +- To set active hours, **SetActiveHours** should be **1**, while **ActiveHoursStart** and **ActiveHoursEnd** should define the time range. +- To schedule a specific instllation and reboot time, **AUOptions** should be **4**, **ScheduledInstallTime** should specify the installation time, **AlwaysAutoRebootAtScheduledTime** set to **1** and **AlwaysAutoRebootAtScheduledTimeMinutes** should specify number of minutes to wait before rebooting. +- To delay rebooting if a user is logged on, **AUOptions** should be **4**, while **NoAutoRebootWithLoggedOnUsers** is set to **1**. + ## Related topics - [Update Windows 10 in the enterprise](waas-update-windows-10.md) From c6eac50aaa4690ba7758858cd78b280e1cccaa33 Mon Sep 17 00:00:00 2001 From: jdeckerMS Date: Fri, 27 Jan 2017 08:29:43 -0800 Subject: [PATCH 6/6] add link to user's guide --- devices/surface-hub/index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/devices/surface-hub/index.md b/devices/surface-hub/index.md index ce7c4f3c37..17f46092e4 100644 --- a/devices/surface-hub/index.md +++ b/devices/surface-hub/index.md @@ -13,7 +13,9 @@ localizationpriority: medium # Microsoft Surface Hub -Documents related to the Microsoft Surface Hub. +Documents related to deploying and managing the Microsoft Surface Hub in your organization. + +>[Looking for the user's guide for Surface Hub?](https://www.microsoft.com/surface/support/surface-hub) ## In this section