mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
Merge branch 'master' of https://cpubwin.visualstudio.com/_git/it-client into moveprivacy
This commit is contained in:
jaimeo
@ -230,7 +230,7 @@
|
||||
### [Deploy Windows 10 updates using System Center Configuration Manager](update/waas-manage-updates-configuration-manager.md)
|
||||
### [Manage device restarts after updates](update/waas-restart.md)
|
||||
### [Manage additional Windows Update settings](update/waas-wu-settings.md)
|
||||
### [Determining the source of Windows updates](update/windows-update-sources.md)
|
||||
### [Determine the source of Windows updates](update/windows-update-sources.md)
|
||||
### [Windows Insider Program for Business](update/waas-windows-insider-for-business.md)
|
||||
#### [Introduction to the Windows Insider Program for Business](update/WIP4Biz-intro.md)
|
||||
#### [Windows Insider Program for Business Frequently Asked Questions](update/waas-windows-insider-for-business-faq.md)
|
||||
|
||||
@ -1,16 +1,16 @@
|
||||
---
|
||||
title: Update Windows 10 in the enterprise (Windows 10)
|
||||
title: Update Windows 10 in enterprise deployments (Windows 10)
|
||||
description: Windows as a service provides an all-new way to think about building, deploying, and servicing Windows 10.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: DaniHalfin
|
||||
author: Jaimeo
|
||||
ms.localizationpriority: high
|
||||
ms.author: daniha
|
||||
ms.date: 11/17/2017
|
||||
ms.author: jaimeo
|
||||
ms.date: 04/06/2018
|
||||
---
|
||||
|
||||
# Update Windows 10 in the enterprise
|
||||
# Update Windows 10 in enterprise deployments
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
@ -13,6 +13,10 @@ ms.date: 03/27/2018
|
||||
# Delivery Optimization in Update Compliance
|
||||
The Update Compliance solution of Windows Analytics provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer distribution over the past 28 days.
|
||||
|
||||
>[!Note]
|
||||
>Delivery Optimization Status is currently in development. See the [Known Issues](#known-issues) section for issues we are aware of and potential workarounds.
|
||||
|
||||
|
||||
## Delivery Optimization Status
|
||||
|
||||
The Delivery Optimization Status section includes three blades:
|
||||
@ -40,3 +44,8 @@ The download sources that could be included are:
|
||||
- Group Bytes: Bytes downloaded from Group Peers which are other devices that belong to the same Group (available when the “Group” download mode is used)
|
||||
- HTTP Bytes: Non-peer bytes. The HTTP download source can be Microsoft Servers, Windows Update Servers, a WSUS server or an SCCM Distribution Point for Express Updates.
|
||||
|
||||
## Known Issues
|
||||
Delivery Optimization is currently in development. The following issues are known:
|
||||
|
||||
- DO Download Mode is not accurately portrayed in the Device Configuration blade. There is no workaround at this time.
|
||||
|
||||
|
||||
@ -90,7 +90,7 @@ For Windows 10, version 1607, organizations already managing their systems with
|
||||
|
||||
|
||||
|
||||
|
||||
For more information, see [Integration with Windows Update for Business in Windows 10](https://docs.microsoft.com/en-us/sccm/sum/deploy-use/integrate-windows-update-for-business-windows-10).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -13,7 +13,7 @@ ms.date: 04/05/2018
|
||||
|
||||
# Frequently asked questions and troubleshooting Windows Analytics
|
||||
|
||||
This topic compiles the most common issues encountered with configuring and using Windows Analytics, as well as general questions.
|
||||
This topic compiles the most common issues encountered with configuring and using Windows Analytics, as well as general questions. This FAQ, along with the [Windows Analytics Technical Community](https://techcommunity.microsoft.com/t5/Windows-Analytics/ct-p/WindowsAnalytics), are recommended resources to consult before contacting Microsoft support.
|
||||
|
||||
## Troubleshooting common problems
|
||||
|
||||
|
||||
@ -127,7 +127,6 @@ Use a software distribution system such as System Center Configuration Manager t
|
||||
|
||||
### Distributing policies at scale
|
||||
There are a number of policies that can be centrally managed to control Windows Analytics device configuration. All of these policies have *preference* registry key equivalents that can be set by using the deployment script. Policy settings override preference settings if both are set.
|
||||
|
||||
>[!NOTE]
|
||||
>You can only set the diagnostic data level to Enhanced by using policy. For example, this is necessary for using Device Health.
|
||||
|
||||
@ -155,4 +154,10 @@ For more information about Internet Explorer Security Zones, see [About URL Secu
|
||||
|
||||
### Distribution at scale without using the deployment script
|
||||
|
||||
We recommend using the deployment script to configure devices. However if this is not an option, you can still manage settings by policy as described in the previous section. However, if you don't run the deployment script, you might have to wait a long time (possibly weeks) before devices send the initial full inventory scan.
|
||||
We recommend using the deployment script to configure devices. However if this is not an option, you can still manage settings by policy as described in the previous section. However, if you don't run the deployment script, you won't benefit from its error checking, and you might have to wait a long time (possibly weeks) before devices send the initial full inventory scan.
|
||||
|
||||
Note that it is possible to intiate a full inventory scan on a device by calling these commands:
|
||||
- CompatTelRunner.exe -m:generaltel.dll -f:DoCensusRun
|
||||
- CompatTelRunner.exe -m:appraiser.dll -f:DoScheduledTelemetryRun ent
|
||||
|
||||
For details on how to run these and how to check results, see the deployment script.
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Determining the source of Windows updates
|
||||
title: Determine the source of Windows updates
|
||||
description: Determine the source that Windows Update service is currently using.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl:
|
||||
@ -10,7 +10,7 @@ ms.author: jaimeo
|
||||
ms.date: 04/05/2018
|
||||
---
|
||||
|
||||
# Determining the source of Windows updates
|
||||
# Determine the source of Windows updates
|
||||
|
||||
Windows 10 devices can receive updates from a variety of sources, including Windows Update online, a Windows Server Update Services server, and others. To determine the source of Windows Updates currently being used on a device, follow these steps:
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
ms.date: 03/30/2018
|
||||
ms.date: 04/11/2018
|
||||
ms.localizationpriority: high
|
||||
---
|
||||
|
||||
@ -103,7 +103,7 @@ SetupDiag.exe /Output:C:\SetupDiag\Dumpdebug.log /Mode:Offline /LogsPath:D:\Dump
|
||||
|
||||
## Known issues
|
||||
|
||||
1. Some rules can take a long time to process if the log files involved as large.
|
||||
1. Some rules can take a long time to process if the log files involved are large.
|
||||
2. SetupDiag only outputs data in a text format. If another format is desired, please provide this [feedback](#feedback).
|
||||
3. If the failing computer is opted into the Insider program and getting regular pre-release updates, or an update is already pending on the computer when SetupDiag is run, it can encounter problems trying to open these log files. This will likely cause a failure to determine a root cause. In this case, try gathering the log files and running SetupDiag in offline mode.
|
||||
|
||||
|
||||
@ -31,7 +31,7 @@ See [Windows 10 Specifications](http://www.microsoft.com/en-US/windows/windows-1
|
||||
Keeping Windows 10 up to date involves deploying a feature update, and Upgrade Readiness tools help you prepare and plan for these Windows updates.
|
||||
The latest cumulative updates must be installed on Windows 10 computers to make sure that the required compatibility updates are installed. You can find the latest cumulative update on the [Microsoft Update Catalog](https://catalog.update.microsoft.com).
|
||||
|
||||
Windows 10 LTSB is not supported by Upgrade Readiness. The Long-Term Servicing Channel of Windows 10 is not intended for general deployment, and does not receive feature updates, therefore it is not compatible with Upgrade Readiness. See [Windows as a service overview](../update/waas-overview.md#long-term-servicing-channel) to understand more about LTSB.
|
||||
While Upgrade Readiness can be used to assist with updating devices from Windows 10 Long-Term Servicing Channel (LTSC) to Windows 10 Semi-Annual Channel, Upgrade Readiness does not support updates to Windows 10 LTSC. The Long-Term Servicing Channel of Windows 10 is not intended for general deployment, and does not receive feature updates, therefore it is not a supported target with Upgrade Readiness. See [Windows as a service overview](../update/waas-overview.md#long-term-servicing-channel) to understand more about LTSC.
|
||||
|
||||
## Operations Management Suite
|
||||
|
||||
|
||||
Reference in New Issue
Block a user