mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 10:53:43 +00:00
Merge branch 'rs4' of https://cpubwin.visualstudio.com/_git/it-client into DOupdates
This commit is contained in:
@ -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**
|
||||
|
@ -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
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: jaimeo
|
||||
ms.author: jaimeo
|
||||
ms.date: 03/20/2018
|
||||
ms.date: 04/03/2018
|
||||
---
|
||||
|
||||
# Frequently asked questions and troubleshooting Windows Analytics
|
||||
@ -33,6 +33,8 @@ If you've followed the steps in the [Enrolling devices in Windows Analytics](win
|
||||
|
||||
[Disable Upgrade Readiness](#disable-upgrade-readiness)
|
||||
|
||||
[Exporting large data sets](#exporting-large-data-sets)
|
||||
|
||||
|
||||
### Devices not showing up
|
||||
|
||||
@ -55,6 +57,11 @@ If you want to check a large number of devices, you should run the latest script
|
||||
|
||||
If you think the issue might be related to a network proxy, check "Enable data sharing" section of the [Enrolling devices in Windows Analytics](windows-analytics-get-started.md) topic. Also see [Understanding connectivity scenarios and the deployment script](https://blogs.technet.microsoft.com/upgradeanalytics/2017/03/10/understanding-connectivity-scenarios-and-the-deployment-script/) on the Windows Analytics blog.
|
||||
|
||||
If you have deployed images that have not been generalized, then many of them might have the same ID and so analytics will see them as one device. If you suspect this is the issue, then you can reset the IDs on the non-generalized devices by performing these steps:
|
||||
1. Net stop diagtrack
|
||||
2. Reg delete hklm\software\microsoft\sqmclient /v MachineId /f
|
||||
3. Net start diagtrack
|
||||
|
||||
|
||||
### Device Health crash data not appearing
|
||||
|
||||
@ -174,6 +181,24 @@ If you want to stop using Upgrade Readiness and stop sending diagnostic data dat
|
||||
3. If you enabled **Internet Explorer Site Discovery**, you can disable Internet Explorer data collection by setting the *IEDataOptIn* registry key to value "0". The IEDataOptIn key can be found under: *HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection*.
|
||||
4. **Optional step:** You can also remove the “CommercialId” key from: "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection".
|
||||
|
||||
### Exporting large data sets
|
||||
|
||||
Azure Log Analytics is optimized for advanced analytics of large data sets and can efficiently generate summaries and analytics for them. The query language is not optimized (or intended) for returning large raw data sets and has built-in limits to protect against overuse. There are times when it might be necessary to get more data than this, but that should be done sparingly since this is not the intended way to use Azure Log Analytics. The following code snippet shows how to retrieve data from UAApp one “page” at a time:
|
||||
|
||||
```
|
||||
let snapshot = toscalar(UAApp | summarize max(TimeGenerated));
|
||||
let pageSize = 100000;
|
||||
let pageNumber = 0;
|
||||
|
||||
UAApp
|
||||
| where TimeGenerated == snapshot and IsRollup==true and RollupLevel=="Granular" and Importance == "Low install count"
|
||||
| order by AppName, AppVendor, AppVersion desc
|
||||
| serialize
|
||||
| where row_number(0) >= (pageSize * pageNumber)
|
||||
| take pageSize
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Other common questions
|
||||
|
||||
|
@ -53,7 +53,8 @@ To enable data sharing, configure your proxy sever to whitelist the following en
|
||||
| `https://oca.telemetry.microsoft.com` | Online Crash Analysis; required for Device Health and Update Compliance AV reports. Not used by Upgrade Readiness. |
|
||||
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>If you have SSL Inspection enabled on your proxy server, you might need to add the above URLs to your SSL inspection exclusion list to allow data to reach Microsoft endpoints.
|
||||
|
||||
### Configuring endpoint access with proxy servers
|
||||
If your organization uses proxy server authentication for outbound traffic, use one or more of the following approaches to ensure that the diagnostic data is not blocked by proxy authentication:
|
||||
|
37
windows/deployment/update/windows-update-sources.md
Normal file
37
windows/deployment/update/windows-update-sources.md
Normal file
@ -0,0 +1,37 @@
|
||||
---
|
||||
title: Determine the source of Windows updates
|
||||
description: Determine the source that Windows Update service is currently using.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl:
|
||||
ms.sitesec: library
|
||||
author: kaushika-msft
|
||||
ms.localizationpriority: high
|
||||
ms.author: jaimeo
|
||||
ms.date: 04/05/2018
|
||||
---
|
||||
|
||||
# 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:
|
||||
|
||||
1. Start Windows PowerShell as an administrator
|
||||
2. Run `\$MUSM = New-Object -ComObject “Microsoft.Update.ServiceManager”`.
|
||||
3. Run `\$MUSM.Services`. Check the resulting output for the **Name** and **OffersWindowsUPdates** parameters, which you can intepret according to this table:
|
||||
|
||||
| Output | Interpretation |
|
||||
|-----------------------------------------------------|-----------------------------------|
|
||||
| - Name: **Microsoft Update**<br>-OffersWindowsUpdates: **True** | - The update source is Microsoft Update, which means that updates for other Microsoft products besides the operating system could also be delivered.<br>- Indicates that the client is configured to receive updates for all Microsoft Products (Office, etc.)|
|
||||
|- Name: **DCat Flighting Prod** <br>- OffersWindowsUpdates: **False**|- The update source is the Windows Insider Program.<br>- Indicates that the client will not receive or is not configured to receive these updates. |
|
||||
| - Name: **Windows Store (DCat Prod)**<br>- OffersWindowsUpdates: **False** |-The update source is Insider Updates for Store Apps.<br>- Indicates that the client will not receive or is not configured to receive these updates.|
|
||||
|- Name: **Windows Server Update Service**<br>- OffersWindowsUpdates: **True** |- The source is a Windows Server Updates Services server.<br>- The client is configured to receive updates from WSUS.|
|
||||
|- Name: **Windows Update**<br>- OffersWindowsUpdates: **True** |- The source is Windows Update.<br>- The client is configured to receive updates from Windows Update Online.|
|
||||
|
||||
|
||||
|
||||
See also:
|
||||
|
||||
[Understanding the Windowsupdate.log file for advanced users](https://support.microsoft.com/help/4035760)
|
||||
|
||||
[You can't install updates on a Windows-based computer](https://support.microsoft.com/help/2509997/you-can-t-install-updates-on-a-windows-based-computer)
|
||||
|
||||
[How to read the Windowsupdate.log file on Windows 7 and earlier OS versions](https://support.microsoft.com/help/902093/how-to-read-the-windowsupdate-log-file)
|
Reference in New Issue
Block a user