deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Update how-windows-update-works.md: amend typo

Browse Source 
Simple typo correction, along with a few MarkDown
codestyle corrections for MD blockquote (`>`) indenting.

- typo correction: initates -> initiates
- codestyle corrections:
  3 MarkDown blockquote indentations amended

Thanks to Jessie Gouw (jessiegouw) for reporting the typo.

Closes #4866
This commit is contained in:
illfated 2019-09-05 20:57:16 +02:00
parent 4d5f85e71d
commit e743b8bace
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
windows/deployment/update/how-windows-update-works.md
View File

@ -16,7 +16,7 @@ ms.topic: article
# How does Windows Update work?
>Applies to: Windows 10
> Applies to: Windows 10
The Windows Update workflow has four core areas of functionality:
@ -35,7 +35,7 @@ The Windows Update workflow has four core areas of functionality:
### Install
1. Orchestrator initates the installation.
1. Orchestrator initiates the installation.
2. The arbiter calls the installer to install the package.
@ -96,8 +96,8 @@ When users start scanning in Windows Update through the Settings panel, the foll
![Windows Update scan log 2](images/update-scan-log-2.png)
- Common service IDs
>[!IMPORTANT]
>ServiceId here identifies a client abstraction, not any specific service in the cloud. No assumption should be made of which server a serviceId is pointing to, it's totally controlled by the SLS responses.
> [!IMPORTANT]
> ServiceId here identifies a client abstraction, not any specific service in the cloud. No assumption should be made of which server a serviceId is pointing to, it's totally controlled by the SLS responses.
|Service|ServiceId|
|-------|---------|
@ -116,8 +116,8 @@ Common update failure is caused due to network issues. To find the root of the i
- "SOAP faults" can be either client- or server-side issues; read the message.
- The WU client uses SLS (Service Locator Service) to discover the configurations and endpoints of Microsoft network update sources – WU, MU, Flighting.
>[!NOTE]
>Warning messages for SLS can be ignored if the search is against WSUS/SCCM.
> [!NOTE]
> Warning messages for SLS can be ignored if the search is against WSUS/SCCM.
- On sites that only use WSUS/SCCM, the SLS may be blocked at the firewall. In this case the SLS request will fail, and can’t scan against Windows Update or Microsoft Update but can still scan against WSUS/SCCM, since it’s locally configured.
![Windows Update scan log 3](images/update-scan-log-3.png)