mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 02:43:43 +00:00
Merge branch 'main' into ado14614835
This commit is contained in:
Rebecca Agiewich
GitHub
@ -14,7 +14,7 @@ ms.collection: highpri
|
||||
|
||||
# Use Quick Assist to help users
|
||||
|
||||
Quick Assist is a Windows application that enables a person to share their device with another person over a remote connection. Your support staff can use it to remotely connect to a user's device and then view its display, make annotations, or take full control. In this way, they can troubleshoot, diagnose technological issues, and provide instructions to users directly on their devices.
|
||||
Quick Assist is a Microsoft Store application that enables a person to share their device with another person over a remote connection. Your support staff can use it to remotely connect to a user's device and then view its display, make annotations, or take full control. In this way, they can troubleshoot, diagnose technological issues, and provide instructions to users directly on their devices.
|
||||
|
||||
## Before you begin
|
||||
|
||||
@ -42,7 +42,6 @@ Both the helper and sharer must be able to reach these endpoints over port 443:
|
||||
| `*.api.support.microsoft.com` | API access for Quick Assist |
|
||||
| `*.vortex.data.microsoft.com` | Used for diagnostic data |
|
||||
| `*.channelservices.microsoft.com` | Required for chat services within Quick Assist |
|
||||
| `*.skype.com` | Skype requests may vary based on geography. If connection issues persist, test this endpoint. |
|
||||
| `*.remoteassistanceprodacs.communication.azure.com` | Azure Communication Services (ACS) technology the Quick Assist app uses. |
|
||||
| `*.turn.azure.com` | Protocol used to help endpoint. |
|
||||
| `browser.pipe.aria.microsoft.com` | Required diagnostic data for client and services used by Quick Assist. |
|
||||
@ -105,23 +104,7 @@ Either the support staff or a user can start a Quick Assist session.
|
||||
|
||||
## If Quick Assist is missing
|
||||
|
||||
If for some reason a user doesn't have Quick Assist on their system or it's not working properly, try to uninstall and reinstall it.
|
||||
|
||||
### Uninstall Quick Assist
|
||||
|
||||
1. Start the Settings app, and then select **Apps**.
|
||||
2. Select **Optional features**.
|
||||
3. In the **Installed features** search bar, type *Quick Assist*.
|
||||
4. Select **Microsoft Quick Assist**, and then select **Uninstall**.
|
||||
|
||||
### Reinstall Quick Assist
|
||||
|
||||
1. Start the Settings app, and then select **Apps**.
|
||||
2. Select **Optional features**.
|
||||
3. Select **Add a feature**.
|
||||
4. In the new dialog that opens, in the **Add an optional feature** search bar, type *Quick Assist*.
|
||||
5. Select the check box for **Microsoft Quick Assist**, and then select **Install**.
|
||||
6. Restart the device.
|
||||
If for some reason a user doesn't have Quick Assist on their system or it's not working properly, try to uninstall and reinstall it. For more information, see [Install Quick Assist](https://support.microsoft.com/windows/install-quick-assist-c17479b7-a49d-4d12-938c-dbfb97c88bca).
|
||||
|
||||
## Next steps
|
||||
|
||||
|
||||
@ -134,14 +134,14 @@ Deployment scheduling controls are always available, but to take advantage of th
|
||||
|
||||
To enroll devices in Windows Update for Business cloud processing, set the **AllowWUfBCloudProcessing** policy using mobile device management (MDM) policy or Group Policy.
|
||||
|
||||
| Policy | Sets registry key under **HKLM\\Software** |
|
||||
|--------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|
|
||||
| GPO for Windows 10, version 1809 or later: Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds > **Allow WUfB Cloud Processing** | \\Policies\\Microsoft\\Windows\\DataCollection\\AllowWUfBCloudProcessing |
|
||||
| MDM for Windows 10, version 1809 or later: ../Vendor/MSFT/ Policy/Config/System/**AllowWUfBCloudProcessing** | \\Microsoft\\PolicyManager\\default\\System\\AllowWUfBCloudProcessing |
|
||||
| Policy| Sets registry key under `HKLM\Software`|
|
||||
|--|--|
|
||||
| GPO for Windows 10, version 1809 or later: Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds > **Allow WUfB Cloud Processing** | `\Policies\Microsoft\Windows\DataCollection\AllowWUfBCloudProcessing` |
|
||||
| MDM for Windows 10, version 1809 or later: ../Vendor/MSFT/ Policy/Config/System/**AllowWUfBCloudProcessing** | `\Microsoft\PolicyManager\current\device\System\AllowWUfBCloudProcessing` |
|
||||
|
||||
Following is an example of setting the policy using Microsoft Endpoint Manager:
|
||||
|
||||
1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
1. Sign in to the [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/).
|
||||
|
||||
2. Select **Devices** > **Configuration profiles** > **Create profile**.
|
||||
|
||||
@ -162,7 +162,7 @@ Following is an example of setting the policy using Microsoft Endpoint Manager:
|
||||
|
||||
8. (Optional) To verify that the policy reached the client, check the value of the following registry entry:
|
||||
|
||||
**HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\PolicyManager \\default\\System\\AllowWUfBCloudProcessing**
|
||||
`HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\System\AllowWUfBCloudProcessing`
|
||||
|
||||
## Best practices
|
||||
Follow these suggestions for the best results with the service.
|
||||
|
||||
@ -57,6 +57,9 @@ To help you better understand the scan source policy, see the default scan behav
|
||||
> [!TIP]
|
||||
> The only two relevant policies for where your updates come from are the specify scan source policy and whether or not you have configured a WSUS server. This should simplify the configuration options.
|
||||
|
||||
> [!NOTE]
|
||||
> If you have devices configured for WSUS and do not configure the scan source policy for feature updates to come from Windows update or set any Windows Update for Business offering policies, then users who select "Check online for updates" on the Settings page may see the optional upgrade to Windows 11. We recommend configuring the scan source policy or a Windows Update for Business offering policy to prevent such.
|
||||
|
||||
## Configure the scan sources
|
||||
|
||||
The policy can be configured using the following two methods:
|
||||
|
||||
@ -23,6 +23,7 @@ title: BitLocker Overview and Requirements FAQ
|
||||
summary: |
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
|
||||
sections:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: BitLocker (Windows 10)
|
||||
title: BitLocker
|
||||
description: This topic provides a high-level overview of BitLocker, including a list of system requirements, practical applications, and deprecated features.
|
||||
ms.assetid: 40526fcc-3e0d-4d75-90e0-c7d0615f33b2
|
||||
ms.author: dansimp
|
||||
@ -102,4 +102,4 @@ When installing the BitLocker optional component on a server you will also need
|
||||
| [Protect BitLocker from pre-boot attacks](./bitlocker-countermeasures.md)| This detailed guide will help you understand the circumstances under which the use of pre-boot authentication is recommended for devices running Windows 11, Windows 10, Windows 8.1, Windows 8, or Windows 7; and when it can be safely omitted from a device’s configuration. |
|
||||
| [Troubleshoot BitLocker](troubleshoot-bitlocker.md) | This guide describes the resources that can help you troubleshoot BitLocker issues, and provides solutions for several common BitLocker issues. |
|
||||
| [Protecting cluster shared volumes and storage area networks with BitLocker](protecting-cluster-shared-volumes-and-storage-area-networks-with-bitlocker.md)| This topic for IT pros describes how to protect CSVs and SANs with BitLocker.|
|
||||
| [Enabling Secure Boot and BitLocker Device Encryption on Windows IoT Core](/windows/iot-core/secure-your-device/SecureBootAndBitLocker) | This topic covers how to use BitLocker with Windows IoT Core |
|
||||
| [Enabling Secure Boot and BitLocker Device Encryption on Windows IoT Core](/windows/iot-core/secure-your-device/SecureBootAndBitLocker) | This topic covers how to use BitLocker with Windows IoT Core |
|
||||
|
||||
@ -14,7 +14,6 @@ manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 04/19/2017
|
||||
ms.technology: windows-sec
|
||||
---
|
||||
|
||||
@ -86,7 +85,7 @@ None. Changes to this policy become effective without a restart when saved local
|
||||
|
||||
### Group Policy
|
||||
|
||||
Setting and deploying this policy using Group Policy takes precedence over the setting on the local device. If the Group Policy is set to **Not Configured**, local settings will apply.
|
||||
Setting and deploying this policy using Group Policy takes precedence over the setting on the local device. If the Group Policy is set to **Not Configured**, local settings will apply. The policy is applicable to domain controllers only.
|
||||
|
||||
### Auditing
|
||||
|
||||
|
||||
Reference in New Issue
Block a user