mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-24 14:53:44 +00:00
Merged PR 3299: Merge master to wdav-uc-tshooting
This commit is contained in:
Iaan D'Souza-Wiltshire
@ -222,8 +222,6 @@
|
||||
#### [Windows Insider Program for Business using Azure Active Directory](update/waas-windows-insider-for-business-aad.md)
|
||||
#### [Windows Insider Program for Business Frequently Asked Questions](update/waas-windows-insider-for-business-faq.md)
|
||||
#### [Olympia Corp enrollment](update/olympia/olympia-enrollment-guidelines.md)
|
||||
##### [Keep your current Windows 10 edition](update/olympia/enrollment-keep-current-edition.md)
|
||||
##### [Upgrade your Windows 10 edition from Pro to Enterprise](update/olympia/enrollment-upgrade-to-enterprise.md)
|
||||
### [Change history for Update Windows 10](update/change-history-for-update-windows-10.md)
|
||||
|
||||
## Windows Analytics
|
||||
|
||||
@ -15,8 +15,18 @@ author: greg-lindsay
|
||||
|
||||
This topic describes how to deploy Windows 10 Enterprise E3 or E5 licenses with [Windows 10 Enterprise Subscription Activation](windows-10-enterprise-subscription-activation.md) or [Windows 10 Enterprise E3 in CSP](windows-10-enterprise-e3-overview.md) and Azure Active Directory (Azure AD).
|
||||
|
||||
>Note: Windows 10 Enterprise Subscription Activation (EA or MPSA) requires Windows 10 Pro, version 1703 or later.
|
||||
>Windows 10 Enterprise E3 in CSP requires Windows 10 Pro, version 1607 or later.
|
||||
>Note: Windows 10 Enterprise Subscription Activation (EA or MPSA) requires Windows 10 Pro, version 1703 or later.<BR>
|
||||
>Windows 10 Enterprise E3 in CSP requires Windows 10 Pro, version 1607 or later.<BR>
|
||||
|
||||
## Enabling Subscription Activation with an existing EA
|
||||
|
||||
If you are an EA customer with an existing Office 365 tenant, use the following steps to enable Windows 10 Subscription licenses on your existing tenant:
|
||||
|
||||
1. Work with your reseller to place an order for $0 SKU. There are two SKUs available, depending on their current Windows Enterprise SA license:<BR>
|
||||
a. **AAA-51069** - Win10UsrOLSActv Alng MonthlySub Addon E3<BR>
|
||||
b. **AAA-51068** - Win10UsrOLSActv Alng MonthlySub Addon E5<BR>
|
||||
2. After placing an order, the OLS admin on the agreement will receive a service activation email, indicating their subscription licenses have been provisioned on the tenant.
|
||||
3. The admin can now assign subscription licenses to users.
|
||||
|
||||
Also in this article:
|
||||
- [Explore the upgrade experience](#explore-the-upgrade-experience): How to upgrade devices using the deployed licenses.
|
||||
@ -195,5 +205,4 @@ Devices must be running Windows 10 Pro, version 1703, and be Azure Active Direct
|
||||
|
||||
A popup window will display the Windows 10 version number and detailed OS build information.
|
||||
|
||||
If a device is running a previous version of Windows 10 Pro (for example, version 1511), it will not be upgraded to Windows 10 Enterprise when a user signs in, even if the user has been assigned a subscription in the CSP portal.
|
||||
|
||||
If a device is running a previous version of Windows 10 Pro (for example, version 1511), it will not be upgraded to Windows 10 Enterprise when a user signs in, even if the user has been assigned a subscription in the CSP portal.
|
||||
@ -79,7 +79,7 @@ For more information, see [MBR2GPT.EXE](mbr-to-gpt.md).
|
||||
|
||||
### Microsoft Deployment Toolkit (MDT)
|
||||
|
||||
MDT build 884 is available, including support for:
|
||||
MDT build 8443 is available, including support for:
|
||||
- Deployment and upgrade of Windows 10, version 1607 (including Enterprise LTSB and Education editions) and Windows Server 2016.
|
||||
- The Windows ADK for Windows 10, version 1607.
|
||||
- Integration with Configuration Manager version 1606.
|
||||
|
||||
@ -1,44 +0,0 @@
|
||||
---
|
||||
title: Keep your current Windows 10 edition
|
||||
description: Olympia Corp enrollment - Keep your current Windows 10 edition
|
||||
ms.author: nibr
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: nickbrower
|
||||
ms.date: 09/01/2017
|
||||
---
|
||||
|
||||
# Olympia Corp enrollment
|
||||
|
||||
## Keep your current Windows 10 edition
|
||||
|
||||
1. Go to **Start > Settings > Accounts > Access work or school**. To see this setting, you need to have administrator rights to your PC (see [local administrator](https://support.microsoft.com/en-us/instantanswers/5de907f1-f8ba-4fd9-a89d-efd23fee918c/create-a-local-user-or-administrator-account-in-windows-10)).
|
||||
|
||||
|
||||
|
||||
2. If you are already connected to a domain, click the existing account and then click **Disconnect**. Click **Restart Later**.
|
||||
|
||||
3. Click **Connect** and enter your **Olympia corporate account** (e.g., username@olympia.windows.com). Click **Next**.
|
||||
|
||||
|
||||
|
||||
4. Enter the temporary password that was sent to you. Click **Sign in**. Follow the instructions to set a new password.
|
||||
|
||||
> [!NOTE]
|
||||
> Passwords should contain 8-16 characters, including at least one special character or number.
|
||||
|
||||
|
||||
|
||||
5. Read the **Terms and Conditions**. Click **Accept** to participate in the program.
|
||||
|
||||
6. If this is the first time you are logging in, please fill in the additional information to help you retrieve your account details.
|
||||
|
||||
7. Create a PIN for signing into your Olympia corporate account.
|
||||
|
||||
8. Go to **Start > Settings > Update & Security > Windows Insider Program**. Click on the current Windows Insider account, and click **Change**. Sign in with your **Olympia corporate account**.
|
||||
|
||||
> [!NOTE]
|
||||
> To complete this step, you will need to register your account with the [Windows Insider Program for Business](https://insider.windows.com/ForBusiness).
|
||||
|
||||
9. Open the **Feedback Hub**, and sign in with your **Olympia corporate account**.
|
||||
@ -1,57 +0,0 @@
|
||||
---
|
||||
title: Upgrade your Windows 10 edition from Pro to Enterprise
|
||||
description: Olympia Corp enrollment - Upgrade your Windows 10 edition from Pro to Enterprise
|
||||
ms.author: nibr
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: nickbrower
|
||||
ms.date: 09/01/2017
|
||||
---
|
||||
|
||||
# Olympia Corp enrollment
|
||||
|
||||
## Upgrade your Windows 10 edition from Pro to Enterprise
|
||||
|
||||
1. Go to **Start > Settings > Accounts > Access work or school**. To see this setting, you need to have administrator rights to your PC (see [local administrator](https://support.microsoft.com/en-us/instantanswers/5de907f1-f8ba-4fd9-a89d-efd23fee918c/create-a-local-user-or-administrator-account-in-windows-10)).
|
||||
|
||||
|
||||
|
||||
2. If you are already connected to a domain, click the existing account and then click **Disconnect**. Click **Restart Later**.
|
||||
|
||||
3. Click **Connect**, then click **Join this device to Azure Active Directory**.
|
||||
|
||||
|
||||
|
||||
4. Enter your **Olympia corporate account** (e.g., username@olympia.windows.com). Click **Next**.
|
||||
|
||||
|
||||
|
||||
5. Enter the temporary password that was sent to you. Click **Sign in**. Follow the instructions to set a new password.
|
||||
|
||||
> [!NOTE]
|
||||
> Passwords should contain 8-16 characters, including at least one special character or number.
|
||||
|
||||
|
||||
|
||||
6. When asked to make sure this is your organization, verify that the information is correct. If so, click **Join**.
|
||||
|
||||
7. If this is the first time you are signing in, please fill in the additional information to help you retrieve your account details.
|
||||
|
||||
8. Create a PIN for signing into your Olympia corporate account.
|
||||
|
||||
9. When asked to make sure this is your organization, verify that the information is correct. If so, click **Join**.
|
||||
|
||||
10. Restart your PC.
|
||||
|
||||
11. In the sign-in screen, choose **Other User** and sign in with your **Olympia corporate account**. Your PC will upgrade to Windows 10 Enterprise*.
|
||||
|
||||
12. Go to **Start > Settings > Update & Security > Windows Insider Program**. Click on the current Windows Insider account, and click **Change**. Sign in with your **Olympia corporate account**.
|
||||
|
||||
> [!NOTE]
|
||||
> To complete this step, you will need to register your account with the [Windows Insider Program for Business](https://insider.windows.com/ForBusiness).
|
||||
|
||||
13. Open the **Feedback Hub**, and sign in with your **Olympia corporate account**.
|
||||
|
||||
\* Please note that your Windows 10 Enterprise license will not be renewed if your PC is not connected to Olympia.
|
||||
|
||||
@ -6,7 +6,7 @@ ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: nickbrower
|
||||
ms.date: 09/01/2017
|
||||
ms.date: 09/14/2017
|
||||
---
|
||||
|
||||
# Olympia Corp enrollment guidelines
|
||||
@ -17,6 +17,87 @@ As part of Windows Insider Lab for Enterprise, you can upgrade to Windows 10 Ent
|
||||
|
||||
Choose one of the following two enrollment options:
|
||||
|
||||
1. [Keep your current Windows 10 edition](./enrollment-keep-current-edition.md)
|
||||
1. [Keep your current Windows 10 edition](#enrollment-keep-current-edition)
|
||||
|
||||
2. [Upgrade your Windows 10 edition from Pro to Enterprise](#enrollment-upgrade-to-enterprise)
|
||||
|
||||
<a id="enrollment-keep-current-edition"></a>
|
||||
|
||||
## Keep your current Windows 10 edition
|
||||
|
||||
1. Go to **Start > Settings > Accounts > Access work or school**. To see this setting, you need to have administrator rights to your PC (see [local administrator](https://support.microsoft.com/en-us/instantanswers/5de907f1-f8ba-4fd9-a89d-efd23fee918c/create-a-local-user-or-administrator-account-in-windows-10)).
|
||||
|
||||
|
||||
|
||||
2. If you are already connected to a domain, click the existing account and then click **Disconnect**. Click **Restart Later**.
|
||||
|
||||
3. Click **Connect** and enter your **Olympia corporate account** (e.g., username@olympia.windows.com). Click **Next**.
|
||||
|
||||
|
||||
|
||||
4. Enter the temporary password that was sent to you. Click **Sign in**. Follow the instructions to set a new password.
|
||||
|
||||
> [!NOTE]
|
||||
> Passwords should contain 8-16 characters, including at least one special character or number.
|
||||
|
||||
|
||||
|
||||
5. Read the **Terms and Conditions**. Click **Accept** to participate in the program.
|
||||
|
||||
6. If this is the first time you are logging in, please fill in the additional information to help you retrieve your account details.
|
||||
|
||||
7. Create a PIN for signing into your Olympia corporate account.
|
||||
|
||||
8. Go to **Start > Settings > Update & Security > Windows Insider Program**. Click on the current Windows Insider account, and click **Change**. Sign in with your **Olympia corporate account**.
|
||||
|
||||
> [!NOTE]
|
||||
> To complete this step, you will need to register your account with the [Windows Insider Program for Business](https://insider.windows.com/ForBusiness).
|
||||
|
||||
9. Open the **Feedback Hub**, and sign in with your **Olympia corporate account**.
|
||||
|
||||
<a id="enrollment-upgrade-to-enterprise"></a>
|
||||
|
||||
## Upgrade your Windows 10 edition from Pro to Enterprise
|
||||
|
||||
1. Go to **Start > Settings > Accounts > Access work or school**. To see this setting, you need to have administrator rights to your PC (see [local administrator](https://support.microsoft.com/en-us/instantanswers/5de907f1-f8ba-4fd9-a89d-efd23fee918c/create-a-local-user-or-administrator-account-in-windows-10)).
|
||||
|
||||
|
||||
|
||||
2. If you are already connected to a domain, click the existing account and then click **Disconnect**. Click **Restart Later**.
|
||||
|
||||
3. Click **Connect**, then click **Join this device to Azure Active Directory**.
|
||||
|
||||
|
||||
|
||||
4. Enter your **Olympia corporate account** (e.g., username@olympia.windows.com). Click **Next**.
|
||||
|
||||
|
||||
|
||||
5. Enter the temporary password that was sent to you. Click **Sign in**. Follow the instructions to set a new password.
|
||||
|
||||
> [!NOTE]
|
||||
> Passwords should contain 8-16 characters, including at least one special character or number.
|
||||
|
||||
|
||||
|
||||
6. When asked to make sure this is your organization, verify that the information is correct. If so, click **Join**.
|
||||
|
||||
7. If this is the first time you are signing in, please fill in the additional information to help you retrieve your account details.
|
||||
|
||||
8. Create a PIN for signing into your Olympia corporate account.
|
||||
|
||||
9. When asked to make sure this is your organization, verify that the information is correct. If so, click **Join**.
|
||||
|
||||
10. Restart your PC.
|
||||
|
||||
11. In the sign-in screen, choose **Other User** and sign in with your **Olympia corporate account**. Your PC will upgrade to Windows 10 Enterprise*.
|
||||
|
||||
12. Go to **Start > Settings > Update & Security > Windows Insider Program**. Click on the current Windows Insider account, and click **Change**. Sign in with your **Olympia corporate account**.
|
||||
|
||||
> [!NOTE]
|
||||
> To complete this step, you will need to register your account with the [Windows Insider Program for Business](https://insider.windows.com/ForBusiness).
|
||||
|
||||
13. Open the **Feedback Hub**, and sign in with your **Olympia corporate account**.
|
||||
|
||||
\* Please note that your Windows 10 Enterprise license will not be renewed if your PC is not connected to Olympia.
|
||||
|
||||
2. [Upgrade your Windows 10 edition from Pro to Enterprise](./enrollment-upgrade-to-enterprise.md)
|
||||
|
||||
@ -5,6 +5,7 @@ ms.assetid: 5a37e390-8617-4768-9eee-50397fbbb2e1
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.date: 09/07/2017
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
@ -28,6 +29,8 @@ The following sections discuss common issues that you might see when you run the
|
||||
|
||||
[Hard Link Migration Problems](#bkmk-hardlink)
|
||||
|
||||
[USMT does not migrate the Start layout](#usmt-does-not-migrate-the-start-layout)
|
||||
|
||||
## General Guidelines for Identifying Migration Problems
|
||||
|
||||
|
||||
@ -222,6 +225,28 @@ There are three typical causes for this issue.
|
||||
|
||||
**Resolution:** To migrate PST files that are not linked to Outlook profiles, you must create a separate migration rule to capture these files.
|
||||
|
||||
### USMT does not migrate the Start layout
|
||||
|
||||
**Description:** You are using USMT to migrate profiles from one installation of Windows 10 to another installation of Windows 10 on different hardware. After migration, the user signs in on the new device and does not have the Start menu layout they had previously configured.
|
||||
|
||||
**Cause:** A code change in the Start Menu with Windows 10 version 1607 and later is incompatible with this USMT function.
|
||||
|
||||
**Resolution:** The following workaround is available:
|
||||
|
||||
1. With the user signed in, back up the Start layout using the following Windows PowerShell command. You can specify a different path if desired:
|
||||
|
||||
```
|
||||
Export-StartLayout -Path "C:\Layout\user1.xml"
|
||||
```
|
||||
2. Migrate the user's profile with USMT.
|
||||
3. Before the user signs in on the new device, import the Start layout using the following Windows PowerShell command:
|
||||
|
||||
```
|
||||
Import-StartLayout –LayoutPath "C:\Layout\user1.xml" –MountPath %systemdrive%
|
||||
```
|
||||
|
||||
This workaround changes the Default user's Start layout. The workaround does not scale to a mass migrations or multiuser devices, but it can potentially unblock some scenarios. If other users will sign on to the device you should delete layoutmodification.xml from the Default user profile. Otherwise, all users who sign on to that device will use the imported Start layout.
|
||||
|
||||
## <a href="" id="bkmk-offline"></a>Offline Migration Problems
|
||||
|
||||
|
||||
@ -286,6 +311,10 @@ USMTutils /rd <storedir>
|
||||
|
||||
You should also reboot the machine.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: What Does USMT Migrate (Windows 10)
|
||||
description: What Does USMT Migrate
|
||||
title: What does USMT migrate (Windows 10)
|
||||
description: What does USMT migrate
|
||||
ms.assetid: f613987d-0f17-43fe-9717-6465865ceda7
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -8,23 +8,23 @@ ms.sitesec: library
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# What Does USMT Migrate?
|
||||
# What does USMT migrate?
|
||||
|
||||
|
||||
## In This Topic
|
||||
## In this topic
|
||||
|
||||
|
||||
- [Default Migration Scripts](#bkmk-defaultmigscripts)
|
||||
- [Default migration scripts](#bkmk-defaultmigscripts)
|
||||
|
||||
- [User Data](#bkmk-3)
|
||||
|
||||
- [Operating-System Components](#bkmk-4)
|
||||
- [Operating-system components](#bkmk-4)
|
||||
|
||||
- [Supported Applications](#bkmk-2)
|
||||
- [Supported applications](#bkmk-2)
|
||||
|
||||
- [What USMT Does Not Migrate](#no)
|
||||
- [What USMT does not migrate](#no)
|
||||
|
||||
## <a href="" id="bkmk-defaultmigscripts"></a>Default Migration Scripts
|
||||
## <a href="" id="bkmk-defaultmigscripts"></a>Default migration scripts
|
||||
|
||||
|
||||
The User State Migration Tool (USMT) 10.0 is designed so that an IT engineer can precisely define migrations using the USMT .xml scripting language. USMT provides the following sample scripts:
|
||||
@ -43,7 +43,7 @@ The User State Migration Tool (USMT) 10.0 is designed so that an IT engineer ca
|
||||
|
||||
- Access control lists (ACLs) for folders outside the user profile.
|
||||
|
||||
## <a href="" id="bkmk-3"></a>User Data
|
||||
## <a href="" id="bkmk-3"></a>User data
|
||||
|
||||
|
||||
This section describes the user data that USMT migrates by default, using the MigUser.xml file. It also defines how to migrate ACLs.
|
||||
@ -52,6 +52,9 @@ This section describes the user data that USMT migrates by default, using the Mi
|
||||
|
||||
My Documents, My Video, My Music, My Pictures, desktop files, Start menu, Quick Launch settings, and Favorites.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Starting in Windows 10, version 1607 the USMT does not migrate the Start menu layout. To migrate a user's Start menu, you must export and then import settings using the Windows PowerShell cmdlets **Export-StartLayout** and **Import-StartLayout**. For more information, see [USMT common issues](https://docs.microsoft.com/windows/deployment/usmt/usmt-common-issues#usmt-does-not-migrate-the-start-layout).
|
||||
|
||||
- **Folders from the All Users and Public profiles.** When you specify the MigUser.xml file, USMT also migrates the following from the **All Users** profile in Windows® XP, or the **Public** profile in Windows Vista, Windows 7, or Windows 8:
|
||||
|
||||
- Shared Documents
|
||||
@ -84,7 +87,7 @@ To migrate ACLs, you must specify the directory to migrate in the MigUser.xml fi
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-4"></a>Operating-System Components
|
||||
## <a href="" id="bkmk-4"></a>Operating-system components
|
||||
|
||||
|
||||
USMT migrates operating-system components to a destination computer from computers running Windows 7 and Windows 8
|
||||
@ -151,7 +154,7 @@ Some settings, such as fonts, are not applied by the LoadState tool until after
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-2"></a>Supported Applications
|
||||
## <a href="" id="bkmk-2"></a>Supported applications
|
||||
|
||||
|
||||
Although it is not required for all applications, it is good practice to install all applications on the destination computer before restoring the user state. Installing applications before migrating settings helps to ensure that the migrated settings are not overwritten by the application installers.
|
||||
@ -361,12 +364,12 @@ When you specify the MigApp.xml file, USMT migrates the settings for the followi
|
||||
|
||||
|
||||
|
||||
## <a href="" id="no"></a>What USMT Does Not Migrate
|
||||
## <a href="" id="no"></a>What USMT does not migrate
|
||||
|
||||
|
||||
The following is a list of the settings that USMT does not migrate. If you are having a problem that is not listed here, see [Common Issues](usmt-common-issues.md).
|
||||
|
||||
### Application Settings
|
||||
### Application settings
|
||||
|
||||
USMT does not migrate the following application settings:
|
||||
|
||||
@ -382,7 +385,7 @@ USMT does not migrate the following application settings:
|
||||
|
||||
- You attempt to migrate from a 32-bit computer to a 64-bit computer. This is because the ICQ Pro default installation directory is different on the two types of computers. When you install ICQ Pro on a 32-bit computer, the default location is "C:\\Program Files\\...". The ICQ Pro default installation directory on an x64-based computer, however, is “C:\\Program Files (x86)\\...”.
|
||||
|
||||
### Operating-System Settings
|
||||
### Operating-System settings
|
||||
|
||||
USMT does not migrate the following operating-system settings.
|
||||
|
||||
@ -402,10 +405,14 @@ You should also note the following:
|
||||
|
||||
- You can use the /**localonly** option to exclude the data from removable drives and network drives mapped on the source computer. For more information about what is excluded when you specify /**localonly**, see [ScanState Syntax](usmt-scanstate-syntax.md).
|
||||
|
||||
### Start menu layout
|
||||
|
||||
Starting in Windows 10, version 1607 the USMT does not migrate the Start menu layout. To migrate a user's Start menu, you must export and then import settings using the Windows PowerShell cmdlets **Export-StartLayout** and **Import-StartLayout**. For more information, see [USMT common issues](https://docs.microsoft.com/windows/deployment/usmt/usmt-common-issues#usmt-does-not-migrate-the-start-layout).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Plan Your Migration](usmt-plan-your-migration.md)
|
||||
[Plan your migration](usmt-plan-your-migration.md)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ms.mktglfcycl: deploy
|
||||
localizationpriority: high
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
ms.date: 08/23/2017
|
||||
ms.date: 09/05/2017
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
@ -15,6 +15,11 @@ author: greg-lindsay
|
||||
|
||||
This document describes how to configure virtual machines (VMs) to enable [Windows 10 Subscription Activation](windows-10-enterprise-subscription-activation.md) in a Windows Virtual Desktop Access (VDA) scenario. Windows VDA is a device or user-based licensing mechanism for managing access to virtual desktops.
|
||||
|
||||
Deployment instructions are provided for the following scenarios:
|
||||
1. [Active Directory-joined VMs](#active-directory-joined-vms)
|
||||
2. [Azure Active Directory-joined VMs](#azure-active-directory-joined-vms)
|
||||
3. [Azure Gallery VMs](#azure-gallery-vms)
|
||||
|
||||
## Requirements
|
||||
|
||||
- VMs must be running Windows 10 Pro, version 1703 (also known as the Creator's Update) or later.
|
||||
@ -64,7 +69,35 @@ For Azure AD-joined VMs, follow the same instructions (above) as for [Active Dir
|
||||
- In step 9, during setup with Windows Configuration Designer, under **Name**, type a name for the project that indicates it is not for Active Directory joined VMs, such as **Desktop Bulk Enrollment Token Pro GVLK**.
|
||||
- In step 12, during setup with Windows Configuration Designer, on the Account Management page, instead of enrolling in Active Directory, choose **Enroll in Azure AD**, click **Get Bulk Token**, sign in and add the bulk token using your organization's credentials.
|
||||
- In step 17, when entering the PackagePath, use the project name you entered in step 9 (ex: **Desktop Bulk Enrollment Token Pro GVLK.ppkg**)
|
||||
- When attempting to access the VM using remote desktop, you will need to create a custom RDP settings file as described below.
|
||||
- When attempting to access the VM using remote desktop, you will need to create a custom RDP settings file as described below in [Create custom RDP settings for Azure](#create-custom-rpd-settings-for-azure).
|
||||
|
||||
## Azure Gallery VMs
|
||||
|
||||
1. (Optional) To disable network level authentication, type the following at an elevated command prompt:
|
||||
|
||||
```
|
||||
REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v UserAuthentication /t REG_DWORD /d 0 /f
|
||||
```
|
||||
|
||||
2. At an elevated command prompt, type **sysdm.cpl** and press ENTER.
|
||||
3. On the Remote tab, choose **Allow remote connections to this computer** and then click **Select Users**.
|
||||
4. Click **Add**, type **Authenticated users**, and then click **OK** three times.
|
||||
(https://docs.microsoft.com/azure/virtual-machines/windows/prepare-for-upload-vhd-image#steps-to-generalize-a-vhd).
|
||||
5. [Install Windows Configuration Designer](/windows/configuration/provisioning-packages/provisioning-install-icd).
|
||||
6. Open Windows Configuration Designer and click **Provison desktop services**.
|
||||
7. Under **Name**, type **Desktop Bulk Enrollment Token Pro GVLK**, click **Finish**, and then on the **Set up device** page enter a device name.
|
||||
- Note: You can use a different project name, but this name is also used with dism.exe in a subsequent step.
|
||||
8. Under **Enter product key** type the Pro GVLK key: **W269N-WFGWX-YVC9B-4J6C9-T83GX**.
|
||||
9. On the Set up network page, choose **Off**.
|
||||
10. On the Account Management page, choose **Enroll in Azure AD**, click **Get Bulk Token**, sign in, and add the bulk token using your organizations credentials.
|
||||
11. On the Add applications page, add applications if desired. This step is optional.
|
||||
12. On the Add certificates page, add certificates if desired. This step is optional.
|
||||
13. On the Finish page, click **Create**.
|
||||
14. Copy the .ppkg file to the remote Virtual machine. Double click to initiate the provisioning package install. This will reboot the system.
|
||||
|
||||
- When attempting to access the VM using remote desktop, you will need to create a custom RDP settings file as described [below](#create-custom-rpd-settings-for-azure).
|
||||
|
||||
## Create custom RDP settings for Azure
|
||||
|
||||
To create custom RDP settings for Azure:
|
||||
|
||||
|
||||
@ -18,7 +18,7 @@ ms.date: 06/30/2017
|
||||
|
||||
- Windows 10
|
||||
|
||||
Windows AutoPilot is a collection of technologies used to setup and pre-configure new devices, getting them ready for productive use. In addition, you can use Windows AutoPilot to reset, repurpose and recover devices.</br>
|
||||
Windows AutoPilot is a collection of technologies used to set up and pre-configure new devices, getting them ready for productive use. In addition, you can use Windows AutoPilot to reset, repurpose and recover devices.</br>
|
||||
This solution enables an IT department to achieve the above with little to no infrastructure to manage, with a process that's easy and simple.
|
||||
|
||||
## Benefits of Windows AutoPilot
|
||||
|
||||
@ -102,7 +102,7 @@ changepk.exe /ProductKey %ProductKey%
|
||||
### Obtaining an Azure AD licence
|
||||
|
||||
Enterprise Agreement/Software Assurance (EA/SA):
|
||||
- Organizations with a traditional EA must order a $0 SKU, process e-mails sent to the license administrator for the company, and assign licenses using Azure AD (ideally to groups using the new Azure AD Premium feature for group assignment).
|
||||
- Organizations with a traditional EA must order a $0 SKU, process e-mails sent to the license administrator for the company, and assign licenses using Azure AD (ideally to groups using the new Azure AD Premium feature for group assignment). For more information, see [Enabling Subscription Activation with an existing EA](https://docs.microsoft.com/en-us/windows/deployment/deploy-enterprise-licenses#enabling-subscription-activation-with-an-existing-ea).
|
||||
- The license administrator can assign seats to Azure AD users with the same process that is used for O365.
|
||||
- New EA/SA Windows Enterprise customers can acquire both an SA subscription and an associated $0 cloud subscription.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user