mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 13:57:22 +00:00
Merge pull request #4135 from ShannonLeavitt/acrolinx-windows-configuration
Acrolinx fixes: acrolinx-windows-configuration
This commit is contained in:
commit
110e53b1a1
@ -20,7 +20,7 @@ manager: dansimp
|
||||
|
||||
Cortana will respond with the information from Bing.
|
||||
|
||||
:::image type="content" source="../screenshot5.png" alt-text="Screenshot: Cortana showing current time in Hyderbad":::
|
||||
:::image type="content" source="../screenshot5.png" alt-text="Screenshot: Cortana showing current time in Hyderabad":::
|
||||
|
||||
>[!NOTE]
|
||||
>This scenario requires Bing Answers to be enabled. To learn more, see [Set up and configure the Bing Answers feature](https://docs.microsoft.com/windows/configuration/cortana-at-work/set-up-and-test-cortana-in-windows-10#set-up-and-configure-the-bing-answers-feature).
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Use MDM Bridge WMI Provider to create a Windows 10 kiosk (Windows 10)
|
||||
description: Environments that use Windows Management Instrumentation (WMI)can use the MDM Bridge WMI Provider to configure the MDM_AssignedAccess class.
|
||||
description: Environments that use Windows Management Instrumentation (WMI) can use the MDM Bridge WMI Provider to configure the MDM_AssignedAccess class.
|
||||
ms.assetid: 428680AE-A05F-43ED-BD59-088024D1BFCC
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
@ -22,9 +22,9 @@ ms.topic: article
|
||||
|
||||
- Windows 10 Pro, Enterprise, and Education
|
||||
|
||||
Environments that use [Windows Management Instrumentation (WMI)](https://msdn.microsoft.com/library/aa394582.aspx) can use the [MDM Bridge WMI Provider](https://msdn.microsoft.com/library/windows/desktop/dn905224.aspx) to configure the MDM_AssignedAccess class. See [PowerShell Scripting with WMI Bridge Provider](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/using-powershell-scripting-with-the-wmi-bridge-provider) for more details about using a PowerShell script to configure AssignedAccess.
|
||||
Environments that use [Windows Management Instrumentation (WMI)](https://msdn.microsoft.com/library/aa394582.aspx) can use the [MDM Bridge WMI Provider](https://msdn.microsoft.com/library/windows/desktop/dn905224.aspx) to configure the MDM_AssignedAccess class. For more information about using a PowerShell script to configure AssignedAccess, see [PowerShell Scripting with WMI Bridge Provider](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/using-powershell-scripting-with-the-wmi-bridge-provider).
|
||||
|
||||
Here’s an example to set AssignedAccess configuration:
|
||||
Here's an example to set AssignedAccess configuration:
|
||||
|
||||
1. Download the [psexec tool](https://technet.microsoft.com/sysinternals/bb897553.aspx).
|
||||
2. Run `psexec.exe -i -s cmd.exe`.
|
||||
|
@ -255,7 +255,7 @@ This sample demonstrates that both UWP and Win32 apps can be configured to autom
|
||||
```
|
||||
|
||||
## [Preview] Global Profile Sample XML
|
||||
Global Profile is currently supported in Windows 10 Insider Preview (20H1 builds). Global Profile is designed for scenarios where a user does not have a designated profile, yet IT Admin still wants the user to run in lock down mode, or used as mitigation when a profile cannot be determined for an user.
|
||||
Global Profile is currently supported in Windows 10 Insider Preview (20H1 builds). Global Profile is designed for scenarios where a user does not have a designated profile, yet IT Admin still wants the user to run in lockdown mode, or used as mitigation when a profile cannot be determined for a user.
|
||||
|
||||
This sample demonstrates that only a global profile is used, no active user configured. Global profile will be applied when every non-admin account logs in
|
||||
```xml
|
||||
@ -309,7 +309,7 @@ This sample demonstrates that only a global profile is used, no active user conf
|
||||
</AssignedAccessConfiguration>
|
||||
```
|
||||
|
||||
Below sample shows dedicated profile and global profile mixed usage, aauser would use one profile, everyone else that's non-admin will use another profile.
|
||||
Below sample shows dedicated profile and global profile mixed usage, a user would use one profile, everyone else that's non-admin will use another profile.
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
<AssignedAccessConfiguration
|
||||
@ -396,7 +396,7 @@ Below sample shows dedicated profile and global profile mixed usage, aauser woul
|
||||
## [Preview] Folder Access sample xml
|
||||
In Windows 10, version 1809, folder access is locked down so that when common file dialog is opened, IT Admin can specify if the user has access to the Downloads folder, or no access to any folder at all. This restriction has been redesigned for finer granulatity and easier use, and is available in Windows 10 Insider Preview (19H2, 20H1 builds).
|
||||
|
||||
IT Admin now can specify user access to Downloads folder, Removable drives, or no restrictions at all. Note that Downloads and Removable Drives can be allowed at the same time.
|
||||
IT Admin now can specify user access to Downloads folder, Removable drives, or no restrictions at all. Downloads and Removable Drives can be allowed at the same time.
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
@ -889,7 +889,7 @@ Schema for Windows 10 Insider Preview (19H2, 20H1 builds)
|
||||
</xs:schema>
|
||||
```
|
||||
|
||||
To authorize a compatible configuration XML that includes elements and attributes from Windows 10, version 1809 or newer, always include the namespace of these add-on schemas, and decorate the attributes and elements accordingly with the namespace alias. For example, to configure the auto-launch feature which is added in Windows 10, version 1809, use the following sample. Notice an alias r1809 is given to the 201810 namespace for Windows 10, version 1809, and the alias is tagged on AutoLaunch and AutoLaunchArguments inline.
|
||||
To authorize a compatible configuration XML that includes elements and attributes from Windows 10, version 1809 or newer, always include the namespace of these add-on schemas, and decorate the attributes and elements accordingly with the namespace alias. For example, to configure the autolaunch feature that was added in Windows 10, version 1809, use the following sample. Notice an alias r1809 is given to the 201810 namespace for Windows 10, version 1809, and the alias is tagged on AutoLaunch and AutoLaunchArguments inline.
|
||||
```xml
|
||||
<AssignedAccessConfiguration
|
||||
xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
||||
|
@ -12,41 +12,41 @@ manager: dansimp
|
||||
ms.topic: troubleshooting
|
||||
---
|
||||
|
||||
# Troubleshoot Start Menu errors
|
||||
# Troubleshoot Start menu errors
|
||||
|
||||
Start failures can be organized into these categories:
|
||||
|
||||
- **Deployment/Install issues** - Easiest to identify but difficult to recover. This failure is consistent and usually permanent. Reset, restore from backup, or rollback to recover.
|
||||
- **Performance issues** - More common with older hardware, low-powered machines. Symptoms include: High CPU utilization, disk contention, memory resources. This makes Start very slow to respond. Behavior is intermittent depending on available resources.
|
||||
- **Crashes** - Also easy to identify. Crashes in Shell Experience Host or related can be found in System or Application event logs. This can be a code defect or related to missing or altered permissions to files or registry keys by a program or incorrect security tightening configurations. Determining permissions issues can be time consuming but a [SysInternals tool called Procmon](https://docs.microsoft.com/sysinternals/downloads/procmon) will show **Access Denied**. The other option is to get a dump of the process when it crashes and depending on comfort level, review the dump in the debugger, or have support review the data.
|
||||
- **Hangs** in Shell Experience host or related. These are the hardest issues to identify as there are few events logged, but behavior is typically intermittent or recovers with a reboot. If a background application or service hangs, Start will not have resources to respond in time. Clean boot may help identify if the issue is related to additional software. Procmon is also useful in this scenario.
|
||||
- **Hangs** - in Shell Experience host or related. These are the hardest issues to identify as there are few events logged, but behavior is typically intermittent or recovers with a reboot. If a background application or service hangs, Start will not have resources to respond in time. Clean boot may help identify if the issue is related to additional software. Procmon is also useful in this scenario.
|
||||
- **Other issues** - Customization, domain policies, deployment issues.
|
||||
|
||||
## Basic troubleshooting
|
||||
|
||||
When troubleshooting basic Start issues (and for the most part, all other Windows apps), there are a few things to check if they are not working as expected. When experiencing issues where the Start Menu or sub-component are not working, there are some quick tests to narrow down where the issue may reside.
|
||||
When troubleshooting basic Start issues (and for the most part, all other Windows apps), there are a few things to check if they are not working as expected. For issues where the Start menu or subcomponent isn't working, you can do some quick tests to narrow down where the issue may reside.
|
||||
|
||||
### Check the OS and update version
|
||||
|
||||
- Is the system running the latest Feature and Cumulative Monthly update?
|
||||
- Did the issue start immediately after an update? Ways to check:
|
||||
- Powershell:[System.Environment]::OSVersion.Version
|
||||
- PowerShell:[System.Environment]::OSVersion.Version
|
||||
- WinVer from CMD.exe
|
||||
|
||||
### Check if Start is installed
|
||||
|
||||
- If Start fails immediately after a feature update, on thing to check is if the App package failed to install successfully.
|
||||
|
||||
- If Start was working and just fails intermittently, it's likely that Start is installed correctly, but the issue occurs downstream. The way to check for this is to look for output from these two PS commands:
|
||||
- If Start was working and just fails intermittently, it's likely that Start is installed correctly, but the issue occurs downstream. The way to check for this problem is to look for output from these two PS commands:
|
||||
|
||||
- `get-AppXPackage -Name Microsoft.Windows.ShellExperienceHost`
|
||||
- `get-AppXPackage -Name Microsoft.Windows.Cortana`
|
||||
|
||||

|
||||
|
||||
Failure messages will appear if they are not installed
|
||||
Failure messages will appear if they aren't installed
|
||||
|
||||
- If Start is not installed the fastest resolution is to revert to a known good configuration. This can be rolling back the update, resetting the PC to defaults (where there is a choice to save to delete user data), or restoring from backup. There is no supported method to install Start Appx files. The results are often problematic and unreliable.
|
||||
- If Start is not installed, then the fastest resolution is to revert to a known good configuration. This can be rolling back the update, resetting the PC to defaults (where there is a choice to save to delete user data), or restoring from backup. No method is supported to install Start Appx files. The results are often problematic and unreliable.
|
||||
|
||||
### Check if Start is running
|
||||
|
||||
@ -54,7 +54,7 @@ If either component is failing to start on boot, reviewing the event logs for er
|
||||
- `get-process -name shellexperiencehost`
|
||||
- `get-process -name searchui`
|
||||
|
||||
If it is installed but not running, test booting into safe mode or use MSCONFIG to eliminate 3rd party or additional drivers and applications.
|
||||
If it is installed but not running, test booting into safe mode or use MSCONFIG to eliminate third-party or additional drivers and applications.
|
||||
|
||||
### Check whether the system a clean install or upgrade
|
||||
|
||||
@ -76,9 +76,9 @@ If these events are found, Start is not activated correctly. Each event will hav
|
||||
|
||||
### Other things to consider
|
||||
|
||||
When did this start?
|
||||
When did the problem start?
|
||||
|
||||
- Top issues for Start Menu failure are triggered
|
||||
- Top issues for Start menu failure are triggered
|
||||
- After an update
|
||||
- After installation of an application
|
||||
- After joining a domain or applying a domain policy
|
||||
@ -87,7 +87,7 @@ When did this start?
|
||||
- Start or related component crashes or hangs
|
||||
- Customization failure
|
||||
|
||||
To narrow this down further, it's good to note:
|
||||
To narrow down the problem further, it's good to note:
|
||||
|
||||
- What is the install background?
|
||||
- Was this a deployment, install from media, other
|
||||
@ -103,7 +103,7 @@ To narrow this down further, it's good to note:
|
||||
- Some Group Policies intended for Windows 7 or older have been known to cause issues with Start
|
||||
- Untested Start Menu customizations can cause unexpected behavior by typically not complete Start failures.
|
||||
|
||||
- Is this a virtualized environment?
|
||||
- Is the environment virtualized?
|
||||
- VMware
|
||||
- Citrix
|
||||
- Other
|
||||
@ -123,13 +123,13 @@ To narrow this down further, it's good to note:
|
||||
- Microsoft-Windows-CloudStore*
|
||||
|
||||
|
||||
- Check for crashes that may be related to Start (explorer.exe, taskbar, etc)
|
||||
- Check for crashes that may be related to Start (explorer.exe, taskbar, and so on)
|
||||
- Application log event 1000, 1001
|
||||
- Check WER reports
|
||||
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive\
|
||||
- C:\ProgramData\Micrt\Windowsosof\WER\ReportQueue\
|
||||
|
||||
If there is a component of Start that is consistently crashing, capture a dump which can be reviewed by Microsoft Support.
|
||||
If there is a component of Start that is consistently crashing, capture a dump that can be reviewed by Microsoft Support.
|
||||
|
||||
## Common errors and mitigation
|
||||
|
||||
@ -169,7 +169,8 @@ The PDC registry key is:
|
||||
**Type**=dword:00000001
|
||||
|
||||
In addition to the listed dependencies for the service, Background Tasks Infrastructure Service requires the Power Dependency Coordinator Driver to be loaded. If the PDC does not load at boot, Background Tasks Infrastructure Service will fail and affect Start Menu.
|
||||
Events for both PDC and Background Tasks Infrastructure Service will be recorded in the event logs. PDC should not be disabled or deleted. BrokerInfrastructure is an automatic service. This Service is required for all these operating Systems as running to have a stable Start Menu.
|
||||
|
||||
Events for both PDC and Background Tasks Infrastructure Service will be recorded in the event logs. PDC shouldn't be disabled or deleted. BrokerInfrastructure is an automatic service. This Service is required for all these operating Systems as running to have a stable Start Menu.
|
||||
|
||||
>[!NOTE]
|
||||
>You cannot stop this automatic service when machine is running (C:\windows\system32\svchost.exe -k DcomLaunch -p).
|
||||
@ -179,17 +180,17 @@ Events for both PDC and Background Tasks Infrastructure Service will be recorded
|
||||
|
||||
**Cause**: There was a change in the All Apps list between Windows 10, versions 1511 and 1607. These changes mean the original Group Policy and corresponding registry key no longer apply.
|
||||
|
||||
**Resolution**: This issue was resolved in the June 2017 updates. Please update Windows 10, version 1607 to the latest cumulative or feature updates.
|
||||
**Resolution**: This issue was resolved in the June 2017 updates. Update Windows 10, version 1607, to the latest cumulative or feature updates.
|
||||
|
||||
>[!NOTE]
|
||||
>When the Group Policy is enabled, the desired behavior also needs to be selected. By default, it is set to **None**.
|
||||
|
||||
|
||||
### Symptom: Application tiles like Alarm, Calculator, and Edge are missing from Start Menu and the Settings app fails to open on Windows 10, version 1709 when a local user profile is deleted
|
||||
### Symptom: Application tiles like Alarm, Calculator, and Edge are missing from Start menu and the Settings app fails to open on Windows 10, version 1709 when a local user profile is deleted
|
||||
|
||||

|
||||
|
||||
**Cause**: This is a known issue where the first-time logon experience is not detected and does not trigger the install of some Apps.
|
||||
**Cause**: This issue is known. The first-time sign-in experience is not detected and does not trigger the install of some apps.
|
||||
|
||||
**Resolution**: This issue has been fixed for Windows 10, version 1709 in [KB 4089848](https://support.microsoft.com/help/4089848) March 22, 2018—KB4089848 (OS Build 16299.334)
|
||||
|
||||
@ -202,17 +203,17 @@ Events for both PDC and Background Tasks Infrastructure Service will be recorded
|
||||
- Event ID 22 is logged when the xml is malformed, meaning the specified file simply isn’t valid xml.
|
||||
- When editing the xml file, it should be saved in UTF-8 format.
|
||||
|
||||
- Unexpected information: This occurs when possibly trying to add a tile via unexpected or undocumented method.
|
||||
- Unexpected information: This occurs when possibly trying to add a tile via an unexpected or undocumented method.
|
||||
- **Event ID: 64** is logged when the xml is valid but has unexpected values.
|
||||
- For example: The following error occurred while parsing a layout xml file: The attribute 'LayoutCustomizationRestrictiontype' on the element '{http://schemas.microsoft.com/Start/2014/LayoutModification}DefaultLayoutOverride' is not defined in the DTD/Schema.
|
||||
|
||||
XML files can and should be tested locally on a Hyper-V or other virtual machine before deployment or application by Group Policy
|
||||
|
||||
### Symptom: Start menu no longer works after a PC is refreshed using F12 during start up
|
||||
### Symptom: Start menu no longer works after a PC is refreshed using F12 during startup
|
||||
|
||||
**Description**: If a user is having problems with a PC, is can be refreshed, reset, or restored. Refreshing the PC is a beneficial option because it maintains personal files and settings. When users have trouble starting the PC, "Change PC settings" in Settings is not accessible. So, to access the System Refresh, users may use the F12 key at start up. Refreshing the PC finishes, but Start Menu is not accessible.
|
||||
**Description**: If a user is having problems with a PC, it can be refreshed, reset, or restored. Refreshing the PC is a beneficial option because it maintains personal files and settings. When users have trouble starting the PC, "Change PC settings" in Settings is not accessible. So, to access the System Refresh, users may use the F12 key at startup. Refreshing the PC finishes, but Start Menu is not accessible.
|
||||
|
||||
**Cause**: This is a known issue and has been resolved in a cumulative update released August 30th 2018.
|
||||
**Cause**: This issue is known and was resolved in a cumulative update released August 30, 2018.
|
||||
|
||||
**Resolution**: Install corrective updates; a fix is included in the [September 11, 2018-KB4457142 release](https://support.microsoft.com/help/4457142).
|
||||
|
||||
@ -232,7 +233,7 @@ Specifically, behaviors include
|
||||
- Applications (apps or icons) pinned to the start menu are missing.
|
||||
- Entire tile window disappears.
|
||||
- The start button fails to respond.
|
||||
- If a new roaming user is created, the first logon appears normal, but on subsequent logons, tiles are missing.
|
||||
- If a new roaming user is created, the first sign-in appears normal, but on subsequent sign-ins, tiles are missing.
|
||||
|
||||
|
||||

|
||||
@ -261,12 +262,12 @@ After the upgrade the user pinned tiles are missing:
|
||||
|
||||

|
||||
|
||||
Additionally, users may see blank tiles if logon was attempted without network connectivity.
|
||||
Additionally, users may see blank tiles if sign-in was attempted without network connectivity.
|
||||
|
||||

|
||||
|
||||
|
||||
**Resolution**: This is fixed in [October 2017 update](https://support.microsoft.com/en-us/help/4041676).
|
||||
**Resolution**: This issue was fixed in the [October 2017 update](https://support.microsoft.com/en-us/help/4041676).
|
||||
|
||||
### Symptom: Tiles are missing after upgrade from Windows 10, version 1607 to version 1709 for users with Roaming User Profiles (RUP) enabled and managed Start Menu layout with partial lockdown
|
||||
|
||||
@ -278,13 +279,13 @@ Additionally, users may see blank tiles if logon was attempted without network c
|
||||
|
||||
### Symptom: Start Menu issues with Tile Data Layer corruption
|
||||
|
||||
**Cause**: Windows 10, version 1507 through the release of version 1607 uses a database for the Tile image information. This is called the Tile Data Layer database (The feature was deprecated in [Windows 10 1703](https://support.microsoft.com/help/4014193/features-that-are-removed-or-deprecated-in-windows-10-creators-update)).
|
||||
**Cause**: Windows 10, version 1507 through the release of version 1607 uses a database for the Tile image information. This is called the Tile Data Layer database. (The feature was deprecated in [Windows 10 1703](https://support.microsoft.com/help/4014193/features-that-are-removed-or-deprecated-in-windows-10-creators-update).)
|
||||
|
||||
**Resolution** There are steps you can take to fix the icons, first is to confirm that is the issue that needs to be addressed.
|
||||
|
||||
1. The App or Apps work fine when you click on the tiles.
|
||||
1. The App or Apps work fine when you select the tiles.
|
||||
2. The tiles are blank, have a generic placeholder icon, have the wrong or strange title information.
|
||||
3. The app is missing, but listed as installed via Powershell and works if you launch via URI.
|
||||
3. The app is missing, but listed as installed via PowerShell and works if you launch via URI.
|
||||
- Example: `windows-feedback://`
|
||||
4. In some cases, Start can be blank, and Action Center and Cortana do not launch.
|
||||
|
||||
@ -301,9 +302,9 @@ Although a reboot is not required, it may help clear up any residual issues afte
|
||||
|
||||
### Symptoms: Start Menu and Apps cannot start after upgrade to Windows 10 version 1809 when Symantec Endpoint Protection is installed
|
||||
|
||||
**Description** Start Menu, Search and Apps do not start after you upgrade a Windows 7-based computer that has Symantec Endpoint Protection installed to Windows 10 version 1809.
|
||||
**Description**: Start menu, Search, and Apps do not start after you upgrade a computer running Windows 7 that has Symantec Endpoint Protection installed to Windows 10 version 1809.
|
||||
|
||||
**Cause** This occurs because of a failure to load sysfer.dll. During upgrade, the setup process does not set the privilege group "All Application Packages" on sysfer.dll and other Symantec modules.
|
||||
**Cause**: This problem occurs because of a failure to load sysfer.dll. During upgrade, the setup process does not set the privilege group "All Application Packages" on sysfer.dll and other Symantec modules.
|
||||
|
||||
**Resolution** This issue was fixed by the Windows Cumulative Update that were released on December 5, 2018—KB4469342 (OS Build 17763.168).
|
||||
|
||||
@ -321,7 +322,7 @@ If you have already encountered this issue, use one of the following two options
|
||||
|
||||
4. Confirm that **All Application Packages** group is missing.
|
||||
|
||||
5. Click **Edit**, and then click **Add** to add the group.
|
||||
5. Select **Edit**, and then select **Add** to add the group.
|
||||
|
||||
6. Test Start and other Apps.
|
||||
|
||||
|
@ -24,7 +24,7 @@ As an administrator of User Experience Virtualization (UE-V), you can restore ap
|
||||
## Restore Settings in UE-V when a User Adopts a New Device
|
||||
|
||||
|
||||
To restore settings when a user adopts a new device, you can put a settings location template in **backup** or **roam (default)** profile using the Set-UevTemplateProfile PowerShell cmdlet. This lets computer settings sync to the new computer, in addition to user settings. Templates assigned to the backup profile are backed up for that device and configured on a per-device basis. To backup settings for a template, use the following cmdlet in Windows PowerShell:
|
||||
To restore settings when a user adopts a new device, you can put a settings location template in a **backup** or **roam (default)** profile using the Set-UevTemplateProfile PowerShell cmdlet. This setup lets computer settings sync to the new computer, in addition to user settings. Templates assigned to the backup profile are backed up for that device and configured on a per-device basis. To back up settings for a template, use the following cmdlet in Windows PowerShell:
|
||||
|
||||
```powershell
|
||||
Set-UevTemplateProfile -ID <TemplateID> -Profile <backup>
|
||||
@ -50,7 +50,7 @@ As part of the Backup/Restore feature, UE-V added **last known good (LKG)** to t
|
||||
|
||||
### How to Backup/Restore Templates with UE-V
|
||||
|
||||
These are the key backup and restore components of UE-V:
|
||||
Here are the key backup and restore components of UE-V:
|
||||
|
||||
- Template profiles
|
||||
|
||||
@ -74,7 +74,7 @@ All templates are included in the roaming profile when registered unless otherwi
|
||||
|
||||
Templates can be added to the Backup Profile with PowerShell or WMI using the Set-UevTemplateProfile cmdlet. Templates in the Backup Profile back up these settings to the Settings Storage Location in a special Device name directory. Specified settings are backed up to this location.
|
||||
|
||||
Templates designated BackupOnly include settings specific to that device that should not be synchronized unless explicitly restored. These settings are stored in the same device-specific settings package location on the settings storage location as the Backedup Settings. These templates have a special identifier embedded in the template that specifies they should be part of this profile.
|
||||
Templates designated BackupOnly include settings specific to that device that shouldn't be synchronized unless explicitly restored. These settings are stored in the same device-specific settings package location on the settings storage location as the Backedup Settings. These templates have a special identifier embedded in the template that specifies they should be part of this profile.
|
||||
|
||||
**Settings packages location within the Settings Storage Location template**
|
||||
|
||||
@ -90,10 +90,10 @@ Restoring a user’s device restores the currently registered Template’s setti
|
||||
|
||||
- **Automatic restore**
|
||||
|
||||
If the user’s UE-V settings storage path, domain, and Computer name match the current user then all of the settings for that user are synchronized, with only the latest settings applied. If a user logs on to a new device for the first time and these criteria are met, the settings data is applied to that device.
|
||||
If the user’s UE-V settings storage path, domain, and Computer name match the current user then all of the settings for that user are synchronized, with only the latest settings applied. If a user signs in to a new device for the first time and these criteria are met, the settings data is applied to that device.
|
||||
|
||||
**Note**
|
||||
Accessibility and Windows Desktop settings require the user to re-logon to Windows to be applied.
|
||||
Accessibility and Windows Desktop settings require the user to sign in again to Windows to be applied.
|
||||
|
||||
|
||||
|
||||
@ -104,7 +104,7 @@ Restoring a user’s device restores the currently registered Template’s setti
|
||||
## Restore Application and Windows Settings to Original State
|
||||
|
||||
|
||||
WMI and Windows PowerShell commands let you restore application and Windows settings to the settings values that were on the computer the first time that the application started after the UE-V service was enabled. This restoring action is performed on a per-application or Windows settings basis. The settings are restored the next time that the application runs, or the settings are restored when the user logs on to the operating system.
|
||||
WMI and Windows PowerShell commands let you restore application and Windows settings to the settings values that were on the computer the first time that the application started after the UE-V service was enabled. This restoring action is performed on a per-application or Windows settings basis. The settings are restored the next time that the application runs, or the settings are restored when the user signs in to the operating system.
|
||||
|
||||
**To restore application settings and Windows settings with Windows PowerShell for UE-V**
|
||||
|
||||
|
@ -37,7 +37,7 @@ Administrators can still define which user-customized application settings can s
|
||||
|
||||
### Upgrading from UE-V 1.0 to the in-box version of UE-V is blocked
|
||||
|
||||
Version 1.0 of UE-V used Offline Files (Client Side Caching) for settings synchronization and pinned the UE-V sync folder to be available when the network was offline, however, this technology was removed in UE-V 2.x. As a result, UE-V 1.0 users are blocked from upgrading to UE-V for Windows 10, version 1607.
|
||||
Version 1.0 of UE-V used Offline Files (Client-Side Caching) for settings synchronization and pinned the UE-V sync folder to be available when the network was offline, however, this technology was removed in UE-V 2.x. As a result, UE-V 1.0 users are blocked from upgrading to UE-V for Windows 10, version 1607.
|
||||
|
||||
WORKAROUND: Remove the UE-V 1.0 sync folder from the Offline Files configuration and then upgrade to the in-box version of UE-V for Windows, version 1607 release.
|
||||
|
||||
@ -55,13 +55,13 @@ WORKAROUND: To resolve this problem, run the application by selecting one of the
|
||||
|
||||
### Unpredictable results when both Office 2010 and Office 2013 are installed on the same device
|
||||
|
||||
When a user has both Office 2010 and Office 2013 installed, any common settings between the two versions of Office are roamed by UE-V. This could cause the Office 2010 package size to be quite large or result in unpredictable conflicts with 2013, particularly if Office 365 is used.
|
||||
When a user has both Office 2010 and Office 2013 installed, any common settings between the two versions of Office are roamed by UE-V. This could cause the Office 2010 package size to be large or result in unpredictable conflicts with 2013, particularly if Office 365 is used.
|
||||
|
||||
WORKAROUND: Install only one version of Office or limit which settings are synchronized by UE-V.
|
||||
|
||||
### Uninstall and re-install of Windows 8 applications reverts settings to initial state
|
||||
### Uninstallation and reinstallation of Windows 8 applications reverts settings to initial state
|
||||
|
||||
While using UE-V settings synchronization for a Windows 8 application, if the user uninstalls the application and then reinstalls the application, the application’s settings revert to their default values. This happens because the uninstall removes the local (cached) copy of the application’s settings but does not remove the local UE-V settings package. When the application is reinstalled and launched, UE-V gather the application settings that were reset to the application defaults and then uploads the default settings to the central storage location. Other computers running the application then download the default settings. This behavior is identical to the behavior of desktop applications.
|
||||
While using UE-V settings synchronization for a Windows 8 application, if the user uninstalls the application and then reinstalls the application, the application’s settings revert to their default values. This result happens because the uninstall removes the local (cached) copy of the application’s settings but does not remove the local UE-V settings package. When the application is reinstalled and launched, UE-V gathers the application settings that were reset to the application defaults and then uploads the default settings to the central storage location. Other computers running the application then download the default settings. This behavior is identical to the behavior of desktop applications.
|
||||
|
||||
WORKAROUND: None.
|
||||
|
||||
@ -85,7 +85,7 @@ WORKAROUND: Use folder redirection or some other technology to ensure that any f
|
||||
|
||||
### Long Settings Storage Paths could cause an error
|
||||
|
||||
Keep settings storage paths as short as possible. Long paths could prevent resolution or synchronization. UE-V uses the Settings storage path as part of the calculated path to store settings. That path is calculated in the following way: settings storage path + “settingspackages” + package dir (template ID) + package name (template ID) + .pkgx. If that calculated path exceeds 260 characters, package storage will fail and generate the following error message in the UE-V operational event log:
|
||||
Keep settings storage paths as short as possible. Long paths could prevent resolution or synchronization. UE-V uses the Settings storage path as part of the calculated path to store settings. That path is calculated in the following way: settings storage path + "settingspackages" + package dir (template ID) + package name (template ID) + .pkgx. If that calculated path exceeds 260 characters, package storage will fail and generate the following error message in the UE-V operational event log:
|
||||
|
||||
\[boost::filesystem::copy\_file: The system cannot find the path specified\]
|
||||
|
||||
@ -95,7 +95,7 @@ WORKAROUND: None.
|
||||
|
||||
### Some operating system settings only roam between like operating system versions
|
||||
|
||||
Operating system settings for Narrator and currency characters specific to the locale (i.e. language and regional settings) will only roam across like operating system versions of Windows. For example, currency characters will not roam between Windows 7 and Windows 8.
|
||||
Operating system settings for Narrator and currency characters specific to the locale (that is, language and regional settings) will only roam across like operating system versions of Windows. For example, currency characters will not roam between Windows 7 and Windows 8.
|
||||
|
||||
WORKAROUND: None
|
||||
|
||||
|
@ -45,7 +45,7 @@ Specifies the settings you can configure when joining a device to a domain, incl
|
||||
| --- | --- | --- |
|
||||
| Account | string | Account to use to join computer to domain |
|
||||
| AccountOU | Enter the full path for the organizational unit. For example: OU=testOU,DC=domain,DC=Domain,DC=com. | Name of organizational unit for the computer account |
|
||||
| ComputerName | Specify a unique name for the domain-joined computers using %RAND:x%, where x is an integer less than 15 digits long, or using %SERIAL% characters in the name.</br></br>ComputerName is a string with a maximum length of 15 bytes of content:</br></br>- ComputerName can use ASCII characters (1 byte each) and/or multi-byte characters such as Kanji, so long as you do not exceed 15 bytes of content.</br></br>- ComputerName cannot use spaces or any of the following characters: \{ | \} ~ \[ \\ \] ^ ' : ; < = > ? @ ! " \# $ % ` \( \) + / . , \* &, or contain any spaces.</br></br>- ComputerName cannot use some non-standard characters, such as emoji.</br></br>Computer names that cannot be validated through the DnsValidateName function cannot be used, for example, computer names that only contain numbers (0-9). For more information, see the [DnsValidateName function](https://go.microsoft.com/fwlink/?LinkId=257040). | Specifies the name of the Windows device (computer name on PCs) |
|
||||
| ComputerName | Specify a unique name for the domain-joined computers using %RAND:x%, where x is an integer that includes fewer than 15 digits, or using %SERIAL% characters in the name.</br></br>ComputerName is a string with a maximum length of 15 bytes of content:</br></br>- ComputerName can use ASCII characters (1 byte each) and/or multi-byte characters such as Kanji, so long as you do not exceed 15 bytes of content.</br></br>- ComputerName cannot use spaces or any of the following characters: \{ | \} ~ \[ \\ \] ^ ' : ; < = > ? @ ! " \# $ % ` \( \) + / . , \* &, or contain any spaces.</br></br>- ComputerName cannot use some non-standard characters, such as emoji.</br></br> Computer names that cannot be validated through the DnsValidateName function cannot be used, for example, computer names that only contain numbers (0-9). For more information, see the [DnsValidateName function](https://go.microsoft.com/fwlink/?LinkId=257040). | Specifies the name of the Windows device (computer name on PCs) |
|
||||
| DomainName | string (cannot be empty) | Specify the name of the domain that the device will join |
|
||||
| Password | string (cannot be empty) | Corresponds to the password of the user account that's authorized to join the computer account to the domain. |
|
||||
|
||||
@ -56,6 +56,6 @@ Use these settings to add local user accounts to the device.
|
||||
| Setting | Value | Description |
|
||||
| --- | --- | --- |
|
||||
| UserName | string (cannot be empty) | Specify a name for the local user account |
|
||||
| HomeDir | string (cannot be ampty) | Specify the path of the home directory for the user |
|
||||
| HomeDir | string (cannot be empty) | Specify the path of the home directory for the user |
|
||||
| Password | string (cannot be empty) | Specify the password for the user account |
|
||||
| UserGroup | string (cannot be empty) | Specify the local user group for the user |
|
||||
|
@ -27,7 +27,7 @@ Use for settings related to Maps.
|
||||
|
||||
## ChinaVariantWin10
|
||||
|
||||
Use **ChinaVariantWin10** to specify that the Windows device is intended to ship in China. When set to **True**, maps approved by the State Bureau of Surveying and Mapping in China are used, which are obtained from a server located in China.
|
||||
Use **ChinaVariantWin10** to specify that the Windows device is intended to ship in China. When set to **True**, maps approved by the State Bureau of Surveying and Mapping in China are used. These maps are obtained from a server located in China.
|
||||
|
||||
This customization may result in different maps, servers, or other configuration changes on the device.
|
||||
|
||||
@ -38,7 +38,7 @@ Use to store map data on an SD card.
|
||||
|
||||
Map data is used by the Maps application and the map control for third-party applications. This data can be store on an SD card, which provides the advantage of saving internal memory space for user data and allows the user to download more offline map data. Microsoft recommends enabling the **UseExternalStorage** setting on devices that have less than 8 GB of user storage and an SD card slot.
|
||||
|
||||
You can use **UseExternalStorage** whether or not you include an SD card with preloaded map data on the phone. If set to **True**, the OS only allows the user to download offline maps when an SD card is present. If an SD card is not present, users can still view and cache maps, but they will not be able to download a region of offline maps until an SD card is inserted.
|
||||
You can use **UseExternalStorage** whether or not you include an SD card with preloaded map data on the phone. If set to **True**, the OS only allows the user to download offline maps when an SD card is present. If no SD card is present, users can view and cache maps, but they can't download a region of offline maps until an SD card is inserted.
|
||||
|
||||
If set to **False**, map data will always be stored on the internal data partition of the device.
|
||||
|
||||
@ -47,4 +47,4 @@ If set to **False**, map data will always be stored on the internal data partiti
|
||||
|
||||
## UseSmallerCache
|
||||
|
||||
Do not use.
|
||||
Don't use this setting.
|
||||
|
@ -27,20 +27,20 @@ Use to configure settings to personalize a PC.
|
||||
|
||||
## DeployDesktopImage
|
||||
|
||||
Deploy a jpg, jpeg or png image to the device to be used as desktop image. If you have a local file and want to embed it into the package being deployed, you configure this setting and [DesktopImageUrl](#desktopimageurl).
|
||||
Deploy a .jpg, .jpeg, or .png image to the device to be used as a desktop image. If you have a local file and want to embed it into the package being deployed, you configure this setting and [DesktopImageUrl](#desktopimageurl).
|
||||
|
||||
When using **DeployDesktopImage** and [DeployLockScreenImageFile](#deploylockscreenimage, the file names need to be different.
|
||||
|
||||
## DeployLockScreenImage
|
||||
|
||||
Deploy a jpg, jpeg or png image to the device to be used as lock screen image. If you have a local file and want to embed it into the package being deployed, you configure this setting and [LockScreenImageUrl](#lockscreenimageurl).
|
||||
Deploy a .jpg, .jpeg, or .png image to the device to be used as lock screen image. If you have a local file and want to embed it into the package being deployed, you configure this setting and [LockScreenImageUrl](#lockscreenimageurl).
|
||||
|
||||
When using [DeployDesktopImage](#deploydesktopimage) and **DeployLockScreenImageFile**, the file names need to be different.
|
||||
|
||||
## DesktopImageUrl
|
||||
|
||||
Specify a jpg, jpeg or png image to be used as desktop image. This setting can take a http or https url to a remote image to be downloaded or a file url to a local image. If you have a local file and want to embed it into the package being deployed, you also set [DeployDesktopImage](#deploydesktopimage).
|
||||
Specify a .jpg, .jpeg, or .png image to be used as desktop image. This setting can take an HTTP or HTTPS URL to a remote image to be downloaded or a file URL to a local image. If you have a local file and want to embed it into the package being deployed, you also set [DeployDesktopImage](#deploydesktopimage).
|
||||
|
||||
## LockScreenImageUrl
|
||||
|
||||
Specify a jpg, jpeg or png image to be used as Lock Screen Image. This setting can take a http or https Url to a remote image to be downloaded or a file Url to an existing local image. If you have a local file and want to embed it into the package being deployed, you also set [DeployLockScreenImage](#deploylockscreenimage).
|
||||
Specify a .jpg, .jpeg, or .png image to be used as Lock Screen Image. This setting can take an HTTP or HTTPS URL to a remote image to be downloaded or a file URL to an existing local image. If you have a local file and want to embed it into the package being deployed, you also set [DeployLockScreenImage](#deploylockscreenimage).
|
||||
|
@ -30,7 +30,7 @@ ms.reviewer:
|
||||
|
||||
Desktop Analytics reports are powered by diagnostic data not included in the Basic level.
|
||||
|
||||
In Windows 10, version 1709, we introduced a new feature: "Limit Enhanced diagnostic data to the minimum required by Windows Analytics". When enabled, this feature limits the operating system diagnostic data events included in the Enhanced level to only those described below. Note that the Enhanced level also includes limited crash reports, which are not described below. For more information on the Enhanced level, see [Configure Windows diagnostic data in your organization](configure-windows-diagnostic-data-in-your-organization.md).
|
||||
In Windows 10, version 1709, we introduced a new feature: "Limit Enhanced diagnostic data to the minimum required by Windows Analytics". When enabled, this feature limits the operating system diagnostic data events included in the Enhanced level to only the events described below. The Enhanced level also includes limited crash reports, which are not described below. For more information on the Enhanced level, see [Configure Windows diagnostic data in your organization](configure-windows-diagnostic-data-in-your-organization.md).
|
||||
|
||||
With the retirement of Windows Analytics, this policy will continue to be supported by Desktop Analytics, but will not include Office related diagnostic data.
|
||||
|
||||
@ -48,7 +48,7 @@ The following fields are available:
|
||||
- **GhostCount_Sum:** Total number of instances where the application stopped responding
|
||||
- **HandleCountAtExit_Sum:** Total handle count for a process when it exits
|
||||
- **HangCount_Max:** Maximum number of hangs detected
|
||||
- **HangCount_Sum:** Total number of application hangs detected
|
||||
- **HangCount_Sum:** Total number of application hangs that are detected
|
||||
- **HardFaultCountAtExit_Sum:** Total number of hard page faults detected for a process when it exits
|
||||
- **HeartbeatCount:** Heartbeats logged for this summary
|
||||
- **HeartbeatSuspendedCount:** Heartbeats logged for this summary where the process was suspended
|
||||
@ -68,7 +68,7 @@ The following fields are available:
|
||||
- **WriteSizeInKBAtExit_Sum:** Total size of IO writes for a process when it exited
|
||||
|
||||
## Microsoft.Office.TelemetryEngine.IsPreLaunch
|
||||
Applicable for Office UWP applications. This event is fired when an office application is initiated for the first-time post upgrade/install from the store. This is part of basic diagnostic data, used to track whether a particular session is launch session or not.
|
||||
Applicable for Office UWP applications. This event is fired when an Office application is initiated for the first-time post upgrade/install from the store. It's part of basic diagnostic data. It's used to track whether a particular session is a launch session or not.
|
||||
|
||||
- **appVersionBuild:** Third part of the version *.*.XXXXX.*
|
||||
- **appVersionMajor:** First part of the version X.*.*.*
|
||||
@ -77,10 +77,10 @@ Applicable for Office UWP applications. This event is fired when an office appli
|
||||
- **SessionID:** ID of the session
|
||||
|
||||
## Microsoft.Office.SessionIdProvider.OfficeProcessSessionStart
|
||||
This event sends basic information upon the start of a new Office session. This is used to count the number of unique sessions seen on a given device. This is used as a heartbeat event to ensure that the application is running on a device or not. In addition, it serves as a critical signal for overall application reliability.
|
||||
This event sends basic information upon the start of a new Office session. It's used to count the number of unique sessions seen on a given device. The event is used as a heartbeat event to ensure that the application is running on a device. In addition, it serves as a critical signal for overall application reliability.
|
||||
|
||||
- **AppSessionGuid:** ID of the session which maps to the process of the application
|
||||
- **processSessionId:** ID of the session which maps to the process of the application
|
||||
- **AppSessionGuid:** ID of the session that maps to the process of the application
|
||||
- **processSessionId:** ID of the session that maps to the process of the application
|
||||
|
||||
## Microsoft.Office.TelemetryEngine.SessionHandOff
|
||||
Applicable to Win32 Office applications. This event helps us understand whether there was a new session created to handle a user-initiated file open event. It is a critical diagnostic information that is used to derive reliability signal and ensure that the application is working as expected.
|
||||
@ -89,7 +89,7 @@ Applicable to Win32 Office applications. This event helps us understand whether
|
||||
- **appVersionMajor:** First part of the version X.*.*.*
|
||||
- **appVersionMinor:** Second part of the version *.X.*.*
|
||||
- **appVersionRev:** Fourth part of the version *.*.*.XXXXX
|
||||
- **childSessionID:** Id of the session that was created to handle the user initiated file open
|
||||
- **childSessionID:** ID of the session that was created to handle the user initiated file open
|
||||
- **parentSessionId:** ID of the session that was already running
|
||||
|
||||
## Microsoft.Office.CorrelationMetadata.UTCCorrelationMetadata
|
||||
@ -102,15 +102,15 @@ Collects Office metadata through UTC to compare with equivalent data collected t
|
||||
- **appVersionMajor:** First part of the version X.*.*.*
|
||||
- **appVersionMinor:** Second part of the version *.X.*.*
|
||||
- **appVersionRevision:** Fourth part of the version *.*.*.XXXXX
|
||||
- **audienceGroup:** Is this part of the insiders or production
|
||||
- **audienceGroup:** Is this group part of the insiders or production?
|
||||
- **audienceId:** ID of the audience setting
|
||||
- **channel:** Are you part of Semi annual channel or Semi annual channel-Targeted?
|
||||
- **deviceClass:** Is this a desktop or a mobile?
|
||||
- **deviceClass:** Is this device a desktop device or a mobile device?
|
||||
- **impressionId:** What features were available to you in this session
|
||||
- **languageTag:** Language of the app
|
||||
- **officeUserID:** A unique identifier tied to the office installation on a particular device.
|
||||
- **osArchitecture:** Is the machine 32 bit or 64 bit?
|
||||
- **osEnvironment:** Is this a win32 app or a UWP app?
|
||||
- **osEnvironment:** Is this app a win32 app or a UWP app?
|
||||
- **osVersionString:** Version of the OS
|
||||
- **sessionID:** ID of the session
|
||||
|
||||
@ -131,7 +131,7 @@ This event is fired when the telemetry engine within an office application is re
|
||||
- **appVersionMajor:** First part of the version X.*.*.*
|
||||
- **appVersionMinor:** Second part of the version *.X.*.*
|
||||
- **appVersionRev:** Fourth part of the version *.*.*.XXXXX
|
||||
- **officeUserID:** This is an ID of the installation tied to the device. It does not map to a particular user
|
||||
- **officeUserID:** ID of the installation tied to the device. It does not map to a particular user
|
||||
- **SessionID:** ID of the session
|
||||
|
||||
## Microsoft.Office.TelemetryEngine.FirstProcessed
|
||||
@ -141,7 +141,7 @@ This event is fired when the telemetry engine within an office application has p
|
||||
- **appVersionMajor:** First part of the version X.*.*.*
|
||||
- **appVersionMinor:** Second part of the version *.X.*.*
|
||||
- **appVersionRev:** Fourth part of the version *.*.*.XXXXX
|
||||
- **officeUserID:** This is an ID of the installation tied to the device. It does not map to a particular user
|
||||
- **officeUserID:** ID of the installation tied to the device. It does not map to a particular user
|
||||
- **SessionID:** ID of the session
|
||||
|
||||
## Microsoft.Office.TelemetryEngine.FirstRuleRequest
|
||||
@ -151,7 +151,7 @@ This event is fired when the telemetry engine within an office application has r
|
||||
- **appVersionMajor:** First part of the version X.*.*.*
|
||||
- **appVersionMinor:** Second part of the version *.X.*.*
|
||||
- **appVersionRev:** Fourth part of the version *.*.*.XXXXX
|
||||
- **officeUserID:** This is an ID of the installation tied to the device. It does not map to a particular user
|
||||
- **officeUserID:** ID of the installation tied to the device. It does not map to a particular user
|
||||
- **SessionID:** ID of the session
|
||||
|
||||
## Microsoft.Office.TelemetryEngine.Init
|
||||
@ -161,18 +161,18 @@ This event is fired when the telemetry engine within an office application has b
|
||||
- **appVersionMajor:** First part of the version X.*.*.*
|
||||
- **appVersionMinor:** Second part of the version *.X.*.*
|
||||
- **appVersionRev:** Fourth part of the version *.*.*.XXXXX
|
||||
- **officeUserID:** This is an ID of the installation tied to the device. It does not map to a particular user
|
||||
- **officeUserID:** ID of the installation tied to the device. It does not map to a particular user
|
||||
- **SessionID:** ID of the session
|
||||
|
||||
## Microsoft.Office.TelemetryEngine.Resume
|
||||
This event is fired when the application resumes from sleep state. Used for understanding whether there are issues in the application life-cycle.
|
||||
This event is fired when the application resumes from sleep state. Used for understanding whether there are issues in the application life cycle.
|
||||
|
||||
- **appVersionBuild:** Third part of the version *.*.XXXXX.*
|
||||
- **appVersionMajor:** First part of the version X.*.*.*
|
||||
- **appVersionMinor:** Second part of the version *.X.*.*
|
||||
- **appVersionRev:** Fourth part of the version *.*.*.XXXXX
|
||||
- **maxSequenceIdSeen:** How many events from this session have seen so far?
|
||||
- **officeUserID:** This is an ID of the installation tied to the device. It does not map to a particular user
|
||||
- **officeUserID:** ID of the installation tied to the device. It does not map to a particular user
|
||||
- **rulesSubmittedBeforeResume:** How many events were submitted before the process was resumed?
|
||||
- **SessionID:** ID of the session
|
||||
|
||||
@ -183,7 +183,7 @@ This event is fired when the telemetry engine within an office application fails
|
||||
- **appVersionMajor:** First part of the version X.*.*.*
|
||||
- **appVersionMinor:** Second part of the version *.X.*.*
|
||||
- **appVersionRev:** Fourth part of the version *.*.*.XXXXX
|
||||
- **officeUserID:** This is an ID of the installation tied to the device. It does not map to a particular user
|
||||
- **officeUserID:** ID of the installation tied to the device. It does not map to a particular user
|
||||
- **SessionID:** ID of the session
|
||||
|
||||
## Microsoft.Office.TelemetryEngine.RuleRequestFailedDueToClientOffline
|
||||
@ -193,7 +193,7 @@ This event is fired when the telemetry engine within an office application fails
|
||||
- **appVersionMajor:** First part of the version X.*.*.*
|
||||
- **appVersionMinor:** Second part of the version *.X.*.*
|
||||
- **appVersionRev:** Fourth part of the version *.*.*.XXXXX
|
||||
- **officeUserID:** This is an ID of the installation tied to the device. It does not map to a particular user
|
||||
- **officeUserID:** ID of the installation tied to the device. It does not map to a particular user
|
||||
- **SessionID:** ID of the session
|
||||
|
||||
## Microsoft.Office.TelemetryEngine.ShutdownComplete
|
||||
@ -204,7 +204,7 @@ This event is fired when the telemetry engine within an office application has p
|
||||
- **appVersionMinor:** Second part of the version *.X.*.*
|
||||
- **appVersionRev:** Fourth part of the version *.*.*.XXXXX
|
||||
- **maxSequenceIdSeen:** How many events from this session have seen so far?
|
||||
- **officeUserID:** This is an ID of the installation tied to the device. It does not map to a particular user
|
||||
- **officeUserID:** ID of the installation tied to the device. It does not map to a particular user
|
||||
- **rulesSubmittedBeforeResume:** How many events were submitted before the process was resumed?
|
||||
- **SessionID:** ID of the session
|
||||
|
||||
@ -215,7 +215,7 @@ This event is fired when the telemetry engine within an office application been
|
||||
- **appVersionMajor:** First part of the version X.*.*.*
|
||||
- **appVersionMinor:** Second part of the version *.X.*.*
|
||||
- **appVersionRev:** Fourth part of the version *.*.*.XXXXX
|
||||
- **officeUserID:** This is an ID of the installation tied to the device. It does not map to a particular user
|
||||
- **officeUserID:** ID of the installation tied to the device. It does not map to a particular user
|
||||
- **rulesSubmittedBeforeResume:** How many events were submitted before the process was resumed?
|
||||
- **SessionID:** ID of the session
|
||||
|
||||
@ -227,26 +227,26 @@ This event is fired when the telemetry engine within an office application has p
|
||||
- **appVersionMinor:** Second part of the version *.X.*.*
|
||||
- **appVersionRev:** Fourth part of the version *.*.*.XXXXX
|
||||
- **maxSequenceIdSeen:** How many events from this session have seen so far?
|
||||
- **officeUserID:** This is an ID of the installation tied to the device. It does not map to a particular user
|
||||
- **officeUserID:** ID of the installation tied to the device. It does not map to a particular user
|
||||
- **rulesSubmittedBeforeResume:** How many events were submitted before the process was resumed?
|
||||
- **SessionID:** ID of the session
|
||||
- **SuspendType:** Type of suspend
|
||||
|
||||
## Microsoft.Office.TelemetryEngine.SuspendStart
|
||||
This event is fired when the office application suspends as per app life-cycle change. Used for understanding whether there are issues in the application life-cycle.
|
||||
This event is fired when the office application suspends as per app life-cycle change. Used for understanding whether there are issues in the application life cycle.
|
||||
|
||||
- **appVersionBuild:** Third part of the version *.*.XXXXX.*
|
||||
- **appVersionMajor:** First part of the version X.*.*.*
|
||||
- **appVersionMinor:** Second part of the version *.X.*.*
|
||||
- **appVersionRev:** Fourth part of the version *.*.*.XXXXX
|
||||
- **maxSequenceIdSeen:** How many events from this session have seen so far?
|
||||
- **officeUserID:** This is an ID of the installation tied to the device. It does not map to a particular user
|
||||
- **officeUserID:** ID of the installation tied to the device. It does not map to a particular user
|
||||
- **rulesSubmittedBeforeResume:** How many events were submitted before the process was resumed?
|
||||
- **SessionID:** ID of the session
|
||||
- **SuspendType:** Type of suspend
|
||||
|
||||
## Microsoft.OSG.OSS.CredProvFramework.ReportResultStop
|
||||
This event indicates the result of an attempt to authenticate a user with a credential provider. It helps Microsoft to improve logon reliability. Using this event with Desktop Analytics can help organizations monitor and improve logon success for different methods (for example, biometric) on managed devices.
|
||||
This event indicates the result of an attempt to authenticate a user with a credential provider. It helps Microsoft to improve sign-in reliability. Using this event with Desktop Analytics can help organizations monitor and improve sign-in success for different methods (for example, biometric) on managed devices.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -262,11 +262,11 @@ The following fields are available:
|
||||
- **ReturnCode:** Output of the ReportResult function
|
||||
- **SessionId:** Session identifier
|
||||
- **Sign-in error status:** The sign-in error status
|
||||
- **SubStatus:** Sign-in error sub-status
|
||||
- **SubStatus:** Sign-in error substatus
|
||||
- **UserTag:** Count of the number of times a user has selected a provider
|
||||
|
||||
## Microsoft.Windows.Kernel.Power.OSStateChange
|
||||
This event denotes the transition between operating system states (e.g., On, Off, Sleep, etc.). By using this event with Desktop Analytics, organizations can use this to monitor reliability and performance of managed devices
|
||||
This event denotes the transition between operating system states (On, Off, Sleep, etc.). By using this event with Desktop Analytics, organizations can monitor reliability and performance of managed devices.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -281,10 +281,10 @@ The following fields are available:
|
||||
- **EnergyChangeV2Flags:** Flags for disambiguating EnergyChangeV2 context
|
||||
- **EventSequence:** A sequential number used to evaluate the completeness of the data
|
||||
- **LastStateTransition:** ID of the last operating system state transition
|
||||
- **LastStateTransitionSub:** ID of the last operating system sub-state transition
|
||||
- **LastStateTransitionSub:** ID of the last operating system substate transition
|
||||
- **StateDurationMS:** Number of milliseconds spent in the last operating system state
|
||||
- **StateTransition:** ID of the operating system state the system is transitioning to
|
||||
- **StateTransitionSub:** ID of the operating system sub-state the system is transitioning to
|
||||
- **StateTransitionSub:** ID of the operating system substate the system is transitioning to
|
||||
- **TotalDurationMS:** Total time (in milliseconds) spent in all states since the last boot
|
||||
- **TotalUptimeMS:** Total time (in milliseconds) the device was in Up or Running states since the last boot
|
||||
- **TransitionsToOn:** Number of transitions to the Powered On state since the last boot
|
||||
@ -305,7 +305,7 @@ Sends details about any error codes detected during a failed sign-in.
|
||||
The following fields are available:
|
||||
|
||||
- **ntsStatus:** The NTSTATUS error code status returned from an attempted sign-in
|
||||
- **ntsSubstatus:** The NTSTATUS error code sub-status returned from an attempted sign-in
|
||||
- **ntsSubstatus:** The NTSTATUS error code substatus returned from an attempted sign-in
|
||||
|
||||
## Microsoft.Windows.Security.Biometrics.Service.BioServiceActivityCapture
|
||||
Indicates that a biometric capture was compared to known templates
|
||||
@ -327,7 +327,7 @@ The following field is available:
|
||||
- **ticksSinceBoot:** Duration of boot event (milliseconds)
|
||||
|
||||
## Microsoft.Windows.Shell.Desktop.LogonFramework.AllLogonTasks
|
||||
This event summarizes the logon procedure to help Microsoft improve performance and reliability. By using this event with Desktop Analytics organizations can help identify logon problems on managed devices.
|
||||
This event summarizes the logon procedure to help Microsoft improve performance and reliability. By using this event with Desktop Analytics, organizations can help identify logon problems on managed devices.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -341,7 +341,7 @@ The following fields are available:
|
||||
- **wilActivity:** Indicates errors in the task to help Microsoft improve reliability.
|
||||
|
||||
## Microsoft.Windows.Shell.Desktop.LogonFramework.LogonTask
|
||||
This event describes system tasks which are part of the user logon sequence and helps Microsoft to improve reliability.
|
||||
This event describes system tasks that are part of the user logon sequence and helps Microsoft to improve reliability.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -359,7 +359,7 @@ For a device subject to Windows Information Protection policy, learning events a
|
||||
The following fields are available:
|
||||
|
||||
- **actiontype:** Indicates what type of resource access the app was attempting (for example, opening a local document vs. a network resource) when it encountered a policy boundary. Useful for Windows Information Protection administrators to tune policy rules.
|
||||
- **appIdType:** Based on the type of application, this indicates what type of app rule a Windows Information Protection administrator would need to create for this app.
|
||||
- **appIdType:** Based on the type of application, this field indicates what type of app rule a Windows Information Protection administrator would need to create for this app.
|
||||
- **appname:** App that triggered the event
|
||||
- **status:** Indicates whether errors occurred during WIP learning events
|
||||
|
||||
@ -397,11 +397,11 @@ The following fields are available:
|
||||
- **MonitorWidth:** Number of horizontal pixels in the application host monitor resolution
|
||||
- **MouseInputSec:** Total number of seconds during which there was mouse input
|
||||
- **NewProcessCount:** Number of new processes contributing to the aggregate
|
||||
- **PartATransform_AppSessionGuidToUserSid:** Flag which influences how other parts of the event are constructed
|
||||
- **PartATransform_AppSessionGuidToUserSid:** Flag that influences how other parts of the event are constructed
|
||||
- **PenInputSec:** Total number of seconds during which there was pen input
|
||||
- **SpeechRecognitionSec:** Total number of seconds of speech recognition
|
||||
- **SummaryRound:** Incrementing number indicating the round (batch) being summarized
|
||||
- **TargetAsId:** Flag which influences how other parts of the event are constructed
|
||||
- **TargetAsId:** Flag that influences how other parts of the event are constructed
|
||||
- **TotalUserOrDisplayActiveDurationMS:** Total time the user or the display was active (in milliseconds)
|
||||
- **TouchInputSec:** Total number of seconds during which there was touch input
|
||||
- **UserActiveDurationMS:** Total time that the user was active including all input methods
|
||||
@ -415,7 +415,7 @@ The following fields are available:
|
||||
## Revisions
|
||||
|
||||
### PartA_UserSid removed
|
||||
A previous revision of this list stated that a field named PartA_UserSid was a member of the event Microsoft.Windows.LogonController.LogonAndUnlockSubmit. This was incorrect. The list has been updated to reflect that no such field is present in the event.
|
||||
A previous revision of this list stated that a field named PartA_UserSid was a member of the event Microsoft.Windows.LogonController.LogonAndUnlockSubmit. This statement was incorrect. The list has been updated to reflect that no such field is present in the event.
|
||||
|
||||
### Office events added
|
||||
In Windows 10, version 1809 (also applies to versions 1709 and 1803 starting with [KB 4462932](https://support.microsoft.com/help/4462932/windows-10-update-kb4462932) and [KB 4462933](https://support.microsoft.com/help/4462933/windows-10-update-kb4462933) respectively), 16 events were added, describing Office app launch and availability. These events were added to improve the precision of Office data in Windows Analytics.
|
||||
|
@ -42,7 +42,7 @@ Most diagnostic events contain a header of common data:
|
||||
|
||||
| Category Name | Examples |
|
||||
| - | - |
|
||||
| Common Data | Information that is added to most diagnostic events, if relevant and available:<br><ul><li>OS name, version, build, and [locale](https://msdn.microsoft.com/library/windows/desktop/dd318716.aspx)</li><li>User ID -- a unique identifier associated with the user's Microsoft Account (if one is used) or local account. The user's Microsoft Account identifier is not collected from devices configured to send Basic diagnostic data</li><li>Xbox UserID</li><li>Environment from which the event was logged -- Application ID of app or component that logged the event, Session GUID. Used to track events over a given period of time such the period an app is running or between boots of the OS.</li><li>The diagnostic event name, Event ID, [ETW](https://msdn.microsoft.com/library/windows/desktop/bb968803.aspx) opcode, version, schema signature, keywords, and flags</li><li>HTTP header information, including the IP address. This IP address is the source address that’s provided by the network packet header and received by the diagnostics ingestion service.</li><li>Various IDs that are used to correlate and sequence related events together.</li><li>Device ID. This is not the user provided device name, but an ID that is unique for that device.</li><li>Device class -- Desktop, Server, or Mobile</li><li>Event collection time</li><li>Diagnostic level -- Basic or Full, Sample level -- for sampled data, what sample level is this device opted into</li></ul> |
|
||||
| Common Data | Information that is added to most diagnostic events, if relevant and available:<br><ul><li>OS name, version, build, and [locale](https://msdn.microsoft.com/library/windows/desktop/dd318716.aspx)</li><li>User ID - a unique identifier associated with the user's Microsoft Account (if one is used) or local account. The user's Microsoft Account identifier is not collected from devices configured to send Basic diagnostic data</li><li>Xbox UserID</li><li>Environment from which the event was logged - Application ID of app or component that logged the event, Session GUID. Used to track events over a given period of time such the period an app is running or between boots of the OS.</li><li>The diagnostic event name, Event ID, [ETW](https://msdn.microsoft.com/library/windows/desktop/bb968803.aspx) opcode, version, schema signature, keywords, and flags</li><li>HTTP header information, including the IP address. This IP address is the source address that’s provided by the network packet header and received by the diagnostics ingestion service.</li><li>Various IDs that are used to correlate and sequence related events together.</li><li>Device ID. This ID is not the user provided device name, but an ID that is unique for that device.</li><li>Device class - Desktop, Server, or Mobile</li><li>Event collection time</li><li>Diagnostic level - Basic or Full, Sample level - for sampled data, what sample level is this device opted into</li></ul> |
|
||||
|
||||
## Device, Connectivity, and Configuration data
|
||||
|
||||
@ -50,38 +50,38 @@ This type of data includes details about the device, its configuration and conne
|
||||
|
||||
| Category Name | Examples |
|
||||
| - | - |
|
||||
| Device properties | Information about the OS and device hardware, such as:<br><ul><li> OS - version name, Edition</li><li>Installation type, subscription status, and genuine OS status</li><li>Processor architecture, speed, number of cores, manufacturer, and model</li><li>OEM details --manufacturer, model, and serial number<li>Device identifier and Xbox serial number</li><li>Firmware/BIOS -- type, manufacturer, model, and version</li><li>Memory -- total memory, video memory, speed, and how much memory is available after the device has reserved memory</li><li>Storage -- total capacity and disk type</li><li>Battery -- charge capacity and InstantOn support</li><li>Hardware chassis type, color, and form factor</li><li>Is this a virtual machine?</li></ul> |
|
||||
| Device capabilities | Information about the specific device capabilities such as:<br/><ul><li>Camera -- whether the device has a front facing, a rear facing camera, or both.</li><li>Touch screen -- does the device include a touch screen? If so, how many hardware touch points are supported?</li><li>Processor capabilities -- CompareExchange128, LahfSahf, NX, PrefetchW, and SSE2</li><li>Trusted Platform Module (TPM) – whether present and what version</li><li>Virtualization hardware -- whether an IOMMU is present, SLAT support, is virtualization enabled in the firmware</li><li>Voice – whether voice interaction is supported and the number of active microphones</li><li>Number of displays, resolutions, DPI</li><li>Wireless capabilities</li><li>OEM or platform face detection</li><li>OEM or platform video stabilization and quality level set</li><li>Advanced Camera Capture mode (HDR vs. LowLight), OEM vs. platform implementation, HDR probability, and Low Light probability</li></ul> |
|
||||
| Device preferences and settings | Information about the device settings and user preferences such as:<br><ul><li>User Settings – System, Device, Network & Internet, Personalization, Cortana, Apps, Accounts, Time & Language, Gaming, Ease of Access, Privacy, Update & Security</li><li>User-provided device name</li><li>Whether device is domain-joined, or cloud-domain joined (i.e. part of a company-managed network)</li><li>Hashed representation of the domain name</li><li>MDM (mobile device management) enrollment settings and status</li><li>BitLocker, Secure Boot, encryption settings, and status</li><li>Windows Update settings and status</li><li>Developer Unlock settings and status</li><li>Default app choices</li><li>Default browser choice</li><li>Default language settings for app, input, keyboard, speech, and display</li><li>App store update settings</li><li>Enterprise OrganizationID, Commercial ID</li></ul> |
|
||||
| Device peripherals | Information about the device peripherals such as:<br><ul><li>Peripheral name, device model, class, manufacturer and description</li><li>Peripheral device state, install state, and checksum</li><li>Driver name, package name, version, and manufacturer</li><li>HWID - A hardware vendor defined ID to match a device to a driver [INF file](https://msdn.microsoft.com/windows/hardware/drivers/install/hardware-ids)</li><li>Driver state, problem code, and checksum</li><li>Whether driver is kernel mode, signed, and image size</li></ul> |
|
||||
| Device network info | Information about the device network configuration such as:<br><ul><li>Network system capabilities</li><li>Local or Internet connectivity status</li><li>Proxy, gateway, DHCP, DNS details and addresses</li><li>Paid or free network</li><li>Wireless driver is emulated or not</li><li>Access point mode capable</li><li>Access point manufacturer, model, and MAC address</li><li>WDI Version</li><li>Name of networking driver service</li><li>Wi-Fi Direct details</li><li>Wi-Fi device hardware ID and manufacturer</li><li>Wi-Fi scan attempt counts and item counts</li><li>Mac randomization is supported/enabled or not</li><li>Number of spatial streams and channel frequencies supported</li><li>Manual or Auto Connect enabled</li><li>Time and result of each connection attempt</li><li>Airplane mode status and attempts</li><li>Interface description provided by the manufacturer</li><li>Data transfer rates</li><li>Cipher algorithm</li><li>Mobile Equipment ID (IMEI) and Mobile Country Code (MCCO)</li><li>Mobile operator and service provider name</li><li>Available SSIDs and BSSIDs</li><li>IP Address type -- IPv4 or IPv6</li><li>Signal Quality percentage and changes</li><li>Hotspot presence detection and success rate</li><li>TCP connection performance</li><li>Miracast device names</li><li>Hashed IP address</li></ul>
|
||||
| Device properties | Information about the OS and device hardware, such as:<br><ul><li> OS - version name, Edition</li><li>Installation type, subscription status, and genuine OS status</li><li>Processor architecture, speed, number of cores, manufacturer, and model</li><li>OEM details - manufacturer, model, and serial number<li>Device identifier and Xbox serial number</li><li>Firmware/BIOS - type, manufacturer, model, and version</li><li>Memory - total memory, video memory, speed, and how much memory is available after the device has reserved memory</li><li>Storage - total capacity and disk type</li><li>Battery - charge capacity and InstantOn support</li><li>Hardware chassis type, color, and form factor</li><li>Is this machine a virtual machine?</li></ul> |
|
||||
| Device capabilities | Information about the specific device capabilities such as:<br/><ul><li>Camera - whether the device has a front facing, a rear facing camera, or both.</li><li>Touch screen - does the device include a touch screen? If so, how many hardware touch points are supported?</li><li>Processor capabilities - CompareExchange128, LahfSahf, NX, PrefetchW, and SSE2</li><li>Trusted Platform Module (TPM) – whether present and what version</li><li>Virtualization hardware - whether an IOMMU is present, SLAT support, is virtualization enabled in the firmware</li><li>Voice – whether voice interaction is supported and the number of active microphones</li><li>Number of displays, resolutions, DPI</li><li>Wireless capabilities</li><li>OEM or platform face detection</li><li>OEM or platform video stabilization and quality level set</li><li>Advanced Camera Capture mode (HDR vs. LowLight), OEM vs. platform implementation, HDR probability, and Low Light probability</li></ul> |
|
||||
| Device preferences and settings | Information about the device settings and user preferences such as:<br><ul><li>User Settings – System, Device, Network & Internet, Personalization, Cortana, Apps, Accounts, Time & Language, Gaming, Ease of Access, Privacy, Update & Security</li><li>User-provided device name</li><li>Whether device is domain-joined, or cloud-domain joined (that is, part of a company-managed network)</li><li>Hashed representation of the domain name</li><li>MDM (mobile device management) enrollment settings and status</li><li>BitLocker, Secure Boot, encryption settings, and status</li><li>Windows Update settings and status</li><li>Developer Unlock settings and status</li><li>Default app choices</li><li>Default browser choice</li><li>Default language settings for app, input, keyboard, speech, and display</li><li>App store update settings</li><li>Enterprise OrganizationID, Commercial ID</li></ul> |
|
||||
| Device peripherals | Information about the device peripherals such as:<br><ul><li>Peripheral name, device model, class, manufacturer, and description</li><li>Peripheral device state, install state, and checksum</li><li>Driver name, package name, version, and manufacturer</li><li>HWID - A hardware vendor defined ID to match a device to a driver [INF file](https://msdn.microsoft.com/windows/hardware/drivers/install/hardware-ids)</li><li>Driver state, problem code, and checksum</li><li>Whether driver is kernel mode, signed, and image size</li></ul> |
|
||||
| Device network info | Information about the device network configuration such as:<br><ul><li>Network system capabilities</li><li>Local or Internet connectivity status</li><li>Proxy, gateway, DHCP, DNS details, and addresses</li><li>Paid or free network</li><li>Wireless driver is emulated or not</li><li>Access point mode capable</li><li>Access point manufacturer, model, and MAC address</li><li>WDI Version</li><li>Name of networking driver service</li><li>Wi-Fi Direct details</li><li>Wi-Fi device hardware ID and manufacturer</li><li>Wi-Fi scan attempt counts and item counts</li><li>Mac randomization is supported/enabled or not</li><li>Number of spatial streams and channel frequencies supported</li><li>Manual or Auto Connect enabled</li><li>Time and result of each connection attempt</li><li>Airplane mode status and attempts</li><li>Interface description provided by the manufacturer</li><li>Data transfer rates</li><li>Cipher algorithm</li><li>Mobile Equipment ID (IMEI) and Mobile Country Code (MCCO)</li><li>Mobile operator and service provider name</li><li>Available SSIDs and BSSIDs</li><li>IP Address type - IPv4 or IPv6</li><li>Signal Quality percentage and changes</li><li>Hotspot presence detection and success rate</li><li>TCP connection performance</li><li>Miracast device names</li><li>Hashed IP address</li></ul>
|
||||
|
||||
## Product and Service Usage data
|
||||
|
||||
This type of data includes details about the usage of the device, operating system, applications and services.
|
||||
This type of data includes details about the usage of the device, operating system, applications, and services.
|
||||
|
||||
| Category Name | Examples |
|
||||
| - | - |
|
||||
| App usage | Information about Windows and application usage such as:<ul><li>OS component and app feature usage</li><li>User navigation and interaction with app and Windows features. This could potentially include user input, such as name of a new alarm set, user menu choices, or user favorites.</li><li>Time of and count of app/component launches, duration of use, session GUID, and process ID</li><li>App time in various states – running foreground or background, sleeping, or receiving active user interaction</li><li>User interaction method and duration – whether and length of time user used the keyboard, mouse, pen, touch, speech, or game controller</li><li>Cortana launch entry point/reason</li><li>Notification delivery requests and status</li><li>Apps used to edit images and videos</li><li>SMS, MMS, VCard, and broadcast message usage statistics on primary or secondary line</li><li>Incoming and Outgoing calls and Voicemail usage statistics on primary or secondary line</li><li>Emergency alerts are received or displayed statistics</li><li>Content searches within an app</li><li>Reading activity -- bookmarking used, print used, layout changed</li></ul>|
|
||||
| App or product state | Information about Windows and application state such as:<ul><li>Start Menu and Taskbar pins</li><li>Online/Offline status</li><li>App launch state –- with deep-link such as Groove launched with an audio track to play, or share contract such as MMS launched to share a picture.</li><li>Personalization impressions delivered</li><li>Whether the user clicked or hovered on UI controls or hotspots</li><li>User feedback Like or Dislike or rating was provided</li><li>Caret location or position within documents and media files -- how much of a book has been read in a single session or how much of a song has been listened to.</li></ul>|
|
||||
| App usage | Information about Windows and application usage such as:<ul><li>OS component and app feature usage</li><li>User navigation and interaction with app and Windows features. This information could include user input, such as the name of a new alarm set, user menu choices, or user favorites.</li><li>Time of and count of app/component launches, duration of use, session GUID, and process ID</li><li>App time in various states – running foreground or background, sleeping, or receiving active user interaction</li><li>User interaction method and duration – whether and length of time user used the keyboard, mouse, pen, touch, speech, or game controller</li><li>Cortana launch entry point/reason</li><li>Notification delivery requests and status</li><li>Apps used to edit images and videos</li><li>SMS, MMS, VCard, and broadcast message usage statistics on primary or secondary line</li><li>Incoming and Outgoing calls and Voicemail usage statistics on primary or secondary line</li><li>Emergency alerts are received or displayed statistics</li><li>Content searches within an app</li><li>Reading activity - bookmarking used, print used, layout changed</li></ul>|
|
||||
| App or product state | Information about Windows and application state such as:<ul><li>Start Menu and Taskbar pins</li><li>Online/Offline status</li><li>App launch state –- with deep-link such as Groove launched with an audio track to play, or share contract such as MMS launched to share a picture.</li><li>Personalization impressions delivered</li><li>Whether the user clicked or hovered on UI controls or hotspots</li><li>User feedback Like or Dislike or rating was provided</li><li>Caret location or position within documents and media files - how much of a book has been read in a single session or how much of a song has been listened to.</li></ul>|
|
||||
| Login properties | <ul><li>Login success or failure</li><li>Login sessions and state</li></ul>|
|
||||
|
||||
|
||||
## Product and Service Performance data
|
||||
|
||||
This type of data includes details about the health of the device, operating system, apps and drivers.
|
||||
This type of data includes details about the health of the device, operating system, apps, and drivers.
|
||||
|
||||
| Category Name | Description and Examples |
|
||||
| - | - |
|
||||
|Device health and crash data | Information about the device and software health such as:<br><ul><li>Error codes and error messages, name and ID of the app, and process reporting the error</li><li>DLL library predicted to be the source of the error -- xyz.dll</li><li>System generated files -- app or product logs and trace files to help diagnose a crash or hang</li><li>System settings such as registry keys</li><li>User generated files – .doc, .ppt, .csv files where they are indicated as a potential cause for a crash or hang</li><li>Details and counts of abnormal shutdowns, hangs, and crashes</li><li>Crash failure data – OS, OS component, driver, device, 1st and 3rd party app data</li><li>Crash and Hang dumps<ul><li>The recorded state of the working memory at the point of the crash.</li><li>Memory in use by the kernel at the point of the crash.</li><li>Memory in use by the application at the point of the crash.</li><li>All the physical memory used by Windows at the point of the crash.</li><li>Class and function name within the module that failed.</li></li></ul> |
|
||||
|Device performance and reliability data | Information about the device and software performance such as:<br><ul><li>User Interface interaction durations -- Start Menu display times, browser tab switch times, app launch and switch times, and Cortana and search performance and reliability.</li><li>Device on/off performance -- Device boot, shutdown, power on/off, lock/unlock times, and user authentication times (fingerprint and face recognition durations).</li><li>In-app responsiveness -- time to set alarm, time to fully render in-app navigation menus, time to sync reading list, time to start GPS navigation, time to attach picture MMS, and time to complete a Microsoft Store transaction.</li><li>User input responsiveness – onscreen keyboard invocation times for different languages, time to show auto-complete words, pen or touch latencies, latency for handwriting recognition to words, Narrator screen reader responsiveness, and CPU score.</li><li>UI and media performance and glitches/smoothness -- video playback frame rate, audio glitches, animation glitches (stutter when bringing up Start), graphics score, time to first frame, play/pause/stop/seek responsiveness, time to render PDF, dynamic streaming of video from OneDrive performance</li><li>Disk footprint -- Free disk space, out of memory conditions, and disk score.</li><li>Excessive resource utilization – components impacting performance or battery life through high CPU usage during different screen and power states</li><li>Background task performance -- download times, Windows Update scan duration, Microsoft Defender Antivirus scan times, disk defrag times, mail fetch times, service startup and state transition times, and time to index on-device files for search results</li><li>Peripheral and devices -- USB device connection times, time to connect to a wireless display, printing times, network availability and connection times (time to connect to Wi-Fi, time to get an IP address from DHCP etc.), smart card authentication times, automatic brightness environmental response times</li><li>Device setup -- first setup experience times (time to install updates, install apps, connect to network etc.), time to recognize connected devices (printer and monitor), and time to setup Microsoft Account.</li><li>Power and Battery life – power draw by component (Process/CPU/GPU/Display), hours of screen off time, sleep state transition details, temperature and thermal throttling, battery drain in a power state (screen off or screen on), processes and components requesting power use during screen off, auto-brightness details, time device is plugged into AC vs. battery, battery state transitions</li><li>Service responsiveness - Service URI, operation, latency, service success/error codes, and protocol.</li><li>Diagnostic heartbeat – regular signal to validate the health of the diagnostics system</li></ul>|
|
||||
|Movies|Information about movie consumption functionality on the device. This isn't intended to capture user viewing, listening or habits.<br><ul><li>Video Width, height, color pallet, encoding (compression) type, and encryption type</li><li>Instructions for how to stream content for the user -- the smooth streaming manifest of chunks of content files that must be pieced together to stream the content based on screen resolution and bandwidth</li><li>URL for a specific two second chunk of content if there is an error</li><li>Full screen viewing mode details|
|
||||
|Music & TV|Information about music and TV consumption on the device. This isn't intended to capture user viewing, listening or habits.<br><ul><li>Service URL for song being downloaded from the music service – collected when an error occurs to facilitate restoration of service</li><li>Content type (video, audio, surround audio)</li><li>Local media library collection statistics -- number of purchased tracks, number of playlists</li><li>Region mismatch -- User OS Region, and Xbox Live region</li></ul>|
|
||||
|Reading|Information about reading consumption functionality on the device. This isn't intended to capture user viewing, listening or habits.<br><ul><li>App accessing content and status and options used to open a Microsoft Store book</li><li>Language of the book</li><li>Time spent reading content</li><li>Content type and size details</li></ul>|
|
||||
|Photos App|Information about photos usage on the device. This isn't intended to capture user viewing, listening or habits.<br><ul><li>File source data -- local, SD card, network device, and OneDrive</li><li>Image & video resolution, video length, file sizes types and encoding</li><li>Collection view or full screen viewer use and duration of view</li></ul></ul>|
|
||||
|On-device file query | Information about local search activity on the device such as: <ul><li>Kind of query issued and index type (ConstraintIndex, SystemIndex)</li><li>Number of items requested and retrieved</li><li>File extension of search result user interacted with</li><li>Launched item kind, file extension, index of origin, and the App ID of the opening app.</li><li>Name of process calling the indexer and time to service the query.</li><li>A hash of the search scope (file, Outlook, OneNote, IE history) </li><li>The state of the indices (fully optimized, partially optimized, being built)</li></ul> |
|
||||
|Purchasing| Information about purchases made on the device such as:<br><ul><li>Product ID, edition ID and product URI</li><li>Offer details -- price</li><li>Order requested date/time</li><li>Store client type -- web or native client</li><li>Purchase quantity and price</li><li>Payment type -- credit card type and PayPal</li></ul> |
|
||||
|Entitlements | Information about entitlements on the device such as:<br><ul><li>Service subscription status and errors</li><li>DRM and license rights details -- Groove subscription or OS volume license</li><li>Entitlement ID, lease ID, and package ID of the install package</li><li>Entitlement revocation</li><li>License type (trial, offline vs online) and duration</li><li>License usage session</li></ul> |
|
||||
|Device health and crash data | Information about the device and software health such as:<br><ul><li>Error codes and error messages, name and ID of the app, and process reporting the error</li><li>DLL library predicted to be the source of the error - xyz.dll</li><li>System-generated files - app or product logs and trace files to help diagnose a crash or hang</li><li>System settings such as registry keys</li><li>User-generated files – .doc, .ppt, .csv files where they are indicated as a potential cause for a crash or hang</li><li>Details and counts of abnormal shutdowns, hangs, and crashes</li><li>Crash failure data – OS, OS component, driver, device, 1st and 3rd party app data</li><li>Crash and Hang dumps<ul><li>The recorded state of the working memory at the point of the crash.</li><li>Memory in use by the kernel at the point of the crash.</li><li>Memory in use by the application at the point of the crash.</li><li>All the physical memory used by Windows at the point of the crash.</li><li>Class and function name within the module that failed.</li></li></ul> |
|
||||
|Device performance and reliability data | Information about the device and software performance such as:<br><ul><li>User Interface interaction durations - Start Menu display times, browser tab switch times, app launch and switch times, and Cortana and search performance and reliability.</li><li>Device on/off performance - Device boot, shutdown, power on/off, lock/unlock times, and user authentication times (fingerprint and face recognition durations).</li><li>In-app responsiveness - time to set alarm, time to fully render in-app navigation menus, time to sync reading list, time to start GPS navigation, time to attach picture MMS, and time to complete a Microsoft Store transaction.</li><li>User input responsiveness – onscreen keyboard invocation times for different languages, time to show autocomplete words, pen or touch latencies, latency for handwriting recognition to words, Narrator screen reader responsiveness, and CPU score.</li><li>UI and media performance and glitches/smoothness - video playback frame rate, audio glitches, animation glitches (stutter when bringing up Start), graphics score, time to first frame, play/pause/stop/seek responsiveness, time to render PDF, dynamic streaming of video from OneDrive performance</li><li>Disk footprint - Free disk space, out of memory conditions, and disk score.</li><li>Excessive resource utilization – components impacting performance or battery life through high CPU usage during different screen and power states</li><li>Background task performance - download times, Windows Update scan duration, Microsoft Defender Antivirus scan times, disk defrag times, mail fetch times, service startup and state transition times, and time to index on-device files for search results</li><li>Peripheral and devices - USB device connection times, time to connect to a wireless display, printing times, network availability, and connection times (time to connect to Wi-Fi, time to get an IP address from DHCP, and so on), smart card authentication times, automatic brightness environmental response times</li><li>Device setup - first setup experience times (time to install updates, install apps, connect to network etc.), time to recognize connected devices (printer and monitor), and time to setup Microsoft Account.</li><li>Power and Battery life – power draw by component (Process/CPU/GPU/Display), hours of screen off time, sleep state transition details, temperature and thermal throttling, battery drain in a power state (screen off or screen on), processes and components requesting power use during screen off, autobrightness details, time device is plugged into AC vs. battery, battery state transitions</li><li>Service responsiveness - Service URI, operation, latency, service success/error codes, and protocol.</li><li>Diagnostic heartbeat – regular signal to validate the health of the diagnostics system</li></ul>|
|
||||
|Movies|Information about movie consumption functionality on the device. This information isn't intended to capture user viewing, listening, or habits.<br><ul><li>Video Width, height, color pallet, encoding (compression) type, and encryption type</li><li>Instructions for how to stream content for the user - the smooth streaming manifest of chunks of content files that must be pieced together to stream the content based on screen resolution and bandwidth</li><li>URL for a specific two-second chunk of content if there is an error</li><li>Full screen viewing mode details|
|
||||
|Music & TV|Information about music and TV consumption on the device. This information isn't intended to capture user viewing, listening, or habits.<br><ul><li>Service URL for song being downloaded from the music service – collected when an error occurs to facilitate restoration of service</li><li>Content type (video, audio, surround audio)</li><li>Local media library collection statistics - number of purchased tracks, number of playlists</li><li>Region mismatch - User OS Region, and Xbox Live region</li></ul>|
|
||||
|Reading|Information about reading consumption functionality on the device. This information isn't intended to capture user viewing, listening, or habits.<br><ul><li>App accessing content and status and options used to open a Microsoft Store book</li><li>Language of the book</li><li>Time spent reading content</li><li>Content type and size details</li></ul>|
|
||||
|Photos App|Information about photos usage on the device. This information isn't intended to capture user viewing, listening, or habits.<br><ul><li>File source data - local, SD card, network device, and OneDrive</li><li>Image & video resolution, video length, file sizes types and encoding</li><li>Collection view or full screen viewer use and duration of view</li></ul></ul>|
|
||||
|On-device file query | Information about local search activity on the device such as: <ul><li>Type of query issued and index type (ConstraintIndex, SystemIndex)</li><li>Number of items requested and retrieved</li><li>File extension of search result user interacted with</li><li>Launched item kind, file extension, index of origin, and the App ID of the opening app.</li><li>Name of process calling the indexer and time to service the query.</li><li>A hash of the search scope (file, Outlook, OneNote, IE history) </li><li>The state of the indices (fully optimized, partially optimized, being built)</li></ul> |
|
||||
|Purchasing| Information about purchases made on the device such as: <br><ul><li>Product ID, edition ID, and product URI</li><li>Offer details - price</li><li>Order requested date/time</li><li>Store client type - web or native client</li><li>Purchase quantity and price</li><li>Payment type - credit card type and PayPal</li></ul> |
|
||||
|Entitlements | Information about entitlements on the device such as:<br><ul><li>Service subscription status and errors</li><li>DRM and license rights details - Groove subscription or OS volume license</li><li>Entitlement ID, lease ID, and package ID of the install package</li><li>Entitlement revocation</li><li>License type (trial, offline versus online) and duration</li><li>License usage session</li></ul> |
|
||||
|
||||
## Software Setup and Inventory data
|
||||
|
||||
@ -90,7 +90,7 @@ This type of data includes software installation and update information on the d
|
||||
| Category Name | Data Examples |
|
||||
| - | - |
|
||||
| Installed Applications and Install History | Information about apps, drivers, update packages, or OS components installed on the device such as:<br><ul><li>App, driver, update package, or component’s Name, ID, or Package Family Name</li><li>Product, SKU, availability, catalog, content, and Bundle IDs</li><li>OS component, app or driver publisher, language, version and type (Win32 or UWP)</li><li>Install date, method, and install directory, count of install attempts</li><li>MSI package code and product code</li><li>Original OS version at install time</li><li>User or administrator or mandatory installation/update</li><li>Installation type – clean install, repair, restore, OEM, retail, upgrade, and update</li></ul> |
|
||||
| Device update information | Information about Windows Update such as:<br><ul><li>Update Readiness analysis of device hardware, OS components, apps, and drivers (progress, status, and results)</li><li>Number of applicable updates, importance, type</li><li>Update download size and source -- CDN or LAN peers</li><li>Delay upgrade status and configuration</li><li>OS uninstall and rollback status and count</li><li>Windows Update server and service URL</li><li>Windows Update machine ID</li><li>Windows Insider build details</li></ul>
|
||||
| Device update information | Information about Windows Update such as:<br><ul><li>Update Readiness analysis of device hardware, OS components, apps, and drivers (progress, status, and results)</li><li>Number of applicable updates, importance, type</li><li>Update download size and source - CDN or LAN peers</li><li>Delay upgrade status and configuration</li><li>OS uninstall and rollback status and count</li><li>Windows Update server and service URL</li><li>Windows Update machine ID</li><li>Windows Insider build details</li></ul>
|
||||
|
||||
## Browsing History data
|
||||
|
||||
@ -98,7 +98,7 @@ This type of data includes details about web browsing in the Microsoft browsers.
|
||||
|
||||
| Category Name | Description and Examples |
|
||||
| - | - |
|
||||
| Microsoft browser data | Information about Address bar and search box performance on the device such as:<ul><li>Text typed in address bar and search box</li><li>Text selected for Ask Cortana search</li><li>Service response time </li><li>Auto-completed text if there was an auto-complete</li><li>Navigation suggestions provided based on local history and favorites</li><li>Browser ID</li><li>URLs (which may include search terms)</li><li>Page title</li></ul>|
|
||||
| Microsoft browser data | Information about Address bar and search box performance on the device such as:<ul><li>Text typed in address bar and search box</li><li>Text selected for Ask Cortana search</li><li>Service response time </li><li>Autocompleted text if there was an autocomplete</li><li>Navigation suggestions provided based on local history and favorites</li><li>Browser ID</li><li>URLs (which may include search terms)</li><li>Page title</li></ul>|
|
||||
|
||||
|
||||
## Inking Typing and Speech Utterance data
|
||||
@ -107,4 +107,4 @@ This type of data gathers details about the voice, inking, and typing input feat
|
||||
|
||||
| Category Name | Description and Examples |
|
||||
| - | - |
|
||||
| Voice, inking, and typing | Information about voice, inking and typing features such as:<br><ul><li>Type of pen used (highlighter, ball point, pencil), pen color, stroke height and width, and how long it is used</li><li>Pen gestures (click, double click, pan, zoom, rotate)</li><li>Palm Touch x,y coordinates</li><li>Input latency, missed pen signals, number of frames, strokes, first frame commit time, sample rate</li><li>Ink strokes written, text before and after the ink insertion point, recognized text entered, Input language - processed to remove identifiers, sequencing information, and other data (such as email addresses and numeric values) which could be used to reconstruct the original content or associate the input to the user.</li><li>Text input from Windows Mobile on-screen keyboards except from password fields and private sessions - processed to remove identifiers, sequencing information, and other data (such as email addresses, and numeric values) which could be used to reconstruct the original content or associate the input to the user.</li><li>Text of speech recognition results -- result codes and recognized text</li><li>Language and model of the recognizer, System Speech language</li><li>App ID using speech features</li><li>Whether user is known to be a child</li><li>Confidence and Success/Failure of speech recognition</li></ul> |
|
||||
| Voice, inking, and typing | Information about voice, inking, and typing features such as:<br><ul><li>Type of pen used (highlighter, ball point, pencil), pen color, stroke height and width, and how long it is used</li><li>Pen gestures (click, double-click, pan, zoom, rotate)</li><li>Palm Touch x,y coordinates</li><li>Input latency, missed pen signals, number of frames, strokes, first frame commit time, sample rate</li><li>Ink strokes written, text before and after the ink insertion point, recognized text entered, Input language - processed to remove identifiers, sequencing information, and other data (such as email addresses and numeric values) which could be used to reconstruct the original content or associate the input to the user.</li><li>Text input from Windows Mobile on-screen keyboards except from password fields and private sessions - processed to remove identifiers, sequencing information, and other data (such as email addresses, and numeric values) which could be used to reconstruct the original content or associate the input to the user.</li><li>Text of speech recognition results - result codes and recognized text</li><li>Language and model of the recognizer, System Speech language</li><li>App ID using speech features</li><li>Whether user is known to be a child</li><li>Confidence and Success/Failure of speech recognition</li></ul> |
|
||||
|
@ -28,7 +28,7 @@ Applies to:
|
||||
|
||||
Microsoft uses Windows diagnostic data to keep Windows secure and up-to-date, troubleshoot problems, and make product improvements. For users who have turned on "Tailored experiences", it can also be used to offer you personalized tips, ads, and recommendations to enhance Microsoft products and services for your needs. This article describes all types of diagnostic data collected by Windows at the Full level (inclusive of data collected at Basic), with comprehensive examples of data we collect per each type. For additional, detailed technical descriptions of Basic data items, see [Windows 10, version 20H2 required diagnostic events and fields](https://docs.microsoft.com/windows/configuration/basic-level-windows-diagnostic-events-and-fields).
|
||||
|
||||
In addition, this article provides references to equivalent definitions for the data types and examples from [ISO/IEC 19944:2017 Information technology -- Cloud computing -- Cloud services and devices: Data flow, data categories and data use](https://www.iso.org/standard/66674.html). Each data type also has a Data Use statement, for diagnostics and for Tailored experiences on the device, using the terms as defined by the standard. These Data Use statements define the purposes for which Microsoft processes each type of Windows diagnostic data, using a uniform set of definitions referenced at the end of this document and based on the ISO standard. Reference to the ISO standard provides additional clarity about the information collected, and allows easy comparison with other services or guidance that also references the standard.
|
||||
In addition, this article provides references to equivalent definitions for the data types and examples from [ISO/IEC 19944:2017 Information technology - Cloud computing - Cloud services and devices: Data flow, data categories, and data use](https://www.iso.org/standard/66674.html). Each data type also has a Data Use statement, for diagnostics and for Tailored experiences on the device, using the terms as defined by the standard. These Data Use statements define the purposes for which Microsoft processes each type of Windows diagnostic data, using a uniform set of definitions referenced at the end of this document and based on the ISO standard. Reference to the ISO standard provides additional clarity about the information collected, and allows easy comparison with other services or guidance that also references the standard.
|
||||
|
||||
The data covered in this article is grouped into the following types:
|
||||
|
||||
@ -52,21 +52,21 @@ Header data supports the use of data associated with all diagnostic events. Ther
|
||||
|
||||
Information that is added to most diagnostic events, if relevant and available:
|
||||
|
||||
- Diagnostic level -- Basic or Full, Sample level -- for sampled data, what sample level is this device opted into (8.2.3.2.4 Observed Usage of the Service Capability)
|
||||
- Diagnostic level - Basic or Full, Sample level - for sampled data, what sample level is this device opted into (8.2.3.2.4 Observed Usage of the Service Capability)
|
||||
- Operating system name, version, build, and locale (8.2.3.2.2 Telemetry data)
|
||||
- Event collection time (8.2.3.2.2 Telemetry data)
|
||||
- User ID -- a unique identifier associated with the user's Microsoft Account (if one is used) or local account. The user's Microsoft Account identifier is not collected from devices configured to send Basic - diagnostic data (8.2.5 Account data)
|
||||
- User ID - a unique identifier associated with the user's Microsoft Account (if one is used) or local account. The user's Microsoft Account identifier is not collected from devices configured to send Basic - diagnostic data (8.2.5 Account data)
|
||||
- Xbox UserID (8.2.5 Account data)
|
||||
- Device ID -- This is not the user provided device name, but an ID that is unique for that device. (8.2.3.2.3 Connectivity data)
|
||||
- Device class -- Desktop, Server, or Mobile (8.2.3.2.3 Connectivity data)
|
||||
- Environment from which the event was logged -- Application ID of app or component that logged the event, Session GUID. Used to track events over a given period of time, such as the amount of time an app is running or between boots of the operating system (8.2.4 Cloud service provider data)
|
||||
- Device ID - This ID is not the user provided device name, but an ID that is unique for that device. (8.2.3.2.3 Connectivity data)
|
||||
- Device class - Desktop, Server, or Mobile (8.2.3.2.3 Connectivity data)
|
||||
- Environment from which the event was logged - Application ID of app or component that logged the event, Session GUID. Used to track events over a given period of time, such as the amount of time an app is running or between boots of the operating system (8.2.4 Cloud service provider data)
|
||||
- Diagnostic event name, Event ID, ETW opcode, version, schema signature, keywords, and flags (8.2.4 Cloud service provider data)
|
||||
- HTTP header information, including the IP address. This IP address is the source address that’s provided by the network packet header and received by the diagnostics ingestion service (8.2.4 Cloud service provider data)
|
||||
- Various IDs that are used to correlate and sequence related events together (8.2.4 Cloud service provider data)
|
||||
|
||||
|
||||
## Device, Connectivity, and Configuration data
|
||||
This type of data includes details about the device, its configuration and connectivity capabilities, and status. Device, Connectivity, and Configuration Data is equivalent to ISO/IEC 19944:2017, 8.2.3.2.3 Connectivity data.
|
||||
This type of data includes details about the device, its configuration and connectivity capabilities, and status. Device, Connectivity, and Configuration data is equivalent to ISO/IEC 19944:2017, 8.2.3.2.3 Connectivity data.
|
||||
|
||||
### Data Use for Device, Connectivity, and Configuration data
|
||||
|
||||
@ -88,41 +88,41 @@ If a user has enabled Tailored experiences on the device, [Pseudonymized](#pseud
|
||||
|
||||
- Data about device properties and capabilities is used to provide tips about how to use or configure the device to get the best performance and user experience.
|
||||
|
||||
- Data about device capabilities, such as whether the device is pen-enabled, is used to recommend (Microsoft and third-party) apps that are appropriate for the device. These may be free or paid apps.
|
||||
- Data about device capabilities, such as whether the device is pen-enabled, is used to recommend (Microsoft and third-party) apps that are appropriate for the device. These apps might be free or paid.
|
||||
|
||||
### Data Description for Device, Connectivity, and Configuration data type
|
||||
|
||||
**Device properties sub-type:** Information about the operating system and device hardware
|
||||
**Device properties subtype:** Information about the operating system and device hardware
|
||||
|
||||
- Operating system - version name, edition
|
||||
- Installation type, subscription status, and genuine operating system status
|
||||
- Processor architecture, speed, number of cores, manufacturer, and model
|
||||
- OEM details --manufacturer, model, and serial number
|
||||
- OEM details - manufacturer, model, and serial number
|
||||
- Device identifier and Xbox serial number
|
||||
- Firmware/BIOS operating system -- type, manufacturer, model, and version
|
||||
- Memory -- total memory, video memory, speed, and how much memory is available after the device has reserved memory
|
||||
- Storage -- total capacity and disk type
|
||||
- Battery -- charge capacity and InstantOn support
|
||||
- Firmware/BIOS operating system - type, manufacturer, model, and version
|
||||
- Memory - total memory, video memory, speed, and how much memory is available after the device has reserved memory
|
||||
- Storage - total capacity and disk type
|
||||
- Battery - charge capacity and InstantOn support
|
||||
- Hardware chassis type, color, and form factor
|
||||
- Is this a virtual machine?
|
||||
- Is this machine a virtual machine?
|
||||
|
||||
**Device capabilities sub-type:** Information about the capabilities of the device
|
||||
**Device capabilities subtype:** Information about the capabilities of the device
|
||||
|
||||
- Camera -- whether the device has a front facing camera, a rear facing camera, or both.
|
||||
- Touch screen -- Whether the device has a touch screen? If yes, how many hardware touch points are supported?
|
||||
- Processor capabilities -- CompareExchange128, LahfSahf, NX, PrefetchW, and SSE2
|
||||
- Trusted Platform Module (TPM) -- whether a TPM exists and if yes, what version
|
||||
- Virtualization hardware -- whether an IOMMU exists, whether it includes SLAT support, and whether virtualization is enabled in the firmware
|
||||
- Voice -- whether voice interaction is supported and the number of active microphones
|
||||
- Camera - whether the device has a front facing camera, a rear facing camera, or both.
|
||||
- Touch screen - Does the device have a touch screen? If yes, how many hardware touch points are supported?
|
||||
- Processor capabilities - CompareExchange128, LahfSahf, NX, PrefetchW, and SSE2
|
||||
- Trusted Platform Module (TPM) - whether a TPM exists and if yes, what version
|
||||
- Virtualization hardware - whether an IOMMU exists, whether it includes SLAT support, and whether virtualization is enabled in the firmware
|
||||
- Voice - whether voice interaction is supported and the number of active microphones
|
||||
- Number of displays, resolutions, and DPI
|
||||
- Wireless capabilities
|
||||
- OEM or platform face detection
|
||||
- OEM or platform video stabilization and quality-level set
|
||||
- Advanced Camera Capture mode (HDR versus Low Light), OEM versus platform implementation, HDR probability, and Low Light probability
|
||||
|
||||
**Device preferences and settings sub-type:** Information about the device settings and user preferences
|
||||
**Device preferences and settings subtype:** Information about the device settings and user preferences
|
||||
|
||||
- User Settings -- System, Device, Network & Internet, Personalization, Cortana, Apps, Accounts, Time & Language, Gaming, Ease of Access, Privacy, Update & Security
|
||||
- User Settings - System, Device, Network & Internet, Personalization, Cortana, Apps, Accounts, Time & Language, Gaming, Ease of Access, Privacy, Update & Security
|
||||
- User-provided device name
|
||||
- Whether device is domain-joined, or cloud-domain joined (for example, part of a company-managed network)
|
||||
- Hashed representation of the domain name
|
||||
@ -136,7 +136,7 @@ If a user has enabled Tailored experiences on the device, [Pseudonymized](#pseud
|
||||
- App store update settings
|
||||
- Enterprise OrganizationID, Commercial ID
|
||||
|
||||
**Device peripherals sub-type:** Information about the peripherals of the device
|
||||
**Device peripherals subtype:** Information about the peripherals of the device
|
||||
|
||||
- Peripheral name, device model, class, manufacturer, and description
|
||||
- Peripheral device state, install state, and checksum
|
||||
@ -145,7 +145,7 @@ If a user has enabled Tailored experiences on the device, [Pseudonymized](#pseud
|
||||
- Driver state, problem code, and checksum
|
||||
- Whether driver is kernel mode, signed, and image size
|
||||
|
||||
**Device network info sub-type:** Information about the device network configuration
|
||||
**Device network info subtype:** Information about the device network configuration
|
||||
|
||||
- Network system capabilities
|
||||
- Local or Internet connectivity status
|
||||
@ -170,7 +170,7 @@ If a user has enabled Tailored experiences on the device, [Pseudonymized](#pseud
|
||||
- Mobile Equipment ID (IMEI) and Mobile Country Code (MCCO)
|
||||
- Mobile operator and service provider name
|
||||
- Available SSIDs and BSSIDs
|
||||
- IP Address type -- IPv4 or IPv6
|
||||
- IP Address type - IPv4 or IPv6
|
||||
- Signal Quality percentage and changes
|
||||
- Hotspot presence detection and success rate
|
||||
- TCP connection performance
|
||||
@ -178,7 +178,7 @@ If a user has enabled Tailored experiences on the device, [Pseudonymized](#pseud
|
||||
- Hashed IP address
|
||||
|
||||
## Product and Service Usage data
|
||||
This type of data includes details about the usage of the device, operating system, applications and services. Product and Service Usage data is equivalent to ISO/IEC 19944:2017, 8.2.3.2.4 Observed Usage of the Service Capability.
|
||||
This type of data includes details about the usage of the device, operating system, applications, and services. Product and Service Usage data is equivalent to ISO/IEC 19944:2017, 8.2.3.2.4 Observed Usage of the Service Capability.
|
||||
|
||||
### Data Use for Product and Service Usage data
|
||||
|
||||
@ -195,16 +195,16 @@ This type of data includes details about the usage of the device, operating syst
|
||||
**With (optional) Tailored experiences:**<br>
|
||||
If a user has enabled Tailored experiences on the device, [pseudonymized](#pseudo) Product and Service Usage data from Windows 10 is used by Microsoft to [personalize](#personalize), [recommend](#recommend), and [offer](#offer) Microsoft products and services to Windows 10 users. Also, if a user has enabled Tailored experiences on the device, [pseudonymized](#pseudo) Product and Service Usage data from Windows 10 is used by Microsoft to [promote](#promote) third-party Windows apps, services, hardware, and peripherals to Windows 10 users. For example:
|
||||
|
||||
- If data shows that a user has not used a particular feature of Windows, we may recommend that the user try that feature.
|
||||
- Data about which apps are most-used on a device is used to provide recommendations for similar or complementary (Microsoft or third-party) apps. These may be free or paid apps.
|
||||
- If data shows that a user has not used a particular feature of Windows, we might recommend that the user try that feature.
|
||||
- Data about which apps are most-used on a device is used to provide recommendations for similar or complementary (Microsoft or third-party) apps. These apps might be free or paid.
|
||||
|
||||
|
||||
### Data Description for Product and Service Usage data type
|
||||
|
||||
**App usage sub-type:** Information about Windows and application usage
|
||||
**App usage subtype:** Information about Windows and application usage
|
||||
|
||||
- Operating system component and app feature usage
|
||||
- User navigation and interaction with app and Windows features. This could potentially include user input, such as name of a new alarm set, user menu choices, or user favorites
|
||||
- User navigation and interaction with app and Windows features. This information could include user input, such as the name of a new alarm set, user menu choices, or user favorites
|
||||
- Time of and count of app and component launches, duration of use, session GUID, and process ID
|
||||
- App time in various states –- running in the foreground or background, sleeping, or receiving active user interaction
|
||||
- User interaction method and duration –- whether the user used a keyboard, mouse, pen, touch, speech, or game controller, and for how long
|
||||
@ -215,9 +215,9 @@ If a user has enabled Tailored experiences on the device, [pseudonymized](#pseud
|
||||
- Incoming and outgoing calls and voicemail usage statistics on primary or secondary lines
|
||||
- Emergency alerts are received or displayed statistics
|
||||
- Content searches within an app
|
||||
- Reading activity -- bookmarked, printed, or had the layout changed
|
||||
- Reading activity - bookmarked, printed, or had the layout changed
|
||||
|
||||
**App or product state sub-type:** Information about Windows and application state
|
||||
**App or product state subtype:** Information about Windows and application state
|
||||
|
||||
- Start Menu and Taskbar pins
|
||||
- Online and offline status
|
||||
@ -225,18 +225,18 @@ If a user has enabled Tailored experiences on the device, [pseudonymized](#pseud
|
||||
- Personalization impressions delivered
|
||||
- Whether the user clicked on, or hovered over, UI controls or hotspots
|
||||
- User provided feedback, such as Like, Dislike or a rating
|
||||
- Caret location or position within documents and media files -- how much has been read in a book in a single session, or how much of a song has been listened to.
|
||||
- Caret location or position within documents and media files - how much has been read in a book in a single session, or how much of a song has been listened to.
|
||||
|
||||
**Purchasing sub-type:** Information about purchases made on the device
|
||||
**Purchasing subtype:** Information about purchases made on the device
|
||||
|
||||
- Product ID, edition ID and product URI
|
||||
- Offer details -- price
|
||||
- Product ID, edition ID, and product URI
|
||||
- Offer details - price
|
||||
- Date and time an order was requested
|
||||
- Microsoft Store client type -- web or native client
|
||||
- Microsoft Store client type - web or native client
|
||||
- Purchase quantity and price
|
||||
- Payment type -- credit card type and PayPal
|
||||
- Payment type - credit card type and PayPal
|
||||
|
||||
**Login properties sub-type:** Information about logins on the device
|
||||
**Login properties subtype:** Information about logins on the device
|
||||
|
||||
- Login success or failure
|
||||
- Login sessions and state
|
||||
@ -259,21 +259,21 @@ If a user has enabled Tailored experiences on the device, [pseudonymized](#pseud
|
||||
|
||||
- Data about battery performance on a device may be used to recommend settings changes that can improve battery performance.
|
||||
- If data shows a device is running low on file storage, we may recommend Windows-compatible cloud storage solutions to free up space.
|
||||
- If data shows the device is experiencing performance issues, we may provide recommendations for Windows apps that can help diagnose or resolve these issues. These may be free or paid apps.
|
||||
- If data shows the device is experiencing performance issues, we may provide recommendations for Windows apps that can help diagnose or resolve these issues. These apps might be free or paid.
|
||||
|
||||
**Microsoft doesn't use crash and hang dump data to [personalize](#personalize), [recommend](#recommend), [offer](#offer), or [promote](#promote) any product or service.**
|
||||
|
||||
### Data Description for Product and Service Performance data type
|
||||
|
||||
**Device health and crash data sub-type:** Information about the device and software health
|
||||
**Device health and crash data subtype:** Information about the device and software health
|
||||
|
||||
- Error codes and error messages, name and ID of the app, and process reporting the error
|
||||
- DLL library predicted to be the source of the error -- for example, xyz.dll
|
||||
- System generated files -- app or product logs and trace files to help diagnose a crash or hang
|
||||
- DLL library predicted to be the source of the error - for example, xyz.dll
|
||||
- System-generated files - app or product logs and trace files to help diagnose a crash or hang
|
||||
- System settings, such as registry keys
|
||||
- User generated files -- files that are indicated as a potential cause for a crash or hang. For example, .doc, .ppt, .csv files
|
||||
- User-generated files - files that are indicated as a potential cause for a crash or hang. For example, .doc, .ppt, .csv files
|
||||
- Details and counts of abnormal shutdowns, hangs, and crashes
|
||||
- Crash failure data -- operating system, operating system component, driver, device, and 1st and 3rd-party app data
|
||||
- Crash failure data - operating system, operating system component, driver, device, and first-party and third-party app data
|
||||
- Crash and hang dumps, including:
|
||||
- The recorded state of the working memory at the point of the crash
|
||||
- Memory in-use by the kernel at the point of the crash.
|
||||
@ -281,43 +281,43 @@ If a user has enabled Tailored experiences on the device, [pseudonymized](#pseud
|
||||
- All the physical memory used by Windows at the point of the crash
|
||||
- Class and function name within the module that failed.
|
||||
|
||||
**Device performance and reliability data sub-type:** Information about the device and software performance
|
||||
**Device performance and reliability data subtype:** Information about the device and software performance
|
||||
|
||||
- User interface interaction durations -- Start menu display times, browser tab switch times, app launch and switch times, and Cortana and Search performance and reliability
|
||||
- Device on and off performance -- Device boot, shutdown, power on and off, lock and unlock times, and user authentication times (fingerprint and face recognition durations)
|
||||
- In-app responsiveness -- time to set alarm, time to fully render in-app navigation menus, time to sync reading list, time to start GPS navigation, time to attach picture MMS, and time to complete a Microsoft Store transaction
|
||||
- User input responsiveness -- onscreen keyboard invocation times for different languages, time to show auto-complete words, pen or touch latencies, latency for handwriting recognition to words, Narrator screen reader responsiveness, and CPU score
|
||||
- UI and media performance and glitches versus smoothness -- video playback frame rate, audio glitches, animation glitches (stutter when bringing up Start), graphics score, time to first frame, play/pause/stop/seek responsiveness, time to render PDF, dynamic streaming of video from OneDrive performance
|
||||
- Disk footprint -- Free disk space, out of memory conditions, and disk score
|
||||
- Excessive resource utilization -- components impacting performance or battery life through high CPU usage during different screen and power states
|
||||
- Background task performance -- download times, Windows Update scan duration, Microsoft Defender Antivirus scan times, disk defrag times, mail fetch times, service startup and state transition times, and time to index on-device files for search results
|
||||
- Peripheral and devices -- USB device connection times, time to connect to a wireless display, printing times, network availability and connection times (time to connect to Wi-Fi, time to get an IP address from DHCP etc.), smart card authentication times, automatic brightness, and environmental response times
|
||||
- Device setup -- first setup experience times (time to install updates, install apps, connect to network, and so on), time to recognize connected devices (printer and monitor), and time to set up a Microsoft Account
|
||||
- Power and Battery life -- power draw by component (Process/CPU/GPU/Display), hours of time the screen is off, sleep state transition details, temperature and thermal throttling, battery drain in a power state (screen off or screen on), processes and components requesting power use while the screen is off, auto-brightness details, time device is plugged into AC versus battery, and battery state transitions
|
||||
- Service responsiveness -- Service URI, operation, latency, service success and error codes, and protocol
|
||||
- Diagnostic heartbeat -- regular signal used to validate the health of the diagnostics system
|
||||
- User interface interaction durations - Start menu display times, browser tab switch times, app launch and switch times, and Cortana and Search performance and reliability
|
||||
- Device on and off performance - Device boot, shutdown, power on and off, lock and unlock times, and user authentication times (fingerprint and face recognition durations)
|
||||
- In-app responsiveness - time to set alarm, time to fully render in-app navigation menus, time to sync reading list, time to start GPS navigation, time to attach picture MMS, and time to complete a Microsoft Store transaction
|
||||
- User input responsiveness - onscreen keyboard invocation times for different languages, time to show autocomplete words, pen or touch latencies, latency for handwriting recognition to words, Narrator screen reader responsiveness, and CPU score
|
||||
- UI and media performance and glitches versus smoothness - video playback frame rate, audio glitches, animation glitches (stutter when bringing up Start), graphics score, time to first frame, play/pause/stop/seek responsiveness, time to render PDF, dynamic streaming of video from OneDrive performance
|
||||
- Disk footprint - Free disk space, out of memory conditions, and disk score
|
||||
- Excessive resource utilization - components impacting performance or battery life through high CPU usage during different screen and power states
|
||||
- Background task performance - download times, Windows Update scan duration, Microsoft Defender Antivirus scan times, disk defrag times, mail fetch times, service startup and state transition times, and time to index on-device files for search results
|
||||
- Peripheral and devices - USB device connection times, time to connect to a wireless display, printing times, network availability and connection times (time to connect to Wi-Fi, time to get an IP address from DHCP etc.), smart card authentication times, automatic brightness, and environmental response times
|
||||
- Device setup - first setup experience times (time to install updates, install apps, connect to network, and so on), time to recognize connected devices (printer and monitor), and time to set up a Microsoft Account
|
||||
- Power and Battery life - power draw by component (Process/CPU/GPU/Display), hours of time the screen is off, sleep state transition details, temperature and thermal throttling, battery drain in a power state (screen off or screen on), processes and components requesting power use while the screen is off, autobrightness details, time device is plugged into AC versus battery, and battery state transitions
|
||||
- Service responsiveness - Service URI, operation, latency, service success and error codes, and protocol
|
||||
- Diagnostic heartbeat - regular signal used to validate the health of the diagnostics system
|
||||
|
||||
**Movies sub-type:** Information about movie consumption functionality on the device
|
||||
**Movies subtype:** Information about movie consumption functionality on the device
|
||||
|
||||
> [!NOTE]
|
||||
> This isn't intended to capture user viewing, listening, or habits.
|
||||
|
||||
- Video Width, height, color palette, encoding (compression) type, and encryption type
|
||||
- Instructions about how to stream content for the user -- the smooth streaming manifest of content file chunks that must be pieced together to stream the content based on screen resolution and bandwidth
|
||||
- Instructions about how to stream content for the user - the smooth streaming manifest of content file chunks that must be pieced together to stream the content based on screen resolution and bandwidth
|
||||
- URL for a specific two-second chunk of content if there is an error
|
||||
- Full-screen viewing mode details
|
||||
|
||||
**Music & TV sub-type:** Information about music and TV consumption on the device
|
||||
**Music & TV subtype:** Information about music and TV consumption on the device
|
||||
|
||||
> [!NOTE]
|
||||
> This isn't intended to capture user viewing, listening, or habits.
|
||||
|
||||
- Service URL for song being downloaded from the music service -- collected when an error occurs to facilitate restoration of service
|
||||
- Service URL for song being downloaded from the music service - collected when an error occurs to facilitate restoration of service
|
||||
- Content type (video, audio, or surround audio)
|
||||
- Local media library collection statistics -- number of purchased tracks and number of playlists
|
||||
- Region mismatch -- User's operating system region and Xbox Live region
|
||||
- Local media library collection statistics - number of purchased tracks and number of playlists
|
||||
- Region mismatch - User's operating system region and Xbox Live region
|
||||
|
||||
**Reading sub-type:** Information about reading consumption functionality on the device
|
||||
**Reading subtype:** Information about reading consumption functionality on the device
|
||||
|
||||
> [!NOTE]
|
||||
> This isn't intended to capture user viewing, listening, or habits.
|
||||
@ -327,42 +327,42 @@ If a user has enabled Tailored experiences on the device, [pseudonymized](#pseud
|
||||
- Time spent reading content
|
||||
- Content type and size details
|
||||
|
||||
**Photos app sub-type:** Information about photos usage on the device
|
||||
**Photos app subtype:** Information about photos usage on the device
|
||||
|
||||
> [!NOTE]
|
||||
> This isn't intended to capture user viewing, listening, or habits.
|
||||
|
||||
- File source data -- local, SD card, network device, and OneDrive
|
||||
- File source data - local, SD card, network device, and OneDrive
|
||||
- Image and video resolution, video length, file sizes types, and encoding
|
||||
- Collection view or full screen viewer use and duration of view
|
||||
|
||||
**On-device file query sub-type:** Information about local search activity on the device
|
||||
**On-device file query subtype:** Information about local search activity on the device
|
||||
|
||||
- Kind of query issued and index type (ConstraintIndex or SystemIndex)
|
||||
- Type of query issued and index type (ConstraintIndex or SystemIndex)
|
||||
- Number of items requested and retrieved
|
||||
- File extension of search result with which the user interacted
|
||||
- Launched item type, file extension, index of origin, and the App ID of the opening app
|
||||
- Name of process calling the indexer and the amount of time to service the query
|
||||
- A hash of the search scope (file, Outlook, OneNote, or IE history). The state of the indices (fully optimized, partially optimized, or being built)
|
||||
|
||||
**Entitlements sub-type:** Information about entitlements on the device
|
||||
**Entitlements subtype:** Information about entitlements on the device
|
||||
|
||||
- Service subscription status and errors
|
||||
- DRM and license rights details -- Groove subscription or operating system volume license
|
||||
- DRM and license rights details - Groove subscription or operating system volume license
|
||||
- Entitlement ID, lease ID, and package ID of the install package
|
||||
- Entitlement revocation
|
||||
- License type (trial, offline versus online) and duration
|
||||
- License usage session
|
||||
|
||||
## Software Setup and Inventory data
|
||||
This type of data includes software installation and update information on the device. Software Setup and Inventory Data is a sub-type of ISO/IEC 19944:2017 8.2.3.2.4 Observed Usage of the Service Capability.
|
||||
This type of data includes software installation and update information on the device. Software Setup and Inventory Data is a subtype of ISO/IEC 19944:2017 8.2.3.2.4 Observed Usage of the Service Capability.
|
||||
|
||||
### Data Use for Software Setup and Inventory data
|
||||
|
||||
**For Diagnostics:**<br>
|
||||
[Pseudonymized](#pseudo) Software Setup and Inventory data from Windows 10 is used by Microsoft to [provide](#provide) and [improve](#improve) Windows 10 and related Microsoft product and services. For example:
|
||||
|
||||
- Data about the specific drivers that are installed on a device is used to understand whether there are any hardware or driver compatibility issues which should block or delay a Windows update.
|
||||
- Data about the specific drivers that are installed on a device is used to understand whether there are any hardware or driver compatibility issues that should block or delay a Windows update.
|
||||
- Data about when a download starts and finishes on a device is used to understand and address download problems.
|
||||
- Data about the specific Microsoft Store apps that are installed on a device is used to determine which app updates to provide to the device.
|
||||
- Data about the antimalware installed on a device is used to understand malware transmissions vectors.
|
||||
@ -374,7 +374,7 @@ If a user has enabled Tailored experiences on the device, [pseudonymized](#pseud
|
||||
|
||||
### Data Description for Software Setup and Inventory data type
|
||||
|
||||
**Installed applications and install history sub-type:** Information about apps, drivers, update packages, or operating system components installed on the device
|
||||
**Installed applications and install history subtype:** Information about apps, drivers, update packages, or operating system components installed on the device
|
||||
|
||||
- App, driver, update package, or component’s Name, ID, or Package Family Name
|
||||
- Product, SKU, availability, catalog, content, and Bundle IDs
|
||||
@ -383,13 +383,13 @@ If a user has enabled Tailored experiences on the device, [pseudonymized](#pseud
|
||||
- MSI package and product code
|
||||
- Original operating system version at install time
|
||||
- User, administrator, or mandatory installation or update
|
||||
- Installation type -- clean install, repair, restore, OEM, retail, upgrade, or update
|
||||
- Installation type - clean install, repair, restore, OEM, retail, upgrade, or update
|
||||
|
||||
**Device update information sub-type:** Information about apps, drivers, update packages, or operating system components installed on the device
|
||||
**Device update information subtype:** Information about apps, drivers, update packages, or operating system components installed on the device
|
||||
|
||||
- Update Readiness analysis of device hardware, operating system components, apps, and drivers (progress, status, and results)
|
||||
- Number of applicable updates, importance, and type
|
||||
- Update download size and source -- CDN or LAN peers
|
||||
- Update download size and source - CDN or LAN peers
|
||||
- Delay upgrade status and configuration
|
||||
- Operating system uninstall and rollback status and count
|
||||
- Windows Update server and service URL
|
||||
@ -397,7 +397,7 @@ If a user has enabled Tailored experiences on the device, [pseudonymized](#pseud
|
||||
- Windows Insider build details
|
||||
|
||||
## Browsing History data
|
||||
This type of data includes details about web browsing in the Microsoft browsers. Browsing History data is equivalent to ISO/IEC 19944:2017 8.2.3.2.8 Client side browsing history.
|
||||
This type of data includes details about web browsing in the Microsoft browsers. Browsing History data is equivalent to ISO/IEC 19944:2017 8.2.3.2.8 Client-side browsing history.
|
||||
|
||||
### Data Use for Browsing History data
|
||||
|
||||
@ -413,23 +413,23 @@ This type of data includes details about web browsing in the Microsoft browsers.
|
||||
**With (optional) Tailored experiences:**<br>
|
||||
If a user has enabled Tailored experiences on the device, [pseudonymized](#pseudo) Browsing History data from Windows 10 is used by Microsoft to [personalize](#personalize), [recommend](#recommend), and [offer](#offer) Microsoft products and services to Windows 10 users. Also, if a user has enabled Tailored experiences on the device, [pseudonymized](#pseudo) Browsing History data from Windows 10 is used by Microsoft to [promote](#promote) third-party Windows apps, services, hardware, and peripherals to Windows 10 users. For example:
|
||||
|
||||
- We may recommend that a user download a compatible app from the Microsoft Store if they have browsed to the related website. For example, if a user uses the Facebook website, we may recommend the Facebook app.
|
||||
- We might recommend that a user download a compatible app from the Microsoft Store if they have browsed to the related website. For example, if a user uses the Facebook website, we may recommend the Facebook app.
|
||||
|
||||
### Data Description for Browsing History data type
|
||||
|
||||
**Microsoft browser data sub-type:** Information about **Address** bar and **Search** box performance on the device
|
||||
**Microsoft browser data subtype:** Information about **Address** bar and **Search** box performance on the device
|
||||
|
||||
- Text typed in **Address** bar and **Search** box
|
||||
- Text selected for an Ask Cortana search
|
||||
- Service response time
|
||||
- Auto-completed text, if there was an auto-complete
|
||||
- Autocompleted text, if there was an autocomplete
|
||||
- Navigation suggestions provided based on local history and favorites
|
||||
- Browser ID
|
||||
- URLs (may include search terms)
|
||||
- Page title
|
||||
|
||||
## Inking Typing and Speech Utterance data
|
||||
This type of data gathers details about the voice, inking, and typing input features on the device. Inking, Typing and Speech Utterance data is a sub-type of ISO/IEC 19944:2017 8.2.3.2.1 End User Identifiable information.
|
||||
This type of data gathers details about the voice, inking, and typing input features on the device. Inking, Typing, and Speech Utterance data is a subtype of ISO/IEC 19944:2017 8.2.3.2.1 End User Identifiable information.
|
||||
|
||||
### Data Use for Inking, Typing, and Speech Utterance data
|
||||
|
||||
@ -438,7 +438,7 @@ This type of data gathers details about the voice, inking, and typing input feat
|
||||
|
||||
- Data about words marked as spelling mistakes and replaced with another word from the context menu is used to improve the spelling feature.
|
||||
- Data about alternate words shown and selected by the user after right-clicking is used to improve the word recommendation feature.
|
||||
- Data about auto-corrected words that were restored back to the original word by the user is used to improve the auto-correct feature.
|
||||
- Data about autocorrected words that were restored back to the original word by the user is used to improve the autocorrect feature.
|
||||
- Data about whether Narrator detected and recognized a touch gesture is used to improve touch gesture recognition.
|
||||
- Data about handwriting samples sent from the Handwriting Panel is used to help Microsoft improve handwriting recognition.
|
||||
|
||||
@ -448,15 +448,15 @@ This type of data gathers details about the voice, inking, and typing input feat
|
||||
|
||||
### Data Description for Inking, Typing, and Speech Utterance data type
|
||||
|
||||
**Voice, inking, and typing sub-type:** Information about voice, inking and typing features
|
||||
**Voice, inking, and typing subtype:** Information about voice, inking, and typing features
|
||||
|
||||
- Type of pen used (highlighter, ball point, or pencil), pen color, stroke height and width, and how long it is used
|
||||
- Pen gestures (click, double click, pan, zoom, or rotate)
|
||||
- Palm Touch x,y coordinates
|
||||
- Input latency, missed pen signals, number of frames, strokes, first frame commit time, and sample rate
|
||||
- Ink strokes written, text before and after the ink insertion point, recognized text entered, input language -- processed to remove identifiers, sequencing information, and other data (such as email addresses and - numeric values), which could be used to reconstruct the original content or associate the input to the user
|
||||
- Text input from Windows 10 Mobile on-screen keyboards, except from password fields and private sessions -- processed to remove identifiers, sequencing information, and other data (such as email addresses and numeric values), which could be used to reconstruct the original content or associate the input to the user
|
||||
- Text of speech recognition results -- result codes and recognized text
|
||||
- Ink strokes written, text before and after the ink insertion point, recognized text entered, input language - processed to remove identifiers, sequencing information, and other data (such as email addresses and - numeric values), which could be used to reconstruct the original content or associate the input to the user
|
||||
- Text input from Windows 10 Mobile on-screen keyboards, except from password fields and private sessions - processed to remove identifiers, sequencing information, and other data (such as email addresses and numeric values), which could be used to reconstruct the original content or associate the input to the user
|
||||
- Text of speech recognition results - result codes and recognized text
|
||||
- Language and model of the recognizer and the System Speech language
|
||||
- App ID using speech features
|
||||
- Whether user is known to be a child
|
||||
@ -496,9 +496,9 @@ Use of the specified data categories give recommendations about Microsoft produc
|
||||
|
||||
ISO/IEC 19944:2017 Reference: **9.3.5 Offer upgrades or upsell**
|
||||
|
||||
Implies the source of the data is Microsoft products and services, and the upgrades offered come from Microsoft products and services that are relevant to the context of the current capability. The target audience for the offer is Microsoft customers.
|
||||
Implies that the source of the data is Microsoft products and services, and the upgrades offered come from Microsoft products and services that are relevant to the context of the current capability. The target audience for the offer is Microsoft customers.
|
||||
|
||||
Specifically, use of the specified data categories to make an offer or upsell new capability or capacity of a Microsoft product or service which is (i) contextually relevant to the product or service in which it appears; (ii) likely to result in additional future revenue for Microsoft from end user; and (iii) Microsoft receives no consideration for placement.
|
||||
Specifically, use of the specified data categories to make an offer or upsell new capability or capacity of a Microsoft product or service that is (i) contextually relevant to the product or service in which it appears; (ii) likely to result in additional future revenue for Microsoft from end user; and (iii) Microsoft receives no consideration for placement.
|
||||
|
||||
### Promote
|
||||
|
||||
@ -508,7 +508,7 @@ Use of the specified data categories to promote a product or service in or on a
|
||||
|
||||
### Data identification qualifiers
|
||||
|
||||
Here are the list of data identification qualifiers and the ISO/IEC 19944:2017 reference:
|
||||
Here are the data identification qualifiers and the ISO/IEC 19944:2017 reference:
|
||||
|
||||
- **<a name="pseudo">Pseudonymized Data</a>** 8.3.3 Pseudonymized data. Microsoft usage notes are as defined.
|
||||
- **<a name="anon">Anonymized Data</a>** 8.3.5 Anonymized data. Microsoft usage notes are as defined.
|
||||
|
Loading…
x
Reference in New Issue
Block a user