Merge remote-tracking branch 'refs/remotes/origin/rs1' into Aug2
@ -47,8 +47,10 @@
|
||||
## [Configure a PXE server to load Windows PE](configure-a-pxe-server-to-load-windows-pe.md)
|
||||
## [Windows 10 upgrade paths](windows-10-upgrade-paths.md)
|
||||
## [Windows 10 edition upgrade](windows-10-edition-upgrades.md)
|
||||
## [Provisioning packages for Windows 10](provisioning-packages.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)
|
||||
|
@ -11,10 +11,18 @@ 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).
|
||||
|
||||
## RELEASE: Windows 10, version 1607
|
||||
|
||||
The topics in this library have been updated for Windows 10, version 1607 (also known as the Anniversary Update). The following new topics have been added:
|
||||
|
||||
- [Provisioning packages for Windows 10](provisioning-packages.md)
|
||||
- [Provision PCs with apps and certificates for initial deployment](provision-pcs-with-apps-and-certificates.md)
|
||||
- [Provision PCs with common settings for initial deployment](provision-pcs-for-initial-deployment.md)
|
||||
|
||||
## July 2016
|
||||
| New or changed topic | Description |
|
||||
|----------------------|-------------|
|
||||
| [Manage Windows upgrades with Upgrade Analytics](manage-windows-upgrades-with-upgrade-analytics.md) | New |
|
||||
| [Manage Windows upgrades with Upgrade Analytics](manage-windows-upgrades-with-upgrade-analytics.md) | New |
|
||||
|
||||
## June 2016
|
||||
| New or changed topic | Description |
|
||||
@ -44,12 +52,3 @@ This topic lists new and updated topics in the [Deploy Windows 10](index.md) doc
|
||||
- [Change history for Plan for Windows 10 deployment](../plan/change-history-for-plan-for-windows-10-deployment.md)
|
||||
- [Change history for Keep Windows 10 secure](../keep-secure/change-history-for-keep-windows-10-secure.md)
|
||||
- [Change history for Manage and update Windows 10](../manage/change-history-for-manage-and-update-windows-10.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
BIN
windows/deploy/images/ICD.png
Normal file
After Width: | Height: | Size: 59 KiB |
BIN
windows/deploy/images/ICDstart-option.PNG
Normal file
After Width: | Height: | Size: 13 KiB |
Before Width: | Height: | Size: 1.2 KiB After Width: | Height: | Size: 20 KiB |
BIN
windows/deploy/images/choose-package.png
Normal file
After Width: | Height: | Size: 20 KiB |
BIN
windows/deploy/images/connect-aad.png
Normal file
After Width: | Height: | Size: 70 KiB |
Before Width: | Height: | Size: 1.5 KiB After Width: | Height: | Size: 20 KiB |
BIN
windows/deploy/images/express-settings.png
Normal file
After Width: | Height: | Size: 108 KiB |
BIN
windows/deploy/images/icd-simple-edit.png
Normal file
After Width: | Height: | Size: 15 KiB |
BIN
windows/deploy/images/icd-simple.PNG
Normal file
After Width: | Height: | Size: 12 KiB |
BIN
windows/deploy/images/license-terms.png
Normal file
After Width: | Height: | Size: 180 KiB |
BIN
windows/deploy/images/oobe.jpg
Normal file
After Width: | Height: | Size: 27 KiB |
BIN
windows/deploy/images/package.png
Normal file
After Width: | Height: | Size: 4.4 KiB |
BIN
windows/deploy/images/prov.jpg
Normal file
After Width: | Height: | Size: 17 KiB |
BIN
windows/deploy/images/setupmsg.jpg
Normal file
After Width: | Height: | Size: 22 KiB |
BIN
windows/deploy/images/sign-in-prov.png
Normal file
After Width: | Height: | Size: 49 KiB |
BIN
windows/deploy/images/trust-package.png
Normal file
After Width: | Height: | Size: 42 KiB |
BIN
windows/deploy/images/uwp-dependencies.PNG
Normal file
After Width: | Height: | Size: 19 KiB |
BIN
windows/deploy/images/uwp-family.PNG
Normal file
After Width: | Height: | Size: 25 KiB |
BIN
windows/deploy/images/uwp-license.PNG
Normal file
After Width: | Height: | Size: 11 KiB |
BIN
windows/deploy/images/who-owns-pc.png
Normal file
After Width: | Height: | Size: 37 KiB |
@ -15,7 +15,6 @@ 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. |
|
||||
|[Manage Windows upgrades with Upgrade Analytics](manage-windows-upgrades-with-upgrade-analytics.md) |With Upgrade Analytics, enterprises now have the tools to plan and manage the upgrade process end to end, allowing them to adopt new Windows releases more quickly. With Windows telemetry enabled, Upgrade Analytics collects system, application, and driver data for analysis. We then identify compatibility issues that can block an upgrade and suggest fixes when they are known to Microsoft. The Upgrade Analytics workflow steps you through the discovery and rationalization process until you have a list of computers that are ready to be upgraded. |
|
||||
|[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. |
|
||||
@ -24,13 +23,15 @@ Learn about deploying Windows 10 for IT professionals.
|
||||
|[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. |
|
||||
|[Windows 10 upgrade paths](windows-10-upgrade-paths.md) |You can upgrade directly to Windows 10 from a previous operating system. |
|
||||
|[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)
|
||||
|
148
windows/deploy/provision-pcs-for-initial-deployment.md
Normal file
@ -0,0 +1,148 @@
|
||||
---
|
||||
title: Provision PCs with common settings (Windows 10)
|
||||
description: Create a provisioning package to apply common settings to a PC running Windows 10.
|
||||
ms.assetid: 66D14E97-E116-4218-8924-E2A326C9367E
|
||||
keywords: ["runtime provisioning", "provisioning package"]
|
||||
ms.prod: W10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Provision PCs with common settings for initial deployment
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
This topic explains how to create and apply a simple provisioning package that contains common enterprise settings to a device running all desktop editions of Windows 10 except Windows 10 Home.
|
||||
|
||||
You can apply a provisioning package on a USB drive to off-the-shelf devices during setup, making it fast and easy to configure new devices.
|
||||
|
||||
## Advantages
|
||||
- You can configure new devices without reimaging.
|
||||
|
||||
- Works on both mobile and desktop devices.
|
||||
|
||||
- No network connectivity required.
|
||||
|
||||
- Simple to apply.
|
||||
|
||||
[Learn more about the benefits and uses of provisioning packages.](provisioning-packages.md)
|
||||
|
||||
## What does simple provisioning do?
|
||||
|
||||
In a simple provisioning package, you can configure:
|
||||
|
||||
- Device name
|
||||
- Upgraded product edition
|
||||
- Wi-Fi network
|
||||
- Active Directory enrollment
|
||||
- Local administrator account
|
||||
|
||||
Provisioning packages can include management instructions and policies, installation of specific apps, customization of network connections and policies, and more. To learn about provisioning packages that include more than the settings in a simple provisioning package, see [Provision PCs with apps and certificates](provision-pcs-with-apps-and-certificates.md).
|
||||
|
||||
> **Tip!** Use simple provisioning to create a package with the common settings, then switch to the advanced editor to add other settings, apps, policies, etc.
|
||||
|
||||

|
||||
|
||||
## Create the provisioning 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 provisioning package. [Install the ADK.](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit)
|
||||
|
||||
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. Click **Simple provisioning**.
|
||||
|
||||

|
||||
|
||||
3. Name your project and click **Finish**. The screens for simple provisioning will walk you through the following steps.
|
||||
|
||||

|
||||
|
||||
4. In the **Set up device** step, enter a unique 15-character name for the device. For help generating a unique name, you can use %SERIAL%, which includes a hardware-specific serial number, or you can use %RAND:x%, which generates random characters of x length.
|
||||
|
||||
5. (Optional) You can upgrade the following editions of Windows 10 by providing a product key for the edition to upgrade to.
|
||||
- Pro to Education
|
||||
- Pro to Enterprise
|
||||
- Enterprise to Education
|
||||
|
||||
6. Click **Set up network**.
|
||||
|
||||
7. Toggle **On** or **Off** for wireless network connectivity. If you select **On**, enter the SSID, type, and (if required) password for the wireless network.
|
||||
|
||||
8. Click **Enroll into Active Directory**.
|
||||
|
||||
9. Toggle **Yes** or **No** for Active Directory enrollment. If you select **Yes**, enter the credentials for an account with permissions to enroll the device. (Optional) Enter a user name and password to create a local administrator account.
|
||||
|
||||
> **Warning**: If you don't create a local administrator account and the device fails to enroll in Active Directory for any reason, you will have to reimage the device and start over. As a best practice, we recommend:
|
||||
- Use a least-privileged domain account to join the device to the domain.
|
||||
- Create a temporary administrator account to use for debugging or reprovisioning if the device fails to enroll successfully.
|
||||
- [Use Group Policy to delete the temporary administrator account](https://blogs.technet.microsoft.com/canitpro/2014/12/10/group-policy-creating-a-standard-local-admin-account/) after the device is enrolled in Active Directory.
|
||||
|
||||
10. Click **Finish**.
|
||||
|
||||
11. Review your settings in the summary. You can return to previous pages to change your selections. Then, under **Protect your package**, toggle **Yes** or **No** to encrypt the provisioning package. If you select **Yes**, enter a password. This password must be entered to apply the encrypted provisioning package.
|
||||
|
||||
12. Click **Create**.
|
||||
|
||||
> **Important** When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed.
|
||||
|
||||
## Apply package
|
||||
|
||||
1. Start with a computer on the first-run setup screen. If the PC has gone past this screen, reset the PC to start over. To reset the PC, go to **Settings** > **Update & security** > **Recovery** > **Reset this PC**.
|
||||
|
||||

|
||||
|
||||
2. Insert the USB drive and press the Windows key five times. Windows Setup will recognize the drive and ask if you want to set up the device. Select **Set up**.
|
||||
|
||||

|
||||
|
||||
3. The next screen asks you to select a provisioning source. Select **Removable Media** and tap **Next**.
|
||||
|
||||

|
||||
|
||||
4. Select the provisioning package (\*.ppkg) that you want to apply, and tap **Next**.
|
||||
|
||||

|
||||
|
||||
5. Select **Yes, add it**.
|
||||
|
||||

|
||||
|
||||
6. Read and accept the Microsoft Software License Terms.
|
||||
|
||||

|
||||
|
||||
7. Select **Use Express settings**.
|
||||
|
||||

|
||||
|
||||
8. If the PC doesn't use a volume license, you'll see the **Who owns this PC?** screen. Select **My work or school owns it** and tap **Next**.
|
||||
|
||||

|
||||
|
||||
9. On the **Choose how you'll connect** screen, select **Join Azure AD** or **Join a domain** and tap **Next**.
|
||||
|
||||

|
||||
|
||||
10. Sign in with your domain, Azure AD, or Office 365 account and password. When you see the progress ring, you can remove the USB drive.
|
||||
|
||||

|
||||
|
||||
## Learn more
|
||||
- [Build and apply a provisioning package]( http://go.microsoft.com/fwlink/p/?LinkId=629651)
|
||||
|
||||
- Watch the video: [Provisioning Windows 10 Devices with New Tools](http://go.microsoft.com/fwlink/p/?LinkId=615921)
|
||||
|
||||
- Watch the video: [Windows 10 for Mobile Devices: Provisioning Is Not Imaging](http://go.microsoft.com/fwlink/p/?LinkId=615922)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
223
windows/deploy/provision-pcs-with-apps-and-certificates.md
Normal file
@ -0,0 +1,223 @@
|
||||
---
|
||||
title: Provision PCs with apps and certificates (Windows 10)
|
||||
description: Create a provisioning package to apply settings to a PC running Windows 10.
|
||||
ms.assetid: 66D14E97-E116-4218-8924-E2A326C9367E
|
||||
keywords: ["runtime provisioning", "provisioning package"]
|
||||
ms.prod: W10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Provision PCs with apps and certificates for initial deployment
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
This topic explains how to create and apply a provisioning package that contains apps and certificates to a device running all desktop editions of Windows 10 except Windows 10 Home. Provisioning packages can include management instructions and policies, installation of specific apps, customization of network connections and policies, and more.
|
||||
|
||||
You can apply a provisioning package on a USB drive to off-the-shelf devices during setup, making it fast and easy to configure new devices.
|
||||
|
||||
## Advantages
|
||||
- You can configure new devices without reimaging.
|
||||
|
||||
- Works on both mobile and desktop devices.
|
||||
|
||||
- No network connectivity required.
|
||||
|
||||
- Simple to apply.
|
||||
|
||||
[Learn more about the benefits and uses of provisioning packages.](provisioning-packages.md)
|
||||
|
||||
## Create the provisioning 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 provisioning package. [Install the ADK.](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit)
|
||||
|
||||
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. Click **Advanced provisioning**.
|
||||
|
||||

|
||||
|
||||
3. Name your project and click **Next**.
|
||||
|
||||
3. Select **All Windows desktop editions**, click **Next**, and then click **Finish**.
|
||||
|
||||
|
||||
### Add a desktop app to your package
|
||||
|
||||
1. In the **Available customizations** pane, go to **Runtime settings** > **ProvisioningCommands** > **DeviceContext** > **CommandFiles**.
|
||||
|
||||
2. Add all the files required for the app install, including the data files and the installer.
|
||||
|
||||
3. Go to **Runtime settings** > **ProvisioningCommands** > **DeviceContext** > **CommandLine** and specify the command line that needs to be executed to install the app. This is a single command line (such as a script, executable, or msi) that triggers a silent install of your CommandFiles. Note that the install must execute silently (without displaying any UI). For MSI installers use, the `msiexec /quiet` option.
|
||||
|
||||
> **Note**: If you are installing more than one app, then use CommandLine to invoke the script or batch file that orchestrates installation of the files. For more information, see [Install a Win32 app using a provisioning package](https://msdn.microsoft.com/en-us/library/windows/hardware/mt703295%28v=vs.85%29.aspx).
|
||||
|
||||
|
||||
### Add a universal app to your package
|
||||
|
||||
Universal apps that you can distribute in the provisioning package can be line-of-business (LOB) apps developed by your organization, Windows Store for Business apps that you acquire with [offline licensing](../manage/acquire-apps-windows-store-for-business.md), or third-party apps. This procedure will assume you are distributing apps from the Windows Store for Business. For other apps, obtain the necessary information (such as the package family name) from the app developer.
|
||||
|
||||
1. In the **Available customizations** pane, go to **Runtime settings** > **UniversalAppInstall**.
|
||||
|
||||
2. For **DeviceContextApp**, specify the **PackageFamilyName** for the app. In Windows Store for Business, the package family name is listed in the **Package details** section of the download page.
|
||||
|
||||

|
||||
|
||||
3. For **ApplicationFile**, click **Browse** to find and select the target app (either an \*.appx or \*.appxbundle).
|
||||
|
||||
4. For **DependencyAppxFiles**, click **Browse** to find and add any dependencies for the app. In Windows Store for Business, any dependencies for the app are listed in the **Required frameworks** section of the download page.
|
||||
|
||||

|
||||
|
||||
5. For **DeviceContextAppLicense**, enter the **LicenseProductID**. In Windows Store for Business, you generate the license for the app on the app's download page.
|
||||
|
||||

|
||||
|
||||
[Learn more about distributing offline apps from the Windows Store for Business.](../manage/distribute-offline-apps.md)
|
||||
|
||||
> **Note:** Removing a provisioning package will not remove any apps installed by device context in that provisioning package.
|
||||
|
||||
|
||||
|
||||
### Add a certificate to your package
|
||||
|
||||
1. In the **Available customizations** pane, go to **Runtime settings** > **Certificates** > **ClientCertificates**.
|
||||
|
||||
2. Enter a **CertificateName** and then click **Add**.
|
||||
|
||||
2. Enter the **CertificatePassword**.
|
||||
|
||||
3. For **CertificatePath**, browse and select the certificate to be used.
|
||||
|
||||
4. Set **ExportCertificate** to **False**.
|
||||
|
||||
5. For **KeyLocation**, select **Software only**.
|
||||
|
||||
|
||||
### Add other settings to your 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).
|
||||
|
||||
### Build your package
|
||||
|
||||
1. When you are done configuring the provisioning package, on the **File** menu, click **Save**.
|
||||
|
||||
2. Read the warning that project files may contain sensitive information, and click **OK**.
|
||||
> **Important** When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed.
|
||||
|
||||
3. On the **Export** menu, click **Provisioning package**.
|
||||
|
||||
1. 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)
|
||||
|
||||
|
||||
|
||||
## Apply package
|
||||
|
||||
**During initial setup, from a USB drive**
|
||||
|
||||
1. Start with a computer on the first-run setup screen. If the PC has gone past this screen, reset the PC to start over. To reset the PC, go to **Settings** > **Update & security** > **Recovery** > **Reset this PC**.
|
||||
|
||||

|
||||
|
||||
2. Insert the USB drive and press the Windows key five times. Windows Setup will recognize the drive and ask if you want to set up the device. Select **Set up**.
|
||||
|
||||

|
||||
|
||||
3. The next screen asks you to select a provisioning source. Select **Removable Media** and tap **Next**.
|
||||
|
||||

|
||||
|
||||
4. Select the provisioning package (\*.ppkg) that you want to apply, and tap **Next**.
|
||||
|
||||

|
||||
|
||||
5. Select **Yes, add it**.
|
||||
|
||||

|
||||
|
||||
6. Read and accept the Microsoft Software License Terms.
|
||||
|
||||

|
||||
|
||||
7. Select **Use Express settings**.
|
||||
|
||||

|
||||
|
||||
8. If the PC doesn't use a volume license, you'll see the **Who owns this PC?** screen. Select **My work or school owns it** and tap **Next**.
|
||||
|
||||

|
||||
|
||||
9. On the **Choose how you'll connect** screen, select **Join Azure AD** or **Join a domain** and tap **Next**.
|
||||
|
||||

|
||||
|
||||
10. Sign in with your domain, Azure AD, or Office 365 account and password. When you see the progress ring, you can remove the USB drive.
|
||||
|
||||

|
||||
|
||||
|
||||
**After setup, from a USB drive, network folder, or SharePoint site**
|
||||
|
||||
On a desktop computer, navigate to **Settings** > **Accounts** > **Work access** > **Add or remove a management package** > **Add a package**, and select the package to install.
|
||||
|
||||

|
||||
|
||||
## Learn more
|
||||
- [Build and apply a provisioning package]( http://go.microsoft.com/fwlink/p/?LinkId=629651)
|
||||
|
||||
- Watch the video: [Provisioning Windows 10 Devices with New Tools](http://go.microsoft.com/fwlink/p/?LinkId=615921)
|
||||
|
||||
- Watch the video: [Windows 10 for Mobile Devices: Provisioning Is Not Imaging](http://go.microsoft.com/fwlink/p/?LinkId=615922)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
137
windows/deploy/provisioning-packages.md
Normal file
@ -0,0 +1,137 @@
|
||||
---
|
||||
title: Provisioning packages (Windows 10)
|
||||
description: With Windows 10, you can create provisioning packages that let you quickly and efficiently configure a device without having to install a new image.
|
||||
ms.assetid: 287706E5-063F-4AB5-902C-A0DF6D0730BC
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mobile
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Provisioning packages for Windows 10
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
|
||||
Windows provisioning makes it easy for IT administrators to configure end-user devices without imaging. Using Windows Provisioning, an IT administrator can easily specify desired configuration and settings required to enroll the devices into management (through a wizard-driven user interface) and then apply that configuration to target devices in a matter of minutes. It is best suited for small- to medium-sized businesses with deployments that range from tens to a few hundred computers.
|
||||
|
||||
With Windows 10, you can create provisioning packages that let you quickly and efficiently configure a device without having to install a new image.
|
||||
|
||||
Provisioning packages are simple enough that with a short set of written instructions, a student or non-technical employee can use them to configure their device. This can result in a significant reduction in the time required to configure multiple devices in your organization.
|
||||
|
||||
## New in Windows 10, Version 1607
|
||||
|
||||
The Windows Assessment and Deployment Kit (ADK) for Windows 10 includes the Imaging and Configuration Designer (ICD), a tool for configuring images and runtime settings which are then built into provisioning packages. Windows ICD for Windows 10, Version 1607, simplifies common provisioning scenarios.
|
||||
|
||||

|
||||
|
||||
Windows ICD in Windows 10, Version 1607, supports the following scenarios for IT administrators:
|
||||
|
||||
* **Simple provisioning** – Enables IT administrators to define a desired configuration in Windows ICD and then apply that configuration on target devices. The simple provisioning wizard makes the entire process quick and easy by guiding an IT administrator through common configuration settings in a step-by-step manner.
|
||||
|
||||
> [Learn how to use simple provisioning to configure Windows 10 computers.](provision-pcs-for-initial-deployment.md)
|
||||
|
||||
* **Advanced provisioning (deployment of classic (Win32) and Universal Windows Platform (UWP) apps, and certificates)** – Allows an IT administrator to use Windows ICD to open provisioning packages in the advanced settings editor and include apps for deployment on end-user devices.
|
||||
|
||||
> [Learn how to use advanced provisioning to configure Windows 10 computers with apps and certificates.](provision-pcs-with-apps-and-certificates.md)
|
||||
|
||||
* **Mobile device enrollment into management** - Enables IT administrators to purchase off-the-shelf retail Windows 10 Mobile devices and enroll them into mobile device management (MDM) before handing them to end-users in the organization. IT administrators can use Windows ICD to specify the management end-point and apply the configuration on target devices by connecting them to a Windows PC (tethered deployment) or through an SD card. Supported management end-points include:
|
||||
|
||||
* System Center Configuration Manager and Microsoft Intune hybrid (certificate-based enrollment)
|
||||
* AirWatch (password-string based enrollment)
|
||||
* Mobile Iron (password-string based enrollment)
|
||||
* Other MDMs (cert-based enrollment)
|
||||
|
||||
> **Note:** Windows ICD in Windows 10, Version 1607, also provides a wizard to create provisioning packages for school PCs. To learn more, see [Set up students' PCs to join domain](https://technet.microsoft.com/edu/windows/index).
|
||||
|
||||
## Benefits of provisioning packages
|
||||
|
||||
|
||||
Provisioning packages let you:
|
||||
|
||||
- Quickly configure a new device without going through the process of installing a new image.
|
||||
|
||||
- Save time by configuring multiple devices using one provisioning package.
|
||||
|
||||
- Quickly configure employee-owned devices in an organization without a mobile device management (MDM) infrastructure.
|
||||
|
||||
- Set up a device without the device having network connectivity.
|
||||
|
||||
Provisioning packages can be:
|
||||
|
||||
- Installed using removable media such as an SD card or USB flash drive.
|
||||
|
||||
- Attached to an email.
|
||||
|
||||
- Downloaded from a network share.
|
||||
|
||||
## What you can configure
|
||||
|
||||
|
||||
The following table provides some examples of what can be configured using provisioning packages.
|
||||
|
||||
| Customization options | Examples |
|
||||
|--------------------------|-----------------------------------------------------------------------------------------------|
|
||||
| Bulk Active Directory join and device name | Join devices to Active Directory domain and assign device names using hardware-specific serial numbers or random characters |
|
||||
| Applications | Windows apps, line-of-business applications |
|
||||
| Bulk enrollment into MDM | Automatic enrollment into a third-party MDM service\* |
|
||||
| Certificates | Root certification authority (CA), client certificates |
|
||||
| Connectivity profiles | Wi-Fi, proxy settings, Email |
|
||||
| Enterprise policies | Security restrictions (password, device lock, camera, and so on), encryption, update settings |
|
||||
| Data assets | Documents, music, videos, pictures |
|
||||
| Start menu customization | Start menu layout, application pinning |
|
||||
| Other | Home and lock screen wallpaper, computer name, domain join, DNS settings, and so on |
|
||||
\* Using a provisioning package for auto-enrollment to System Center Configuration Manager or Configuration Manager/Intune hybrid is not supported. Use the Configuration Manager console to enroll devices.
|
||||
|
||||
|
||||
For details about the settings you can customize in provisioning packages, see [Windows Provisioning settings reference]( http://go.microsoft.com/fwlink/p/?LinkId=619012).
|
||||
|
||||
## Creating a provisioning package
|
||||
|
||||
|
||||
With Windows 10, you can use the Windows Imaging and Configuration Designer (ICD) tool to create provisioning packages. To install Windows ICD and create provisioning packages, you must [install the Windows Assessment and Deployment Kit (ADK) for Windows 10](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit).
|
||||
|
||||
While running ADKsetup.exe for Windows 10, version 1607, select the following feature from the **Select the features you want to install** dialog box:
|
||||
|
||||
- Configuration Designer
|
||||
|
||||
> **Note:** In previous versions of the Windows 10 ADK, you had to install additional features for Windows ICD to run. Starting in version 1607, you can install Windows ICD without other ADK features.
|
||||
|
||||
After you install Windows ICD, you can use it to create a provisioning package. For detailed instructions on how to create a provisioning package, see [Build and apply a provisioning package](http://go.microsoft.com/fwlink/p/?LinkID=629651).
|
||||
|
||||
## Applying a provisioning package to a device
|
||||
|
||||
|
||||
Provisioning packages can be applied both during image deployment and during runtime. For information on how to apply a provisioning package to a Windows 10-based device, see [Build and apply a provisioning package](http://go.microsoft.com/fwlink/p/?LinkID=629651).
|
||||
|
||||
## Learn more
|
||||
|
||||
|
||||
[Windows 10: Deployment](http://go.microsoft.com/fwlink/p/?LinkId=533708)
|
||||
|
||||
## Related topics
|
||||
|
||||
- [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)
|
||||
- [Configure devices without MDM](../manage/configure-devices-without-mdm.md)
|
||||
- [Set up a shared or guest PC with Windows 10](../manage/set-up-shared-or-guest-pc.md)
|
||||
- [Configure devices without MDM](../manage/configure-devices-without-mdm.md)
|
||||
- [Set up a device for anyone to use (kiosk mode)](../manage/set-up-a-device-for-anyone-to-use.md)
|
||||
- [Customize Windows 10 Start and taskbar with ICD and provisioning packages](../manage/customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md)
|
||||
- [Set up student PCs to join domain](https://technet.microsoft.com/en-us/edu/windows/set-up-students-pcs-to-join-domain)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -328,7 +328,7 @@ For more information on UEFI, see the [UEFI firmware](http://go.microsoft.com/fw
|
||||
## Related topics
|
||||
|
||||
|
||||
[Update Windows 10 images with provisioning packages](update-windows-10-images-with-provisioning-packages.md)
|
||||
|
||||
|
||||
[Deploy Windows To Go](deploy-windows-to-go.md)
|
||||
|
||||
|