mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-19 16:57:23 +00:00
Merge branch 'master' into live
This commit is contained in:
commit
ec8ab79485
@ -22,6 +22,7 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in
|
||||
| [Get started with Update Compliance](update-compliance-get-started.md) | New |
|
||||
| [Use Update Compliance to monitor Windows Updates](update-compliance-using.md) | New |
|
||||
| [Assign devices to servicing branches for Windows 10 updates](waas-servicing-branches-windows-10-updates.md) | Added Group Policy setting that blocks user access to Windows Update. |
|
||||
| [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) | Added Express updates. |
|
||||
| [Distribute offline apps](distribute-offline-apps.md) | General updates to topic. Added links to supporting content for System Center Configuration Manager and Microsoft Intune. |
|
||||
|
||||
## January 2017
|
||||
@ -79,7 +80,7 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in
|
||||
| [Configure Windows 10 taskbar](configure-windows-10-taskbar.md) | Updated sample XML for combined Start and taskbar layout; added note to explain the difference between applying taskbar configuration by Group Policy and by provisioning package |
|
||||
| [Set up a kiosk on Windows 10 Pro, Enterprise, or Education](set-up-a-kiosk-for-windows-10-for-desktop-editions.md) | Updated instructions for exiting assigned access mode. |
|
||||
| Application development for Windows as a service | Topic moved to MSDN: [Application development for Windows as a service](https://msdn.microsoft.com/windows/uwp/get-started/application-development-for-windows-as-a-service)
|
||||
| Windows 10 servicing options | New content replaced this topic; see [Overview of Windows as a service](https://technet.microsoft.com/en-us/itpro/windows/manage/waas-overview) |
|
||||
| Windows 10 servicing options | New content replaced this topic; see [Overview of Windows as a service](waas-overview.md) |
|
||||
|
||||
## RELEASE: Windows 10, version 1607
|
||||
|
||||
|
@ -44,6 +44,35 @@ Two methods of peer-to-peer content distribution are available in Windows 10.
|
||||
>
|
||||
>In addition to client content sharing, similar functionality is available in the Windows Preinstallation Environment (Windows PE) for imaging-related content. Using this technology, clients imaging with System Center Configuration Manager task sequences can source operating system images, driver packages, boot images, packages, and programs from peers instead of distribution points. For detailed information about how Windows PE Peer Cache works and how to configure it, see [Prepare Windows PE peer cache to reduce WAN traffic in System Center Configuration Manager](https://technet.microsoft.com/en-us/library/mt613173.aspx).
|
||||
|
||||
## Express update delivery
|
||||
|
||||
Windows 10 update downloads can be large because every package contains all previously released fixes to ensure consistency and simplicity. Windows has been able to reduce the size of Windows Update downloads with a feature called Express.
|
||||
|
||||
### How Microsoft supports Express
|
||||
- **Express on WSUS Standalone**
|
||||
|
||||
Express update delivery is available on [all support versions of WSUS](https://technet.microsoft.com/library/cc708456(v=ws.10).aspx).
|
||||
- **Express on devices directly connected to Windows Update**
|
||||
- **Enterprise devices managed using [Windows Update for Business](waas-manage-updates-wufb.md)** also get the benefit of Express update delivery support without any change in configuration.
|
||||
|
||||
### How Express download works
|
||||
|
||||
For OS updates that support Express, there are two versions of the file payload stored on the service:
|
||||
1. **Full-file version** - essentially replacing the local versions of the update binaries.
|
||||
2. **Express version** - containing the deltas needed to patch the existing binaries on the device.
|
||||
|
||||
Both the full-file version and the Express version are referenced in the udpate's metadata, which has been downloaded to the client as part of the scan phase.
|
||||
|
||||
**Express download works as follows:**
|
||||
|
||||
The Windows Update client will try to download Express first, and under certain situations fall back to full-file if needed (for example, if going through a proxy that doesn't support byte range requests).
|
||||
|
||||
1. When the Windows Update client initiates an Express download, **Windows Update first downloads a stub**, which is part of the Express package.
|
||||
2. **The Windows Update client passes this stub to the Windows installer**, which uses the stub to do a local inventory, comparing the deltas of the file on the device with what is needed to get to the latest version of the file being offered.
|
||||
3. **The Windows installer then requests the Windows Update client to download the ranges**, which have been determined to be required.
|
||||
4. **The client downloads these ranges and passes them to the Windows Installer**, which applies the ranges and then determines if additional ranges are needed. This repeats until the Windows installer tells the Windows Update client that all necessary ranges have been downloaded.
|
||||
|
||||
At this point, the download is complete and the update is ready to be installed.
|
||||
|
||||
## Steps to manage updates for Windows 10
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user