mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 21:37:22 +00:00
Merge branch 'master' into v-mathavale-5560668-part8
This commit is contained in:
commit
a595fda31b
@ -9,7 +9,7 @@ metadata:
|
||||
keywords: Microsoft Edge Legacy, Windows 10
|
||||
ms.localizationpriority: medium
|
||||
ms.prod: edge
|
||||
author: shortpatti
|
||||
author: dougeby
|
||||
ms.author: pashort
|
||||
ms.topic: landing-page
|
||||
ms.devlang: na
|
||||
|
@ -11,7 +11,7 @@ metadata:
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: landing-page # Required
|
||||
ms.collection: collection # Optional; Remove if no collection is used.
|
||||
author: shortpatti #Required; your GitHub user alias, with correct capitalization.
|
||||
author: dougeby #Required; your GitHub user alias, with correct capitalization.
|
||||
ms.author: pashort #Required; microsoft alias of author; optional team alias.
|
||||
ms.date: 07/07/2020 #Required; mm/dd/yyyy format.
|
||||
|
||||
|
@ -62,7 +62,7 @@ sections:
|
||||
|
||||
- question: Will Internet Explorer 11 continue to receive updates?
|
||||
answer: |
|
||||
We're committed to keeping Internet Explorer a supported, reliable, and safe browser. Internet Explorer is still a component of Windows and follows the support lifecycle of the OS on which it's installed. For details, see [Lifecycle FAQ - Internet Explorer](https://support.microsoft.com/help/17454/). While we continue to support and update Internet Explorer, the latest features and platform updates will only be available in Microsoft Edge.
|
||||
We're committed to keeping Internet Explorer a supported, reliable, and safe browser. Internet Explorer is still a component of Windows and follows the support lifecycle of the OS on which it's installed. For details, see [Lifecycle FAQ - Internet Explorer](/lifecycle/faq/internet-explorer-microsoft-edge). While we continue to support and update Internet Explorer, the latest features and platform updates will only be available in Microsoft Edge.
|
||||
|
||||
- question: How do I find out which version of Microsoft Edge I have?
|
||||
answer: |
|
||||
|
@ -14,9 +14,7 @@ ms.author: dansimp
|
||||
[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
|
||||
|
||||
|
||||
Return to: [Deprecated document modes and Internet Explorer 11](deprecated-document-modes.md)<br>
|
||||
Return to: [Deprecated document modes and Internet Explorer 11](deprecated-document-modes.md)
|
||||
|
||||
<p>
|
||||
<img src="images/docmode-decisions-lg.png" alt="Full-sized flowchart detailing how document modes are chosen in IE11" width="1355" height="1625" style="max-width:none;">
|
||||
</p>
|
||||
:::image type="content" source="images/docmode-decisions-lg.png" alt-text="Full-sized flowchart detailing how document modes are chosen in IE11" lightbox="images/docmode-decisions-lg.png":::
|
||||
|
||||
|
@ -36,11 +36,4 @@ Use the topics in this section to learn about how to auto detect your settings,
|
||||
|------|------------|
|
||||
|[Auto detect settings Internet Explorer 11](auto-detect-settings-for-ie11.md) |Guidance about how to update your automatic detection of DHCP and DNS servers. |
|
||||
|[Auto configuration settings for Internet Explorer 11](auto-configuration-settings-for-ie11.md) |Guidance about how to add, update and lock your auto configuration settings. |
|
||||
|[Auto proxy configuration settings for Internet Explorer 11](auto-proxy-configuration-settings-for-ie11.md) |Guidance about how to add, update, and lock your auto-proxy settings. |
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|[Auto proxy configuration settings for Internet Explorer 11](auto-proxy-configuration-settings-for-ie11.md) |Guidance about how to add, update, and lock your auto-proxy settings. |
|
||||
|
@ -24,9 +24,6 @@ summary: |
|
||||
sections:
|
||||
- name: Ignored
|
||||
questions:
|
||||
- question: |
|
||||
Frequently Asked Questions
|
||||
answer: |
|
||||
- question: |
|
||||
What operating system does IE11 run on?
|
||||
answer: |
|
||||
|
@ -148,7 +148,7 @@ sections:
|
||||
- question: |
|
||||
Where to find Internet Explorer security zones registry entries
|
||||
answer: |
|
||||
Most of the Internet Zone entries can be found in [Internet Explorer security zones registry entries for advanced users](https://support.microsoft.com/help/182569/internet-explorer-security-zones-registry-entries-for-advanced-users).
|
||||
Most of the Internet Zone entries can be found in [Internet Explorer security zones registry entries for advanced users](/troubleshoot/browsers/ie-security-zones-registry-entries).
|
||||
|
||||
This article was written for Internet Explorer 6 but is still applicable to Internet Explorer 11.
|
||||
|
||||
@ -193,7 +193,7 @@ sections:
|
||||
answer: |
|
||||
Internet Explorer 11 is the last major version of Internet Explorer. Internet Explorer 11 will continue receiving security updates and technical support for the lifecycle of the version of Windows on which it is installed.
|
||||
|
||||
For more information, see [Lifecycle FAQ — Internet Explorer and Edge](https://support.microsoft.com/help/17454/lifecycle-faq-internet-explorer).
|
||||
For more information, see [Lifecycle FAQ — Internet Explorer and Edge](/lifecycle/faq/internet-explorer-microsoft-edge).
|
||||
|
||||
- question: |
|
||||
How to configure TLS (SSL) for Internet Explorer
|
||||
|
@ -2,6 +2,15 @@
|
||||
|
||||
|
||||
|
||||
## Week of November 29, 2021
|
||||
|
||||
|
||||
| Published On |Topic title | Change |
|
||||
|------|------------|--------|
|
||||
| 11/29/2021 | [What is Windows 11 SE](/education/windows/windows-11-se-overview) | added |
|
||||
| 11/29/2021 | [Windows 11 SE settings list](/education/windows/windows-11-se-settings-list) | added |
|
||||
|
||||
|
||||
## Week of November 15, 2021
|
||||
|
||||
|
||||
@ -12,13 +21,3 @@
|
||||
| 11/18/2021 | [Deploy Windows 10 in a school district (Windows 10)](/education/windows/deploy-windows-10-in-a-school-district) | modified |
|
||||
| 11/18/2021 | [Deploy Windows 10 in a school (Windows 10)](/education/windows/deploy-windows-10-in-a-school) | modified |
|
||||
| 11/18/2021 | [For IT administrators get Minecraft Education Edition](/education/windows/school-get-minecraft) | modified |
|
||||
|
||||
|
||||
## Week of October 25, 2021
|
||||
|
||||
|
||||
| Published On |Topic title | Change |
|
||||
|------|------------|--------|
|
||||
| 10/28/2021 | [Deploy Windows 10 in a school district (Windows 10)](/education/windows/deploy-windows-10-in-a-school-district) | modified |
|
||||
| 10/28/2021 | [Deploy Windows 10 in a school (Windows 10)](/education/windows/deploy-windows-10-in-a-school) | modified |
|
||||
| 10/28/2021 | [Windows 10 for Education (Windows 10)](/education/windows/index) | modified |
|
||||
|
@ -20,7 +20,7 @@ ms.topic: article
|
||||
- Windows 11 SE
|
||||
- Microsoft Intune for Education
|
||||
|
||||
Windows 11 SE is a new edition of Windows that's designed for education. It runs on web-first devices that use essential education apps. Microsoft Office 365 is preinstalled.
|
||||
Windows 11 SE is a new edition of Windows that's designed for education. It runs on web-first devices that use essential education apps. Microsoft Office 365 is preinstalled (subscription sold separately).
|
||||
|
||||
For education customers seeking cost-effective devices, Microsoft Windows 11 SE is a great choice. Windows 11 SE includes the following benefits:
|
||||
|
||||
|
@ -62,6 +62,45 @@ The following settings can't be changed.
|
||||
| Administrative tools | Administrative tools, such as the command prompt and Windows PowerShell, can't be opened. Windows PowerShell scripts deployed using Microsoft Endpoint Manager can run. |
|
||||
| Apps | Only certain apps are allowed to run on Windows 11 SE. For more info on what apps can run on Windows 11 SE, see [Windows 11 SE for Education overview](windows-11-se-overview.md). |
|
||||
|
||||
## What's available in the Settings app
|
||||
|
||||
On Windows 11 SE devices, the Settings app shows the following setting pages. Depending on the hardware, some setting pages might not be shown.
|
||||
|
||||
- Accessibility
|
||||
|
||||
- Accounts
|
||||
- Email & accounts
|
||||
|
||||
- Apps
|
||||
|
||||
- Bluetooth & devices
|
||||
- Bluetooth
|
||||
- Printers & scanners
|
||||
- Mouse
|
||||
- Touchpad
|
||||
- Typing
|
||||
- Pen
|
||||
- AutoPlay
|
||||
|
||||
- Network & internet
|
||||
- WiFi
|
||||
- VPN
|
||||
|
||||
- Personalization
|
||||
- Taskbar
|
||||
|
||||
- Privacy & security
|
||||
|
||||
- System
|
||||
- Display
|
||||
- Notifications
|
||||
- Tablet mode
|
||||
- Multitasking
|
||||
- Projecting to this PC
|
||||
|
||||
- Time & Language
|
||||
- Language & region
|
||||
|
||||
## Next steps
|
||||
|
||||
[Windows 11 SE for Education overview](windows-11-se-overview.md)
|
||||
|
@ -34,7 +34,7 @@ In this walkthrough, we'll show you how to deploy and manage a full cloud IT sol
|
||||
- Create policies and app deployment rules
|
||||
- Log in as a user and start using your Windows device
|
||||
|
||||
Go to the <a href="https://business.microsoft.com" target="_blank">Microsoft Business site</a> and select **Products** to learn more about pricing and purchasing options for your business.
|
||||
Go to [Microsoft 365 for business](https://www.microsoft.com/microsoft-365/business) to learn more about pricing and purchasing options for your business.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@ -50,16 +50,17 @@ Here's a few things to keep in mind before you get started:
|
||||
To set up a cloud infrastructure for your organization, follow the steps in this section.
|
||||
|
||||
### 1.1 Set up Office 365 for business
|
||||
See <a href="https://support.office.com/article/Set-up-Office-365-for-business-6a3a29a0-e616-4713-99d1-15eda62d04fa" target="_blank">Set up Office 365 for business</a> to learn more about the setup steps for businesses and nonprofits who have Office 365. You can watch video and learn how to:
|
||||
|
||||
See [Microsoft 365 admin center for business](/microsoft-365/admin) and [Microsoft 365 resources for nonprofits](https://www.microsoft.com/nonprofits/microsoft-365) to learn more about the setup steps for businesses and nonprofits who have Office 365. You can learn how to:
|
||||
- Plan your setup
|
||||
- Create Office 365 accounts and how to add your domain.
|
||||
- Install Office
|
||||
|
||||
To set up your Microsoft 365 for business tenant, see <a href="https://support.office.com/article/Get-started-with-Office-365-for-Business-d6466f0d-5d13-464a-adcb-00906ae87029" target="_blank">Get Started with Microsoft 365 for business</a>.
|
||||
To set up your Microsoft 365 for business tenant, see [Get Started with Microsoft 365 for business](/microsoft-365/business-video/what-is-microsoft-365).
|
||||
|
||||
If you're new at setting up Office 365, and you'd like to see how it's done, you can follow these steps to get started:
|
||||
|
||||
1. Go to the <a href="https://products.office.com/business/office-365-affiliate-program-buy-business-premium" target="_blank">Office 365</a> page in the <a href="https://business.microsoft.com" target="_blank">Microsoft Business site</a>. Select **Try now** to use the Microsoft 365 Business Standard Trial or select **Buy now** to sign up for Microsoft 365 Business Standard. In this walkthrough, we'll select **Try now**.
|
||||
1. Go to [Try or buy a Microsoft 365 for business subscription](/microsoft-365/commerce/try-or-buy-microsoft-365). In this walkthrough, we'll select **Try now**.
|
||||
|
||||
**Figure 1** - Try or buy Office 365
|
||||
|
||||
@ -68,7 +69,7 @@ If you're new at setting up Office 365, and you'd like to see how it's done, you
|
||||
2. Fill out the sign up form and provide information about you and your company.
|
||||
3. Create a user ID and password to use to sign into your account.
|
||||
|
||||
This step creates an onmicrosoft.com email address. You can use this email address to sign in to the various admin centers. Save your sign-in info so you can use it to sign into <a href="https://portal.office.com" target="_blank">https://portal.office.com</a> (the admin portal).
|
||||
This step creates an `onmicrosoft.com` email address. You can use this email address to sign in to the various admin centers. Save your sign-in info so you can use it to sign into [https://portal.office.com](https://portal.office.com) (the admin portal).
|
||||
|
||||
4. Select **Create my account** and then enter the phone number you used in step 2 to verify your identity. You'll be asked to enter your verification code.
|
||||
5. Select **You're ready to go...** which will take you to the Microsoft 365 admin center.
|
||||
@ -78,7 +79,7 @@ If you're new at setting up Office 365, and you'd like to see how it's done, you
|
||||
|
||||
**Figure 2** - Microsoft 365 admin center
|
||||
|
||||

|
||||
:::image type="content" alt-text="Opens the Microsoft 365 admin center." source="images/office365_portal.png":::
|
||||
|
||||
|
||||
6. Select the **Admin** tile to go to the admin center.
|
||||
@ -88,22 +89,22 @@ If you're new at setting up Office 365, and you'd like to see how it's done, you
|
||||
|
||||
**Figure 3** - Admin center
|
||||
|
||||

|
||||
:::image type="content" alt-text="Complete the Office 365 setup in the Microsoft 365 admin center." source="images/office365_admin_portal.png":::
|
||||
|
||||
|
||||
8. Go back to the <a href="https://portal.office.com/adminportal/home#/homepage" target="_blank">admin center</a> to add or buy a domain.
|
||||
8. Go back to the [admin center](https://portal.office.com/adminportal/home#/homepage) to add or buy a domain.
|
||||
1. Select the **Domains** option.
|
||||
|
||||
**Figure 4** - Option to add or buy a domain
|
||||
|
||||

|
||||
:::image type="content" alt-text="Add or buy a domain in admin center." source="images/office365_buy_domain.png":::
|
||||
|
||||
|
||||
2. In the **Home > Domains** page, you will see the Microsoft-provided domain, such as `fabrikamdesign.onmicrosoft.com`.
|
||||
|
||||
**Figure 5** - Microsoft-provided domain
|
||||
|
||||

|
||||
:::image type="content" alt-text="Microsoft-provided domain." source="images/office365_ms_provided_domain.png":::
|
||||
|
||||
- If you already have a domain, select **+ Add domain** to add your existing domain. If you select this option, you'll be required to verify that you own the domain. Follow the steps in the wizard to verify your domain.
|
||||
- If you don't already own a domain, select **+ Buy domain**. If you're using a trial plan, you'll be required to upgrade your trial plan in order to buy a domain. Choose the subscription plan to use for your business and provide the details to complete your order.
|
||||
@ -112,7 +113,7 @@ If you're new at setting up Office 365, and you'd like to see how it's done, you
|
||||
|
||||
**Figure 6** - Domains
|
||||
|
||||

|
||||
:::image type="content" alt-text="Verify your domains in the admin center." source="images/office365_additional_domain.png":::
|
||||
|
||||
### 1.2 Add users and assign product licenses
|
||||
Once you've set up Office and added your domain, it's time to add users so they have access to Office 365. People in your organization need an account before they can sign in and access Office 365. The easiest way to add users is to add them one at a time in the Microsoft 365 admin center.
|
||||
@ -121,55 +122,55 @@ When adding users, you can also assign admin privileges to certain users in your
|
||||
|
||||
**To add users and assign product licenses**
|
||||
|
||||
1. In the <a href="https://portal.office.com/adminportal/home#/homepage" target="_blank">admin center</a>, select **Users > Active users**.
|
||||
1. In the [admin center](https://portal.office.com/adminportal/home#/homepage), select **Users > Active users**.
|
||||
|
||||
**Figure 7** - Add users
|
||||
|
||||

|
||||
:::image type="content" alt-text="Add Office 365 users." source="images/office365_users.png":::
|
||||
|
||||
2. In the **Home > Active users** page, add users individually or in bulk.
|
||||
- To add users one at a time, select **+ Add a user**.
|
||||
|
||||
If you select this option, you'll see the **New user** screen and you can add details about the new user including their name, user name, role, and so on. You also have the opportunity to assign **Product licenses**. For detailed step-by-step info on adding a user account, see *Add a user account in the admin center* in <a href="https://support.office.com/article/Add-users-individually-or-in-bulk-to-Office-365-Admin-Help-1970f7d6-03b5-442f-b385-5880b9c256ec" target="_blank">Add users individually or in bulk to Office 365 - Admin Help</a>.
|
||||
If you select this option, you'll see the **New user** screen and you can add details about the new user including their name, user name, role, and so on. You also have the opportunity to assign **Product licenses**. For detailed step-by-step info on adding a user account, see [Add users and assign licenses at the same time](/microsoft-365/admin/add-users/add-users).
|
||||
|
||||
**Figure 8** - Add an individual user
|
||||
|
||||

|
||||
:::image type="content" alt-text="Add an individual user." source="images/office365_add_individual_user.png":::
|
||||
|
||||
- To add multiple users at once, select **More** and then choose **+ Import multiple users**. If you select this option, you'll need to create and upload a CSV file containing the list of users.
|
||||
|
||||
The **Import multiple users** screen includes a link where you can learn more about importing multiple users and also links for downloading a sample CSV file (one with headers only and another with headers and sample user information). For detailed step-by-step info on adding multiple users to Office 365, see <a href="https://support.office.com/article/Add-several-users-at-the-same-time-to-Office-365-Admin-Help-1f5767ed-e717-4f24-969c-6ea9d412ca88" target="_blank">Add several users at the same time to Office 365 - Admin Help</a>. Once you've added all the users, don't forget to assign **Product licenses** to the new users.
|
||||
The **Import multiple users** screen includes a link where you can learn more about importing multiple users and also links for downloading a sample CSV file (one with headers only and another with headers and sample user information). For detailed step-by-step info on adding multiple users to Office 365, see [Add users and assign licenses at the same time](/microsoft-365/admin/add-users/add-users). Once you've added all the users, don't forget to assign **Product licenses** to the new users.
|
||||
|
||||
**Figure 9** - Import multiple users
|
||||
|
||||

|
||||
:::image type="content" alt-text="Import multiple users." source="images/office365_import_multiple_users.png":::
|
||||
|
||||
3. Verify that all the users you added appear in the list of **Active users**. The **Status** should indicate the product licenses that were assigned to them.
|
||||
|
||||
**Figure 10** - List of active users
|
||||
|
||||

|
||||
:::image type="content" alt-text="Verify users and assigned product licenses." source="images/o365_active_users.png":::
|
||||
|
||||
### 1.3 Add Microsoft Intune
|
||||
Microsoft Intune provides mobile device management, app management, and PC management capabilities from the cloud. Using Intune, organizations can provide their employees with access to apps, data, and corporate resources from anywhere on almost any device while helping to keep corporate information secure. To learn more, see <a href="/intune/understand-explore/introduction-to-microsoft-intune" target="_blank">What is Intune?</a>
|
||||
Microsoft Intune provides mobile device management, app management, and PC management capabilities from the cloud. Using Intune, organizations can provide their employees with access to apps, data, and corporate resources from anywhere on almost any device while helping to keep corporate information secure. To learn more, see [Microsoft Intune is an MDM and MAM provider](/mem/intune/fundamentals/what-is-intune).
|
||||
|
||||
**To add Microsoft Intune to your tenant**
|
||||
|
||||
1. In the <a href="https://portal.office.com/adminportal/home#/homepage" target="_blank">admin center</a>, select **Billing > Purchase services**.
|
||||
1. In the [admin center](https://portal.office.com/adminportal/home#/homepage), select **Billing > Purchase services**.
|
||||
2. In the **Home > Purchase services** screen, search for **Microsoft Intune**. Hover over **Microsoft Intune** to see the options to start a free 30-day trial or to buy now.
|
||||
3. Confirm your order to enable access to Microsoft Intune.
|
||||
4. In the admin center, the Intune licenses will show as available and ready to be assigned to users. Select **Users > Active users** and then edit the product licenses assigned to the users to turn on **Intune A Direct**.
|
||||
|
||||
**Figure 11** - Assign Intune licenses
|
||||
|
||||

|
||||
:::image type="content" alt-text="Assign Microsoft Intune licenses to users." source="images/o365_assign_intune_license.png":::
|
||||
|
||||
5. In the admin center, confirm that **Intune** shows up in the list under **Admin centers**. If it doesn't, sign out and then sign back in and then check again.
|
||||
6. Select **Intune**. This step opens the Endpoint Manager admin center.
|
||||
|
||||
**Figure 12** - Microsoft Intune management portal
|
||||
|
||||

|
||||
:::image type="content" alt-text="Microsoft Intune management portal." source="images/intune_portal_home.png":::
|
||||
|
||||
Intune should now be added to your tenant. We'll come back to Intune later when we [Configure Microsoft Store for Business for app distribution](#17-configure-microsoft-store-for-business-for-app-distribution).
|
||||
|
||||
@ -178,7 +179,7 @@ Microsoft Azure is an open and flexible cloud platform that enables you to quick
|
||||
|
||||
**To add Azure AD to your domain**
|
||||
|
||||
1. In the <a href="https://portal.office.com/adminportal/home#/homepage" target="_blank">admin center</a>, select **Admin centers > Azure AD**.
|
||||
1. In the [admin center](https://portal.office.com/adminportal/home#/homepage), select **Admin centers > Azure AD**.
|
||||
|
||||
> [!NOTE]
|
||||
> You will need Azure AD Premium to configure automatic MDM enrollment with Intune.
|
||||
@ -187,57 +188,57 @@ Microsoft Azure is an open and flexible cloud platform that enables you to quick
|
||||
|
||||
**Figure 13** - Access to Azure AD is not available
|
||||
|
||||

|
||||
:::image type="content" alt-text="Access to Azure AD not available." source="images/azure_ad_access_not_available.png":::
|
||||
|
||||
3. From the error message, select the country/region for your business. The region should match with the location you specified when you signed up for Office 365.
|
||||
4. Select **Azure subscription**. This step will take you to a free trial sign up screen.
|
||||
|
||||
**Figure 14** - Sign up for Microsoft Azure
|
||||
|
||||

|
||||
:::image type="content" alt-text="Sign up for Microsoft Azure." source="images/azure_ad_sign_up_screen.png":::
|
||||
|
||||
5. In the **Free trial sign up** screen, fill in the required information and then click **Sign up**.
|
||||
6. After you sign up, you should see the message that your subscription is ready. Click **Start managing my service**.
|
||||
|
||||
**Figure 15** - Start managing your Azure subscription
|
||||
|
||||

|
||||
:::image type="content" alt-text="Start managing your Azure subscription." source="images/azure_ad_successful_signup.png":::
|
||||
|
||||
This step will take you to the <a href="https://portal.azure.com" target="_blank">Microsoft Azure portal</a>.
|
||||
This step will take you to the [Microsoft Azure portal](https://portal.azure.com).
|
||||
|
||||
### 1.5 Add groups in Azure AD
|
||||
This section is the walkthrough is optional. However, we recommend that you create groups in Azure AD to manage access to corporate resources, such as apps, policies and settings, and so on. For more information, see <a href="/azure/active-directory/active-directory-manage-groups" target="_blank">Managing access to resources with Azure Active Directory groups</a>.
|
||||
This section is the walkthrough is optional. However, we recommend that you create groups in Azure AD to manage access to corporate resources, such as apps, policies and settings, and so on. For more information, see [Managing access to resources with Azure Active Directory groups](/azure/active-directory/active-directory-manage-groups.
|
||||
|
||||
To add Azure AD group(s), we will use the <a href="https://manage.windowsazure.com/" target="_blank">classic Azure portal (https://manage.windowsazure.com)</a>. See <a href="/azure/active-directory/active-directory-accessmanagement-manage-groups" target="_blank">Managing groups in Azure Active Directory</a> for more information about managing groups.
|
||||
To add Azure AD group(s), use the [Microsoft Azure portal](https://portal.azure.com). See [Managing groups in Azure Active Directory](/azure/active-directory/active-directory-accessmanagement-manage-groups) for more information about managing groups.
|
||||
|
||||
**To add groups in Azure AD**
|
||||
|
||||
1. If this is the first time you're setting up your directory, when you navigate to the **Azure Active Directory** node in the <a href="https://manage.windowsazure.com/" target="_blank">classic Azure portal</a>, you will see a screen informing you that your directory is ready for use.
|
||||
1. If this is the first time you're setting up your directory, when you navigate to the **Azure Active Directory** node, you will see a screen informing you that your directory is ready for use.
|
||||
|
||||
Afterwards, you should see a list of active directories. In the following example, **Fabrikam Design** is the active directory.
|
||||
|
||||
**Figure 16** - Azure first sign-in screen
|
||||
|
||||

|
||||
:::image type="content" alt-text="Select Azure AD." source="images/azure_portal_classic_configure_directory.png":::
|
||||
|
||||
2. Select the directory (such as Fabrikam Design) to go to the directory's home page.
|
||||
|
||||
**Figure 17** - Directory home page
|
||||
|
||||

|
||||
:::image type="content" alt-text="Directory home page." source="images/azure_portal_classic_directory_ready.png":::
|
||||
|
||||
3. From the menu options on top, select **Groups**.
|
||||
|
||||
**Figure 18** - Azure AD groups
|
||||
|
||||

|
||||
:::image type="content" alt-text="Add groups in Azure AD." source="images/azure_portal_classic_groups.png":::
|
||||
|
||||
4. Select **Add a group** (from the top) or **Add group** at the bottom.
|
||||
5. In the **Add Group** window, add a name, group type, and description for the group and click the checkmark to save your changes. The new group will appear on the groups list.
|
||||
|
||||
**Figure 19** - Newly added group in Azure AD
|
||||
|
||||

|
||||
:::image type="content" alt-text="Verify the new group appears on the list." source="images/azure_portal_classic_all_users_group.png":::
|
||||
|
||||
6. In the **Groups** tab, select the arrow next to the group (such as **All users**), add members to the group, and then save your changes.
|
||||
|
||||
@ -245,34 +246,34 @@ To add Azure AD group(s), we will use the <a href="https://manage.windowsazure.c
|
||||
|
||||
**Figure 20** - Members in the new group
|
||||
|
||||

|
||||
:::image type="content" alt-text="Members added to the new group." source="images/azure_portal_classic_members_added.png":::
|
||||
|
||||
7. Repeat steps 2-6 to add other groups. You can add groups based on their roles in your company, based on the apps that each group can use, and so on.
|
||||
|
||||
### 1.6 Configure automatic MDM enrollment with Intune
|
||||
Now that you have Azure AD Premium and have it properly configured, you can configure automatic MDM enrollment with Intune, which allows users to enroll their Windows devices into Intune management, join their devices directly to Azure AD, and get access to Office 365 resources after sign in.
|
||||
|
||||
You can read <a href="https://blogs.technet.microsoft.com/enterprisemobility/2015/08/14/windows-10-azure-ad-and-microsoft-intune-automatic-mdm-enrollment-powered-by-the-cloud/" target="_blank">this blog post</a> to learn how you can combine login, Azure AD Join, and Intune MDM enrollment into an easy step so that you can bring your devices into a managed state that complies with the policies for your organization. We will use this blog post as our guide for this part of the walkthrough.
|
||||
You can read the [Windows 10, Azure AD and Microsoft Intune blog post](https://blogs.technet.microsoft.com/enterprisemobility/2015/08/14/windows-10-azure-ad-and-microsoft-intune-automatic-mdm-enrollment-powered-by-the-cloud/) to learn how you can combine login, Azure AD Join, and Intune MDM enrollment into an easy step so that you can bring your devices into a managed state that complies with the policies for your organization. We will use this blog post as our guide for this part of the walkthrough.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> We will use the classic Azure portal instead of the new portal to configure automatic MDM enrollment with Intune.
|
||||
|
||||
**To enable automatic MDM enrollment**
|
||||
|
||||
1. In the <a href="https://manage.windowsazure.com/" target="_blank">classic Azure portal</a>, click on your company's Azure Active Directory to go back to the main window. Select **Applications** from the list of directory menu options.
|
||||
1. In the Azure portal, click on your company's Azure Active Directory to go back to the main window. Select **Applications** from the list of directory menu options.
|
||||
|
||||
The list of applications for your company will appear. **Microsoft Intune** will be one of the applications on the list.
|
||||
|
||||
**Figure 21** - List of applications for your company
|
||||
|
||||

|
||||
:::image type="content" alt-text="List of applications for your company." source="images/azure_portal_classic_applications.png":::
|
||||
|
||||
2. Select **Microsoft Intune** to configure the application.
|
||||
3. In the Microsoft Intune configuration page, click **Configure** to start automatic MDM enrollment configuration with Intune.
|
||||
|
||||
**Figure 22** - Configure Microsoft Intune in Azure
|
||||
|
||||

|
||||
:::image type="content" alt-text="Configure Microsoft Intune in Azure." source="images/azure_portal_classic_configure_intune_app.png":::
|
||||
|
||||
4. In the Microsoft Intune configuration page:
|
||||
- In the **Properties** section, you should see a list of URLs for MDM discovery, MDM terms of use, and MDM compliance.
|
||||
@ -291,66 +292,66 @@ You can read <a href="https://blogs.technet.microsoft.com/enterprisemobility/201
|
||||
|
||||
**Figure 23** - Configure Microsoft Intune
|
||||
|
||||

|
||||
:::image type="content" alt-text="Configure automatic MDM enrollment with Intune." source="images/azure_portal_classic_configure_intune_mdm_enrollment.png":::
|
||||
|
||||
### 1.7 Configure Microsoft Store for Business for app distribution
|
||||
Next, you'll need to configure Microsoft Store for Business to distribute apps with a management tool such as Intune.
|
||||
|
||||
In this part of the walkthrough, we'll be working on the <a href="https://manage.microsoft.com/" target="_blank">Microsoft Intune management portal</a> and <a href="https://businessstore.microsoft.com/Store/Apps" target="_blank">Microsoft Store for Business</a>.
|
||||
In this part of the walkthrough, use the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) and [Microsoft Store for Business](https://businessstore.microsoft.com/Store/Apps).
|
||||
|
||||
**To associate your Store account with Intune and configure synchronization**
|
||||
|
||||
1. From the <a href="https://manage.microsoft.com/" target="_blank">Microsoft Intune management portal</a>, select **Admin**.
|
||||
1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
2. In the **Administration** workspace, click **Mobile Device Management**. If this is the first item you're using the portal, click **manage mobile devices** in the **Mobile Device Management** window. The page will refresh and you'll have new options under **Mobile Device Management**.
|
||||
|
||||
**Figure 24** - Mobile device management
|
||||
|
||||

|
||||
:::image type="content" alt-text="Set up mobile device management in Intune." source="images/intune_admin_mdm_configure.png":::
|
||||
|
||||
3. Sign into <a href="https://businessstore.microsoft.com/Store/Apps" target="_blank">Microsoft Store for Business</a> using the same tenant account that you used to sign into Intune.
|
||||
3. Sign into [Microsoft Store for Business](https://businessstore.microsoft.com/Store/Apps) using the same tenant account that you used to sign into Intune.
|
||||
4. Accept the EULA.
|
||||
5. In the Store portal, select **Settings > Management tools** to go to the management tools page.
|
||||
6. In the **Management tools** page, find **Microsoft Intune** on the list and click **Activate** to get Intune ready to use with Microsoft Store for Business.
|
||||
|
||||
**Figure 25** - Activate Intune as the Store management tool
|
||||
|
||||

|
||||
:::image type="content" alt-text="Activate Intune from the Store portal." source="images/wsfb_management_tools_activate.png":::
|
||||
|
||||
7. Go back to the <a href="https://manage.microsoft.com/" target="_blank">Intune management portal</a>, select **Admin > Mobile Device Management**, expand **Windows**, and then choose **Store for Business**.
|
||||
7. Go back to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Admin > Mobile Device Management**, expand **Windows**, and then choose **Store for Business**.
|
||||
8. In the **Microsoft Store for Business** page, select **Configure Sync** to sync your Store for Business volume-purchased apps with Intune.
|
||||
|
||||
**Figure 26** - Configure Store for Business sync in Intune
|
||||
|
||||

|
||||
:::image type="content" alt-text="Configure Store for Business sync in Intune." source="images/intune_admin_mdm_store_sync.png":::
|
||||
|
||||
9. In the **Configure Microsoft Store for Business app sync** dialog box, check **Enable Microsoft Store for Business sync**. In the **Language** dropdown list, choose the language in which you want apps from the Store to be displayed in the Intune console and then click **OK**.
|
||||
|
||||
**Figure 27** - Enable Microsoft Store for Business sync in Intune
|
||||
|
||||

|
||||
:::image type="content" alt-text="Enable Store for Business sync in Intune." source="images/intune_configure_store_app_sync_dialog.png":::
|
||||
|
||||
The **Microsoft Store for Business** page will refresh and it will show the details from the sync.
|
||||
|
||||
**To buy apps from the Store**
|
||||
|
||||
In your <a href="https://businessstore.microsoft.com/Store/Apps" target="_blank">Microsoft Store for Business</a> portal, you can see the list of apps that you own by going to **Manage > Inventory**. You should see the following apps in your inventory:
|
||||
In your [Microsoft Store for Business portal](https://businessstore.microsoft.com/Store/Apps), you can see the list of apps that you own by going to **Manage > Inventory**. You should see the following apps in your inventory:
|
||||
- Sway
|
||||
- OneNote
|
||||
- PowerPoint Mobile
|
||||
- Excel Mobile
|
||||
- Word Mobile
|
||||
|
||||
In the <a href="https://manage.microsoft.com/" target="_blank">Intune management portal</a>, select **Apps > Apps > Volume-Purchased Apps** and verify that you can see the same list of apps appear on Intune.
|
||||
In the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Apps > Apps > Volume-Purchased Apps** and verify that you can see the same list of apps appear on Intune.
|
||||
|
||||
In the following example, we'll show you how to buy apps through the Microsoft Store for Business and then make sure the apps appear on Intune.
|
||||
|
||||
**Example 1 - Add other apps like Reader and InstaNote**
|
||||
|
||||
1. In the <a href="https://businessstore.microsoft.com/Store/Apps" target="_blank">Microsoft Store for Business</a> portal, click **Shop**, scroll down to the **Made by Microsoft** category, and click **Show all** to see all the Microsoft apps in the list.
|
||||
1. In the [Microsoft Store for Business portal](https://businessstore.microsoft.com/Store/Apps), click **Shop**, scroll down to the **Made by Microsoft** category, and click **Show all** to see all the Microsoft apps in the list.
|
||||
|
||||
**Figure 28** - Shop for Store apps
|
||||
|
||||

|
||||
:::image type="content" alt-text="Shop for Store apps." source="images/wsfb_shop_microsoft_apps.png":::
|
||||
|
||||
2. Click to select an app, such as **Reader**. This opens the app page.
|
||||
3. In the app's Store page, click **Get the app**. You should see a dialog that confirms your order. Click **Close**. This will refresh the app's Store page.
|
||||
@ -360,7 +361,7 @@ In the following example, we'll show you how to buy apps through the Microsoft S
|
||||
|
||||
**Figure 29** - App inventory shows the purchased apps
|
||||
|
||||

|
||||
:::image type="content" alt-text="Confirm that your inventory shows purchased apps." source="images/wsfb_manage_inventory_newapps.png":::
|
||||
|
||||
> [!NOTE]
|
||||
> Sync happens automatically, but it may take up to 24 hours for your organization's private store and 12 hours for Intune to sync all your purchased apps. You can force a sync to make this process happen faster. For more info, see [To sync recently purchased apps](#forceappsync).
|
||||
@ -369,18 +370,18 @@ In the following example, we'll show you how to buy apps through the Microsoft S
|
||||
|
||||
If you need to sync your most recently purchased apps and have it appear in your catalog, you can do this by forcing a sync.
|
||||
|
||||
1. In the <a href="https://manage.microsoft.com/" target="_blank">Intune management portal</a>, select **Admin > Mobile Device Management > Windows > Store for Business**.
|
||||
1. In the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Admin > Mobile Device Management > Windows > Store for Business**.
|
||||
2. In the **Microsoft Store for Business** page, click **Sync now** to force a sync.
|
||||
|
||||
**Figure 30** - Force a sync in Intune
|
||||
|
||||

|
||||
:::image type="content" alt-text="Force a sync in Intune." source="images/intune_admin_mdm_forcesync.png":::
|
||||
|
||||
**To view purchased apps**
|
||||
- In the <a href="https://manage.microsoft.com/" target="_blank">Intune management portal</a>, select **Apps > Apps** and then choose **Volume-Purchased Apps** to see the list of available apps. Verify that the apps you purchased were imported correctly.
|
||||
- In the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Apps > Apps** and then choose **Volume-Purchased Apps** to see the list of available apps. Verify that the apps you purchased were imported correctly.
|
||||
|
||||
**To add more apps**
|
||||
- If you have other apps that you want to deploy or manage, you must add it to Microsoft Intune. To deploy Win32 apps and Web links, see <a href="/intune/deploy-use/add-apps-for-mobile-devices-in-microsoft-intune" target="_blank">Add apps for enrolled devices to Intune</a> for more info on how to do this.
|
||||
- If you have other apps that you want to deploy or manage, you must add it to Microsoft Intune. To deploy Win32 apps and Web links, see [Add apps to Microsoft Intune](/mem/intune/apps/apps-add) for more info on how to do this.
|
||||
|
||||
## 2. Set up devices
|
||||
|
||||
@ -395,7 +396,7 @@ To set up new Windows devices, go through the Windows initial device setup or fi
|
||||
|
||||
**Figure 31** - First screen in Windows device setup
|
||||
|
||||

|
||||
:::image type="content" alt-text="First screen in Windows device setup." source="images/win10_hithere.png":::
|
||||
|
||||
> [!NOTE]
|
||||
> During setup, if you don't have a Wi-Fi network configured, make sure you connect the device to the Internet through a wired/Ethernet connection.
|
||||
@ -405,13 +406,13 @@ To set up new Windows devices, go through the Windows initial device setup or fi
|
||||
|
||||
**Figure 32** - Choose how you'll connect your Windows device
|
||||
|
||||

|
||||
:::image type="content" alt-text="Choose how you'll connect the Windows device." source="images/win10_choosehowtoconnect.png":::
|
||||
|
||||
4. In the **Let's get you signed in** screen, sign in using a user account you added in section [1.2 Add users and assign product licenses](#12-add-users-and-assign-product-licenses). We suggest signing in as one of the global administrators. Later, sign in on another device using one of the non-admin accounts.
|
||||
|
||||
**Figure 33** - Sign in using one of the accounts you added
|
||||
|
||||

|
||||
:::image type="content" alt-text="Sign in using one of the accounts you added." source="images/win10_signin_admin_account.png":::
|
||||
|
||||
5. If this is the first time you're signing in, you will be asked to update your password. Update the password and continue with sign-in and setup.
|
||||
|
||||
@ -425,16 +426,16 @@ Verify that the device is set up correctly and boots without any issues.
|
||||
2. Confirm that the Store and built-in apps are working.
|
||||
|
||||
### 2.3 Verify the device is Azure AD joined
|
||||
In the <a href="https://manage.microsoft.com/" target="_blank">Intune management portal</a>, verify that the device is joined to Azure AD and shows up as being managed in Microsoft Intune.
|
||||
In the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), verify that the device is joined to Azure AD and shows up as being managed in Microsoft Intune.
|
||||
|
||||
**To verify if the device is joined to Azure AD**
|
||||
1. Check the device name on your PC. On your Windows PC, select **Settings > System > About** and then check **PC name**.
|
||||
|
||||
**Figure 34** - Check the PC name on your device
|
||||
|
||||

|
||||
:::image type="content" alt-text="Check the PC name on your device." source="images/win10_settings_pcname.png":::
|
||||
|
||||
2. Log in to the <a href="https://manage.microsoft.com/" target="_blank">Intune management portal</a>.
|
||||
2. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
3. Select **Groups** and then go to **Devices**.
|
||||
4. In the **All Devices** page, look at the list of devices and select the entry that matches the name of your PC.
|
||||
- Check that the device name appears in the list. Select the device and it will also show the current logged-in user in the **General Information** section.
|
||||
@ -443,7 +444,7 @@ In the <a href="https://manage.microsoft.com/" target="_blank">Intune management
|
||||
|
||||
**Figure 35** - Check that the device appears in Intune
|
||||
|
||||

|
||||
:::image type="content" alt-text="Check that the device appears in Intune." source="images/intune_groups_devices_list.png":::
|
||||
|
||||
## 3. Manage device settings and features
|
||||
You can use Microsoft Intune admin settings and policies to manage features on your organization's mobile devices and computers. For more info, see [Manage settings and features on your devices with Microsoft Intune policies](/intune/deploy-use/manage-settings-and-features-on-your-devices-with-microsoft-intune-policies).
|
||||
@ -454,7 +455,7 @@ In this section, we'll show you how to reconfigure app deployment settings and a
|
||||
In some cases, if an app is missing from the device, you need to reconfigure the deployment settings for the app and set the app to require installation as soon as possible.
|
||||
|
||||
**To reconfigure app deployment settings**
|
||||
1. In the <a href="https://manage.microsoft.com/" target="_blank">Intune management portal</a>, select **Apps** and go to **Apps > Volume-Purchased Apps**.
|
||||
1. In the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Apps** and go to **Apps > Volume-Purchased Apps**.
|
||||
2. Select the app, right-click, then select **Manage Deployment...**.
|
||||
3. Select the group(s) whose apps will be managed, and then click **Add** to add the group.
|
||||
4. Click **Next** at the bottom of the app deployment settings window or select **Deployment Action** on the left column to check the deployment settings for the app.
|
||||
@ -462,7 +463,7 @@ In some cases, if an app is missing from the device, you need to reconfigure the
|
||||
|
||||
**Figure 36** - Reconfigure an app's deployment setting in Intune
|
||||
|
||||

|
||||
:::image type="content" alt-text="Reconfigure app deployment settings in Intune." source="images/intune_apps_deploymentaction.png":::
|
||||
|
||||
6. Click **Finish**.
|
||||
7. Repeat steps 2-6 for other apps that you want to deploy to the device(s) as soon as possible.
|
||||
@ -472,12 +473,12 @@ In some cases, if an app is missing from the device, you need to reconfigure the
|
||||
|
||||
**Figure 37** - Confirm that additional apps were deployed to the device
|
||||
|
||||

|
||||
:::image type="content" alt-text="Confirm that additional apps were deployed to the device." source="images/win10_deploy_apps_immediately.png":::
|
||||
|
||||
### 3.2 Configure other settings in Intune
|
||||
|
||||
**To disable the camera**
|
||||
1. In the <a href="https://manage.microsoft.com/" target="_blank">Intune management portal</a>, select **Policy > Configuration Policies**.
|
||||
1. In the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices > Configuration Policies**.
|
||||
2. In the **Policies** window, click **Add** to create a new policy.
|
||||
3. On the **Create a New Policy** page, click **Windows** to expand the group, select **General Configuration (Windows 10 Desktop and Mobile and later)**, choose **Create and Deploy a Custom Policy**, and then click **Create Policy**.
|
||||
4. On the **Create Policy** page, select **Device Capabilities**.
|
||||
@ -488,7 +489,7 @@ In some cases, if an app is missing from the device, you need to reconfigure the
|
||||
|
||||
**Figure 38** - Add a configuration policy
|
||||
|
||||

|
||||
:::image type="content" alt-text="Add a configuration policy." source="images/intune_policy_disablecamera.png":::
|
||||
|
||||
7. Click **Save Policy**. A confirmation window will pop up.
|
||||
8. On the **Deploy Policy** confirmation window, select **Yes** to deploy the policy now.
|
||||
@ -497,16 +498,16 @@ In some cases, if an app is missing from the device, you need to reconfigure the
|
||||
|
||||
**Figure 39** - The new policy should appear in the **Policies** list.
|
||||
|
||||

|
||||
:::image type="content" alt-text="New policy appears on the list." source="images/intune_policies_newpolicy_deployed.png":::
|
||||
|
||||
**To turn off Windows Hello and PINs during device setup**
|
||||
1. In the <a href="https://manage.microsoft.com/" target="_blank">Intune management portal</a>, select **Admin**.
|
||||
1. Go to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
2. Go to **Mobile Device Management > Windows > Windows Hello for Business**.
|
||||
3. In the **Windows Hello for Business** page, select **Disable Windows Hello for Business on enrolled devices**.
|
||||
|
||||
**Figure 40** - Policy to disable Windows Hello for Business
|
||||
|
||||

|
||||
:::image type="content" alt-text="Disable Windows Hello for Business." source="images/intune_policy_disable_windowshello.png":::
|
||||
|
||||
4. Click **Save**.
|
||||
|
||||
@ -533,49 +534,49 @@ For other devices, such as those personally-owned by employees who need to conne
|
||||
|
||||
**Figure 41** - Add an Azure AD account to the device
|
||||
|
||||

|
||||
:::image type="content" alt-text="Add an Azure AD account to the device." source="images/win10_add_new_user_join_aad.png":::
|
||||
|
||||
4. In the **Let's get you signed in** window, enter the work credentials for the account and then click **Sign in** to authenticate the user.
|
||||
|
||||
**Figure 42** - Enter the account details
|
||||
|
||||

|
||||
:::image type="content" alt-text="Enter the account details." source="images/win10_add_new_user_account_aadwork.png":::
|
||||
|
||||
5. You will be asked to update the password so enter a new password.
|
||||
6. Verify the details to make sure you're connecting to the right organization and then click **Join**.
|
||||
|
||||
**Figure 43** - Make sure this is your organization
|
||||
|
||||

|
||||
:::image type="content" alt-text="Make sure this is your organization." source="images/win10_confirm_organization_details.png":::
|
||||
|
||||
7. You will see a confirmation window that says the device is now connected to your organization. Click **Done**.
|
||||
|
||||
**Figure 44** - Confirmation that the device is now connected
|
||||
|
||||

|
||||
:::image type="content" alt-text="Confirmation that the device is now connected." source="images/win10_confirm_device_connected_to_org.png":::
|
||||
|
||||
8. The **Connect to work or school** window will refresh and will now include an entry that shows you're connected to your organization's Azure AD. This means the device is now registered in Azure AD and enrolled in MDM and the account should have access to the organization's resources.
|
||||
|
||||
**Figure 45** - Device is now enrolled in Azure AD
|
||||
|
||||

|
||||
:::image type="content" alt-text="Device is enrolled in Azure AD." source="images/win10_device_enrolled_in_aad.png":::
|
||||
|
||||
9. You can confirm that the new device and user are showing up as Intune-managed by going to the <a href="https://manage.microsoft.com/" target="_blank">Intune management portal</a> and following the steps in [2.3 Verify the device is Azure AD joined](#23-verify-the-device-is-azure-ad-joined). It may take several minutes before the new device shows up so check again later.
|
||||
9. You can confirm that the new device and user are showing up as Intune-managed by going to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) and following the steps in [2.3 Verify the device is Azure AD joined](#23-verify-the-device-is-azure-ad-joined). It may take several minutes before the new device shows up so check again later.
|
||||
|
||||
### 4.2 Add a new user
|
||||
You can add new users to your tenant simply by adding them to the Microsoft 365 groups. Adding new users to Microsoft 365 groups automatically adds them to the corresponding groups in Microsoft Intune.
|
||||
|
||||
See [Add users to Office 365](/microsoft-365/admin/add-users/add-users) to learn more. Once you're done adding new users, go to the <a href="https://manage.microsoft.com/" target="_blank">Intune management portal</a> and verify that the same users were added to the Intune groups as well.
|
||||
See [Add users to Office 365](/microsoft-365/admin/add-users/add-users) to learn more. Once you're done adding new users, go to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) and verify that the same users were added to the Intune groups as well.
|
||||
|
||||
## Get more info
|
||||
|
||||
### For IT admins
|
||||
To learn more about the services and tools mentioned in this walkthrough, and learn what other tasks you can do, follow these links:
|
||||
- <a href="https://support.office.com/article/Set-up-Office-365-for-business-6a3a29a0-e616-4713-99d1-15eda62d04fa" target="_blank">Set up Office 365 for business</a>
|
||||
- Common admin tasks in Office 365 including email and OneDrive in <a href="https://support.office.com/article/Common-management-tasks-for-Office-365-46c667f7-5073-47b9-a75f-05a60cf77d91" target="_blank">Manage Office 365</a>
|
||||
- More info about managing devices, apps, data, troubleshooting, and more in <a href="/intune/" target="_blank">Intune documentation</a>
|
||||
- [Set up Office 365 for business](/microsoft-365/admin/setup)
|
||||
- Common admin tasks in Office 365 including email and OneDrive in [Manage Office 365](/microsoft-365/admin/)
|
||||
- More info about managing devices, apps, data, troubleshooting, and more in the [/mem/intune/](/mem/intune/)
|
||||
- Learn more about Windows client in the [Windows client documentation for IT Pros](/windows/resources/).
|
||||
- Info about distributing apps to your employees, managing apps, managing settings, and more in <a href="/microsoft-store/" target="_blank">Microsoft Store for Business</a>
|
||||
- Info about distributing apps to your employees, managing apps, managing settings, and more in [Microsoft Store for Business](/microsoft-store/)
|
||||
|
||||
### For information workers
|
||||
Whether it's in the classroom, getting the most out of your devices, or learning some of the cool things you can do, we've got teachers covered. Follow these links for more info:
|
||||
|
@ -44,5 +44,5 @@ If you created a new Azure AD directory when you signed up for Store for Busines
|
||||
You can use the [Office 365 admin dashboard](https://portal.office.com/adminportal) or [Azure management portal](https://go.microsoft.com/fwlink/p/?LinkId=691086) to add user accounts to your Azure AD directory. If you'll be using Azure management portal, you'll need an active subscription to [Azure management portal](https://go.microsoft.com/fwlink/p/?LinkId=708617).
|
||||
|
||||
For more information, see:
|
||||
- [Add user accounts using Office 365 admin dashboard](https://support.office.com/en-us/article/add-users-individually-or-in-bulk-to-office-365-admin-help-1970f7d6-03b5-442f-b385-5880b9c256ec)
|
||||
- [Add user accounts using Office 365 admin dashboard](/microsoft-365/admin/add-users)
|
||||
- [Add user accounts using Azure management portal](/azure/active-directory/fundamentals/add-users-azure-active-directory)
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Whats new in Microsoft Store for Business and Education
|
||||
description: Learn about newest features in Microsoft Store for Business and Microsoft Store for Education.
|
||||
title: Microsoft Store for Business and Education release history
|
||||
description: Know the release history of Microsoft Store for Business and Microsoft Store for Education.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
|
@ -76,6 +76,7 @@ ms.localizationpriority: medium
|
||||
| --- | --- |
|
||||
| [Microsoft Store for Business and Education PowerShell module - preview](microsoft-store-for-business-education-powershell-module.md) | New |
|
||||
| [Microsoft Store for Business and Education overview - supported markets](./microsoft-store-for-business-overview.md#supported-markets) | Updates for added market support. |
|
||||
| [Manage Windows device deployment with Windows Autopilot Deployment](add-profile-to-devices.md) | New. Information about Windows Autopilot Deployment Program and how it is used in Microsoft Store for Business and Education. |
|
||||
|
||||
## June 2017
|
||||
|
||||
@ -84,10 +85,3 @@ ms.localizationpriority: medium
|
||||
| [Notifications in Microsoft Store for Business and Education](notifications-microsoft-store-business.md) | New. Information about notification model in Microsoft Store for Business and Education. |
|
||||
| [Get Minecraft: Education Edition with Windows 10 device promotion](/education/windows/get-minecraft-device-promotion) | New. Information about redeeming Minecraft: Education Edition licenses with qualifying purchases of Windows 10 devices. |
|
||||
| [Microsoft Store for Business and Education overview - supported markets](./microsoft-store-for-business-overview.md#supported-markets) | Updates for added market support. |
|
||||
|
||||
## July 2017
|
||||
|
||||
| New or changed topic | Description |
|
||||
| -------------------- | ----------- |
|
||||
| [Manage Windows device deployment with Windows Autopilot Deployment](add-profile-to-devices.md) | New. Information about Windows Autopilot Deployment Program and how it is used in Microsoft Store for Business and Education. |
|
||||
| [Microsoft Store for Business and Education overview - supported markets](./microsoft-store-for-business-overview.md#supported-markets) | Updates for added market support. |
|
@ -56,7 +56,7 @@ The private store for your organization is a page in Microsoft Store app that co
|
||||
|
||||
## Troubleshooting Microsoft Store for Business integration with Microsoft Endpoint Configuration Manager
|
||||
|
||||
If you encounter any problems when integrating Microsoft Store for Business with Configuration Manager, use the [troubleshooting guide](https://support.microsoft.com/help/4010214/understand-and-troubleshoot-microsoft-store-for-business-integration-w).
|
||||
If you encounter any problems when integrating Microsoft Store for Business with Configuration Manager, use the [troubleshooting guide](/troubleshoot/mem/configmgr/troubleshoot-microsoft-store-for-business-integration).
|
||||
|
||||
## Still having trouble?
|
||||
|
||||
|
@ -63,7 +63,7 @@ The computer on which you are installing the Office Deployment Tool must have th
|
||||
|
||||
| Prerequisite | Description |
|
||||
|----------------------|--------------------|
|
||||
| Prerequisite software | .Net Framework 4 |
|
||||
| Prerequisite software | .NET Framework 4 |
|
||||
| Supported operating systems | 64-bit version of Windows 10/11<br>64-bit version of Windows 8 or 8.1<br>64-bit version of Windows 7 |
|
||||
|
||||
>[!NOTE]
|
||||
@ -120,7 +120,7 @@ The XML file included in the Office Deployment Tool specifies the product detail
|
||||
|--------------|----------------------------|----------------|
|
||||
| Add element | Specifies which products and languages the package will include. | N/A |
|
||||
| **OfficeClientEdition** (attribute of **Add** element) | Specifies whether Office 2016 32-bit or 64-bit edition will be used. **OfficeClientEdition** must be set to a valid value for the operation to succeed. | `OfficeClientEdition="32"`<br>`OfficeClientEdition="64"` |
|
||||
| Product element | Specifies the application. Project 2016 and Visio 2016 must be specified here as added products to include them in the applications.<br>For more information about Product IDs, see [Product IDs that are supported by the Office Deployment Tool for Click-to-Run](https://support.microsoft.com/kb/2842297). | `Product ID ="O365ProPlusRetail"`<br>`Product ID ="VisioProRetail"`<br>`Product ID ="ProjectProRetail"` |
|
||||
| Product element | Specifies the application. Project 2016 and Visio 2016 must be specified here as added products to include them in the applications.<br>For more information about Product IDs, see [Product IDs that are supported by the Office Deployment Tool for Click-to-Run](/office365/troubleshoot/installation). | `Product ID ="O365ProPlusRetail"`<br>`Product ID ="VisioProRetail"`<br>`Product ID ="ProjectProRetail"` |
|
||||
| Language element | Specifies which language the applications support. | `Language ID="en-us"` |
|
||||
| Version (attribute of **Add** element) | Optional. Specifies which build the package will use.<br>Defaults to latest advertised build (as defined in v32.CAB at the Office source). | `16.1.2.3` |
|
||||
| SourcePath (attribute of **Add** element) | Specifies the location the applications will be saved to. | `Sourcepath = "\\Server\Office2016"` |
|
||||
|
@ -19,90 +19,81 @@ ms.author: greglin
|
||||
|
||||
The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10 version 1703 and later
|
||||
|
||||
<table border="1">
|
||||
<thead>
|
||||
<th>Problem</th>
|
||||
<th>Workaround</th>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>Unable to manually create a system-owned folder needed for the <code>set-AppVClientConfiguration</code> PowerShell cmdlet when using the <i>PackageInstallationRoot</i>, <i>IntegrationRootUser</i>, or <i>IntegrationRootGlobal</i> parameters.</td>
|
||||
<td>Don't create this file manually, instead let the <code>Add-AppVClientPackage</code> cmdlet auto-generate it.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Failure to update an App-V package from App-V 5.x to the latest in-box version, by using the PowerShell sequencing commands.</td>
|
||||
<td>Make sure you have the complete App-V package or the MSI file from the original app.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Unable to modify the locale for auto-sequencing.</td>
|
||||
<td>Open the <code>C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\AutoSequencer\Unattend_Sequencer_User_Setup_Template.xml</code> file and include the language code for your locale. For example, if you wanted Spanish (Spain), you'd use: <strong>es-ES</strong>.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Filetype and protocol handlers aren't registering properly with the Google Chrome browser, causing you to not see App-V packages as an option for default apps from the <strong>Settings > Apps> Default Apps</strong> area.</td>
|
||||
<td>The recommended workaround is to add the following code to the AppXManifest.xml file, underneath the <strong><appv:Extensions></strong> tag:
|
||||
<pre><code>
|
||||
<appv:Extension Category="AppV.URLProtocol">
|
||||
<appv:URLProtocol>
|
||||
<appv:Name>ftp</appv:Name>
|
||||
<appv:ApplicationURLProtocol>
|
||||
<appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
|
||||
<appv:ShellCommands>
|
||||
<appv:DefaultCommand>open</appv:DefaultCommand>
|
||||
<appv:ShellCommand>
|
||||
<appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
|
||||
<appv:Name>open</appv:Name>
|
||||
<appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
|
||||
<appv:DdeExec>
|
||||
<appv:DdeCommand />
|
||||
</appv:DdeExec>
|
||||
</appv:ShellCommand>
|
||||
</appv:ShellCommands>
|
||||
</appv:ApplicationURLProtocol>
|
||||
</appv:URLProtocol>
|
||||
</appv:Extension>
|
||||
<appv:Extension Category="AppV.URLProtocol">
|
||||
<appv:URLProtocol>
|
||||
<appv:Name>http</appv:Name>
|
||||
<appv:ApplicationURLProtocol>
|
||||
<appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
|
||||
<appv:ShellCommands>
|
||||
<appv:DefaultCommand>open</appv:DefaultCommand>
|
||||
<appv:ShellCommand>
|
||||
<appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
|
||||
<appv:Name>open</appv:Name>
|
||||
<appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
|
||||
<appv:DdeExec>
|
||||
<appv:DdeCommand />
|
||||
</appv:DdeExec>
|
||||
</appv:ShellCommand>
|
||||
</appv:ShellCommands>
|
||||
</appv:ApplicationURLProtocol>
|
||||
</appv:URLProtocol>
|
||||
</appv:Extension>
|
||||
<appv:Extension Category="AppV.URLProtocol">
|
||||
<appv:URLProtocol>
|
||||
<appv:Name>https</appv:Name>
|
||||
<appv:ApplicationURLProtocol>
|
||||
<appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
|
||||
<appv:ShellCommands>
|
||||
<appv:DefaultCommand>open</appv:DefaultCommand>
|
||||
<appv:ShellCommand>
|
||||
<appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
|
||||
<appv:Name>open</appv:Name>
|
||||
<appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
|
||||
<appv:DdeExec>
|
||||
<appv:DdeCommand />
|
||||
</appv:DdeExec>
|
||||
</appv:ShellCommand>
|
||||
</appv:ShellCommands>
|
||||
</appv:ApplicationURLProtocol>
|
||||
</appv:URLProtocol>
|
||||
</appv:Extension>
|
||||
</code></pre><br/> </td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
- **Problem**: Unable to manually create a system-owned folder needed for the `set-AppVClientConfiguration` PowerShell cmdlet when using the PackageInstallationRoot, IntegrationRootUser, or IntegrationRootGlobal parameters.
|
||||
|
||||
**Workaround**: Don't create this file manually, instead let the `Add-AppVClientPackage` cmdlet auto-generate it.
|
||||
|
||||
- **Problem**: Failure to update an App-V package from App-V 5.x to the latest in-box version, by using the PowerShell sequencing commands.
|
||||
|
||||
**Workaround**: Make sure you have the complete App-V package or the MSI file from the original app.
|
||||
|
||||
- **Problem**: Unable to modify the locale for auto-sequencing.
|
||||
|
||||
**Workaround**: Open the `C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\AutoSequencer\Unattend_Sequencer_User_Setup_Template.xml` file and include the language code for your locale. For example, if you wanted Spanish (Spain), you'd use: es-ES.
|
||||
|
||||
- **Problem**: Filetype and protocol handlers aren't registering properly with the Google Chrome browser, causing you to not see App-V packages as an option for default apps from the Settings > Apps> Default Apps area.
|
||||
|
||||
**Workaround**: The recommended workaround is to add the following code to the AppXManifest.xml file, underneath the `<appv:Extensions>` tag:
|
||||
|
||||
```xml
|
||||
<appv:Extension Category="AppV.URLProtocol">
|
||||
<appv:URLProtocol>
|
||||
<appv:Name>ftp</appv:Name>
|
||||
<appv:ApplicationURLProtocol>
|
||||
<appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
|
||||
<appv:ShellCommands>
|
||||
<appv:DefaultCommand>open</appv:DefaultCommand>
|
||||
<appv:ShellCommand>
|
||||
<appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
|
||||
<appv:Name>open</appv:Name>
|
||||
<appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
|
||||
<appv:DdeExec>
|
||||
<appv:DdeCommand />
|
||||
</appv:DdeExec>
|
||||
</appv:ShellCommand>
|
||||
</appv:ShellCommands>
|
||||
</appv:ApplicationURLProtocol>
|
||||
</appv:URLProtocol>
|
||||
</appv:Extension>
|
||||
<appv:Extension Category="AppV.URLProtocol">
|
||||
<appv:URLProtocol>
|
||||
<appv:Name>http</appv:Name>
|
||||
<appv:ApplicationURLProtocol>
|
||||
<appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
|
||||
<appv:ShellCommands>
|
||||
<appv:DefaultCommand>open</appv:DefaultCommand>
|
||||
<appv:ShellCommand>
|
||||
<appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
|
||||
<appv:Name>open</appv:Name>
|
||||
<appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
|
||||
<appv:DdeExec>
|
||||
<appv:DdeCommand />
|
||||
</appv:DdeExec>
|
||||
</appv:ShellCommand>
|
||||
</appv:ShellCommands>
|
||||
</appv:ApplicationURLProtocol>
|
||||
</appv:URLProtocol>
|
||||
</appv:Extension>
|
||||
<appv:Extension Category="AppV.URLProtocol">
|
||||
<appv:URLProtocol>
|
||||
<appv:Name>https</appv:Name>
|
||||
<appv:ApplicationURLProtocol>
|
||||
<appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
|
||||
<appv:ShellCommands>
|
||||
<appv:DefaultCommand>open</appv:DefaultCommand>
|
||||
<appv:ShellCommand>
|
||||
<appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
|
||||
<appv:Name>open</appv:Name>
|
||||
<appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
|
||||
<appv:DdeExec>
|
||||
<appv:DdeCommand />
|
||||
</appv:DdeExec>
|
||||
</appv:ShellCommand>
|
||||
</appv:ShellCommands>
|
||||
</appv:ApplicationURLProtocol>
|
||||
</appv:URLProtocol>
|
||||
</appv:Extension>
|
||||
```
|
||||
|
||||
## Related resources list
|
||||
For information that can help with troubleshooting App-V for Windows client, see:
|
||||
|
@ -231,7 +231,7 @@ If Windows cannot load the system registry hive into memory, you must restore th
|
||||
If the problem persists, you may want to restore the system state backup to an alternative location, and then retrieve the registry hives to be replaced.
|
||||
|
||||
> [!NOTE]
|
||||
> Starting in Windows 10, version 1803, Windows no longer automatically backs up the system registry to the RegBack folder.This change is by design, and is intended to help reduce the overall disk footprint size of Windows. To recover a system with a corrupt registry hive, Microsoft recommends that you use a system restore point. For more details, check [this article](https://support.microsoft.com/en-us/help/4509719/the-system-registry-is-no-longer-backed-up-to-the-regback-folder-start).
|
||||
> Starting in Windows 10, version 1803, Windows no longer automatically backs up the system registry to the RegBack folder.This change is by design, and is intended to help reduce the overall disk footprint size of Windows. To recover a system with a corrupt registry hive, Microsoft recommends that you use a system restore point. For more details, check [this article](/troubleshoot/windows-client/deployment/system-registry-no-backed-up-regback-folder)
|
||||
|
||||
## Kernel Phase
|
||||
|
||||
@ -414,4 +414,4 @@ If the dump file shows an error that is related to a driver (for example, window
|
||||
5. Copy all the hives from the Regback folder, paste them in the Config folder, and then try to start the computer in Normal mode.
|
||||
|
||||
> [!NOTE]
|
||||
> Starting in Windows 10, version 1803, Windows no longer automatically backs up the system registry to the RegBack folder.This change is by design, and is intended to help reduce the overall disk footprint size of Windows. To recover a system with a corrupt registry hive, Microsoft recommends that you use a system restore point. For more details, check [this article](https://support.microsoft.com/en-us/help/4509719/the-system-registry-is-no-longer-backed-up-to-the-regback-folder-start).
|
||||
> Starting in Windows 10, version 1803, Windows no longer automatically backs up the system registry to the RegBack folder.This change is by design, and is intended to help reduce the overall disk footprint size of Windows. To recover a system with a corrupt registry hive, Microsoft recommends that you use a system restore point. For more details, check [this article](/troubleshoot/windows-client/deployment/system-registry-no-backed-up-regback-folder).
|
||||
|
@ -37,9 +37,8 @@ It is important to understand the different Wi-Fi components involved, their exp
|
||||
The intention of this troubleshooter is to show how to find a starting point in the verbosity of wireless_dbg ETW and home in on the responsible components that are causing the connection problem.
|
||||
|
||||
### Known Issues and fixes
|
||||
** **
|
||||
|
||||
| **OS version** | **Fixed in** |
|
||||
| OS version | Fixed in |
|
||||
| --- | --- |
|
||||
| **Windows 10, version 1803** | [KB4284848](https://support.microsoft.com/help/4284848) |
|
||||
| **Windows 10, version 1709** | [KB4284822](https://support.microsoft.com/help/4284822) |
|
||||
@ -54,13 +53,13 @@ Make sure that you install the latest Windows updates, cumulative updates, and r
|
||||
- [Windows 10 version 1511](https://support.microsoft.com/help/4000824)
|
||||
- [Windows 8.1 and Windows Server 2012 R2](https://support.microsoft.com/help/4009470)
|
||||
- [Windows Server 2012](https://support.microsoft.com/help/4009471)
|
||||
- [Windows 7 SP1 and Windows Server 2008 R2 SP1](https://support.microsoft.com/help/40009469)
|
||||
- [Windows 7 SP1 and Windows Server 2008 R2 SP1](https://support.microsoft.com/help/4009469)
|
||||
|
||||
## Data Collection
|
||||
|
||||
1. Network Capture with ETW. Enter the following at an elevated command prompt:
|
||||
|
||||
```cmd
|
||||
```console
|
||||
netsh trace start wireless_dbg capture=yes overwrite=yes maxsize=4096 tracefile=c:\tmp\wireless.etl
|
||||
```
|
||||
2. Reproduce the issue.
|
||||
@ -70,12 +69,12 @@ Make sure that you install the latest Windows updates, cumulative updates, and r
|
||||
- If intermittent connection drops trigger stop command on a script (ping or test network constantly until fail, then netsh trace stop).
|
||||
3. Stop the trace by entering the following command:
|
||||
|
||||
```cmd
|
||||
```console
|
||||
netsh trace stop
|
||||
```
|
||||
4. To convert the output file to text format:
|
||||
|
||||
```cmd
|
||||
```console
|
||||
netsh trace convert c:\tmp\wireless.etl
|
||||
```
|
||||
|
||||
@ -105,39 +104,39 @@ The wifi connection state machine has the following states:
|
||||
|
||||
Standard wifi connections tend to transition between states such as:
|
||||
|
||||
**Connecting**
|
||||
- Connecting
|
||||
|
||||
Reset --> Ihv_Configuring --> Configuring --> Associating --> Authenticating --> Connected
|
||||
Reset --> Ihv_Configuring --> Configuring --> Associating --> Authenticating --> Connected
|
||||
|
||||
**Disconnecting**
|
||||
- Disconnecting
|
||||
|
||||
Connected --> Roaming --> Wait_For_Disconnected --> Disconnected --> Reset
|
||||
Connected --> Roaming --> Wait_For_Disconnected --> Disconnected --> Reset
|
||||
|
||||
>Filtering the ETW trace with the [TextAnalysisTool](https://github.com/TextAnalysisTool/Releases) (TAT) is an easy first step to determine where a failed connection setup is breaking down. A useful [wifi filter file](#wifi-filter-file) is included at the bottom of this article.
|
||||
Filtering the ETW trace with the [TextAnalysisTool](https://github.com/TextAnalysisTool/Releases) (TAT) is an easy first step to determine where a failed connection setup is breaking down. A useful [wifi filter file](#wifi-filter-file) is included at the bottom of this article.
|
||||
|
||||
Use the **FSM transition** trace filter to see the connection state machine. You can see [an example](#textanalysistool-example) of this filter applied in the TAT at the bottom of this page.
|
||||
|
||||
The following is an example of a good connection setup:
|
||||
|
||||
<pre>
|
||||
```console
|
||||
44676 [2]0F24.1020::2018-09-17 10:22:14.658 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Disconnected to State: Reset
|
||||
45473 [1]0F24.1020::2018-09-17 10:22:14.667 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Reset to State: Ihv_Configuring
|
||||
45597 [3]0F24.1020::2018-09-17 10:22:14.708 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Ihv_Configuring to State: Configuring
|
||||
46085 [2]0F24.17E0::2018-09-17 10:22:14.710 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Configuring to State: Associating
|
||||
47393 [1]0F24.1020::2018-09-17 10:22:14.879 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Associating to State: Authenticating
|
||||
49465 [2]0F24.17E0::2018-09-17 10:22:14.990 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Authenticating to State: Connected
|
||||
</pre>
|
||||
```
|
||||
|
||||
The following is an example of a failed connection setup:
|
||||
|
||||
<pre>
|
||||
```console
|
||||
44676 [2]0F24.1020::2018-09-17 10:22:14.658 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Disconnected to State: Reset
|
||||
45473 [1]0F24.1020::2018-09-17 10:22:14.667 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Reset to State: Ihv_Configuring
|
||||
45597 [3]0F24.1020::2018-09-17 10:22:14.708 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Ihv_Configuring to State: Configuring
|
||||
46085 [2]0F24.17E0::2018-09-17 10:22:14.710 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Configuring to State: Associating
|
||||
47393 [1]0F24.1020::2018-09-17 10:22:14.879 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Associating to State: Authenticating
|
||||
49465 [2]0F24.17E0::2018-09-17 10:22:14.990 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Authenticating to State: Roaming
|
||||
</pre>
|
||||
```
|
||||
|
||||
By identifying the state at which the connection fails, one can focus more specifically in the trace on logs just prior to the last known good state.
|
||||
|
||||
@ -155,7 +154,7 @@ Enable the **FSM transition, SecMgr Transition,** and **AuthMgr Transition** fil
|
||||
|
||||
Continuing with the example above, the combined filters look like this:
|
||||
|
||||
<pre>
|
||||
```console
|
||||
[2] 0C34.2FF0::08/28/17-13:24:28.693 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State:
|
||||
Reset to State: Ihv_Configuring
|
||||
[2] 0C34.2FF0::08/28/17-13:24:28.693 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State:
|
||||
@ -173,7 +172,7 @@ Associating to State: Authenticating
|
||||
[2] 0C34.2FF0::08/28/17-13:24:29.7512788 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition DEACTIVATE (11) --> INACTIVE (1)
|
||||
[2] 0C34.2FF0::08/28/17-13:24:29.7513404 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State:
|
||||
Authenticating to State: Roaming
|
||||
</pre>
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
> In the next to last line the SecMgr transition is suddenly deactivating:<br>
|
||||
@ -182,7 +181,7 @@ Authenticating to State: Roaming
|
||||
|
||||
Enabling the **Microsoft-Windows-WLAN-AutoConfig** filter will show more detail leading to the DEACTIVATE transition:
|
||||
|
||||
<pre>
|
||||
```console
|
||||
[3] 0C34.2FE8::08/28/17-13:24:28.902 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State:
|
||||
Associating to State: Authenticating
|
||||
[1] 0C34.275C::08/28/17-13:24:28.960 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition START AUTH (3) --> WAIT FOR AUTH SUCCESS (4)
|
||||
@ -196,7 +195,7 @@ Associating to State: Authenticating
|
||||
[2] 0C34.2FF0::08/28/17-13:24:29.7512788 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition DEACTIVATE (11) --> INACTIVE (1)
|
||||
[2] 0C34.2FF0::08/28/17-13:24:29.7513404 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State:
|
||||
Authenticating to State: Roaming
|
||||
</pre>
|
||||
```
|
||||
|
||||
The trail backwards reveals a **Port Down** notification:
|
||||
|
||||
@ -208,7 +207,7 @@ Below, the MSM is the native wifi stack. These are Windows native wifi drivers w
|
||||
|
||||
Enable trace filter for **[Microsoft-Windows-NWifi]:**
|
||||
|
||||
<pre>
|
||||
```console
|
||||
[3] 0C34.2FE8::08/28/17-13:24:28.902 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State:
|
||||
Associating to State: Authenticating
|
||||
[1] 0C34.275C::08/28/17-13:24:28.960 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition START AUTH (3) --> WAIT FOR AUTH SUCCESS (4)
|
||||
@ -222,12 +221,14 @@ Associating to State: Authenticating
|
||||
[2] 0C34.2FF0::08/28/17-13:24:29.751 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition WAIT FOR AUTH SUCCESS (7) --> DEACTIVATE (11)
|
||||
[2] 0C34.2FF0::08/28/17-13:24:29.7512788 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition DEACTIVATE (11) --> INACTIVE (1)
|
||||
[2] 0C34.2FF0::08/28/17-13:24:29.7513404 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State:
|
||||
Authenticating to State: Roaming</pre>
|
||||
Authenticating to State: Roaming
|
||||
```
|
||||
|
||||
In the trace above, we see the line:
|
||||
|
||||
<pre>
|
||||
[0]0000.0000::08/28/17-13:24:29.127 [Microsoft-Windows-NWiFi]DisAssoc: 0x8A1514B62510 Reason: 0x4</pre>
|
||||
```console
|
||||
[0]0000.0000::08/28/17-13:24:29.127 [Microsoft-Windows-NWiFi]DisAssoc: 0x8A1514B62510 Reason: 0x4
|
||||
```
|
||||
|
||||
This is followed by **PHY_STATE_CHANGE** and **PORT_DOWN** events due to a disassociate coming from the Access Point (AP), as an indication to deny the connection. This could be due to invalid credentials, connection parameters, loss of signal/roaming, and various other reasons for aborting a connection. The action here would be to examine the reason for the disassociate sent from the indicated AP MAC (8A:15:14:B6:25:10). This would be done by examining internal logging/tracing from the AP.
|
||||
|
||||
@ -238,7 +239,7 @@ This is followed by **PHY_STATE_CHANGE** and **PORT_DOWN** events due to a disas
|
||||
|
||||
## Example ETW capture
|
||||
|
||||
<pre>
|
||||
```console
|
||||
C:\tmp>netsh trace start wireless_dbg capture=yes overwrite=yes maxsize=4096 tracefile=c:\tmp\wireless.etl
|
||||
|
||||
Trace configuration:
|
||||
@ -279,7 +280,7 @@ C:\tmp>dir
|
||||
01/09/2019 02:59 PM 2,786,540 wireless.txt
|
||||
3 File(s) 10,395,004 bytes
|
||||
2 Dir(s) 46,648,332,288 bytes free
|
||||
</pre>
|
||||
```
|
||||
|
||||
## Wifi filter file
|
||||
|
||||
|
@ -3,7 +3,7 @@ title: Windows 10 default media removal policy
|
||||
description: In Windows 10, version 1809, the default removal policy for external storage media changed from "Better performance" to "Quick removal."
|
||||
ms.prod: w10
|
||||
author: Teresa-Motiv
|
||||
ms.author: v-tea
|
||||
ms.author: dougeby
|
||||
ms.date: 11/25/2020
|
||||
ms.topic: article
|
||||
ms.custom:
|
||||
|
@ -73,7 +73,7 @@ Ensure [Remote Credential Guard](/windows/access-protection/remote-credential-gu
|
||||
> When you connect to the remote PC, enter your account name in this format: AzureAD\yourloginid@domain.com.
|
||||
|
||||
> [!NOTE]
|
||||
> If you cannot connect using Remote Desktop Connection 6.0, you must turn off the new features of RDP 6.0 and revert back to RDP 5.0 by making a few changes in the RDP file. See the details in this [support article](https://support.microsoft.com/help/941641/remote-desktop-connection-6-0-prompts-you-for-credentials-before-you-e).
|
||||
> If you cannot connect using Remote Desktop Connection 6.0, you must turn off the new features of RDP 6.0 and revert back to RDP 5.0 by making a few changes in the RDP file. See the details in this [support article](/troubleshoot/windows-server/remote/remote-desktop-connection-6-prompts-credentials).
|
||||
|
||||
## Supported configurations
|
||||
|
||||
|
@ -67,7 +67,7 @@ Kernel memory crash dumps require enough page file space or dedicated dump file
|
||||
|
||||
Computers that are running Microsoft Windows or Microsoft Windows Server usually must have a page file to support a system crash dump. System administrators now have the option to create a dedicated dump file instead.
|
||||
|
||||
A dedicated dump file is a page file that is not used for paging. Instead, it is “dedicated” to back a system crash dump file (Memory.dmp) when a system crash occurs. Dedicated dump files can be put on any disk volume that can support a page file. We recommend that you use a dedicated dump file if you want a system crash dump but you do not want a page file.
|
||||
A dedicated dump file is a page file that is not used for paging. Instead, it is “dedicated” to back a system crash dump file (Memory.dmp) when a system crash occurs. Dedicated dump files can be put on any disk volume that can support a page file. We recommend that you use a dedicated dump file if you want a system crash dump but you do not want a page file. To learn how to create it, see [Overview of memory dump file options for Windows](/troubleshoot/windows-server/performance/memory-dump-file-options).
|
||||
|
||||
## System-managed page files
|
||||
|
||||
|
@ -32,7 +32,7 @@ In Windows 10, version 1607, the following Group Policy settings apply only to W
|
||||
| **Do not show Windows Tips** | Computer Configuration > Administrative Templates > Windows Components > Cloud Content | For more info, see [Windows spotlight on the lock screen](/windows/configuration/windows-spotlight) |
|
||||
| **Force a specific default lock screen image** | Computer Configuration > Administrative Templates > Control Panel > Personalization | For more info, see [Windows spotlight on the lock screen](/windows/configuration/windows-spotlight) |
|
||||
| **Start layout** | User Configuration\Administrative Templates\Start Menu and Taskbar | In Windows 10, version 1703, this policy setting can be applied to Windows 10 Pro. For more info, see [Manage Windows 10 Start layout options and policies](/windows/configuration/windows-10-start-layout-options-and-policies) |
|
||||
| **Turn off the Store application** | Computer Configuration > Administrative Templates > Windows Components > Store > Turn off the Store application<br><br>User Configuration > Administrative Templates > Windows Components > Store > Turn off the Store application | For more info, see [Knowledge Base article# 3135657](https://support.microsoft.com/kb/3135657). |
|
||||
| **Turn off the Store application** | Computer Configuration > Administrative Templates > Windows Components > Store > Turn off the Store application<br><br>User Configuration > Administrative Templates > Windows Components > Store > Turn off the Store application | For more info, see [Knowledge Base article# 3135657](/troubleshoot/windows-client/group-policy/cannot-disable-microsoft-store). |
|
||||
| **Only display the private store within the Microsoft Store app** | Computer Configuration > Administrative Templates > Windows Components > Store > Only display the private store within the Microsoft Store app<br><br>User Configuration > Administrative Templates > Windows Components > Store > Only display the private store within the Microsoft Store app | For more info, see [Manage access to private store](/microsoft-store/manage-access-to-private-store) |
|
||||
| **Don't search the web or display web results** | Computer Configuration\Administrative Templates\Windows Components\Search\Don't search the web or display web results | For more info, see [Cortana integration in your enterprise](/windows/configuration/cortana-at-work/cortana-at-work-overview) |
|
||||
|
||||
|
@ -26,7 +26,7 @@ To make use of the Settings App group policies on Windows server 2016, install f
|
||||
>[!Note]
|
||||
>Each server that you want to manage access to the Settings App must be patched.
|
||||
|
||||
If your company uses one or the PolicyDefinitions folder of the Domain Controllers used for Group Policy management, to centrally manage the new policies, copy the ControlPanel.admx and ControlPanel.adml file to [Central Store](https://support.microsoft.com/help/3087759/how-to-create-and-manage-the-central-store-for-group-policy-administra).
|
||||
If your company uses one or the PolicyDefinitions folder of the Domain Controllers used for Group Policy management, to centrally manage the new policies, copy the ControlPanel.admx and ControlPanel.adml file to [Central Store](/troubleshoot/windows-client/group-policy/create-and-manage-central-store).
|
||||
|
||||
This policy is available for both User and Computer depending on the version of the OS. Windows Server 2016 with KB 4457127 applied will have both User and Computer policy. Windows 10, version 1703, added Computer policy for the Settings app. Windows 10, version 1809, added User policy for the Settings app.
|
||||
|
||||
|
@ -42,7 +42,7 @@ The name of the folder in which you store the mandatory profile must use the cor
|
||||
| Windows 10, versions 1507 and 1511 | N/A | v5 |
|
||||
| Windows 10, versions 1607, 1703, 1709, 1803, 1809, 1903 and 1909 | Windows Server 2016 and Windows Server 2019 | v6 |
|
||||
|
||||
For more information, see [Deploy Roaming User Profiles, Appendix B](/windows-server/storage/folder-redirection/deploy-roaming-user-profiles#appendix-b-profile-version-reference-information) and [Roaming user profiles versioning in Windows 10 and Windows Server Technical Preview](https://support.microsoft.com/kb/3056198).
|
||||
For more information, see [Deploy Roaming User Profiles, Appendix B](/windows-server/storage/folder-redirection/deploy-roaming-user-profiles#appendix-b-profile-version-reference-information) and [Roaming user profiles versioning in Windows 10 and Windows Server Technical Preview](/troubleshoot/windows-server/user-profiles-and-logon/roaming-user-profiles-versioning).
|
||||
|
||||
## Mandatory user profile
|
||||
|
||||
|
@ -39,11 +39,11 @@ Here's a step-by-step guide to adding an Azure Active Directory tenant, adding a
|
||||
|
||||
If you don't have a paid subscription to any Microsoft service, you can purchase an Azure AD premium subscription. Go to the Office 356 portal at https://portal.office.com/, and then sign in using the admin account that you created in Step 4 (for example, user1@contosoltd.onmicrosoftcom).
|
||||
|
||||

|
||||

|
||||
|
||||
6. Select **Install software**.
|
||||
|
||||

|
||||

|
||||
|
||||
7. In the Microsoft 365 admin center, select **Purchase Services** from the left navigation.
|
||||
|
||||
@ -69,27 +69,27 @@ If you have paid subscriptions to Office 365, Microsoft Dynamics CRM Online, Ent
|
||||
|
||||
1. Sign in to the Microsoft 365 admin center at <https://portal.office.com> using your organization's account.
|
||||
|
||||

|
||||

|
||||
|
||||
2. On the **Home** page, select on the Admin tools icon.
|
||||
|
||||

|
||||

|
||||
|
||||
3. On the **Admin center** page, hover your mouse over the Admin tools icon on the left and then click **Azure AD**. This will take you to the Azure Active Directory sign-up page and brings up your existing Office 365 organization account information.
|
||||
|
||||

|
||||

|
||||
|
||||
4. On the **Sign up** page, make sure to enter a valid phone number and then click **Sign up**.
|
||||
|
||||

|
||||

|
||||
|
||||
5. It may take a few minutes to process the request.
|
||||
|
||||

|
||||

|
||||
|
||||
6. You will see a welcome page when the process completes.
|
||||
|
||||

|
||||

|
||||
|
||||
|
||||
|
||||
|
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: ManikaDhiman
|
||||
author: dansimp
|
||||
ms.date: 07/10/2019
|
||||
---
|
||||
|
||||
|
@ -6,7 +6,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: ManikaDhiman
|
||||
author: dansimp
|
||||
ms.reviewer: jsuther1974
|
||||
ms.date: 09/10/2020
|
||||
---
|
||||
|
@ -28,7 +28,7 @@ For RequireDeviceEncryption and RequireStorageCardEncryption, the Get operation
|
||||
|
||||
The following shows the BitLocker configuration service provider in tree format.
|
||||
|
||||
```
|
||||
```console
|
||||
./Device/Vendor/MSFT
|
||||
BitLocker
|
||||
----RequireStorageCardEncryption
|
||||
@ -63,85 +63,21 @@ BitLocker
|
||||
<a href="" id="--device-vendor-msft-bitlocker"></a>**./Device/Vendor/MSFT/BitLocker**
|
||||
Defines the root node for the BitLocker configuration service provider.
|
||||
<!--Policy-->
|
||||
<a href="" id="requirestoragecardencryption"></a>**RequireStorageCardEncryption**
|
||||
<!--Description-->
|
||||
Allows the administrator to require storage card encryption on the device. This policy is valid only for a mobile SKU.
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
|
||||
Data type is integer. Sample value for this node to enable this policy: 1. Disabling this policy will not turn off the encryption on the storage card, but the user will no longer be prompted to turn it on.
|
||||
<!--SupportedValues-->
|
||||
- 0 (default) – Storage cards do not need to be encrypted.
|
||||
- 1 – Require storage cards to be encrypted.
|
||||
<!--/SupportedValues-->
|
||||
Disabling this policy will not turn off the encryption on the system card, but the user will no longer be prompted to turn it on.
|
||||
|
||||
If you want to disable this policy use the following SyncML:
|
||||
|
||||
```xml
|
||||
<SyncML>
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
<CmdID>$CmdID$</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/BitLocker/RequireStorageCardEncryption</LocURI>
|
||||
</Target>
|
||||
<Meta>
|
||||
<Format xmlns="syncml:metinf">int</Format>
|
||||
</Meta>
|
||||
<Data>0</Data>
|
||||
</Item>
|
||||
</Replace>
|
||||
</SyncBody>
|
||||
</SyncML>
|
||||
```
|
||||
|
||||
Data type is integer. Supported operations are Add, Get, Replace, and Delete.
|
||||
<!--/Policy-->
|
||||
<!--Policy-->
|
||||
<a href="" id="requiredeviceencryption"></a>**RequireDeviceEncryption**
|
||||
<!--Description-->
|
||||
Allows the administrator to require encryption to be turned on by using BitLocker\Device Encryption.
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
<!--/SupportedSKUs-->
|
||||
Data type is integer. Sample value for this node to enable this policy: 1.
|
||||
Supported operations are Add, Get, Replace, and Delete.
|
||||
@ -193,24 +129,15 @@ If you want to disable this policy, use the following SyncML:
|
||||
Allows you to set the default encryption method for each of the different drive types: operating system drives, fixed data drives, and removable data drives. Hidden, system, and recovery partitions are skipped from encryption. This setting is a direct mapping to the BitLocker Group Policy "Choose drive encryption method and cipher strength (Windows 10 [Version 1511] and later)".
|
||||
<!--/Description-->
|
||||
<!--SupportedValues-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
<!--/SupportedValues-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -276,26 +203,15 @@ Data type is string. Supported operations are Add, Get, Replace, and Delete.
|
||||
Allows you to associate unique organizational identifiers to a new drive that is enabled with BitLocker.
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -347,26 +263,15 @@ If you disable or do not configure this setting, the identification field is not
|
||||
Allows users on devices that are compliant with InstantGo or the Microsoft Hardware Security Test Interface (HSTI) to not have a PIN for preboot authentication.
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -400,26 +305,15 @@ If this policy is disabled, the options of "Require additional authentication at
|
||||
Allows users to configure whether or not enhanced startup PINs are used with BitLocker.
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -456,26 +350,15 @@ If you disable or do not configure this policy setting, enhanced PINs will not b
|
||||
Allows you to configure whether standard users are allowed to change BitLocker PIN or password that is used to protect the operating system drive.
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -512,26 +395,15 @@ Sample value for this node to disable this policy is:
|
||||
Allows users to enable authentication options that require user input from the preboot environment, even if the platform indicates a lack of preboot input capability.
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -574,26 +446,15 @@ When the Windows Recovery Environment is not enabled and this policy is not enab
|
||||
Allows you to configure the encryption type that is used by BitLocker.
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -633,26 +494,15 @@ For more information about the tool to manage BitLocker, see [Manage-bde](/windo
|
||||
This setting is a direct mapping to the BitLocker Group Policy "Require additional authentication at startup".
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -741,26 +591,15 @@ Data type is string. Supported operations are Add, Get, Replace, and Delete.
|
||||
This setting is a direct mapping to the BitLocker Group Policy "Configure minimum PIN length for startup".
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -818,26 +657,15 @@ This setting is a direct mapping to the BitLocker Group Policy "Configure pre-bo
|
||||
(PrebootRecoveryInfo_Name).
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -907,26 +735,15 @@ Data type is string. Supported operations are Add, Get, Replace, and Delete.
|
||||
This setting is a direct mapping to the BitLocker Group Policy "Choose how BitLocker-protected operating system drives can be recovered" (OSRecoveryUsage_Name).
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -1004,26 +821,15 @@ Data type is string. Supported operations are Add, Get, Replace, and Delete.
|
||||
This setting is a direct mapping to the BitLocker Group Policy "Choose how BitLocker-protected fixed drives can be recovered" ().
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -1110,26 +916,15 @@ Data type is string. Supported operations are Add, Get, Replace, and Delete.
|
||||
This setting is a direct mapping to the BitLocker Group Policy "Deny write access to fixed drives not protected by BitLocker" (FDVDenyWriteAccess_Name).
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -1179,26 +974,15 @@ Data type is string. Supported operations are Add, Get, Replace, and Delete.
|
||||
Allows you to configure the encryption type on fixed data drives that is used by BitLocker.
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -1240,26 +1024,15 @@ For more information about the tool to manage BitLocker, see [Manage-bde](/windo
|
||||
This setting is a direct mapping to the BitLocker Group Policy "Deny write access to removable drives not protected by BitLocker" (RDVDenyWriteAccess_Name).
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -1320,26 +1093,15 @@ Disabling the policy will let the system choose the default behaviors. If you wa
|
||||
Allows you to configure the encryption type that is used by BitLocker.
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -1375,26 +1137,15 @@ If this policy is disabled or not configured, the BitLocker Setup Wizard asks th
|
||||
Allows you to control the use of BitLocker on removable data drives.
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
@ -1445,26 +1196,15 @@ Allows the admin to disable the warning prompt for other disk encryption on the
|
||||
> [!Warning]
|
||||
> When you enable BitLocker on a device with third-party encryption, it may render the device unusable and require you to reinstall Windows.
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--SupportedValues-->
|
||||
The following list shows the supported values:
|
||||
@ -1509,26 +1249,15 @@ Allows Admin to enforce "RequireDeviceEncryption" policy for scenarios where pol
|
||||
|
||||
If "AllowWarningForOtherDiskEncryption" is not set, or is set to "1", "RequireDeviceEncryption" policy will not try to encrypt drive(s) if a standard user is the current logged on user in the system.
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
<!--SupportedValues-->
|
||||
The expected values for this policy are:
|
||||
@ -1564,26 +1293,15 @@ This setting initiates a client-driven recovery password refresh after an OS dri
|
||||
<!--/Description-->
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
|
||||
Value type is int. Supported operations are Add, Delete, Get, and Replace.
|
||||
@ -1619,26 +1337,15 @@ Each server-side recovery key rotation is represented by a request ID. The serve
|
||||
- RotateRecoveryPasswordsRequestID: Returns request ID of last request processed.
|
||||
- RotateRecoveryPasswordsRotationStatus: Returns status of last request processed.
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
|
||||
Value type is string. Supported operation is Execute. Request ID is expected as a parameter.
|
||||
@ -1664,26 +1371,15 @@ Interior node. Supported operation is Get.
|
||||
This node reports compliance state of device encryption on the system.
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
|
||||
<!--SupportedValues-->
|
||||
@ -1732,26 +1428,15 @@ Status code can be one of the following:
|
||||
- 0 - Pass
|
||||
- Any other code - Failure HRESULT
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
<!--/SupportedSKUs-->
|
||||
|
||||
Value type is int. Supported operation is Get.
|
||||
@ -1767,26 +1452,14 @@ This node reports the RequestID corresponding to RotateRecoveryPasswordsStatus.
|
||||
This node needs to be queried in synchronization with RotateRecoveryPasswordsStatus to ensure the status is correctly matched to the request ID.
|
||||
<!--/Description-->
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
<th>Home</th>
|
||||
<th>Pro</th>
|
||||
<th>Business</th>
|
||||
<th>Enterprise</th>
|
||||
<th>Education</th>
|
||||
<th>Mobile</th>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||
|
||||
</tr>
|
||||
</table>
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|Yes|
|
||||
|Business|Yes|Yes|
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
<!--/SupportedSKUs-->
|
||||
|
||||
|
@ -9,7 +9,7 @@ ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
ms.date: 10/25/2021
|
||||
---
|
||||
|
||||
# BrowserFavorite CSP
|
||||
|
File diff suppressed because one or more lines are too long
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 07/30/2021
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 08/02/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 09/18/2020
|
||||
ms.collection: highpri
|
||||
---
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -1,17 +1,17 @@
|
||||
---
|
||||
title: Data structures for Microsoft Store for Business
|
||||
description: Learn about the various data structures for Microsoft Store for Business.
|
||||
MS-HAID:
|
||||
- 'p\_phdevicemgmt.business\_store\_data\_structures'
|
||||
- 'p\_phDeviceMgmt.data\_structures\_windows\_store\_for\_business'
|
||||
ms.assetid: ABE44EC8-CBE5-4775-BA8A-4564CB73531B
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
description: Learn about data structures for Microsoft Store for Business.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 09/18/2017
|
||||
---
|
||||
|
||||
@ -105,7 +105,7 @@ Specifies the properties of the alternate identifier.
|
||||
|lastModified|dateTime|Specifies the last modified date for an application. Modifications for an application include updated product details, updates to an application, and updates to the quantity of an application.|
|
||||
|licenseType|[LicenseType](#licensetype)|Indicates whether the set of seats for a given application supports online or offline licensing.|
|
||||
|distributionPolicy|[InventoryDistributionPolicy](#inventorydistributionpolicy)||
|
||||
|Status|[InventoryStatus](#inventorystatus)||
|
||||
|status|[InventoryStatus](#inventorystatus)||
|
||||
|
||||
## InventoryResultSet
|
||||
|
||||
@ -191,20 +191,19 @@ Specifies the properties of the localized product.
|
||||
|packageFamilyName|String||
|
||||
|supportedPlatforms|Collection of [ProductPlatform](#productplatform)||
|
||||
|
||||
|
||||
## ProductImage
|
||||
|
||||
Specifies the properties of the product image.
|
||||
|
||||
|Name|Type|Description|
|
||||
|--- |--- |--- |
|
||||
|Location|URI|Location of the download image.|
|
||||
|Purpose|String|Tag for the purpose of the image, for example "screenshot" or "logo".|
|
||||
|Height|String|Height of the image in pixels.|
|
||||
|Width|String|Width of the image in pixels.|
|
||||
|Caption|String|Unlimited length.|
|
||||
|backgroundColor|String|Format "#RRGGBB"|
|
||||
|foregroundColor|String|Format "#RRGGBB"|
|
||||
|location|URI|Location of the download image.|
|
||||
|purpose|string|Tag for the image, for example "screenshot" or "logo".|
|
||||
|height|string|Height of the image in pixels.|
|
||||
|width|string|Width of the image in pixels.|
|
||||
|caption|string|Unlimited length.|
|
||||
|backgroundColor|string|Format "#RRGGBB"|
|
||||
|foregroundColor|string|Format "#RRGGBB"|
|
||||
|fileSize|integer-64|Size of the file.|
|
||||
|
||||
## ProductKey
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/23/2021
|
||||
---
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 03/27/2020
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/03/2020
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2018
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 11/15/2017
|
||||
ms.collection: highpri
|
||||
---
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 11/01/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/25/2021
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 03/12/2018
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/25/2018
|
||||
ms.collection: highpri
|
||||
---
|
||||
@ -36,12 +36,12 @@ To help diagnose enrollment or device management issues in Windows 10 devices m
|
||||
You can also collect the MDM Diagnostic Information logs using the following command:
|
||||
|
||||
```xml
|
||||
mdmdiagnosticstool.exe -area DeviceEnrollment;DeviceProvisioning;Autopilot -cab c:\users\public\documents\MDMDiagReport.cab
|
||||
mdmdiagnosticstool.exe -area DeviceEnrollment;DeviceProvisioning;Autopilot -zip c:\users\public\documents\MDMDiagReport.zip
|
||||
```
|
||||
- In File Explorer, navigate to c:\Users\Public\Documents\MDMDiagnostics to see the report.
|
||||
|
||||
### Understanding cab structure
|
||||
The cab file will have logs according to the areas that were used in the command. This explanation is based on DeviceEnrollment, DeviceProvisioning and Autopilot areas. It applies to the cab files collected via command line or Feedback Hub
|
||||
### Understanding zip structure
|
||||
The zip file will have logs according to the areas that were used in the command. This explanation is based on DeviceEnrollment, DeviceProvisioning and Autopilot areas. It applies to the zip files collected via command line or Feedback Hub
|
||||
|
||||
- DiagnosticLogCSP_Collector_Autopilot_*: Autopilot etls
|
||||
- DiagnosticLogCSP_Collector_DeviceProvisioning_*: Provisioning etls (Microsoft-Windows-Provisioning-Diagnostics-Provider)
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 11/19/2019
|
||||
---
|
||||
|
||||
@ -246,7 +246,15 @@ la--- 1/4/2021 2:45 PM 1
|
||||
la--- 1/4/2021 2:45 PM 2
|
||||
la--- 12/2/2020 6:27 PM 2701 results.xml
|
||||
```
|
||||
Each data gathering directive from the original `Collection` XML corresponds to a folder in the output. For example, if the first directive was <RegistryKey HRESULT="0">HKLM\Software\Policies</RegistryKey> then folder `1` will contain the corresponding `export.reg` file.
|
||||
Each data gathering directive from the original `Collection` XML corresponds to a folder in the output.
|
||||
For example, the first directive was:
|
||||
|
||||
```xml
|
||||
<Collection HRESULT="0">
|
||||
<RegistryKey HRESULT="0">HKLM\Software\Policies</RegistryKey>
|
||||
</Collection>
|
||||
```
|
||||
then folder `1` will contain the corresponding `export.reg` file.
|
||||
|
||||
The `results.xml` file is the authoritative map to the output. It includes a status code for each directive. The order of the directives in the file corresponds to the order of the output folders. Using `results.xml` the administrator can see what data was gathered, what failures may have occurred, and which folders contain which output. For example, the following `results.xml` content indicates that registry export of HKLM\Software\Policies was successful and the data can be found in folder `1`. It also indicates that `netsh.exe wlan show profiles` command failed.
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -11,7 +11,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 11/01/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -18,7 +18,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 11/01/2017
|
||||
ms.reviewer:
|
||||
|
@ -6,7 +6,7 @@ ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: dansimp
|
||||
ms.date: 10/14/2021
|
||||
ms.date: 12/03/2021
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.collection: highpri
|
||||
@ -14,6 +14,10 @@ ms.collection: highpri
|
||||
|
||||
# Enroll a Windows 10 device automatically using Group Policy
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
|
||||
Starting in Windows 10, version 1709, you can use a Group Policy to trigger auto-enrollment to MDM for Active Directory (AD) domain-joined devices.
|
||||
|
||||
The enrollment into Intune is triggered by a group policy created on your local AD and happens without any user interaction. This means you can automatically mass-enroll a large number of domain-joined corporate devices into Microsoft Intune. The enrollment process starts in the background once you sign in to the device with your Azure AD account.
|
||||
@ -45,9 +49,10 @@ For this policy to work, you must verify that the MDM service provider allows th
|
||||
## Verify auto-enrollment requirements and settings
|
||||
To ensure that the auto-enrollment feature is working as expected, you must verify that various requirements and settings are configured correctly.
|
||||
The following steps demonstrate required settings using the Intune service:
|
||||
|
||||
1. Verify that the user who is going to enroll the device has a valid Intune license.
|
||||
|
||||

|
||||
:::image type="content" alt-text="Intune license verification." source="images/auto-enrollment-intune-license-verification.png" lightbox="images/auto-enrollment-intune-license-verification.png":::
|
||||
|
||||
2. Verify that auto-enrollment is activated for those users who are going to enroll the devices into Intune. For additional details, see [Azure AD and Microsoft Intune: Automatic MDM enrollment in the new Portal](./azure-ad-and-microsoft-intune-automatic-mdm-enrollment-in-the-new-portal.md).
|
||||
|
||||
@ -79,7 +84,7 @@ The following steps demonstrate required settings using the Intune service:
|
||||
|
||||
6. Some tenants might have both **Microsoft Intune** and **Microsoft Intune Enrollment** under **Mobility**. Make sure that your auto-enrollment settings are configured under **Microsoft Intune** instead of **Microsoft Intune Enrollment**.
|
||||
|
||||

|
||||
:::image type="content" alt-text="Mobility setting MDM intune." source="images/auto-enrollment-microsoft-intune-setting.png" lightbox="images/auto-enrollment-microsoft-intune-setting.png":::
|
||||
|
||||
7. Verify that the *Enable Automatic MDM enrollment using default Azure AD credentials* group policy (**Local Group Policy Editor > Computer Configuration > Policies > Administrative Templates > Windows Components > MDM**) is properly deployed to all devices which should be enrolled into Intune.
|
||||
You may contact your domain administrators to verify if the group policy has been deployed successfully.
|
||||
@ -88,7 +93,7 @@ You may contact your domain administrators to verify if the group policy has bee
|
||||
|
||||
9. Verify that Microsoft Intune should allow enrollment of Windows devices.
|
||||
|
||||

|
||||
:::image type="content" alt-text="Enrollment of Windows devices." source="images/auto-enrollment-enrollment-of-windows-devices.png" lightbox="images/auto-enrollment-enrollment-of-windows-devices.png":::
|
||||
|
||||
## Configure the auto-enrollment Group Policy for a single PC
|
||||
|
||||
@ -109,12 +114,11 @@ Requirements:
|
||||
|
||||
3. In **Local Computer Policy**, click **Administrative Templates** > **Windows Components** > **MDM**.
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
:::image type="content" alt-text="MDM policies." source="images/autoenrollment-mdm-policies.png" lightbox="images/autoenrollment-mdm-policies.png":::
|
||||
|
||||
4. Double-click **Enable automatic MDM enrollment using default Azure AD credentials** (previously called **Auto MDM Enrollment with AAD Token** in Windows 10, version 1709). For ADMX files in Windows 10, version 1903 and later, select **User Credential** as the Selected Credential Type to use.
|
||||
|
||||

|
||||
:::image type="content" alt-text="MDM autoenrollment policy." source="images/autoenrollment-policy.png" lightbox="images/autoenrollment-policy.png":::
|
||||
|
||||
5. Click **Enable**, and select **User Credential** from the dropdown **Select Credential Type to Use**, then click **OK**.
|
||||
|
||||
@ -155,7 +159,7 @@ Requirements:
|
||||
|
||||
3. In **Task Scheduler Library**, open **Microsoft > Windows** , then click **EnterpriseMgmt**.
|
||||
|
||||

|
||||
:::image type="content" alt-text="Auto-enrollment scheduled task." source="images/autoenrollment-scheduled-task.png" lightbox="images/autoenrollment-scheduled-task.png":::
|
||||
|
||||
To see the result of the task, move the scroll bar to the right to see the **Last Run Result**. Note that **0x80180026** is a failure message (MENROLL\_E_DEVICE\_MANAGEMENT_BLOCKED). You can see the logs in the **History** tab.
|
||||
|
||||
@ -191,6 +195,9 @@ Requirements:
|
||||
|
||||
- 21H1 --> [Administrative Templates (.admx) for Windows 10 May 2021 Update (21H1)](https://www.microsoft.com/download/details.aspx?id=103124)
|
||||
|
||||
- 21H2 --> [Administrative Templates (.admx) for Windows 10 November 2021 Update (21H2)](https://www.microsoft.com/download/103667)
|
||||
|
||||
|
||||
2. Install the package on the Domain Controller.
|
||||
|
||||
3. Navigate, depending on the version to the folder:
|
||||
@ -209,11 +216,13 @@ Requirements:
|
||||
|
||||
- 21H1 --> **C:\Program Files (x86)\Microsoft Group Policy\Windows 10 May 2021 Update (21H1)**
|
||||
|
||||
- 21H2 --> **C:\Program Files (x86)\Microsoft Group Policy\Windows 10 November 2021 Update (21H2)**
|
||||
|
||||
4. Rename the extracted Policy Definitions folder to **PolicyDefinitions**.
|
||||
|
||||
5. Copy PolicyDefinitions folder to **\\contoso.com\SYSVOL\contoso.com\policies\PolicyDefinitions**.
|
||||
5. Copy PolicyDefinitions folder to **\\SYSVOL\contoso.com\policies\PolicyDefinitions**.
|
||||
|
||||
If this folder does not exist, then be aware that you will be switching to a [central policy store](https://support.microsoft.com/help/3087759/how-to-create-and-manage-the-central-store-for-group-policy-administra) for your entire domain.
|
||||
If this folder does not exist, then be aware that you will be switching to a [central policy store](/troubleshoot/windows-client/group-policy/create-and-manage-central-store) for your entire domain.
|
||||
|
||||
6. Wait for the SYSVOL DFSR replication to be completed for the policy to be available.
|
||||
|
||||
@ -240,21 +249,21 @@ To collect Event Viewer logs:
|
||||
|
||||
3. Search for event ID 75, which represents a successful auto-enrollment. Here is an example screenshot that shows the auto-enrollment completed successfully:
|
||||
|
||||

|
||||
:::image type="content" alt-text="Event ID 75." source="images/auto-enrollment-troubleshooting-event-id-75.png" lightbox="images/auto-enrollment-troubleshooting-event-id-75.png":::
|
||||
|
||||
If you cannot find event ID 75 in the logs, it indicates that the auto-enrollment failed. This can happen because of the following reasons:
|
||||
|
||||
- The enrollment failed with error. In this case, search for event ID 76, which represents failed auto-enrollment. Here is an example screenshot that shows that the auto-enrollment failed:
|
||||
|
||||

|
||||
:::image type="content" alt-text="Event ID 76." source="images/auto-enrollment-troubleshooting-event-id-76.png" lightbox="images/auto-enrollment-troubleshooting-event-id-76.png":::
|
||||
|
||||
To troubleshoot, check the error code that appears in the event. See [Troubleshooting Windows device enrollment problems in Microsoft Intune](https://support.microsoft.com/en-ph/help/4469913/troubleshooting-windows-device-enrollment-problems-in-microsoft-intune) for more information.
|
||||
To troubleshoot, check the error code that appears in the event. See [Troubleshooting Windows device enrollment problems in Microsoft Intune](/troubleshoot/mem/intune/troubleshoot-windows-enrollment-errors) for more information.
|
||||
|
||||
- The auto-enrollment did not trigger at all. In this case, you will not find either event ID 75 or event ID 76. To know the reason, you must understand the internal mechanisms happening on the device as described in the following section.
|
||||
|
||||
The auto-enrollment process is triggered by a task (**Microsoft > Windows > EnterpriseMgmt**) within the task-scheduler. This task appears if the *Enable automatic MDM enrollment using default Azure AD credentials* group policy (**Computer Configuration > Policies > Administrative Templates > Windows Components > MDM**) is successfully deployed to the target machine as shown in the following screenshot:
|
||||
|
||||

|
||||
:::image type="content" alt-text="Task scheduler." source="images/auto-enrollment-task-scheduler.png" lightbox="images/auto-enrollment-task-scheduler.png":::
|
||||
|
||||
> [!Note]
|
||||
> This task isn't visible to standard users - run Scheduled Tasks with administrative credentials to find the task.
|
||||
@ -263,24 +272,24 @@ To collect Event Viewer logs:
|
||||
**Applications and Services Logs > Microsoft > Windows > Task Scheduler > Operational**.
|
||||
Look for an entry where the task scheduler created by enrollment client for automatically enrolling in MDM from AAD is triggered by event ID 107.
|
||||
|
||||

|
||||
:::image type="content" alt-text="Event ID 107." source="images/auto-enrollment-event-id-107.png" lightbox="images/auto-enrollment-event-id-107.png":::
|
||||
|
||||
When the task is completed, a new event ID 102 is logged.
|
||||
|
||||

|
||||
:::image type="content" alt-text="Event ID 102." source="images/auto-enrollment-event-id-102.png" lightbox="images/auto-enrollment-event-id-102.png":::
|
||||
|
||||
Note that the task scheduler log displays event ID 102 (task completed) regardless of the auto-enrollment success or failure. This means that the task scheduler log is only useful to confirm if the auto-enrollment task is triggered or not. It does not indicate the success or failure of auto-enrollment.
|
||||
|
||||
If you cannot see from the log that task Schedule created by enrollment client for automatically enrolling in MDM from AAD is initiated, there is possibly issue with the group policy. Immediately run the command `gpupdate /force` in command prompt to get the GPO applied. If this still does not help, further troubleshooting on the Active Directory is required.
|
||||
One frequently seen error is related to some outdated enrollment entries in the registry on the target client device (**HKLM > Software > Microsoft > Enrollments**). If a device has been enrolled (can be any MDM solution and not only Intune), some enrollment information added into the registry is seen:
|
||||
|
||||

|
||||
:::image type="content" alt-text="Outdated enrollment entries." source="images/auto-enrollment-outdated-enrollment-entries.png" lightbox="images/auto-enrollment-outdated-enrollment-entries.png":::
|
||||
|
||||
By default, these entries are removed when the device is un-enrolled, but occasionally the registry key remains even after un-enrollment. In this case, `gpupdate /force` fails to initiate the auto-enrollment task and error code 2149056522 is displayed in the **Applications and Services Logs > Microsoft > Windows > Task Scheduler > Operational** event log file under event ID 7016.
|
||||
|
||||
A resolution to this issue is to remove the registry key manually. If you do not know which registry key to remove, go for the key which displays most entries as the screenshot above. All other keys will display fewer entries as shown in the following screenshot:
|
||||
|
||||

|
||||
:::image type="content" alt-text="Manually deleted entries." source="images/auto-enrollment-activation-verification-less-entries.png" lightbox="images/auto-enrollment-activation-verification-less-entries.png":::
|
||||
|
||||
### Related topics
|
||||
|
||||
@ -289,13 +298,14 @@ To collect Event Viewer logs:
|
||||
- [Link a Group Policy Object](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732979(v=ws.11))
|
||||
- [Filter Using Security Groups](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc752992(v=ws.11))
|
||||
- [Enforce a Group Policy Object Link](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc753909(v=ws.11))
|
||||
- [Group Policy Central Store](https://support.microsoft.com/help/3087759/how-to-create-and-manage-the-central-store-for-group-policy-administra)
|
||||
- [Getting started with Cloud Native Windows Endpoints](https://docs.microsoft.com/mem/cloud-native-windows-endpoints)
|
||||
- [Group Policy Central Store](/troubleshoot/windows-client/group-policy/create-and-manage-central-store)
|
||||
- [Getting started with Cloud Native Windows Endpoints](/mem/cloud-native-windows-endpoints)
|
||||
- [A Framework for Windows endpoint management transformation](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/a-framework-for-windows-endpoint-management-transformation/ba-p/2460684)
|
||||
- [Success with remote Windows Autopilot and Hybrid Azure Active Director join](https://techcommunity.microsoft.com/t5/intune-customer-success/success-with-remote-windows-autopilot-and-hybrid-azure-active/ba-p/2749353)
|
||||
|
||||
|
||||
### Useful Links
|
||||
- [Windows 10 Administrative Templates for Windows 10 November 2021 Update 21H2](https://www.microsoft.com/download/103667)
|
||||
- [Windows 10 Administrative Templates for Windows 10 May 2021 Update 21H1](https://www.microsoft.com/download/details.aspx?id=103124)
|
||||
- [Windows 10 Administrative Templates for Windows 10 November 2019 Update 1909](https://www.microsoft.com/download/details.aspx?id=100591)
|
||||
- [Windows 10 Administrative Templates for Windows 10 May 2019 Update 1903](https://www.microsoft.com/download/details.aspx?id=58495)
|
||||
|
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: ManikaDhiman
|
||||
author: dansimp
|
||||
ms.date: 05/17/2019
|
||||
---
|
||||
|
||||
|
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: ManikaDhiman
|
||||
author: dansimp
|
||||
ms.date: 05/21/2019
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 09/22/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 07/12/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 08/09/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 07/11/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 10/01/2019
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 03/02/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 03/02/2018
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 07/28/2017
|
||||
---
|
||||
|
||||
|
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user