mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 10:53:43 +00:00
Merge remote-tracking branch 'refs/remotes/origin/rs1' into jdprov
This commit is contained in:
jdeckerMS
@ -1,5 +1,4 @@
|
||||
# [Deploy Windows 10](index.md)
|
||||
## [Change history for Deploy Windows 10](change-history-for-deploy-windows-10.md)
|
||||
## [Windows 10 deployment scenarios](windows-10-deployment-scenarios.md)
|
||||
## [Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md)
|
||||
### [Get started with the Microsoft Deployment Toolkit (MDT)](get-started-with-the-microsoft-deployment-toolkit.md)
|
||||
@ -35,10 +34,13 @@
|
||||
### [Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
## [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md)
|
||||
## [Upgrade to Windows 10 with System Center Configuration Manager](upgrade-to-windows-10-with-system-center-configuraton-manager.md)
|
||||
## [Configure a PXE server to load Windows PE](configure-a-pxe-server-to-load-windows-pe.md)
|
||||
## [Windows 10 edition upgrade](windows-10-edition-upgrades.md)
|
||||
## [Provision PCs with common settings for initial deployment](provision-pcs-for-initial-deployment.md)
|
||||
## [Provision PCs with apps and certificates for initial deployments](provision-pcs-with-apps-and-certificates.md)
|
||||
## [Deploy Windows To Go in your organization](deploy-windows-to-go.md)
|
||||
## [Update Windows 10 images with provisioning packages](update-windows-10-images-with-provisioning-packages.md)
|
||||
## [Upgrade a Windows Phone 8.1 to Windows 10 Mobile with Mobile Device Management](upgrade-windows-phone-8-1-to-10.md)
|
||||
## [Sideload apps in Windows 10](sideload-apps-in-windows-10.md)
|
||||
## [Volume Activation [client]](volume-activation-windows-10.md)
|
||||
### [Plan for volume activation [client]](plan-for-volume-activation-client.md)
|
||||
@ -134,4 +136,4 @@
|
||||
###### [Recognized Environment Variables](usmt-recognized-environment-variables.md)
|
||||
###### [XML Elements Library](usmt-xml-elements-library.md)
|
||||
##### [Offline Migration Reference](offline-migration-reference.md)
|
||||
|
||||
## [Change history for Deploy Windows 10](change-history-for-deploy-windows-10.md)
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Activate by Proxy an Active Directory Forest (Windows 10)
|
||||
description: Activate by Proxy an Active Directory Forest
|
||||
ms.assetid: 6475fc87-a6f7-4fa8-b0aa-de19f2dea7e5
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Activate an Active Directory Forest Online (Windows 10)
|
||||
description: Activate an Active Directory Forest Online
|
||||
ms.assetid: 9b5bc193-799b-4aa5-9d3e-0e495f7195d3
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -3,11 +3,11 @@ title: Activate using Active Directory-based activation (Windows 10)
|
||||
description: Active Directory-based activation is implemented as a role service that relies on AD DS to store activation objects.
|
||||
ms.assetid: 08cce6b7-7b5b-42cf-b100-66c363a846af
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Activate using Active Directory-based activation
|
||||
|
||||
@ -3,7 +3,7 @@ title: Activate using Key Management Service (Windows 10)
|
||||
ms.assetid: f2417bfe-7d25-4e82-bc07-de316caa8dac
|
||||
description:
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -3,7 +3,7 @@ title: Activate clients running Windows 10 (Windows 10)
|
||||
description: After you have configured Key Management Service (KMS) or Active Directory-based activation on your network, activating a client running Windows 10 is easy.
|
||||
ms.assetid: 39446e49-ad7c-48dc-9f18-f85a11ded643
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -2,11 +2,11 @@
|
||||
title: Active Directory-Based Activation Overview (Windows 10)
|
||||
description: Active Directory-Based Activation Overview
|
||||
ms.assetid: c1dac3bd-6a86-4c45-83dd-421e63a398c0
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Active Directory-Based Activation Overview
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
title: Add a Windows 10 operating system image using Configuration Manager (Windows 10)
|
||||
description: Operating system images are typically the production image used for deployment throughout the organization.
|
||||
ms.assetid: 77f769cc-1a47-4f36-8082-201cd77b8d3b
|
||||
keywords: ["image, deploy, distribute"]
|
||||
ms.prod: W10
|
||||
keywords: image, deploy, distribute
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: mtniehaus
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
title: Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager (Windows 10)
|
||||
description: In this topic, you will learn how to configure the Windows Preinstallation Environment (Windows PE) to include the network drivers required to connect to the deployment share and the storage drivers required to see the local storage on machines.
|
||||
ms.assetid: 97b3ea46-28d9-407e-8c42-ded2e45e8d5c
|
||||
keywords: ["deploy, task sequence"]
|
||||
ms.prod: W10
|
||||
keywords: deploy, task sequence
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: mtniehaus
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Add and Manage Products (Windows 10)
|
||||
description: Add and Manage Products
|
||||
ms.assetid: a48fbc23-917d-40f7-985c-e49702c05e51
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Add and Remove Computers (Windows 10)
|
||||
description: Add and Remove Computers
|
||||
ms.assetid: cb6f3a78-ece0-4dc7-b086-cb003d82cd52
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: jdeckerMS
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Add and Remove a Product Key (Windows 10)
|
||||
description: Add and Remove a Product Key
|
||||
ms.assetid: feac32bb-fb96-4802-81b8-c69220dcfcce
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -3,7 +3,7 @@ title: Appendix Information sent to Microsoft during activation (Windows 10)
|
||||
ms.assetid: 4bfff495-07d0-4385-86e3-7a077cbd64b8
|
||||
description:
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -3,7 +3,7 @@ title: Assign applications using roles in MDT (Windows 10)
|
||||
description: This topic will show you how to add applications to a role in the MDT database and then assign that role to a computer.
|
||||
ms.assetid: d82902e4-de9c-4bc4-afe0-41d649b83ce7
|
||||
keywords: settings, database, deploy
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
@ -3,7 +3,7 @@ title: Build a distributed environment for Windows 10 deployment (Windows 10)
|
||||
description: In this topic, you will learn how to replicate your Windows 10 deployment shares to facilitate the deployment of Windows 10 in remote or branch locations.
|
||||
ms.assetid: a6cd5657-6a16-4fff-bfb4-44760902d00c
|
||||
keywords: replication, replicate, deploy, configure, remote
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
@ -2,15 +2,25 @@
|
||||
title: Change history for Deploy Windows 10 (Windows 10)
|
||||
description: This topic lists new and updated topics in the Deploy Windows 10 documentation for Windows 10 and Windows 10 Mobile.
|
||||
ms.assetid: 19C50373-6B25-4F5C-A6EF-643D36904349
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Change history for Deploy Windows 10
|
||||
This topic lists new and updated topics in the [Deploy Windows 10](index.md) documentation for [Windows 10 and Windows 10 Mobile](../index.md).
|
||||
|
||||
## June 2016
|
||||
| New or changed topic | Description |
|
||||
|----------------------|-------------|
|
||||
| [Configure a PXE server to load Windows PE](configure-a-pxe-server-to-load-windows-pe.md) | New |
|
||||
|
||||
## May 2016
|
||||
| New or changed topic | Description |
|
||||
|----------------------|-------------|
|
||||
| [Upgrade a Windows Phone 8.1 to Windows 10 Mobile with Mobile Device Management](upgrade-windows-phone-8-1-to-10.md) | New |
|
||||
|
||||
## December 2015
|
||||
| New or changed topic | Description |
|
||||
|----------------------|-------------|
|
||||
|
||||
168
windows/deploy/configure-a-pxe-server-to-load-windows-pe.md
Normal file
168
windows/deploy/configure-a-pxe-server-to-load-windows-pe.md
Normal file
@ -0,0 +1,168 @@
|
||||
---
|
||||
title: Configure a PXE server to load Windows PE (Windows 10)
|
||||
description: This topic describes how to configure a PXE server to load Windows PE so that it can be used with an image file to install Windows 10 from the network.
|
||||
keywords: upgrade, update, windows, windows 10, pxe, WinPE, image, wim
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Configure a PXE server to load Windows PE
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
## Summary
|
||||
|
||||
This walkthrough describes how to configure a PXE server to load Windows PE by booting a client computer from the network. Using the Windows PE tools and a Windows 10 image file, you can install Windows 10 from the network.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- A deployment computer: A computer with the [Windows Assessment and Deployment Kit](https://www.microsoft.com/en-us/download/details.aspx?id=39982) (Windows ADK) installed.
|
||||
- A DHCP server: A DHCP server or DHCP proxy configured to respond to PXE client requests is required.
|
||||
- A PXE server: A server running the TFTP service that can host Windows PE boot files that the client will download.
|
||||
- A file server: A server hosting a network file share.
|
||||
|
||||
All four of the roles specified above can be hosted on the same computer or each can be on a separate computer.
|
||||
|
||||
## Step 1: Copy Windows PE source files
|
||||
|
||||
1. On the deployment computer, click **Start**, and type **deployment**.
|
||||
|
||||
2. Right-click **Deployment and Imaging Tools Environment** and then click **Run as administrator**. The Deployment and Imaging Tools Environment shortcut opens a Command Prompt window and automatically sets environment variables to point to all the necessary tools.
|
||||
|
||||
3. Run the following command to copy the base Windows PE files into a new folder. The script requires two arguments: hardware architecture and destination location. The value of **<architecture>** can be **x86**, **amd64**, or **arm** and **<destination>** is a path to a local directory. If the directory does not already exist, it will be created.
|
||||
|
||||
```
|
||||
copype.cmd <architecture> <destination>
|
||||
```
|
||||
|
||||
For example, the following command copies **amd64** architecture files to the **C:\winpe_amd64** directory:
|
||||
|
||||
```
|
||||
copype.cmd amd64 C:\winpe_amd64
|
||||
```
|
||||
|
||||
The script creates the destination directory structure and copies all the necessary files for that architecture. In the previous example, the following directories are created:
|
||||
|
||||
```
|
||||
C:\winpe\_amd64
|
||||
C:\winpe\_amd64\fwfiles
|
||||
C:\winpe\_amd64\media
|
||||
C:\winpe\_amd64\mount
|
||||
```
|
||||
4. Mount the base Windows PE image (winpe.wim) to the \mount directory using the DISM tool. Mounting an image file unpacks the file contents into a folder so that you can make changes directly or by using tools such as DISM. See the following example.
|
||||
|
||||
```
|
||||
Dism /mount-image /imagefile:c:\winpe_amd64\media\sources\boot.wim /index:1 /mountdir:C:\winpe_amd64\mount
|
||||
```
|
||||
5. Map a network share to the root TFTP directory on the PXE/TFTP server and create a \Boot folder. Consult your TFTP server documentation to determine the root TFTP server directory, then enable sharing for this directory, and verify it can be accessed on the network. In the following example, the PXE server name is PXE-1 and the TFTP root directory is shared using a network path of \\PXE-1\TFTPRoot:
|
||||
|
||||
```
|
||||
net use y: \\PXE-1\TFTPRoot
|
||||
y:
|
||||
md boot
|
||||
```
|
||||
6. Copy the PXE boot files from the mounted directory to the \Boot folder. For example:
|
||||
|
||||
```
|
||||
copy c:\winpe_amd64\mount\windows\boot\pxe\*.* y:\boot
|
||||
```
|
||||
7. Copy the boot.sdi file to the PXE/TFTP server.
|
||||
|
||||
```
|
||||
copy C:\winpe_amd64\media\boot\boot.sdi y:\boot
|
||||
```
|
||||
8. Copy the bootable Windows PE image (boot.wim) to the \Boot folder.
|
||||
|
||||
```
|
||||
copy C:\winpe_amd64\media\sources\boot.wim y:\boot
|
||||
```
|
||||
|
||||
## Step 2: Configure boot settings and copy the BCD file
|
||||
|
||||
1. Create a BCD store using bcdedit.exe:
|
||||
|
||||
```
|
||||
bcdedit /createstore c:\BCD
|
||||
```
|
||||
2. Configure RAMDISK settings:
|
||||
|
||||
```
|
||||
bcdedit /store c:\BCD /create {ramdiskoptions} /d "Ramdisk options"
|
||||
bcdedit /store c:\BCD /set {ramdiskoptions} ramdisksdidevice partition=C:
|
||||
bcdedit /store c:\BCD /set {ramdiskoptions} ramdisksdipath \winpe_amd64\media\boot\boot.sdi
|
||||
```
|
||||
3. Create a new boot application entry for the Windows PE image:
|
||||
|
||||
```
|
||||
bcdedit /store c:\BCD /set {GUID1} device ramdisk=[c:]\winpe_amd64\media\sources\boot.wim,{ramdiskoptions}
|
||||
bcdedit /store c:\BCD /set {GUID1} path \windows\system32\winload.exe
|
||||
bcdedit /store c:\BCD /set {GUID1} osdevice ramdisk=[c:]\winpe_amd64\media\sources\boot.wim,{ramdiskoptions}
|
||||
bcdedit /store c:\BCD /set {GUID1} systemroot \windows
|
||||
bcdedit /store c:\BCD /set {GUID1} detecthal Yes
|
||||
bcdedit /store c:\BCD /set {GUID1} winpe Yes
|
||||
```
|
||||
4. Configure BOOTMGR settings:
|
||||
|
||||
```
|
||||
bcdedit /store c:\BCD /set {bootmgr} timeout 30
|
||||
bcdedit /store c:\BCD -displayorder {GUID1} -addlast
|
||||
```
|
||||
5. Copy the BCD file to your TFTP server:
|
||||
|
||||
```
|
||||
copy c:\BCD \\PXE-1\TFTPRoot\Boot
|
||||
```
|
||||
|
||||
Your PXE/TFTP server is now configured. You can view the BCD settings that have been configured using the command bcdedit /store <BCD file location> /enum all. See the following example. Note: Your GUID will be different than the one shown below.
|
||||
|
||||
```
|
||||
C:\>bcdedit /store C:\BCD /enum all
|
||||
Windows Boot Manager
|
||||
--------------------
|
||||
identifier {bootmgr}
|
||||
description boot manager
|
||||
displayorder {a4f89c62-2142-11e6-80b6-00155da04110}
|
||||
timeout 30
|
||||
|
||||
Windows Boot Loader
|
||||
-------------------
|
||||
identifier {a4f89c62-2142-11e6-80b6-00155da04110}
|
||||
device ramdisk=[boot]\boot\boot.wim,{ramdiskoptions}
|
||||
description winpe boot image
|
||||
osdevice ramdisk=[boot]\boot\boot.wim,{ramdiskoptions}
|
||||
systemroot \Windows
|
||||
detecthal Yes
|
||||
winpe Yes
|
||||
|
||||
Setup Ramdisk Options
|
||||
---------------------
|
||||
identifier {ramdiskoptions}
|
||||
description ramdisk options
|
||||
ramdisksdidevice boot
|
||||
ramdisksdipath \boot\boot.sdi
|
||||
```
|
||||
|
||||
## PXE boot process summary
|
||||
|
||||
The following summarizes the PXE client boot process.
|
||||
|
||||
1. A client is directed by DHCP options 066 and 067 to download boot\\wdsnbp.com from the TFTP server.
|
||||
2. Wdsnbp.com validates the DHCP/PXE response packet and then the client downloads boot\\pxeboot.com.
|
||||
3. Pxeboot.com requires the client to press the F12 key to initiate a PXE boot.
|
||||
4. The client downloads boot\\bootmgr.exe and the boot\\BCD file from the TFTP server. Note: The BCD store must reside in the \\boot directory on the TFTP server and must be named BCD.
|
||||
5. Bootmgr.exe reads the BCD operating system entries and downloads boot\\boot.sdi and the Windows PE image (boot\\boot.wim). Optional files that can also be downloaded include true type fonts (boot\\Fonts\\wgl4\_boot.ttf) and the hibernation state file (\\hiberfil.sys) if these files are present.
|
||||
6. Bootmgr.exe starts Windows PE by calling winload.exe within the Windows PE image.
|
||||
7. Windows PE loads, a command prompt opens and wpeinit.exe is run to initialize Windows PE.
|
||||
8. The Windows PE client provides access to tools like imagex, diskpart, and bcdboot using the Windows PE command prompt. Using these tools together with a Windows 10 image file, the destination computer can be formatted properly to load a full Windows 10 operating system.
|
||||
|
||||
See Also
|
||||
---------
|
||||
|
||||
#### Concepts
|
||||
|
||||
[Windows PE Walkthroughs](https://technet.microsoft.com/en-us/library/cc748899.aspx)
|
||||
@ -2,7 +2,7 @@
|
||||
title: Configure Client Computers (Windows 10)
|
||||
description: Configure Client Computers
|
||||
ms.assetid: a48176c9-b05c-4dd5-a9ef-83073e2370fc
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -3,7 +3,7 @@ title: Configure MDT for UserExit scripts (Windows 10)
|
||||
description: In this topic, you will learn how to configure the MDT rules engine to use a UserExit script to generate computer names based on a prefix and the computer MAC Address.
|
||||
ms.assetid: 29a421d1-12d2-414e-86dc-25b62f5238a7
|
||||
keywords: rules, script
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
@ -3,7 +3,7 @@ title: Configure MDT settings (Windows 10)
|
||||
description: One of the most powerful features in Microsoft Deployment Toolkit (MDT) 2013 is its extension capabilities; there is virtually no limitation to what you can do in terms of customization.
|
||||
ms.assetid: d3e1280c-3d1b-4fad-8ac4-b65dc711f122
|
||||
keywords: customize, customization, deploy, features, tools
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
@ -3,7 +3,7 @@ title: Configure MDT deployment share rules (Windows 10)
|
||||
description: In this topic, you will learn how to configure the MDT rules engine to reach out to other resources, including external scripts, databases, and web services, for additional information instead of storing settings directly in the rules engine.
|
||||
ms.assetid: b5ce2360-33cc-4b14-b291-16f75797391b
|
||||
keywords: rules, configuration, automate, deploy
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
title: Create a custom Windows PE boot image with Configuration Manager (Windows 10)
|
||||
description: In Microsoft System Center 2012 R2 Configuration Manager, you can create custom Windows Preinstallation Environment (Windows PE) boot images that include extra components and features.
|
||||
ms.assetid: b9e96974-324d-4fa4-b0ce-33cfc49c4809
|
||||
keywords: ["tool, customize, deploy, boot image"]
|
||||
ms.prod: W10
|
||||
keywords: tool, customize, deploy, boot image
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: mtniehaus
|
||||
|
||||
@ -2,9 +2,10 @@
|
||||
title: Create a task sequence with Configuration Manager and MDT (Windows 10)
|
||||
description: In this topic, you will learn how to create a Microsoft System Center 2012 R2 Configuration Manager task sequence with Microsoft Deployment Toolkit (MDT) integration using the MDT wizard.
|
||||
ms.assetid: 0b069bec-5be8-47c6-bf64-7a630f41ac98
|
||||
keywords: ["deploy, upgrade, task sequence, install"]
|
||||
ms.prod: W10
|
||||
keywords: deploy, upgrade, task sequence, install
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.pagetype: mdt
|
||||
ms.sitesec: library
|
||||
author: mtniehaus
|
||||
---
|
||||
|
||||
@ -3,7 +3,7 @@ title: Create a Windows 10 reference image (Windows 10)
|
||||
description: Creating a reference image is important because that image serves as the foundation for the devices in your organization.
|
||||
ms.assetid: 9da2fb57-f2ff-4fce-a858-4ae4c237b5aa
|
||||
keywords: deploy, deployment, configure, customize, install, installation
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
title: Create an application to deploy with Windows 10 using Configuration Manager (Windows 10)
|
||||
description: Microsoft System Center 2012 R2 Configuration Manager supports deploying applications as part of the Windows 10 deployment process.
|
||||
ms.assetid: 2dfb2f39-1597-4999-b4ec-b063e8a8c90c
|
||||
keywords: ["deployment, task sequence, custom, customize"]
|
||||
ms.prod: W10
|
||||
keywords: deployment, task sequence, custom, customize
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: mtniehaus
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
title: Deploy a Windows 10 image using MDT 2013 Update 2 (Windows 10)
|
||||
description: This topic will show you how to take your reference image for Windows 10, and deploy that image to your environment using the Microsoft Deployment Toolkit (MDT), and MDT 2013 Update 2 specifically.
|
||||
ms.assetid: 1d70a3d8-1b1d-4051-b656-c0393a93f83c
|
||||
keywords: [eployment, automate, tools, configure
|
||||
ms.prod: W10
|
||||
keywords: deployment, automate, tools, configure
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
title: Deploy Windows 10 using PXE and Configuration Manager (Windows 10)
|
||||
description: In this topic, you will learn how to deploy Windows 10 using Microsoft System Center 2012 R2 Configuration Manager deployment packages and task sequences.
|
||||
ms.assetid: fb93f514-5b30-4f4b-99dc-58e6860009fa
|
||||
keywords: ["deployment, image, UEFI, task sequence"]
|
||||
ms.prod: W10
|
||||
keywords: deployment, image, UEFI, task sequence
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: mtniehaus
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
title: Deploy Windows 10 with System Center 2012 R2 Configuration Manager (Windows 10)
|
||||
description: If you have Microsoft System Center 2012 R2 Configuration Manager in your environment, you will most likely want to use it to deploy Windows 10.
|
||||
ms.assetid: eacd7b7b-dde0-423d-97cd-29bde9e8b363
|
||||
keywords: ["deployment, custom, boot"]
|
||||
ms.prod: W10
|
||||
keywords: deployment, custom, boot
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: mtniehaus
|
||||
|
||||
@ -3,7 +3,7 @@ title: Deploy Windows 10 with the Microsoft Deployment Toolkit (Windows 10)
|
||||
description: This guide will walk you through the process of deploying Windows 10 in an enterprise environment using the Microsoft Deployment Toolkit (MDT), and MDT 2013 Update 2 specifically.
|
||||
ms.assetid: 837f009c-617e-4b3f-9028-2246067ee0fb
|
||||
keywords: deploy, tools, configure, script
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: mtniehaus
|
||||
|
||||
@ -2,10 +2,11 @@
|
||||
title: Deploy Windows To Go in your organization (Windows 10)
|
||||
description: This topic helps you to deploy Windows To Go in your organization.
|
||||
ms.assetid: cfe550be-ffbd-42d1-ab4d-80efae49b07f
|
||||
keywords: ["deployment, USB, device, BitLocker, workspace, security, data"]
|
||||
ms.prod: W10
|
||||
keywords: deployment, USB, device, BitLocker, workspace, security, data
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mobility
|
||||
author: mtniehaus
|
||||
---
|
||||
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
title: Finalize the operating system configuration for Windows 10 deployment with Configuration Manager (Windows 10)
|
||||
description: This topic walks you through the steps to finalize the configuration of your Windows 10 operating deployment, which includes enablement of the optional Microsoft Deployment Toolkit (MDT) monitoring for Microsoft System Center 2012 R2 Configuration Manager, logs folder creation, rules configuration, content distribution, and deployment of the previously created task sequence.
|
||||
ms.assetid: 38b55fa8-e717-4689-bd43-8348751d493e
|
||||
keywords: ["configure, deploy, upgrade"]
|
||||
ms.prod: W10
|
||||
keywords: configure, deploy, upgrade
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: mtniehaus
|
||||
|
||||
@ -3,7 +3,7 @@ title: Get started with the Microsoft Deployment Toolkit (MDT) (Windows 10)
|
||||
description: This topic will help you gain a better understanding of how to use the Microsoft Deployment Toolkit (MDT), and MDT 2013 Update 2 in particular, as part of a Windows operating system deployment.
|
||||
ms.assetid: a256442c-be47-4bb9-a105-c831f58ce3ee
|
||||
keywords: deploy, image, feature, install, tools
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Getting Started with the User State Migration Tool (USMT) (Windows 10)
|
||||
description: Getting Started with the User State Migration Tool (USMT)
|
||||
ms.assetid: 506ff1d2-94b8-4460-8672-56aad963504b
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Getting Started with the User State Migration Tool (USMT)
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Import and Export VAMT Data (Windows 10)
|
||||
description: Import and Export VAMT Data
|
||||
ms.assetid: 09a2c595-1a61-4da6-bd46-4ba8763cfd4f
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Deploy Windows 10 (Windows 10)
|
||||
description: Learn about deploying Windows 10 for IT professionals.
|
||||
ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Deploy Windows 10
|
||||
@ -15,21 +15,22 @@ Learn about deploying Windows 10 for IT professionals.
|
||||
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Change history for Deploy Windows 10](change-history-for-deploy-windows-10.md) |This topic lists new and updated topics in the Deploy Windows 10 documentation for [Windows 10 and Windows 10 Mobile](../index.md). |
|
||||
|[Windows 10 deployment scenarios](windows-10-deployment-scenarios.md) |To successfully deploy the Windows 10 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the key capabilities and limitations of each, is a key task. |
|
||||
|[Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md) |This guide will walk you through the process of deploying Windows 10 in an enterprise environment using the Microsoft Deployment Toolkit (MDT), and MDT 2013 Update 2 specifically. |
|
||||
|[Deploy Windows 10 with System Center 2012 R2 Configuration Manager](deploy-windows-10-with-system-center-2012-r2-configuration-manager.md) |If you have Microsoft System Center 2012 R2 Configuration Manager in your environment, you will most likely want to use it to deploy Windows 10. This topic will show you how to set up Configuration Manager for operating system deployment and how to integrate Configuration Manager with the Microsoft Deployment Toolkit (MDT) or, more specifically, MDT 2013 Update 2. |
|
||||
|[Upgrade to Windows 10 with the Microsoft Deployment Toolkit](upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md) |The simplest path to upgrade PCs that are currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. You can use a Microsoft Deployment Toolkit (MDT) 2013 Update 2 task sequence to completely automate the process. |
|
||||
|[Upgrade to Windows 10 with System Center Configuration Manager](upgrade-to-windows-10-with-system-center-configuraton-manager.md) |The simplest path to upgrade PCs currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. You can use a System Center Configuration Manager task sequence to completely automate the process. |
|
||||
|[Configure a PXE server to load Windows PE](configure-a-pxe-server-to-load-windows-pe.md) |This guide describes how to configure a PXE server to load Windows PE by booting a client computer from the network. |
|
||||
|[Windows 10 edition upgrade](windows-10-edition-upgrades.md) |With Windows 10, you can quickly upgrade from one edition of Windows 10 to another, provided the upgrade path is supported. |
|
||||
| [Provision PCs with common settings for initial deployment](provision-pcs-for-initial-deployment.md) | Create a provisioning package to apply commonly used settings to a PC running Windows 10. |
|
||||
| [Provision PCs with apps and certificates for initial deployments](provision-pcs-with-apps-and-certificates.md) | Create a provisioning package to add apps and certificates to a PC running Windows 10. |
|
||||
|[Deploy Windows To Go in your organization](deploy-windows-to-go.md) |This topic helps you to deploy Windows To Go in your organization. Before you begin deployment, make sure that you have reviewed the topics [Windows To Go: feature overview](../plan/windows-to-go-overview.md) and [Prepare your organization for Windows To Go](../plan/prepare-your-organization-for-windows-to-go.md) to ensure that you have the correct hardware and are prepared to complete the deployment. You can then use the steps in this topic to start your Windows To Go deployment. |
|
||||
|
||||
|[Update Windows 10 images with provisioning packages](update-windows-10-images-with-provisioning-packages.md) |Use a provisioning package to apply settings, profiles, and file assets to a Windows 10 image. |
|
||||
|[Upgrade a Windows Phone 8.1 to Windows 10 Mobile with Mobile Device Management](upgrade-windows-phone-8-1-to-10.md) |This topic describes how to upgrade eligible Windows Phone 8.1 devices to Windows 10 Mobile. |
|
||||
|[Sideload apps in Windows 10](sideload-apps-in-windows-10.md) |Sideload line-of-business apps in Windows 10. |
|
||||
|[Volume Activation [client]](volume-activation-windows-10.md) |This guide is designed to help organizations that are planning to use volume activation to deploy and activate Windows 10, including organizations that have used volume activation for earlier versions of Windows. |
|
||||
|[Windows 10 deployment tools reference](windows-10-deployment-tools-reference.md) |Learn about the tools available to deploy Windows 10. |
|
||||
|
||||
|[Change history for Deploy Windows 10](change-history-for-deploy-windows-10.md) |This topic lists new and updated topics in the Deploy Windows 10 documentation for [Windows 10 and Windows 10 Mobile](../index.md). |
|
||||
## Related topics
|
||||
- [Windows 10 and Windows 10 Mobile](../index.md)
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Install and Configure VAMT (Windows 10)
|
||||
description: Install and Configure VAMT
|
||||
ms.assetid: 5c7ae9b9-0dbc-4277-bc4f-8b3e4ab0bf50
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Install a KMS Client Key (Windows 10)
|
||||
description: Install a KMS Client Key
|
||||
ms.assetid: d234468e-7917-4cf5-b0a8-4968454f7759
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Install a Product Key (Windows 10)
|
||||
description: Install a Product Key
|
||||
ms.assetid: 78812c87-2208-4f8b-9c2c-5a8a18b2d648
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Install VAMT (Windows 10)
|
||||
description: Install VAMT
|
||||
ms.assetid: 2eabd3e2-0a68-43a5-8189-2947e46482fc
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -4,7 +4,7 @@ description: This topic will help you understand the benefits of integrating the
|
||||
ms.assetid: 3bd1cf92-81e5-48dc-b874-0f5d9472e5a5
|
||||
ms.pagetype: mdt
|
||||
keywords: deploy, image, customize, task sequence
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: mtniehaus
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Introduction to VAMT (Windows 10)
|
||||
description: Introduction to VAMT
|
||||
ms.assetid: 0439685e-0bae-4967-b0d4-dd84ca6d7fa7
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -3,7 +3,7 @@ title: Key features in MDT 2013 Update 2 (Windows 10)
|
||||
description: The Microsoft Deployment Toolkit (MDT) has been in existence since 2003, when it was first introduced as Business Desktop Deployment (BDD) 1.0.
|
||||
ms.assetid: 858e384f-e9db-4a93-9a8b-101a503e4868
|
||||
keywords: deploy, feature, tools, upgrade, migrate, provisioning
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Perform KMS Activation (Windows 10)
|
||||
description: Perform KMS Activation
|
||||
ms.assetid: 5a3ae8e6-083e-4153-837e-ab0a225c1d10
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Perform Local Reactivation (Windows 10)
|
||||
description: Perform Local Reactivation
|
||||
ms.assetid: aacd5ded-da11-4d27-a866-3f57332f5dec
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Manage Activations (Windows 10)
|
||||
description: Manage Activations
|
||||
ms.assetid: 53bad9ed-9430-4f64-a8de-80613870862c
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Manage Product Keys (Windows 10)
|
||||
description: Manage Product Keys
|
||||
ms.assetid: 4c6c4216-b4b7-437c-904e-4cb257f913cd
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Manage VAMT Data (Windows 10)
|
||||
description: Manage VAMT Data
|
||||
ms.assetid: 233eefa4-3125-4965-a12d-297a67079dc4
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -3,7 +3,7 @@ title: MDT 2013 Update 2 Lite Touch components (Windows 10)
|
||||
description: This topic provides an overview of the features in the Microsoft Deployment Toolkit (MDT) 2013 Update 2 that support Lite Touch Installation (LTI) for Windows 10.
|
||||
ms.assetid: 7d6fc159-e338-439e-a2e6-1778d0da9089
|
||||
keywords: deploy, install, deployment, boot, log, monitor
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Migrate Application Settings (Windows 10)
|
||||
description: Migrate Application Settings
|
||||
ms.assetid: 28f70a83-0a3e-4a6b-968a-2b78ccd3cc07
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Migrate Application Settings
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Migration Store Types Overview (Windows 10)
|
||||
description: Migration Store Types Overview
|
||||
ms.assetid: 3b6ce746-76c6-43ff-8cd5-02ed0ae0cf70
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Migration Store Types Overview
|
||||
|
||||
@ -3,11 +3,11 @@ title: Monitor activation (Windows 10)
|
||||
ms.assetid: 264a3e86-c880-4be4-8828-bf4c839dfa26
|
||||
description:
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Monitor activation
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
title: Monitor the Windows 10 deployment with Configuration Manager (Windows 10)
|
||||
description: In this topic, you will learn how to monitor a Windows 10 deployment that was started previously using Microsoft System Center 2012 R2 Configuration Manager and the Microsoft Deployment Toolkit (MDT) Deployment Workbench.
|
||||
ms.assetid: 4863c6aa-6369-4171-8e1a-b052ca195fce
|
||||
keywords: ["deploy, upgrade"]
|
||||
ms.prod: W10
|
||||
keywords: deploy, upgrade
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: mtniehaus
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Offline Migration Reference (Windows 10)
|
||||
description: Offline Migration Reference
|
||||
ms.assetid: f347547c-d601-4c3e-8f2d-0138edeacfda
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Offline Migration Reference
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Perform Online Activation (Windows 10)
|
||||
description: Perform Online Activation
|
||||
ms.assetid: 8381792b-a454-4e66-9b4c-e6e4c9303823
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -3,7 +3,7 @@ title: Plan for volume activation (Windows 10)
|
||||
description: Product activation is the process of validating software with the manufacturer after it has been installed on a specific computer.
|
||||
ms.assetid: f84b005b-c362-4a70-a84e-4287c0d2e4ca
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -3,7 +3,7 @@ title: Prepare for deployment with MDT 2013 Update 2 (Windows 10)
|
||||
description: This topic will walk you through the steps necessary to create the server structure required to deploy the Windows 10 operating system using the Microsoft Deployment Toolkit (MDT) 2013 Update 2.
|
||||
ms.assetid: 5103c418-0c61-414b-b93c-a8e8207d1226
|
||||
keywords: deploy, system requirements
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
title: Prepare for Zero Touch Installation of Windows 10 with Configuration Manager (Windows 10)
|
||||
description: This topic will walk you through the process of integrating Microsoft System Center 2012 R2 Configuration Manager SP1 with Microsoft Deployment Toolkit (MDT) 2013 Update 2, as well as the other preparations needed to deploying Windows 10 via Zero Touch Installation. Additional preparations include the installation of hotfixes as well as activities that speed up the Pre-Boot Execution Environment (PXE).
|
||||
ms.assetid: 06e3a221-31ef-47a5-b4da-3b927cb50d08
|
||||
keywords: ["install, configure, deploy, deployment"]
|
||||
ms.prod: W10
|
||||
keywords: install, configure, deploy, deployment
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: mtniehaus
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Perform Proxy Activation (Windows 10)
|
||||
description: Perform Proxy Activation
|
||||
ms.assetid: 35a919ed-f1cc-4d10-9c88-9bd634549dc3
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
title: Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager (Windows 10)
|
||||
description: This topic will show you how to use a previously created task sequence to refresh a Windows 7 SP1 client with Windows 10 using Microsoft System Center 2012 R2 Configuration Manager and Microsoft Deployment Toolkit (MDT) 2013 Update 2.
|
||||
ms.assetid: 57c81667-1019-4711-b3de-15ae9c5387c7
|
||||
keywords: ["upgrade, install, installation, computer refresh"]
|
||||
ms.prod: W10
|
||||
keywords: upgrade, install, installation, computer refresh
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: mtniehaus
|
||||
|
||||
@ -3,7 +3,7 @@ title: Refresh a Windows 7 computer with Windows 10 (Windows 10)
|
||||
description: This topic will show you how to use MDT 2013 Update 2 Lite Touch Installation (LTI) to upgrade a Windows 7 computer to a Windows 10 computer using the computer refresh process.
|
||||
ms.assetid: 2866fb3c-4909-4c25-b083-6fc1f7869f6f
|
||||
keywords: reinstallation, customize, template, script, restore
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Remove Products (Windows 10)
|
||||
description: Remove Products
|
||||
ms.assetid: 4d44379e-dda1-4a8f-8ebf-395b6c0dad8e
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
title: Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager (Windows 10)
|
||||
description: In this topic, you will learn how to replacing a Windows 7 SP1 computer using Microsoft System Center 2012 R2 Configuration Manager.
|
||||
ms.assetid: 3c8a2d53-8f08-475f-923a-bca79ca8ac36
|
||||
keywords: ["upgrade, install, installation, replace computer, setup"]
|
||||
ms.prod: W10
|
||||
keywords: upgrade, install, installation, replace computer, setup
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: mtniehaus
|
||||
|
||||
@ -3,7 +3,7 @@ title: Replace a Windows 7 computer with a Windows 10 computer (Windows 10)
|
||||
description: A computer replace scenario for Windows 10 is quite similar to a computer refresh for Windows 10; however, because you are replacing a machine, you cannot store the backup on the old computer.
|
||||
ms.assetid: acf091c9-f8f4-4131-9845-625691c09a2a
|
||||
keywords: deploy, deployment, replace
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Scenario 3 KMS Client Activation (Windows 10)
|
||||
description: Scenario 3 KMS Client Activation
|
||||
ms.assetid: 72b04e8f-cd35-490c-91ab-27ea799b05d0
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Scenario 1 Online Activation (Windows 10)
|
||||
description: Scenario 1 Online Activation
|
||||
ms.assetid: 94dba40e-383a-41e4-b74b-9e884facdfd3
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Scenario 2 Proxy Activation (Windows 10)
|
||||
description: Scenario 2 Proxy Activation
|
||||
ms.assetid: ed5a8a56-d9aa-4895-918f-dd1898cb2c1a
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -3,7 +3,7 @@ title: Set up MDT for BitLocker (Windows 10)
|
||||
ms.assetid: 386e6713-5c20-4d2a-a220-a38d94671a38
|
||||
description:
|
||||
keywords: disk, encryption, TPM, configure, secure, script
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Sideload LOB apps in Windows 10 (Windows 10)
|
||||
description: Sideload line-of-business apps in Windows 10.
|
||||
ms.assetid: C46B27D0-375B-4F7A-800E-21595CF1D53D
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Sideload LOB apps in Windows 10
|
||||
|
||||
@ -3,7 +3,7 @@ title: Simulate a Windows 10 deployment in a test environment (Windows 10)
|
||||
description: This topic will walk you through the process of creating a simulated environment on which to test your Windows 10 deployment using MDT.
|
||||
ms.assetid: 2de86c55-ced9-4078-b280-35e0329aea9c
|
||||
keywords: deploy, script
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Understanding Migration XML Files (Windows 10)
|
||||
description: Understanding Migration XML Files
|
||||
ms.assetid: d3d1fe89-085c-4da8-9657-fd54b8bfc4b7
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Understanding Migration XML Files
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Update Product Status (Windows 10)
|
||||
description: Update Product Status
|
||||
ms.assetid: 39d4abd4-801a-4e8f-9b8c-425a24a96764
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -0,0 +1,123 @@
|
||||
---
|
||||
title: Update Windows 10 images with provisioning packages (Windows 10)
|
||||
description: Use a provisioning package to apply settings, profiles, and file assets to a Windows 10 image.
|
||||
ms.assetid: 3CA345D2-B60A-4860-A3BF-174713C3D3A6
|
||||
keywords: provisioning, bulk deployment, image
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Update Windows 10 images with provisioning packages
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
|
||||
Use a provisioning package to apply settings, profiles, and file assets to a Windows 10 image.
|
||||
|
||||
In Windows 10, you can apply a provisioning package at any time. A provisioning package can include management instructions and policies, installation of specific apps, customization of network connections and policies, and more.
|
||||
|
||||
You can include provisioning packages when you build a Windows image. This way, you can create a single provisioning package that you can add to different hardware-specific images.
|
||||
|
||||
You can also put a provisioning package on a USB drive or SD card to apply to off-the-shelf devices. You can even send the provisioning package to someone in email.
|
||||
|
||||
Rather than wiping a device and applying a new system image when you need to change configuration, you can reset the device to its original state and then apply a new provisioning package.
|
||||
|
||||
For details about the settings you can customize in provisioning packages, see [Windows Provisioning settings reference]( http://go.microsoft.com/fwlink/p/?LinkId=619012).
|
||||
|
||||
## Advantages
|
||||
- You can configure new devices without reimaging.
|
||||
|
||||
- Works on both mobile and desktop devices.
|
||||
|
||||
- No network connectivity required.
|
||||
|
||||
- Simple for people to apply.
|
||||
|
||||
- Ensure compliance and security before a device is enrolled in MDM.
|
||||
|
||||
## Create package
|
||||
Use the Windows Imaging and Configuration Designer (ICD) tool included in the Windows Assessment and Deployment Kit (ADK) for Windows 10 to create a runtime provisioning package. [Install the ADK.](http://go.microsoft.com/fwlink/p/?LinkId=526740)
|
||||
|
||||
1. Open Windows ICD (by default, `%windir%\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe`).
|
||||
|
||||
2. Choose **New provisioning package**.
|
||||
|
||||
3. Name your project, and click **Next**.
|
||||
|
||||
4. Choose **Common to all Windows editions** and click **Next**.
|
||||
|
||||
5. On **New project**, click **Finish**. The workspace for your package opens.
|
||||
|
||||
6. Configure settings. [Learn more about specific settings in provisioning packages.]( http://go.microsoft.com/fwlink/p/?LinkId=615916)
|
||||
|
||||
7. On the **File** menu, select **Save.**
|
||||
|
||||
8. On the **Export** menu, select **Provisioning package**.
|
||||
|
||||
9. Change **Owner** to **IT Admin**, which will set the precedence of this provisioning package higher than provisioning packages applied to this device from other sources, and then select **Next.**
|
||||
|
||||
10. Set a value for **Package Version**.
|
||||
|
||||
**Tip**
|
||||
You can make changes to existing packages and change the version number to update previously applied packages.
|
||||
|
||||
11. Optional. In the **Provisioning package security** window, you can choose to encrypt the package and enable package signing.
|
||||
|
||||
- **Enable package encryption** - If you select this option, an auto-generated password will be shown on the screen.
|
||||
|
||||
- **Enable package signing** - If you select this option, you must select a valid certificate to use for signing the package. You can specify the certificate by clicking **Select...** and choosing the certificate you want to use to sign the package.
|
||||
|
||||
**Important**
|
||||
We recommend that you include a trusted provisioning certificate in your provisioning package. When the package is applied to a device, the certificate is added to the system store and any package signed with that certificate thereafter can be applied silently.
|
||||
|
||||
12. Click **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location.<p>
|
||||
Optionally, you can click **Browse** to change the default output location.
|
||||
|
||||
13. Click **Next**.
|
||||
|
||||
14. Click **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status.<p>
|
||||
If you need to cancel the build, click **Cancel**. This cancels the current build process, closes the wizard, and takes you back to the **Customizations Page**.
|
||||
|
||||
15. If your build fails, an error message will show up that includes a link to the project folder. You can scan the logs to determine what caused the error. Once you fix the issue, try building the package again.<p>
|
||||
If your build is successful, the name of the provisioning package, output directory, and project directory will be shown.
|
||||
|
||||
- If you choose, you can build the provisioning package again and pick a different path for the output package. To do this, click **Back** to change the output package name and path, and then click **Next** to start another build.
|
||||
|
||||
- If you are done, click **Finish** to close the wizard and go back to the **Customizations Page**.
|
||||
|
||||
16. Select the **output location** link to go to the location of the package. You can provide that .ppkg to others through any of the following methods:
|
||||
|
||||
- Shared network folder
|
||||
|
||||
- SharePoint site
|
||||
|
||||
- Removable media (USB/SD)
|
||||
|
||||
- Email
|
||||
|
||||
- USB tether (mobile only)
|
||||
|
||||
- NFC (mobile only)
|
||||
|
||||
## Add package to image
|
||||
**To add a provisioning package to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education)**
|
||||
|
||||
- Follow the steps in the "To build an image for Windows 10 for desktop editions" section in [Use the Windows ICD command-line interface]( http://go.microsoft.com/fwlink/p/?LinkId=617371).
|
||||
|
||||
**To add a provisioning package to a Windows 10 Mobile image**
|
||||
|
||||
- Follow the steps in the "To build an image for Windows 10 Mobile or Windows 10 IoT Core (IoT Core)" section in [Use the Windows ICD command-line interface]( http://go.microsoft.com/fwlink/p/?LinkId=617371).<p>
|
||||
The provisioning package is placed in the FFU image and is flashed or sector written to the device. During device setup time, the provisioning engine starts and consumes the packages.
|
||||
|
||||
## Learn more
|
||||
- [Build and apply a provisioning package]( http://go.microsoft.com/fwlink/p/?LinkId=629651)
|
||||
|
||||
- [Provisioning Windows 10 Devices with New Tools](http://go.microsoft.com/fwlink/p/?LinkId=615921)
|
||||
|
||||
- [Windows 10 for Mobile Devices: Provisioning Is Not Imaging](http://go.microsoft.com/fwlink/p/?LinkId=615922)
|
||||
|
||||
## Related topics
|
||||
- [Configure devices without MDM](../manage/configure-devices-without-mdm.md)
|
||||
@ -2,8 +2,8 @@
|
||||
title: Upgrade to Windows 10 with System Center Configuration Manager (Windows 10)
|
||||
description: The simplest path to upgrade PCs currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. You can use a System Center Configuration Manager task sequence to completely automate the process.
|
||||
ms.assetid: F8DF6191-0DB0-4EF5-A9B1-6A11D5DE4878
|
||||
keywords: ["upgrade, update, task sequence, deploy"]
|
||||
ms.prod: W10
|
||||
keywords: upgrade, update, task sequence, deploy
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
author: mtniehaus
|
||||
---
|
||||
|
||||
@ -3,7 +3,7 @@ title: Upgrade to Windows 10 with the Microsoft Deployment Toolkit (Windows 10)
|
||||
description: The simplest path to upgrade PCs that are currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade.
|
||||
ms.assetid: B8993151-3C1E-4F22-93F4-2C5F2771A460
|
||||
keywords: upgrade, update, task sequence, deploy
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
102
windows/deploy/upgrade-windows-phone-8-1-to-10.md
Normal file
102
windows/deploy/upgrade-windows-phone-8-1-to-10.md
Normal file
@ -0,0 +1,102 @@
|
||||
---
|
||||
title: Upgrade Windows Phone 8.1 to Windows 10 Mobile in an MDM environment (Windows 10)
|
||||
description: This article describes how to upgrade eligible Windows Phone 8.1 devices to Windows 10 Mobile using MDM.
|
||||
keywords: upgrade, update, windows, phone, windows 10, mdm, mobile
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
author: Jamiejdt
|
||||
---
|
||||
|
||||
# Upgrade a Windows Phone 8.1 to Windows 10 Mobile with Mobile Device Management (MDM)
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10 Mobile
|
||||
|
||||
## Summary
|
||||
This article describes how to upgrade eligible Windows Phone 8.1 devices to Windows 10 Mobile using Mobile Device Management (MDM). To determine if the device is eligible for an upgrade, see the [How to determine whether an upgrade is available for a device](#howto-upgrade-available) topic in this article.
|
||||
|
||||
The Windows Phone 8.1 to Windows 10 Mobile upgrade uses an "opt-in" or "seeker" model. An eligible device must opt-in to be offered the upgrade. For consumers, the Windows 10 Mobile Upgrade Advisor app is available from the Windows Store to perform the opt-in. For Enterprises, Microsoft is offering a centralized management solution through MDM that can push a management policy to each eligible device to perform the opt-in.
|
||||
|
||||
If you use a list of allowed applications (app whitelisting) with MDM, verify that system applications are whitelisted before you upgrade to Windows 10 Mobile. Also, be aware that there are [known issues](https://msdn.microsoft.com/en-us/library/windows/hardware/mt299056.aspx#whitelist) with app whitelisting that could adversely affect the device after you upgrade.
|
||||
|
||||
Some enterprises might want to control the availability of the Windows 10 Mobile upgrade to their users. With the opt-in model, the enterprise can blacklist the Upgrade Advisor app to prevent their users from upgrading prematurely. For more information about how to blacklist the Upgrade Advisor app, see the [How to blacklist the Upgrade Advisor app](#howto-blacklist) section in this article. Enterprises that have blacklisted the Upgrade Advisor app can use the solution described in this article to select the upgrade timing on a per-device basis.
|
||||
|
||||
## More information
|
||||
|
||||
To provide enterprises with a solution that's independent of the Upgrade Advisor, a new registry key in the registry configuration service provider (CSP) is available. A special GUID key value is defined. When Microsoft Update (MU) detects the presence of the registry key value on a device, any available upgrade will be made available to the device.
|
||||
|
||||
### Prerequisites
|
||||
|
||||
- Windows Phone 8.1 device with an available upgrade to Windows 10 Mobile.
|
||||
- Device connected to Wi-Fi or cellular network to perform scan for upgrade.
|
||||
- Device is already enrolled with an MDM session.
|
||||
- Device is able to receive the management policy.
|
||||
- MDM is capable of pushing the management policy to devices. Minimum version numbers for some popular MDM providers that support this solution are: InTune: 5.0.5565, AirWatch: 8.2, Mobile Iron: 9.0.
|
||||
|
||||
### Instructions for the MDM server
|
||||
|
||||
The registry CSP is used to push the GUID value to the following registry key for which the Open Mobile Alliance (OMA) Device Management (DM) client has Read/Write access and for which the Device Update service has Read access.
|
||||
|
||||
```
|
||||
[HKLM\Software\Microsoft\Provisioning\OMADM]
|
||||
"EnterpriseUpgrade"="d369c9b6-2379-466d-9162-afc53361e3c2”
|
||||
```
|
||||
|
||||
|
||||
The complete SyncML command for the solution is as follows. Note: The SyncML may vary, depending on your MDM solution.
|
||||
|
||||
```
|
||||
SyncML xmlns="SYNCML:SYNCML1.1">
|
||||
<SyncBody>
|
||||
<Add>
|
||||
<CmdID>250</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Vendor/MSFT/Registry/HKLM/SOFTWARE/Microsoft/Provisioning/OMADM/EnterpriseUpgrade</LocURI>
|
||||
</Target>
|
||||
<Meta>
|
||||
<Format xmlns=”syncml:metinf”>chr</Format>
|
||||
</Meta>
|
||||
<Data>d369c9b6-2379-466d-9162-afc53361e3c2</Data>
|
||||
</Item>
|
||||
</Add>
|
||||
<Final/>
|
||||
</SyncBody>
|
||||
</SyncML>
|
||||
```
|
||||
|
||||
The OMA DM server policy description is provided in the following table:
|
||||
|
||||
|Item |Setting |
|
||||
|------|------------|
|
||||
| OMA-URI |./Vendor/MSFT/Registry/HKLM/SOFTWARE/Microsoft/Provisioning/OMADM/EnterpriseUpgrade |
|
||||
| Data Type |String |
|
||||
| Value |d369c9b6-2379-466d-9162-afc53361e3c2 |
|
||||
|
||||
|
||||
After the device consumes the policy, it will be able to receive an available upgrade.
|
||||
|
||||
To disable the policy, delete the **OMADM** registry key or set the **EnterpriseUpgrade** string value to anything other than the GUID.
|
||||
|
||||
### How to determine whether an upgrade is available for a device <a id="howto-upgrade-available"></a>
|
||||
|
||||
The Windows 10 Mobile Upgrade Advisor app is not designed or intended for Enterprise customers who want to automate the upgrade process. However, the Windows 10 Mobile Upgrade Advisor app is the best mechanism to determine when an upgrade is available. The app dynamically queries whether the upgrade is released for this device model and associated mobile operator (MO).
|
||||
|
||||
We recommend that enterprises use a pilot device with the Windows 10 Mobile Upgrade Advisor app installed. The pilot device provides the device model and MO used by the enterprise. When you run the app on the pilot device, it will tell you that either an upgrade is available, that the device is eligible for upgrade, or that an upgrade is not available for this device.
|
||||
|
||||
Note: The availability of Windows 10 Mobile as an update for existing Windows Phone 8.1 devices varies by device manufacturer, device model, country or region, mobile operator or service provider, hardware limitations, and other factors. To check for compatibility and other important installation information, see the [Windows 10 mobile](https://www.microsoft.com/en/mobile/windows10) page.
|
||||
|
||||
### How to blacklist the Upgrade Advisor app <a id="howto-blacklist"></a>
|
||||
|
||||
Some enterprises may want to block their users from installing the Windows 10 Mobile Upgrade Advisor app. With Windows Phone 8.1, you can allow or deny individual apps by adding specific app publishers or the app globally unique identifier (GUID) from the Window Phone Store to an allow or deny XML list. The GUID for a particular application can be found in the URL for the app in the phone store. For example, the GUID to the Windows 10 Mobile Upgrade Adviser (fbe47e4f-7769-4103-910e-dca8c43e0b07) is displayed in the following URL:
|
||||
|
||||
http://windowsphone.com/s?appid=fbe47e4f-7769-4103-910e-dca8c43e0b07
|
||||
|
||||
For more information about how to do this, see [Try it out: restrict Windows Phone 8.1 apps](https://technet.microsoft.com/en-us/windows/dn771706.aspx).
|
||||
|
||||
## Related topics
|
||||
|
||||
[Windows 10 Mobile and mobile device management](..\manage\windows-10-mobile-and-mdm.md)
|
||||
@ -3,7 +3,7 @@ title: Use Orchestrator runbooks with MDT (Windows 10)
|
||||
description: This topic will show you how to integrate Microsoft System Center 2012 R2 Orchestrator with MDT to replace the existing web services that are used in deployment solutions.
|
||||
ms.assetid: 68302780-1f6f-4a9c-9407-b14371fdce3f
|
||||
keywords: web services, database
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
|
||||
@ -4,7 +4,7 @@ description: This topic is designed to teach you how to use the MDT database to
|
||||
ms.assetid: 8956ab54-90ba-45d3-a384-4fdec72c4d46
|
||||
ms.pagetype: mdt
|
||||
keywords: database, permissions, settings, configure, deploy
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: mtniehaus
|
||||
|
||||
@ -3,7 +3,7 @@ title: Use the Volume Activation Management Tool (Windows 10)
|
||||
description: The Volume Activation Management Tool (VAMT) provides several useful features, including the ability to perform VAMT proxy activation and to track and monitor several types of product keys.
|
||||
ms.assetid: b11f0aee-7b60-44d1-be40-c960fc6c4c47
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Use VAMT in Windows PowerShell (Windows 10)
|
||||
description: Use VAMT in Windows PowerShell
|
||||
ms.assetid: 13e0ceec-d827-4681-a5c3-8704349e3ba9
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
|
||||
@ -3,7 +3,7 @@ title: Use web services in MDT (Windows 10)
|
||||
description: In this topic, you will learn how to create a simple web service that generates computer names and then configure MDT to use that service during your Windows 10 deployment.
|
||||
ms.assetid: 8f47535e-0551-4ccb-8f02-bb97539c6522
|
||||
keywords: deploy, web apps
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.pagetype: mdt
|
||||
ms.sitesec: library
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: USMT Best Practices (Windows 10)
|
||||
description: USMT Best Practices
|
||||
ms.assetid: e3cb1e78-4230-4eae-b179-e6e9160542d2
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# USMT Best Practices
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Choose a Migration Store Type (Windows 10)
|
||||
description: Choose a Migration Store Type
|
||||
ms.assetid: 4e163e90-9c57-490b-b849-2ed52ab6765f
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Choose a Migration Store Type
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: User State Migration Tool (USMT) Command-line Syntax (Windows 10)
|
||||
description: User State Migration Tool (USMT) Command-line Syntax
|
||||
ms.assetid: f9d205c9-e824-46c7-8d8b-d7e4b52fd514
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# User State Migration Tool (USMT) Command-line Syntax
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Common Issues (Windows 10)
|
||||
description: Common Issues
|
||||
ms.assetid: 5a37e390-8617-4768-9eee-50397fbbb2e1
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Common Issues
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Common Migration Scenarios (Windows 10)
|
||||
description: Common Migration Scenarios
|
||||
ms.assetid: 1d8170d5-e775-4963-b7a5-b55e8987c1e4
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Common Migration Scenarios
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Config.xml File (Windows 10)
|
||||
description: Config.xml File
|
||||
ms.assetid: 9dc98e76-5155-4641-bcb3-81915db538e8
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Config.xml File
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Conflicts and Precedence (Windows 10)
|
||||
description: Conflicts and Precedence
|
||||
ms.assetid: 0e2691a8-ff1e-4424-879b-4d5a2f8a113a
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Conflicts and Precedence
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Custom XML Examples (Windows 10)
|
||||
description: Custom XML Examples
|
||||
ms.assetid: 48f441d9-6c66-43ef-91e9-7c78cde6fcc0
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Custom XML Examples
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Customize USMT XML Files (Windows 10)
|
||||
description: Customize USMT XML Files
|
||||
ms.assetid: d58363c1-fd13-4f65-8b91-9986659dc93e
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Customize USMT XML Files
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Determine What to Migrate (Windows 10)
|
||||
description: Determine What to Migrate
|
||||
ms.assetid: 01ae1d13-c3eb-4618-b39d-ee5d18d55761
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Determine What to Migrate
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Estimate Migration Store Size (Windows 10)
|
||||
description: Estimate Migration Store Size
|
||||
ms.assetid: cfb9062b-7a2a-467a-a24e-0b31ce830093
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Estimate Migration Store Size
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Exclude Files and Settings (Windows 10)
|
||||
description: Exclude Files and Settings
|
||||
ms.assetid: df85baf1-6e29-4995-a4bb-ba3f8f7fed0b
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Exclude Files and Settings
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Extract Files from a Compressed USMT Migration Store (Windows 10)
|
||||
description: Extract Files from a Compressed USMT Migration Store
|
||||
ms.assetid: ad9fbd6e-f89e-4444-8538-9b11566b1f33
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Extract Files from a Compressed USMT Migration Store
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Frequently Asked Questions (Windows 10)
|
||||
description: Frequently Asked Questions
|
||||
ms.assetid: 813c13a7-6818-4e6e-9284-7ee49493241b
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Frequently Asked Questions
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: General Conventions (Windows 10)
|
||||
description: General Conventions
|
||||
ms.assetid: 5761986e-a847-41bd-bf8e-7c1bd01acbc6
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# General Conventions
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Hard-Link Migration Store (Windows 10)
|
||||
description: Hard-Link Migration Store
|
||||
ms.assetid: b0598418-4607-4952-bfa3-b6e4aaa2c574
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Hard-Link Migration Store
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: How USMT Works (Windows 10)
|
||||
description: How USMT Works
|
||||
ms.assetid: 5c8bd669-9e1e-473d-81e6-652f40b24171
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# How USMT Works
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: User State Migration Tool (USMT) How-to topics (Windows 10)
|
||||
description: User State Migration Tool (USMT) How-to topics
|
||||
ms.assetid: 7b9a2f2a-a43a-4984-9746-a767f9f1c7e3
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# User State Migration Tool (USMT) How-to topics
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Identify Applications Settings (Windows 10)
|
||||
description: Identify Applications Settings
|
||||
ms.assetid: eda68031-9b02-4a5b-a893-3786a6505381
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Identify Applications Settings
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
title: Identify File Types, Files, and Folders (Windows 10)
|
||||
description: Identify File Types, Files, and Folders
|
||||
ms.assetid: 93bb2a33-c126-4f7a-a961-6c89686d54e0
|
||||
ms.prod: W10
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Identify File Types, Files, and Folders
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user