Merge branch 'master' of https://cpubwin.visualstudio.com/_git/it-client into UCazure
@ -5321,11 +5321,6 @@
|
|||||||
"redirect_document_id": true
|
"redirect_document_id": true
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"source_path": "devices/hololens/hololens-insider.md",
|
|
||||||
"redirect_url": "/devices/hololens/hololens-whats-new",
|
|
||||||
"redirect_document_id": true
|
|
||||||
},
|
|
||||||
{
|
|
||||||
"source_path": "windows/configuration/windows-diagnostic-data-1709.md",
|
"source_path": "windows/configuration/windows-diagnostic-data-1709.md",
|
||||||
"redirect_url": "/windows/configuration/windows-diagnostic-data",
|
"redirect_url": "/windows/configuration/windows-diagnostic-data",
|
||||||
"redirect_document_id": true
|
"redirect_document_id": true
|
||||||
|
@ -27,7 +27,7 @@ You can find the Microsoft Edge Group Policy settings in the following location
|
|||||||
|
|
||||||
## Configuration options
|
## Configuration options
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
|
|
||||||
## Configure Open Microsoft Edge With
|
## Configure Open Microsoft Edge With
|
||||||
|
BIN
browsers/edge/images/allow-shared-books-folder.png
Normal file
After Width: | Height: | Size: 96 KiB |
Before Width: | Height: | Size: 87 KiB After Width: | Height: | Size: 64 KiB |
Before Width: | Height: | Size: 141 KiB After Width: | Height: | Size: 101 KiB |
Before Width: | Height: | Size: 155 KiB After Width: | Height: | Size: 167 KiB |
Before Width: | Height: | Size: 77 KiB |
Before Width: | Height: | Size: 77 KiB After Width: | Height: | Size: 47 KiB |
Before Width: | Height: | Size: 74 KiB |
Before Width: | Height: | Size: 74 KiB |
Before Width: | Height: | Size: 154 KiB After Width: | Height: | Size: 116 KiB |
Before Width: | Height: | Size: 176 KiB |
Before Width: | Height: | Size: 305 KiB |
Before Width: | Height: | Size: 236 KiB |
Before Width: | Height: | Size: 92 KiB After Width: | Height: | Size: 67 KiB |
Before Width: | Height: | Size: 56 KiB After Width: | Height: | Size: 35 KiB |
Before Width: | Height: | Size: 209 KiB |
Before Width: | Height: | Size: 258 KiB |
Before Width: | Height: | Size: 257 KiB After Width: | Height: | Size: 173 KiB |
Before Width: | Height: | Size: 257 KiB |
Before Width: | Height: | Size: 13 KiB |
Before Width: | Height: | Size: 333 KiB After Width: | Height: | Size: 283 KiB |
Before Width: | Height: | Size: 96 KiB After Width: | Height: | Size: 81 KiB |
Before Width: | Height: | Size: 110 KiB |
Before Width: | Height: | Size: 94 KiB After Width: | Height: | Size: 78 KiB |
Before Width: | Height: | Size: 109 KiB |
Before Width: | Height: | Size: 93 KiB After Width: | Height: | Size: 80 KiB |
Before Width: | Height: | Size: 110 KiB |
Before Width: | Height: | Size: 79 KiB After Width: | Height: | Size: 57 KiB |
Before Width: | Height: | Size: 83 KiB |
Before Width: | Height: | Size: 213 KiB After Width: | Height: | Size: 183 KiB |
Before Width: | Height: | Size: 246 KiB |
Before Width: | Height: | Size: 64 KiB After Width: | Height: | Size: 42 KiB |
Before Width: | Height: | Size: 62 KiB |
Before Width: | Height: | Size: 272 KiB After Width: | Height: | Size: 249 KiB |
Before Width: | Height: | Size: 325 KiB |
Before Width: | Height: | Size: 56 KiB After Width: | Height: | Size: 36 KiB |
@ -1,13 +0,0 @@
|
|||||||
---
|
|
||||||
description: A full-sized view of the Microsoft Edge infographic.
|
|
||||||
title: Full-sized view of the Microsoft Edge infographic
|
|
||||||
ms.date: 11/10/2016
|
|
||||||
ms.author: pashort
|
|
||||||
author: shortpatti
|
|
||||||
---
|
|
||||||
|
|
||||||
Return to: [Browser: Microsoft Edge and Internet Explorer 11](enterprise-guidance-using-microsoft-edge-and-ie11.md)<br>
|
|
||||||
Download image: [Total Economic Impact of Microsoft Edge: Infographic](https://www.microsoft.com/en-us/download/details.aspx?id=53892)
|
|
||||||
|
|
||||||

|
|
||||||
|
|
@ -1,9 +0,0 @@
|
|||||||
---
|
|
||||||
author: shortpatti
|
|
||||||
ms.author: pashort
|
|
||||||
ms.date: 10/02/2018
|
|
||||||
ms.prod: edge
|
|
||||||
ms:topic: include
|
|
||||||
---
|
|
||||||
|
|
||||||
UI settings for the home button are disabled preventing your users from making changes
|
|
@ -1,26 +0,0 @@
|
|||||||
---
|
|
||||||
title: Use Windows PowerShell to manage group policy
|
|
||||||
description:
|
|
||||||
ms.prod: edge
|
|
||||||
ms.mktglfcycl: explore
|
|
||||||
ms.sitesec: library
|
|
||||||
ms.pagetype:
|
|
||||||
ms.localizationpriority: medium
|
|
||||||
ms.date: 10/02/2018
|
|
||||||
ms.author: pashort
|
|
||||||
author: shortpatti
|
|
||||||
---
|
|
||||||
|
|
||||||
# Use Windows PowerShell to manage group policy
|
|
||||||
|
|
||||||
Windows PowerShell supports group policy automation of the same tasks you perform in Group Policy Management Console (GPMC) for domain-based group policy objects (GPOs):
|
|
||||||
|
|
||||||
- Maintain GPOs (GPO creation, removal, backup, and import)
|
|
||||||
- Associate GPOs with Active Directory service containers (group policy link creation, update, and removal)
|
|
||||||
- Set permissions on GPOs
|
|
||||||
- Modify inheritance flags on Active Directory organization units (OUs) and domains
|
|
||||||
- Configure registry-based policy settings and group policy preferences registry settings (update, retrieval, and removal)
|
|
||||||
- Create starter GPOs
|
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -1,5 +1,6 @@
|
|||||||
# [Microsoft HoloLens](index.md)
|
# [Microsoft HoloLens](index.md)
|
||||||
## [What's new in Microsoft HoloLens](hololens-whats-new.md)
|
## [What's new in Microsoft HoloLens](hololens-whats-new.md)
|
||||||
|
## [Insider preview for Microsoft HoloLens](hololens-insider.md)
|
||||||
## [HoloLens in the enterprise: requirements and FAQ](hololens-requirements.md)
|
## [HoloLens in the enterprise: requirements and FAQ](hololens-requirements.md)
|
||||||
## [Set up HoloLens](hololens-setup.md)
|
## [Set up HoloLens](hololens-setup.md)
|
||||||
## [Unlock Windows Holographic for Business features](hololens-upgrade-enterprise.md)
|
## [Unlock Windows Holographic for Business features](hololens-upgrade-enterprise.md)
|
||||||
|
@ -16,10 +16,6 @@ ms.date: 07/27/2018
|
|||||||
|
|
||||||
This topic lists new and updated topics in the [Microsoft HoloLens documentation](index.md).
|
This topic lists new and updated topics in the [Microsoft HoloLens documentation](index.md).
|
||||||
|
|
||||||
## Windows 10 Holographic for Business, version 1800
|
|
||||||
|
|
||||||
The topics in this library have been updated for Windows 10 Holographic for Business, version 1809.
|
|
||||||
|
|
||||||
## July 2018
|
## July 2018
|
||||||
|
|
||||||
New or changed topic | Description
|
New or changed topic | Description
|
||||||
|
176
devices/hololens/hololens-insider.md
Normal file
@ -0,0 +1,176 @@
|
|||||||
|
---
|
||||||
|
title: Insider preview for Microsoft HoloLens (HoloLens)
|
||||||
|
description: It’s simple to get started with Insider builds and to provide valuable feedback for our next major operating system update for HoloLens.
|
||||||
|
ms.prod: hololens
|
||||||
|
ms.sitesec: library
|
||||||
|
author: jdeckerms
|
||||||
|
ms.author: jdecker
|
||||||
|
ms.topic: article
|
||||||
|
ms.localizationpriority: medium
|
||||||
|
ms.date: 07/27/2018
|
||||||
|
---
|
||||||
|
|
||||||
|
# Insider preview for Microsoft HoloLens
|
||||||
|
|
||||||
|
Welcome to the latest Insider Preview builds for HoloLens! It’s simple to get started and provide valuable feedback for our next major operating system update for HoloLens.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<span id="get-insider" />
|
||||||
|
## How do I install the Insider builds?
|
||||||
|
|
||||||
|
On a device running the Windows 10 April 2018 Update, go to **Settings -> Update & Security -> Windows Insider Program** and select **Get started**. Link the account you used to register as a Windows Insider.
|
||||||
|
|
||||||
|
Then, select **Active development of Windows**, choose whether you’d like to receive **Fast** or **Slow** builds, and review the program terms.
|
||||||
|
|
||||||
|
Select **Confirm -> Restart Now** to finish up. After your device has rebooted, go to **Settings -> Update & Security -> Check for updates** to get the latest build.
|
||||||
|
|
||||||
|
## New features for HoloLens
|
||||||
|
|
||||||
|
The latest Insider Preview (RS5) has arrived for all HoloLens customers! This latest flight is packed with improvements that have been introduced since the [last major release of HoloLens software in May 2018](https://docs.microsoft.com/windows/mixed-reality/release-notes-october-2018).
|
||||||
|
|
||||||
|
### For everyone
|
||||||
|
|
||||||
|
|
||||||
|
Feature | Details | Instructions
|
||||||
|
--- | --- | ---
|
||||||
|
Stop video capture from the Start or quick actions menu | If you start video capture from the Start menu or quick actions menu, you’ll be able to stop recording from the same place. (Don’t forget, you can always do this with voice commands too.) | To start recording, select **Start > Video**. To stop recording, select **Start > Stop video**.
|
||||||
|
Project to a Miracast-enabled device | Project your HoloLens content to a nearby Surface device or TV/Monitor if using Microsoft Display adapter | On **Start**, select **Connect**. Select the device you want to project to.
|
||||||
|
New notifications | View and respond to notification toasts on HoloLens, just like you do on a PC. | You’ll now see notifications from apps that provide them. Gaze to respond to or dismiss them (or if you’re in an immersive experience, use the bloom gesture).
|
||||||
|
HoloLens overlays (file picker, keyboard, dialogs, etc.) | You’ll now see overlays such as the keyboard, dialogs, file picker, etc. when using immersive apps. | When you’re using an immersive app, input text, select a file from the file picker, or interact with dialogs without leaving the app.
|
||||||
|
Visual feedback overlay UI for volume change | When you use the volume up/down buttons on your HoloLens you’ll see a visual display of the volume level. | Adjust the device volume using the volume up/down buttons located on the right arm of the HoloLens. Use the visual display to track the volume level.
|
||||||
|
New UI for device boot | A loading indicator was added during the boot process to provide visual feedback that the system is loading. | Reboot your device to see the new loading indicator—it’s between the "Hello" message and the Windows boot logo.
|
||||||
|
Share UX: Nearby Sharing | Addition of the Windows Nearby Sharing experience, allowing you to share a capture with a nearby Windows device. | Capture a photo or video on HoloLens (or use the share button from an app such as Microsoft Edge). Select a nearby Windows device to share with.
|
||||||
|
Share from Microsoft Edge | Share button is now available on Microsoft Edge windows on HoloLens. | In Microsoft Edge, select **Share**. Use the HoloLens share picker to share web content.
|
||||||
|
|
||||||
|
### For developers
|
||||||
|
|
||||||
|
- Support for Holographic [Camera Capture UI API](https://docs.microsoft.com/windows/uwp/audio-video-camera/capture-photos-and-video-with-cameracaptureui), which will let developers expose a way for users to seamlessly invoke camera or video capture from within their applications. For example, users can now capture and insert photo or video content directly within apps like Word.
|
||||||
|
- Mixed Reality Capture has been improved to exclude hidden mesh from captures, which means videos captures by apps will no longer contain black corners around the content.
|
||||||
|
|
||||||
|
### For commercial customers
|
||||||
|
|
||||||
|
|
||||||
|
Feature | Details | Instructions
|
||||||
|
--- | --- | ---
|
||||||
|
Enable post-setup provisioning | Can now apply a runtime provisioning package at any time using **Settings**. | On your PC:<br><br>1. Create a provisioning package as described at [Create a provisioning package for HoloLens using the HoloLens wizard](hololens-provisioning.md). <br>2. Connect the HoloLens device via USB to a PC. HoloLens will show up as a device in File Explorer on the PC. <br>3. Drag and drop the provisioning package to the Documents folder on the HoloLens. <br><br>On your HoloLens: <br><br>1. Go to **Settings > Accounts > Access work or school**. <br>2. In **Related Settings**, select **Add or remove a provisioning package**.<br>3. On the next page, select **Add a package** to launch the file picker and select your provisioning package. <br>**Note:** if the folder is empty, make sure you select **This Device** and select **Documents**.<br>After your package has been applied, it will show in the list of Installed packages. To view package details or to remove the package from the device, select the listed package.
|
||||||
|
Assigned access with Azure AD groups | Flexibility to use Azure AD groups for configuration of Windows assigned access to set up single or multi-app kiosk configuration. | Prepare XML file to configure Assigned Access on PC:<br><br>1. In a text editor, open [the provided file AssignedAccessHoloLensConfiguration_AzureADGroup.xml](#xml).<br>2. Change the group ID to one available in your Azure AD tenant. You can find the group ID of an Azure Active Directory Group by either :<br>- following the steps at [Azure Active Directory version 2 cmdlets for group management](https://docs.microsoft.com/azure/active-directory/active-directory-accessmanagement-groups-settings-v2-cmdlets),<br>OR<br>- in the Azure portal, with the steps at [Manage the settings for a group in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-groups-settings-azure-portal).<br><br>**Note:** The sample configures the following apps: Skype, Learning, Feedback Hub, Flow, Camera, and Calibration. <br><br>Create provisioning package with WCD:<br><br>1. On a PC, follow the steps at [Create a provisioning package for HoloLens using the HoloLens wizard](hololens-provisioning.md) to create a provisioning package.<br>2. Ensure that you include the license file in **Set up device**.<br>3. Select **Switch to advanced editor** (bottom left), and **Yes** for warning prompt.<br>4. Expand the runtime settings selection in the **Available customizations** panel and select **AssignedAccess > MultiAppAssignedAccessSettings**.<br>5. In the middle panel, you should now see the setting displayed with documentation in the panel below. Browse to the XML you modified for Assigned Access.<br>6. On the **Export** menu, select **Provisioning package**. <br>**Warning:** If you encrypt the provisioning package, provisioning the HoloLens device will fail.<br>7. Select **Next** to specify the output location where you want the provisioning package to go once it's built.<br>8. Select **Next**, and then select **Build** to start building the package.<br>9. When the build completes, select **Finish**. <br><br>Apply the package to HoloLens: <br><br>1. Connect HoloLens via USB to a PC and start the device, but do not continue past the **Fit** page of OOBE (the first page with the blue box). HoloLens will show up as a device in File Explorer on the PC. <br>2. In File Explorer, drag and drop the provisioning package (.ppkg) onto the device storage.<br>3. Briefly press and release the **Volume Down** and **Power** buttons simultaneously again while on the fit page. <br>4. The device will ask you if you trust the package and would like to apply it. Confirm that you trust the package.<br>5. You will see whether the package was applied successfully or not. If it failed, you can fix your package and try again. If it succeeded, proceed with OOBE.<br><br>Enable assigned access on HoloLens: <br><br>1. After applying the provisioning package, during the **Account Setup** flows in OOBE, select **My work or school owns this** to set up your device with an Azure AD account. <br>**Note:** This account must not be in the group chosen for Assigned Access.<br>2. Once you reach the Shell, ensure the Skype app is installed either via your MDM environment or from the Store. <br>3. After the Skype app is installed, sign out. <br>4. On the sign-in screen, select the **Other User** option and enter an Azure AD account email address that belongs to the group chosen for Assigned Access. Then enter the password to sign in. You should now see this user with only the apps configured in the Assigned Access profile.
|
||||||
|
PIN sign-in on profile switch from sign-in screen | PIN sign-in is now available for **Other User**. | When signing in as **Other User**, the PIN option is now available under **Sign-In options**.
|
||||||
|
Sign in with Web Cred Provider using password | You can now select the Globe sign-in option to launch web sign-in with your password. Look for additional web sign-in methods coming in the future. | From the sign-in screen, select **Sign-In options** and select the Globe option to launch web sign-in. Enter your user name if needed, then your password. <br>**Note:** You can choose to bypass any PIN/Smartcard options when prompted during web sign-in.
|
||||||
|
Read device hardware info through MDM so devices can be tracked by serial # | IT administrators can see and track HoloLens by device serial number in their MDM console. | Refer to your MDM documentation for feature availability, and for how to use your MDM console to view HoloLens device serial number.
|
||||||
|
Set HoloLens device name through MDM (rename) | IT administrators can see and rename HoloLens devices in their MDM console. | Refer to your MDM documentation for feature availability, and for how to use your MDM console to view and set your HoloLens device name (rename).
|
||||||
|
|
||||||
|
### For international customers
|
||||||
|
|
||||||
|
|
||||||
|
Feature | Details | Instructions
|
||||||
|
--- | --- | ---
|
||||||
|
Localized Chinese and Japanese builds | Use HoloLens with localized user interface for Simplified Chinese or Japanese, including localized Pinyin keyboard, dictation, and voice commands. | See below.
|
||||||
|
|
||||||
|
#### Installing the Chinese or Japanese versions of the Insider builds
|
||||||
|
|
||||||
|
In order to switch to the Chinese or Japanese version of HoloLens, you’ll need to download the build for the language on a PC and then install it on your HoloLens using the Windows Device Recovery Tool (WDRT).
|
||||||
|
|
||||||
|
>[!IMPORTANT]
|
||||||
|
>Installing the Chinese or Japanese builds of HoloLens using WDRT will delete existing data, like personal files and settings, from your HoloLens.
|
||||||
|
|
||||||
|
1. On a retail HoloLens device, [opt in to Insider Preview builds](#get-insider) to prepare your device for the RS5 Preview.
|
||||||
|
2. On your PC, download and install [the Windows Device Recovery Tool (WDRT)](https://support.microsoft.com/help/12379).
|
||||||
|
3. Download the package for the language you want to your PC: [Simplified Chinese](https://aka.ms/hololenspreviewdownload-ch) or [Japanese](https://aka.ms/hololenspreviewdownload-jp).
|
||||||
|
4. When the download is finished, select **File Explorer > Downloads**. Right-click the zipped folder you just downloaded, and select **Extract all... > Extract** to unzip it.
|
||||||
|
5. Connect your HoloLens to your PC using the micro-USB cable it came with. (Even if you've been using other cables to connect your HoloLens, this one works best.)
|
||||||
|
6. The tool will automatically detect your HoloLens. Select the Microsoft HoloLens tile.
|
||||||
|
7. On the next screen, select **Manual package selection** and choose the installation file contained in the folder you unzipped in step 4. (Look for a file with the extension “.ffu”.)
|
||||||
|
8. Select **Install software** and follow the instructions to finish installing.
|
||||||
|
9. Once the build is installed, HoloLens setup will start automatically. Put on the device and follow the setup directions.
|
||||||
|
10. After you complete setup, go to **Settings -> Update & Security -> Windows Insider Program** and select **Get started**. Link the account you used to register as a Windows Insider. Then, select **Active development of Windows**, choose whether you’d like to receive **Fast** or **Slow** builds, and review the program terms. Select **Confirm -> Restart Now** to finish up. After your device has rebooted, go to **Settings -> Update & Security -> Check for updates** to get the latest build.
|
||||||
|
|
||||||
|
|
||||||
|
## Note for language support
|
||||||
|
|
||||||
|
- You can’t change the system language between English, Japanese, and Chinese using the Settings app. Flashing a new build is the only supported way to change the device system language.
|
||||||
|
- While you can enter Simplified Chinese / Japanese text using the on-screen Pinyin keyboard, typing in Simplified Chinese / Japanese using a Bluetooth hardware keyboard is not supported at this time. However, on Chinese/Japanese HoloLens, you can continue to use a BT keyboard to type in English (the Shift key on a hardware keyboard toggles the keyboard to type in English).
|
||||||
|
|
||||||
|
## Note for developers
|
||||||
|
|
||||||
|
You are welcome and encouraged to try developing your applications using this build of HoloLens. Check out the [HoloLens Developer Documentation](https://developer.microsoft.com/windows/mixed-reality/development) to get started. Those same instructions work with this latest build of HoloLens. You can use the same builds of Unity and Visual Studio that you're already using for HoloLens development.
|
||||||
|
|
||||||
|
## Provide feedback and report issues
|
||||||
|
|
||||||
|
Please use [the Feedback Hub app](https://docs.microsoft.com/windows/mixed-reality/give-us-feedback) on your HoloLens or Windows 10 PC to provide feedback and report issues. Using Feedback Hub ensures that all necessary diagnostics information is included to help our engineers quickly debug and resolve the problem. Issues with the Chinese and Japanese version of HoloLens should be reported the same way.
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
|
>Be sure to accept the prompt that asks whether you’d like Feedback Hub to access your Documents folder (select **Yes** when prompted).
|
||||||
|
|
||||||
|
<span id="xml" />
|
||||||
|
## AssignedAccessHoloLensConfiguration_AzureADGroup.xml
|
||||||
|
|
||||||
|
Copy this sample XML to use for the [**Assigned access with Azure AD groups** feature](#for-commercial-customers).
|
||||||
|
|
||||||
|
```xml
|
||||||
|
<?xml version="1.0" encoding="utf-8" ?>
|
||||||
|
<!--
|
||||||
|
This is a sample Assigned Access XML file. The Profile specifies which apps are allowed
|
||||||
|
and their app IDs. An Assigned Access Config specifies the accounts or groups to which
|
||||||
|
a Profile is applicable.
|
||||||
|
|
||||||
|
!!! NOTE: Change the Name of the AzureActiveDirectoryGroup below to a valid object ID for a group in the tenant being tested. !!!
|
||||||
|
|
||||||
|
You can find the object ID of an Azure Active Directory Group by following the steps at
|
||||||
|
https://docs.microsoft.com/en-us/azure/active-directory/active-directory-accessmanagement-groups-settings-v2-cmdlets
|
||||||
|
|
||||||
|
OR in the Azure portal with the steps at
|
||||||
|
https://docs.microsoft.com/en-us/azure/active-directory/active-directory-groups-settings-azure-portal
|
||||||
|
|
||||||
|
-->
|
||||||
|
<AssignedAccessConfiguration xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config">
|
||||||
|
<Profiles>
|
||||||
|
<Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}">
|
||||||
|
<AllAppsList>
|
||||||
|
<AllowedApps>
|
||||||
|
<!-- Learning app -->
|
||||||
|
<App AppUserModelId="GGVLearning_cw5n1h2txyewy!GGVLearning" />
|
||||||
|
<!-- Calibration app -->
|
||||||
|
<App AppUserModelId="ViewCalibrationApp_cw5n1h2txyewy!ViewCalibrationApp" />
|
||||||
|
<!-- Feedback Hub -->
|
||||||
|
<App AppUserModelId="Microsoft.WindowsFeedbackHub_8wekyb3d8bbwe!App" />
|
||||||
|
<!-- HoloSkype -->
|
||||||
|
<App AppUserModelId="Microsoft.SkypeApp_kzf8qxf38zg5c!App" />
|
||||||
|
<!-- HoloCamera -->
|
||||||
|
<App AppUserModelId="HoloCamera_cw5n1h2txyewy!App" />
|
||||||
|
<!-- HoloDevicesFlow -->
|
||||||
|
<App AppUserModelId="HoloDevicesFlow_cw5n1h2txyewy!App" />
|
||||||
|
</AllowedApps>
|
||||||
|
</AllAppsList>
|
||||||
|
<!-- This section is required for parity with Desktop Assigned Access. It is not currently used on HoloLens -->
|
||||||
|
<StartLayout>
|
||||||
|
<![CDATA[<LayoutModificationTemplate xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout" Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
|
||||||
|
<LayoutOptions StartTileGroupCellWidth="6" />
|
||||||
|
<DefaultLayoutOverride>
|
||||||
|
<StartLayoutCollection>
|
||||||
|
<defaultlayout:StartLayout GroupCellWidth="6">
|
||||||
|
<start:Group Name="Life at a glance">
|
||||||
|
<start:Tile Size="2x2" Column="0" Row="0" AppUserModelID="Microsoft.SkypeApp_kzf8qxf38zg5c!App" />
|
||||||
|
</start:Group>
|
||||||
|
</defaultlayout:StartLayout>
|
||||||
|
</StartLayoutCollection>
|
||||||
|
</DefaultLayoutOverride>
|
||||||
|
</LayoutModificationTemplate>
|
||||||
|
]]>
|
||||||
|
</StartLayout>
|
||||||
|
<!-- This section is required for parity with Desktop Assigned Access. It is not currently used on HoloLens -->
|
||||||
|
<Taskbar ShowTaskbar="true"/>
|
||||||
|
</Profile>
|
||||||
|
</Profiles>
|
||||||
|
<Configs>
|
||||||
|
<!-- IMPORTANT: Replace the group ID here with a valid object ID for a group in the tenant being tested that you want to
|
||||||
|
be enabled for assigned access. Refer to https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/groups-settings-v2-cmdlets on how to determine Object-Id for a AzureActiveDirectoryGroup. -->
|
||||||
|
<Config>
|
||||||
|
<UserGroup Type="AzureActiveDirectoryGroup" Name="ade2d5d2-1c86-4303-888e-80f323c33c61" /> <!-- All Intune Licensed Users -->
|
||||||
|
<DefaultProfile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}"/>
|
||||||
|
</Config>
|
||||||
|
</Configs>
|
||||||
|
</AssignedAccessConfiguration>
|
||||||
|
|
||||||
|
```
|
||||||
|
|
@ -8,7 +8,7 @@ author: jdeckerms
|
|||||||
ms.author: jdecker
|
ms.author: jdecker
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.date: 09/11/2018
|
ms.date: 12/20/2017
|
||||||
---
|
---
|
||||||
|
|
||||||
# Install apps on HoloLens
|
# Install apps on HoloLens
|
||||||
@ -55,7 +55,8 @@ The method that you use to install an app from your Microsoft Store for Business
|
|||||||
|
|
||||||
## Use MDM to deploy apps to HoloLens
|
## Use MDM to deploy apps to HoloLens
|
||||||
|
|
||||||
|
>[!IMPORTANT]
|
||||||
|
>Online-licensed apps cannot be deployed with Microsoft Store for Business on HoloLens via an MDM provider. If attempted, apps will remain in “downloading” state. Instead, you can use your MDM provider to deploy MDM-hosted apps to HoloLens, or deploy offline-licensed apps to HoloLens via Store for Business
|
||||||
|
|
||||||
|
|
||||||
You can deploy UWP apps to HoloLens using your MDM provider. For Intune instructions, see [Deploy apps in Microsoft Intune](https://docs.microsoft.com/intune/deploy-use/add-apps).
|
You can deploy UWP apps to HoloLens using your MDM provider. For Intune instructions, see [Deploy apps in Microsoft Intune](https://docs.microsoft.com/intune/deploy-use/add-apps).
|
||||||
@ -63,8 +64,6 @@ You can deploy UWP apps to HoloLens using your MDM provider. For Intune instruct
|
|||||||
Using Intune, you can also [monitor your app deployment](https://docs.microsoft.com/intune/deploy-use/monitor-apps-in-microsoft-intune).
|
Using Intune, you can also [monitor your app deployment](https://docs.microsoft.com/intune/deploy-use/monitor-apps-in-microsoft-intune).
|
||||||
|
|
||||||
|
|
||||||
>[!TIP]
|
|
||||||
>In Windows 10, version 1607, online-licensed apps cannot be deployed with Microsoft Store for Business on HoloLens via an MDM provider. If attempted, apps will remain in “downloading” state. [Update your HoloLens to a later build](https://support.microsoft.com/help/12643/hololens-update-hololens) for this capability.
|
|
||||||
|
|
||||||
## Use the Windows Device Portal to install apps on HoloLens
|
## Use the Windows Device Portal to install apps on HoloLens
|
||||||
|
|
||||||
@ -80,15 +79,13 @@ Using Intune, you can also [monitor your app deployment](https://docs.microsoft.
|
|||||||
>[!TIP]
|
>[!TIP]
|
||||||
>If you see a certificate error in the browser, follow [these troubleshooting steps](https://developer.microsoft.com/windows/mixed-reality/Using_the_Windows_Device_Portal.html#security_certificate).
|
>If you see a certificate error in the browser, follow [these troubleshooting steps](https://developer.microsoft.com/windows/mixed-reality/Using_the_Windows_Device_Portal.html#security_certificate).
|
||||||
|
|
||||||
4. In the Windows Device Portal, click **Views** and select **Apps**.
|
4. In the Windows Device Portal, click **Apps**.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
5. Click **Add** to open the **Deploy or Install Application dialog**.
|
5. In **Install app**, select an **app package** from a folder on your computer or network. If the app package requires additional software, click **Add dependency**.
|
||||||
|
|
||||||
6. Select an **app package** from a folder on your computer or network. If the app package requires additional software or framework packages, click **I want to specify framework packages**.
|
6. In **Deploy**, click **Go** to deploy the app package and added dependencies to the connected HoloLens.
|
||||||
|
|
||||||
7. Click **Next** to deploy the app package and added dependencies to the connected HoloLens.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -7,43 +7,32 @@ author: jdeckerms
|
|||||||
ms.author: jdecker
|
ms.author: jdecker
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.date: 10/02/2018
|
ms.date: 08/14/2018
|
||||||
---
|
---
|
||||||
|
|
||||||
# Set up HoloLens in kiosk mode
|
# Set up HoloLens in kiosk mode
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
In Windows 10, version 1803 and later, you can configure your HoloLens devices to run as multi-app or single-app kiosks. You can also configure guest access for a HoloLens kiosk device by [designating a SpecialGroup account in your XML file.](#guest)
|
In Windows 10, version 1803, you can configure your HoloLens devices to run as multi-app or single-app kiosks. You can also configure guest access for a HoloLens kiosk device by [designating a SpecialGroup account in your XML file.](#guest)
|
||||||
|
|
||||||
When HoloLens is configured as a multi-app kiosk, only the allowed apps are available to the user. The benefit of a multi-app kiosk, or fixed-purpose device, is to provide an easy-to-understand experience for individuals by putting in front of them only the things they need to use, and removing from their view the things they don’t need to access.
|
When HoloLens is configured as a multi-app kiosk, only the allowed apps are available to the user. The benefit of a multi-app kiosk, or fixed-purpose device, is to provide an easy-to-understand experience for individuals by putting in front of them only the things they need to use, and removing from their view the things they don’t need to access.
|
||||||
|
|
||||||
Single-app kiosk mode starts the specified app when the user signs in, and restricts the user's ability to launch new apps or change the running app.
|
Single-app kiosk mode starts the specified app when the user signs in, and restricts the user's ability to launch new apps or change the running app. When single-app kiosk mode is enabled for HoloLens, the bloom gesture and Cortana are disabled, and placed apps aren't shown in the user's surroundings.
|
||||||
|
|
||||||
The following table lists the device capabilities in the different kiosk modes.
|
The [AssignedAccess Configuration Service Provider (CSP)](https://docs.microsoft.com/windows/client-management/mdm/assignedaccess-csp) enables kiosk configuration.
|
||||||
|
|
||||||
Kiosk mode | Voice and Bloom commands | Mini-menu | Camera and video | Miracast
|
|
||||||
--- | --- | --- | --- | ---
|
|
||||||
Single-app kiosk |  |  |  | 
|
|
||||||
Multi-app kiosk |  |  with **Home** and **Volume** (default)<br><br>Photo and video buttons shown in mini-menu if the Camera app is enabled in the kiosk configuration.<br><br>Miracast is shown if the Camera app and device picker app are enabled in the kiosk configuration. |  if the Camera app is enabled in the kiosk configuration. |  if the Camera app and device picker app are enabled in the kiosk configuration.
|
|
||||||
|
|
||||||
>[!NOTE]
|
|
||||||
>Use the Application User Model ID (AUMID) to allow apps in your kiosk configuration. The Camera app AUMID is `HoloCamera_cw5n1h2txyewy!HoloCamera`. The device picker app AUMID is `HoloDevicesFlow_cw5n1h2txyewy!HoloDevicesFlow`.
|
|
||||||
|
|
||||||
The [AssignedAccess Configuration Service Provider (CSP)](https://docs.microsoft.com/windows/client-management/mdm/assignedaccess-csp) enables kiosk configuration.
|
|
||||||
|
|
||||||
>[!WARNING]
|
>[!WARNING]
|
||||||
>The assigned access feature which enables kiosk mode is intended for corporate-owned fixed-purpose devices. When the multi-app assigned access configuration is applied on the device, certain policies are enforced system-wide, and will impact other users on the device. Deleting the multi-app configuration will remove the assigned access lockdown profiles associated with the users, but it cannot revert all [the enforced policies](https://docs.microsoft.com/windows/configuration/lock-down-windows-10-to-specific-apps#policies-set-by-multi-app-kiosk-configuration). A factory reset is needed to clear all the policies enforced via assigned access.
|
>The assigned access feature which enables kiosk mode is intended for corporate-owned fixed-purpose devices. When the multi-app assigned access configuration is applied on the device, certain policies are enforced system-wide, and will impact other users on the device. Deleting the multi-app configuration will remove the assigned access lockdown profiles associated with the users, but it cannot revert all [the enforced policies](https://docs.microsoft.com/windows/configuration/lock-down-windows-10-to-specific-apps#policies-set-by-multi-app-kiosk-configuration). A factory reset is needed to clear all the policies enforced via assigned access.
|
||||||
>
|
>
|
||||||
>Be aware that voice commands are enabled for multi-app kiosk mode configured in Microsoft Intune or provisioning packages, even if the Cortana app is not selected as a kiosk app.
|
>Be aware that voice commands are enabled for kiosk mode configured in Microsoft Intune or provisioning packages, even if the Cortana app is not selected as a kiosk app.
|
||||||
|
|
||||||
For HoloLens devices running Windows 10, version 1803 or later, there are three methods that you can use to configure the device as a kiosk:
|
For HoloLens devices running Windows 10, version 1803, there are three methods that you can use to configure the device as a kiosk:
|
||||||
- You can use [Microsoft Intune or other mobile device management (MDM) service](#intune-kiosk) to configure single-app and multi-app kiosks.
|
- You can use [Microsoft Intune or other mobile device management (MDM) service](#intune-kiosk) to configure single-app and multi-app kiosks.
|
||||||
- You can [use a provisioning package](#ppkg-kiosk) to configure single-app and multi-app kiosks.
|
- You can [use a provisioning package](#ppkg-kiosk) to configure single-app and multi-app kiosks.
|
||||||
- You can [use the Windows Device Portal](#portal-kiosk) to configure single-app kiosks. This method is recommended only for demonstrations, as it requires that developer mode be enabled on the device.
|
- You can [use the Windows Device Portal](#portal-kiosk) to configure single-app kiosks. This method is recommended only for demonstrations, as it requires that developer mode be enabled on the device.
|
||||||
|
|
||||||
>[!NOTE]
|
For HoloLens devices running Windows 10, version 1607, you can [use the Windows Device Portal](#portal-kiosk) to configure single-app kiosks.
|
||||||
>For HoloLens devices running Windows 10, version 1607, [use the Windows Device Portal](#portal-kiosk) to configure single-app kiosks.
|
|
||||||
|
|
||||||
<span id="start-kiosk"/>
|
<span id="start-kiosk"/>
|
||||||
## Start layout for HoloLens
|
## Start layout for HoloLens
|
||||||
@ -220,10 +209,10 @@ Use the following snippet in your kiosk configuration XML to enable the **Guest*
|
|||||||
- We recommend that you do **not** select the Settings app and the File Explorer app as a kiosk app.
|
- We recommend that you do **not** select the Settings app and the File Explorer app as a kiosk app.
|
||||||
- You can select Cortana as a kiosk app.
|
- You can select Cortana as a kiosk app.
|
||||||
- To enable photo or video capture, the HoloCamera app must be enabled as a kiosk app.
|
- To enable photo or video capture, the HoloCamera app must be enabled as a kiosk app.
|
||||||
|
|
||||||
## More information
|
## More information
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Watch how to configure a kiosk in a provisioning package.
|
Watch how to configure a kiosk in a provisioning package.
|
||||||
>[!VIDEO https://www.microsoft.com/videoplayer/embed/fa125d0f-77e4-4f64-b03e-d634a4926884?autoplay=false]
|
>[!VIDEO https://www.microsoft.com/videoplayer/embed/fa125d0f-77e4-4f64-b03e-d634a4926884?autoplay=false]
|
||||||
|
|
||||||
|
@ -7,7 +7,7 @@ author: jdeckerms
|
|||||||
ms.author: jdecker
|
ms.author: jdecker
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.date: 10/02/2018
|
ms.date: 04/30/2018
|
||||||
---
|
---
|
||||||
|
|
||||||
# Configure HoloLens using a provisioning package
|
# Configure HoloLens using a provisioning package
|
||||||
@ -137,7 +137,7 @@ After you're done, click **Create**. It only takes a few seconds. When the packa
|
|||||||
10. When the build completes, click **Finish**.
|
10. When the build completes, click **Finish**.
|
||||||
|
|
||||||
<span id="apply" />
|
<span id="apply" />
|
||||||
## Apply a provisioning package to HoloLens during setup
|
## Apply a provisioning package to HoloLens
|
||||||
|
|
||||||
1. Connect the device via USB to a PC and start the device, but do not continue past the **Fit** page of OOBE (the first page with the blue box).
|
1. Connect the device via USB to a PC and start the device, but do not continue past the **Fit** page of OOBE (the first page with the blue box).
|
||||||
|
|
||||||
@ -156,23 +156,6 @@ After you're done, click **Create**. It only takes a few seconds. When the packa
|
|||||||
>[!NOTE]
|
>[!NOTE]
|
||||||
>If the device was purchased before August 2016, you will need to sign into the device with a Microsoft account, get the latest OS update, and then reset the OS in order to apply the provisioning package.
|
>If the device was purchased before August 2016, you will need to sign into the device with a Microsoft account, get the latest OS update, and then reset the OS in order to apply the provisioning package.
|
||||||
|
|
||||||
## Apply a provisioning package to HoloLens after setup
|
|
||||||
|
|
||||||
>[!NOTE]
|
|
||||||
>Windows 10, version 1809 only
|
|
||||||
|
|
||||||
On your PC:
|
|
||||||
1. Create a provisioning package as described at [Create a provisioning package for HoloLens using the HoloLens wizard](hololens-provisioning.md).
|
|
||||||
2. Connect the HoloLens device via USB to a PC. HoloLens will show up as a device in File Explorer on the PC.
|
|
||||||
3. Drag and drop the provisioning package to the Documents folder on the HoloLens.
|
|
||||||
|
|
||||||
On your HoloLens:
|
|
||||||
1. Go to **Settings > Accounts > Access work or school**.
|
|
||||||
2. In **Related Settings**, select **Add or remove a provisioning package**.
|
|
||||||
3. On the next page, select **Add a package** to launch the file picker and select your provisioning package. If the folder is empty, make sure you select **This Device** and select **Documents**.
|
|
||||||
|
|
||||||
After your package has been applied, it will show in the list of **Installed packages**. To view package details or to remove the package from the device, select the listed package.
|
|
||||||
|
|
||||||
## What you can configure
|
## What you can configure
|
||||||
|
|
||||||
Provisioning packages make use of configuration service providers (CSPs). If you're not familiar with CSPs, see [Introduction to configuration service providers (CSPs) for IT pros](https://technet.microsoft.com/itpro/windows/manage/how-it-pros-can-use-configuration-service-providers).
|
Provisioning packages make use of configuration service providers (CSPs). If you're not familiar with CSPs, see [Introduction to configuration service providers (CSPs) for IT pros](https://technet.microsoft.com/itpro/windows/manage/how-it-pros-can-use-configuration-service-providers).
|
||||||
|
@ -7,7 +7,7 @@ author: jdeckerms
|
|||||||
ms.author: jdecker
|
ms.author: jdecker
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.date: 08/02/2018
|
ms.date: 07/27/2017
|
||||||
---
|
---
|
||||||
|
|
||||||
# Set up HoloLens
|
# Set up HoloLens
|
||||||
@ -30,12 +30,7 @@ The HoloLens setup process combines a quick tutorial on using HoloLens with the
|
|||||||
2. [Turn on HoloLens](https://support.microsoft.com/help/12642). You will be guided through a calibration procedure and how to perform [the gestures](https://support.microsoft.com/help/12644/hololens-use-gestures) that you will use to operate HoloLens.
|
2. [Turn on HoloLens](https://support.microsoft.com/help/12642). You will be guided through a calibration procedure and how to perform [the gestures](https://support.microsoft.com/help/12644/hololens-use-gestures) that you will use to operate HoloLens.
|
||||||
3. Next, you'll be guided through connecting to a Wi-Fi network.
|
3. Next, you'll be guided through connecting to a Wi-Fi network.
|
||||||
4. After HoloLens connects to the Wi-Fi network, you select between **My work or school owns it** and **I own it**.
|
4. After HoloLens connects to the Wi-Fi network, you select between **My work or school owns it** and **I own it**.
|
||||||
- When you choose **My work or school owns it**, you sign in with an Azure AD account.
|
- When you choose **My work or school owns it**, you sign in with an Azure AD account. If your organization uses Azure AD Premium and has configured automatic MDM enrollment, HoloLens will be enrolled in MDM. If your organization does not use Azure AD Premium, automatic MDM enrollment isn't available, so you will need to [enroll HoloLens in device management manually](hololens-enroll-mdm.md#enroll-through-settings-app).
|
||||||
|
|
||||||
>[!NOTE]
|
|
||||||
>[To share your HoloLens device with multiple Azure AD accounts](hololens-multiple-users.md), the HoloLens device must be running Windows 10, version 1803, and be [upgraded to Windows Holographic for Business](hololens-upgrade-enterprise.md).
|
|
||||||
|
|
||||||
If your organization uses Azure AD Premium and has configured automatic MDM enrollment, HoloLens will be enrolled in MDM. If your organization does not use Azure AD Premium, automatic MDM enrollment isn't available, so you will need to [enroll HoloLens in device management manually](hololens-enroll-mdm.md#enroll-through-settings-app).
|
|
||||||
1. Enter your organizational account.
|
1. Enter your organizational account.
|
||||||
2. Accept privacy statement.
|
2. Accept privacy statement.
|
||||||
3. Sign in using your Azure AD credentials. This may redirect to your organization's sign-in page.
|
3. Sign in using your Azure AD credentials. This may redirect to your organization's sign-in page.
|
||||||
|
@ -1,58 +1,18 @@
|
|||||||
---
|
---
|
||||||
title: What's new in Microsoft HoloLens (HoloLens)
|
title: What's new in Microsoft HoloLens (HoloLens)
|
||||||
description: Windows Holographic for Business gets new features in Windows 10, version 1809.
|
description: Windows Holographic for Business gets new features in Windows 10, version 1803.
|
||||||
ms.prod: hololens
|
ms.prod: hololens
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
author: jdeckerms
|
author: jdeckerms
|
||||||
ms.author: jdecker
|
ms.author: jdecker
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.date: 10/02/2018
|
ms.date: 04/30/2018
|
||||||
---
|
---
|
||||||
|
|
||||||
# What's new in Microsoft HoloLens
|
# What's new in Microsoft HoloLens
|
||||||
|
|
||||||
|
|
||||||
## Windows 10, version 1809 for Microsoft HoloLens
|
|
||||||
|
|
||||||
### For everyone
|
|
||||||
|
|
||||||
Feature | Details
|
|
||||||
--- | ---
|
|
||||||
Mini-menu | When you're in an app, the Bloom gesture will now open a mini-menu to give you quick access to commonly used system features without having to leave the app. See [Set up HoloLens in kiosk mode](hololens-kiosk.md) for information about the mini-menu in kiosk mode.<br><br>
|
|
||||||
Stop video capture from the Start or quick actions menu | If you start video capture from the Start menu or quick actions menu, you’ll be able to stop recording from the same place. (Don’t forget, you can always do this with voice commands too.)
|
|
||||||
Project to a Miracast-enabled device | Project your HoloLens content to a nearby Surface device or TV/Monitor if using Microsoft Display adapter. On **Start**, select **Connect**, and then select the device you want to project to. **Note:** You can deploy HoloLens to use Miracast projection without enabling developer mode.
|
|
||||||
New notifications | View and respond to notification toasts on HoloLens, just like you do on a PC. Gaze to respond to or dismiss them (or if you’re in an immersive experience, use the bloom gesture).
|
|
||||||
HoloLens overlays (file picker, keyboard, dialogs, etc.) | You’ll now see overlays such as the keyboard, dialogs, file picker, etc. when using immersive apps.
|
|
||||||
Visual feedback overlay UI for volume change | When you use the volume up/down buttons on your HoloLens you’ll see a visual display of the volume level.
|
|
||||||
New UI for device boot | A loading indicator was added during the boot process to provide visual feedback that the system is loading. Reboot your device to see the new loading indicator—it’s between the "Hello" message and the Windows boot logo.
|
|
||||||
Share UX: Nearby Sharing | Addition of the Windows Nearby Sharing experience, allowing you to share a capture with a nearby Windows device. When you capture a photo or video on HoloLens (or use the share button from an app such as Microsoft Edge), select a nearby Windows device to share with.
|
|
||||||
Share from Microsoft Edge | Share button is now available on Microsoft Edge windows on HoloLens. In Microsoft Edge, select **Share**. Use the HoloLens share picker to share web content.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### For administrators
|
|
||||||
|
|
||||||
|
|
||||||
Feature | Details
|
|
||||||
--- | ---
|
|
||||||
[Enable post-setup provisioning](hololens-provisioning.md) | You can now apply a runtime provisioning package at any time using **Settings**.
|
|
||||||
Assigned access with Azure AD groups | You can now use Azure AD groups for configuration of Windows assigned access to set up single or multi-app kiosk configuration.
|
|
||||||
PIN sign-in on profile switch from sign-in screen | PIN sign-in is now available for **Other User**. | When signing in as **Other User**, the PIN option is now available under **Sign-In options**.
|
|
||||||
Sign in with Web Credential Provider using password | You can now select the Globe sign-in option to launch web sign-in with your password. From the sign-in screen, select **Sign-In options** and select the Globe option to launch web sign-in. Enter your user name if needed, then your password. <br>**Note:** You can choose to bypass any PIN/Smartcard options when prompted during web sign-in.
|
|
||||||
Read device hardware info through MDM so devices can be tracked by serial # | IT administrators can see and track HoloLens by device serial number in their MDM console. Refer to your MDM documentation for feature availability and instructions.
|
|
||||||
Set HoloLens device name through MDM (rename) | IT administrators can see and rename HoloLens devices in their MDM console. Refer to your MDM documentation for feature availability and instructions.
|
|
||||||
|
|
||||||
### For international customers
|
|
||||||
|
|
||||||
|
|
||||||
Feature | Details
|
|
||||||
--- | ---
|
|
||||||
Localized Chinese and Japanese builds | Use HoloLens with localized user interface for Simplified Chinese or Japanese, including localized Pinyin keyboard, dictation, and voice commands.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Windows 10, version 1803 for Microsoft HoloLens
|
|
||||||
|
|
||||||
Windows 10, version 1803, is the first feature update to Windows Holographic for Business since its release in Windows 10, version 1607. This update introduces the following changes:
|
Windows 10, version 1803, is the first feature update to Windows Holographic for Business since its release in Windows 10, version 1607. This update introduces the following changes:
|
||||||
|
|
||||||
|
@ -22,6 +22,7 @@ ms.date: 07/27/2018
|
|||||||
| Topic | Description |
|
| Topic | Description |
|
||||||
| --- | --- |
|
| --- | --- |
|
||||||
| [What's new in Microsoft HoloLens](hololens-whats-new.md) | Discover the new features in the latest update. |
|
| [What's new in Microsoft HoloLens](hololens-whats-new.md) | Discover the new features in the latest update. |
|
||||||
|
[Insider preview for Microsoft HoloLens](hololens-insider.md) | Learn about new HoloLens features available in the latest Insider Preview build.
|
||||||
| [HoloLens in the enterprise: requirements](hololens-requirements.md) | Lists requirements for general use, Wi-Fi, and device management |
|
| [HoloLens in the enterprise: requirements](hololens-requirements.md) | Lists requirements for general use, Wi-Fi, and device management |
|
||||||
| [Set up HoloLens](hololens-setup.md) | How to set up HoloLens for the first time |
|
| [Set up HoloLens](hololens-setup.md) | How to set up HoloLens for the first time |
|
||||||
| [Unlock Windows Holographic for Business features](hololens-upgrade-enterprise.md) | How to upgrade your Development Edition HoloLens to Windows Holographic for Business |
|
| [Unlock Windows Holographic for Business features](hololens-upgrade-enterprise.md) | How to upgrade your Development Edition HoloLens to Windows Holographic for Business |
|
||||||
|
@ -68,7 +68,7 @@ The XML below is for Windows 10, version 1803.
|
|||||||
<AccessType>
|
<AccessType>
|
||||||
<Add />
|
<Add />
|
||||||
</AccessType>
|
</AccessType>
|
||||||
<Description>This node specifies the name for a device. This setting can be managed remotely. A couple of macros can be embedded within the value for dynamic substitution: %RAND:<# of digits>% and %SERIAL%. Examples: (a) "Test%RAND:6%" will generate a name "Test" followed by 6 random digits (e.g., "Test123456"). (b) "Foo%SERIAL%", will generate a name "Foo" followed by the serial number derived from device's ID. The server must explicitly reboot the device for this value to take effect.</Description>
|
<Description>This node specifies the name for a device. This setting can be managed remotely. A couple of macros can be embedded within the value for dynamic substitution: %RAND:<# of digits>% and %SERIAL%. Examples: (a) "Test%RAND:6%" will generate a name "Test" followed by 6 random digits (e.g., "Test123456"). (b) "Foo%SERIAL%", will generate a name "Foo" followed by the serial number derived from device's ID. The server must explicitly reboot the device for this value to take effect.</Description>
|
||||||
<DFFormat>
|
<DFFormat>
|
||||||
<chr />
|
<chr />
|
||||||
</DFFormat>
|
</DFFormat>
|
||||||
|
@ -89,7 +89,7 @@ Required. A character string that specifies the location of the icon associated
|
|||||||
|
|
||||||
Supported operations are Get, Replace, and Add (cannot Add after the account is created).
|
Supported operations are Get, Replace, and Add (cannot Add after the account is created).
|
||||||
|
|
||||||
The account icon can be used as a tile in the **Start** list or an icon in the applications list under **Settings > email & accounts**. Some icons are already provided on the device. The suggested icon for POP/IMAP or generic ActiveSync accounts is at res://AccountSettingsSharedRes{*ScreenResolution*}!%s.genericmail.png. The suggested icon for Exchange Accounts is at res://AccountSettingsSharedRes{*ScreenResolution*}!%s.office.outlook.png. Custom icons can be added if desired.
|
The account icon can be used as a tile in the **Start** list or an icon in the applications list under **Settings > email & accounts**. Some icons are already provided on the device. The suggested icon for POP/IMAP or generic ActiveSync accounts is at res://AccountSettingsSharedRes{*ScreenResolution*}!%s.genericmail.png. The suggested icon for Exchange Accounts is at res://AccountSettingsSharedRes{*ScreenResolution*}!%s.office.outlook.png. Custom icons can be added if desired.
|
||||||
|
|
||||||
<a href="" id="account-guid-accounttype"></a>***Account GUID*/AccountType**
|
<a href="" id="account-guid-accounttype"></a>***Account GUID*/AccountType**
|
||||||
Required. A character string that specifies the account type.
|
Required. A character string that specifies the account type.
|
||||||
|
@ -106,7 +106,7 @@ ms.date: 06/26/2017
|
|||||||
<Target>
|
<Target>
|
||||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/AllowAppvClient</LocURI>
|
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/AllowAppvClient</LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data><enabled/></Data>
|
<Data><enabled/></Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Replace>
|
</Replace>
|
||||||
```
|
```
|
||||||
@ -126,7 +126,7 @@ ms.date: 06/26/2017
|
|||||||
<Target>
|
<Target>
|
||||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/AllowPackageScripts</LocURI>
|
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/AllowPackageScripts</LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data><enabled/></Data>
|
<Data><enabled/></Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Replace>
|
</Replace>
|
||||||
```
|
```
|
||||||
|
@ -60,7 +60,7 @@ In the out-of-the-box scenario, the web view is 100% full screen, which gives th
|
|||||||
|
|
||||||
For Azure AD enrollment to work for an Active Directory Federated Services (AD FS) backed Azure AD account, you must enable password authentication for the intranet on the ADFS service as described in solution \#2 in [this article](https://go.microsoft.com/fwlink/?LinkId=690246).
|
For Azure AD enrollment to work for an Active Directory Federated Services (AD FS) backed Azure AD account, you must enable password authentication for the intranet on the ADFS service as described in solution \#2 in [this article](https://go.microsoft.com/fwlink/?LinkId=690246).
|
||||||
|
|
||||||
Once a user has an Azure AD account added to Windows 10 and enrolled in MDM, the enrollment can be manages through **Settings** > **Accounts** > **Work access**. Device management of either Azure AD Join for corporate scenarios or BYOD scenarios are similar.
|
Once a user has an Azure AD account added to Windows 10 and enrolled in MDM, the enrollment can be manages through **Settings** > **Accounts** > **Work access**. Device management of either Azure AD Join for corporate scenarios or BYOD scenarios are similar.
|
||||||
|
|
||||||
> **Note** Users cannot remove the device enrollment through the **Work access** user interface because management is tied to the Azure AD or work account.
|
> **Note** Users cannot remove the device enrollment through the **Work access** user interface because management is tied to the Azure AD or work account.
|
||||||
|
|
||||||
@ -122,7 +122,7 @@ Use the following steps to register a cloud-based MDM application with Azure AD.
|
|||||||
6. Click **Add an application my organization is developing**.
|
6. Click **Add an application my organization is developing**.
|
||||||
7. Enter a friendly name for the application, such as ContosoMDM, select **Web Application and or Web API**, then click **Next**.
|
7. Enter a friendly name for the application, such as ContosoMDM, select **Web Application and or Web API**, then click **Next**.
|
||||||
8. Enter the login URL for your MDM service.
|
8. Enter the login URL for your MDM service.
|
||||||
9. For the App ID, enter **https://<your\_tenant\_name>/ContosoMDM**, then click OK.
|
9. For the App ID, enter **https://<your\_tenant\_name>/ContosoMDM**, then click OK.
|
||||||
10. While still in the Azure portal, click the **Configure** tab of your application.
|
10. While still in the Azure portal, click the **Configure** tab of your application.
|
||||||
11. Mark your application as **multi-tenant**.
|
11. Mark your application as **multi-tenant**.
|
||||||
12. Find the client ID value and copy it.
|
12. Find the client ID value and copy it.
|
||||||
|
@ -33,7 +33,7 @@ The following diagram shows the BrowserFavorite configuration service provider i
|
|||||||
<a href="" id="favorite-name-------------"></a>***favorite name***
|
<a href="" id="favorite-name-------------"></a>***favorite name***
|
||||||
Required. Specifies the user-friendly name of the favorite URL that is displayed in the Favorites list of Internet Explorer.
|
Required. Specifies the user-friendly name of the favorite URL that is displayed in the Favorites list of Internet Explorer.
|
||||||
|
|
||||||
> **Note** The *favorite name* should contain only characters that are valid in the Windows file system. The invalid characters are: \\ / : \* ? " < > |
|
> **Note** The *favorite name* should contain only characters that are valid in the Windows file system. The invalid characters are: \\ / : \* ? " < > |
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -194,7 +194,7 @@ Required. Specifies the root CA thumbprint. It is a 20-byte value of the SHA1 ce
|
|||||||
Supported operations are Get, Add, Delete, and Replace.
|
Supported operations are Get, Add, Delete, and Replace.
|
||||||
|
|
||||||
<a href="" id="my-scep-uniqueid-install-subjectalternativenames"></a>**My/SCEP/*UniqueID*/Install/SubjectAlternativeNames**
|
<a href="" id="my-scep-uniqueid-install-subjectalternativenames"></a>**My/SCEP/*UniqueID*/Install/SubjectAlternativeNames**
|
||||||
Optional. Specifies the subject alternative name. Multiple alternative names can be specified. Each name is the combination of name format+actual name. Refer to the name type definition in MSDN. Each pair is separated by semicolon. For example, multiple subject alternative names are presented in the format *<nameformat1>*+*<actual name1>*;*<name format 2>*+*<actual name2>*. Value type is chr.
|
Optional. Specifies the subject alternative name. Multiple alternative names can be specified. Each name is the combination of name format+actual name. Refer to the name type definition in MSDN. Each pair is separated by semicolon. For example, multiple subject alternative names are presented in the format *<nameformat1>*+*<actual name1>*;*<name format 2>*+*<actual name2>*. Value type is chr.
|
||||||
|
|
||||||
Supported operations are Get, Add, Delete, and Replace.
|
Supported operations are Get, Add, Delete, and Replace.
|
||||||
|
|
||||||
@ -299,7 +299,7 @@ For ROBO renewal failure, the client retries the renewal periodically until the
|
|||||||
|
|
||||||
For manual retry failure, there are no built-in retries. The user can retry later. At the next scheduled certificate renewal retry period, the device prompts the credential dialog again.
|
For manual retry failure, there are no built-in retries. The user can retry later. At the next scheduled certificate renewal retry period, the device prompts the credential dialog again.
|
||||||
|
|
||||||
The default value is 7 and the valid values are 1 – 1000 AND =< RenewalPeriod, otherwise it will result in errors. Value type is an integer.
|
The default value is 7 and the valid values are 1 – 1000 AND =< RenewalPeriod, otherwise it will result in errors. Value type is an integer.
|
||||||
|
|
||||||
Supported operations are Add, Get, Delete, and Replace.
|
Supported operations are Add, Get, Delete, and Replace.
|
||||||
|
|
||||||
|
@ -32,7 +32,7 @@ To help diagnose enrollment or device management issues in Windows 10 devices m
|
|||||||
|
|
||||||
Starting with the Windows 10, version 1511, MDM logs are captured in the Event Viewer in the following location:
|
Starting with the Windows 10, version 1511, MDM logs are captured in the Event Viewer in the following location:
|
||||||
|
|
||||||
- Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostic-Provider
|
- Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostic-Provider
|
||||||
|
|
||||||
Here's a screenshot:
|
Here's a screenshot:
|
||||||
|
|
||||||
@ -138,7 +138,7 @@ Since there is no Event Viewer in Windows 10 Mobile, you can use the [Field Medi
|
|||||||

|

|
||||||
|
|
||||||
7. Save the logs. They will be stored in the Field Medic log location on the device.
|
7. Save the logs. They will be stored in the Field Medic log location on the device.
|
||||||
8. You can send the logs via email by attaching the files from **Documents > Field Medic > Reports > ...** folder.
|
8. You can send the logs via email by attaching the files from **Documents > Field Medic > Reports > ...** folder.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
|
@ -124,7 +124,7 @@ A production ready deployment must have the appropriate certificate details as p
|
|||||||
|
|
||||||
EAP XML must be updated with relevant information for your environment This can be done either manually by editing the XML sample below, or by using the step by step UI guide. After the EAP XML is updated, refer to instructions from your MDM to deploy the updated configuration as follows:
|
EAP XML must be updated with relevant information for your environment This can be done either manually by editing the XML sample below, or by using the step by step UI guide. After the EAP XML is updated, refer to instructions from your MDM to deploy the updated configuration as follows:
|
||||||
|
|
||||||
- For Wi-Fi, look for the <EAPConfig> section of your current WLAN Profile XML (This is what you specify for the WLanXml node in the Wi-Fi CSP). Within these tags you will find the complete EAP configuration. Replace the section under <EAPConfig> with your updated XML and update your Wi-Fi profile. You might need to refer to your MDM’s guidance on how to deploy a new Wi-Fi profile.
|
- For Wi-Fi, look for the <EAPConfig> section of your current WLAN Profile XML (This is what you specify for the WLanXml node in the Wi-Fi CSP). Within these tags you will find the complete EAP configuration. Replace the section under <EAPConfig> with your updated XML and update your Wi-Fi profile. You might need to refer to your MDM’s guidance on how to deploy a new Wi-Fi profile.
|
||||||
- For VPN, EAP Configuration is a separate field in the MDM Configuration. Work with your MDM provider to identify and update the appropriate Field.
|
- For VPN, EAP Configuration is a separate field in the MDM Configuration. Work with your MDM provider to identify and update the appropriate Field.
|
||||||
|
|
||||||
For information about EAP Settings, see <https://technet.microsoft.com/library/hh945104.aspx#BKMK_Cfg_cert_Selct>
|
For information about EAP Settings, see <https://technet.microsoft.com/library/hh945104.aspx#BKMK_Cfg_cert_Selct>
|
||||||
|
@ -302,7 +302,7 @@ Value is one of the following:
|
|||||||
|
|
||||||
When an application removal or configuration roll-back is provisioned, the EMAIL2 CSP passes the request to Configuration Manager, which handles the transaction externally. When a MAPI application is removed, the accounts that were created with it are deleted and all messages and other properties that the transport (for example, Short Message Service \[SMS\], Post Office Protocol \[POP\], or Simple Mail Transfer Protocol \[SMTP\]) might have stored, are lost. If an attempt to create a new email account is unsuccessful, the new account is automatically deleted. If an attempt to edit an existing account is unsuccessful, the original configuration is automatically rolled back (restored).
|
When an application removal or configuration roll-back is provisioned, the EMAIL2 CSP passes the request to Configuration Manager, which handles the transaction externally. When a MAPI application is removed, the accounts that were created with it are deleted and all messages and other properties that the transport (for example, Short Message Service \[SMS\], Post Office Protocol \[POP\], or Simple Mail Transfer Protocol \[SMTP\]) might have stored, are lost. If an attempt to create a new email account is unsuccessful, the new account is automatically deleted. If an attempt to edit an existing account is unsuccessful, the original configuration is automatically rolled back (restored).
|
||||||
|
|
||||||
For OMA DM, the EMAIL2 CSP handles the Replace command differently from most other configuration service providers. For the EMAIL2 CSP, Configuration Manager implicitly adds the missing part of the node to be replaced or any segment in the path of the node if it is left out in the <LocURI></LocURI> block. There are separate parameters defined for the outgoing server logon credentials. The following are the usage rules for these credentials:
|
For OMA DM, the EMAIL2 CSP handles the Replace command differently from most other configuration service providers. For the EMAIL2 CSP, Configuration Manager implicitly adds the missing part of the node to be replaced or any segment in the path of the node if it is left out in the \<LocURI>\</LocURI\> block. There are separate parameters defined for the outgoing server logon credentials. The following are the usage rules for these credentials:
|
||||||
|
|
||||||
- The incoming server logon credentials are used (AUTHNAME, AUTHSECRET, and DOMAIN) unless the outgoing server credentials are set.
|
- The incoming server logon credentials are used (AUTHNAME, AUTHSECRET, and DOMAIN) unless the outgoing server credentials are set.
|
||||||
|
|
||||||
|
@ -70,7 +70,7 @@ Summary of steps to enable a policy:
|
|||||||
<Target>
|
<Target>
|
||||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/AllowAppVClient </LocURI>
|
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/AllowAppVClient </LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data><Enabled/></Data>
|
<Data><Enabled/></Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Replace>
|
</Replace>
|
||||||
<Final/>
|
<Final/>
|
||||||
@ -270,7 +270,7 @@ The \<Data> payload is \<disabled/>. Here is an example to disable AppVirtualiza
|
|||||||
<Target>
|
<Target>
|
||||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/PublishingAllowServer2</LocURI>
|
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/PublishingAllowServer2</LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data><disabled/></Data>
|
<Data><disabled/></Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Replace>
|
</Replace>
|
||||||
<Final/>
|
<Final/>
|
||||||
|
@ -40,7 +40,7 @@ Supported operations are Add, Delete, Get and Replace.
|
|||||||
The Apps and Settings sections of lockdown XML constitute an Allow list. Any app or setting that is not specified in AssignedAccessXML will not be available on the device to users. The following table describes the entries in lockdown XML.
|
The Apps and Settings sections of lockdown XML constitute an Allow list. Any app or setting that is not specified in AssignedAccessXML will not be available on the device to users. The following table describes the entries in lockdown XML.
|
||||||
|
|
||||||
> [!Important]
|
> [!Important]
|
||||||
> When using the AssignedAccessXml in the EnterpriseAssignedAccess CSP through an MDM, the XML must use escaped characters, such as \< instead of < because it is embedded in an XML. The examples provided in the topic are formatted for readability.
|
> When using the AssignedAccessXml in the EnterpriseAssignedAccess CSP through an MDM, the XML must use escaped characters, such as \< instead of < because it is embedded in an XML. The examples provided in the topic are formatted for readability.
|
||||||
|
|
||||||
When using the AssignedAccessXml in a provisioning package using the Windows Configuration Designer tool, do not use escaped characters.
|
When using the AssignedAccessXml in a provisioning package using the Windows Configuration Designer tool, do not use escaped characters.
|
||||||
|
|
||||||
@ -51,8 +51,8 @@ ActionCenter | Example: `<ActionCenter enabled="true"></ActionCenter>`
|
|||||||
ActionCenter | In Windows 10, when the Action Center is disabled, Above Lock notifications and toasts are also disabled. When the Action Center is enabled, the following policies are also enabled; **AboveLock/AllowActionCenterNotifications** and **AboveLock/AllowToasts**. For more information about these policies, see [Policy CSP](policy-configuration-service-provider.md)
|
ActionCenter | In Windows 10, when the Action Center is disabled, Above Lock notifications and toasts are also disabled. When the Action Center is enabled, the following policies are also enabled; **AboveLock/AllowActionCenterNotifications** and **AboveLock/AllowToasts**. For more information about these policies, see [Policy CSP](policy-configuration-service-provider.md)
|
||||||
ActionCenter | You can also add the following optional attributes to the ActionCenter element to override the default behavior: **aboveLockToastEnabled** and **actionCenterNotificationEnabled**. Valid values are 0 (policy disabled), 1 (policy enabled), and -1 (not set, policy enabled). In this example, the Action Center is enabled and both policies are disabled.: `<ActionCenter enabled="true" aboveLockToastEnabled="0" actionCenterNotificationEnabled="0"/>`
|
ActionCenter | You can also add the following optional attributes to the ActionCenter element to override the default behavior: **aboveLockToastEnabled** and **actionCenterNotificationEnabled**. Valid values are 0 (policy disabled), 1 (policy enabled), and -1 (not set, policy enabled). In this example, the Action Center is enabled and both policies are disabled.: `<ActionCenter enabled="true" aboveLockToastEnabled="0" actionCenterNotificationEnabled="0"/>`
|
||||||
ActionCenter | These optional attributes are independent of each other. In this example, Action Center is enabled, the notifications policy is disabled, and the toast policy is enabled by default because it is not set. `<ActionCenter enabled="true" actionCenterNotificationEnabled="0"/>`
|
ActionCenter | These optional attributes are independent of each other. In this example, Action Center is enabled, the notifications policy is disabled, and the toast policy is enabled by default because it is not set. `<ActionCenter enabled="true" actionCenterNotificationEnabled="0"/>`
|
||||||
StartScreenSize | Specify the size of the Start screen. In addition to 4/6 columns, you can also use 4/6/8 depending on screen resolutions. Valid values: **Small** - sets the width to 4 columns on device with short axis <400epx or 6 columns on devices with short axis >=400epx. **Large** - sets the width to 6 columns on devices with short axis <400epx or 8 columns on devices with short axis >=400epx.
|
StartScreenSize | Specify the size of the Start screen. In addition to 4/6 columns, you can also use 4/6/8 depending on screen resolutions. Valid values: **Small** - sets the width to 4 columns on device with short axis <400epx or 6 columns on devices with short axis >=400epx. **Large** - sets the width to 6 columns on devices with short axis <400epx or 8 columns on devices with short axis >=400epx.
|
||||||
StartScreenSize | If you have existing lockdown XML, you must update it if your device has >=400epx on its short axis so that tiles on Start can fill all 8 columns if you want to use all 8 columns instead of 6, or use 6 columns instead of 4. Example: `<StartScreenSize>Large</StartScreenSize>`
|
StartScreenSize | If you have existing lockdown XML, you must update it if your device has >=400epx on its short axis so that tiles on Start can fill all 8 columns if you want to use all 8 columns instead of 6, or use 6 columns instead of 4. Example: `<StartScreenSize>Large</StartScreenSize>`
|
||||||
Application | Provide the product ID for each app that will be available on the device. You can find the product ID for a locally developed app in the AppManifest.xml file of the app. For the list of product ID and AUMID see [ProductIDs in Windows 10 Mobile](#productid).
|
Application | Provide the product ID for each app that will be available on the device. You can find the product ID for a locally developed app in the AppManifest.xml file of the app. For the list of product ID and AUMID see [ProductIDs in Windows 10 Mobile](#productid).
|
||||||
Application | To turn on the notification for a Windows app, you must include the application's AUMID in the lockdown XML. However, the user can change the setting at any time from user interface. Example: `<Application productId="{A558FEBA-85D7-4665-B5D8-A2FF9C19799B}" aumid="microsoft.windowscommunicationsapps_8wekyb3d8bbwe!microsoft.windowslive.mail"/>`
|
Application | To turn on the notification for a Windows app, you must include the application's AUMID in the lockdown XML. However, the user can change the setting at any time from user interface. Example: `<Application productId="{A558FEBA-85D7-4665-B5D8-A2FF9C19799B}" aumid="microsoft.windowscommunicationsapps_8wekyb3d8bbwe!microsoft.windowslive.mail"/>`
|
||||||
Application | <img src="images/enterpriseassignedaccess-csp.png" alt="modern app notification" />
|
Application | <img src="images/enterpriseassignedaccess-csp.png" alt="modern app notification" />
|
||||||
@ -105,7 +105,7 @@ aumid="microsoft.windowscommunicationsapps_8wekyb3d8bbwe!microsoft.windowslive.m
|
|||||||
|
|
||||||
Entry | Description
|
Entry | Description
|
||||||
----------- | ------------
|
----------- | ------------
|
||||||
Folder | A folder should be contained in <Applications/> node among with other <Application/> nodes, it shares most grammar with the Application Node, **folderId** is mandatory, **folderName** is optional, which is the folder name displayed on Start. **folderId** is a unique unsigned integer for each folder.
|
Folder | A folder should be contained in <Applications/> node among with other <Application/> nodes, it shares most grammar with the Application Node, **folderId** is mandatory, **folderName** is optional, which is the folder name displayed on Start. **folderId** is a unique unsigned integer for each folder.
|
||||||
|
|
||||||
Folder example:
|
Folder example:
|
||||||
``` syntax
|
``` syntax
|
||||||
@ -403,7 +403,7 @@ The Search and custom buttons can be <em>remapped</em> or configured to open a s
|
|||||||
>
|
>
|
||||||
> Button remapping can enable a user to open an application that is not in the Allow list. Use button lock down to prevent application access for a user role.
|
> Button remapping can enable a user to open an application that is not in the Allow list. Use button lock down to prevent application access for a user role.
|
||||||
|
|
||||||
To remap a button in lockdown XML, you supply the button name, the button event (typically "press"), and the product ID for the application the button will open.
|
To remap a button in lockdown XML, you supply the button name, the button event (typically "press"), and the product ID for the application the button will open.
|
||||||
|
|
||||||
``` syntax
|
``` syntax
|
||||||
<ButtonRemapList>
|
<ButtonRemapList>
|
||||||
@ -1199,7 +1199,7 @@ The following example shows how to add a new policy.
|
|||||||
<characteristic type="EnterpriseAssignedAccess">
|
<characteristic type="EnterpriseAssignedAccess">
|
||||||
<characteristic type="AssignedAccess">
|
<characteristic type="AssignedAccess">
|
||||||
<parm name=" AssignedAccessXml" datatype="string"
|
<parm name=" AssignedAccessXml" datatype="string"
|
||||||
value="<?xml version="1.0" encoding="utf-8"?><HandheldLockdown version="1.0"><Default><Apps><Application productId="{5B04B775-356B-4AA0-AAF8-6491FFEA5615}" pinToStart="1"/><Application productId="{5B04B775-356B-4AA0-AAF8-6491FFEA5612}" pinToStart="0"/></Apps><Settings><System name="Microsoft.Themes" /><System name="Microsoft.About" /></Settings><Buttons><ButtonLockdownList><Button name="Start"><ButtonEvent name="Press" /><ButtonEvent name="PressAndHold" /></Button><Button name="Camera"><ButtonEvent name="Press" /><ButtonEvent name="PressAndHold" /></Button><Button name="Search"><ButtonEvent name="Press" /><ButtonEvent name="PressAndHold" /></Button></ButtonLockdownList><ButtonRemapList/></Buttons><MenuItems><DisableMenuItems/></MenuItems></Default><RoleList><Role guid="{76C01983-A872-4C4E-B4C6-321EAC709CEA}" name="Associate"><Apps><Application productId="{5B04B775-356B-4AA0-AAF8-6491FFEA5615}" pinToStart="1"/></Apps><Settings><System name="Microsoft.Themes" /><System name="Microsoft.About" /></Settings><Buttons><ButtonLockdownList><Button name="Start"><ButtonEvent name="Press" /><ButtonEvent name="PressAndHold" /></Button><Button name="Camera"><ButtonEvent name="Press" /><ButtonEvent name="PressAndHold" /></Button></ButtonLockdownList><ButtonRemapList/></Buttons><MenuItems><DisableMenuItems/></MenuItems></Role><Role guid="{8ABB8A10-4418-4467-9E18-99D11FA54E30}" name="Manager"><Apps><Application productId="{5B04B775-356B-4AA0-AAF8-6491FFEA5612}" pinToStart="1"/></Apps><Settings><System name="Microsoft.Themes" /></Settings><Buttons><ButtonLockdownList><Button name="Start"><ButtonEvent name="Press" /><ButtonEvent name="PressAndHold" /></Button></ButtonLockdownList><ButtonRemapList/></Buttons><MenuItems><DisableMenuItems/></MenuItems></Role></RoleList></HandheldLockdown>"/>
|
value="<?xml version="1.0" encoding="utf-8"?><HandheldLockdown version="1.0"><Default><Apps><Application productId="{5B04B775-356B-4AA0-AAF8-6491FFEA5615}" pinToStart="1"/><Application productId="{5B04B775-356B-4AA0-AAF8-6491FFEA5612}" pinToStart="0"/></Apps><Settings><System name="Microsoft.Themes" /><System name="Microsoft.About" /></Settings><Buttons><ButtonLockdownList><Button name="Start"><ButtonEvent name="Press" /><ButtonEvent name="PressAndHold" /></Button><Button name="Camera"><ButtonEvent name="Press" /><ButtonEvent name="PressAndHold" /></Button><Button name="Search"><ButtonEvent name="Press" /><ButtonEvent name="PressAndHold" /></Button></ButtonLockdownList><ButtonRemapList/></Buttons><MenuItems><DisableMenuItems/></MenuItems></Default><RoleList><Role guid="{76C01983-A872-4C4E-B4C6-321EAC709CEA}" name="Associate"><Apps><Application productId="{5B04B775-356B-4AA0-AAF8-6491FFEA5615}" pinToStart="1"/></Apps><Settings><System name="Microsoft.Themes" /><System name="Microsoft.About" /></Settings><Buttons><ButtonLockdownList><Button name="Start"><ButtonEvent name="Press" /><ButtonEvent name="PressAndHold" /></Button><Button name="Camera"><ButtonEvent name="Press" /><ButtonEvent name="PressAndHold" /></Button></ButtonLockdownList><ButtonRemapList/></Buttons><MenuItems><DisableMenuItems/></MenuItems></Role><Role guid="{8ABB8A10-4418-4467-9E18-99D11FA54E30}" name="Manager"><Apps><Application productId="{5B04B775-356B-4AA0-AAF8-6491FFEA5612}" pinToStart="1"/></Apps><Settings><System name="Microsoft.Themes" /></Settings><Buttons><ButtonLockdownList><Button name="Start"><ButtonEvent name="Press" /><ButtonEvent name="PressAndHold" /></Button></ButtonLockdownList><ButtonRemapList/></Buttons><MenuItems><DisableMenuItems/></MenuItems></Role></RoleList></HandheldLockdown>"/>
|
||||||
</characteristic>
|
</characteristic>
|
||||||
</characteristic>
|
</characteristic>
|
||||||
</wap-provisioningdoc>
|
</wap-provisioningdoc>
|
||||||
@ -1237,7 +1237,7 @@ The following example shows how to lock down a device.
|
|||||||
<Target>
|
<Target>
|
||||||
<LocURI>./Vendor/MSFT/EnterpriseAssignedAccess/AssignedAccess/AssignedAccessXml</LocURI>
|
<LocURI>./Vendor/MSFT/EnterpriseAssignedAccess/AssignedAccess/AssignedAccessXml</LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data><?xml version="1.0" encoding="utf-8"?><HandheldLockdown version="1.0"><Default><Apps><Application productId="{5B04B775-356B-4AA0-AAF8-6491FFEA5615}" pinToStart="1"/><Application productId="{5B04B775-356B-4AA0-AAF8-6491FFEA5612}" pinToStart="2"/></Apps><Settings><System name="Microsoft.Themes" /><System name="Microsoft.About" /></Settings><Buttons><Button name="Start" disableEvents="PressAndHold" /><Button name="Camera" disableEvents="All" /><Button name="Search" disableEvents="All" /></Buttons><MenuItems><DisableMenuItems/></MenuItems></Default><RoleList><Role guid="{76C01983-A872-4C4E-B4C6-321EAC709CEA}" name="Associate"><Apps><Application productId="{5B04B775-356B-4AA0-AAF8-6491FFEA5615}" pinToStart="1"/></Apps><Settings><System name="Microsoft.Themes" /><System name="Microsoft.About" /></Settings><Buttons><Button name="Start" disableEvents="PressAndHold" /><Button name="Camera" disableEvents="All" /></Buttons><MenuItems><DisableMenuItems/></MenuItems></Role><Role guid="{8ABB8A10-4418-4467-9E18-99D11FA54E30}" name="Manager"><Apps><Application productId="{5B04B775-356B-4AA0-AAF8-6491FFEA5612}" pinToStart="1"/></Apps><Settings><System name="Microsoft.Themes" /></Settings><Buttons><Button name="Start" disableEvents="PressAndHold" /></Buttons><MenuItems><DisableMenuItems/></MenuItems></Role></RoleList></HandheldLockdown></Data>
|
<Data><?xml version="1.0" encoding="utf-8"?><HandheldLockdown version="1.0"><Default><Apps><Application productId="{5B04B775-356B-4AA0-AAF8-6491FFEA5615}" pinToStart="1"/><Application productId="{5B04B775-356B-4AA0-AAF8-6491FFEA5612}" pinToStart="2"/></Apps><Settings><System name="Microsoft.Themes" /><System name="Microsoft.About" /></Settings><Buttons><Button name="Start" disableEvents="PressAndHold" /><Button name="Camera" disableEvents="All" /><Button name="Search" disableEvents="All" /></Buttons><MenuItems><DisableMenuItems/></MenuItems></Default><RoleList><Role guid="{76C01983-A872-4C4E-B4C6-321EAC709CEA}" name="Associate"><Apps><Application productId="{5B04B775-356B-4AA0-AAF8-6491FFEA5615}" pinToStart="1"/></Apps><Settings><System name="Microsoft.Themes" /><System name="Microsoft.About" /></Settings><Buttons><Button name="Start" disableEvents="PressAndHold" /><Button name="Camera" disableEvents="All" /></Buttons><MenuItems><DisableMenuItems/></MenuItems></Role><Role guid="{8ABB8A10-4418-4467-9E18-99D11FA54E30}" name="Manager"><Apps><Application productId="{5B04B775-356B-4AA0-AAF8-6491FFEA5612}" pinToStart="1"/></Apps><Settings><System name="Microsoft.Themes" /></Settings><Buttons><Button name="Start" disableEvents="PressAndHold" /></Buttons><MenuItems><DisableMenuItems/></MenuItems></Role></RoleList></HandheldLockdown></Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Add>
|
</Add>
|
||||||
<Final/>
|
<Final/>
|
||||||
|
@ -13,7 +13,7 @@ ms.date: 06/26/2017
|
|||||||
# EnterpriseAssignedAccess XSD
|
# EnterpriseAssignedAccess XSD
|
||||||
|
|
||||||
|
|
||||||
This XSD can be used to validate that the lockdown XML in the <Data> block of the AssignedAccessXML node.
|
This XSD can be used to validate that the lockdown XML in the \<Data\> block of the AssignedAccessXML node.
|
||||||
|
|
||||||
``` syntax
|
``` syntax
|
||||||
<?xml version="1.0" encoding="utf-16LE" ?>
|
<?xml version="1.0" encoding="utf-16LE" ?>
|
||||||
|
@ -60,7 +60,7 @@ The following diagram shows the EnterpriseDataProtection CSP in tree format.
|
|||||||
|
|
||||||
<p style="margin-left: 20px">Here are the steps to create canonical domain names:
|
<p style="margin-left: 20px">Here are the steps to create canonical domain names:
|
||||||
|
|
||||||
1. Transform the ASCII characters (A-Z only) to lower case. For example, Microsoft.COM -> microsoft.com.
|
1. Transform the ASCII characters (A-Z only) to lower case. For example, Microsoft.COM -> microsoft.com.
|
||||||
2. Call [IdnToAscii](https://msdn.microsoft.com/library/windows/desktop/dd318149.aspx) with IDN\_USE\_STD3\_ASCII\_RULES as the flags.
|
2. Call [IdnToAscii](https://msdn.microsoft.com/library/windows/desktop/dd318149.aspx) with IDN\_USE\_STD3\_ASCII\_RULES as the flags.
|
||||||
3. Call [IdnToUnicode](https://msdn.microsoft.com/library/windows/desktop/dd318151.aspx) with no flags set (dwFlags = 0).
|
3. Call [IdnToUnicode](https://msdn.microsoft.com/library/windows/desktop/dd318151.aspx) with no flags set (dwFlags = 0).
|
||||||
|
|
||||||
|
@ -32,7 +32,7 @@ The root node for the EnterpriseExt configuration service provider. Supported op
|
|||||||
Node for setting the custom device ID and string.
|
Node for setting the custom device ID and string.
|
||||||
|
|
||||||
<a href="" id="devicecustomdata-customid"></a>**DeviceCustomData/CustomID**
|
<a href="" id="devicecustomdata-customid"></a>**DeviceCustomData/CustomID**
|
||||||
Any string value as the device ID. This value appears in **Settings** > **About** > **Info**.
|
Any string value as the device ID. This value appears in **Settings** > **About** > **Info**.
|
||||||
|
|
||||||
Here's an example for getting custom data.
|
Here's an example for getting custom data.
|
||||||
|
|
||||||
|
@ -593,7 +593,7 @@ Query the device for a specific app subcategory, such as nonStore apps.
|
|||||||
</Get>
|
</Get>
|
||||||
```
|
```
|
||||||
|
|
||||||
The result contains a list of apps, such as <Data>App1/App2/App3</Data>.
|
The result contains a list of apps, such as \<Data>App1/App2/App\</Data\>.
|
||||||
|
|
||||||
Subsequent query for a specific app for its properties.
|
Subsequent query for a specific app for its properties.
|
||||||
|
|
||||||
|
@ -123,7 +123,7 @@ MTS requires calls to be authenticated using an Azure AD OAuth bearer token. The
|
|||||||
|
|
||||||
Here are the details for requesting an authorization token:
|
Here are the details for requesting an authorization token:
|
||||||
|
|
||||||
- Login Authority = https:<span></span>//login.windows.net/<TargetTenantId>
|
- Login Authority = https:<span></span>//login.windows.net/\<TargetTenantId\>
|
||||||
- Resource/audience\* = https:<span></span>//onestore.microsoft.com
|
- Resource/audience\* = https:<span></span>//onestore.microsoft.com
|
||||||
- ClientId = your AAD application client id
|
- ClientId = your AAD application client id
|
||||||
- ClientSecret = your AAD application client secret/key
|
- ClientSecret = your AAD application client secret/key
|
||||||
|
@ -334,7 +334,7 @@ A Get operation on ./Vendor/MSFT/NodeCache/MDM%20SyncML%20Server/Nodes/20/Expect
|
|||||||
A Get operation on the ChangedNodesData returns an encoded XML. Here is example:
|
A Get operation on the ChangedNodesData returns an encoded XML. Here is example:
|
||||||
|
|
||||||
```syntax
|
```syntax
|
||||||
<Nodes><Node Id="10" Uri=""></Node><Node Id="20" Uri="./DevDetail/Ext/Microsoft/DeviceName">U09NRU5FV1ZBTFVF</Node></Nodes>
|
<Nodes><Node Id="10" Uri=""></Node><Node Id="20" Uri="./DevDetail/Ext/Microsoft/DeviceName">U09NRU5FV1ZBTFVF</Node></Nodes>
|
||||||
```
|
```
|
||||||
It represents this:
|
It represents this:
|
||||||
|
|
||||||
|
@ -1420,12 +1420,12 @@ Related policy:
|
|||||||
|
|
||||||
If enabled, you must include URLs to the pages, separating multiple pages using angle brackets in the following format:
|
If enabled, you must include URLs to the pages, separating multiple pages using angle brackets in the following format:
|
||||||
|
|
||||||
<support.contoso.com><support.microsoft.com>
|
<support.contoso.com><support.microsoft.com>
|
||||||
|
|
||||||
If disabled or not configured, the webpages specified in App settings loads as the default Start pages.
|
If disabled or not configured, the webpages specified in App settings loads as the default Start pages.
|
||||||
|
|
||||||
Version 1703 or later:
|
Version 1703 or later:
|
||||||
If you do not want to send traffic to Microsoft, enable this policy and use the <about:blank> value, which honors domain- and non-domain-joined devices, when it is the only configured URL.
|
If you do not want to send traffic to Microsoft, enable this policy and use the <about:blank> value, which honors domain- and non-domain-joined devices, when it is the only configured URL.
|
||||||
|
|
||||||
Version 1809:
|
Version 1809:
|
||||||
If enabled, and you select either Start page, New Tab page, or previous page in the Configure Open Microsoft Edge With policy, Microsoft Edge ignores the Configure Start Pages policy. If not configured or you set the Configure Open Microsoft Edge With policy to a specific page or pages, Microsoft Edge uses the Configure Start Pages policy.
|
If enabled, and you select either Start page, New Tab page, or previous page in the Configure Open Microsoft Edge With policy, Microsoft Edge ignores the Configure Start Pages policy. If not configured or you set the Configure Open Microsoft Edge With policy to a specific page or pages, Microsoft Edge uses the Configure Start Pages policy.
|
||||||
@ -10603,12 +10603,12 @@ Related policy:
|
|||||||
|
|
||||||
If enabled, you must include URLs to the pages, separating multiple pages using angle brackets in the following format:
|
If enabled, you must include URLs to the pages, separating multiple pages using angle brackets in the following format:
|
||||||
|
|
||||||
<support.contoso.com><support.microsoft.com>
|
<support.contoso.com><support.microsoft.com>
|
||||||
|
|
||||||
If disabled or not configured, the webpages specified in App settings loads as the default Start pages.
|
If disabled or not configured, the webpages specified in App settings loads as the default Start pages.
|
||||||
|
|
||||||
Version 1703 or later:
|
Version 1703 or later:
|
||||||
If you do not want to send traffic to Microsoft, enable this policy and use the <about:blank> value, which honors domain- and non-domain-joined devices, when it is the only configured URL.
|
If you do not want to send traffic to Microsoft, enable this policy and use the <about:blank> value, which honors domain- and non-domain-joined devices, when it is the only configured URL.
|
||||||
|
|
||||||
Version 1809:
|
Version 1809:
|
||||||
If enabled, and you select either Start page, New Tab page, or previous page in the Configure Open Microsoft Edge With policy, Microsoft Edge ignores the Configure Start Pages policy. If not configured or you set the Configure Open Microsoft Edge With policy to a specific page or pages, Microsoft Edge uses the Configure Start Pages policy.
|
If enabled, and you select either Start page, New Tab page, or previous page in the Configure Open Microsoft Edge With policy, Microsoft Edge ignores the Configure Start Pages policy. If not configured or you set the Configure Open Microsoft Edge With policy to a specific page or pages, Microsoft Edge uses the Configure Start Pages policy.
|
||||||
@ -22414,12 +22414,12 @@ Related policy:
|
|||||||
|
|
||||||
If enabled, you must include URLs to the pages, separating multiple pages using angle brackets in the following format:
|
If enabled, you must include URLs to the pages, separating multiple pages using angle brackets in the following format:
|
||||||
|
|
||||||
<support.contoso.com><support.microsoft.com>
|
<support.contoso.com><support.microsoft.com>
|
||||||
|
|
||||||
If disabled or not configured, the webpages specified in App settings loads as the default Start pages.
|
If disabled or not configured, the webpages specified in App settings loads as the default Start pages.
|
||||||
|
|
||||||
Version 1703 or later:
|
Version 1703 or later:
|
||||||
If you do not want to send traffic to Microsoft, enable this policy and use the <about:blank> value, which honors domain- and non-domain-joined devices, when it is the only configured URL.
|
If you do not want to send traffic to Microsoft, enable this policy and use the <about:blank> value, which honors domain- and non-domain-joined devices, when it is the only configured URL.
|
||||||
|
|
||||||
Version 1809:
|
Version 1809:
|
||||||
If enabled, and you select either Start page, New Tab page, or previous page in the Configure Open Microsoft Edge With policy, Microsoft Edge ignores the Configure Start Pages policy. If not configured or you set the Configure Open Microsoft Edge With policy to a specific page or pages, Microsoft Edge uses the Configure Start Pages policy.
|
If enabled, and you select either Start page, New Tab page, or previous page in the Configure Open Microsoft Edge With policy, Microsoft Edge ignores the Configure Start Pages policy. If not configured or you set the Configure Open Microsoft Edge With policy to a specific page or pages, Microsoft Edge uses the Configure Start Pages policy.
|
||||||
@ -49724,12 +49724,12 @@ Related policy:
|
|||||||
|
|
||||||
If enabled, you must include URLs to the pages, separating multiple pages using angle brackets in the following format:
|
If enabled, you must include URLs to the pages, separating multiple pages using angle brackets in the following format:
|
||||||
|
|
||||||
<support.contoso.com><support.microsoft.com>
|
<support.contoso.com><support.microsoft.com>
|
||||||
|
|
||||||
If disabled or not configured, the webpages specified in App settings loads as the default Start pages.
|
If disabled or not configured, the webpages specified in App settings loads as the default Start pages.
|
||||||
|
|
||||||
Version 1703 or later:
|
Version 1703 or later:
|
||||||
If you do not want to send traffic to Microsoft, enable this policy and use the <about:blank> value, which honors domain- and non-domain-joined devices, when it is the only configured URL.
|
If you do not want to send traffic to Microsoft, enable this policy and use the <about:blank> value, which honors domain- and non-domain-joined devices, when it is the only configured URL.
|
||||||
|
|
||||||
Version 1809:
|
Version 1809:
|
||||||
If enabled, and you select either Start page, New Tab page, or previous page in the Configure Open Microsoft Edge With policy, Microsoft Edge ignores the Configure Start Pages policy. If not configured or you set the Configure Open Microsoft Edge With policy to a specific page or pages, Microsoft Edge uses the Configure Start Pages policy.
|
If enabled, and you select either Start page, New Tab page, or previous page in the Configure Open Microsoft Edge With policy, Microsoft Edge ignores the Configure Start Pages policy. If not configured or you set the Configure Open Microsoft Edge With policy to a specific page or pages, Microsoft Edge uses the Configure Start Pages policy.
|
||||||
|
@ -176,7 +176,7 @@ The following SyncML examples describe how to set a MDM policy that is defined b
|
|||||||
<Target>
|
<Target>
|
||||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/PublishingAllowServer2</LocURI>
|
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/PublishingAllowServer2</LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data><disabled/></Data>
|
<Data><disabled/></Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Replace>
|
</Replace>
|
||||||
<Final/>
|
<Final/>
|
||||||
@ -340,7 +340,7 @@ The `multiText` element simply corresponds to a REG_MULTISZ registry string and
|
|||||||
<Target>
|
<Target>
|
||||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/VirtualComponentsAllowList</LocURI>
|
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/VirtualComponentsAllowList</LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data><enabled/><data id="Virtualization_JITVAllowList_Prompt" value="C:\QuickPatch\TEST\snot.exeC:\QuickPatch\TEST\foo.exeC:\QuickPatch\TEST\bar.exe"/></Data>
|
<Data><enabled/><data id="Virtualization_JITVAllowList_Prompt" value="C:\QuickPatch\TEST\snot.exeC:\QuickPatch\TEST\foo.exeC:\QuickPatch\TEST\bar.exe"/></Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Replace>
|
</Replace>
|
||||||
<Final/>
|
<Final/>
|
||||||
@ -384,7 +384,7 @@ Variations of the `list` element are dictated by attributes. These attributes ar
|
|||||||
<Target>
|
<Target>
|
||||||
<LocURI>./User/Vendor/MSFT/Policy/Config/InternetExplorer/DisableSecondaryHomePageChange</LocURI>
|
<LocURI>./User/Vendor/MSFT/Policy/Config/InternetExplorer/DisableSecondaryHomePageChange</LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data><Enabled/><Data id="SecondaryHomePagesList" value="http://name1http://name1http://name2http://name2"/></Data>
|
<Data><Enabled/><Data id="SecondaryHomePagesList" value="http://name1http://name1http://name2http://name2"/></Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Replace>
|
</Replace>
|
||||||
<Final/>
|
<Final/>
|
||||||
@ -416,7 +416,7 @@ Variations of the `list` element are dictated by attributes. These attributes ar
|
|||||||
<Target>
|
<Target>
|
||||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/InternetExplorer/DisableUpdateCheck</LocURI>
|
<LocURI>./Device/Vendor/MSFT/Policy/Config/InternetExplorer/DisableUpdateCheck</LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data><Enabled/></Data>
|
<Data><Enabled/></Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Replace>
|
</Replace>
|
||||||
<Final/>
|
<Final/>
|
||||||
@ -470,8 +470,8 @@ Variations of the `list` element are dictated by attributes. These attributes ar
|
|||||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/BitLocker/EncryptionMethodByDriveType</LocURI>
|
<LocURI>./Device/Vendor/MSFT/Policy/Config/BitLocker/EncryptionMethodByDriveType</LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data>
|
<Data>
|
||||||
<enabled/>
|
<enabled/>
|
||||||
<data id="EncryptionMethodWithXtsOsDropDown_Name" value="4"/>
|
<data id="EncryptionMethodWithXtsOsDropDown_Name" value="4"/>
|
||||||
</Data>
|
</Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Replace>
|
</Replace>
|
||||||
@ -507,8 +507,8 @@ Variations of the `list` element are dictated by attributes. These attributes ar
|
|||||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/StreamingAllowReestablishmentInterval</LocURI>
|
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/StreamingAllowReestablishmentInterval</LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data>
|
<Data>
|
||||||
<enabled/>
|
<enabled/>
|
||||||
<data id="Streaming_Reestablishment_Interval_Prompt" value="4"/>
|
<data id="Streaming_Reestablishment_Interval_Prompt" value="4"/>
|
||||||
</Data>
|
</Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Replace>
|
</Replace>
|
||||||
@ -560,8 +560,8 @@ Variations of the `list` element are dictated by attributes. These attributes ar
|
|||||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/DeviceInstallation/PreventInstallationOfMatchingDeviceSetupClasses</LocURI>
|
<LocURI>./Device/Vendor/MSFT/Policy/Config/DeviceInstallation/PreventInstallationOfMatchingDeviceSetupClasses</LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data>
|
<Data>
|
||||||
<enabled/><data id="DeviceInstall_Classes_Deny_Retroactive" value="true"/>
|
<enabled/><data id="DeviceInstall_Classes_Deny_Retroactive" value="true"/>
|
||||||
<Data id="DeviceInstall_Classes_Deny_List" value="1deviceId12deviceId2"/>
|
<Data id="DeviceInstall_Classes_Deny_List" value="1deviceId12deviceId2"/>
|
||||||
</Data>
|
</Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Replace>
|
</Replace>
|
||||||
|
@ -603,41 +603,41 @@ Profile example
|
|||||||
<Target>
|
<Target>
|
||||||
<LocURI>./Vendor/MSFT/VPNv2/VPN_Demo/ProfileXML</LocURI>
|
<LocURI>./Vendor/MSFT/VPNv2/VPN_Demo/ProfileXML</LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data><VPNProfile>
|
<Data><VPNProfile>
|
||||||
<ProfileName>VPN_Demo</ProfileName>
|
<ProfileName>VPN_Demo</ProfileName>
|
||||||
<NativeProfile>
|
<NativeProfile>
|
||||||
<Servers>VPNServer.contoso.com</Servers>
|
<Servers>VPNServer.contoso.com</Servers>
|
||||||
<NativeProtocolType>Automatic</NativeProtocolType>
|
<NativeProtocolType>Automatic</NativeProtocolType>
|
||||||
<Authentication>
|
<Authentication>
|
||||||
<UserMethod>Eap</UserMethod>
|
<UserMethod>Eap</UserMethod>
|
||||||
<Eap>
|
<Eap>
|
||||||
<Configuration>
|
<Configuration>
|
||||||
<EapHostConfig xmlns="http://www.microsoft.com/provisioning/EapHostConfig"> <EapMethod> <Type xmlns="http://www.microsoft.com/provisioning/EapCommon">25</Type> <VendorId xmlns="http://www.microsoft.com/provisioning/EapCommon">0</VendorId> <VendorType xmlns="http://www.microsoft.com/provisioning/EapCommon">0</VendorType> <AuthorId xmlns="http://www.microsoft.com/provisioning/EapCommon">0</AuthorId> </EapMethod> <Config xmlns="http://www.microsoft.com/provisioning/EapHostConfig"> <Eap xmlns="http://www.microsoft.com/provisioning/BaseEapConnectionPropertiesV1"> <Type>25</Type> <EapType xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV1"> <ServerValidation> <DisableUserPromptForServerValidation>false</DisableUserPromptForServerValidation> <ServerNames></ServerNames> </ServerValidation> <FastReconnect>true</FastReconnect> <InnerEapOptional>false</InnerEapOptional> <Eap xmlns="http://www.microsoft.com/provisioning/BaseEapConnectionPropertiesV1"> <Type>13</Type> <EapType xmlns="http://www.microsoft.com/provisioning/EapTlsConnectionPropertiesV1"> <CredentialsSource> <CertificateStore> <SimpleCertSelection>false</SimpleCertSelection> </CertificateStore> </CredentialsSource> <ServerValidation> <DisableUserPromptForServerValidation>false</DisableUserPromptForServerValidation> <ServerNames></ServerNames> </ServerValidation> <DifferentUsername>false</DifferentUsername> <PerformServerValidation xmlns="http://www.microsoft.com/provisioning/EapTlsConnectionPropertiesV2">false</PerformServerValidation> <AcceptServerName xmlns="http://www.microsoft.com/provisioning/EapTlsConnectionPropertiesV2">false</AcceptServerName> <TLSExtensions xmlns="http://www.microsoft.com/provisioning/EapTlsConnectionPropertiesV2"> <FilteringInfo xmlns="http://www.microsoft.com/provisioning/EapTlsConnectionPropertiesV3"> <EKUMapping> <EKUMap> <EKUName>Unknown Key Usage</EKUName> <EKUOID>1.3.6.1.4.1.311.87</EKUOID> </EKUMap> </EKUMapping> <ClientAuthEKUList Enabled="true"> <EKUMapInList> <EKUName>Unknown Key Usage</EKUName> </EKUMapInList> </ClientAuthEKUList> </FilteringInfo> </TLSExtensions> </EapType> </Eap> <EnableQuarantineChecks>false</EnableQuarantineChecks> <RequireCryptoBinding>false</RequireCryptoBinding> <PeapExtensions> <PerformServerValidation xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV2">false</PerformServerValidation> <AcceptServerName xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV2">false</AcceptServerName> </PeapExtensions> </EapType> </Eap> </Config> </EapHostConfig>
|
<EapHostConfig xmlns="http://www.microsoft.com/provisioning/EapHostConfig"> <EapMethod> <Type xmlns="http://www.microsoft.com/provisioning/EapCommon">25</Type> <VendorId xmlns="http://www.microsoft.com/provisioning/EapCommon">0</VendorId> <VendorType xmlns="http://www.microsoft.com/provisioning/EapCommon">0</VendorType> <AuthorId xmlns="http://www.microsoft.com/provisioning/EapCommon">0</AuthorId> </EapMethod> <Config xmlns="http://www.microsoft.com/provisioning/EapHostConfig"> <Eap xmlns="http://www.microsoft.com/provisioning/BaseEapConnectionPropertiesV1"> <Type>25</Type> <EapType xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV1"> <ServerValidation> <DisableUserPromptForServerValidation>false</DisableUserPromptForServerValidation> <ServerNames></ServerNames> </ServerValidation> <FastReconnect>true</FastReconnect> <InnerEapOptional>false</InnerEapOptional> <Eap xmlns="http://www.microsoft.com/provisioning/BaseEapConnectionPropertiesV1"> <Type>13</Type> <EapType xmlns="http://www.microsoft.com/provisioning/EapTlsConnectionPropertiesV1"> <CredentialsSource> <CertificateStore> <SimpleCertSelection>false</SimpleCertSelection> </CertificateStore> </CredentialsSource> <ServerValidation> <DisableUserPromptForServerValidation>false</DisableUserPromptForServerValidation> <ServerNames></ServerNames> </ServerValidation> <DifferentUsername>false</DifferentUsername> <PerformServerValidation xmlns="http://www.microsoft.com/provisioning/EapTlsConnectionPropertiesV2">false</PerformServerValidation> <AcceptServerName xmlns="http://www.microsoft.com/provisioning/EapTlsConnectionPropertiesV2">false</AcceptServerName> <TLSExtensions xmlns="http://www.microsoft.com/provisioning/EapTlsConnectionPropertiesV2"> <FilteringInfo xmlns="http://www.microsoft.com/provisioning/EapTlsConnectionPropertiesV3"> <EKUMapping> <EKUMap> <EKUName>Unknown Key Usage</EKUName> <EKUOID>1.3.6.1.4.1.311.87</EKUOID> </EKUMap> </EKUMapping> <ClientAuthEKUList Enabled="true"> <EKUMapInList> <EKUName>Unknown Key Usage</EKUName> </EKUMapInList> </ClientAuthEKUList> </FilteringInfo> </TLSExtensions> </EapType> </Eap> <EnableQuarantineChecks>false</EnableQuarantineChecks> <RequireCryptoBinding>false</RequireCryptoBinding> <PeapExtensions> <PerformServerValidation xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV2">false</PerformServerValidation> <AcceptServerName xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV2">false</AcceptServerName> </PeapExtensions> </EapType> </Eap> </Config> </EapHostConfig>
|
||||||
</Configuration>
|
</Configuration>
|
||||||
</Eap>
|
</Eap>
|
||||||
</Authentication>
|
</Authentication>
|
||||||
<RoutingPolicyType>SplitTunnel</RoutingPolicyType>
|
<RoutingPolicyType>SplitTunnel</RoutingPolicyType>
|
||||||
</NativeProfile>
|
</NativeProfile>
|
||||||
<DomainNameInformation>
|
<DomainNameInformation>
|
||||||
<DomainName>.contoso.com</DomainName>
|
<DomainName>.contoso.com</DomainName>
|
||||||
<DNSServers>10.5.5.5</DNSServers>
|
<DNSServers>10.5.5.5</DNSServers>
|
||||||
</DomainNameInformation>
|
</DomainNameInformation>
|
||||||
<TrafficFilter>
|
<TrafficFilter>
|
||||||
<App>%ProgramFiles%\Internet Explorer\iexplore.exe</App>
|
<App>%ProgramFiles%\Internet Explorer\iexplore.exe</App>
|
||||||
</TrafficFilter>
|
</TrafficFilter>
|
||||||
<TrafficFilter>
|
<TrafficFilter>
|
||||||
<App>Microsoft.MicrosoftEdge_8wekyb3d8bbwe</App>
|
<App>Microsoft.MicrosoftEdge_8wekyb3d8bbwe</App>
|
||||||
</TrafficFilter>
|
</TrafficFilter>
|
||||||
<Route>
|
<Route>
|
||||||
<Address>10.0.0.0</Address>
|
<Address>10.0.0.0</Address>
|
||||||
<PrefixSize>8</PrefixSize>
|
<PrefixSize>8</PrefixSize>
|
||||||
</Route>
|
</Route>
|
||||||
<Route>
|
<Route>
|
||||||
<Address>25.0.0.0</Address>
|
<Address>25.0.0.0</Address>
|
||||||
<PrefixSize>8</PrefixSize>
|
<PrefixSize>8</PrefixSize>
|
||||||
</Route>
|
</Route>
|
||||||
<RememberCredentials>true</RememberCredentials>
|
<RememberCredentials>true</RememberCredentials>
|
||||||
</VPNProfile></Data>
|
</VPNProfile></Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Add>
|
</Add>
|
||||||
|
|
||||||
@ -1166,7 +1166,7 @@ PluginPackageFamilyName
|
|||||||
<Target>
|
<Target>
|
||||||
<LocURI>./Vendor/MSFT/VPNv2/VPNProfileName/PluginProfile/CustomConfiguration</LocURI>
|
<LocURI>./Vendor/MSFT/VPNv2/VPNProfileName/PluginProfile/CustomConfiguration</LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data><pluginschema><ipAddress>auto</ipAddress><port>443</port><networksettings><routes><includev4><route><address>172.10.10.0</address><prefix>24</prefix></route></includev4></routes><namespaces><namespace><space>.vpnbackend.com</space><dnsservers><server>172.10.10.11</server></dnsservers></namespace></namespaces></networksettings></pluginschema></Data>
|
<Data><pluginschema><ipAddress>auto</ipAddress><port>443</port><networksettings><routes><includev4><route><address>172.10.10.0</address><prefix>24</prefix></route></includev4></routes><namespaces><namespace><space>.vpnbackend.com</space><dnsservers><server>172.10.10.11</server></dnsservers></namespace></namespaces></networksettings></pluginschema></Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Add>
|
</Add>
|
||||||
```
|
```
|
||||||
|
@ -347,7 +347,7 @@ Here's the XSD for the ProfileXML node in VPNv2 CSP for Windows 10 and some pro
|
|||||||
<PluginProfile>
|
<PluginProfile>
|
||||||
<ServerUrlList>testserver1.contoso.com;testserver2.contoso..com</ServerUrlList>
|
<ServerUrlList>testserver1.contoso.com;testserver2.contoso..com</ServerUrlList>
|
||||||
<PluginPackageFamilyName>JuniperNetworks.JunosPulseVpn_cw5n1h2txyewy</PluginPackageFamilyName>
|
<PluginPackageFamilyName>JuniperNetworks.JunosPulseVpn_cw5n1h2txyewy</PluginPackageFamilyName>
|
||||||
<CustomConfiguration><pulse-schema><isSingleSignOnCredential>true</isSingleSignOnCredential></pulse-schema></CustomConfiguration>
|
<CustomConfiguration><pulse-schema><isSingleSignOnCredential>true</isSingleSignOnCredential></pulse-schema></CustomConfiguration>
|
||||||
</PluginProfile>
|
</PluginProfile>
|
||||||
<Route>
|
<Route>
|
||||||
<Address>192.168.0.0</Address>
|
<Address>192.168.0.0</Address>
|
||||||
|
@ -23,7 +23,7 @@ Programming considerations:
|
|||||||
- Because the Windows 10 Mobile emulator does not support Wi-Fi, you cannot test the Wi-Fi configuration with an emulator. You can still provision a Wi-Fi network using the WiFi CSP, then check it in the Wi-Fi settings page, but you cannot test the network connectivity in the emulator.
|
- Because the Windows 10 Mobile emulator does not support Wi-Fi, you cannot test the Wi-Fi configuration with an emulator. You can still provision a Wi-Fi network using the WiFi CSP, then check it in the Wi-Fi settings page, but you cannot test the network connectivity in the emulator.
|
||||||
- For WEP, WPA, and WPA2-based networks, include the passkey in the network configuration in plaintext. The passkey is encrypted automatically when it is stored on the device.
|
- For WEP, WPA, and WPA2-based networks, include the passkey in the network configuration in plaintext. The passkey is encrypted automatically when it is stored on the device.
|
||||||
- The SSID of the Wi-Fi network part of the LocURI node must be a valid URI based on RFC 2396. This requires that all non-ASCII characters must be escaped using a %-character. Unicode characters without the necessary escaping are not supported.
|
- The SSID of the Wi-Fi network part of the LocURI node must be a valid URI based on RFC 2396. This requires that all non-ASCII characters must be escaped using a %-character. Unicode characters without the necessary escaping are not supported.
|
||||||
- The <name>*name\_goes\_here*</name><SSIDConfig> must match <SSID><name> *name\_goes\_here*</name></SSID>.
|
- The <name>*name\_goes\_here*</name><SSIDConfig> must match <SSID><name> *name\_goes\_here*</name></SSID>.
|
||||||
- For the WiFi CSP, you cannot use the Replace command unless the node already exists.
|
- For the WiFi CSP, you cannot use the Replace command unless the node already exists.
|
||||||
- Using Proxyis only supported in Windows 10 Mobile. Using this configuration in Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) will result in failure.
|
- Using Proxyis only supported in Windows 10 Mobile. Using this configuration in Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) will result in failure.
|
||||||
|
|
||||||
@ -41,10 +41,10 @@ Identifies the Wi-Fi network configuration. Each Wi-Fi network configuration is
|
|||||||
|
|
||||||
Supported operation is Get.
|
Supported operation is Get.
|
||||||
|
|
||||||
<a href="" id="-ssid-"></a>***<SSID>***
|
<a href="" id="-ssid-"></a>***<SSID>***
|
||||||
Specifies the name of the Wi-Fi network (32 bytes maximum) to create, configure, query, or delete. The name is case sensitive and can be represented in ASCII. The SSID is added when the WlanXML node is added. When the SSID node is deleted, then all the subnodes are also deleted.
|
Specifies the name of the Wi-Fi network (32 bytes maximum) to create, configure, query, or delete. The name is case sensitive and can be represented in ASCII. The SSID is added when the WlanXML node is added. When the SSID node is deleted, then all the subnodes are also deleted.
|
||||||
|
|
||||||
SSID is the name of network you are connecting to, while Profile name is the name of the Profile which contains the WiFi settings information. If the Profile name is not set right in the MDM SyncML, as per the information in the WiFi settings XML, it could lead to some unexpected errors. For example, <LocURI>./Vendor/MSFT/WiFi/Profile/<*MUST BE NAME OF PROFILE AS PER WIFI XML*>/WlanXml</LocURI>.
|
SSID is the name of network you are connecting to, while Profile name is the name of the Profile which contains the WiFi settings information. If the Profile name is not set right in the MDM SyncML, as per the information in the WiFi settings XML, it could lead to some unexpected errors. For example, <LocURI>./Vendor/MSFT/WiFi/Profile/<*MUST BE NAME OF PROFILE AS PER WIFI XML*>/WlanXml</LocURI>.
|
||||||
|
|
||||||
The supported operations are Add, Get, Delete, and Replace.
|
The supported operations are Add, Get, Delete, and Replace.
|
||||||
|
|
||||||
@ -130,7 +130,7 @@ The following example shows how to add PEAP-MSCHAPv2 network with SSID 'MyNetwor
|
|||||||
<Meta>
|
<Meta>
|
||||||
<Format xmlns="syncml:metinf">chr</Format>
|
<Format xmlns="syncml:metinf">chr</Format>
|
||||||
</Meta>
|
</Meta>
|
||||||
<Data><?xml version="1.0"?><WLANProfile xmlns="http://contoso.com/networking/WLAN/profile/v1"><name>MyNetwork</name><SSIDConfig><SSID><hex>412D4D534654574C414E</hex><name>MyNetwork</name></SSID><nonBroadcast>false</nonBroadcast></SSIDConfig><connectionType>ESS</connectionType><connectionMode>manual</connectionMode><MSM><security><authEncryption><authentication>WPA2</authentication><encryption>AES</encryption><useOneX>true</useOneX></authEncryption><OneX xmlns="http://contoso.com/networking/OneX/v1"><authMode>user</authMode><EAPConfig><EapHostConfig xmlns="http://contoso.com/provisioning/EapHostConfig"><EapMethod><Type xmlns="http://contoso.com/provisioning/EapCommon">25</Type><VendorId xmlns="http://contoso.com/provisioning/EapCommon">0</VendorId><VendorType xmlns="http://contoso.com/provisioning/EapCommon">0</VendorType><AuthorId xmlns="http://contoso.com/provisioning/EapCommon">0</AuthorId></EapMethod><Config xmlns="http://contoso.com/provisioning/EapHostConfig"><Eap xmlns="http://contoso.com/provisioning/BaseEapConnectionPropertiesV1"><Type>25</Type><EapType xmlns="http://contoso.com/provisioning/MsPeapConnectionPropertiesV1"><ServerValidation><DisableUserPromptForServerValidation>true</DisableUserPromptForServerValidation><ServerNames></ServerNames></ServerValidation><FastReconnect>true</FastReconnect><InnerEapOptional>false</InnerEapOptional><Eap xmlns="http://contoso.com/provisioning/BaseEapConnectionPropertiesV1"><Type>26</Type><EapType xmlns="http://contoso.com/provisioning/MsChapV2ConnectionPropertiesV1"><UseWinLogonCredentials>false</UseWinLogonCredentials></EapType></Eap><EnableQuarantineChecks>false</EnableQuarantineChecks><RequireCryptoBinding>false</RequireCryptoBinding><PeapExtensions><PerformServerValidation xmlns="http://contoso.com/provisioning/MsPeapConnectionPropertiesV2">false</PerformServerValidation><AcceptServerName xmlns="http://contoso.com/provisioning/MsPeapConnectionPropertiesV2">false</AcceptServerName></PeapExtensions></EapType></Eap></Config></EapHostConfig></EAPConfig></OneX></security></MSM></WLANProfile> </Data>
|
<Data><?xml version="1.0"?><WLANProfile xmlns="http://contoso.com/networking/WLAN/profile/v1"><name>MyNetwork</name><SSIDConfig><SSID><hex>412D4D534654574C414E</hex><name>MyNetwork</name></SSID><nonBroadcast>false</nonBroadcast></SSIDConfig><connectionType>ESS</connectionType><connectionMode>manual</connectionMode><MSM><security><authEncryption><authentication>WPA2</authentication><encryption>AES</encryption><useOneX>true</useOneX></authEncryption><OneX xmlns="http://contoso.com/networking/OneX/v1"><authMode>user</authMode><EAPConfig><EapHostConfig xmlns="http://contoso.com/provisioning/EapHostConfig"><EapMethod><Type xmlns="http://contoso.com/provisioning/EapCommon">25</Type><VendorId xmlns="http://contoso.com/provisioning/EapCommon">0</VendorId><VendorType xmlns="http://contoso.com/provisioning/EapCommon">0</VendorType><AuthorId xmlns="http://contoso.com/provisioning/EapCommon">0</AuthorId></EapMethod><Config xmlns="http://contoso.com/provisioning/EapHostConfig"><Eap xmlns="http://contoso.com/provisioning/BaseEapConnectionPropertiesV1"><Type>25</Type><EapType xmlns="http://contoso.com/provisioning/MsPeapConnectionPropertiesV1"><ServerValidation><DisableUserPromptForServerValidation>true</DisableUserPromptForServerValidation><ServerNames></ServerNames></ServerValidation><FastReconnect>true</FastReconnect><InnerEapOptional>false</InnerEapOptional><Eap xmlns="http://contoso.com/provisioning/BaseEapConnectionPropertiesV1"><Type>26</Type><EapType xmlns="http://contoso.com/provisioning/MsChapV2ConnectionPropertiesV1"><UseWinLogonCredentials>false</UseWinLogonCredentials></EapType></Eap><EnableQuarantineChecks>false</EnableQuarantineChecks><RequireCryptoBinding>false</RequireCryptoBinding><PeapExtensions><PerformServerValidation xmlns="http://contoso.com/provisioning/MsPeapConnectionPropertiesV2">false</PerformServerValidation><AcceptServerName xmlns="http://contoso.com/provisioning/MsPeapConnectionPropertiesV2">false</AcceptServerName></PeapExtensions></EapType></Eap></Config></EapHostConfig></EAPConfig></OneX></security></MSM></WLANProfile> </Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Add>
|
</Add>
|
||||||
<Add>
|
<Add>
|
||||||
@ -215,7 +215,7 @@ The following example shows how to add PEAP-MSCHAPv2 network with SSID ‘MyNetw
|
|||||||
<Meta>
|
<Meta>
|
||||||
<Format xmlns="syncml:metinf">chr</Format>
|
<Format xmlns="syncml:metinf">chr</Format>
|
||||||
</Meta>
|
</Meta>
|
||||||
<Data><?xml version="1.0"?><WLANProfile xmlns="http://www.microsoft.com/networking/WLAN/profile/v1"><name>MyNetwork</name><SSIDConfig><SSID><name>MyNetwork</name></SSID><nonBroadcast>false</nonBroadcast></SSIDConfig><connectionType>ESS</connectionType><connectionMode>manual</connectionMode><MSM><security><authEncryption><authentication>WPA2</authentication><encryption>AES</encryption><useOneX>true</useOneX></authEncryption><OneX xmlns="http://www.microsoft.com/networking/OneX/v1"><authMode>user</authMode><EAPConfig><EapHostConfig xmlns="http://www.microsoft.com/provisioning/EapHostConfig"><EapMethod><Type xmlns="http://www.microsoft.com/provisioning/EapCommon">25</Type><VendorId xmlns="http://www.microsoft.com/provisioning/EapCommon">0</VendorId><VendorType xmlns="http://www.microsoft.com/provisioning/EapCommon">0</VendorType><AuthorId xmlns="http://www.microsoft.com/provisioning/EapCommon">0</AuthorId></EapMethod><Config xmlns="http://www.microsoft.com/provisioning/EapHostConfig"><Eap xmlns="http://www.microsoft.com/provisioning/BaseEapConnectionPropertiesV1"><Type>25</Type><EapType xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV1"><ServerValidation><DisableUserPromptForServerValidation>true</DisableUserPromptForServerValidation><ServerNames></ServerNames><TrustedRootCA> InsertCertThumbPrintHere </TrustedRootCA></ServerValidation><FastReconnect>true</FastReconnect><InnerEapOptional>false</InnerEapOptional><Eap xmlns="http://www.microsoft.com/provisioning/BaseEapConnectionPropertiesV1"><Type>26</Type><EapType xmlns="http://www.microsoft.com/provisioning/MsChapV2ConnectionPropertiesV1"><UseWinLogonCredentials>false</UseWinLogonCredentials></EapType></Eap><EnableQuarantineChecks>false</EnableQuarantineChecks><RequireCryptoBinding>false</RequireCryptoBinding><PeapExtensions><PerformServerValidation xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV2">true</PerformServerValidation><AcceptServerName xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV2">false</AcceptServerName></PeapExtensions></EapType></Eap></Config></EapHostConfig></EAPConfig></OneX></security></MSM></WLANProfile> </Data>
|
<Data><?xml version="1.0"?><WLANProfile xmlns="http://www.microsoft.com/networking/WLAN/profile/v1"><name>MyNetwork</name><SSIDConfig><SSID><name>MyNetwork</name></SSID><nonBroadcast>false</nonBroadcast></SSIDConfig><connectionType>ESS</connectionType><connectionMode>manual</connectionMode><MSM><security><authEncryption><authentication>WPA2</authentication><encryption>AES</encryption><useOneX>true</useOneX></authEncryption><OneX xmlns="http://www.microsoft.com/networking/OneX/v1"><authMode>user</authMode><EAPConfig><EapHostConfig xmlns="http://www.microsoft.com/provisioning/EapHostConfig"><EapMethod><Type xmlns="http://www.microsoft.com/provisioning/EapCommon">25</Type><VendorId xmlns="http://www.microsoft.com/provisioning/EapCommon">0</VendorId><VendorType xmlns="http://www.microsoft.com/provisioning/EapCommon">0</VendorType><AuthorId xmlns="http://www.microsoft.com/provisioning/EapCommon">0</AuthorId></EapMethod><Config xmlns="http://www.microsoft.com/provisioning/EapHostConfig"><Eap xmlns="http://www.microsoft.com/provisioning/BaseEapConnectionPropertiesV1"><Type>25</Type><EapType xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV1"><ServerValidation><DisableUserPromptForServerValidation>true</DisableUserPromptForServerValidation><ServerNames></ServerNames><TrustedRootCA> InsertCertThumbPrintHere </TrustedRootCA></ServerValidation><FastReconnect>true</FastReconnect><InnerEapOptional>false</InnerEapOptional><Eap xmlns="http://www.microsoft.com/provisioning/BaseEapConnectionPropertiesV1"><Type>26</Type><EapType xmlns="http://www.microsoft.com/provisioning/MsChapV2ConnectionPropertiesV1"><UseWinLogonCredentials>false</UseWinLogonCredentials></EapType></Eap><EnableQuarantineChecks>false</EnableQuarantineChecks><RequireCryptoBinding>false</RequireCryptoBinding><PeapExtensions><PerformServerValidation xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV2">true</PerformServerValidation><AcceptServerName xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV2">false</AcceptServerName></PeapExtensions></EapType></Eap></Config></EapHostConfig></EAPConfig></OneX></security></MSM></WLANProfile> </Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Add>
|
</Add>
|
||||||
</Atomic>
|
</Atomic>
|
||||||
|
@ -205,136 +205,136 @@ The following example shows an ADMX file in SyncML format:
|
|||||||
<Target>
|
<Target>
|
||||||
<LocURI>./Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/ContosoCompanyApp/Policy/AppAdmxFile01</LocURI>
|
<LocURI>./Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/ContosoCompanyApp/Policy/AppAdmxFile01</LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data><policyDefinitions revision="1.0" schemaVersion="1.0">
|
<Data><policyDefinitions revision="1.0" schemaVersion="1.0">
|
||||||
<categories>
|
<categories>
|
||||||
<category name="ParentCategoryArea"/>
|
<category name="ParentCategoryArea"/>
|
||||||
<category name="Category1">
|
<category name="Category1">
|
||||||
<parentCategory ref="ParentCategoryArea" />
|
<parentCategory ref="ParentCategoryArea" />
|
||||||
</category>
|
</category>
|
||||||
<category name="Category2">
|
<category name="Category2">
|
||||||
<parentCategory ref="ParentCategoryArea" />
|
<parentCategory ref="ParentCategoryArea" />
|
||||||
</category>
|
</category>
|
||||||
<category name="Category3">
|
<category name="Category3">
|
||||||
<parentCategory ref="Category2" />
|
<parentCategory ref="Category2" />
|
||||||
</category>
|
</category>
|
||||||
</categories>
|
</categories>
|
||||||
<policies>
|
<policies>
|
||||||
<policy name="L_PolicyConfigurationMode" class="Machine" displayName="$(string.L_PolicyConfigurationMode)" explainText="$(string.L_ExplainText_ConfigurationMode)" presentation="$(presentation.L_PolicyConfigurationMode)" key="software\policies\contoso\companyApp" valueName="configurationmode">
|
<policy name="L_PolicyConfigurationMode" class="Machine" displayName="$(string.L_PolicyConfigurationMode)" explainText="$(string.L_ExplainText_ConfigurationMode)" presentation="$(presentation.L_PolicyConfigurationMode)" key="software\policies\contoso\companyApp" valueName="configurationmode">
|
||||||
<parentCategory ref="Category1" />
|
<parentCategory ref="Category1" />
|
||||||
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
||||||
<enabledValue>
|
<enabledValue>
|
||||||
<decimal value="1" />
|
<decimal value="1" />
|
||||||
</enabledValue>
|
</enabledValue>
|
||||||
<disabledValue>
|
<disabledValue>
|
||||||
<decimal value="0" />
|
<decimal value="0" />
|
||||||
</disabledValue>
|
</disabledValue>
|
||||||
<elements>
|
<elements>
|
||||||
<text id="L_ServerAddressInternal_VALUE" key="software\policies\contoso\companyApp" valueName="serveraddressinternal" required="true" />
|
<text id="L_ServerAddressInternal_VALUE" key="software\policies\contoso\companyApp" valueName="serveraddressinternal" required="true" />
|
||||||
<text id="L_ServerAddressExternal_VALUE" key="software\policies\contoso\companyApp" valueName="serveraddressexternal" required="true" />
|
<text id="L_ServerAddressExternal_VALUE" key="software\policies\contoso\companyApp" valueName="serveraddressexternal" required="true" />
|
||||||
</elements>
|
</elements>
|
||||||
</policy>
|
</policy>
|
||||||
<policy name="L_PolicyEnableSIPHighSecurityMode" class="Machine" displayName="$(string.L_PolicyEnableSIPHighSecurityMode)" explainText="$(string.L_ExplainText_EnableSIPHighSecurityMode)" presentation="$(presentation.L_PolicyEnableSIPHighSecurityMode)" key="software\policies\contoso\companyApp" valueName="enablesiphighsecuritymode">
|
<policy name="L_PolicyEnableSIPHighSecurityMode" class="Machine" displayName="$(string.L_PolicyEnableSIPHighSecurityMode)" explainText="$(string.L_ExplainText_EnableSIPHighSecurityMode)" presentation="$(presentation.L_PolicyEnableSIPHighSecurityMode)" key="software\policies\contoso\companyApp" valueName="enablesiphighsecuritymode">
|
||||||
<parentCategory ref="Category1" />
|
<parentCategory ref="Category1" />
|
||||||
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
||||||
<enabledValue>
|
<enabledValue>
|
||||||
<decimal value="1" />
|
<decimal value="1" />
|
||||||
</enabledValue>
|
</enabledValue>
|
||||||
<disabledValue>
|
<disabledValue>
|
||||||
<decimal value="0" />
|
<decimal value="0" />
|
||||||
</disabledValue>
|
</disabledValue>
|
||||||
</policy>
|
</policy>
|
||||||
<policy name="L_PolicySipCompression" class="Machine" displayName="$(string.L_PolicySipCompression)" explainText="$(string.L_ExplainText_SipCompression)" presentation="$(presentation.L_PolicySipCompression)" key="software\policies\contoso\companyApp">
|
<policy name="L_PolicySipCompression" class="Machine" displayName="$(string.L_PolicySipCompression)" explainText="$(string.L_ExplainText_SipCompression)" presentation="$(presentation.L_PolicySipCompression)" key="software\policies\contoso\companyApp">
|
||||||
<parentCategory ref="Category1" />
|
<parentCategory ref="Category1" />
|
||||||
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
||||||
<elements>
|
<elements>
|
||||||
<enum id="L_PolicySipCompression" valueName="sipcompression">
|
<enum id="L_PolicySipCompression" valueName="sipcompression">
|
||||||
<item displayName="$(string.L_SipCompressionVal0)">
|
<item displayName="$(string.L_SipCompressionVal0)">
|
||||||
<value>
|
<value>
|
||||||
<decimal value="0" />
|
<decimal value="0" />
|
||||||
</value>
|
</value>
|
||||||
</item>
|
</item>
|
||||||
<item displayName="$(string.L_SipCompressionVal1)">
|
<item displayName="$(string.L_SipCompressionVal1)">
|
||||||
<value>
|
<value>
|
||||||
<decimal value="1" />
|
<decimal value="1" />
|
||||||
</value>
|
</value>
|
||||||
</item>
|
</item>
|
||||||
<item displayName="$(string.L_SipCompressionVal2)">
|
<item displayName="$(string.L_SipCompressionVal2)">
|
||||||
<value>
|
<value>
|
||||||
<decimal value="2" />
|
<decimal value="2" />
|
||||||
</value>
|
</value>
|
||||||
</item>
|
</item>
|
||||||
<item displayName="$(string.L_SipCompressionVal3)">
|
<item displayName="$(string.L_SipCompressionVal3)">
|
||||||
<value>
|
<value>
|
||||||
<decimal value="3" />
|
<decimal value="3" />
|
||||||
</value>
|
</value>
|
||||||
</item>
|
</item>
|
||||||
</enum>
|
</enum>
|
||||||
</elements>
|
</elements>
|
||||||
</policy>
|
</policy>
|
||||||
<policy name="L_PolicyPreventRun" class="Machine" displayName="$(string.L_PolicyPreventRun)" explainText="$(string.L_ExplainText_PreventRun)" presentation="$(presentation.L_PolicyPreventRun)" key="software\policies\contoso\companyApp" valueName="preventrun">
|
<policy name="L_PolicyPreventRun" class="Machine" displayName="$(string.L_PolicyPreventRun)" explainText="$(string.L_ExplainText_PreventRun)" presentation="$(presentation.L_PolicyPreventRun)" key="software\policies\contoso\companyApp" valueName="preventrun">
|
||||||
<parentCategory ref="Category1" />
|
<parentCategory ref="Category1" />
|
||||||
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
||||||
<enabledValue>
|
<enabledValue>
|
||||||
<decimal value="1" />
|
<decimal value="1" />
|
||||||
</enabledValue>
|
</enabledValue>
|
||||||
<disabledValue>
|
<disabledValue>
|
||||||
<decimal value="0" />
|
<decimal value="0" />
|
||||||
</disabledValue>
|
</disabledValue>
|
||||||
</policy>
|
</policy>
|
||||||
<policy name="L_PolicyConfiguredServerCheckValues" class="Machine" displayName="$(string.L_PolicyConfiguredServerCheckValues)" explainText="$(string.L_ExplainText_ConfiguredServerCheckValues)" presentation="$(presentation.L_PolicyConfiguredServerCheckValues)" key="software\policies\contoso\companyApp">
|
<policy name="L_PolicyConfiguredServerCheckValues" class="Machine" displayName="$(string.L_PolicyConfiguredServerCheckValues)" explainText="$(string.L_ExplainText_ConfiguredServerCheckValues)" presentation="$(presentation.L_PolicyConfiguredServerCheckValues)" key="software\policies\contoso\companyApp">
|
||||||
<parentCategory ref="Category2" />
|
<parentCategory ref="Category2" />
|
||||||
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
||||||
<elements>
|
<elements>
|
||||||
<text id="L_ConfiguredServerCheckValues_VALUE" valueName="configuredservercheckvalues" required="true" />
|
<text id="L_ConfiguredServerCheckValues_VALUE" valueName="configuredservercheckvalues" required="true" />
|
||||||
</elements>
|
</elements>
|
||||||
</policy>
|
</policy>
|
||||||
<policy name="L_PolicySipCompression_1" class="User" displayName="$(string.L_PolicySipCompression)" explainText="$(string.L_ExplainText_SipCompression)" presentation="$(presentation.L_PolicySipCompression_1)" key="software\policies\contoso\companyApp">
|
<policy name="L_PolicySipCompression_1" class="User" displayName="$(string.L_PolicySipCompression)" explainText="$(string.L_ExplainText_SipCompression)" presentation="$(presentation.L_PolicySipCompression_1)" key="software\policies\contoso\companyApp">
|
||||||
<parentCategory ref="Category2" />
|
<parentCategory ref="Category2" />
|
||||||
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
||||||
<elements>
|
<elements>
|
||||||
<enum id="L_PolicySipCompression" valueName="sipcompression">
|
<enum id="L_PolicySipCompression" valueName="sipcompression">
|
||||||
<item displayName="$(string.L_SipCompressionVal0)">
|
<item displayName="$(string.L_SipCompressionVal0)">
|
||||||
<value>
|
<value>
|
||||||
<decimal value="0" />
|
<decimal value="0" />
|
||||||
</value>
|
</value>
|
||||||
</item>
|
</item>
|
||||||
<item displayName="$(string.L_SipCompressionVal1)">
|
<item displayName="$(string.L_SipCompressionVal1)">
|
||||||
<value>
|
<value>
|
||||||
<decimal value="1" />
|
<decimal value="1" />
|
||||||
</value>
|
</value>
|
||||||
</item>
|
</item>
|
||||||
<item displayName="$(string.L_SipCompressionVal2)">
|
<item displayName="$(string.L_SipCompressionVal2)">
|
||||||
<value>
|
<value>
|
||||||
<decimal value="2" />
|
<decimal value="2" />
|
||||||
</value>
|
</value>
|
||||||
</item>
|
</item>
|
||||||
<item displayName="$(string.L_SipCompressionVal3)">
|
<item displayName="$(string.L_SipCompressionVal3)">
|
||||||
<value>
|
<value>
|
||||||
<decimal value="3" />
|
<decimal value="3" />
|
||||||
</value>
|
</value>
|
||||||
</item>
|
</item>
|
||||||
</enum>
|
</enum>
|
||||||
</elements>
|
</elements>
|
||||||
</policy>
|
</policy>
|
||||||
<policy name="L_PolicyPreventRun_1" class="User" displayName="$(string.L_PolicyPreventRun)" explainText="$(string.L_ExplainText_PreventRun)" presentation="$(presentation.L_PolicyPreventRun_1)" key="software\policies\contoso\companyApp" valueName="preventrun">
|
<policy name="L_PolicyPreventRun_1" class="User" displayName="$(string.L_PolicyPreventRun)" explainText="$(string.L_ExplainText_PreventRun)" presentation="$(presentation.L_PolicyPreventRun_1)" key="software\policies\contoso\companyApp" valueName="preventrun">
|
||||||
<parentCategory ref="Category3" />
|
<parentCategory ref="Category3" />
|
||||||
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
||||||
<enabledValue>
|
<enabledValue>
|
||||||
<decimal value="1" />
|
<decimal value="1" />
|
||||||
</enabledValue>
|
</enabledValue>
|
||||||
<disabledValue>
|
<disabledValue>
|
||||||
<decimal value="0" />
|
<decimal value="0" />
|
||||||
</disabledValue>
|
</disabledValue>
|
||||||
</policy>
|
</policy>
|
||||||
<policy name="L_PolicyGalDownloadInitialDelay_1" class="User" displayName="$(string.L_PolicyGalDownloadInitialDelay)" explainText="$(string.L_ExplainText_GalDownloadInitialDelay)" presentation="$(presentation.L_PolicyGalDownloadInitialDelay_1)" key="software\policies\contoso\companyApp">
|
<policy name="L_PolicyGalDownloadInitialDelay_1" class="User" displayName="$(string.L_PolicyGalDownloadInitialDelay)" explainText="$(string.L_ExplainText_GalDownloadInitialDelay)" presentation="$(presentation.L_PolicyGalDownloadInitialDelay_1)" key="software\policies\contoso\companyApp">
|
||||||
<parentCategory ref="Category3" />
|
<parentCategory ref="Category3" />
|
||||||
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
||||||
<elements>
|
<elements>
|
||||||
<decimal id="L_GalDownloadInitialDelay_VALUE" valueName="galdownloadinitialdelay" minValue="0" required="true" />
|
<decimal id="L_GalDownloadInitialDelay_VALUE" valueName="galdownloadinitialdelay" minValue="0" required="true" />
|
||||||
</elements>
|
</elements>
|
||||||
</policy>
|
</policy>
|
||||||
</policies>
|
</policies>
|
||||||
</policyDefinitions></Data>
|
</policyDefinitions></Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Add>
|
</Add>
|
||||||
<Final/>
|
<Final/>
|
||||||
@ -423,7 +423,7 @@ The following examples describe how to set an ADMX-ingested app policy.
|
|||||||
<Target>
|
<Target>
|
||||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/ContosoCompanyApp~ Policy~ParentCategoryArea~Category1/L_PolicyConfigurationMode</LocURI>
|
<LocURI>./Device/Vendor/MSFT/Policy/Config/ContosoCompanyApp~ Policy~ParentCategoryArea~Category1/L_PolicyConfigurationMode</LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data><enabled/><data id="L_ServerAddressInternal_VALUE" value="TextValue1"/><data id="L_ServerAddressExternal_VALUE" value="TextValue2"/></Data>
|
<Data><enabled/><data id="L_ServerAddressInternal_VALUE" value="TextValue1"/><data id="L_ServerAddressExternal_VALUE" value="TextValue2"/></Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Replace>
|
</Replace>
|
||||||
<Final/>
|
<Final/>
|
||||||
@ -457,7 +457,7 @@ The following examples describe how to set an ADMX-ingested app policy.
|
|||||||
<Target>
|
<Target>
|
||||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/ContosoCompanyApp~ Policy~ParentCategoryArea~Category1/L_PolicyConfigurationMode</LocURI>
|
<LocURI>./Device/Vendor/MSFT/Policy/Config/ContosoCompanyApp~ Policy~ParentCategoryArea~Category1/L_PolicyConfigurationMode</LocURI>
|
||||||
</Target>
|
</Target>
|
||||||
<Data><disabled/></Data>
|
<Data><disabled/></Data>
|
||||||
</Item>
|
</Item>
|
||||||
</Replace>
|
</Replace>
|
||||||
<Final/>
|
<Final/>
|
||||||
|
@ -65,7 +65,7 @@ To perform a "wipe and persist" reset, preserving the provisioning applied to th
|
|||||||
## Reset using the UI
|
## Reset using the UI
|
||||||
|
|
||||||
|
|
||||||
1. On your mobile device, go to **Settings** > **System** > **About** > **Reset your Phone**
|
1. On your mobile device, go to **Settings** > **System** > **About** > **Reset your Phone**
|
||||||
|
|
||||||
2. When you tap **Reset your phone**, the dialog box will present an option to **Also remove provisioned content** if:
|
2. When you tap **Reset your phone**, the dialog box will present an option to **Also remove provisioned content** if:
|
||||||
|
|
||||||
|
@ -32,54 +32,54 @@ $nameSpaceName="root\cimv2\mdm\dmmap"
|
|||||||
$className="MDM_AssignedAccess"
|
$className="MDM_AssignedAccess"
|
||||||
$obj = Get-CimInstance -Namespace $namespaceName -ClassName $className
|
$obj = Get-CimInstance -Namespace $namespaceName -ClassName $className
|
||||||
$obj.Configuration = @"
|
$obj.Configuration = @"
|
||||||
<?xml version="1.0" encoding="utf-8" ?>
|
<?xml version="1.0" encoding="utf-8" ?>
|
||||||
<AssignedAccessConfiguration xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config">
|
<AssignedAccessConfiguration xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config">
|
||||||
<Profiles>
|
<Profiles>
|
||||||
<Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}">
|
<Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}">
|
||||||
<AllAppsList>
|
<AllAppsList>
|
||||||
<AllowedApps>
|
<AllowedApps>
|
||||||
<App AppUserModelId="Microsoft.ZuneMusic_8wekyb3d8bbwe!Microsoft.ZuneMusic" />
|
<App AppUserModelId="Microsoft.ZuneMusic_8wekyb3d8bbwe!Microsoft.ZuneMusic" />
|
||||||
<App AppUserModelId="Microsoft.ZuneVideo_8wekyb3d8bbwe!Microsoft.ZuneVideo" />
|
<App AppUserModelId="Microsoft.ZuneVideo_8wekyb3d8bbwe!Microsoft.ZuneVideo" />
|
||||||
<App AppUserModelId="Microsoft.Windows.Photos_8wekyb3d8bbwe!App" />
|
<App AppUserModelId="Microsoft.Windows.Photos_8wekyb3d8bbwe!App" />
|
||||||
<App AppUserModelId="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
<App AppUserModelId="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||||
<App AppUserModelId="Microsoft.WindowsCalculator_8wekyb3d8bbwe!App" />
|
<App AppUserModelId="Microsoft.WindowsCalculator_8wekyb3d8bbwe!App" />
|
||||||
<App DesktopAppPath="%windir%\system32\mspaint.exe" />
|
<App DesktopAppPath="%windir%\system32\mspaint.exe" />
|
||||||
<App DesktopAppPath="C:\Windows\System32\notepad.exe" />
|
<App DesktopAppPath="C:\Windows\System32\notepad.exe" />
|
||||||
</AllowedApps>
|
</AllowedApps>
|
||||||
</AllAppsList>
|
</AllAppsList>
|
||||||
<StartLayout>
|
<StartLayout>
|
||||||
<![CDATA[<LayoutModificationTemplate xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout" Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
|
<![CDATA[<LayoutModificationTemplate xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout" Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
|
||||||
<LayoutOptions StartTileGroupCellWidth="6" />
|
<LayoutOptions StartTileGroupCellWidth="6" />
|
||||||
<DefaultLayoutOverride>
|
<DefaultLayoutOverride>
|
||||||
<StartLayoutCollection>
|
<StartLayoutCollection>
|
||||||
<defaultlayout:StartLayout GroupCellWidth="6">
|
<defaultlayout:StartLayout GroupCellWidth="6">
|
||||||
<start:Group Name="Group1">
|
<start:Group Name="Group1">
|
||||||
<start:Tile Size="4x4" Column="0" Row="0" AppUserModelID="Microsoft.ZuneMusic_8wekyb3d8bbwe!Microsoft.ZuneMusic" />
|
<start:Tile Size="4x4" Column="0" Row="0" AppUserModelID="Microsoft.ZuneMusic_8wekyb3d8bbwe!Microsoft.ZuneMusic" />
|
||||||
<start:Tile Size="2x2" Column="4" Row="2" AppUserModelID="Microsoft.ZuneVideo_8wekyb3d8bbwe!Microsoft.ZuneVideo" />
|
<start:Tile Size="2x2" Column="4" Row="2" AppUserModelID="Microsoft.ZuneVideo_8wekyb3d8bbwe!Microsoft.ZuneVideo" />
|
||||||
<start:Tile Size="2x2" Column="4" Row="0" AppUserModelID="Microsoft.Windows.Photos_8wekyb3d8bbwe!App" />
|
<start:Tile Size="2x2" Column="4" Row="0" AppUserModelID="Microsoft.Windows.Photos_8wekyb3d8bbwe!App" />
|
||||||
<start:Tile Size="2x2" Column="4" Row="4" AppUserModelID="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
<start:Tile Size="2x2" Column="4" Row="4" AppUserModelID="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||||
<start:Tile Size="4x2" Column="0" Row="4" AppUserModelID="Microsoft.WindowsCalculator_8wekyb3d8bbwe!App" />
|
<start:Tile Size="4x2" Column="0" Row="4" AppUserModelID="Microsoft.WindowsCalculator_8wekyb3d8bbwe!App" />
|
||||||
</start:Group>
|
</start:Group>
|
||||||
<start:Group Name="Group2">
|
<start:Group Name="Group2">
|
||||||
<start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Accessories\Paint.lnk" />
|
<start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Accessories\Paint.lnk" />
|
||||||
<start:DesktopApplicationTile Size="2x2" Column="0" Row="0" DesktopApplicationLinkPath="%APPDATA%\Microsoft\Windows\Start Menu\Programs\Accessories\Notepad.lnk" />
|
<start:DesktopApplicationTile Size="2x2" Column="0" Row="0" DesktopApplicationLinkPath="%APPDATA%\Microsoft\Windows\Start Menu\Programs\Accessories\Notepad.lnk" />
|
||||||
</start:Group>
|
</start:Group>
|
||||||
</defaultlayout:StartLayout>
|
</defaultlayout:StartLayout>
|
||||||
</StartLayoutCollection>
|
</StartLayoutCollection>
|
||||||
</DefaultLayoutOverride>
|
</DefaultLayoutOverride>
|
||||||
</LayoutModificationTemplate>
|
</LayoutModificationTemplate>
|
||||||
]]>
|
]]>
|
||||||
</StartLayout>
|
</StartLayout>
|
||||||
<Taskbar ShowTaskbar="true"/>
|
<Taskbar ShowTaskbar="true"/>
|
||||||
</Profile>
|
</Profile>
|
||||||
</Profiles>
|
</Profiles>
|
||||||
<Configs>
|
<Configs>
|
||||||
<Config>
|
<Config>
|
||||||
<Account>MultiAppKioskUser</Account>
|
<Account>MultiAppKioskUser</Account>
|
||||||
<DefaultProfile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}"/>
|
<DefaultProfile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}"/>
|
||||||
</Config>
|
</Config>
|
||||||
</Configs>
|
</Configs>
|
||||||
</AssignedAccessConfiguration>
|
</AssignedAccessConfiguration>
|
||||||
"@
|
"@
|
||||||
|
|
||||||
Set-CimInstance -CimInstance $obj
|
Set-CimInstance -CimInstance $obj
|
||||||
|
@ -27,15 +27,13 @@ Go to the [Azure portal](https://portal.azure.com), select **All services**, and
|
|||||||
### Permissions
|
### Permissions
|
||||||
|
|
||||||
>[!IMPORTANT]
|
>[!IMPORTANT]
|
||||||
>Unlike the OMS portal, the Azure portal requires access to both an Azure Log Analytics subscription and a linked Azure subscription.
|
>Unlike the OMS portal (which only requires permission to access the Azure Log Analytics workspace), the Azure portal also requires access to be configured to either the linked Azure subscription or Azure resource group.
|
||||||
|
|
||||||
To check the Log Analytics workspaces you can access, select **Log Analytics**. You should see a grid control listing all workspaces, along with the Azure subscription each is linked to:
|
To check the Log Analytics workspaces you can access, select **Log Analytics**. You should see a grid control listing all workspaces, along with the Azure subscription each is linked to:
|
||||||
|
|
||||||
[](images/azure-portal-LAmain-wkspc-subname-sterile.png)
|
[](images/azure-portal-LAmain-wkspc-subname-sterile.png)
|
||||||
|
|
||||||
If you do not see your workspace in this view, you do not have access to the underlying Azure subscription. To view and assign permissions for a workspace, select its name and then, in the flyout that opens, select **Access control (IAM)**. You can view and assign permissions for a subscription similarly by selecting the subscription name and selecting **Access control (IAM)**.
|
If you do not see your workspace in this view, but you are able to access the workspace from the classic portal, that means you do not have access to the workspaces's Azure subscription or resource group. To remedy this, you will need to find someone with admin rights to grant you access, which they can do by selecting the subscription name and selecting **Access control (IAM)** (alternatively they can configure your access at the resource group level). They should either grant you "Log Analytics Reader" access (for read-only access) or "Log Analytics Contributor" access (which enables making changes such as creating deployment plans and changing application readiness states).
|
||||||
|
|
||||||
The Azure subscription requires at least "Log Analytics Reader" permission. Making changes (for example, to set app importance in Upgrade Readiness) requires "Log Analytics Contributor" permission. You can view your current role and make changes in other roles by using the Access control (IAM) tab in Azure. These permissions will be inherited by Azure Log Analytics.
|
|
||||||
|
|
||||||
When permissions are configured, you can select the workspace and then select **Workspace summary** to see information similar to what was shown in the OMS overview page.
|
When permissions are configured, you can select the workspace and then select **Workspace summary** to see information similar to what was shown in the OMS overview page.
|
||||||
|
|
||||||
|
@ -28,7 +28,7 @@ Use this article to learn about diagnostic events, grouped by event area, and th
|
|||||||
|
|
||||||
You can learn more about Windows functional and diagnostic data through these articles:
|
You can learn more about Windows functional and diagnostic data through these articles:
|
||||||
|
|
||||||
|
- [Windows 10, version 1809 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
||||||
- [Windows 10, version 1803 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
- [Windows 10, version 1803 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
||||||
- [Windows 10, version 1709 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1709.md)
|
- [Windows 10, version 1709 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1709.md)
|
||||||
- [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md)
|
- [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md)
|
||||||
|
@ -28,7 +28,7 @@ Use this article to learn about diagnostic events, grouped by event area, and th
|
|||||||
|
|
||||||
You can learn more about Windows functional and diagnostic data through these articles:
|
You can learn more about Windows functional and diagnostic data through these articles:
|
||||||
|
|
||||||
|
- [Windows 10, version 1809 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
||||||
- [Windows 10, version 1803 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
- [Windows 10, version 1803 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
||||||
- [Windows 10, version 1703 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1703.md)
|
- [Windows 10, version 1703 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1703.md)
|
||||||
- [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md)
|
- [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md)
|
||||||
|
@ -28,7 +28,7 @@ Use this article to learn about diagnostic events, grouped by event area, and th
|
|||||||
|
|
||||||
You can learn more about Windows functional and diagnostic data through these articles:
|
You can learn more about Windows functional and diagnostic data through these articles:
|
||||||
|
|
||||||
|
- [Windows 10, version 1809 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
||||||
- [Windows 10, version 1709 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1709.md)
|
- [Windows 10, version 1709 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1709.md)
|
||||||
- [Windows 10, version 1703 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1703.md)
|
- [Windows 10, version 1703 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1703.md)
|
||||||
- [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md)
|
- [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md)
|
||||||
|
@ -9,7 +9,7 @@ ms.pagetype: security
|
|||||||
localizationpriority: high
|
localizationpriority: high
|
||||||
author: brianlic-msft
|
author: brianlic-msft
|
||||||
ms.author: brianlic
|
ms.author: brianlic
|
||||||
ms.date: 09/10/2018
|
ms.date: 10/03/2018
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
||||||
@ -1818,18 +1818,14 @@ The following fields are available:
|
|||||||
- **AdvertisingId** Current state of the advertising ID setting.
|
- **AdvertisingId** Current state of the advertising ID setting.
|
||||||
- **AppDiagnostics** Current state of the app diagnostics setting.
|
- **AppDiagnostics** Current state of the app diagnostics setting.
|
||||||
- **Appointments** Current state of the calendar setting.
|
- **Appointments** Current state of the calendar setting.
|
||||||
- **AppointmentsSystem** Current state of the calendar setting.
|
|
||||||
- **Bluetooth** Current state of the Bluetooth capability setting.
|
- **Bluetooth** Current state of the Bluetooth capability setting.
|
||||||
- **BluetoothSync** Current state of the Bluetooth sync capability setting.
|
- **BluetoothSync** Current state of the Bluetooth sync capability setting.
|
||||||
- **BroadFileSystemAccess** Current state of the broad file system access setting.
|
- **BroadFileSystemAccess** Current state of the broad file system access setting.
|
||||||
- **CellularData** Current state of the cellular data capability setting.
|
- **CellularData** Current state of the cellular data capability setting.
|
||||||
- **Chat** Current state of the chat setting.
|
- **Chat** Current state of the chat setting.
|
||||||
- **ChatSystem** Current state of the chat setting.
|
|
||||||
- **Contacts** Current state of the contacts setting.
|
- **Contacts** Current state of the contacts setting.
|
||||||
- **ContactsSystem** Current state of the Contacts setting.
|
|
||||||
- **DocumentsLibrary** Current state of the documents library setting.
|
- **DocumentsLibrary** Current state of the documents library setting.
|
||||||
- **Email** Current state of the email setting.
|
- **Email** Current state of the email setting.
|
||||||
- **EmailSystem** Current state of the email setting.
|
|
||||||
- **FindMyDevice** Current state of the "find my device" setting.
|
- **FindMyDevice** Current state of the "find my device" setting.
|
||||||
- **GazeInput** Current state of the gaze input setting.
|
- **GazeInput** Current state of the gaze input setting.
|
||||||
- **HumanInterfaceDevice** Current state of the human interface device setting.
|
- **HumanInterfaceDevice** Current state of the human interface device setting.
|
||||||
@ -1841,7 +1837,6 @@ The following fields are available:
|
|||||||
- **Microphone** Current state of the microphone setting.
|
- **Microphone** Current state of the microphone setting.
|
||||||
- **PhoneCall** Current state of the phone call setting.
|
- **PhoneCall** Current state of the phone call setting.
|
||||||
- **PhoneCallHistory** Current state of the call history setting.
|
- **PhoneCallHistory** Current state of the call history setting.
|
||||||
- **PhoneCallHistorySystem** Current state of the call history setting.
|
|
||||||
- **PicturesLibrary** Current state of the pictures library setting.
|
- **PicturesLibrary** Current state of the pictures library setting.
|
||||||
- **Radios** Current state of the radios setting.
|
- **Radios** Current state of the radios setting.
|
||||||
- **SensorsCustom** Current state of the custom sensor setting.
|
- **SensorsCustom** Current state of the custom sensor setting.
|
||||||
@ -1851,7 +1846,6 @@ The following fields are available:
|
|||||||
- **USB** Current state of the USB setting.
|
- **USB** Current state of the USB setting.
|
||||||
- **UserAccountInformation** Current state of the account information setting.
|
- **UserAccountInformation** Current state of the account information setting.
|
||||||
- **UserDataTasks** Current state of the tasks setting.
|
- **UserDataTasks** Current state of the tasks setting.
|
||||||
- **UserDataTasksSystem** Current state of the tasks setting.
|
|
||||||
- **UserNotificationListener** Current state of the notifications setting.
|
- **UserNotificationListener** Current state of the notifications setting.
|
||||||
- **VideosLibrary** Current state of the videos library setting.
|
- **VideosLibrary** Current state of the videos library setting.
|
||||||
- **Webcam** Current state of the camera setting.
|
- **Webcam** Current state of the camera setting.
|
||||||
@ -1985,18 +1979,14 @@ The following fields are available:
|
|||||||
- **AdvertisingId** Current state of the advertising ID setting.
|
- **AdvertisingId** Current state of the advertising ID setting.
|
||||||
- **AppDiagnostics** Current state of the app diagnostics setting.
|
- **AppDiagnostics** Current state of the app diagnostics setting.
|
||||||
- **Appointments** Current state of the calendar setting.
|
- **Appointments** Current state of the calendar setting.
|
||||||
- **AppointmentsSystem** Current state of the calendar setting.
|
|
||||||
- **Bluetooth** Current state of the Bluetooth capability setting.
|
- **Bluetooth** Current state of the Bluetooth capability setting.
|
||||||
- **BluetoothSync** Current state of the Bluetooth sync capability setting.
|
- **BluetoothSync** Current state of the Bluetooth sync capability setting.
|
||||||
- **BroadFileSystemAccess** Current state of the broad file system access setting.
|
- **BroadFileSystemAccess** Current state of the broad file system access setting.
|
||||||
- **CellularData** Current state of the cellular data capability setting.
|
- **CellularData** Current state of the cellular data capability setting.
|
||||||
- **Chat** Current state of the chat setting.
|
- **Chat** Current state of the chat setting.
|
||||||
- **ChatSystem** Current state of the chat setting.
|
|
||||||
- **Contacts** Current state of the contacts setting.
|
- **Contacts** Current state of the contacts setting.
|
||||||
- **ContactsSystem** Current state of the contacts setting.
|
|
||||||
- **DocumentsLibrary** Current state of the documents library setting.
|
- **DocumentsLibrary** Current state of the documents library setting.
|
||||||
- **Email** Current state of the email setting.
|
- **Email** Current state of the email setting.
|
||||||
- **EmailSystem** Current state of the email setting.
|
|
||||||
- **GazeInput** Current state of the gaze input setting.
|
- **GazeInput** Current state of the gaze input setting.
|
||||||
- **HumanInterfaceDevice** Current state of the human interface device setting.
|
- **HumanInterfaceDevice** Current state of the human interface device setting.
|
||||||
- **InkTypeImprovement** Current state of the improve inking and typing setting.
|
- **InkTypeImprovement** Current state of the improve inking and typing setting.
|
||||||
@ -2008,7 +1998,6 @@ The following fields are available:
|
|||||||
- **Microphone** Current state of the microphone setting.
|
- **Microphone** Current state of the microphone setting.
|
||||||
- **PhoneCall** Current state of the phone call setting.
|
- **PhoneCall** Current state of the phone call setting.
|
||||||
- **PhoneCallHistory** Current state of the call history setting.
|
- **PhoneCallHistory** Current state of the call history setting.
|
||||||
- **PhoneCallHistorySystem** Current state of the call history setting.
|
|
||||||
- **PicturesLibrary** Current state of the pictures library setting.
|
- **PicturesLibrary** Current state of the pictures library setting.
|
||||||
- **Radios** Current state of the radios setting.
|
- **Radios** Current state of the radios setting.
|
||||||
- **SensorsCustom** Current state of the custom sensor setting.
|
- **SensorsCustom** Current state of the custom sensor setting.
|
||||||
@ -2018,7 +2007,6 @@ The following fields are available:
|
|||||||
- **USB** Current state of the USB setting.
|
- **USB** Current state of the USB setting.
|
||||||
- **UserAccountInformation** Current state of the account information setting.
|
- **UserAccountInformation** Current state of the account information setting.
|
||||||
- **UserDataTasks** Current state of the tasks setting.
|
- **UserDataTasks** Current state of the tasks setting.
|
||||||
- **UserDataTasksSystem** Current state of the tasks setting.
|
|
||||||
- **UserNotificationListener** Current state of the notifications setting.
|
- **UserNotificationListener** Current state of the notifications setting.
|
||||||
- **VideosLibrary** Current state of the videos library setting.
|
- **VideosLibrary** Current state of the videos library setting.
|
||||||
- **Webcam** Current state of the camera setting.
|
- **Webcam** Current state of the camera setting.
|
||||||
|
@ -23,10 +23,10 @@ Hybrid environments are distributed systems that enable organizations to use on-
|
|||||||
|
|
||||||
The distributed systems on which these technologies were built involved several pieces of on-premises and cloud infrastructure. High-level pieces of the infrastructure include:
|
The distributed systems on which these technologies were built involved several pieces of on-premises and cloud infrastructure. High-level pieces of the infrastructure include:
|
||||||
* [Directories](#directories)
|
* [Directories](#directories)
|
||||||
* [Public Key Infrastucture](#public-key-infastructure)
|
* [Public Key Infrastructure](#public-key-infrastructure)
|
||||||
* [Directory Synchronization](#directory-synchronization)
|
* [Directory Synchronization](#directory-synchronization)
|
||||||
* [Federation](#federation)
|
* [Federation](#federation)
|
||||||
* [MultiFactor Authetication](#multifactor-authentication)
|
* [MultiFactor Authentication](#multifactor-authentication)
|
||||||
* [Device Registration](#device-registration)
|
* [Device Registration](#device-registration)
|
||||||
|
|
||||||
## Directories ##
|
## Directories ##
|
||||||
@ -114,9 +114,9 @@ Organizations wanting to deploy hybrid key trust need their domain joined device
|
|||||||
<br>
|
<br>
|
||||||
|
|
||||||
### Next Steps ###
|
### Next Steps ###
|
||||||
Follow the Windows Hello for Business hybrid key trust deployment guide. For proof-of-concepts, labs, and new installations, choose the **New Installation Basline**.
|
Follow the Windows Hello for Business hybrid key trust deployment guide. For proof-of-concepts, labs, and new installations, choose the **New Installation Baseline**.
|
||||||
|
|
||||||
For environments transitioning from on-premises to hybrid, start with **Configure Azure Directory Syncrhonization**.
|
For environments transitioning from on-premises to hybrid, start with **Configure Azure Directory Synchronization**.
|
||||||
|
|
||||||
For federated and non-federated environments, start with **Configure Windows Hello for Business settings**.
|
For federated and non-federated environments, start with **Configure Windows Hello for Business settings**.
|
||||||
|
|
||||||
|
@ -6,7 +6,7 @@ ms.mktglfcycl: deploy
|
|||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.pagetype: security
|
ms.pagetype: security
|
||||||
author: aadake
|
author: aadake
|
||||||
ms.date: 09/19/2018
|
ms.date: 10/03/2018
|
||||||
---
|
---
|
||||||
|
|
||||||
# Kernel DMA Protection for Thunderbolt™ 3
|
# Kernel DMA Protection for Thunderbolt™ 3
|
||||||
@ -61,11 +61,11 @@ Systems released prior to Windows 10 version 1803 do not support Kernel DMA Prot
|
|||||||
>[!NOTE]
|
>[!NOTE]
|
||||||
>Kernel DMA Protection is not compatible with other BitLocker DMA attacks countermeasures. It is recommended to disable the BitLocker DMA attacks countermeasures if the system supports Kernel DMA Protection. Kernel DMA Protection provides higher security bar for the system over the BitLocker DMA attack countermeasures, while maintaining usability of external peripherals.
|
>Kernel DMA Protection is not compatible with other BitLocker DMA attacks countermeasures. It is recommended to disable the BitLocker DMA attacks countermeasures if the system supports Kernel DMA Protection. Kernel DMA Protection provides higher security bar for the system over the BitLocker DMA attack countermeasures, while maintaining usability of external peripherals.
|
||||||
|
|
||||||
## Enabling Kernel DMA protection
|
## How to check if Kernel DMA Protection is enabled
|
||||||
|
|
||||||
Systems running Windows 10 version 1803 that do support Kernel DMA Protection do have this security feature enabled automatically by the OS with no user or IT admin configuration required.
|
Systems running Windows 10 version 1803 that do support Kernel DMA Protection do have this security feature enabled automatically by the OS with no user or IT admin configuration required.
|
||||||
|
|
||||||
**To check if a device supports kernel DMA protection**
|
**To check if a device supports Kernel DMA Protection**
|
||||||
|
|
||||||
1. Launch MSINFO32.exe in a command prompt, or in the Windows search bar.
|
1. Launch MSINFO32.exe in a command prompt, or in the Windows search bar.
|
||||||
2. Check the value of **Kernel DMA Protection**.
|
2. Check the value of **Kernel DMA Protection**.
|
||||||
@ -73,14 +73,14 @@ Systems running Windows 10 version 1803 that do support Kernel DMA Protection do
|
|||||||
3. If the current state of **Kernel DMA Protection** is OFF and **Virtualization Technology in Firmware** is NO:
|
3. If the current state of **Kernel DMA Protection** is OFF and **Virtualization Technology in Firmware** is NO:
|
||||||
- Reboot into BIOS settings
|
- Reboot into BIOS settings
|
||||||
- Turn on Intel Virtualization Technology.
|
- Turn on Intel Virtualization Technology.
|
||||||
- Turn on Intel Virtualization Technology for I/O (VT-d). In Windows 10 version 1803, only Intel VT-d is supported. Other platforms can use DMA attack mitigations described in BitLocker Countermeasures.
|
- Turn on Intel Virtualization Technology for I/O (VT-d). In Windows 10 version 1803, only Intel VT-d is supported. Other platforms can use DMA attack mitigations described in [BitLocker countermeasures](bitlocker/bitlocker-countermeasures.md).
|
||||||
- Reboot system into Windows 10.
|
- Reboot system into Windows 10.
|
||||||
4. If the state of **Kernel DMA Protection** remains Off, then the system does not support this feature.
|
4. If the state of **Kernel DMA Protection** remains Off, then the system does not support this feature.
|
||||||
|
|
||||||
## Frequently asked questions
|
## Frequently asked questions
|
||||||
|
|
||||||
### Do in-market systems support Kernel DMA protection for Thunderbolt™ 3?
|
### Do in-market systems support Kernel DMA Protection for Thunderbolt™ 3?
|
||||||
In market systems, released with Windows 10 version 1709 or earlier, will not support Kernel DMA protection for Thunderbolt™ 3 after upgrading to Windows 10 version 1803, as this feature requires the BIOS/platform firmware changes and guarantees.
|
In market systems, released with Windows 10 version 1709 or earlier, will not support Kernel DMA Protection for Thunderbolt™ 3 after upgrading to Windows 10 version 1803, as this feature requires the BIOS/platform firmware changes and guarantees.
|
||||||
|
|
||||||
### Does Kernel DMA Protection prevent drive-by DMA attacks during Boot?
|
### Does Kernel DMA Protection prevent drive-by DMA attacks during Boot?
|
||||||
No, Kernel DMA Protection only protects against drive-by DMA attacks after the OS is loaded. It is the responsibility of the system firmware/BIOS to protect against attacks via the Thunderbolt™ 3 ports during boot.
|
No, Kernel DMA Protection only protects against drive-by DMA attacks after the OS is loaded. It is the responsibility of the system firmware/BIOS to protect against attacks via the Thunderbolt™ 3 ports during boot.
|
||||||
|
@ -65,86 +65,86 @@ Here are a few examples of responses from the Reporting CSP.
|
|||||||
|
|
||||||
#### File ownership on a file is changed from work to personal
|
#### File ownership on a file is changed from work to personal
|
||||||
```
|
```
|
||||||
<SyncML><SyncHdr/><SyncBody><Status><CmdID>1</CmdID><MsgRef>1</MsgRef><CmdRef>0</CmdRef><Cmd>SyncHdr</Cmd><Data>200</Data></Status><Status><CmdID>2</CmdID><MsgRef>1</MsgRef><CmdRef>2</CmdRef><Cmd>Replace</Cmd><Data>200</Data></Status><Status><CmdID>3</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Cmd>Get</Cmd><Data>200</Data></Status><Results><CmdID>4</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Item><Source><LocURI>./Vendor/MSFT/Reporting/EnterpriseDataProtection/RetrieveByTimeRange/Logs</LocURI></Source><Meta><Format xmlns="syncml:metinf">xml</Format></Meta><Data><?xml version="1.0" encoding="utf-8"?>
|
<SyncML><SyncHdr/><SyncBody><Status><CmdID>1</CmdID><MsgRef>1</MsgRef><CmdRef>0</CmdRef><Cmd>SyncHdr</Cmd><Data>200</Data></Status><Status><CmdID>2</CmdID><MsgRef>1</MsgRef><CmdRef>2</CmdRef><Cmd>Replace</Cmd><Data>200</Data></Status><Status><CmdID>3</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Cmd>Get</Cmd><Data>200</Data></Status><Results><CmdID>4</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Item><Source><LocURI>./Vendor/MSFT/Reporting/EnterpriseDataProtection/RetrieveByTimeRange/Logs</LocURI></Source><Meta><Format xmlns="syncml:metinf">xml</Format></Meta><Data><?xml version="1.0" encoding="utf-8"?>
|
||||||
<Reporting Version="com.contoso/2.0/MDM/Reporting">
|
<Reporting Version="com.contoso/2.0/MDM/Reporting">
|
||||||
<User UserID="S-1-12-1-1111111111-1111111111-1111111111-1111111111" EnterpriseID="corp.contoso.com">
|
<User UserID="S-1-12-1-1111111111-1111111111-1111111111-1111111111" EnterpriseID="corp.contoso.com">
|
||||||
<Log ProviderType="EDPAudit" LogType="ProtectionRemoved" TimeStamp="131357166318347527">
|
<Log ProviderType="EDPAudit" LogType="ProtectionRemoved" TimeStamp="131357166318347527">
|
||||||
<Policy>Protection removed</Policy>
|
<Policy>Protection removed</Policy>
|
||||||
<Justification>NULL</Justification>
|
<Justification>NULL</Justification>
|
||||||
<FilePath>C:\Users\TestUser\Desktop\tmp\demo\Work document.docx</FilePath>
|
<FilePath>C:\Users\TestUser\Desktop\tmp\demo\Work document.docx</FilePath>
|
||||||
</Log>
|
</Log>
|
||||||
</User>
|
</User>
|
||||||
</Reporting></Data></Item></Results><Final/></SyncBody></SyncML>
|
</Reporting></Data></Item></Results><Final/></SyncBody></SyncML>
|
||||||
```
|
```
|
||||||
|
|
||||||
#### A work file is uploaded to a personal webpage in Edge
|
#### A work file is uploaded to a personal webpage in Edge
|
||||||
```
|
```
|
||||||
<SyncML><SyncHdr/><SyncBody><Status><CmdID>1</CmdID><MsgRef>1</MsgRef><CmdRef>0</CmdRef><Cmd>SyncHdr</Cmd><Data>200</Data></Status><Status><CmdID>2</CmdID><MsgRef>1</MsgRef><CmdRef>2</CmdRef><Cmd>Replace</Cmd><Data>200</Data></Status><Status><CmdID>3</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Cmd>Get</Cmd><Data>200</Data></Status><Results><CmdID>4</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Item><Source><LocURI>./Vendor/MSFT/Reporting/EnterpriseDataProtection/RetrieveByTimeRange/Logs</LocURI></Source><Meta><Format xmlns="syncml:metinf">xml</Format></Meta><Data><?xml version="1.0" encoding="utf-8"?>
|
<SyncML><SyncHdr/><SyncBody><Status><CmdID>1</CmdID><MsgRef>1</MsgRef><CmdRef>0</CmdRef><Cmd>SyncHdr</Cmd><Data>200</Data></Status><Status><CmdID>2</CmdID><MsgRef>1</MsgRef><CmdRef>2</CmdRef><Cmd>Replace</Cmd><Data>200</Data></Status><Status><CmdID>3</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Cmd>Get</Cmd><Data>200</Data></Status><Results><CmdID>4</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Item><Source><LocURI>./Vendor/MSFT/Reporting/EnterpriseDataProtection/RetrieveByTimeRange/Logs</LocURI></Source><Meta><Format xmlns="syncml:metinf">xml</Format></Meta><Data><?xml version="1.0" encoding="utf-8"?>
|
||||||
<Reporting Version="com.contoso/2.0/MDM/Reporting">
|
<Reporting Version="com.contoso/2.0/MDM/Reporting">
|
||||||
<User UserID="S-1-12-1-1111111111-1111111111-1111111111-1111111111" EnterpriseID="corp.contoso.com">
|
<User UserID="S-1-12-1-1111111111-1111111111-1111111111-1111111111" EnterpriseID="corp.contoso.com">
|
||||||
<Log ProviderType="EDPAudit" LogType="DataCopied" TimeStamp="131357192409318534">
|
<Log ProviderType="EDPAudit" LogType="DataCopied" TimeStamp="131357192409318534">
|
||||||
<Policy>CopyPaste</Policy>
|
<Policy>CopyPaste</Policy>
|
||||||
<Justification>NULL</Justification>
|
<Justification>NULL</Justification>
|
||||||
<SourceApplicationName>NULL</SourceApplicationName>
|
<SourceApplicationName>NULL</SourceApplicationName>
|
||||||
<DestinationEnterpriseID>NULL</DestinationEnterpriseID>
|
<DestinationEnterpriseID>NULL</DestinationEnterpriseID>
|
||||||
<DestinationApplicationName>mail.contoso.com</DestinationApplicationName>
|
<DestinationApplicationName>mail.contoso.com</DestinationApplicationName>
|
||||||
<DataInfo>C:\Users\TestUser\Desktop\tmp\demo\Work document.docx</DataInfo>
|
<DataInfo>C:\Users\TestUser\Desktop\tmp\demo\Work document.docx</DataInfo>
|
||||||
</Log>
|
</Log>
|
||||||
</User>
|
</User>
|
||||||
</Reporting></Data></Item></Results><Final/></SyncBody></SyncML>
|
</Reporting></Data></Item></Results><Final/></SyncBody></SyncML>
|
||||||
```
|
```
|
||||||
|
|
||||||
#### Work data is pasted into a personal webpage
|
#### Work data is pasted into a personal webpage
|
||||||
```
|
```
|
||||||
<SyncML><SyncHdr/><SyncBody><Status><CmdID>1</CmdID><MsgRef>1</MsgRef><CmdRef>0</CmdRef><Cmd>SyncHdr</Cmd><Data>200</Data></Status><Status><CmdID>2</CmdID><MsgRef>1</MsgRef><CmdRef>2</CmdRef><Cmd>Replace</Cmd><Data>200</Data></Status><Status><CmdID>3</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Cmd>Get</Cmd><Data>200</Data></Status><Results><CmdID>4</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Item><Source><LocURI>./Vendor/MSFT/Reporting/EnterpriseDataProtection/RetrieveByTimeRange/Logs</LocURI></Source><Meta><Format xmlns="syncml:metinf">xml</Format></Meta><Data><?xml version="1.0" encoding="utf-8"?>
|
<SyncML><SyncHdr/><SyncBody><Status><CmdID>1</CmdID><MsgRef>1</MsgRef><CmdRef>0</CmdRef><Cmd>SyncHdr</Cmd><Data>200</Data></Status><Status><CmdID>2</CmdID><MsgRef>1</MsgRef><CmdRef>2</CmdRef><Cmd>Replace</Cmd><Data>200</Data></Status><Status><CmdID>3</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Cmd>Get</Cmd><Data>200</Data></Status><Results><CmdID>4</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Item><Source><LocURI>./Vendor/MSFT/Reporting/EnterpriseDataProtection/RetrieveByTimeRange/Logs</LocURI></Source><Meta><Format xmlns="syncml:metinf">xml</Format></Meta><Data><?xml version="1.0" encoding="utf-8"?>
|
||||||
<Reporting Version="com.contoso/2.0/MDM/Reporting">
|
<Reporting Version="com.contoso/2.0/MDM/Reporting">
|
||||||
<User UserID="S-1-12-1-1111111111-1111111111-1111111111-1111111111" EnterpriseID="corp.contoso.com">
|
<User UserID="S-1-12-1-1111111111-1111111111-1111111111-1111111111" EnterpriseID="corp.contoso.com">
|
||||||
<Log ProviderType="EDPAudit" LogType="DataCopied" TimeStamp="131357193734179782">
|
<Log ProviderType="EDPAudit" LogType="DataCopied" TimeStamp="131357193734179782">
|
||||||
<Policy>CopyPaste</Policy>
|
<Policy>CopyPaste</Policy>
|
||||||
<Justification>NULL</Justification>
|
<Justification>NULL</Justification>
|
||||||
<SourceApplicationName>O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\MICROSOFT OFFICE 2016\WINWORD.EXE\16.0.8027.1000</SourceApplicationName>
|
<SourceApplicationName>O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\MICROSOFT OFFICE 2016\WINWORD.EXE\16.0.8027.1000</SourceApplicationName>
|
||||||
<DestinationEnterpriseID>NULL</DestinationEnterpriseID>
|
<DestinationEnterpriseID>NULL</DestinationEnterpriseID>
|
||||||
<DestinationApplicationName>mail.contoso.com</DestinationApplicationName>
|
<DestinationApplicationName>mail.contoso.com</DestinationApplicationName>
|
||||||
<DataInfo>EnterpriseDataProtectionId|Object Descriptor|Rich Text Format|HTML Format|AnsiText|Text|EnhancedMetafile|Embed Source|Link Source|Link Source Descriptor|ObjectLink|Hyperlink</DataInfo>
|
<DataInfo>EnterpriseDataProtectionId|Object Descriptor|Rich Text Format|HTML Format|AnsiText|Text|EnhancedMetafile|Embed Source|Link Source|Link Source Descriptor|ObjectLink|Hyperlink</DataInfo>
|
||||||
</Log>
|
</Log>
|
||||||
</User>
|
</User>
|
||||||
</Reporting></Data></Item></Results><Final/></SyncBody></SyncML>
|
</Reporting></Data></Item></Results><Final/></SyncBody></SyncML>
|
||||||
```
|
```
|
||||||
|
|
||||||
#### A work file is opened with a personal application
|
#### A work file is opened with a personal application
|
||||||
```
|
```
|
||||||
<SyncML><SyncHdr/><SyncBody><Status><CmdID>1</CmdID><MsgRef>1</MsgRef><CmdRef>0</CmdRef><Cmd>SyncHdr</Cmd><Data>200</Data></Status><Status><CmdID>2</CmdID><MsgRef>1</MsgRef><CmdRef>2</CmdRef><Cmd>Replace</Cmd><Data>200</Data></Status><Status><CmdID>3</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Cmd>Get</Cmd><Data>200</Data></Status><Results><CmdID>4</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Item><Source><LocURI>./Vendor/MSFT/Reporting/EnterpriseDataProtection/RetrieveByTimeRange/Logs</LocURI></Source><Meta><Format xmlns="syncml:metinf">xml</Format></Meta><Data><?xml version="1.0" encoding="utf-8"?>
|
<SyncML><SyncHdr/><SyncBody><Status><CmdID>1</CmdID><MsgRef>1</MsgRef><CmdRef>0</CmdRef><Cmd>SyncHdr</Cmd><Data>200</Data></Status><Status><CmdID>2</CmdID><MsgRef>1</MsgRef><CmdRef>2</CmdRef><Cmd>Replace</Cmd><Data>200</Data></Status><Status><CmdID>3</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Cmd>Get</Cmd><Data>200</Data></Status><Results><CmdID>4</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Item><Source><LocURI>./Vendor/MSFT/Reporting/EnterpriseDataProtection/RetrieveByTimeRange/Logs</LocURI></Source><Meta><Format xmlns="syncml:metinf">xml</Format></Meta><Data><?xml version="1.0" encoding="utf-8"?>
|
||||||
<Reporting Version="com.contoso/2.0/MDM/Reporting">
|
<Reporting Version="com.contoso/2.0/MDM/Reporting">
|
||||||
<User UserID="S-1-12-1-1111111111-1111111111-1111111111-1111111111" EnterpriseID="corp.contoso.com">
|
<User UserID="S-1-12-1-1111111111-1111111111-1111111111-1111111111" EnterpriseID="corp.contoso.com">
|
||||||
<Log ProviderType="EDPAudit" LogType="ApplicationGenerated" TimeStamp="131357194991209469">
|
<Log ProviderType="EDPAudit" LogType="ApplicationGenerated" TimeStamp="131357194991209469">
|
||||||
<Policy>NULL</Policy>
|
<Policy>NULL</Policy>
|
||||||
<Justification></Justification>
|
<Justification></Justification>
|
||||||
<Object>C:\Users\TestUser\Desktop\tmp\demo\Work document.docx</Object>
|
<Object>C:\Users\TestUser\Desktop\tmp\demo\Work document.docx</Object>
|
||||||
<Action>1</Action>
|
<Action>1</Action>
|
||||||
<SourceName>O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\MICROSOFT® WINDOWS® OPERATING SYSTEM\WORDPAD.EXE\10.0.15063.2</SourceName>
|
<SourceName>O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\MICROSOFT® WINDOWS® OPERATING SYSTEM\WORDPAD.EXE\10.0.15063.2</SourceName>
|
||||||
<DestinationEnterpriseID>Personal</DestinationEnterpriseID>
|
<DestinationEnterpriseID>Personal</DestinationEnterpriseID>
|
||||||
<DestinationName>O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\MICROSOFT® WINDOWS® OPERATING SYSTEM\WORDPAD.EXE\10.0.15063.2</DestinationName>
|
<DestinationName>O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\MICROSOFT® WINDOWS® OPERATING SYSTEM\WORDPAD.EXE\10.0.15063.2</DestinationName>
|
||||||
<Application>O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\MICROSOFT® WINDOWS® OPERATING SYSTEM\WORDPAD.EXE\10.0.15063.2</Application>
|
<Application>O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\MICROSOFT® WINDOWS® OPERATING SYSTEM\WORDPAD.EXE\10.0.15063.2</Application>
|
||||||
</Log>
|
</Log>
|
||||||
</User>
|
</User>
|
||||||
</Reporting></Data></Item></Results><Final/></SyncBody></SyncML>
|
</Reporting></Data></Item></Results><Final/></SyncBody></SyncML>
|
||||||
```
|
```
|
||||||
|
|
||||||
#### Work data is pasted into a personal application
|
#### Work data is pasted into a personal application
|
||||||
```
|
```
|
||||||
<SyncML><SyncHdr/><SyncBody><Status><CmdID>1</CmdID><MsgRef>1</MsgRef><CmdRef>0</CmdRef><Cmd>SyncHdr</Cmd><Data>200</Data></Status><Status><CmdID>2</CmdID><MsgRef>1</MsgRef><CmdRef>2</CmdRef><Cmd>Replace</Cmd><Data>200</Data></Status><Status><CmdID>3</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Cmd>Get</Cmd><Data>200</Data></Status><Results><CmdID>4</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Item><Source><LocURI>./Vendor/MSFT/Reporting/EnterpriseDataProtection/RetrieveByTimeRange/Logs</LocURI></Source><Meta><Format xmlns="syncml:metinf">xml</Format></Meta><Data><?xml version="1.0" encoding="utf-8"?>
|
<SyncML><SyncHdr/><SyncBody><Status><CmdID>1</CmdID><MsgRef>1</MsgRef><CmdRef>0</CmdRef><Cmd>SyncHdr</Cmd><Data>200</Data></Status><Status><CmdID>2</CmdID><MsgRef>1</MsgRef><CmdRef>2</CmdRef><Cmd>Replace</Cmd><Data>200</Data></Status><Status><CmdID>3</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Cmd>Get</Cmd><Data>200</Data></Status><Results><CmdID>4</CmdID><MsgRef>1</MsgRef><CmdRef>4</CmdRef><Item><Source><LocURI>./Vendor/MSFT/Reporting/EnterpriseDataProtection/RetrieveByTimeRange/Logs</LocURI></Source><Meta><Format xmlns="syncml:metinf">xml</Format></Meta><Data><?xml version="1.0" encoding="utf-8"?>
|
||||||
<Reporting Version="com.contoso/2.0/MDM/Reporting">
|
<Reporting Version="com.contoso/2.0/MDM/Reporting">
|
||||||
<User UserID="S-1-12-1-1111111111-1111111111-1111111111-1111111111" EnterpriseID="corp.contoso.com">
|
<User UserID="S-1-12-1-1111111111-1111111111-1111111111-1111111111" EnterpriseID="corp.contoso.com">
|
||||||
<Log ProviderType="EDPAudit" LogType="DataCopied" TimeStamp="131357196076537270">
|
<Log ProviderType="EDPAudit" LogType="DataCopied" TimeStamp="131357196076537270">
|
||||||
<Policy>CopyPaste</Policy>
|
<Policy>CopyPaste</Policy>
|
||||||
<Justification>NULL</Justification>
|
<Justification>NULL</Justification>
|
||||||
<SourceApplicationName>O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\MICROSOFT OFFICE 2016\WINWORD.EXE\16.0.8027.1000</SourceApplicationName>
|
<SourceApplicationName>O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\MICROSOFT OFFICE 2016\WINWORD.EXE\16.0.8027.1000</SourceApplicationName>
|
||||||
<DestinationEnterpriseID>NULL</DestinationEnterpriseID>
|
<DestinationEnterpriseID>NULL</DestinationEnterpriseID>
|
||||||
<DestinationApplicationName></DestinationApplicationName>
|
<DestinationApplicationName></DestinationApplicationName>
|
||||||
<DataInfo>EnterpriseDataProtectionId|Object Descriptor|Rich Text Format|HTML Format|AnsiText|Text|EnhancedMetafile|Embed Source|Link Source|Link Source Descriptor|ObjectLink|Hyperlink</DataInfo>
|
<DataInfo>EnterpriseDataProtectionId|Object Descriptor|Rich Text Format|HTML Format|AnsiText|Text|EnhancedMetafile|Embed Source|Link Source|Link Source Descriptor|ObjectLink|Hyperlink</DataInfo>
|
||||||
</Log>
|
</Log>
|
||||||
</User>
|
</User>
|
||||||
</Reporting></Data></Item></Results><Final/></SyncBody></SyncML>
|
</Reporting></Data></Item></Results><Final/></SyncBody></SyncML>
|
||||||
```
|
```
|
||||||
|
|
||||||
## Collect WIP audit logs by using Windows Event Forwarding (for Windows desktop domain-joined devices only)
|
## Collect WIP audit logs by using Windows Event Forwarding (for Windows desktop domain-joined devices only)
|
||||||
|
@ -963,12 +963,12 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### [Windows security baselines](windows-security-baselines.md)
|
### [Windows security baselines](windows-security-baselines.md)
|
||||||
#### [Security Compliance Toolkit](security-compliance-toolkit-10.md)
|
#### [Security Compliance Toolkit](security-compliance-toolkit-10.md)
|
||||||
#### [Get support](get-support-for-security-baselines.md)
|
#### [Get support](get-support-for-security-baselines.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### [Windows 10 Mobile security guide](windows-10-mobile-security-guide.md)
|
### [Windows 10 Mobile security guide](windows-10-mobile-security-guide.md)
|
||||||
|
|
||||||
## [Change history for Threat protection](change-history-for-threat-protection.md)
|
## [Change history for Threat protection](change-history-for-threat-protection.md)
|
||||||
|
BIN
windows/security/threat-protection/images/powershell-example.png
Normal file
After Width: | Height: | Size: 83 KiB |
BIN
windows/security/threat-protection/images/vbs-example.png
Normal file
After Width: | Height: | Size: 116 KiB |
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Coordinated Malware Eradication
|
title: Coordinated Malware Eradication
|
||||||
description: Information and criteria regarding CME
|
description: The Coordinated Malware Eradication program aims to unite security organizations to disrupt the malware ecosystem.
|
||||||
keywords: security, malware
|
keywords: security, malware, malware eradication, Microsoft Malware Protection Center, MMPC
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: secure
|
ms.mktglfcycl: secure
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: How Microsoft identifies malware and potentially unwanted applications
|
title: How Microsoft identifies malware and potentially unwanted applications
|
||||||
description: criteria
|
description: Learn how Microsoft reviews software for unwanted behavior, advertising, privacy violations, and negative consumer opinion to determine if it is malware (malicious software) or potentially unwanted applications.
|
||||||
keywords: security, malware
|
keywords: security, malware, virus research threats, research malware, pc protection, computer infection, virus infection, descriptions, remediation, latest threats, MMPC, Microsoft Malware Protection Center, PUA, potentially unwanted applications
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: secure
|
ms.mktglfcycl: secure
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Industry collaboration programs
|
title: Industry collaboration programs
|
||||||
description: Describing the 3 industry collaboration programs
|
description: Microsoft industry-wide antimalware collaboration programs - Virus Information Alliance (VIA), Microsoft Virus Initiative (MVI), and Coordinated Malware Eradication (CME)
|
||||||
keywords: security, malware
|
keywords: security, malware, antivirus industry, antimalware Industry, collaboration programs, alliances, Virus Information Alliance, Microsoft Virus Initiative, Coordinated Malware Eradication, WDSI, MMPC, Microsoft Malware Protection Center, partnerships
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: secure
|
ms.mktglfcycl: secure
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
|
@ -26,18 +26,12 @@ Check out the following resources for information on how to submit and view subm
|
|||||||
|
|
||||||
### Detection criteria
|
### Detection criteria
|
||||||
|
|
||||||
To objectively identify malware and unidentified software, Microsoft applies a set of criteria for evaluating malicious or potentially harmful code.
|
To objectively identify malware and unidentified software, Microsoft applies a [set of criteria](criteria.md) for evaluating malicious or potentially harmful code.
|
||||||
|
|
||||||
For more information, see
|
|
||||||
|
|
||||||
### Developer questions
|
### Developer questions
|
||||||
|
|
||||||
Find more guidance about the file submission and detection dispute process in our FAQ for software developers.
|
Find more guidance about the file submission and detection dispute process in our [FAQ for software developers](developer-faq.md).
|
||||||
|
|
||||||
For more information, see
|
|
||||||
|
|
||||||
### Scan your software
|
### Scan your software
|
||||||
|
|
||||||
Use Windows Defender Antivirus to check your software against the latest definitions and cloud protection from Microsoft.
|
Use [Windows Defender Antivirus](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10?ocid=cx-docs-avreports) to check your software against the latest definitions and cloud protection from Microsoft.
|
||||||
|
|
||||||
For more information, see
|
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Exploits and exploit kits
|
title: Exploits and exploit kits
|
||||||
description: Learn about exploits, how they can infect devices, and what you can do to protect yourself.
|
description: Learn about how exploits use vulnerabilities in common software to give an attackers access to your computer and to install other malware.
|
||||||
keywords: security, malware, exploits, exploit kits, prevention, vulnerabilities
|
keywords: security, malware, exploits, exploit kits, prevention, vulnerabilities, Microsoft, Exploit malware family, exploits, java, flash, adobe, update software, prevent exploits, exploit pack, vulnerability, 0-day, holes, weaknesses, attack, Flash, Adobe, out-of-date software, out of date software, update, update software, reinfection, Java cache, reinfected, won't remove, won't clean, still detects, full scan, MSE, Defender, WDSI, MMPC, Microsoft Malware Protection Center
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: secure
|
ms.mktglfcycl: secure
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Macro malware
|
title: Macro malware
|
||||||
description: Learn about how macro malware works, how it can infect devices, and what you can do to protect yourself.
|
description: Learn about macro viruses and malware, which are embedded in documents and are used to drop malicious payloads and distribute other threats.
|
||||||
keywords: security, malware, macro, protection
|
keywords: security, malware, macro, protection, WDSI, MMPC, Microsoft Malware Protection Center, macro virus, macro malware, documents, viruses in Office, viruses in Word
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: secure
|
ms.mktglfcycl: secure
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Malware names
|
title: Malware names
|
||||||
description: Identifying malware vocabulary
|
description: Understand the malware naming convention used by Windows Defender Antivirus and other Microsoft antimalware.
|
||||||
keywords: security, malware, names
|
keywords: security, malware, names, Microsoft, MMPC, Microsoft Malware Protection Center, WDSI, malware name, malware prefix, malware type, virus name
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: secure
|
ms.mktglfcycl: secure
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Prevent malware infection
|
title: Prevent malware infection
|
||||||
description: Malware prevention best practices
|
description: Learn steps you can take to help prevent a malware or potentially unwanted software from infecting your computer.
|
||||||
keywords: security, malware, prevention, infection, tips
|
keywords: security, malware, prevention, infection, tips, Microsoft, MMPC, Microsoft Malware Protection Center, virus, trojan, worm, stop, prevent, full scan, infection, avoid malware, avoid trojan, avoid virus, infection, how, detection, security software, antivirus, updates, how malware works, how virus works, firewall, turn on, user privileges, limit, prevention, WDSI, MMPC, Microsoft Malware Protection Center
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: secure
|
ms.mktglfcycl: secure
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Ransomware
|
title: Ransomware
|
||||||
description: Learn about ransomware, how it works, and what you can do to protect yourself.
|
description: Learn how to protect your computer and network from ransomware attacks, which can stop you from accessing your files.
|
||||||
keywords: security, malware, ransomware, encryption, extortion, money, key, infection, prevention, tips
|
keywords: security, malware, ransomware, encryption, extortion, money, key, infection, prevention, tips, WDSI, MMPC, Microsoft Malware Protection Center, ransomware-as-a-service, ransom, ransomware downloader, protection, prevention, solution, exploit kits, backup, Cerber, Locky, WannaCry, WannaCrypt, Petya, Spora
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: secure
|
ms.mktglfcycl: secure
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Rootkits
|
title: Rootkits
|
||||||
description: Learn about rootkits, how they hide malware on your device, and what you can do to protect yourself.
|
description: Rootkits may be used by malware authors to hide malicious code on your computer and make malware or potentially unwanted software harder to remove.
|
||||||
keywords: security, malware, rootkit, hide, protection, hiding
|
keywords: security, malware, rootkit, hide, protection, hiding, WDSI, MMPC, Microsoft Malware Protection Center, rootkits, Sirefef, Rustock, Sinowal, Cutwail, malware, virus
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: secure
|
ms.mktglfcycl: secure
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: How Microsoft identifies malware and potentially unwanted applications
|
title: How Microsoft identifies malware and potentially unwanted applications
|
||||||
description: criteria
|
description: Learn how to submit files to Microsoft for malware analysis, how to track your submissions, and dispute detections.
|
||||||
keywords: security, malware
|
keywords: security, sample submission help, malware file, virus file, trojan file, submit, send to Microsoft, submit a sample, virus, trojan, worm, undetected, doesn’t detect, email microsoft, email malware, I think this is malware, I think it's a virus, where can I send a virus, is this a virus, MSE, doesn’t detect, no signature, no detection, suspect file, MMPC, Microsoft Malware Protection Center, researchers, analyst, WDSI
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: secure
|
ms.mktglfcycl: secure
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Tech Support Scams
|
title: Tech Support Scams
|
||||||
description: Learn about how supply chain attacks work, deliver malware do your devices, and what you can do to protect yourself
|
description: Microsoft security software can protect you from tech support scams that claims to scan for malware or viruses and then shows you fake detections and warnings.
|
||||||
keywords: security, malware, tech support, scam, protection, trick, spoof, fake, error messages, report
|
keywords: security, malware, tech support, scam, protection, trick, spoof, fake, error messages, report, rogue security software, fake, antivirus, fake software, rogue, threats, fee, removal fee, upgrade, pay for removal, install full version, trial, lots of threats, scanner, scan, clean, computer, security, program, XP home security, fake microsoft, activate, activate scan, activate antivirus, warnings, pop-ups, security warnings, security pop-ups tech support scams, fake Microsoft error notification, fake virus alert, fake product expiration, fake Windows activation, scam web pages, scam phone numbers, telephone numbers, MMPC, WDSI, Microsoft Malware Protection Center, tech support scam numbers
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: secure
|
ms.mktglfcycl: secure
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Trojan malware
|
title: Trojan malware
|
||||||
description: Learn about how trojans work, deliver malware do your devices, and what you can do to protect yourself.
|
description: Trojans are a type of threat that can infect your device. This page tells you what they are and how to remove them.
|
||||||
keywords: security, malware, protection, trojan, download, file, infection
|
keywords: security, malware, protection, trojan, download, file, infection, trojans, virus, protection, cleanup, removal, antimalware, antivirus, WDSI, MMPC, Microsoft Malware Protection Center, malware types
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: secure
|
ms.mktglfcycl: secure
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
|