mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 11:53:37 +00:00
Windows improper acronyms-batch01
Task 6027362: This PR contains updates for the following acronyms:
This commit is contained in:
Alekhya Jupudi
@ -861,7 +861,7 @@ Here's the list of corresponding Group Policy settings in HKLM\\Software\\Polici
|
||||
|DeferFeatureUpdates|REG_DWORD|1: defer feature updates<br><br>Other value or absent: don’t defer feature updates|
|
||||
|DeferFeatureUpdatesPeriodInDays|REG_DWORD|0-180: days to defer feature updates|
|
||||
|PauseFeatureUpdates|REG_DWORD|1: pause feature updates<br><br>Other value or absent: don’t pause feature updates|
|
||||
|ExcludeWUDriversInQualityUpdate|REG_DWORD|1: exclude WU drivers<br><br>Other value or absent: offer WU drivers|
|
||||
|ExcludeWUDriversInQualityUpdate|REG_DWORD|1: exclude Windows Update drivers<br><br>Other value or absent: offer Windows Update drivers|
|
||||
|
||||
Here's the list of older policies that are still supported for backward compatibility. You can use these older policies for Windows 10, version 1511 devices.
|
||||
|
||||
|
||||
@ -496,7 +496,7 @@ The status error mapping is listed below.
|
||||
|--- |--- |
|
||||
|0|Success|
|
||||
|1|Failure: invalid PFN|
|
||||
|2|Failure: invalid or expired device authentication with MSA|
|
||||
|2|Failure: invalid or expired device authentication with Microsoft account|
|
||||
|3|Failure: WNS client registration failed due to an invalid or revoked PFN|
|
||||
|4|Failure: no Channel URI assigned|
|
||||
|5|Failure: Channel URI has expired|
|
||||
|
||||
@ -64,12 +64,12 @@ manager: dansimp
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
Specifies whether user is allowed to add non-MSA email accounts.
|
||||
Specifies whether user is allowed to add email accounts other than Microsoft account.
|
||||
|
||||
Most restricted value is 0.
|
||||
|
||||
> [!NOTE]
|
||||
> This policy will only block UI/UX-based methods for adding non-Microsoft accounts.
|
||||
> This policy will only block UI/UX-based methods for adding non-Microsoft accounts.
|
||||
|
||||
<!--/Description-->
|
||||
<!--SupportedValues-->
|
||||
@ -109,7 +109,7 @@ The following list shows the supported values:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
Specifies whether the user is allowed to use an MSA account for non-email related connection authentication and services.
|
||||
Specifies whether the user is allowed to use a Microsoft account for non-email related connection authentication and services.
|
||||
|
||||
Most restricted value is 0.
|
||||
|
||||
@ -154,10 +154,10 @@ The following list shows the supported values:
|
||||
Added in Windows 10, version 1703. Allows IT Admins the ability to disable the "Microsoft Account Sign-In Assistant" (wlidsvc) NT service.
|
||||
|
||||
> [!NOTE]
|
||||
> If the MSA service is disabled, Windows Update will no longer offer feature updates to devices running Windows 10 1709 or higher. See [Feature updates are not being offered while other updates are](/windows/deployment/update/windows-update-troubleshooting#feature-updates-are-not-being-offered-while-other-updates-are).
|
||||
> If the Microsoft account service is disabled, Windows Update will no longer offer feature updates to devices running Windows 10 1709 or higher. See [Feature updates are not being offered while other updates are](/windows/deployment/update/windows-update-troubleshooting#feature-updates-are-not-being-offered-while-other-updates-are).
|
||||
|
||||
> [!NOTE]
|
||||
> If the MSA service is disabled, the Subscription Activation feature will not work properly and your users will not be able to “step-up” from Windows 10 Pro to Windows 10 Enterprise, because the MSA ticket for license authentication cannot be generated. The machine will remain on Windows 10 Pro and no error will be displayed in the Activation Settings app.
|
||||
> If the Microsoft account service is disabled, the Subscription Activation feature will not work properly and your users will not be able to “step-up” from Windows 10 Pro to Windows 10 Enterprise, because the Microsoft account ticket for license authentication cannot be generated. The machine will remain on Windows 10 Pro and no error will be displayed in the Activation Settings app.
|
||||
|
||||
<!--/Description-->
|
||||
<!--SupportedValues-->
|
||||
|
||||
@ -106,7 +106,7 @@ On a device where this policy is configured, the user specified in the policy wi
|
||||
> [!NOTE]
|
||||
>
|
||||
> - Some events such as major OS updates may require the specified user to logon to the device again to resume auto-logon behavior.
|
||||
> - Auto-logon is only supported for MSA and AAD users.
|
||||
> - Auto-logon is only supported for Microsoft account and AAD users.
|
||||
|
||||
<!--/SupportedSKUs-->
|
||||
<hr/>
|
||||
|
||||
@ -25,7 +25,7 @@ All that's required to use Quick Assist is suitable network and internet connect
|
||||
|
||||
### Authentication
|
||||
|
||||
The helper can authenticate when they sign in by using a Microsoft Account (MSA) or Azure Active Directory (Azure AD). Local Active Directory authentication isn't currently supported.
|
||||
The helper can authenticate when they sign in by using a Microsoft account (MSA) or Azure Active Directory (Azure AD). Local Active Directory authentication isn't currently supported.
|
||||
|
||||
### Network considerations
|
||||
|
||||
@ -36,7 +36,7 @@ Both the helper and sharer must be able to reach these endpoints over port 443:
|
||||
| Domain/Name | Description |
|
||||
|--|--|
|
||||
| `*.support.services.microsoft.com` | Primary endpoint used for Quick Assist application |
|
||||
| `*.login.microsoftonline.com` | Required for logging in to the application (MSA) |
|
||||
| `*.login.microsoftonline.com` | Required for logging in to the application (Microsoft account) |
|
||||
| `*.channelwebsdks.azureedge.net` | Used for chat services within Quick Assist |
|
||||
| `*.aria.microsoft.com` | Used for accessibility features within the app |
|
||||
| `*.api.support.microsoft.com` | API access for Quick Assist |
|
||||
|
||||
@ -15,7 +15,7 @@ ms.topic: troubleshooting
|
||||
|
||||
# What version of Windows am I running?
|
||||
|
||||
To determine if your device is enrolled in the [Long-Term Servicing Channel](/windows/deployment/update/waas-overview#servicing-channels) (LTSC, formerly LTSB) or the [General Availability Channel](/windows/deployment/update/waas-overview#servicing-channels) (SAC) you'll need to know what version of Windows 10 you're running. There are a few ways to figure this out. Each method provides a different set of details, so it’s useful to learn about all of them.
|
||||
To determine if your device is enrolled in the [Long-Term Servicing Channel](/windows/deployment/update/waas-overview#servicing-channels) (LTSC, formerly LTSB) or the [General Availability Channel](/windows/deployment/update/waas-overview#servicing-channels) (GA Channel) you'll need to know what version of Windows 10 you're running. There are a few ways to figure this out. Each method provides a different set of details, so it’s useful to learn about all of them.
|
||||
|
||||
## System Properties
|
||||
Click **Start** > **Settings** > **System** > click **About** from the bottom of the left-hand menu
|
||||
|
||||
Reference in New Issue
Block a user