mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 22:07:22 +00:00
Merge pull request #2924 from MicrosoftDocs/master
OOB Publish 5/28/2020 8:55 AM PST
This commit is contained in:
Thomas Raya
GitHub
commit
956ef5aa49
@ -14648,7 +14648,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/basic-level-windows-diagnostic-events-and-fields.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/privacy/required-windows-diagnostic-events-and-fields-2005",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/privacy/required-windows-diagnostic-events-and-fields-2004",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
|
||||
@ -13,7 +13,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Enable or block Windows Mixed Reality apps in the enterprise
|
||||
# Enable or block Windows Mixed Reality apps in enterprises
|
||||
|
||||
**Applies to**
|
||||
|
||||
@ -33,7 +33,7 @@ Organizations that use Windows Server Update Services (WSUS) must take action to
|
||||
|
||||
2. Windows Mixed Reality Feature on Demand (FOD) is downloaded from Windows Update. If access to Windows Update is blocked, you must manually install the Windows Mixed Reality FOD.
|
||||
|
||||
a. Download the FOD .cab file for [Windows 10, version 1903 and 1909](https://software-download.microsoft.com/download/pr/Microsoft-Windows-Holographic-Desktop-FOD-Package-31bf3856ad364e35-amd64.cab), [Windows 10, version 1809](https://software-download.microsoft.com/download/pr/microsoft-windows-holographic-desktop-fod-package31bf3856ad364e35amd64_1.cab), [Windows 10, version 1803](https://download.microsoft.com/download/9/9/3/9934B163-FA01-4108-A38A-851B4ACD1244/Microsoft-Windows-Holographic-Desktop-FOD-Package~31bf3856ad364e35~amd64~~.cab), or [Windows 10, version 1709](https://download.microsoft.com/download/6/F/8/6F816172-AC7D-4F45-B967-D573FB450CB7/Microsoft-Windows-Holographic-Desktop-FOD-Package.cab).
|
||||
a. Download the FOD .cab file for [Windows 10, version 20H1](https://software-download.microsoft.com/download/pr/Microsoft-Windows-Holographic-Desktop-FOD-Package~31bf3856ad364e35~amd64~~.cab), [Windows 10, version 1903 and 1909](https://software-download.microsoft.com/download/pr/Microsoft-Windows-Holographic-Desktop-FOD-Package-31bf3856ad364e35-amd64.cab), [Windows 10, version 1809](https://software-download.microsoft.com/download/pr/microsoft-windows-holographic-desktop-fod-package31bf3856ad364e35amd64_1.cab), [Windows 10, version 1803](https://download.microsoft.com/download/9/9/3/9934B163-FA01-4108-A38A-851B4ACD1244/Microsoft-Windows-Holographic-Desktop-FOD-Package~31bf3856ad364e35~amd64~~.cab), or [Windows 10, version 1709](https://download.microsoft.com/download/6/F/8/6F816172-AC7D-4F45-B967-D573FB450CB7/Microsoft-Windows-Holographic-Desktop-FOD-Package.cab).
|
||||
|
||||
>[!NOTE]
|
||||
>You must download the FOD .cab file that matches your operating system version.
|
||||
|
||||
@ -25,8 +25,8 @@ ms.topic: article
|
||||
|
||||
This topic helps you to deploy Windows To Go in your organization. Before you begin deployment, make sure that you have reviewed the topics [Windows To Go: feature overview](planning/windows-to-go-overview.md) and [Prepare your organization for Windows To Go](planning/prepare-your-organization-for-windows-to-go.md) to ensure that you have the correct hardware and are prepared to complete the deployment. You can then use the steps in this topic to start your Windows To Go deployment.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Windows To Go is no longer being developed. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
> [!IMPORTANT]
|
||||
> Windows To Go is removed in Windows 10, version 2004 and later operating systems. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
|
||||
## Deployment tips
|
||||
|
||||
|
||||
@ -10,7 +10,8 @@ ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: mobility
|
||||
ms.sitesec: library
|
||||
audience: itpro
author: greg-lindsay
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -21,8 +22,8 @@ ms.topic: article
|
||||
|
||||
- Windows 10
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Windows To Go is no longer being developed. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
> [!IMPORTANT]
|
||||
> Windows To Go is removed in Windows 10, version 2004 and later operating systems. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
|
||||
The following are the best practice recommendations for using Windows To Go:
|
||||
|
||||
|
||||
@ -23,7 +23,7 @@ ms.topic: article
|
||||
- Windows 10
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Windows To Go is no longer being developed. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
> Windows To Go is removed in Windows 10, version 2004 and later operating systems. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
|
||||
From the start, Windows To Go was designed to minimize differences between the user experience of working on a laptop and Windows To Go booted from a USB drive. Given that Windows To Go was designed as an enterprise solution, extra consideration was given to the deployment workflows that enterprises already have in place. Additionally, there has been a focus on minimizing the number of differences in deployment between Windows To Go workspaces and laptop PCs.
|
||||
|
||||
|
||||
@ -22,8 +22,8 @@ ms.topic: article
|
||||
|
||||
- Windows 10
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Windows To Go is no longer being developed. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
> [!IMPORTANT]
|
||||
> Windows To Go is removed in Windows 10, version 2004 and later operating systems. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
|
||||
The following information is provided to help you plan and design a new deployment of a Windows To Go in your production environment. It provides answers to the “what”, “why”, and “when” questions an IT professional might have when planning to deploy Windows To Go.
|
||||
|
||||
|
||||
@ -22,8 +22,8 @@ ms.topic: article
|
||||
|
||||
- Windows 10
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Windows To Go is no longer being developed. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
> [!IMPORTANT]
|
||||
> Windows To Go is removed in Windows 10, version 2004 and later operating systems. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
|
||||
One of the most important requirements to consider when you plan your Windows To Go deployment is to ensure that the data, content, and resources you work with in the Windows To Go workspace is protected and secure.
|
||||
|
||||
|
||||
@ -26,7 +26,9 @@ The features described below are no longer being actively developed, and might b
|
||||
|
||||
|Feature | Details and mitigation | Announced in version |
|
||||
| ----------- | --------------------- | ---- |
|
||||
| Hyper-V vSwitch on LBFO | In a future release, the Hyper-V vSwitch will no longer have the capability to be bound to an LBFO team. Instead, it can be bound via [Switch Embedded Teaming](https://docs.microsoft.com/windows-server/virtualization/hyper-v-virtual-switch/rdma-and-switch-embedded-teaming#bkmk_sswitchembedded) (SET).| 1909 |
|
||||
| Companion Device Framework | The [Companion Device Framework](https://docs.microsoft.com/windows-hardware/design/device-experiences/windows-hello-companion-device-framework) is no longer under active development.| 2004 |
|
||||
| Microsoft Edge | The legacy version of Microsoft Edge is no longer being developed.| 2004 |
|
||||
| Dynamic Disks | The [Dynamic Disks](https://docs.microsoft.com/windows/win32/fileio/basic-and-dynamic-disks#dynamic-disks) feature is no longer being developed. This feature will be fully replaced by [Storage Spaces](https://docs.microsoft.com/windows-server/storage/storage-spaces/overview) in a future release.| 2004 |
|
||||
| Language Community tab in Feedback Hub | The Language Community tab will be removed from the Feedback Hub. The standard feedback process: [Feedback Hub - Feedback](feedback-hub://?newFeedback=true&feedbackType=2) is the recommended way to provide translation feedback. | 1909 |
|
||||
| My People / People in the Shell | My People is no longer being developed. It may be removed in a future update. | 1909 |
|
||||
| Package State Roaming (PSR) | PSR will be removed in a future update. PSR allows non-Microsoft developers to access roaming data on devices, enabling developers of UWP applications to write data to Windows and synchronize it to other instantiations of Windows for that user. <br> <br>The recommended replacement for PSR is [Azure App Service](https://docs.microsoft.com/azure/app-service/). Azure App Service is widely supported, well documented, reliable, and supports cross-platform/cross-ecosystem scenarios such as iOS, Android and web. | 1909 |
|
||||
|
||||
@ -27,6 +27,9 @@ The following features and functionalities have been removed from the installed
|
||||
|
||||
|Feature | Details and mitigation | Removed in version |
|
||||
| ----------- | --------------------- | ------ |
|
||||
| Cortana | Cortana has been updated and enhanced in the Windows 10 May 2020 Update. With [these changes](https://docs.microsoft.com/windows/whats-new/whats-new-windows-10-version-2004#cortana), some previously available consumer skills such as music, connected home, and other non-Microsoft skills are no longer available. | 2004 |
|
||||
| Windows To Go | Windows To Go was announced as deprecated in Windows 10, version 1903 and is removed in this release. | 2004 |
|
||||
| Mobile Plans and Messaging apps | Both apps are still supported, but are now distributed in a different way. OEMs can now include these apps in Windows images for cellular enabled devices. The apps are removed for non-cellular devices.| 2004 |
|
||||
| PNRP APIs| The Peer Name Resolution Protocol (PNRP) cloud service was removed in Windows 10, version 1809. We are planning to complete the removal process by removing the corresponding APIs. | 1909 |
|
||||
| Taskbar settings roaming | Roaming of taskbar settings is removed in this release. This feature was announced as no longer being developed in Windows 10, version 1903. | 1909 |
|
||||
| Desktop messaging app doesn't offer messages sync | The messaging app on Desktop has a sync feature that can be used to sync SMS text messages received from Windows Mobile and keep a copy of them on the Desktop. The sync feature has been removed from all devices. Due to this change, you will only be able to access messages from the device that received the message. | 1903 |
|
||||
|
||||
@ -22,8 +22,8 @@ ms.topic: article
|
||||
|
||||
- Windows 10
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Windows To Go is no longer being developed. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
> [!IMPORTANT]
|
||||
> Windows To Go is removed in Windows 10, version 2004 and later operating systems. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
|
||||
The following list identifies some commonly asked questions about Windows To Go.
|
||||
|
||||
|
||||
@ -23,7 +23,7 @@ ms.topic: article
|
||||
- Windows 10
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Windows To Go is no longer being developed. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
> Windows To Go is removed in Windows 10, version 2004 and later operating systems. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
|
||||
Windows To Go is a feature in Windows 10 Enterprise and Windows 10 Education that enables the creation of a Windows To Go workspace that can be booted from a USB-connected external drive on PCs.
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@
|
||||
### [Diagnostic Data Viewer Overview](diagnostic-data-viewer-overview.md)
|
||||
### [Diagnostic Data Viewer for PowerShell Overview](Microsoft-DiagnosticDataViewer.md)
|
||||
## Basic level Windows diagnostic data events and fields
|
||||
### [Windows 10, version 2005 required Windows diagnostic data events and fields](required-windows-diagnostic-data-events-and-fields-2005.md)
|
||||
### [Windows 10, version 2004 required Windows diagnostic data events and fields](required-windows-diagnostic-data-events-and-fields-2004.md)
|
||||
### [Windows 10, version 1903 and Windows 10, version 1909 basic level Windows diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1903.md)
|
||||
### [Windows 10, version 1809 basic level Windows diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
||||
### [Windows 10, version 1803 basic level Windows diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
description: Use this article to learn more about what required Windows diagnostic data is gathered.
|
||||
title: Windows 10, version 2005 required diagnostic events and fields (Windows 10)
|
||||
title: Windows 10, version 2004 required diagnostic events and fields (Windows 10)
|
||||
keywords: privacy, telemetry
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
@ -17,7 +17,7 @@ ms.date: 03/27/2020
|
||||
---
|
||||
|
||||
|
||||
# Windows 10, version 2005 required Windows diagnostic events and fields
|
||||
# Windows 10, version 2004 required Windows diagnostic events and fields
|
||||
|
||||
|
||||
> [!IMPORTANT]
|
||||
@ -26,7 +26,7 @@ ms.date: 03/27/2020
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10, version 2005
|
||||
- Windows 10, version 2004
|
||||
|
||||
|
||||
Required diagnostic data gathers a limited set of information that is critical for understanding the device and its configuration including: basic device information, quality-related information, app compatibility, and Microsoft Store.
|
||||
@ -90,7 +90,6 @@ The following fields are available:
|
||||
- **CosDeviceSolutionUrl** Microsoft.Windows.Appraiser.General.DatasourceDevicePnpAdd . Empty string
|
||||
- **CosPopulatedFromId** The expected uplevel driver matching ID based on driver coverage data.
|
||||
- **IsBootCritical** Indicates whether the device boot is critical.
|
||||
- **SdbEntries** Deprecated in RS3.
|
||||
- **UplevelInboxDriver** Indicates whether there is a driver uplevel for this device.
|
||||
- **WuDriverCoverage** Indicates whether there is a driver uplevel for this device, according to Windows Update.
|
||||
- **WuDriverUpdateId** The Windows Update ID of the applicable uplevel driver.
|
||||
@ -103,10 +102,6 @@ This event sends compatibility database data about driver packages to help keep
|
||||
|
||||
This event includes fields from [Ms.Device.DeviceInventoryChange](#msdevicedeviceinventorychange).
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **SdbEntries** Deprecated in RS3.
|
||||
|
||||
|
||||
### Microsoft.Windows.Appraiser.General.DataSourceMatchingInfoPassiveRemove
|
||||
|
||||
@ -636,7 +631,6 @@ The following fields are available:
|
||||
- **Categories** A comma separated list of functional categories in which the container belongs.
|
||||
- **DiscoveryMethod** The discovery method for the device container.
|
||||
- **FriendlyName** The name of the device container.
|
||||
- **Icon** Deprecated in RS3. The path or index to the icon file.
|
||||
- **IsActive** Is the device connected, or has it been seen in the last 14 days?
|
||||
- **IsConnected** For a physically attached device, this value is the same as IsPresent. For wireless a device, this value represents a communication link.
|
||||
- **IsMachineContainer** Is the container the root device itself?
|
||||
Loading…
x
Reference in New Issue
Block a user