mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 22:37:22 +00:00
Merge branch 'master' into wdav-10things
This commit is contained in:
Denise Vangel-MSFT
commit
a1ff1d27cc
5
CODEOWNERS
Normal file
5
CODEOWNERS
Normal file
@ -0,0 +1,5 @@
|
||||
docfx.json @microsoftdocs/officedocs-admin
|
||||
.openpublishing.build.ps1 @microsoftdocs/officedocs-admin
|
||||
.openpublishing.publish.config.json @microsoftdocs/officedocs-admin
|
||||
CODEOWNERS @microsoftdocs/officedocs-admin
|
||||
.acrolinx-config.edn @microsoftdocs/officedocs-admin
|
||||
@ -99,7 +99,7 @@ You can also disable the calibration prompt by following these steps:
|
||||
1. Turn off **When a new person uses this HoloLens, automatically ask to run eye calibration**.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Please understand that this setting may adversely affect hologram rendering quality and comfort.
|
||||
> This setting may adversely affect hologram rendering quality and comfort. When you turn off this setting, features that depend on eye tracking (such as text scrolling) no longer work in immersive applications.
|
||||
|
||||
### HoloLens 2 eye-tracking technology
|
||||
|
||||
|
||||
@ -56,7 +56,7 @@ To use these commands, gaze at a 3D object, hologram, or app window.
|
||||
| "Face me" | Turn it to face you |
|
||||
| "Move this" | Move it (follow your gaze) |
|
||||
| "Close" | Close it |
|
||||
| "Follow" / "Stop following" | Make it follow you as you move around |
|
||||
| "Follow me" / "Stop following" | Make it follow you as you move around |
|
||||
|
||||
### See it, say it
|
||||
|
||||
@ -64,7 +64,7 @@ Many buttons and other elements on HoloLens also respond to your voice—for exa
|
||||
|
||||
### Dictation mode
|
||||
|
||||
Tired of typing? Switch to dictation mode any time that the holographic keyboard is active. To get started, select the microphone icon or say "Start dictating." To stop dictating, select **Done** or say "Stop dictating." To delete what you just dictated, say "Delete that."
|
||||
Tired of typing? Switch to dictation mode any time that the holographic keyboard is active. To get started, select the microphone button or say "Start dictating." To stop dictating, select the button again or say "Stop dictating." To delete what you just dictated, say "Delete that."
|
||||
|
||||
> [!NOTE]
|
||||
> To use dictation mode, you have to have an internet connection.
|
||||
|
||||
@ -106,6 +106,14 @@ The Advanced Recovery Companion is a new app in Microsoft Store restore the oper
|
||||
5. On the **Device info** page, select **Install software** to install the default package. (If you have a Full Flash Update (FFU) image that you want to install instead, select **Manual package selection**.)
|
||||
6. Software installation will begin. Do not use the device or disconnect the cable during installation. When you see the **Installation finished** page, you can disconnect and use your device.
|
||||
|
||||
>[!TIP]
|
||||
>In the event that a HoloLens 2 gets into a state where Advanced Recovery Companion cannot recognize the device, and it does not boot, try forcing the device into Flashing Mode and recovering it with Advanced Recovery Companion:
|
||||
|
||||
1. Connect the HoloLens 2 to a PC with Advanced Recovery Companion installed.
|
||||
1. Press and hold the **Volume Up and Power buttons** until the device reboots. Release the Power button, but continue to hold the Volume Up button until the third LED is lit. It will the the only lit LED.
|
||||
1. The device should be visible in **Device Manager** as a **Microsoft HoloLens Recovery** device:
|
||||
1. Launch Advanced Recovery Companion, and follow the on-screen prompts to reflash the OS to the HoloLens 2.
|
||||
|
||||
### HoloLens (1st gen)
|
||||
|
||||
If necessary, you can install a completely new operating system on your HoloLens (1st gen) with the Windows Device Recovery Tool.
|
||||
|
||||
@ -105,8 +105,8 @@ To **close** the Start menu, do the Start gesture when the Start menu is open.
|
||||
> [!IMPORTANT]
|
||||
> For the one-handed Start gesture to work:
|
||||
>
|
||||
> 1. You must update to the November 2019 update (build 18363) or later.
|
||||
> 1. Your eyes must be calibrated on the device so that eye tracking functions correctly. If you do not see orbiting dots around the Start icon when you look at it, your eyes are not calibrated on the device.
|
||||
> 1. You must update to the November 2019 update (build 18363.1039) or later.
|
||||
> 1. Your eyes must be calibrated on the device so that eye tracking functions correctly. If you do not see orbiting dots around the Start icon when you look at it, your eyes are not [calibrated](https://docs.microsoft.com/hololens/hololens-calibration#calibrating-your-hololens-2) on the device.
|
||||
|
||||
You can also perform the Start gesture with only one hand. To do this, hold out your hand with your palm facing you and look at the **Start icon** on your inner wrist. **While keeping your eye on the icon**, pinch your thumb and index finger together.
|
||||
|
||||
|
||||
@ -43,6 +43,15 @@ Try adjusting the position of your device visor so the holographic frame matches
|
||||
- **If you need to look up to see holograms**. First, shift the back of the headband a bit higher on your head. Then use one hand to hold the headband in place and the other to gently rotate the visor so you have a good view of the holographic frame.
|
||||
- **If you need to look down to see holograms**. First, shift the back of the headband a bit lower on your head. Then place your thumbs under the device arms and your index fingers on top of the headband, and gently squeeze with your thumbs to rotate the visor so you have a good view of the holographic frame.
|
||||
|
||||
## Hologram image color or brightness does not look right
|
||||
|
||||
For HoloLens 2, take the following steps to ensure the highest visual quality of holograms presented in displays:
|
||||
|
||||
- **Increase brightness of the display.** Holograms look best when the display is at its brightest level.
|
||||
- **Bring visor closer to your eyes.** Swing the visor down to the closest position to your eyes.
|
||||
- **Shift visor down.** Try moving the brow pad on your forehead down, which will result in the visor moving down closer to your nose.
|
||||
- **Run eye calibration.** The display uses your IPD and eye gaze to optimize images on the display. If you don't run eye calibration, the image quality may be made worse.
|
||||
|
||||
## The device slides down when I'm using it, or I need to make the headband too tight to keep it secure
|
||||
|
||||
The overhead strap can help keep your HoloLens secure on your head, particularly if you're moving around a lot. The strap may also let you loosen the headband a bit. [Learn how to use it](hololens2-setup.md#adjust-fit).
|
||||
|
||||
@ -17,7 +17,7 @@ appliesto:
|
||||
|
||||
# Supported languages for HoloLens 2
|
||||
|
||||
HoloLens 2 supports the following languages. This support includes voice commands and dictation features.
|
||||
HoloLens 2 supports the following languages, including voice commands and dictation features, keyboard layouts, and OCR recognition within apps.
|
||||
|
||||
- Chinese Simplified (China)
|
||||
- English (Australia)
|
||||
@ -39,7 +39,35 @@ HoloLens 2 is also available in the following languages. However, this support d
|
||||
|
||||
## Changing language or keyboard
|
||||
|
||||
The setup process configures your HoloLens for a region and language. You can change this configuration by using the **Time & language** section of **Settings**.
|
||||
|
||||
> [!NOTE]
|
||||
> Your speech and dictation language depends on the Windows display language.
|
||||
>
|
||||
To change the Windows display language, region, or keyboard settings, use the start gesture to open the **Start** menu, and then select **Settings** > **Time and Language** > **Language**.
|
||||
|
||||
## To change the Windows display language
|
||||
|
||||
1. Go to the **Start** menu, and then select **Settings** > **Time and language** > **Language**.
|
||||
2. Select **Windows display language**, and then select a language.
|
||||
|
||||
If the supported language you’re looking for is not in the menu, follow these steps:
|
||||
|
||||
1. Under **Preferred languages** select **Add a language**.
|
||||
2. Search for and add the language.
|
||||
3. Select the **Windows display language** menu again and choose the language you added.
|
||||
|
||||
The Windows display language affects the following settings for Windows and for apps that support localization:
|
||||
|
||||
- The user interface text language.
|
||||
- The speech language.
|
||||
- The default layout of the on-screen keyboard.
|
||||
|
||||
## To change the keyboard layout
|
||||
|
||||
To add or remove a keyboard layout, open the **Start** menu and then select **Settings** > **Time & language** > **Keyboard**.
|
||||
|
||||
If your HoloLens has more than one keyboard layout, use the **Layout** key to switch between them. The **Layout** key is in the lower right corner of the on-screen keyboard.
|
||||
|
||||
> [!NOTE]
|
||||
> The on-screen keyboard can use Input Method Editor (IME) to enter characters in languages such as Chinese. However, HoloLens does not support external Bluetooth keyboards that use IME.
|
||||
>
|
||||
> While you use IME with the on-screen keyboard, you can continue to use a Bluetooth keyboard to type in English. To switch between keyboards, press ~.
|
||||
|
||||
@ -55,4 +55,4 @@ appliesto:
|
||||
## Related resources
|
||||
|
||||
* [Documentation for Holographic app development](https://developer.microsoft.com/windows/mixed-reality/development)
|
||||
* [HoloLens release notes](https://developer.microsoft.com/windows/mixed-reality/release_notes)
|
||||
* [HoloLens release notes](https://docs.microsoft.com/hololens/hololens-release-notes)
|
||||
|
||||
@ -7,6 +7,7 @@
|
||||
### [Surface Hub 2S tech specs](surface-hub-2s-techspecs.md)
|
||||
### [Operating system essentials (Surface Hub)](differences-between-surface-hub-and-windows-10-enterprise.md)
|
||||
### [Adjust Surface Hub 2S brightness, volume, and input](surface-hub-2s-onscreen-display.md)
|
||||
### [Use Microsoft Whiteboard on a Surface Hub](https://support.office.com/article/use-microsoft-whiteboard-on-a-surface-hub-5c594985-129d-43f9-ace5-7dee96f7621d)
|
||||
|
||||
## Plan
|
||||
### [Surface Hub 2S Site Readiness Guide](surface-hub-2s-site-readiness-guide.md)
|
||||
@ -58,6 +59,7 @@
|
||||
### [Operating system essentials (Surface Hub)](differences-between-surface-hub-and-windows-10-enterprise.md)
|
||||
### [Technical information for 55” Microsoft Surface Hub](surface-hub-technical-55.md)
|
||||
### [Technical information for 84” Microsoft Surface Hub](surface-hub-technical-84.md)
|
||||
### [Use Microsoft Whiteboard on a Surface Hub](https://support.office.com/article/use-microsoft-whiteboard-on-a-surface-hub-5c594985-129d-43f9-ace5-7dee96f7621d)
|
||||
|
||||
## Plan
|
||||
### [Prepare your environment for Microsoft Surface Hub](prepare-your-environment-for-surface-hub.md)
|
||||
|
||||
@ -30,7 +30,6 @@ Surface Hub 2S is an all-in-one digital interactive whiteboard, meetings platfor
|
||||
<p><a href="https://techcommunity.microsoft.com/t5/Surface-IT-Pro-Blog/Behind-the-design-Surface-Hub-2S/ba-p/464099" target="_blank">Behind the design: Surface Hub 2S</a></p>
|
||||
<p><a href="surface-hub-2s-whats-new.md">What's new in Surface Hub 2S</a></p>
|
||||
<p><a href="differences-between-surface-hub-and-windows-10-enterprise.md">Operating system essentials</a></p>
|
||||
<p><a href="https://support.office.com/article/use-microsoft-whiteboard-on-a-surface-hub-5c594985-129d-43f9-ace5-7dee96f7621d">Enable Microsoft Whiteboard on Surface Hub</a></p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@ -49,6 +49,7 @@ If you have a single-forest on-premises deployment with Microsoft Exchange 2013
|
||||
```PowerShell
|
||||
New-Mailbox -UserPrincipalName HUB01@contoso.com -Alias HUB01 -Name "Hub-01" -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String <password> -AsPlainText -Force)
|
||||
```
|
||||
[!IMPORTANT] ActiveSync Virtual Directory Basic Authentication is required to be enabled as the Surface Hub is unable to authenticate using other authentication methods.
|
||||
|
||||
3. After setting up the mailbox, you will need to either create a new Exchange ActiveSync policy, or use a compatible existing policy.
|
||||
|
||||
|
||||
@ -28,7 +28,7 @@ Surface Hub 2S allows IT administrators to manage settings and policies using a
|
||||
|
||||
### Auto registration — Azure Active Directory Affiliated
|
||||
|
||||
When affiliating Surface Hub 2S with a tenant that has Intune auto enrollment enabled, the device will automatically enroll with Intune. For more information, refer to [Intune enrollment methods for Windows devices](https://docs.microsoft.com/intune/enrollment/windows-enrollment-methods).
|
||||
During the initial setup process, when affiliating a Surface Hub with an Azure AD tenant that has Intune auto enrollment enabled, the device will automatically enroll with Intune. For more information, refer to [Intune enrollment methods for Windows devices](https://docs.microsoft.com/intune/enrollment/windows-enrollment-methods). Azure AD affiliation and Intune auto enrollment is required for the Surface Hub to be a "compliant device" in Intune.
|
||||
|
||||
## Windows 10 Team Edition settings
|
||||
|
||||
|
||||
@ -21,11 +21,10 @@ When deploying Surface devices in point of sale or other “always-on”
|
||||
kiosk scenarios, you can optimize power management using the new Surface
|
||||
Brightness Control app.
|
||||
|
||||
Available for download with [Surface Tools for
|
||||
IT](https://www.microsoft.com/download/details.aspx?id=46703), Surface Brightness Control is
|
||||
designed to help reduce thermal load and lower the overall carbon
|
||||
footprint for deployed Surface devices. The tool automatically dims the screen when not in use and
|
||||
includes the following configuration options:
|
||||
Available for download with [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703).
|
||||
Surface Brightness Control is designed to help reduce thermal load and lower the overall carbon footprint for deployed Surface devices.
|
||||
If you plan to get only this tool from the download page, select the file **Surface_Brightness_Control_v1.16.137.0.msi** in the available list.
|
||||
The tool automatically dims the screen when not in use and includes the following configuration options:
|
||||
|
||||
- Period of inactivity before dimming the display.
|
||||
|
||||
|
||||
@ -62,18 +62,19 @@ Some third-party antivirus software cannot be installed on a Windows 10 PC runni
|
||||
|
||||
## Servicing Surface Pro X
|
||||
|
||||
Outside of personal devices that rely on Windows Update, servicing devices in most corporate environments requires downloading and managing the deployment of .MSI files to update target devices. Refer to the following documentation, which will be updated later to include guidance for servicing Surface Pro X:
|
||||
Surface Pro X supports Windows 10, version 1903 and later. As an ARM-based device, it has specific requirements for maintaining the latest drivers and firmware.
|
||||
|
||||
- [Deploy the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md).
|
||||
Surface Pro X was designed to use Windows Update to simplify the process of keeping drivers and firmware up to date for both home users and small business users. Use the default settings to receive Automatic updates. To verify:
|
||||
|
||||
> [!NOTE]
|
||||
> Surface Pro X supports Windows 10, version 1903 and later.
|
||||
1. Go to **Start** > **Settings > Update & Security > Windows Update** > **Advanced Options.**
|
||||
2. Under **Choose how updates are installed,** select **Automatic (recommended)**.
|
||||
|
||||
### Windows Server Update Services
|
||||
Windows Server Update Services (WSUS) does not support the ability to deliver drivers and firmware to Surface Pro X.
|
||||
|
||||
For more information, refer to the [Microsoft Endpoint Configuration Manager documentation](https://docs.microsoft.com/configmgr/sum/get-started/configure-classifications-and-products).
|
||||
### Recommendations for commercial customers
|
||||
|
||||
- Use Windows Update or Windows Update for Business for maintaining the latest drivers and firmware. For more information, see [Deploy Updates using Windows Update for Business](https://docs.microsoft.com/windows/deployment/update/waas-manage-updates-wufb).
|
||||
- If your procedures require using a Windows Installer .msi file, contact [Surface for Business support](https://support.microsoft.com/help/4037645).
|
||||
- For more information about deploying and managing updates on Surface devices, see [Deploy the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md).
|
||||
- Note that Windows Server Update Services (WSUS) does not support the ability to deliver drivers and firmware to Surface Pro X.
|
||||
|
||||
## Running apps on Surface Pro X
|
||||
|
||||
|
||||
@ -39,3 +39,18 @@ This section lists common issues that you may encounter when you upgrade your Ad
|
||||
- Install the required hotfix.
|
||||
|
||||
- Connect to AGPM using an AGPM client to test that your difference reports are now functioning.
|
||||
|
||||
## Install Hotfix Package 1 for Microsoft Advanced Group Policy Management 4.0 SP3
|
||||
|
||||
**Issue fixed in this hotfix**: AGPM can't generate difference reports when it controls or manages new Group Policy Objects (GPOs).
|
||||
|
||||
**How to get this update**: Install the latest version of Microsoft Desktop Optimization Pack ([March 2017 Servicing Release](https://www.microsoft.com/download/details.aspx?id=54967)). See [KB 4014009](https://support.microsoft.com/help/4014009/) for more information.
|
||||
|
||||
More specifically, you can choose to download only the first file, `AGPM4.0SP1_Server_X64_KB4014009.exe`, from the list presented after pressing the download button.
|
||||
|
||||
The download link to the Microsoft Desktop Optimization Pack (March 2017 Servicing Release) can be found [here](https://www.microsoft.com/download/details.aspx?id=54967).
|
||||
|
||||
|
||||
## Reference link
|
||||
https://support.microsoft.com/help/3127165/hotfix-package-1-for-microsoft-advanced-group-policy-management-4-0-sp
|
||||
|
||||
|
||||
@ -1,13 +1,14 @@
|
||||
---
|
||||
title: Deploying MBAM 2.5 in a stand-alone configuration
|
||||
description: Introducing how to deploy MBAM 2.5 in a stand-alone configuration.
|
||||
author: delhan
|
||||
author: Deland-Han
|
||||
ms.reviewer: dcscontentpm
|
||||
manager: dansimp
|
||||
ms.author: delhan
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 09/16/2019
|
||||
manager: dcscontentpm
|
||||
---
|
||||
|
||||
# Deploying MBAM 2.5 in a standalone configuration
|
||||
|
||||
@ -1,13 +1,14 @@
|
||||
---
|
||||
title: Troubleshooting MBAM 2.5 installation problems
|
||||
description: Introducing how to troubleshoot MBAM 2.5 installation problems.
|
||||
author: delhan
|
||||
author: Deland-Han
|
||||
ms.reviewer: dcscontentpm
|
||||
manager: dansimp
|
||||
ms.author: delhan
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 09/16/2019
|
||||
manager: dcscontentpm
|
||||
---
|
||||
|
||||
# Troubleshooting MBAM 2.5 installation problems
|
||||
@ -386,7 +387,7 @@ Basic checks:
|
||||
|
||||
* If the communication between client and server is secure, make sure that you are using a valid SSL certificate.
|
||||
|
||||
* Verify network connectivity between the web server and the database server to which the data is sent for insertion. You can check database connectivity from the web server to the database server by using ODBC Data Source Administrator. Detailed SQL Server connection troubleshooting information is available in [How to Troubleshoot Connecting to the SQL Server Database Engine](http://social.technet.microsoft.com/wiki/contents/articles/2102.how-to-troubleshoot-connecting-to-the-sql-server-database-engine.aspx).
|
||||
* Verify network connectivity between the web server and the database server to which the data is sent for insertion. You can check database connectivity from the web server to the database server by using ODBC Data Source Administrator. Detailed SQL Server connection troubleshooting information is available in [How to Troubleshoot Connecting to the SQL Server Database Engine](https://social.technet.microsoft.com/wiki/contents/articles/2102.how-to-troubleshoot-connecting-to-the-sql-server-database-engine.aspx).
|
||||
|
||||
#### Troubleshooting the connectivity issue
|
||||
|
||||
@ -528,11 +529,11 @@ The web service may not connect to the database server because of a permissions
|
||||
|
||||
* These groups do not have the required permissions on the database.
|
||||
|
||||
You will notice permissions-related errors in the Application logs on the MBAM administration and monitoring server if any of the previous conditions are true. In that case, you should manually add the NT Authority\Network Service account and MBAM administration server’s computer account and grant them a server-wide public role on the SQL database server that is using SQL Server Management Studio (http://msdn.microsoft.com/en-us/library/aa337562.aspx).
|
||||
You will notice permissions-related errors in the Application logs on the MBAM administration and monitoring server if any of the previous conditions are true. In that case, you should manually add the NT Authority\Network Service account and MBAM administration server’s computer account and grant them a server-wide public role on the SQL database server that is using SQL Server Management Studio (https://msdn.microsoft.com/library/aa337562.aspx).
|
||||
|
||||
#### Review the web service logs
|
||||
|
||||
If no events are logged in the Application logs on the MBAM administration server, it’s time to review the web service logs (.svclog) of the MBAM web service that is hosted on the MBAM administration and monitoring server. You will have to use the Service Trace Viewer Tool (SvcTraceViewer.exe) http://msdn.microsoft.com/en-us/library/ms732023.aspx to view the log file.
|
||||
If no events are logged in the Application logs on the MBAM administration server, it’s time to review the web service logs (.svclog) of the MBAM web service that is hosted on the MBAM administration and monitoring server. You will have to use the Service Trace Viewer Tool (SvcTraceViewer.exe) https://msdn.microsoft.com/library/ms732023.aspx to view the log file.
|
||||
|
||||
You should primarily investigate the service trace logs of RecoveryandHardwareService and ComplianceStatusService. By default, web service logs are located in the C:\inetpub\Microsoft BitLocker Management Solution\Logs folder. There, each service writes its .svclog file under its own folder.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Change history for Application management in Windows 10 (Windows 10)
|
||||
description: This topic lists changes to documentation for configuring Windows 10.
|
||||
description: View changes to documentation for application management in Windows 10.
|
||||
keywords:
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Change history for Client management (Windows 10)
|
||||
description: This topic lists changes to documentation for configuring Windows 10.
|
||||
description: View changes to documentation for client management in Windows 10.
|
||||
keywords:
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -8,7 +8,7 @@ author: Deland-Han
|
||||
ms.localizationpriority: medium
|
||||
ms.author: delhan
|
||||
ms.reviewer: greglin
|
||||
manager: willchen
|
||||
manager: dcscontentpm
|
||||
---
|
||||
|
||||
# Introduction to page files
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: AccountManagement CSP
|
||||
description: Used to configure settings in the Account Manager service
|
||||
description: Learn about the AccountManagement CSP, which is used to configure settings in the Account Manager service.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: AccountManagement DDF file
|
||||
description: Used to configure settings in the Account Manager service
|
||||
description: View the OMA DM device description framework (DDF) for the AccountManagement configuration service provider. This file is used to configure settings.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Accounts DDF file
|
||||
description: XML file containing the device description framework
|
||||
description: XML file containing the device description framework for the Accounts configuration service provider.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: ApplicationControl CSP DDF
|
||||
description: This topic shows the OMA DM device description framework (DDF) for the **ApplicationControl** configuration service provider. DDF files are used only with OMA DM provisioning XML.
|
||||
description: View the OMA DM device description framework (DDF) for the ApplicationControl configuration service provider. DDF files are used only with OMA DM provisioning XML.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: ApplicationControl CSP
|
||||
description: ApplicationControl CSP
|
||||
description: The ApplicationControl CSP allows you to manage multiple Windows Defender Application Control (WDAC) policies from a MDM server.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -36,8 +36,7 @@ On the desktop and mobile devices, you can use an enrollment certificate or enro
|
||||
> - Bulk-join is not supported in Azure Active Directory Join.
|
||||
> - Bulk enrollment does not work in Intune standalone environment.
|
||||
> - Bulk enrollment works in System Center Configuration Manager (SCCM) + Intune hybrid environment where the ppkg is generated from the SCCM console.
|
||||
|
||||
|
||||
> - To change bulk enrollment settings, login to **AAD**, then **Devices**, and then click **Device Settings**. Change the number under **Maximum number of devices per user**.
|
||||
|
||||
## What you need
|
||||
|
||||
@ -169,4 +168,3 @@ Here are links to step-by-step provisioning topics in Technet.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: CertificateStore DDF file
|
||||
description: This topic shows the OMA DM device description framework (DDF) for the CertificateStore configuration service provider. DDF files are used only with OMA DM provisioning XML.
|
||||
description: Learn about OMA DM device description framework (DDF) for the CertificateStore configuration service provider. DDF files are used with OMA DM provisioning XML.
|
||||
ms.assetid: D9A12D4E-3122-45C3-AD12-CC4FFAEC08B8
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: CleanPC CSP
|
||||
description: The CleanPC configuration service provider (CSP) allows removal of user-installed and pre-installed applications, with the option to persist user data. This CSP was added in Windows 10, version 1703.
|
||||
description: The CleanPC configuration service provider (CSP) allows you to remove user-installed and pre-installed applications, with the option to persist user data.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -90,7 +90,7 @@ The response of the GetUpdateData call returns an array of ServerSyncUpdateData
|
||||
- **Language** – The language code identifier (LCID). For example, en or es.
|
||||
- **Title** – Title of the update. For example, “Windows SharePoint Services 3.0 Service Pack 3 x64 Edition (KB2526305)”
|
||||
- **Description** – Description of the update. For example, “Windows SharePoint Services 3.0 Service Pack 3 (KB2526305) provides the latest updates to Windows SharePoint Services 3.0. After you install this item, you may have to restart your computer. After you have installed this item, it cannot be removed.”
|
||||
- **KBArticleID** – The KB article number for this update that has details regarding the particular update. For example, <http://support.microsoft.com/kb/2902892>.
|
||||
- **KBArticleID** – The KB article number for this update that has details regarding the particular update. For example, <https://support.microsoft.com/kb/2902892>.
|
||||
|
||||
## <a href="" id="recommendedflow"></a>Recommended Flow for Using the Server-Server Sync Protocol
|
||||
|
||||
@ -635,7 +635,7 @@ If a machine has Microsoft Update enabled, any Microsoft Updates in these catego
|
||||
> This policy is available on Windows 10 Pro, Windows 10 Enterprise, Windows 10 Education, and Windows 10 Mobile Enterprise
|
||||
|
||||
> [!Important]
|
||||
> Starting in Windows 10, version 1703 this policy is not supported in Windows 10 Mobile Enteprise and IoT Enterprise.
|
||||
> Starting in Windows 10, version 1703 this policy is not supported in Windows 10 Mobile Enterprise and IoT Enterprise.
|
||||
|
||||
<p style="margin-left: 20px">Allows the device to check for updates from a WSUS server instead of Microsoft Update. This is useful for on-premises MDMs that need to update devices that cannot connect to the Internet.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: DeviceManageability CSP
|
||||
description: The DeviceManageability configuration service provider (CSP) is used retrieve the general information about MDM configuration capabilities on the device. This CSP was added in Windows 10, version 1607.
|
||||
description: The DeviceManageability configuration service provider (CSP) is used retrieve general information about MDM configuration capabilities on the device.
|
||||
ms.assetid: FE563221-D5B5-4EFD-9B60-44FE4066B0D2
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: DeviceStatus CSP
|
||||
description: The DeviceStatus configuration service provider is used by the enterprise to keep track of device inventory and query the state of compliance of these devices with their enterprise policies.
|
||||
description: The DeviceStatus configuration service provider keeps track of device inventory and queries the compliance state of devices within the enterprise.
|
||||
ms.assetid: 039B2010-9290-4A6E-B77B-B2469B482360
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: DMClient CSP
|
||||
description: The DMClient configuration service provider is used to specify additional enterprise-specific mobile device management configuration settings for identifying the device in the enterprise domain, security mitigation for certificate renewal, and server-triggered enterprise unenrollment.
|
||||
description: Understand how the DMClient configuration service provider works. It is used to specify enterprise-specific mobile device management configuration settings.
|
||||
ms.assetid: a5cf35d9-ced0-4087-a247-225f102f2544
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: EAP configuration
|
||||
description: The topic provides a step-by-step guide for creating an Extensible Authentication Protocol (EAP) configuration XML for the VPN profile and information about EAP certificate filtering in Windows 10.
|
||||
description: Learn how to create an Extensible Authentication Protocol (EAP) configuration XML for a VPN profile, plus info about EAP certificate filtering in Windows 10.
|
||||
ms.assetid: DD3F2292-4B4C-4430-A57F-922FED2A8FAE
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: EnrollmentStatusTracking DDF
|
||||
description: This topic shows the OMA DM device description framework (DDF) for the EnrollmentStatusTracking configuration service provider. DDF files are used only with OMA DM provisioning XML.
|
||||
description: View the OMA DM device description framework (DDF) for the EnrollmentStatusTracking configuration service provider. DDF files are used only with OMA DM provisioning XML.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: EnrollmentStatusTracking CSP
|
||||
description: During Autopilot deployment, you can configure the Enrollment Status Page (ESP) to block the device use until the required apps are installed.
|
||||
description: Learn how to perform a hybrid certificate trust deployment of Windows Hello for Business, for systems with no previous installations.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Provide server-side support for mobile app management on Windows
|
||||
description: The Windows version of mobile application management (MAM) is a lightweight solution for managing company data access and security on personal devices. MAM support is built into Windows on top of Windows Information Protection (WIP).
|
||||
description: The Windows version of mobile application management (MAM) is a lightweight solution for managing company data access and security on personal devices.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Mobile device management
|
||||
description: Windows 10 provides an enterprise management solution to help IT pros manage company security policies and business applications, while avoiding compromise of the users’ privacy on their personal devices.
|
||||
description: Windows 10 provides an enterprise-level solution to mobile management, to help IT pros comply with security policies while avoiding compromise of user's privacy
|
||||
MS-HAID:
|
||||
- 'p\_phDeviceMgmt.provisioning\_and\_device\_management'
|
||||
- 'p\_phDeviceMgmt.mobile\_device\_management\_windows\_mdm'
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: MultiSIM DDF file
|
||||
description: XML file containing the device description framework
|
||||
description: XML file containing the device description framework for the MultiSIM configuration service provider.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: What's new in MDM enrollment and management
|
||||
description: This topic provides information about what's new and breaking changes in Windows 10 mobile device management (MDM) enrollment and management experience across all Windows 10 devices.
|
||||
description: Discover what's new and breaking changes in Windows 10 mobile device management (MDM) enrollment and management experience across all Windows 10 devices.
|
||||
MS-HAID:
|
||||
- 'p\_phdevicemgmt.mdm\_enrollment\_and\_management\_overview'
|
||||
- 'p\_phDeviceMgmt.new\_in\_windows\_mdm\_enrollment\_management'
|
||||
|
||||
@ -99,14 +99,5 @@ ADMX Info:
|
||||
<!--/Policy-->
|
||||
<hr/>
|
||||
|
||||
Footnotes:
|
||||
|
||||
- 1 - Added in Windows 10, version 1607.
|
||||
- 2 - Added in Windows 10, version 1703.
|
||||
- 3 - Added in Windows 10, version 1709.
|
||||
- 4 - Added in Windows 10, version 1803.
|
||||
- 5 - Added in Windows 10, version 1809.
|
||||
- 6 - Added in Windows 10, version 1903.
|
||||
|
||||
<!--/Policies-->
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Policy CSP - DeviceHealthMonitoring
|
||||
description: Policy CSP - TimeLanguageSettings
|
||||
description: Learn which DeviceHealthMonitoring policies are supported for your edition of Windows.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Policy CSP - TimeLanguageSettings
|
||||
description: Policy CSP - TimeLanguageSettings
|
||||
description: Learn which TimeLanguageSettings policies are supported for your edition of Windows.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -4248,7 +4248,7 @@ ADMX Info:
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
> [!IMPORTANT]
|
||||
> Starting in Windows 10, version 1703 this policy is not supported in Windows 10 Mobile Enteprise and IoT Mobile.
|
||||
> Starting in Windows 10, version 1703 this policy is not supported in Windows 10 Mobile Enterprise and IoT Mobile.
|
||||
|
||||
Allows the device to check for updates from a WSUS server instead of Microsoft Update. This is useful for on-premises MDMs that need to update devices that cannot connect to the Internet.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Register your free Azure Active Directory subscription
|
||||
description: If you have paid subscriptions to Office 365, Microsoft Dynamics CRM Online, Enterprise Mobility Suite, or other Microsoft services, you have a free subscription to Azure AD.
|
||||
description: Paid subscribers to Office 365, Microsoft Dynamics CRM Online, Enterprise Mobility Suite, or other Microsoft services, have a free subscription to Azure AD.
|
||||
ms.assetid: 97DCD303-BB11-4AFF-84FE-B7F14CDF64F7
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Reporting DDF file
|
||||
description: This topic shows the OMA DM device description framework (DDF) for the Reporting configuration service provider. This CSP was added in Windows 10, version 1511. Support for desktop security auditing was added for the desktop in Windows 10, version 1607.
|
||||
description: View the OMA DM device description framework (DDF) for the Reporting configuration service provider.
|
||||
ms.assetid: 7A5B79DB-9571-4F7C-ABED-D79CD08C1E35
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: TenantLockdown DDF file
|
||||
description: XML file containing the device description framework
|
||||
description: XML file containing the device description framework for the TenantLockdown configuration service provider.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: UnifiedWriteFilter CSP
|
||||
description: The UnifiedWriteFilter (UWF) configuration service provider enables the IT administrator to remotely manage the UWF to help protect physical storage media including any writable storage type.
|
||||
description: The UnifiedWriteFilter (UWF) configuration service provider allows you to remotely manage the UWF. Understand how it helps protect physical storage media.
|
||||
ms.assetid: F4716AC6-0AA5-4A67-AECE-E0F200BA95EB
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Win32CompatibilityAppraiser DDF file
|
||||
description: XML file containing the device description framework
|
||||
description: XML file containing the device description framework for the Win32CompatibilityAppraiser configuration service provider.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Enterprise settings, policies, and app management
|
||||
description: The actual management interaction between the device and server is done via the DM client. The DM client communicates with the enterprise management server via DM v1.2 SyncML syntax.
|
||||
description: The DM client manages the interaction between a device and a server. Learn more about the client-server management workflow.
|
||||
MS-HAID:
|
||||
- 'p\_phdevicemgmt.enterprise\_settings\_\_policies\_\_and\_app\_management'
|
||||
- 'p\_phDeviceMgmt.windows\_mdm\_enterprise\_settings'
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: WindowsSecurityAuditing DDF file
|
||||
description: This topic shows the OMA DM device description framework (DDF) for the WindowsSecurityAuditing configuration service provider. This CSP was added in Windows 10, version 1511.
|
||||
description: View the OMA DM device description framework (DDF) for the WindowsSecurityAuditing configuration service provider.
|
||||
ms.assetid: B1F9A5FA-185B-48C6-A7F4-0F0F23B971F0
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: WiredNetwork CSP
|
||||
description: The WiredNetwork configuration service provider (CSP) is used by the enterprise to configure wired Internet on devices that do not have GP to enable them to access corporate Internet over ethernet.
|
||||
description: The WiredNetwork configuration service provider (CSP) is used by the enterprise to configure wired Internet on devices that do not have GP. Learn how it works.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Change history for Configure Windows 10 (Windows 10)
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
description: This topic lists changes to documentation for configuring Windows 10.
|
||||
description: View changes to documentation for configuring Windows 10.
|
||||
keywords:
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
@ -119,7 +119,7 @@ The following topics were moved into the [Privacy](/windows/privacy/index) libra
|
||||
|
||||
New or changed topic | Description
|
||||
--- | ---
|
||||
[Configure Windows diagnostic data in your organizationspro](https://docs.microsoft.com/windows/privacy/configure-windows-diagnostic-data-in-your-organization) | Updated endpoints.
|
||||
[Configure Windows diagnostic data in your organization](https://docs.microsoft.com/windows/privacy/configure-windows-diagnostic-data-in-your-organization) | Updated endpoints.
|
||||
[Configure cellular settings for tablets and PCs](provisioning-apn.md) | Added instructions for confirming that the settings were applied.
|
||||
|
||||
## March 2018
|
||||
@ -233,4 +233,4 @@ The topics in this library have been updated for Windows 10, version 1703 (also
|
||||
- [Use the Lockdown Designer app to create a Lockdown XML file](mobile-devices/mobile-lockdown-designer.md)
|
||||
- [Add image for secondary tiles](start-secondary-tiles.md)
|
||||
- [Provision PCs with apps](provisioning-packages/provision-pcs-with-apps.md)
|
||||
- [Windows 10, version 1703 basic level Windows diagnostic events and fields](https://docs.microsoft.com/windows/privacy/basic-level-windows-diagnostic-events-and-fields-1703)
|
||||
- [Windows 10, version 1703 basic level Windows diagnostic events and fields](https://docs.microsoft.com/windows/privacy/basic-level-windows-diagnostic-events-and-fields-1703)
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Cortana integration in your business or enterprise (Windows 10)
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
description: The world’s first personal digital assistant helps users get things done, even at work. Cortana includes powerful configuration options specifically to optimize for unique small to medium-sized business and enterprise environments.
|
||||
description: Cortana includes powerful configuration options specifically to optimize for unique small to medium-sized business and enterprise environments.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Create a provisioning package (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.
|
||||
description: Learn how to create a provisioning package for Windows 10. Provisioning packages let you quickly configure a device without having to install a new image.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
|
||||
@ -58,7 +58,7 @@ This procedure explains how to configure digital signage using Kiosk Browser on
|
||||
- Enter a user name and password, and toggle **Auto sign-in** to **Yes**.
|
||||
- Under **Configure the kiosk mode app**, enter the user name for the account that you're creating.
|
||||
- For **App type**, select **Universal Windows App**.
|
||||
- In **Enter the AUMID for the app**, enter `Microsoft.KioskBrowser_8wekyb3d8bbwe`.
|
||||
- In **Enter the AUMID for the app**, enter `Microsoft.KioskBrowser_8wekyb3d8bbwe!App`.
|
||||
11. In the bottom left corner of Windows Configuration Designer, select **Switch to advanced editor**.
|
||||
12. Go to **Runtime settings** > **Policies** > **KioskBrowser**. Let's assume that the URL for your digital signage content is contoso.com/menu.
|
||||
- In **BlockedUrlExceptions**, enter `https://www.contoso.com/menu`.
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
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.
|
||||
description: Learn how to configure the MDT rules engine to reach out to other resources for additional information instead of storing settings directly in the rules engine.
|
||||
ms.assetid: b5ce2360-33cc-4b14-b291-16f75797391b
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -27,7 +27,7 @@ When using MDT, you can assign setting in three distinct ways:
|
||||
- You can prompt the user or technician for information.
|
||||
- You can have MDT generate the settings automatically.
|
||||
|
||||
In order illustrate these three options, let's look at some sample configurations.
|
||||
In order to illustrate these three options, let's look at some sample configurations.
|
||||
|
||||
## <a href="" id="sec02"></a>Sample configurations
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Create a task sequence with Configuration Manager (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.
|
||||
description: 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
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
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.
|
||||
description: Learn how to replace a Windows 7 device with a Windows 10 device. Although the process is similar to performing a refresh, you'll need to backup data externally
|
||||
ms.assetid: acf091c9-f8f4-4131-9845-625691c09a2a
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,177 +1,178 @@
|
||||
---
|
||||
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
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: web services, database
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Use Orchestrator runbooks with MDT
|
||||
|
||||
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.
|
||||
MDT can integrate with System Center 2012 R2 Orchestrator, which is a component that ties the Microsoft System Center products together, as well as other products from both Microsoft and third-party vendors. The difference between using Orchestrator and "normal" web services, is that with Orchestrator you have a rich drag-and-drop style interface when building the solution, and little or no coding is required.
|
||||
|
||||
**Note**
|
||||
If you are licensed to use Orchestrator, we highly recommend that you start using it. To find out more about licensing options for System Center 2012 R2 and Orchestrator, visit the [System Center 2012 R2](https://go.microsoft.com/fwlink/p/?LinkId=619553) website.
|
||||
|
||||
## <a href="" id="sec01"></a>Orchestrator terminology
|
||||
|
||||
Before diving into the core details, here is a quick course in Orchestrator terminology:
|
||||
- **Orchestrator Server.** This is a server that executes runbooks.
|
||||
- **Runbooks.** A runbook is similar to a task sequence; it is a series of instructions based on conditions. Runbooks consist of workflow activities; an activity could be Copy File, Get User from Active Directory, or even Write to Database.
|
||||
- **Orchestrator Designer.** This is where you build the runbooks. In brief, you do that by creating an empty runbook, dragging in the activities you need, and then connecting them in a workflow with conditions and subscriptions.
|
||||
- **Subscriptions.** These are variables that come from an earlier activity in the runbook. So if you first execute an activity in which you type in a computer name, you can then subscribe to that value in the next activity. All these variables are accumulated during the execution of the runbook.
|
||||
- **Orchestrator Console.** This is the Microsoft Silverlight-based web page you can use interactively to execute runbooks. The console listens to TCP port 81 by default.
|
||||
- **Orchestrator web services.** These are the web services you use in the Microsoft Deployment Toolkit to execute runbooks during deployment. The web services listen to TCP port 82 by default.
|
||||
- **Integration packs.** These provide additional workflow activities you can import to integrate with other products or solutions, like the rest of Active Directory, other System Center 2012 R2 products, or Microsoft Exchange Server, to name a few.
|
||||
|
||||
**Note**
|
||||
To find and download additional integration packs, see [Integration Packs for System Center 2012 - Orchestrator](https://go.microsoft.com/fwlink/p/?LinkId=619554).
|
||||
|
||||
## <a href="" id="sec02"></a>Create a sample runbook
|
||||
|
||||
This section assumes you have Orchestrator 2012 R2 installed on a server named OR01. In this section, you create a sample runbook, which is used to log some of the MDT deployment information into a text file on OR01.
|
||||
|
||||
1. On OR01, using File Explorer, create the **E:\\Logfile** folder, and grant Users modify permissions (NTFS).
|
||||
2. In the **E:\\Logfile** folder, create the DeployLog.txt file.
|
||||
**Note**
|
||||
Make sure File Explorer is configured to show known file extensions so the file is not named DeployLog.txt.txt.
|
||||
|
||||
|
||||
|
||||
Figure 23. The DeployLog.txt file.
|
||||
|
||||
3. Using System Center 2012 R2 Orchestrator Runbook Designer, in the **Runbooks** node, create the **1.0 MDT** folder.
|
||||
|
||||
|
||||
|
||||
Figure 24. Folder created in the Runbooks node.
|
||||
|
||||
4. In the **Runbooks** node, right-click the **1.0 MDT** folder, and select **New / Runbook**.
|
||||
5. On the ribbon bar, click **Check Out**.
|
||||
6. Right-click the **New Runbook** label, select **Rename**, and assign the name **MDT Sample**.
|
||||
7. Add (using a drag-and-drop operation) the following items from the **Activities** list to the middle pane:
|
||||
1. Runbook Control / Initialize Data
|
||||
2. Text File Management / Append Line
|
||||
8. Connect **Initialize Data** to **Append Line**.
|
||||
|
||||
|
||||
|
||||
Figure 25. Activities added and connected.
|
||||
|
||||
9. Right-click the **Initialize Data** activity, and select **Properties**
|
||||
10. On **the Initialize Data Properties** page, click **Add**, change **Parameter 1** to **OSDComputerName**, and then click **Finish**.
|
||||
|
||||
|
||||
|
||||
Figure 26. The Initialize Data Properties window.
|
||||
|
||||
11. Right-click the **Append Line** activity, and select **Properties**.
|
||||
12. On the **Append Line Properties** page, in the **File** text box, type **E:\\Logfile\\DeployLog.txt**.
|
||||
13. In the **File** encoding drop-down list, select **ASCII**.
|
||||
14. In the **Append** area, right-click inside the **Text** text box and select **Expand**.
|
||||
|
||||
|
||||
|
||||
Figure 27. Expanding the Text area.
|
||||
|
||||
15. In the blank text box, right-click and select **Subscribe / Published Data**.
|
||||
|
||||
|
||||
|
||||
Figure 28. Subscribing to data.
|
||||
|
||||
16. In the **Published Data** window, select the **OSDComputerName** item, and click **OK**.
|
||||
17. After the **{OSDComputerName from "Initialize Data"}** text, type in **has been deployed at** and, once again, right-click and select **Subscribe / Published Data**.
|
||||
18. In the **Published Data** window, select the **Show common Published Data** check box, select the **Activity end time** item, and click **OK**.
|
||||
|
||||
|
||||
|
||||
Figure 29. The expanded text box after all subscriptions have been added.
|
||||
|
||||
19. On the **Append Line Properties** page, click **Finish**.
|
||||
## <a href="" id="sec03"></a>Test the demo MDT runbook
|
||||
After the runbook is created, you are ready to test it.
|
||||
20. On the ribbon bar, click **Runbook Tester**.
|
||||
21. Click **Run**, and in the **Initialize Data Parameters** dialog box, use the following setting and then click **OK**:
|
||||
- OSDComputerName: PC0010
|
||||
22. Verify that all activities are green (for additional information, see each target).
|
||||
23. Close the **Runbook Tester**.
|
||||
24. On the ribbon bar, click **Check In**.
|
||||
|
||||
|
||||
|
||||
Figure 30. All tests completed.
|
||||
|
||||
## Use the MDT demo runbook from MDT
|
||||
|
||||
1. On MDT01, using the Deployment Workbench, in the MDT Production deployment share, select the **Task Sequences** node, and create a folder named **Orchestrator**.
|
||||
2. Right-click the **Orchestrator** node, and select **New Task Sequence**. Use the following settings for the New Task Sequence Wizard:
|
||||
1. Task sequence ID: OR001
|
||||
2. Task sequence name: Orchestrator Sample
|
||||
3. Task sequence comments: <blank>
|
||||
4. Template: Custom Task Sequence
|
||||
3. In the **Orchestrator** node, double-click the **Orchestrator Sample** task sequence, and then select the **Task Sequence** tab.
|
||||
4. Remove the default **Application Install** action.
|
||||
5. Add a **Gather** action and select the **Gather only local data (do not process rules)** option.
|
||||
6. After the **Gather** action, add a **Set Task Sequence Variable** action with the following settings:
|
||||
1. Name: Set Task Sequence Variable
|
||||
2. Task Sequence Variable: OSDComputerName
|
||||
3. Value: %hostname%
|
||||
7. After the **Set Task Sequence Variable** action, add a new **Execute Orchestrator Runbook** action with the following settings:
|
||||
1. Orchestrator Server: OR01.contoso.com
|
||||
2. Use Browse to select **1.0 MDT / MDT Sample**.
|
||||
8. Click **OK**.
|
||||
|
||||
|
||||
|
||||
Figure 31. The ready-made task sequence.
|
||||
|
||||
## Run the orchestrator sample task sequence
|
||||
|
||||
Since this task sequence just starts a runbook, you can test this on the PC0001 client that you used for the MDT simulation environment.
|
||||
**Note**
|
||||
Make sure the account you are using has permissions to run runbooks on the Orchestrator server. For more information about runbook permissions, see [Runbook Permissions](https://go.microsoft.com/fwlink/p/?LinkId=619555).
|
||||
|
||||
1. On PC0001, log on as **CONTOSO\\MDT\_BA**.
|
||||
2. Using an elevated command prompt (run as Administrator), type the following command:
|
||||
|
||||
``` syntax
|
||||
cscript \\MDT01\MDTProduction$\Scripts\Litetouch.vbs
|
||||
```
|
||||
3. Complete the Windows Deployment Wizard using the following information:
|
||||
1. Task Sequence: Orchestrator Sample
|
||||
2. Credentials:
|
||||
1. User Name: MDT\_BA
|
||||
2. Password: P@ssw0rd
|
||||
3. Domain: CONTOSO
|
||||
4. Wait until the task sequence is completed and then verify that the DeployLog.txt file in the E:\\Logfile folder on OR01 was updated.
|
||||
|
||||
|
||||
|
||||
Figure 32. The ready-made task sequence.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Set up MDT for BitLocker](set-up-mdt-for-bitlocker.md)
|
||||
|
||||
[Configure MDT deployment share rules](configure-mdt-deployment-share-rules.md)
|
||||
|
||||
[Configure MDT for UserExit scripts](configure-mdt-for-userexit-scripts.md)
|
||||
|
||||
[Simulate a Windows10 deployment in a test environment](simulate-a-windows-10-deployment-in-a-test-environment.md)
|
||||
|
||||
[Use the MDT database to stage Windows 10 deployment information](use-the-mdt-database-to-stage-windows-10-deployment-information.md)
|
||||
|
||||
[Assign applications using roles in MDT](assign-applications-using-roles-in-mdt.md)
|
||||
|
||||
[Use web services in MDT](use-web-services-in-mdt.md)
|
||||
---
|
||||
title: Use Orchestrator runbooks with MDT (Windows 10)
|
||||
description: Learn 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
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: web services, database
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Use Orchestrator runbooks with MDT
|
||||
|
||||
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.
|
||||
MDT can integrate with System Center 2012 R2 Orchestrator, which is a component that ties the Microsoft System Center products together, as well as other products from both Microsoft and third-party vendors. The difference between using Orchestrator and "normal" web services, is that with Orchestrator you have a rich drag-and-drop style interface when building the solution, and little or no coding is required.
|
||||
|
||||
**Note**
|
||||
If you are licensed to use Orchestrator, we highly recommend that you start using it. To find out more about licensing options for System Center 2012 R2 and Orchestrator, visit the [System Center 2012 R2](https://go.microsoft.com/fwlink/p/?LinkId=619553) website.
|
||||
|
||||
## <a href="" id="sec01"></a>Orchestrator terminology
|
||||
|
||||
Before diving into the core details, here is a quick course in Orchestrator terminology:
|
||||
- **Orchestrator Server.** This is a server that executes runbooks.
|
||||
- **Runbooks.** A runbook is similar to a task sequence; it is a series of instructions based on conditions. Runbooks consist of workflow activities; an activity could be Copy File, Get User from Active Directory, or even Write to Database.
|
||||
- **Orchestrator Designer.** This is where you build the runbooks. In brief, you do that by creating an empty runbook, dragging in the activities you need, and then connecting them in a workflow with conditions and subscriptions.
|
||||
- **Subscriptions.** These are variables that come from an earlier activity in the runbook. So if you first execute an activity in which you type in a computer name, you can then subscribe to that value in the next activity. All these variables are accumulated during the execution of the runbook.
|
||||
- **Orchestrator Console.** This is the Microsoft Silverlight-based web page you can use interactively to execute runbooks. The console listens to TCP port 81 by default.
|
||||
- **Orchestrator web services.** These are the web services you use in the Microsoft Deployment Toolkit to execute runbooks during deployment. The web services listen to TCP port 82 by default.
|
||||
- **Integration packs.** These provide additional workflow activities you can import to integrate with other products or solutions, like the rest of Active Directory, other System Center 2012 R2 products, or Microsoft Exchange Server, to name a few.
|
||||
|
||||
**Note**
|
||||
To find and download additional integration packs, see [Integration Packs for System Center 2012 - Orchestrator](https://go.microsoft.com/fwlink/p/?LinkId=619554).
|
||||
|
||||
## <a href="" id="sec02"></a>Create a sample runbook
|
||||
|
||||
This section assumes you have Orchestrator 2012 R2 installed on a server named OR01. In this section, you create a sample runbook, which is used to log some of the MDT deployment information into a text file on OR01.
|
||||
|
||||
1. On OR01, using File Explorer, create the **E:\\Logfile** folder, and grant Users modify permissions (NTFS).
|
||||
2. In the **E:\\Logfile** folder, create the DeployLog.txt file.
|
||||
**Note**
|
||||
Make sure File Explorer is configured to show known file extensions so the file is not named DeployLog.txt.txt.
|
||||
|
||||
|
||||
|
||||
Figure 23. The DeployLog.txt file.
|
||||
|
||||
3. Using System Center 2012 R2 Orchestrator Runbook Designer, in the **Runbooks** node, create the **1.0 MDT** folder.
|
||||
|
||||
|
||||
|
||||
Figure 24. Folder created in the Runbooks node.
|
||||
|
||||
4. In the **Runbooks** node, right-click the **1.0 MDT** folder, and select **New / Runbook**.
|
||||
5. On the ribbon bar, click **Check Out**.
|
||||
6. Right-click the **New Runbook** label, select **Rename**, and assign the name **MDT Sample**.
|
||||
7. Add (using a drag-and-drop operation) the following items from the **Activities** list to the middle pane:
|
||||
1. Runbook Control / Initialize Data
|
||||
2. Text File Management / Append Line
|
||||
8. Connect **Initialize Data** to **Append Line**.
|
||||
|
||||
|
||||
|
||||
Figure 25. Activities added and connected.
|
||||
|
||||
9. Right-click the **Initialize Data** activity, and select **Properties**
|
||||
10. On **the Initialize Data Properties** page, click **Add**, change **Parameter 1** to **OSDComputerName**, and then click **Finish**.
|
||||
|
||||
|
||||
|
||||
Figure 26. The Initialize Data Properties window.
|
||||
|
||||
11. Right-click the **Append Line** activity, and select **Properties**.
|
||||
12. On the **Append Line Properties** page, in the **File** text box, type **E:\\Logfile\\DeployLog.txt**.
|
||||
13. In the **File** encoding drop-down list, select **ASCII**.
|
||||
14. In the **Append** area, right-click inside the **Text** text box and select **Expand**.
|
||||
|
||||
|
||||
|
||||
Figure 27. Expanding the Text area.
|
||||
|
||||
15. In the blank text box, right-click and select **Subscribe / Published Data**.
|
||||
|
||||
|
||||
|
||||
Figure 28. Subscribing to data.
|
||||
|
||||
16. In the **Published Data** window, select the **OSDComputerName** item, and click **OK**.
|
||||
17. After the **{OSDComputerName from "Initialize Data"}** text, type in **has been deployed at** and, once again, right-click and select **Subscribe / Published Data**.
|
||||
18. In the **Published Data** window, select the **Show common Published Data** check box, select the **Activity end time** item, and click **OK**.
|
||||
|
||||
|
||||
|
||||
Figure 29. The expanded text box after all subscriptions have been added.
|
||||
|
||||
19. On the **Append Line Properties** page, click **Finish**.
|
||||
## <a href="" id="sec03"></a>Test the demo MDT runbook
|
||||
After the runbook is created, you are ready to test it.
|
||||
20. On the ribbon bar, click **Runbook Tester**.
|
||||
21. Click **Run**, and in the **Initialize Data Parameters** dialog box, use the following setting and then click **OK**:
|
||||
- OSDComputerName: PC0010
|
||||
22. Verify that all activities are green (for additional information, see each target).
|
||||
23. Close the **Runbook Tester**.
|
||||
24. On the ribbon bar, click **Check In**.
|
||||
|
||||
|
||||
|
||||
Figure 30. All tests completed.
|
||||
|
||||
## Use the MDT demo runbook from MDT
|
||||
|
||||
1. On MDT01, using the Deployment Workbench, in the MDT Production deployment share, select the **Task Sequences** node, and create a folder named **Orchestrator**.
|
||||
2. Right-click the **Orchestrator** node, and select **New Task Sequence**. Use the following settings for the New Task Sequence Wizard:
|
||||
1. Task sequence ID: OR001
|
||||
2. Task sequence name: Orchestrator Sample
|
||||
3. Task sequence comments: <blank>
|
||||
4. Template: Custom Task Sequence
|
||||
3. In the **Orchestrator** node, double-click the **Orchestrator Sample** task sequence, and then select the **Task Sequence** tab.
|
||||
4. Remove the default **Application Install** action.
|
||||
5. Add a **Gather** action and select the **Gather only local data (do not process rules)** option.
|
||||
6. After the **Gather** action, add a **Set Task Sequence Variable** action with the following settings:
|
||||
1. Name: Set Task Sequence Variable
|
||||
2. Task Sequence Variable: OSDComputerName
|
||||
3. Value: %hostname%
|
||||
7. After the **Set Task Sequence Variable** action, add a new **Execute Orchestrator Runbook** action with the following settings:
|
||||
1. Orchestrator Server: OR01.contoso.com
|
||||
2. Use Browse to select **1.0 MDT / MDT Sample**.
|
||||
8. Click **OK**.
|
||||
|
||||
|
||||
|
||||
Figure 31. The ready-made task sequence.
|
||||
|
||||
## Run the orchestrator sample task sequence
|
||||
|
||||
Since this task sequence just starts a runbook, you can test this on the PC0001 client that you used for the MDT simulation environment.
|
||||
**Note**
|
||||
Make sure the account you are using has permissions to run runbooks on the Orchestrator server. For more information about runbook permissions, see [Runbook Permissions](https://go.microsoft.com/fwlink/p/?LinkId=619555).
|
||||
|
||||
1. On PC0001, log on as **CONTOSO\\MDT\_BA**.
|
||||
2. Using an elevated command prompt (run as Administrator), type the following command:
|
||||
|
||||
``` syntax
|
||||
cscript \\MDT01\MDTProduction$\Scripts\Litetouch.vbs
|
||||
```
|
||||
3. Complete the Windows Deployment Wizard using the following information:
|
||||
1. Task Sequence: Orchestrator Sample
|
||||
2. Credentials:
|
||||
1. User Name: MDT\_BA
|
||||
2. Password: P@ssw0rd
|
||||
3. Domain: CONTOSO
|
||||
4. Wait until the task sequence is completed and then verify that the DeployLog.txt file in the E:\\Logfile folder on OR01 was updated.
|
||||
|
||||
|
||||
|
||||
Figure 32. The ready-made task sequence.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Set up MDT for BitLocker](set-up-mdt-for-bitlocker.md)
|
||||
|
||||
[Configure MDT deployment share rules](configure-mdt-deployment-share-rules.md)
|
||||
|
||||
[Configure MDT for UserExit scripts](configure-mdt-for-userexit-scripts.md)
|
||||
|
||||
[Simulate a Windows10 deployment in a test environment](simulate-a-windows-10-deployment-in-a-test-environment.md)
|
||||
|
||||
[Use the MDT database to stage Windows 10 deployment information](use-the-mdt-database-to-stage-windows-10-deployment-information.md)
|
||||
|
||||
[Assign applications using roles in MDT](assign-applications-using-roles-in-mdt.md)
|
||||
|
||||
[Use web services in MDT](use-web-services-in-mdt.md)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Use MDT database to stage Windows 10 deployment info (Windows 10)
|
||||
description: This topic is designed to teach you how to use the MDT database to pre-stage information on your Windows 10 deployment in a Microsoft SQL Server 2012 SP1 Express database, rather than include the information in a text file (CustomSettings.ini).
|
||||
description: Learn how to use the MDT database to pre-stage information on your Windows 10 deployment in a Microsoft SQL Server 2012 SP1 Express database.
|
||||
ms.assetid: 8956ab54-90ba-45d3-a384-4fdec72c4d46
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
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.
|
||||
description: 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
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,110 +1,111 @@
|
||||
---
|
||||
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
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: deploy, task sequence
|
||||
ms.prod: w10
|
||||
ms.localizationpriority: medium
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.date: 07/27/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10 versions 1507, 1511
|
||||
|
||||
>[!IMPORTANT]
|
||||
>For instructions to deploy the most recent version of Windows 10 with Configuration Manager, see [Scenarios to deploy enterprise operating systems with System Center Configuration Manager](https://docs.microsoft.com/sccm/osd/deploy-use/scenarios-to-deploy-enterprise-operating-systems).
|
||||
>Configuration Manager 2012 and 2012 R2 provide support for Windows 10 versions 1507 and 1511 only. Later versions of Windows 10 require an updated Configuration Manager release. For a list of Configuration Manager versions and the corresponding Windows 10 client versions that are supported, see [Support for Windows 10 for System Center Configuration Manager](https://docs.microsoft.com/sccm/core/plan-design/configs/support-for-windows-10).
|
||||
|
||||
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. Even though the Windows PE boot image and the Windows 10 operating system contain many out-of-the-box drivers, it is likely you will have to add new or updated drivers to support all your hardware. In this section, you import drivers for both Windows PE and the full Windows 10 operating system.
|
||||
|
||||
For the purposes of this topic, we will use CM01, a machine running Windows Server 2012 R2 Standard that is a member of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
## <a href="" id="sec01"></a>Add drivers for Windows PE
|
||||
|
||||
|
||||
This section will show you how to import some network and storage drivers for Windows PE. This section assumes you have downloaded some drivers to the E:\\Sources\\OSD\\DriverSources\\WinPE x64 folder on CM01.
|
||||
|
||||
1. On CM01, using the Configuration Manager Console, in the Software Library workspace, right-click the **Drivers** node and select **Import Driver**.
|
||||
|
||||
2. In the Import New Driver Wizard, on the **Specify a location to import driver** page, below the Import all drivers in the following network path (UNC) option, browse to the **\\\\CM01\\Sources$\\OSD\\DriverSources\\WinPE x64** folder and click **Next**.
|
||||
|
||||
3. On the **Specify the details for the imported driver** page, click **Categories**, create a category named **WinPE x64**, and then click **Next**.
|
||||
|
||||
4. On the **Select the packages to add the imported driver** page, click **Next**.
|
||||
|
||||
5. On the **Select drivers to include in the boot image** page, select the **Zero Touch WinPE x64** boot image. Also select the **Update distribution points when finished** check box, and click **Next** twice.
|
||||
|
||||
|
||||
|
||||
*Figure 21. Add drivers to Windows PE*
|
||||
|
||||
>[!NOTE]
|
||||
>The Updating Boot Image part of the wizard will appear to hang when displaying Done. It will complete in a minute or two.
|
||||
|
||||
|
||||
## <a href="" id="sec02"></a>Add drivers for Windows 10
|
||||
|
||||
|
||||
This section illustrates how to add drivers for Windows 10 through an example in which you want to import Windows 10 drivers for the HP EliteBook 8560w model. For the purposes of this section, we assume that you have downloaded the Windows 10 drivers for the HP EliteBook 8560w model and copied them to the E:\\Sources\\OSD\\DriverSources\\Windows 10 x64\\HP EliteBook 8560w folder on CM01.
|
||||
|
||||
1. On CM01, using the Configuration Manager Console, right-click the **Drivers** folder and select **Import Driver**.
|
||||
|
||||
2. In the Import New Driver Wizard, on the **Specify a location to import driver** page, below the Import all drivers in the following network path (UNC) option, browse to the **\\\\CM01\\Sources$\\OSD\\DriverSources\\Windows 10 x64\\HP EliteBook 8560w** folder and click **Next**.
|
||||
|
||||
3. On the **Specify the details for the imported driver** page, click **Categories**, create a category named Windows 10 x64 - HP EliteBook 8560w, and then click **Next**.
|
||||
|
||||
|
||||
|
||||
*Figure 22. Create driver categories*
|
||||
|
||||
4. On the **Select the packages to add the imported driver** page, click **New Package**, use the following settings for the package, and then click **Next**:
|
||||
|
||||
* Name: Windows 10 x64 - HP EliteBook 8560w
|
||||
|
||||
* Path: \\\\CM01\\Sources$\\OSD\\DriverPackages\\Windows 10 x64\\HP EliteBook 8560w
|
||||
|
||||
>[!NOTE]
|
||||
>The package path does not yet exist, so you have to type it in. The wizard will create the new package in that folder.
|
||||
|
||||
|
||||
5. On the **Select drivers to include in the boot image** page, do not select anything, and click **Next** twice. After the package has been created, click **Close**.
|
||||
|
||||
>[!NOTE]
|
||||
>If you want to monitor the driver import process more closely, you can open the SMSProv.log file during driver import.
|
||||
|
||||
|
||||
|
||||
*Figure 23. Drivers imported and a new driver package created*
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Integrate Configuration Manager with MDT](../deploy-windows-mdt/integrate-configuration-manager-with-mdt.md)
|
||||
|
||||
|
||||
[Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
||||
|
||||
[Create a custom Windows PE boot image with Configuration Manager](create-a-custom-windows-pe-boot-image-with-configuration-manager.md)
|
||||
|
||||
[Add a Windows 10 operating system image using Configuration Manager](add-a-windows-10-operating-system-image-using-configuration-manager.md)
|
||||
|
||||
[Create an application to deploy with Windows 10 using Configuration Manager](create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Create a task sequence with Configuration Manager and MDT](../deploy-windows-mdt/create-a-task-sequence-with-configuration-manager-and-mdt.md)
|
||||
|
||||
[Deploy Windows 10 using PXE and Configuration Manager](deploy-windows-10-using-pxe-and-configuration-manager.md)
|
||||
|
||||
[Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
---
|
||||
title: Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager (Windows 10)
|
||||
description: Learn how to configure the Windows Preinstallation Environment (Windows PE) to include required network and storage drivers.
|
||||
ms.assetid: 97b3ea46-28d9-407e-8c42-ded2e45e8d5c
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: deploy, task sequence
|
||||
ms.prod: w10
|
||||
ms.localizationpriority: medium
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 07/27/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10 versions 1507, 1511
|
||||
|
||||
>[!IMPORTANT]
|
||||
>For instructions to deploy the most recent version of Windows 10 with Configuration Manager, see [Scenarios to deploy enterprise operating systems with System Center Configuration Manager](https://docs.microsoft.com/sccm/osd/deploy-use/scenarios-to-deploy-enterprise-operating-systems).
|
||||
>Configuration Manager 2012 and 2012 R2 provide support for Windows 10 versions 1507 and 1511 only. Later versions of Windows 10 require an updated Configuration Manager release. For a list of Configuration Manager versions and the corresponding Windows 10 client versions that are supported, see [Support for Windows 10 for System Center Configuration Manager](https://docs.microsoft.com/sccm/core/plan-design/configs/support-for-windows-10).
|
||||
|
||||
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. Even though the Windows PE boot image and the Windows 10 operating system contain many out-of-the-box drivers, it is likely you will have to add new or updated drivers to support all your hardware. In this section, you import drivers for both Windows PE and the full Windows 10 operating system.
|
||||
|
||||
For the purposes of this topic, we will use CM01, a machine running Windows Server 2012 R2 Standard that is a member of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
## <a href="" id="sec01"></a>Add drivers for Windows PE
|
||||
|
||||
|
||||
This section will show you how to import some network and storage drivers for Windows PE. This section assumes you have downloaded some drivers to the E:\\Sources\\OSD\\DriverSources\\WinPE x64 folder on CM01.
|
||||
|
||||
1. On CM01, using the Configuration Manager Console, in the Software Library workspace, right-click the **Drivers** node and select **Import Driver**.
|
||||
|
||||
2. In the Import New Driver Wizard, on the **Specify a location to import driver** page, below the Import all drivers in the following network path (UNC) option, browse to the **\\\\CM01\\Sources$\\OSD\\DriverSources\\WinPE x64** folder and click **Next**.
|
||||
|
||||
3. On the **Specify the details for the imported driver** page, click **Categories**, create a category named **WinPE x64**, and then click **Next**.
|
||||
|
||||
4. On the **Select the packages to add the imported driver** page, click **Next**.
|
||||
|
||||
5. On the **Select drivers to include in the boot image** page, select the **Zero Touch WinPE x64** boot image. Also select the **Update distribution points when finished** check box, and click **Next** twice.
|
||||
|
||||
|
||||
|
||||
*Figure 21. Add drivers to Windows PE*
|
||||
|
||||
>[!NOTE]
|
||||
>The Updating Boot Image part of the wizard will appear to hang when displaying Done. It will complete in a minute or two.
|
||||
|
||||
|
||||
## <a href="" id="sec02"></a>Add drivers for Windows 10
|
||||
|
||||
|
||||
This section illustrates how to add drivers for Windows 10 through an example in which you want to import Windows 10 drivers for the HP EliteBook 8560w model. For the purposes of this section, we assume that you have downloaded the Windows 10 drivers for the HP EliteBook 8560w model and copied them to the E:\\Sources\\OSD\\DriverSources\\Windows 10 x64\\HP EliteBook 8560w folder on CM01.
|
||||
|
||||
1. On CM01, using the Configuration Manager Console, right-click the **Drivers** folder and select **Import Driver**.
|
||||
|
||||
2. In the Import New Driver Wizard, on the **Specify a location to import driver** page, below the Import all drivers in the following network path (UNC) option, browse to the **\\\\CM01\\Sources$\\OSD\\DriverSources\\Windows 10 x64\\HP EliteBook 8560w** folder and click **Next**.
|
||||
|
||||
3. On the **Specify the details for the imported driver** page, click **Categories**, create a category named Windows 10 x64 - HP EliteBook 8560w, and then click **Next**.
|
||||
|
||||
|
||||
|
||||
*Figure 22. Create driver categories*
|
||||
|
||||
4. On the **Select the packages to add the imported driver** page, click **New Package**, use the following settings for the package, and then click **Next**:
|
||||
|
||||
* Name: Windows 10 x64 - HP EliteBook 8560w
|
||||
|
||||
* Path: \\\\CM01\\Sources$\\OSD\\DriverPackages\\Windows 10 x64\\HP EliteBook 8560w
|
||||
|
||||
>[!NOTE]
|
||||
>The package path does not yet exist, so you have to type it in. The wizard will create the new package in that folder.
|
||||
|
||||
|
||||
5. On the **Select drivers to include in the boot image** page, do not select anything, and click **Next** twice. After the package has been created, click **Close**.
|
||||
|
||||
>[!NOTE]
|
||||
>If you want to monitor the driver import process more closely, you can open the SMSProv.log file during driver import.
|
||||
|
||||
|
||||
|
||||
*Figure 23. Drivers imported and a new driver package created*
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Integrate Configuration Manager with MDT](../deploy-windows-mdt/integrate-configuration-manager-with-mdt.md)
|
||||
|
||||
|
||||
[Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
||||
|
||||
[Create a custom Windows PE boot image with Configuration Manager](create-a-custom-windows-pe-boot-image-with-configuration-manager.md)
|
||||
|
||||
[Add a Windows 10 operating system image using Configuration Manager](add-a-windows-10-operating-system-image-using-configuration-manager.md)
|
||||
|
||||
[Create an application to deploy with Windows 10 using Configuration Manager](create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Create a task sequence with Configuration Manager and MDT](../deploy-windows-mdt/create-a-task-sequence-with-configuration-manager-and-mdt.md)
|
||||
|
||||
[Deploy Windows 10 using PXE and Configuration Manager](deploy-windows-10-using-pxe-and-configuration-manager.md)
|
||||
|
||||
[Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
@ -1,117 +1,118 @@
|
||||
---
|
||||
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
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: tool, customize, deploy, boot image
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Create a custom Windows PE boot image with Configuration Manager
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10 versions 1507, 1511
|
||||
|
||||
>[!IMPORTANT]
|
||||
>For instructions to deploy the most recent version of Windows 10 with Configuration Manager, see [Scenarios to deploy enterprise operating systems with System Center Configuration Manager](https://docs.microsoft.com/sccm/osd/deploy-use/scenarios-to-deploy-enterprise-operating-systems).
|
||||
>Configuration Manager 2012 and 2012 R2 provide support for Windows 10 versions 1507 and 1511 only. Later versions of Windows 10 require an updated Configuration Manager release. For a list of Configuration Manager versions and the corresponding Windows 10 client versions that are supported, see [Support for Windows 10 for System Center Configuration Manager](https://docs.microsoft.com/sccm/core/plan-design/configs/support-for-windows-10).
|
||||
|
||||
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. This topic shows you how to create a custom Windows PE 5.0 boot image with the Microsoft Deployment Toolkit (MDT) wizard. You can also add the Microsoft Diagnostics and Recovery Toolset (DaRT) 10 to the boot image as part of the boot image creation process.
|
||||
|
||||
For the purposes of this topic, we will use two machines: DC01 and CM01. DC01 is a domain controller and CM01 is a machine running Windows Server 2012 R2 Standard. Both are members of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
## <a href="" id="sec01"></a>Add DaRT 10 files and prepare to brand the boot image
|
||||
|
||||
|
||||
The steps below outline the process for adding DaRT 10 installation files to the MDT installation directory. You also copy a custom background image to be used later. We assume you have downloaded Microsoft Desktop Optimization Pack (MDOP) 2015 and copied the x64 version of MSDaRT10.msi to the C:\\Setup\\DaRT 10 folder. We also assume you have created a custom background image and saved it in C:\\Setup\\Branding on CM01. In this section, we use a custom background image named ContosoBackground.bmp.
|
||||
|
||||
1. Install DaRT 10 (C:\\Setup\\DaRT 10\\MSDaRT10.msi) using the default settings.
|
||||
|
||||
2. Using File Explorer, navigate to the **C:\\Program Files\\Microsoft DaRT\\v10** folder.
|
||||
|
||||
3. Copy the Toolsx64.cab file to the **C:\\Program Files\\Microsoft Deployment Toolkit\\Templates\\Distribution\\Tools\\x64** folder.
|
||||
|
||||
4. Copy the Toolsx86.cab file to the **C:\\Program Files\\Microsoft Deployment Toolkit\\Templates\\Distribution\\Tools\\x86** folder.
|
||||
|
||||
5. Using File Explorer, navigate to the **C:\\Setup** folder.
|
||||
|
||||
6. Copy the **Branding** folder to **E:\\Sources\\OSD**.
|
||||
|
||||
## <a href="" id="sec02"></a>Create a boot image for Configuration Manager using the MDT wizard
|
||||
|
||||
|
||||
By using the MDT wizard to create the boot image in Configuration Manager, you gain additional options for adding components and features to the boot image. In this section, you create a boot image for Configuration Manager using the MDT wizard.
|
||||
|
||||
1. Using the Configuration Manager Console, in the Software Library workspace, expand **Operating Systems**, right-click **Boot Images**, and select **Create Boot Image using MDT**.
|
||||
|
||||
2. On the **Package Source** page, in the **Package source folder to be created (UNC Path):** text box, type **\\\\CM01\\Sources$\\OSD\\Boot\\Zero Touch WinPE x64** and click **Next**.
|
||||
|
||||
>[!NOTE]
|
||||
>The Zero Touch WinPE x64 folder does not yet exist. The folder will be created later by the wizard.
|
||||
|
||||
3. On the **General Settings** page, assign the name **Zero Touch WinPE x64** and click **Next**.
|
||||
|
||||
4. On the **Options** page, select the **x64** platform, and click **Next**.
|
||||
|
||||
5. On the **Components** page, in addition to the default selected **Microsoft Data Access Components (MDAC/ADO)** support, select the **Microsoft Diagnostics and Recovery Toolkit (DaRT)** check box.
|
||||
|
||||
|
||||
|
||||
Figure 15. Add the DaRT component to the Configuration Manager boot image.
|
||||
|
||||
6. On the **Customization** page, select the **Use a custom background bitmap file** check box, and in the **UNC path:** text box, browse to **\\\\CM01\\Sources$\\OSD\\Branding\\ ContosoBackground.bmp**. Then click **Next** twice.
|
||||
|
||||
>[!NOTE]
|
||||
>It will take a few minutes to generate the boot image.
|
||||
|
||||
7. Distribute the boot image to the CM01 distribution point by selecting the **Boot images** node, right-clicking the **Zero Touch WinPE x64** boot image, and selecting **Distribute Content**.
|
||||
|
||||
8. In the Distribute Content Wizard, add the CM01 distribution point, and complete the wizard.
|
||||
|
||||
9. Using Configuration Manager Trace, review the E:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file. Do not continue until you can see that the boot image is distributed. Look for the line that reads STATMSG: ID=2301. You also can view Content Status in the Configuration Manager Console by selecting **the Zero Touch WinPE x86** boot image.
|
||||
|
||||
|
||||
|
||||
Figure 16. Content status for the Zero Touch WinPE x64 boot image
|
||||
|
||||
10. Using the Configuration Manager Console, right-click the **Zero Touch WinPE x64** boot image and select **Properties**.
|
||||
|
||||
11. In the **Data Source** tab, select the **Deploy this boot image from the PXE-enabled distribution point** check box, and click **OK**.
|
||||
|
||||
12. Using Configuration Manager Trace, review the E:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file and look for this text: Expanding PS10000B to E:\\RemoteInstall\\SMSImages.
|
||||
|
||||
13. Review the **E:\\RemoteInstall\\SMSImages** folder. You should see three folders containing boot images. Two are from the default boot images, and the third folder (PS10000B) is from your new boot image with DaRT.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Integrate Configuration Manager with MDT](../deploy-windows-mdt/integrate-configuration-manager-with-mdt.md)
|
||||
|
||||
[Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
||||
|
||||
[Add a Windows 10 operating system image using Configuration Manager](add-a-windows-10-operating-system-image-using-configuration-manager.md)
|
||||
|
||||
[Create an application to deploy with Windows 10 using Configuration Manager](create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md)
|
||||
|
||||
[Create a task sequence with Configuration Manager and MDT](../deploy-windows-mdt/create-a-task-sequence-with-configuration-manager-and-mdt.md)
|
||||
|
||||
[Deploy Windows 10 using PXE and Configuration Manager](deploy-windows-10-using-pxe-and-configuration-manager.md)
|
||||
|
||||
[Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
title: Create a custom Windows PE boot image with Configuration Manager (Windows 10)
|
||||
description: Microsoft System Center 2012 R2 Configuration Manager can create custom Windows Preinstallation Environment (Windows PE) boot images with extra features.
|
||||
ms.assetid: b9e96974-324d-4fa4-b0ce-33cfc49c4809
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: tool, customize, deploy, boot image
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Create a custom Windows PE boot image with Configuration Manager
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10 versions 1507, 1511
|
||||
|
||||
>[!IMPORTANT]
|
||||
>For instructions to deploy the most recent version of Windows 10 with Configuration Manager, see [Scenarios to deploy enterprise operating systems with System Center Configuration Manager](https://docs.microsoft.com/sccm/osd/deploy-use/scenarios-to-deploy-enterprise-operating-systems).
|
||||
>Configuration Manager 2012 and 2012 R2 provide support for Windows 10 versions 1507 and 1511 only. Later versions of Windows 10 require an updated Configuration Manager release. For a list of Configuration Manager versions and the corresponding Windows 10 client versions that are supported, see [Support for Windows 10 for System Center Configuration Manager](https://docs.microsoft.com/sccm/core/plan-design/configs/support-for-windows-10).
|
||||
|
||||
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. This topic shows you how to create a custom Windows PE 5.0 boot image with the Microsoft Deployment Toolkit (MDT) wizard. You can also add the Microsoft Diagnostics and Recovery Toolset (DaRT) 10 to the boot image as part of the boot image creation process.
|
||||
|
||||
For the purposes of this topic, we will use two machines: DC01 and CM01. DC01 is a domain controller and CM01 is a machine running Windows Server 2012 R2 Standard. Both are members of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
## <a href="" id="sec01"></a>Add DaRT 10 files and prepare to brand the boot image
|
||||
|
||||
|
||||
The steps below outline the process for adding DaRT 10 installation files to the MDT installation directory. You also copy a custom background image to be used later. We assume you have downloaded Microsoft Desktop Optimization Pack (MDOP) 2015 and copied the x64 version of MSDaRT10.msi to the C:\\Setup\\DaRT 10 folder. We also assume you have created a custom background image and saved it in C:\\Setup\\Branding on CM01. In this section, we use a custom background image named ContosoBackground.bmp.
|
||||
|
||||
1. Install DaRT 10 (C:\\Setup\\DaRT 10\\MSDaRT10.msi) using the default settings.
|
||||
|
||||
2. Using File Explorer, navigate to the **C:\\Program Files\\Microsoft DaRT\\v10** folder.
|
||||
|
||||
3. Copy the Toolsx64.cab file to the **C:\\Program Files\\Microsoft Deployment Toolkit\\Templates\\Distribution\\Tools\\x64** folder.
|
||||
|
||||
4. Copy the Toolsx86.cab file to the **C:\\Program Files\\Microsoft Deployment Toolkit\\Templates\\Distribution\\Tools\\x86** folder.
|
||||
|
||||
5. Using File Explorer, navigate to the **C:\\Setup** folder.
|
||||
|
||||
6. Copy the **Branding** folder to **E:\\Sources\\OSD**.
|
||||
|
||||
## <a href="" id="sec02"></a>Create a boot image for Configuration Manager using the MDT wizard
|
||||
|
||||
|
||||
By using the MDT wizard to create the boot image in Configuration Manager, you gain additional options for adding components and features to the boot image. In this section, you create a boot image for Configuration Manager using the MDT wizard.
|
||||
|
||||
1. Using the Configuration Manager Console, in the Software Library workspace, expand **Operating Systems**, right-click **Boot Images**, and select **Create Boot Image using MDT**.
|
||||
|
||||
2. On the **Package Source** page, in the **Package source folder to be created (UNC Path):** text box, type **\\\\CM01\\Sources$\\OSD\\Boot\\Zero Touch WinPE x64** and click **Next**.
|
||||
|
||||
>[!NOTE]
|
||||
>The Zero Touch WinPE x64 folder does not yet exist. The folder will be created later by the wizard.
|
||||
|
||||
3. On the **General Settings** page, assign the name **Zero Touch WinPE x64** and click **Next**.
|
||||
|
||||
4. On the **Options** page, select the **x64** platform, and click **Next**.
|
||||
|
||||
5. On the **Components** page, in addition to the default selected **Microsoft Data Access Components (MDAC/ADO)** support, select the **Microsoft Diagnostics and Recovery Toolkit (DaRT)** check box.
|
||||
|
||||
|
||||
|
||||
Figure 15. Add the DaRT component to the Configuration Manager boot image.
|
||||
|
||||
6. On the **Customization** page, select the **Use a custom background bitmap file** check box, and in the **UNC path:** text box, browse to **\\\\CM01\\Sources$\\OSD\\Branding\\ ContosoBackground.bmp**. Then click **Next** twice.
|
||||
|
||||
>[!NOTE]
|
||||
>It will take a few minutes to generate the boot image.
|
||||
|
||||
7. Distribute the boot image to the CM01 distribution point by selecting the **Boot images** node, right-clicking the **Zero Touch WinPE x64** boot image, and selecting **Distribute Content**.
|
||||
|
||||
8. In the Distribute Content Wizard, add the CM01 distribution point, and complete the wizard.
|
||||
|
||||
9. Using Configuration Manager Trace, review the E:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file. Do not continue until you can see that the boot image is distributed. Look for the line that reads STATMSG: ID=2301. You also can view Content Status in the Configuration Manager Console by selecting **the Zero Touch WinPE x86** boot image.
|
||||
|
||||
|
||||
|
||||
Figure 16. Content status for the Zero Touch WinPE x64 boot image
|
||||
|
||||
10. Using the Configuration Manager Console, right-click the **Zero Touch WinPE x64** boot image and select **Properties**.
|
||||
|
||||
11. In the **Data Source** tab, select the **Deploy this boot image from the PXE-enabled distribution point** check box, and click **OK**.
|
||||
|
||||
12. Using Configuration Manager Trace, review the E:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file and look for this text: Expanding PS10000B to E:\\RemoteInstall\\SMSImages.
|
||||
|
||||
13. Review the **E:\\RemoteInstall\\SMSImages** folder. You should see three folders containing boot images. Two are from the default boot images, and the third folder (PS10000B) is from your new boot image with DaRT.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Integrate Configuration Manager with MDT](../deploy-windows-mdt/integrate-configuration-manager-with-mdt.md)
|
||||
|
||||
[Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
||||
|
||||
[Add a Windows 10 operating system image using Configuration Manager](add-a-windows-10-operating-system-image-using-configuration-manager.md)
|
||||
|
||||
[Create an application to deploy with Windows 10 using Configuration Manager](create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md)
|
||||
|
||||
[Create a task sequence with Configuration Manager and MDT](../deploy-windows-mdt/create-a-task-sequence-with-configuration-manager-and-mdt.md)
|
||||
|
||||
[Deploy Windows 10 using PXE and Configuration Manager](deploy-windows-10-using-pxe-and-configuration-manager.md)
|
||||
|
||||
[Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Finalize operating system configuration for Windows 10 deployment
|
||||
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.
|
||||
description: Follow this walk-through to finalize the configuration of your Windows 10 operating deployment.
|
||||
ms.assetid: 38b55fa8-e717-4689-bd43-8348751d493e
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Monitor the Windows 10 deployment with Configuration Manager
|
||||
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.
|
||||
description: Learn how to monitor a Windows 10 deployment with Configuration Manager. Use the Deployment Workbench to access the computer remotely.
|
||||
ms.assetid: 4863c6aa-6369-4171-8e1a-b052ca195fce
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
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).
|
||||
description: Learn how to prepare a Zero Touch Installation of Windows 10 with Configuration Manager, by integrating Configuration Manager with Microsoft Deployment Toolkit.
|
||||
ms.assetid: 06e3a221-31ef-47a5-b4da-3b927cb50d08
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,147 +1,148 @@
|
||||
---
|
||||
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
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: upgrade, install, installation, computer refresh
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10 versions 1507, 1511
|
||||
|
||||
>[!IMPORTANT]
|
||||
>For instructions to deploy the most recent version of Windows 10 with Configuration Manager, see [Scenarios to deploy enterprise operating systems with System Center Configuration Manager](https://docs.microsoft.com/sccm/osd/deploy-use/scenarios-to-deploy-enterprise-operating-systems).
|
||||
>Configuration Manager 2012 and 2012 R2 provide support for Windows 10 versions 1507 and 1511 only. Later versions of Windows 10 require an updated Configuration Manager release. For a list of Configuration Manager versions and the corresponding Windows 10 client versions that are supported, see [Support for Windows 10 for System Center Configuration Manager](https://docs.microsoft.com/sccm/core/plan-design/configs/support-for-windows-10).
|
||||
|
||||
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. When refreshing a machine to a later version, it appears as an upgrade to the end user, but technically it is not an in-place upgrade. A computer refresh also involves taking care of user data and settings from the old installation and making sure to restore those at the end of the installation. For more information, see [Refresh a Windows 7 computer with Windows 10](../deploy-windows-mdt/refresh-a-windows-7-computer-with-windows-10.md).
|
||||
|
||||
A computer refresh with System Center 2012 R2 Configuration Manager works the same as it does with MDT Lite Touch installation. Configuration Manager also uses the User State Migration Tool (USMT) from the Windows Assessment and Deployment Kit (Windows ADK) 10 in the background. A computer refresh with Configuration Manager involves the following steps:
|
||||
|
||||
1. Data and settings are backed up locally in a backup folder.
|
||||
|
||||
2. The partition is wiped, except for the backup folder.
|
||||
|
||||
3. The new operating system image is applied.
|
||||
|
||||
4. Other applications are installed.
|
||||
|
||||
5. Data and settings are restored.
|
||||
|
||||
For the purposes of this topic, we will use three machines: DC01, CM01, and PC0003. DC01 is a domain controller and CM01 is a machine running Windows Server 2012 R2 Standard. PC0003 is a machine with Windows 7 SP1, on which Windows 10 will be deployed. DC01, CM01, and PC003 are all members of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
In this topic, we assume that you have a Windows 7 SP1 client named PC0003 with the Configuration Manager client installed.
|
||||
|
||||
## <a href="" id="sec01"></a>Create a device collection and add the PC0003 computer
|
||||
|
||||
|
||||
1. On CM01, using the Configuration Manager console, in the Asset and Compliance workspace, right-click **Device Collections**, and then select **Create Device Collection**. Use the following settings:
|
||||
|
||||
* General
|
||||
|
||||
* Name: Install Windows 10 Enterprise x64
|
||||
|
||||
* Limited Collection: All Systems
|
||||
|
||||
* Membership rules:
|
||||
|
||||
* Direct rule
|
||||
|
||||
* Resource Class: System Resource
|
||||
|
||||
* Attribute Name: Name
|
||||
|
||||
* Value: PC0003
|
||||
|
||||
* Select **Resources**
|
||||
|
||||
* Select **PC0003**
|
||||
|
||||
2. Review the Install Windows 10 Enterprise x64 collection. Do not continue until you see the PC0003 machine in the collection.
|
||||
|
||||
>[!NOTE]
|
||||
>It may take a short while for the collection to refresh; you can view progress via the Colleval.log file. If you want to speed up the process, you can manually update membership on the Install Windows 10 Enterprise x64 collection by right-clicking the collection and selecting Update Membership.
|
||||
|
||||
|
||||
|
||||
## <a href="" id="sec02"></a>Create a new deployment
|
||||
|
||||
|
||||
Using the Configuration Manager console, in the Software Library workspace, select **Task Sequences**, right-click **Windows 10 Enterprise x64 RTM**, and then select **Deploy**. Use the following settings:
|
||||
|
||||
- General
|
||||
|
||||
- Collection: Install Windows 10 Enterprise x64
|
||||
|
||||
- Deployment Settings
|
||||
|
||||
- Purpose: Available
|
||||
|
||||
- Make available to the following: Configuration Manager clients, media and PXE
|
||||
|
||||
>[!NOTE]
|
||||
>It is not necessary to make the deployment available to media and Pre-Boot Execution Environment (PXE) for a computer refresh, but you will use the same deployment for bare-metal deployments later on and you will need it at that point.
|
||||
|
||||
|
||||
|
||||
- Scheduling
|
||||
|
||||
- <default>
|
||||
|
||||
- User Experience
|
||||
|
||||
- <default>
|
||||
|
||||
- Alerts
|
||||
|
||||
- <default>
|
||||
|
||||
- Distribution Points
|
||||
|
||||
- <default>
|
||||
|
||||
## <a href="" id="sec03"></a>Initiate a computer refresh
|
||||
|
||||
|
||||
Now you can start the computer refresh on PC0003.
|
||||
|
||||
1. Using the Configuration Manager console, in the Asset and Compliance workspace, in the Install Windows 10 Enterprise x64 collection, right-click **PC0003** and select **Client Notification / Download Computer Policy**. Click **OK**.
|
||||
|
||||
>[!NOTE]
|
||||
>The Client Notification feature is new in Configuration Manager.
|
||||
|
||||
2. On PC0003, using the Software Center (begin using the Start screen, or click the **New software is available** balloon in the system tray), select the **Windows 10 Enterprise x64 RTM** deployment and click **INSTALL**.
|
||||
|
||||
3. In the **Software Center** warning dialog box, click **INSTALL OPERATING SYSTEM**.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Integrate Configuration Manager with MDT](../deploy-windows-mdt/integrate-configuration-manager-with-mdt.md)
|
||||
|
||||
[Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
||||
|
||||
[Create a custom Windows PE boot image with Configuration Manager](create-a-custom-windows-pe-boot-image-with-configuration-manager.md)
|
||||
|
||||
[Add a Windows 10 operating system image using Configuration Manager](add-a-windows-10-operating-system-image-using-configuration-manager.md)
|
||||
|
||||
[Create an application to deploy with Windows 10 using Configuration Manager](create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md)
|
||||
|
||||
[Create a task sequence with Configuration Manager and MDT](../deploy-windows-mdt/create-a-task-sequence-with-configuration-manager-and-mdt.md)
|
||||
|
||||
[Deploy Windows 10 using PXE and Configuration Manager](deploy-windows-10-using-pxe-and-configuration-manager.md)
|
||||
|
||||
[Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
---
|
||||
title: Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager (Windows 10)
|
||||
description: Learn how to use Configuration Manager and Microsoft Deployment Toolkit (MDT) to refresh a Windows 7 SP1 client with Windows 10.
|
||||
ms.assetid: 57c81667-1019-4711-b3de-15ae9c5387c7
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: upgrade, install, installation, computer refresh
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10 versions 1507, 1511
|
||||
|
||||
>[!IMPORTANT]
|
||||
>For instructions to deploy the most recent version of Windows 10 with Configuration Manager, see [Scenarios to deploy enterprise operating systems with System Center Configuration Manager](https://docs.microsoft.com/sccm/osd/deploy-use/scenarios-to-deploy-enterprise-operating-systems).
|
||||
>Configuration Manager 2012 and 2012 R2 provide support for Windows 10 versions 1507 and 1511 only. Later versions of Windows 10 require an updated Configuration Manager release. For a list of Configuration Manager versions and the corresponding Windows 10 client versions that are supported, see [Support for Windows 10 for System Center Configuration Manager](https://docs.microsoft.com/sccm/core/plan-design/configs/support-for-windows-10).
|
||||
|
||||
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. When refreshing a machine to a later version, it appears as an upgrade to the end user, but technically it is not an in-place upgrade. A computer refresh also involves taking care of user data and settings from the old installation and making sure to restore those at the end of the installation. For more information, see [Refresh a Windows 7 computer with Windows 10](../deploy-windows-mdt/refresh-a-windows-7-computer-with-windows-10.md).
|
||||
|
||||
A computer refresh with System Center 2012 R2 Configuration Manager works the same as it does with MDT Lite Touch installation. Configuration Manager also uses the User State Migration Tool (USMT) from the Windows Assessment and Deployment Kit (Windows ADK) 10 in the background. A computer refresh with Configuration Manager involves the following steps:
|
||||
|
||||
1. Data and settings are backed up locally in a backup folder.
|
||||
|
||||
2. The partition is wiped, except for the backup folder.
|
||||
|
||||
3. The new operating system image is applied.
|
||||
|
||||
4. Other applications are installed.
|
||||
|
||||
5. Data and settings are restored.
|
||||
|
||||
For the purposes of this topic, we will use three machines: DC01, CM01, and PC0003. DC01 is a domain controller and CM01 is a machine running Windows Server 2012 R2 Standard. PC0003 is a machine with Windows 7 SP1, on which Windows 10 will be deployed. DC01, CM01, and PC003 are all members of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
In this topic, we assume that you have a Windows 7 SP1 client named PC0003 with the Configuration Manager client installed.
|
||||
|
||||
## <a href="" id="sec01"></a>Create a device collection and add the PC0003 computer
|
||||
|
||||
|
||||
1. On CM01, using the Configuration Manager console, in the Asset and Compliance workspace, right-click **Device Collections**, and then select **Create Device Collection**. Use the following settings:
|
||||
|
||||
* General
|
||||
|
||||
* Name: Install Windows 10 Enterprise x64
|
||||
|
||||
* Limited Collection: All Systems
|
||||
|
||||
* Membership rules:
|
||||
|
||||
* Direct rule
|
||||
|
||||
* Resource Class: System Resource
|
||||
|
||||
* Attribute Name: Name
|
||||
|
||||
* Value: PC0003
|
||||
|
||||
* Select **Resources**
|
||||
|
||||
* Select **PC0003**
|
||||
|
||||
2. Review the Install Windows 10 Enterprise x64 collection. Do not continue until you see the PC0003 machine in the collection.
|
||||
|
||||
>[!NOTE]
|
||||
>It may take a short while for the collection to refresh; you can view progress via the Colleval.log file. If you want to speed up the process, you can manually update membership on the Install Windows 10 Enterprise x64 collection by right-clicking the collection and selecting Update Membership.
|
||||
|
||||
|
||||
|
||||
## <a href="" id="sec02"></a>Create a new deployment
|
||||
|
||||
|
||||
Using the Configuration Manager console, in the Software Library workspace, select **Task Sequences**, right-click **Windows 10 Enterprise x64 RTM**, and then select **Deploy**. Use the following settings:
|
||||
|
||||
- General
|
||||
|
||||
- Collection: Install Windows 10 Enterprise x64
|
||||
|
||||
- Deployment Settings
|
||||
|
||||
- Purpose: Available
|
||||
|
||||
- Make available to the following: Configuration Manager clients, media and PXE
|
||||
|
||||
>[!NOTE]
|
||||
>It is not necessary to make the deployment available to media and Pre-Boot Execution Environment (PXE) for a computer refresh, but you will use the same deployment for bare-metal deployments later on and you will need it at that point.
|
||||
|
||||
|
||||
|
||||
- Scheduling
|
||||
|
||||
- <default>
|
||||
|
||||
- User Experience
|
||||
|
||||
- <default>
|
||||
|
||||
- Alerts
|
||||
|
||||
- <default>
|
||||
|
||||
- Distribution Points
|
||||
|
||||
- <default>
|
||||
|
||||
## <a href="" id="sec03"></a>Initiate a computer refresh
|
||||
|
||||
|
||||
Now you can start the computer refresh on PC0003.
|
||||
|
||||
1. Using the Configuration Manager console, in the Asset and Compliance workspace, in the Install Windows 10 Enterprise x64 collection, right-click **PC0003** and select **Client Notification / Download Computer Policy**. Click **OK**.
|
||||
|
||||
>[!NOTE]
|
||||
>The Client Notification feature is new in Configuration Manager.
|
||||
|
||||
2. On PC0003, using the Software Center (begin using the Start screen, or click the **New software is available** balloon in the system tray), select the **Windows 10 Enterprise x64 RTM** deployment and click **INSTALL**.
|
||||
|
||||
3. In the **Software Center** warning dialog box, click **INSTALL OPERATING SYSTEM**.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Integrate Configuration Manager with MDT](../deploy-windows-mdt/integrate-configuration-manager-with-mdt.md)
|
||||
|
||||
[Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
||||
|
||||
[Create a custom Windows PE boot image with Configuration Manager](create-a-custom-windows-pe-boot-image-with-configuration-manager.md)
|
||||
|
||||
[Add a Windows 10 operating system image using Configuration Manager](add-a-windows-10-operating-system-image-using-configuration-manager.md)
|
||||
|
||||
[Create an application to deploy with Windows 10 using Configuration Manager](create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md)
|
||||
|
||||
[Create a task sequence with Configuration Manager and MDT](../deploy-windows-mdt/create-a-task-sequence-with-configuration-manager-and-mdt.md)
|
||||
|
||||
[Deploy Windows 10 using PXE and Configuration Manager](deploy-windows-10-using-pxe-and-configuration-manager.md)
|
||||
|
||||
[Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
@ -4,13 +4,15 @@ description: Deploying Windows 10 for IT professionals.
|
||||
ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.audience: itpro
author: greg-lindsay
|
||||
ms.audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 11/06/2018
|
||||
audience: itpro
author: greg-lindsay
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -35,7 +37,7 @@ Windows 10 upgrade options are discussed and information is provided about plann
|
||||
|
||||
## Related topics
|
||||
|
||||
[Modern Destop Deployment Center](https://docs.microsoft.com/microsoft-365/enterprise/desktop-deployment-center-home)
|
||||
[Modern Desktop Deployment Center](https://docs.microsoft.com/microsoft-365/enterprise/desktop-deployment-center-home)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,100 +1,101 @@
|
||||
---
|
||||
title: Applying Filters to Data in the SUA Tool (Windows 10)
|
||||
description: On the user interface for the Standard User Analyzer (SUA) tool, you can apply filters to the issues that the tool has found so that you can view only the information that interests you.
|
||||
ms.assetid: 48c39919-3501-405d-bcf5-d2784cbb011f
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: appcompat
|
||||
ms.sitesec: library
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Applying Filters to Data in the SUA Tool
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
On the user interface for the Standard User Analyzer (SUA) tool, you can apply filters to the issues that the tool has found so that you can view only the information that interests you.
|
||||
|
||||
**To apply filters to data in the SUA tool**
|
||||
|
||||
1. Use the SUA tool to test an application. For more information, see [Using the SUA Tool](using-the-sua-tool.md).
|
||||
|
||||
2. After you finish testing, in the SUA tool, click a tab that shows issues that the SUA tool has found. All tabs except the **App Info** tab can show issues.
|
||||
|
||||
3. On the **Options** menu, click a command that corresponds to the filter that you want to apply. The following table describes the commands.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Options menu command</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Filter Noise</strong></p></td>
|
||||
<td align="left"><p>Filters noise from the issues.</p>
|
||||
<p>This command is selected by default.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Load Noise Filter File</strong></p></td>
|
||||
<td align="left"><p>Opens the <strong>Open Noise Filter File</strong> dialog box, in which you can load an existing noise filter (.xml) file.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Export Noise Filter File</strong></p></td>
|
||||
<td align="left"><p>Opens the <strong>Save Noise Filter File</strong> dialog box, in which you can save filter settings as a noise filter (.xml) file.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Only Display Records with Application Name in StackTrace</strong></p></td>
|
||||
<td align="left"><p>Filters out records that do not have the application name in the stack trace.</p>
|
||||
<p>However, because the SUA tool captures only the first 32 stack frames, this command can also filter out real issues with the application where the call stack is deeper than 32 frames.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Show More Details in StackTrace</strong></p></td>
|
||||
<td align="left"><p>Shows additional stack frames that are related to the SUA tool, but not related to the diagnosed application.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Warn Before Deleting AppVerifier Logs</strong></p></td>
|
||||
<td align="left"><p>Displays a warning message before the SUA tool deletes all of the existing SUA-related log files on the computer.</p>
|
||||
<p>This command is selected by default.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Logging</strong></p></td>
|
||||
<td align="left"><p>Provides the following logging-related options:</p>
|
||||
<ul>
|
||||
<li><p>Show or hide log errors.</p></li>
|
||||
<li><p>Show or hide log warnings.</p></li>
|
||||
<li><p>Show or hide log information.</p></li>
|
||||
</ul>
|
||||
<p>To maintain a manageable file size, we recommend that you do not select the option to show informational messages.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
title: Applying Filters to Data in the SUA Tool (Windows 10)
|
||||
description: Learn how to apply filters to results from the Standard User Analyzer (SUA) tool while testing your application.
|
||||
ms.assetid: 48c39919-3501-405d-bcf5-d2784cbb011f
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: appcompat
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Applying Filters to Data in the SUA Tool
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
On the user interface for the Standard User Analyzer (SUA) tool, you can apply filters to the issues that the tool has found so that you can view only the information that interests you.
|
||||
|
||||
**To apply filters to data in the SUA tool**
|
||||
|
||||
1. Use the SUA tool to test an application. For more information, see [Using the SUA Tool](using-the-sua-tool.md).
|
||||
|
||||
2. After you finish testing, in the SUA tool, click a tab that shows issues that the SUA tool has found. All tabs except the **App Info** tab can show issues.
|
||||
|
||||
3. On the **Options** menu, click a command that corresponds to the filter that you want to apply. The following table describes the commands.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Options menu command</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Filter Noise</strong></p></td>
|
||||
<td align="left"><p>Filters noise from the issues.</p>
|
||||
<p>This command is selected by default.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Load Noise Filter File</strong></p></td>
|
||||
<td align="left"><p>Opens the <strong>Open Noise Filter File</strong> dialog box, in which you can load an existing noise filter (.xml) file.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Export Noise Filter File</strong></p></td>
|
||||
<td align="left"><p>Opens the <strong>Save Noise Filter File</strong> dialog box, in which you can save filter settings as a noise filter (.xml) file.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Only Display Records with Application Name in StackTrace</strong></p></td>
|
||||
<td align="left"><p>Filters out records that do not have the application name in the stack trace.</p>
|
||||
<p>However, because the SUA tool captures only the first 32 stack frames, this command can also filter out real issues with the application where the call stack is deeper than 32 frames.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Show More Details in StackTrace</strong></p></td>
|
||||
<td align="left"><p>Shows additional stack frames that are related to the SUA tool, but not related to the diagnosed application.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Warn Before Deleting AppVerifier Logs</strong></p></td>
|
||||
<td align="left"><p>Displays a warning message before the SUA tool deletes all of the existing SUA-related log files on the computer.</p>
|
||||
<p>This command is selected by default.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Logging</strong></p></td>
|
||||
<td align="left"><p>Provides the following logging-related options:</p>
|
||||
<ul>
|
||||
<li><p>Show or hide log errors.</p></li>
|
||||
<li><p>Show or hide log warnings.</p></li>
|
||||
<li><p>Show or hide log information.</p></li>
|
||||
</ul>
|
||||
<p>To maintain a manageable file size, we recommend that you do not select the option to show informational messages.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Create AppHelp Message in Compatibility Administrator (Windows 10)
|
||||
description: The Compatibility Administrator tool enables you to create an AppHelp text message. This is a blocking or non-blocking message that appears when a user starts an application that you know has major functionality issues on the Windows® operating system.
|
||||
description: Create an AppHelp text message with Compatibility Administrator; a message that appears upon starting an app with major issues on the Windows® operating system.
|
||||
ms.assetid: 5c6e89f5-1942-4aa4-8439-ccf0ecd02848
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Plan for Windows 10 deployment (Windows 10)
|
||||
description: Windows 10 provides new deployment capabilities, scenarios, and tools by building on technologies introduced in Windows 7, and Windows 8.1, while at the same time introducing new Windows as a service concepts to keep the operating system up to date.
|
||||
description: Find resources for your Windows 10 deployment. Windows 10 provides new deployment capabilities and tools, and introduces new ways to keep the OS up to date.
|
||||
ms.assetid: 002F9B79-B50F-40C5-A7A5-0B4770E6EC15
|
||||
keywords: deploy, upgrade, update, configure
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,66 +1,67 @@
|
||||
---
|
||||
title: Managing Application-Compatibility Fixes and Custom Fix Databases (Windows 10)
|
||||
description: This section provides information about managing your application-compatibility fixes and custom-compatibility fix databases. This section explains the reasons for using compatibility fixes and how to deploy custom-compatibility fix databases.
|
||||
ms.assetid: 9c2e9396-908e-4a36-ad67-2e40452ce017
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: appcompat
|
||||
ms.sitesec: library
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Managing Application-Compatibility Fixes and Custom Fix Databases
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
This section provides information about managing your application-compatibility fixes and custom-compatibility fix databases. This section explains the reasons for using compatibility fixes and how to deploy custom-compatibility fix databases.
|
||||
|
||||
## In this section
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Topic</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><a href="understanding-and-using-compatibility-fixes.md" data-raw-source="[Understanding and Using Compatibility Fixes](understanding-and-using-compatibility-fixes.md)">Understanding and Using Compatibility Fixes</a></p></td>
|
||||
<td align="left"><p>As the Windows operating system evolves to support new technology and functionality, the implementations of some functions may change. This can cause problems for applications that relied upon the original implementation. You can avoid compatibility issues by using the Microsoft Windows Application Compatibility (Compatibility Fix) infrastructure to create a specific application fix for a particular version of an application.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><a href="compatibility-fix-database-management-strategies-and-deployment.md" data-raw-source="[Compatibility Fix Database Management Strategies and Deployment](compatibility-fix-database-management-strategies-and-deployment.md)">Compatibility Fix Database Management Strategies and Deployment</a></p></td>
|
||||
<td align="left"><p>After you determine that you will use compatibility fixes in your application-compatibility mitigation strategy, you must define a strategy to manage your custom compatibility-fix database. Typically, you can use one of two approaches:</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><a href="testing-your-application-mitigation-packages.md" data-raw-source="[Testing Your Application Mitigation Packages](testing-your-application-mitigation-packages.md)">Testing Your Application Mitigation Packages</a></p></td>
|
||||
<td align="left"><p>This topic provides details about testing your application-mitigation packages, including recommendations about how to report your information and how to resolve any outstanding issues.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
||||
|
||||
[Using the Compatibility Administrator Tool](using-the-compatibility-administrator-tool.md)
|
||||
---
|
||||
title: Managing Application-Compatibility Fixes and Custom Fix Databases (Windows 10)
|
||||
description: Learn why you should use compatibility fixes, and how to deploy and manage custom-compatibility fix databases.
|
||||
ms.assetid: 9c2e9396-908e-4a36-ad67-2e40452ce017
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: appcompat
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Managing Application-Compatibility Fixes and Custom Fix Databases
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
This section provides information about managing your application-compatibility fixes and custom-compatibility fix databases. This section explains the reasons for using compatibility fixes and how to deploy custom-compatibility fix databases.
|
||||
|
||||
## In this section
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Topic</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><a href="understanding-and-using-compatibility-fixes.md" data-raw-source="[Understanding and Using Compatibility Fixes](understanding-and-using-compatibility-fixes.md)">Understanding and Using Compatibility Fixes</a></p></td>
|
||||
<td align="left"><p>As the Windows operating system evolves to support new technology and functionality, the implementations of some functions may change. This can cause problems for applications that relied upon the original implementation. You can avoid compatibility issues by using the Microsoft Windows Application Compatibility (Compatibility Fix) infrastructure to create a specific application fix for a particular version of an application.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><a href="compatibility-fix-database-management-strategies-and-deployment.md" data-raw-source="[Compatibility Fix Database Management Strategies and Deployment](compatibility-fix-database-management-strategies-and-deployment.md)">Compatibility Fix Database Management Strategies and Deployment</a></p></td>
|
||||
<td align="left"><p>After you determine that you will use compatibility fixes in your application-compatibility mitigation strategy, you must define a strategy to manage your custom compatibility-fix database. Typically, you can use one of two approaches:</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><a href="testing-your-application-mitigation-packages.md" data-raw-source="[Testing Your Application Mitigation Packages](testing-your-application-mitigation-packages.md)">Testing Your Application Mitigation Packages</a></p></td>
|
||||
<td align="left"><p>This topic provides details about testing your application-mitigation packages, including recommendations about how to report your information and how to resolve any outstanding issues.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
||||
|
||||
[Using the Compatibility Administrator Tool](using-the-compatibility-administrator-tool.md)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Searching for Fixed Applications in Compatibility Administrator (Windows 10)
|
||||
description: With the search functionality in Compatibility Administrator, you can locate specific executable (.exe) files with previously applied compatibility fixes, compatibility modes, or AppHelp messages.
|
||||
description: Compatibility Administrator can locate specific executable (.exe) files with previously applied compatibility fixes, compatibility modes, or AppHelp messages.
|
||||
ms.assetid: 1051a2dc-0362-43a4-8ae8-07dae39b1cb8
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,86 +1,87 @@
|
||||
---
|
||||
title: Security and data protection considerations for Windows To Go (Windows 10)
|
||||
description: One of the most important requirements to consider when you plan your Windows To Go deployment is to ensure that the data, content, and resources you work with in the Windows To Go workspace is protected and secure.
|
||||
ms.assetid: 5f27339f-6761-44f4-8c29-9a25cf8e75fe
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: mobile, device, USB, secure, BitLocker
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: mobility, security
|
||||
ms.sitesec: library
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Security and data protection considerations for Windows To Go
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Windows To Go is no longer being developed. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
|
||||
One of the most important requirements to consider when you plan your Windows To Go deployment is to ensure that the data, content, and resources you work with in the Windows To Go workspace is protected and secure.
|
||||
|
||||
## Backup and restore
|
||||
|
||||
|
||||
As long as you are not saving data on the Windows To Go drive, there is no need for a backup and restore solution for Windows To Go. If you are saving data on the drive and are not using folder redirection and offline files, you should back up all of your data to a network location, such as cloud storage or a network share after each work session. Review the new and improved features described in [Supporting Information Workers with Reliable File Services and Storage](https://go.microsoft.com/fwlink/p/?LinkId=619102) for different solutions you could implement.
|
||||
|
||||
If the USB drive fails for any reason, the standard process to restore the drive to working condition is to reformat and re-provision the drive with Windows To Go, so all data and customization on the drive will be lost. This is another reason why using roaming user profiles, folder redirection and offline files with Windows To Go is strongly recommended. For more information, see [Folder Redirection, Offline Files, and Roaming User Profiles overview](https://go.microsoft.com/fwlink/p/?LinkId=618924).
|
||||
|
||||
## BitLocker
|
||||
|
||||
|
||||
We recommend that you use BitLocker with your Windows To Go drives to protect the drive from being compromised if the drive is lost or stolen. When BitLocker is enabled, the user must provide a password to unlock the drive and boot the Windows To Go workspace, this helps prevent unauthorized users from booting the drive and using it to gain access to your network resources and confidential data. Because Windows To Go drives are meant to be roamed between computers, the Trusted Platform Module (TPM) cannot be used by BitLocker to protect the drive. Instead, you will be specifying a password that BitLocker will use for disk encryption and decryption. By default, this password must be eight characters in length and can enforce more strict requirements depending on the password complexity requirements defined by your organizations domain controller.
|
||||
|
||||
You can enable BitLocker while using the Windows To Go Creator wizard as part of the drive provisioning process before first use; or it can be enabled afterward by the user from within the Windows To Go workspace.
|
||||
|
||||
**Tip**
|
||||
If the Windows To Go Creator wizard is not able to enable BitLocker, see [Why can't I enable BitLocker from Windows To Go Creator?](windows-to-go-frequently-asked-questions.md#wtg-faq-blfail)
|
||||
|
||||
|
||||
|
||||
If you are using a host computer running Windows 7 that has BitLocker enabled, you should suspend BitLocker before changing the BIOS settings to boot from USB and then resume BitLocker protection. If BitLocker is not suspended first, the next time the computer is started it will boot into recovery mode.
|
||||
|
||||
## Disk discovery and data leakage
|
||||
|
||||
|
||||
We recommend that you use the **NoDefaultDriveLetter** attribute when provisioning the USB drive to help prevent accidental data leakage. **NoDefaultDriveLetter** will prevent the host operating system from assigning a drive letter if a user inserts it into a running computer. This means the drive will not appear in Windows Explorer and an AutoPlay prompt will not be displayed to the user. This reduces the likelihood that an end-user will access the offline Windows To Go disk directly from another computer. If you use the Windows To Go Creator to provision a workspace, this attribute will automatically be set for you.
|
||||
|
||||
To prevent accidental data leakage between Windows To Go and the host system Windows 8 has a new SAN policy—OFFLINE\_INTERNAL - “4” to prevent the operating system from automatically bringing online any internally connected disk. The default configuration for Windows To Go has this policy enabled. It is strongly recommended you do not change this policy to allow mounting of internal hard drives when booted into the Windows To Go workspace. If the internal drive contains a hibernated Windows 8 operating system, mounting the drive will lead to loss of hibernation state and therefor user state or any unsaved user data when the host operating system is booted. If the internal drive contains a hibernated Windows 7 or earlier operating system, mounting the drive will lead to corruption when the host operating system is booted.
|
||||
|
||||
For more information, see [How to Configure Storage Area Network (SAN) Policy in Windows PE](https://go.microsoft.com/fwlink/p/?LinkId=619103).
|
||||
|
||||
## Security certifications for Windows To Go
|
||||
|
||||
|
||||
Windows to Go is a core capability of Windows when it is deployed on the drive and is configured following the guidance for the applicable security certification. Solutions built using Windows To Go can be submitted for additional certifications by the solution provider that cover the solution provider’s specific hardware environment. For more details about Windows security certifications, see the following topics.
|
||||
|
||||
- [Windows Platform Common Criteria Certification](https://go.microsoft.com/fwlink/p/?LinkId=619104)
|
||||
|
||||
- [FIPS 140 Evaluation](https://go.microsoft.com/fwlink/p/?LinkId=619107)
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Windows To Go: feature overview](windows-to-go-overview.md)
|
||||
|
||||
[Prepare your organization for Windows To Go](prepare-your-organization-for-windows-to-go.md)
|
||||
|
||||
[Deployment considerations for Windows To Go](deployment-considerations-for-windows-to-go.md)
|
||||
|
||||
[Windows To Go: frequently asked questions](windows-to-go-frequently-asked-questions.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
title: Security and data protection considerations for Windows To Go (Windows 10)
|
||||
description: Ensure that the data, content, and resources you work with in the Windows To Go workspace are protected and secure.
|
||||
ms.assetid: 5f27339f-6761-44f4-8c29-9a25cf8e75fe
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: mobile, device, USB, secure, BitLocker
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: mobility, security
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Security and data protection considerations for Windows To Go
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Windows To Go is no longer being developed. The feature does not support feature updates and therefore does not enable you to stay current. It also requires a specific type of USB that is no longer supported by many OEMs.
|
||||
|
||||
One of the most important requirements to consider when you plan your Windows To Go deployment is to ensure that the data, content, and resources you work with in the Windows To Go workspace is protected and secure.
|
||||
|
||||
## Backup and restore
|
||||
|
||||
|
||||
As long as you are not saving data on the Windows To Go drive, there is no need for a backup and restore solution for Windows To Go. If you are saving data on the drive and are not using folder redirection and offline files, you should back up all of your data to a network location, such as cloud storage or a network share after each work session. Review the new and improved features described in [Supporting Information Workers with Reliable File Services and Storage](https://go.microsoft.com/fwlink/p/?LinkId=619102) for different solutions you could implement.
|
||||
|
||||
If the USB drive fails for any reason, the standard process to restore the drive to working condition is to reformat and re-provision the drive with Windows To Go, so all data and customization on the drive will be lost. This is another reason why using roaming user profiles, folder redirection and offline files with Windows To Go is strongly recommended. For more information, see [Folder Redirection, Offline Files, and Roaming User Profiles overview](https://go.microsoft.com/fwlink/p/?LinkId=618924).
|
||||
|
||||
## BitLocker
|
||||
|
||||
|
||||
We recommend that you use BitLocker with your Windows To Go drives to protect the drive from being compromised if the drive is lost or stolen. When BitLocker is enabled, the user must provide a password to unlock the drive and boot the Windows To Go workspace, this helps prevent unauthorized users from booting the drive and using it to gain access to your network resources and confidential data. Because Windows To Go drives are meant to be roamed between computers, the Trusted Platform Module (TPM) cannot be used by BitLocker to protect the drive. Instead, you will be specifying a password that BitLocker will use for disk encryption and decryption. By default, this password must be eight characters in length and can enforce more strict requirements depending on the password complexity requirements defined by your organizations domain controller.
|
||||
|
||||
You can enable BitLocker while using the Windows To Go Creator wizard as part of the drive provisioning process before first use; or it can be enabled afterward by the user from within the Windows To Go workspace.
|
||||
|
||||
**Tip**
|
||||
If the Windows To Go Creator wizard is not able to enable BitLocker, see [Why can't I enable BitLocker from Windows To Go Creator?](windows-to-go-frequently-asked-questions.md#wtg-faq-blfail)
|
||||
|
||||
|
||||
|
||||
If you are using a host computer running Windows 7 that has BitLocker enabled, you should suspend BitLocker before changing the BIOS settings to boot from USB and then resume BitLocker protection. If BitLocker is not suspended first, the next time the computer is started it will boot into recovery mode.
|
||||
|
||||
## Disk discovery and data leakage
|
||||
|
||||
|
||||
We recommend that you use the **NoDefaultDriveLetter** attribute when provisioning the USB drive to help prevent accidental data leakage. **NoDefaultDriveLetter** will prevent the host operating system from assigning a drive letter if a user inserts it into a running computer. This means the drive will not appear in Windows Explorer and an AutoPlay prompt will not be displayed to the user. This reduces the likelihood that an end-user will access the offline Windows To Go disk directly from another computer. If you use the Windows To Go Creator to provision a workspace, this attribute will automatically be set for you.
|
||||
|
||||
To prevent accidental data leakage between Windows To Go and the host system Windows 8 has a new SAN policy—OFFLINE\_INTERNAL - “4” to prevent the operating system from automatically bringing online any internally connected disk. The default configuration for Windows To Go has this policy enabled. It is strongly recommended you do not change this policy to allow mounting of internal hard drives when booted into the Windows To Go workspace. If the internal drive contains a hibernated Windows 8 operating system, mounting the drive will lead to loss of hibernation state and, therefore, user state or any unsaved user data when the host operating system is booted. If the internal drive contains a hibernated Windows 7 or earlier operating system, mounting the drive will lead to corruption when the host operating system is booted.
|
||||
|
||||
For more information, see [How to Configure Storage Area Network (SAN) Policy in Windows PE](https://go.microsoft.com/fwlink/p/?LinkId=619103).
|
||||
|
||||
## Security certifications for Windows To Go
|
||||
|
||||
|
||||
Windows to Go is a core capability of Windows when it is deployed on the drive and is configured following the guidance for the applicable security certification. Solutions built using Windows To Go can be submitted for additional certifications by the solution provider that cover the solution provider’s specific hardware environment. For more details about Windows security certifications, see the following topics.
|
||||
|
||||
- [Windows Platform Common Criteria Certification](https://go.microsoft.com/fwlink/p/?LinkId=619104)
|
||||
|
||||
- [FIPS 140 Evaluation](https://go.microsoft.com/fwlink/p/?LinkId=619107)
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Windows To Go: feature overview](windows-to-go-overview.md)
|
||||
|
||||
[Prepare your organization for Windows To Go](prepare-your-organization-for-windows-to-go.md)
|
||||
|
||||
[Deployment considerations for Windows To Go](deployment-considerations-for-windows-to-go.md)
|
||||
|
||||
[Windows To Go: frequently asked questions](windows-to-go-frequently-asked-questions.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Testing Your Application Mitigation Packages (Windows 10)
|
||||
description: This topic provides details about testing your application-mitigation packages, including recommendations about how to report your information and how to resolve any outstanding issues.
|
||||
description: Learn how to test your application-mitigation packages, including how to report your information and how to resolve any outstanding issues.
|
||||
ms.assetid: ae946f27-d377-4db9-b179-e8875d454ccf
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,92 +1,93 @@
|
||||
---
|
||||
title: Using the SUA Tool (Windows 10)
|
||||
description: By using the Standard User Analyzer (SUA) tool, you can test your applications and monitor API calls to detect compatibility issues with the User Account Control (UAC) feature.
|
||||
ms.assetid: ebe52061-3816-47f7-a865-07bc5f405f03
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: appcompat
|
||||
ms.sitesec: library
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Using the SUA Tool
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
By using the Standard User Analyzer (SUA) tool, you can test your applications and monitor API calls to detect compatibility issues with the User Account Control (UAC) feature.
|
||||
|
||||
The SUA Wizard also addresses UAC-related issues. In contrast to the SUA tool, the SUA Wizard guides you through the process step by step, without the in-depth analysis of the SUA tool. For information about the SUA Wizard, see [Using the SUA Wizard](using-the-sua-wizard.md).
|
||||
|
||||
In the SUA tool, you can turn virtualization on and off. When you turn virtualization off, the tested application may function more like the way it does in earlier versions of Windows®.
|
||||
|
||||
In the SUA tool, you can choose to run the application as **Administrator** or as **Standard User**. Depending on your selection, you may locate different types of UAC-related issues.
|
||||
|
||||
## Testing an Application by Using the SUA Tool
|
||||
|
||||
|
||||
Before you can use the SUA tool, you must install Application Verifier. You must also install the Microsoft® .NET Framework 3.5 or later.
|
||||
|
||||
The following flowchart shows the process of using the SUA tool.
|
||||
|
||||
|
||||
|
||||
**To collect UAC-related issues by using the SUA tool**
|
||||
|
||||
1. Close any open instance of the SUA tool or SUA Wizard on your computer.
|
||||
|
||||
If there is an existing SUA instance on the computer, the SUA tool opens in log viewer mode instead of normal mode. In log viewer mode, you cannot start applications, which prevents you from collecting UAC issues.
|
||||
|
||||
2. Run the Standard User Analyzer.
|
||||
|
||||
3. In the **Target Application** box, browse to the executable file for the application that you want to analyze, and then double-click to select it.
|
||||
|
||||
4. Clear the **Elevate** check box, and then click **Launch**.
|
||||
|
||||
If a **Permission denied** dialog box appears, click **OK**. The application starts, despite the warning.
|
||||
|
||||
5. Exercise the aspects of the application for which you want to gather information about UAC issues.
|
||||
|
||||
6. Exit the application.
|
||||
|
||||
7. Review the information from the various tabs in the SUA tool. For information about each tab, see [Tabs on the SUA Tool Interface](tabs-on-the-sua-tool-interface.md).
|
||||
|
||||
**To review and apply the recommended mitigations**
|
||||
|
||||
1. In the SUA tool, on the **Mitigation** menu, click **Apply Mitigations**.
|
||||
|
||||
2. Review the recommended compatibility fixes.
|
||||
|
||||
3. Click **Apply**.
|
||||
|
||||
The SUA tool generates a custom compatibility-fix database and automatically applies it to the local computer, so that you can test the fixes to see whether they worked.
|
||||
|
||||
## Related topics
|
||||
[Tabs on the SUA Tool Interface](tabs-on-the-sua-tool-interface.md)
|
||||
|
||||
[Showing Messages Generated by the SUA Tool](showing-messages-generated-by-the-sua-tool.md)
|
||||
|
||||
[Applying Filters to Data in the SUA Tool](applying-filters-to-data-in-the-sua-tool.md)
|
||||
|
||||
[Fixing Applications by Using the SUA Tool](fixing-applications-by-using-the-sua-tool.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
title: Using the SUA Tool (Windows 10)
|
||||
description: The Standard User Analyzer (SUA) tool can test applications and monitor API calls to detect compatibility issues with the User Account Control (UAC) feature.
|
||||
ms.assetid: ebe52061-3816-47f7-a865-07bc5f405f03
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: appcompat
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Using the SUA Tool
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
By using the Standard User Analyzer (SUA) tool, you can test your applications and monitor API calls to detect compatibility issues with the User Account Control (UAC) feature.
|
||||
|
||||
The SUA Wizard also addresses UAC-related issues. In contrast to the SUA tool, the SUA Wizard guides you through the process step by step, without the in-depth analysis of the SUA tool. For information about the SUA Wizard, see [Using the SUA Wizard](using-the-sua-wizard.md).
|
||||
|
||||
In the SUA tool, you can turn virtualization on and off. When you turn virtualization off, the tested application may function more like the way it does in earlier versions of Windows®.
|
||||
|
||||
In the SUA tool, you can choose to run the application as **Administrator** or as **Standard User**. Depending on your selection, you may locate different types of UAC-related issues.
|
||||
|
||||
## Testing an Application by Using the SUA Tool
|
||||
|
||||
|
||||
Before you can use the SUA tool, you must install Application Verifier. You must also install the Microsoft® .NET Framework 3.5 or later.
|
||||
|
||||
The following flowchart shows the process of using the SUA tool.
|
||||
|
||||
|
||||
|
||||
**To collect UAC-related issues by using the SUA tool**
|
||||
|
||||
1. Close any open instance of the SUA tool or SUA Wizard on your computer.
|
||||
|
||||
If there is an existing SUA instance on the computer, the SUA tool opens in log viewer mode instead of normal mode. In log viewer mode, you cannot start applications, which prevents you from collecting UAC issues.
|
||||
|
||||
2. Run the Standard User Analyzer.
|
||||
|
||||
3. In the **Target Application** box, browse to the executable file for the application that you want to analyze, and then double-click to select it.
|
||||
|
||||
4. Clear the **Elevate** check box, and then click **Launch**.
|
||||
|
||||
If a **Permission denied** dialog box appears, click **OK**. The application starts, despite the warning.
|
||||
|
||||
5. Exercise the aspects of the application for which you want to gather information about UAC issues.
|
||||
|
||||
6. Exit the application.
|
||||
|
||||
7. Review the information from the various tabs in the SUA tool. For information about each tab, see [Tabs on the SUA Tool Interface](tabs-on-the-sua-tool-interface.md).
|
||||
|
||||
**To review and apply the recommended mitigations**
|
||||
|
||||
1. In the SUA tool, on the **Mitigation** menu, click **Apply Mitigations**.
|
||||
|
||||
2. Review the recommended compatibility fixes.
|
||||
|
||||
3. Click **Apply**.
|
||||
|
||||
The SUA tool generates a custom compatibility-fix database and automatically applies it to the local computer, so that you can test the fixes to see whether they worked.
|
||||
|
||||
## Related topics
|
||||
[Tabs on the SUA Tool Interface](tabs-on-the-sua-tool-interface.md)
|
||||
|
||||
[Showing Messages Generated by the SUA Tool](showing-messages-generated-by-the-sua-tool.md)
|
||||
|
||||
[Applying Filters to Data in the SUA Tool](applying-filters-to-data-in-the-sua-tool.md)
|
||||
|
||||
[Fixing Applications by Using the SUA Tool](fixing-applications-by-using-the-sua-tool.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows To Go feature overview (Windows 10)
|
||||
description: Windows To Go is a feature in Windows 10 Enterprise and Windows 10 Education that enables the creation of a Windows To Go workspace that can be booted from a USB-connected external drive on PCs.
|
||||
description: Windows To Go is a feature in Windows 10 Enterprise and Windows 10 Education that lets you create a workspace that can be booted from a USB-connected drive.
|
||||
ms.assetid: 9df82b03-acba-442c-801d-56db241f8d42
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -92,9 +92,9 @@ As of the date of publication, the following are the USB drives currently certif
|
||||
> [!WARNING]
|
||||
> Using a USB drive that has not been certified is not supported.
|
||||
|
||||
- IronKey Workspace W700 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w700.html](https://go.microsoft.com/fwlink/p/?LinkId=618714))
|
||||
- IronKey Workspace W500 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w500.html](https://go.microsoft.com/fwlink/p/?LinkId=618717))
|
||||
- IronKey Workspace W300 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w300.html](https://go.microsoft.com/fwlink/p/?LinkId=618718))
|
||||
- IronKey Workspace W700 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w700.html](https://www.kingston.com/support/technical/products?model=dtws))
|
||||
- IronKey Workspace W500 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w500.html](https://www.kingston.com/support/technical/products?model=dtws))
|
||||
- IronKey Workspace W300 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w300.html](https://www.kingston.com/support/technical/products?model=dtws))
|
||||
- Kingston DataTraveler Workspace for Windows To Go ([http://www.kingston.com/wtg/](https://go.microsoft.com/fwlink/p/?LinkId=618719))
|
||||
- Spyrus Portable Workplace ([http://www.spyruswtg.com/](https://go.microsoft.com/fwlink/p/?LinkId=618720))
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How Windows Update works
|
||||
description: Learn how Windows Update works, including architecture and troubleshooting
|
||||
description: Learn how Windows Update works, including architecture and troubleshooting.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl:
|
||||
audience: itpro
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Overview of Windows as a service (Windows 10)
|
||||
description: In Windows 10, Microsoft has streamlined servicing to make operating system updates simpler to test, manage, and deploy.
|
||||
description: Windows as a service introduces a new way to build, deploy, and service Windows. Learn how Windows as a service works.
|
||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Get started with Windows Update
|
||||
description: Learn how Windows Update works, including architecture and troubleshooting
|
||||
description: An overview of learning resources for Windows Update, including documents on architecture, log files, and common errors.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl:
|
||||
audience: itpro
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Setting up Automatic Update in Windows Update for Business (Windows 10)
|
||||
description: Learn how to get started using Windows Update for Business.
|
||||
description: Learn how to configure Automatic Update group policies in Windows Update for Business.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
audience: itpro
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Managing feature and quality updates with policies in Windows Update for Business (Windows 10)
|
||||
description: Learn how to get started using Windows Update for Business.
|
||||
description: Learn how to manage feature and quality updates using group policies in Windows Update for Business.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
audience: itpro
|
||||
|
||||
@ -3,7 +3,7 @@ title: Log files - Windows IT Pro
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description: Resolve Windows 10 upgrade errors for ITPros. Technical information for IT professionals to help diagnose Windows setup errors.
|
||||
description: Learn how to interpret the log files generated during the Windows 10 upgrade process.
|
||||
keywords: deploy, error, troubleshoot, windows, 10, upgrade, code, rollback, ITPro
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -27,7 +27,8 @@ ms.topic: article
|
||||
|
||||
Several log files are created during each phase of the upgrade process. These log files are essential for troubleshooting upgrade problems. By default, the folders that contain these log files are hidden on the upgrade target computer. To view the log files, configure Windows Explorer to view hidden items, or use a tool to automatically gather these logs. The most useful log is **setupact.log**. The log files are located in a different folder depending on the Windows Setup phase. Recall that you can determine the phase from the extend code.
|
||||
|
||||
Note: Also see the [Windows Error Reporting](windows-error-reporting.md) section in this document for help locating error codes and log files.
|
||||
>[!NOTE]
|
||||
>Also see the [Windows Error Reporting](windows-error-reporting.md) section in this document for help locating error codes and log files.
|
||||
|
||||
The following table describes some log files and how to use them for troubleshooting purposes:<br>
|
||||
|
||||
@ -79,7 +80,7 @@ See the following example:
|
||||
|
||||
## Analyze log files
|
||||
|
||||
>The following instructions are meant for IT professionals. Also see the [Upgrade error codes](upgrade-error-codes.md) section in this guide to familiarize yourself with [result codes](upgrade-error-codes.md#result-codes) and [extend codes](upgrade-error-codes.md#extend-codes).
|
||||
The following instructions are meant for IT professionals. Also see the [Upgrade error codes](upgrade-error-codes.md) section in this guide to familiarize yourself with [result codes](upgrade-error-codes.md#result-codes) and [extend codes](upgrade-error-codes.md#extend-codes).
|
||||
|
||||
<br>To analyze Windows Setup log files:
|
||||
|
||||
@ -110,7 +111,7 @@ See the following example:
|
||||
|
||||
For example, assume that the error code for an error is 0x8007042B - 0x2000D. Searching for "8007042B" reveals the following content from the setuperr.log file:
|
||||
|
||||
>Some lines in the text below are shortened to enhance readability. The date and time at the start of each line (ex: 2016-10-05 15:27:08) is shortened to minutes and seconds, and the certificate file name which is a long text string is shortened to just "CN."
|
||||
Some lines in the text below are shortened to enhance readability. The date and time at the start of each line (ex: 2016-10-05 15:27:08) is shortened to minutes and seconds, and the certificate file name which is a long text string is shortened to just "CN."
|
||||
|
||||
<br><B>setuperr.log</B> content:
|
||||
|
||||
|
||||
@ -1,239 +1,243 @@
|
||||
---
|
||||
title: Quick fixes - Windows IT Pro
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description: Resolve Windows 10 upgrade errors for ITPros. Technical information for IT professionals to help diagnose Windows setup errors.
|
||||
keywords: deploy, error, troubleshoot, windows, 10, upgrade, code, rollback, ITPro
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Quick fixes
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
|
||||
>[!NOTE]
|
||||
>This is a 100 level topic (basic).<br>
|
||||
>See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article.
|
||||
|
||||
The following list of fixes can resolve many Windows upgrade problems. You should try these steps before contacting Microsoft support, or attempting a more advanced analysis of a Windows upgrade failure. Also review information at [Windows 10 help](https://support.microsoft.com/products/windows?os=windows-10).
|
||||
|
||||
The Microsoft Virtual Agent provided by [Microsoft Support](https://support.microsoft.com/contactus/) can help you to analyze and correct some Windows upgrade errors. **To talk to a person about your issue**, start the Virtual Agent (click **Get started**) and enter "Talk to a person" two times.
|
||||
|
||||
>You might also wish to try a new tool available from Microsoft that helps to diagnose many Windows upgrade errors. For more information and to download this tool, see [SetupDiag](setupdiag.md). The topic is more advanced (300 level) because several advanced options are available for using the tool. However, you can now just download and then double-click the tool to run it. By default when you click Save, the tool is saved in your **Downloads** folder. Double-click the tool in the folder and wait until it finishes running (it might take a few minutes), then double-click the **SetupDiagResults.log** file and open it using Notepad to see the results of the analysis.
|
||||
|
||||
## List of fixes
|
||||
|
||||
<ol>
|
||||
<li>Remove nonessential external hardware, such as docks and USB devices. <a href="#remove-external-hardware" data-raw-source="[More information](#remove-external-hardware)">More information</a>.</li>
|
||||
<li>Check the system drive for errors and attempt repairs. <a href="#repair-the-system-drive" data-raw-source="[More information](#repair-the-system-drive)">More information</a>.</li>
|
||||
<li>Run the Windows Update troubleshooter. <a href="#windows-update-troubleshooter" data-raw-source="[More information](#windows-update-troubleshooter)">More information</a>.</li>
|
||||
<li>Attempt to restore and repair system files. <a href="#repair-system-files" data-raw-source="[More information](#repair-system-files)">More information</a>.</li>
|
||||
<li>Update Windows so that all available recommended updates are installed, and ensure the computer is rebooted if this is necessary to complete installation of an update. <a href="#update-windows" data-raw-source="[More information](#update-windows)">More information</a>.</li>
|
||||
<li>Temporarily uninstall non-Microsoft antivirus software.
|
||||
<a href="#uninstall-non-microsoft-antivirus-software" data-raw-source="[More information](#uninstall-non-microsoft-antivirus-software)">More information</a>.</li>
|
||||
|
||||
<li>Uninstall all nonessential software. <a href="#uninstall-non-essential-software" data-raw-source="[More information](#uninstall-non-essential-software)">More information</a>.</li>
|
||||
<li>Update firmware and drivers. <a href="#update-firmware-and-drivers" data-raw-source="[More information](#update-firmware-and-drivers)">More information</a></li>
|
||||
<li>Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. <a href="#ensure-that-download-and-install-updates-is-selected" data-raw-source="[More information](#ensure-that-download-and-install-updates-is-selected)">More information</a>.</li>
|
||||
<li>Verify at least 16 GB of free space is available to upgrade a 32-bit OS, or 20 GB for a 64-bit OS. <a href="#verify-disk-space" data-raw-source="[More information](#verify-disk-space)">More information</a>.</li>
|
||||
</ol>
|
||||
|
||||
## Step by step instructions
|
||||
|
||||
### Remove external hardware
|
||||
|
||||
If the computer is portable and it is currently in a docking station, [undock the computer](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754084(v=ws.11)).
|
||||
|
||||
Unplug nonessential external hardware devices from the computer, such as:
|
||||
- Headphones
|
||||
- Joysticks
|
||||
- Printers
|
||||
- Plotters
|
||||
- Projectors
|
||||
- Scanners
|
||||
- Speakers
|
||||
- USB flash drives
|
||||
- Portable hard drives
|
||||
- Portable CD/DVD/Blu-ray drives
|
||||
- Microphones
|
||||
- Media card readers
|
||||
- Cameras/Webcams
|
||||
- Smart phones
|
||||
- Secondary monitors, keyboards, mice
|
||||
|
||||
For more information about disconnecting external devices, see [Safely remove hardware in Windows 10](https://support.microsoft.com/help/4051300/windows-10-safely-remove-hardware)
|
||||
|
||||
### Repair the system drive
|
||||
|
||||
The system drive is the drive that contains the [system partition](https://docs.microsoft.com/windows-hardware/manufacture/desktop/hard-drives-and-partitions#span-idpartitionsspanspan-idpartitionsspanspan-idpartitionsspanpartitions). This is usually the **C:** drive.
|
||||
|
||||
To check and repair errors on the system drive:
|
||||
|
||||
1. Click **Start**.
|
||||
2. Type **command**.
|
||||
3. Right-click **Command Prompt** and then left-click **Run as administrator**.
|
||||
4. If you are prompted by UAC, click **Yes**.
|
||||
5. Type **chkdsk /F** and press ENTER.
|
||||
6. When you are prompted to schedule a check the next time the system restarts, type **Y**.
|
||||
7. See the following example
|
||||
|
||||
```
|
||||
C:\WINDOWS\system32>chkdsk /F
|
||||
The type of the file system is NTFS.
|
||||
Cannot lock current drive.
|
||||
|
||||
Chkdsk cannot run because the volume is in use by another
|
||||
process. Would you like to schedule this volume to be
|
||||
checked the next time the system restarts? (Y/N) Y
|
||||
|
||||
This volume will be checked the next time the system restarts.
|
||||
```
|
||||
|
||||
8. Restart the computer. The computer will pause before loading Windows and perform a repair of your hard drive.
|
||||
|
||||
### Windows Update Troubleshooter
|
||||
|
||||
The Windows Update troubleshooter tool will automatically analyze and fix problems with Windows Update, such as a corrupted download. It will also tell you if there is a pending reboot that is preventing Windows from updating.
|
||||
|
||||
For Windows 7 and 8.1, the tool is [here](https://aka.ms/diag_wu).
|
||||
|
||||
For Windows 10, the tool is [here](https://aka.ms/wudiag).
|
||||
|
||||
To run the tool, click the appropriate link above. Your web browser will prompt you to save or open the file. Select **open** and the tool will automatically start. The tool will walk you through analyzing and fixing some common problems.
|
||||
|
||||
You can also download the Windows Update Troubleshooter by starting the Microsoft [Virtual Agent](https://support.microsoft.com/contact/virtual-agent/), typing **update Windows**, selecting the version of Windows you are running, and then answering **Yes** when asked "Do you need help troubleshooting Windows Update?"
|
||||
|
||||
If any errors are displayed in the Windows Update Troubleshooter, use the Microsoft [Virtual Agent](https://support.microsoft.com/contact/virtual-agent/) to ask about these errors. The Virtual Agent will perform a search and provide a list of helpful links.
|
||||
|
||||
### Repair system files
|
||||
|
||||
This fix is also described in detail at [answers.microsoft.com](https://answers.microsoft.com/en-us/windows/forum/windows_10-update/system-file-check-sfc-scan-and-repair-system-files/bc609315-da1f-4775-812c-695b60477a93).
|
||||
|
||||
To check and repair system files:
|
||||
|
||||
1. Click **Start**.
|
||||
2. Type **command**.
|
||||
3. Right-click **Command Prompt** and then left-click **Run as administrator**.
|
||||
4. If you are prompted by UAC, click **Yes**.
|
||||
5. Type **sfc /scannow** and press ENTER. See the following example:
|
||||
|
||||
```
|
||||
C:\>sfc /scannow
|
||||
|
||||
Beginning system scan. This process will take some time.
|
||||
|
||||
Beginning verification phase of system scan.
|
||||
Verification 100% complete.
|
||||
|
||||
Windows Resource Protection did not find any integrity violations.
|
||||
```
|
||||
6. If you are running Windows 8.1 or later, type **DISM.exe /Online /Cleanup-image /Restorehealth** and press ENTER (the DISM command options are not available for Windows 7). See the following example:
|
||||
|
||||
```
|
||||
C:\>DISM.exe /Online /Cleanup-image /Restorehealth
|
||||
|
||||
Deployment Image Servicing and Management tool
|
||||
Version: 10.0.16299.15
|
||||
|
||||
Image Version: 10.0.16299.309
|
||||
|
||||
[==========================100.0%==========================] The restore operation completed successfully.
|
||||
The operation completed successfully.
|
||||
|
||||
```
|
||||
>It may take several minutes for the command operations to be completed. For more information, see [Repair a Windows Image](https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/repair-a-windows-image).
|
||||
|
||||
|
||||
### Update Windows
|
||||
|
||||
You should ensure that all important updates are installed before attempting to upgrade. This includes updates to hardware drivers on your computer.
|
||||
|
||||
The Microsoft [Virtual Agent](https://support.microsoft.com/contact/virtual-agent/) can walk you through the process of making sure that Windows is updated.
|
||||
|
||||
Start the [Virtual Agent](https://support.microsoft.com/contact/virtual-agent/) and then type "update windows."
|
||||
|
||||
Answer questions that the agent asks, and follow instructions to ensure that Windows is up to date. You can also run the [Windows Update Troubleshooter](#windows-update-troubleshooter) described above.
|
||||
|
||||
Click **Start**, click power options, and then restart the computer.
|
||||
|
||||
### Uninstall non-Microsoft antivirus software
|
||||
|
||||
Use Windows Defender for protection during the upgrade.
|
||||
|
||||
Verify compatibility information, and if desired re-install antivirus applications after the upgrade. If you plan to re-install the application after upgrading, be sure that you have the installation media and all required activation information before removing the program.
|
||||
|
||||
To remove the application, go to **Control Panel\Programs\Programs and Features** and click the antivirus application, then click Uninstall. Choose **Yes** when you are asked to confirm program removal.
|
||||
|
||||
For more information, see [Windows 7 - How to properly uninstall programs](https://support.microsoft.com/help/2601726) or [Repair or remove programs in Windows 10](https://support.microsoft.com/help/4028054/windows-repair-or-remove-programs-in-windows-10).
|
||||
|
||||
### Uninstall non-essential software
|
||||
|
||||
Outdated applications can cause problems with a Windows upgrade. Removing old or non-essential applications from the computer can therefore help.
|
||||
|
||||
If you plan to reinstall the application later, be sure that you have the installation media and all required activation information before removing it.
|
||||
|
||||
To remove programs, use the same steps as are provided [above](#uninstall-non-microsoft-antivirus-software) for uninstalling non-Microsoft antivirus software, but instead of removing the antivirus application repeat the steps for all your non-essential, unused, or out-of-date software.
|
||||
|
||||
### Update firmware and drivers
|
||||
|
||||
Updating firmware (such as the BIOS) and installing hardware drivers is a somewhat advanced task. Do not attempt to update BIOS if you aren't familiar with BIOS settings or are not sure how to restore the previous BIOS version if there are problems. Most BIOS updates are provided as a "flash" update. Your manufacturer might provide a tool to perform the update, or you might be required to enter the BIOS and update it manually. Be sure to save your working BIOS settings, since some updates can reset your configuration and make the computer fail to boot if (for example) a RAID configuration is changed.
|
||||
|
||||
Most BIOS and other hardware updates can be obtained from a website maintained by your computer manufacturer. For example, Microsoft Surface device drivers can be obtained at: [Download the latest firmware and drivers for Surface devices](https://docs.microsoft.com/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices).
|
||||
|
||||
To obtain the proper firmware drivers, search for the most updated driver version provided by your computer manufacturer. Install these updates and reboot the computer after installation. Request assistance from the manufacturer if you have any questions.
|
||||
|
||||
### Ensure that "Download and install updates" is selected
|
||||
|
||||
When you begin a Windows Update, the setup process will ask you to **Get important updates**. Answer **Yes** if the computer you are updating is connected to the Internet. See the following example:
|
||||
|
||||
|
||||
|
||||
### Verify disk space
|
||||
|
||||
You can see a list of requirements for Windows 10 at [Windows 10 Specifications & System Requirements](https://www.microsoft.com/windows/windows-10-specifications). One of the requirements is that enough hard drive space be available for the installation to take place. At least 16 GB of free space must be available on the system drive to upgrade a 32-bit OS, or 20 GB for a 64-bit OS.
|
||||
|
||||
To view how much hard drive space is available on your computer, open [File Explorer](https://support.microsoft.com/help/4026617/windows-windows-explorer-has-a-new-name). In Windows 7, this was called Windows Explorer.
|
||||
|
||||
In File Explorer, click on **Computer** or **This PC** on the left, then look under **Hard Disk Drives** or under **Devices and drives**. If there are multiple drives listed, the system drive is the drive that includes a Microsoft Windows logo above the drive icon.
|
||||
|
||||
The amount of space available on the system drive will be displayed under the drive. See the following example:
|
||||
|
||||
|
||||
|
||||
In the previous example, there is 703 GB of available free space on the system drive (C:).
|
||||
|
||||
To free up additional space on the system drive, begin by running Disk Cleanup. You can access Disk Cleanup by right-clicking the hard drive icon and then clicking Properties. See the following example:
|
||||
|
||||
|
||||
|
||||
For instructions to run Disk Cleanup and other suggestions to free up hard drive space, see [Tips to free up drive space on your PC](https://support.microsoft.com/help/17421/windows-free-up-drive-space).
|
||||
|
||||
When you run Disk Cleanup and enable the option to Clean up system files, you can remove previous Windows installations which can free a large amount of space. You should only do this if you do not plan to restore the old OS version.
|
||||
|
||||
### Open an elevated command prompt
|
||||
|
||||
>It is no longer necessary to open an elevated command prompt to run the [SetupDiag](setupdiag.md) tool. However, this is still the optimal way to run the tool.
|
||||
|
||||
To launch an elevated command prompt, press the Windows key on your keyboard, type **cmd**, press Ctrl+Shift+Enter, and then Alt+C to confirm the elevation prompt. Screenshots and other steps to open an administrator (aka elevated) command prompt are [here](https://answers.microsoft.com/en-us/windows/forum/windows_7-security/command-prompt-admin-windows-7/6a188166-5e23-461f-b468-f325688ec8c7).
|
||||
|
||||
Note: When you open an elevated command prompt, you will usually start in the **C:\WINDOWS\system32** directory. To run a program that you recently downloaded, you must change to the directory where the program is located. Alternatively, you can move or copy the program to a location on the computer that is automatically searched. These directories are listed in the [PATH variable](https://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings-winpc/adding-path-variable/97300613-20cb-4d85-8d0e-cc9d3549ba23).
|
||||
|
||||
If this is too complicated for you, then use File Explorer to create a new folder under C: with a short name such as "new" then copy or move the programs you want to run (like SetupDiag) to this folder using File Explorer. When you open an elevated command prompt, change to this directory by typing "cd c:\new" and now you can run the programs in that folder.
|
||||
|
||||
If you downloaded the SetupDiag.exe program to your computer, then copied it to the folder C:\new, and you opened an elevated command prompt then typed cd c:\new to change to this directory, you can just type setupdiag and press ENTER to run the program. This program will analyze the files on your computer to see why a Windows Upgrade failed and if the reason was a common one, it will report this reason. It will not fix the problem for you but knowing why the upgrade failed enables you to take steps to fix the problem.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Windows 10 FAQ for IT professionals](https://technet.microsoft.com/windows/dn798755.aspx)
|
||||
<br>[Windows 10 Enterprise system requirements](https://technet.microsoft.com/windows/dn798752.aspx)
|
||||
<br>[Windows 10 Specifications](https://www.microsoft.com/windows/Windows-10-specifications)
|
||||
<br>[Windows 10 IT pro forums](https://social.technet.microsoft.com/Forums/en-US/home?category=Windows10ITPro)
|
||||
<br>[Fix Windows Update errors by using the DISM or System Update Readiness tool](https://support.microsoft.com/kb/947821)
|
||||
---
|
||||
title: Quick fixes - Windows IT Pro
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description: Learn how to quickly resolve many problems which may come up during a Windows 10 upgrade.
|
||||
keywords: deploy, error, troubleshoot, windows, 10, upgrade, code, rollback, ITPro
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Quick fixes
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
|
||||
>[!NOTE]
|
||||
>This is a 100 level topic (basic).<br>
|
||||
>See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article.
|
||||
|
||||
The following list of fixes can resolve many Windows upgrade problems. You should try these steps before contacting Microsoft support, or attempting a more advanced analysis of a Windows upgrade failure. Also review information at [Windows 10 help](https://support.microsoft.com/products/windows?os=windows-10).
|
||||
|
||||
The Microsoft Virtual Agent provided by [Microsoft Support](https://support.microsoft.com/contactus/) can help you to analyze and correct some Windows upgrade errors. **To talk to a person about your issue**, start the Virtual Agent (click **Get started**) and enter "Talk to a person" two times.
|
||||
|
||||
> [!TIP]
|
||||
> You might also wish to try a new tool available from Microsoft that helps to diagnose many Windows upgrade errors. For more information and to download this tool, see [SetupDiag](setupdiag.md). The topic is more advanced (300 level) because several advanced options are available for using the tool. However, you can now just download and then double-click the tool to run it. By default when you click Save, the tool is saved in your **Downloads** folder. Double-click the tool in the folder and wait until it finishes running (it might take a few minutes), then double-click the **SetupDiagResults.log** file and open it using Notepad to see the results of the analysis.
|
||||
|
||||
## List of fixes
|
||||
|
||||
<ol>
|
||||
<li>Remove nonessential external hardware, such as docks and USB devices. <a href="#remove-external-hardware" data-raw-source="[More information](#remove-external-hardware)">More information</a>.</li>
|
||||
<li>Check the system drive for errors and attempt repairs. <a href="#repair-the-system-drive" data-raw-source="[More information](#repair-the-system-drive)">More information</a>.</li>
|
||||
<li>Run the Windows Update troubleshooter. <a href="#windows-update-troubleshooter" data-raw-source="[More information](#windows-update-troubleshooter)">More information</a>.</li>
|
||||
<li>Attempt to restore and repair system files. <a href="#repair-system-files" data-raw-source="[More information](#repair-system-files)">More information</a>.</li>
|
||||
<li>Update Windows so that all available recommended updates are installed, and ensure the computer is rebooted if this is necessary to complete installation of an update. <a href="#update-windows" data-raw-source="[More information](#update-windows)">More information</a>.</li>
|
||||
<li>Temporarily uninstall non-Microsoft antivirus software.
|
||||
<a href="#uninstall-non-microsoft-antivirus-software" data-raw-source="[More information](#uninstall-non-microsoft-antivirus-software)">More information</a>.</li>
|
||||
|
||||
<li>Uninstall all nonessential software. <a href="#uninstall-non-essential-software" data-raw-source="[More information](#uninstall-non-essential-software)">More information</a>.</li>
|
||||
<li>Update firmware and drivers. <a href="#update-firmware-and-drivers" data-raw-source="[More information](#update-firmware-and-drivers)">More information</a></li>
|
||||
<li>Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. <a href="#ensure-that-download-and-install-updates-is-selected" data-raw-source="[More information](#ensure-that-download-and-install-updates-is-selected)">More information</a>.</li>
|
||||
<li>Verify at least 16 GB of free space is available to upgrade a 32-bit OS, or 20 GB for a 64-bit OS. <a href="#verify-disk-space" data-raw-source="[More information](#verify-disk-space)">More information</a>.</li>
|
||||
</ol>
|
||||
|
||||
## Step by step instructions
|
||||
|
||||
### Remove external hardware
|
||||
|
||||
If the computer is portable and it is currently in a docking station, [undock the computer](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754084(v=ws.11)).
|
||||
|
||||
Unplug nonessential external hardware devices from the computer, such as:
|
||||
- Headphones
|
||||
- Joysticks
|
||||
- Printers
|
||||
- Plotters
|
||||
- Projectors
|
||||
- Scanners
|
||||
- Speakers
|
||||
- USB flash drives
|
||||
- Portable hard drives
|
||||
- Portable CD/DVD/Blu-ray drives
|
||||
- Microphones
|
||||
- Media card readers
|
||||
- Cameras/Webcams
|
||||
- Smart phones
|
||||
- Secondary monitors, keyboards, mice
|
||||
|
||||
For more information about disconnecting external devices, see [Safely remove hardware in Windows 10](https://support.microsoft.com/help/4051300/windows-10-safely-remove-hardware)
|
||||
|
||||
### Repair the system drive
|
||||
|
||||
The system drive is the drive that contains the [system partition](https://docs.microsoft.com/windows-hardware/manufacture/desktop/hard-drives-and-partitions#span-idpartitionsspanspan-idpartitionsspanspan-idpartitionsspanpartitions). This is usually the **C:** drive.
|
||||
|
||||
To check and repair errors on the system drive:
|
||||
|
||||
1. Click **Start**.
|
||||
2. Type **command**.
|
||||
3. Right-click **Command Prompt** and then left-click **Run as administrator**.
|
||||
4. If you are prompted by UAC, click **Yes**.
|
||||
5. Type **chkdsk /F** and press ENTER.
|
||||
6. When you are prompted to schedule a check the next time the system restarts, type **Y**.
|
||||
7. See the following example
|
||||
|
||||
```
|
||||
C:\WINDOWS\system32>chkdsk /F
|
||||
The type of the file system is NTFS.
|
||||
Cannot lock current drive.
|
||||
|
||||
Chkdsk cannot run because the volume is in use by another
|
||||
process. Would you like to schedule this volume to be
|
||||
checked the next time the system restarts? (Y/N) Y
|
||||
|
||||
This volume will be checked the next time the system restarts.
|
||||
```
|
||||
|
||||
8. Restart the computer. The computer will pause before loading Windows and perform a repair of your hard drive.
|
||||
|
||||
### Windows Update Troubleshooter
|
||||
|
||||
The Windows Update troubleshooter tool will automatically analyze and fix problems with Windows Update, such as a corrupted download. It will also tell you if there is a pending reboot that is preventing Windows from updating.
|
||||
|
||||
For Windows 7 and 8.1, the tool is [here](https://aka.ms/diag_wu).
|
||||
|
||||
For Windows 10, the tool is [here](https://aka.ms/wudiag).
|
||||
|
||||
To run the tool, click the appropriate link above. Your web browser will prompt you to save or open the file. Select **open** and the tool will automatically start. The tool will walk you through analyzing and fixing some common problems.
|
||||
|
||||
You can also download the Windows Update Troubleshooter by starting the Microsoft [Virtual Agent](https://support.microsoft.com/contact/virtual-agent/), typing **update Windows**, selecting the version of Windows you are running, and then answering **Yes** when asked "Do you need help troubleshooting Windows Update?"
|
||||
|
||||
If any errors are displayed in the Windows Update Troubleshooter, use the Microsoft [Virtual Agent](https://support.microsoft.com/contact/virtual-agent/) to ask about these errors. The Virtual Agent will perform a search and provide a list of helpful links.
|
||||
|
||||
### Repair system files
|
||||
|
||||
This fix is also described in detail at [answers.microsoft.com](https://answers.microsoft.com/en-us/windows/forum/windows_10-update/system-file-check-sfc-scan-and-repair-system-files/bc609315-da1f-4775-812c-695b60477a93).
|
||||
|
||||
To check and repair system files:
|
||||
|
||||
1. Click **Start**.
|
||||
2. Type **command**.
|
||||
3. Right-click **Command Prompt** and then left-click **Run as administrator**.
|
||||
4. If you are prompted by UAC, click **Yes**.
|
||||
5. Type **sfc /scannow** and press ENTER. See the following example:
|
||||
|
||||
```
|
||||
C:\>sfc /scannow
|
||||
|
||||
Beginning system scan. This process will take some time.
|
||||
|
||||
Beginning verification phase of system scan.
|
||||
Verification 100% complete.
|
||||
|
||||
Windows Resource Protection did not find any integrity violations.
|
||||
```
|
||||
6. If you are running Windows 8.1 or later, type **DISM.exe /Online /Cleanup-image /Restorehealth** and press ENTER (the DISM command options are not available for Windows 7). See the following example:
|
||||
|
||||
```
|
||||
C:\>DISM.exe /Online /Cleanup-image /Restorehealth
|
||||
|
||||
Deployment Image Servicing and Management tool
|
||||
Version: 10.0.16299.15
|
||||
|
||||
Image Version: 10.0.16299.309
|
||||
|
||||
[==========================100.0%==========================] The restore operation completed successfully.
|
||||
The operation completed successfully.
|
||||
|
||||
```
|
||||
> [!NOTE]
|
||||
> It may take several minutes for the command operations to be completed. For more information, see [Repair a Windows Image](https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/repair-a-windows-image).
|
||||
|
||||
|
||||
### Update Windows
|
||||
|
||||
You should ensure that all important updates are installed before attempting to upgrade. This includes updates to hardware drivers on your computer.
|
||||
|
||||
The Microsoft [Virtual Agent](https://support.microsoft.com/contact/virtual-agent/) can walk you through the process of making sure that Windows is updated.
|
||||
|
||||
Start the [Virtual Agent](https://support.microsoft.com/contact/virtual-agent/) and then type "update windows."
|
||||
|
||||
Answer questions that the agent asks, and follow instructions to ensure that Windows is up to date. You can also run the [Windows Update Troubleshooter](#windows-update-troubleshooter) described above.
|
||||
|
||||
Click **Start**, click power options, and then restart the computer.
|
||||
|
||||
### Uninstall non-Microsoft antivirus software
|
||||
|
||||
Use Windows Defender for protection during the upgrade.
|
||||
|
||||
Verify compatibility information, and if desired re-install antivirus applications after the upgrade. If you plan to re-install the application after upgrading, be sure that you have the installation media and all required activation information before removing the program.
|
||||
|
||||
To remove the application, go to **Control Panel\Programs\Programs and Features** and click the antivirus application, then click Uninstall. Choose **Yes** when you are asked to confirm program removal.
|
||||
|
||||
For more information, see [Windows 7 - How to properly uninstall programs](https://support.microsoft.com/help/2601726) or [Repair or remove programs in Windows 10](https://support.microsoft.com/help/4028054/windows-repair-or-remove-programs-in-windows-10).
|
||||
|
||||
### Uninstall non-essential software
|
||||
|
||||
Outdated applications can cause problems with a Windows upgrade. Removing old or non-essential applications from the computer can therefore help.
|
||||
|
||||
If you plan to reinstall the application later, be sure that you have the installation media and all required activation information before removing it.
|
||||
|
||||
To remove programs, use the same steps as are provided [above](#uninstall-non-microsoft-antivirus-software) for uninstalling non-Microsoft antivirus software, but instead of removing the antivirus application repeat the steps for all your non-essential, unused, or out-of-date software.
|
||||
|
||||
### Update firmware and drivers
|
||||
|
||||
Updating firmware (such as the BIOS) and installing hardware drivers is a somewhat advanced task. Do not attempt to update BIOS if you aren't familiar with BIOS settings or are not sure how to restore the previous BIOS version if there are problems. Most BIOS updates are provided as a "flash" update. Your manufacturer might provide a tool to perform the update, or you might be required to enter the BIOS and update it manually. Be sure to save your working BIOS settings, since some updates can reset your configuration and make the computer fail to boot if (for example) a RAID configuration is changed.
|
||||
|
||||
Most BIOS and other hardware updates can be obtained from a website maintained by your computer manufacturer. For example, Microsoft Surface device drivers can be obtained at: [Download the latest firmware and drivers for Surface devices](https://docs.microsoft.com/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices).
|
||||
|
||||
To obtain the proper firmware drivers, search for the most updated driver version provided by your computer manufacturer. Install these updates and reboot the computer after installation. Request assistance from the manufacturer if you have any questions.
|
||||
|
||||
### Ensure that "Download and install updates" is selected
|
||||
|
||||
When you begin a Windows Update, the setup process will ask you to **Get important updates**. Answer **Yes** if the computer you are updating is connected to the Internet. See the following example:
|
||||
|
||||
|
||||
|
||||
### Verify disk space
|
||||
|
||||
You can see a list of requirements for Windows 10 at [Windows 10 Specifications & System Requirements](https://www.microsoft.com/windows/windows-10-specifications). One of the requirements is that enough hard drive space be available for the installation to take place. At least 16 GB of free space must be available on the system drive to upgrade a 32-bit OS, or 20 GB for a 64-bit OS.
|
||||
|
||||
To view how much hard drive space is available on your computer, open [File Explorer](https://support.microsoft.com/help/4026617/windows-windows-explorer-has-a-new-name). In Windows 7, this was called Windows Explorer.
|
||||
|
||||
In File Explorer, click on **Computer** or **This PC** on the left, then look under **Hard Disk Drives** or under **Devices and drives**. If there are multiple drives listed, the system drive is the drive that includes a Microsoft Windows logo above the drive icon.
|
||||
|
||||
The amount of space available on the system drive will be displayed under the drive. See the following example:
|
||||
|
||||
|
||||
|
||||
In the previous example, there is 703 GB of available free space on the system drive (C:).
|
||||
|
||||
To free up additional space on the system drive, begin by running Disk Cleanup. You can access Disk Cleanup by right-clicking the hard drive icon and then clicking Properties. See the following example:
|
||||
|
||||
|
||||
|
||||
For instructions to run Disk Cleanup and other suggestions to free up hard drive space, see [Tips to free up drive space on your PC](https://support.microsoft.com/help/17421/windows-free-up-drive-space).
|
||||
|
||||
When you run Disk Cleanup and enable the option to Clean up system files, you can remove previous Windows installations which can free a large amount of space. You should only do this if you do not plan to restore the old OS version.
|
||||
|
||||
### Open an elevated command prompt
|
||||
|
||||
> [!TIP]
|
||||
> It is no longer necessary to open an elevated command prompt to run the [SetupDiag](setupdiag.md) tool. However, this is still the optimal way to run the tool.
|
||||
|
||||
To launch an elevated command prompt, press the Windows key on your keyboard, type **cmd**, press Ctrl+Shift+Enter, and then Alt+C to confirm the elevation prompt. Screenshots and other steps to open an administrator (aka elevated) command prompt are [here](https://answers.microsoft.com/en-us/windows/forum/windows_7-security/command-prompt-admin-windows-7/6a188166-5e23-461f-b468-f325688ec8c7).
|
||||
|
||||
Note: When you open an elevated command prompt, you will usually start in the **C:\WINDOWS\system32** directory. To run a program that you recently downloaded, you must change to the directory where the program is located. Alternatively, you can move or copy the program to a location on the computer that is automatically searched. These directories are listed in the [PATH variable](https://answers.microsoft.com/windows/forum/windows_10-other_settings-winpc/adding-path-variable/97300613-20cb-4d85-8d0e-cc9d3549ba23).
|
||||
|
||||
If this is too complicated for you, then use File Explorer to create a new folder under C: with a short name such as "new" then copy or move the programs you want to run (like SetupDiag) to this folder using File Explorer. When you open an elevated command prompt, change to this directory by typing "cd c:\new" and now you can run the programs in that folder.
|
||||
|
||||
If you downloaded the SetupDiag.exe program to your computer, then copied it to the folder C:\new, and you opened an elevated command prompt then typed cd c:\new to change to this directory, you can just type setupdiag and press ENTER to run the program. This program will analyze the files on your computer to see why a Windows Upgrade failed and if the reason was a common one, it will report this reason. It will not fix the problem for you but knowing why the upgrade failed enables you to take steps to fix the problem.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Windows 10 FAQ for IT professionals](https://technet.microsoft.com/windows/dn798755.aspx)
|
||||
<br>[Windows 10 Enterprise system requirements](https://technet.microsoft.com/windows/dn798752.aspx)
|
||||
<br>[Windows 10 Specifications](https://www.microsoft.com/windows/Windows-10-specifications)
|
||||
<br>[Windows 10 IT pro forums](https://social.technet.microsoft.com/Forums/en-US/home?category=Windows10ITPro)
|
||||
<br>[Fix Windows Update errors by using the DISM or System Update Readiness tool](https://support.microsoft.com/kb/947821)
|
||||
|
||||
@ -3,7 +3,7 @@ title: Resolution procedures - Windows IT Pro
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description: Resolve Windows 10 upgrade errors for ITPros. Technical information for IT professionals to help diagnose Windows setup errors.
|
||||
description: Discover general troubleshooting procedures for dealing with 0xC1900101, the generic rollback code thrown when something goes wrong during a Windows 10 upgrade.
|
||||
keywords: deploy, error, troubleshoot, windows, 10, upgrade, code, rollback, ITPro
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -3,7 +3,7 @@ title: Troubleshoot Windows 10 upgrade errors - Windows IT Pro
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description: Resolve Windows 10 upgrade errors for ITPros. Technical information for IT professionals to help diagnose Windows setup errors.
|
||||
description: Understanding the Windows 10 upgrade process can help you troubleshoot errors when something goes wrong. Find out more with this guide.
|
||||
keywords: deploy, error, troubleshoot, windows, 10, upgrade, code, rollback, ITPro
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -3,7 +3,7 @@ title: Upgrade error codes - Windows IT Pro
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description: Resolve Windows 10 upgrade errors for ITPros. Technical information for IT professionals to help diagnose Windows setup errors.
|
||||
description: Understand the error codes that may come up if something goes wrong during the Windows 10 upgrade process.
|
||||
keywords: deploy, error, troubleshoot, windows, 10, upgrade, code, rollback, ITPro
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -30,7 +30,7 @@ If the upgrade process is not successful, Windows Setup will return two codes:
|
||||
1. **A result code**: The result code corresponds to a specific Win32 or NTSTATUS error.
|
||||
2. **An extend code**: The extend code contains information about both the *phase* in which an error occurred, and the *operation* that was being performed when the error occurred.
|
||||
|
||||
>For example, a result code of **0xC1900101** with an extend code of **0x4000D** will be returned as: **0xC1900101 - 0x4000D**.
|
||||
For example, a result code of **0xC1900101** with an extend code of **0x4000D** will be returned as: **0xC1900101 - 0x4000D**.
|
||||
|
||||
Note: If only a result code is returned, this can be because a tool is being used that was not able to capture the extend code. For example, if you are using the [Windows 10 Upgrade Assistant](https://support.microsoft.com/kb/3159635) then only a result code might be returned.
|
||||
|
||||
@ -39,7 +39,7 @@ Note: If only a result code is returned, this can be because a tool is being use
|
||||
|
||||
## Result codes
|
||||
|
||||
>A result code of **0xC1900101** is generic and indicates that a rollback occurred. In most cases, the cause is a driver compatibility issue. <br>To troubleshoot a failed upgrade that has returned a result code of 0xC1900101, analyze the extend code to determine the Windows Setup phase, and see the [Resolution procedures](resolution-procedures.md) section later in this article.
|
||||
A result code of **0xC1900101** is generic and indicates that a rollback occurred. In most cases, the cause is a driver compatibility issue. <br>To troubleshoot a failed upgrade that has returned a result code of 0xC1900101, analyze the extend code to determine the Windows Setup phase, and see the [Resolution procedures](resolution-procedures.md) section later in this article.
|
||||
|
||||
The following set of result codes are associated with [Windows Setup](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-setup-command-line-options) compatibility warnings:
|
||||
|
||||
@ -77,7 +77,8 @@ Some result codes are self-explanatory, whereas others are more generic and requ
|
||||
|
||||
## Extend codes
|
||||
|
||||
>**Important**: Extend codes reflect the current Windows 10 upgrade process, and might change in future releases of Windows 10. The codes discussed in this section apply to Windows 10 version 1607, also known as the Anniversary Update.
|
||||
>[!IMPORTANT]
|
||||
>Extend codes reflect the current Windows 10 upgrade process, and might change in future releases of Windows 10. The codes discussed in this section apply to Windows 10 version 1607, also known as the Anniversary Update.
|
||||
|
||||
Extend codes can be matched to the phase and operation when an error occurred. To match an extend code to the phase and operation:
|
||||
|
||||
|
||||
@ -33,7 +33,7 @@ In order to use the direct connection scenario, set the parameter **ClientProxy=
|
||||
|
||||
### Connection through the WinHTTP proxy
|
||||
|
||||
This is the first and most simple proxy scenario. The WinHTTP stack was designed for use in services and does not support proxy autodetection, PAC scripts or authentication.
|
||||
This is the first and most simple proxy scenario.
|
||||
|
||||
In order to set the WinHTTP proxy system-wide on your computers, you need to
|
||||
- Use the command netsh winhttp set proxy \<server\>:\<port\>
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Perform in-place upgrade to Windows 10 via Configuration Manager
|
||||
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. Use a System Center Configuration Manager task sequence to completely automate the process.
|
||||
description: In-place upgrades make upgrading Windows 7, Windows 8, and Windows 8.1 to Windows 10 easy -- you can even automate the whole process with a SCCM task sequence.
|
||||
ms.assetid: F8DF6191-0DB0-4EF5-A9B1-6A11D5DE4878
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -3,7 +3,7 @@ title: Windows error reporting - Windows IT Pro
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
description: Resolve Windows 10 upgrade errors for ITPros. Technical information for IT professionals to help diagnose Windows setup errors.
|
||||
description: Learn how to review the events generated by Windows Error Reporting when something goes wrong during Windows 10 setup.
|
||||
keywords: deploy, error, troubleshoot, windows, 10, upgrade, code, rollback, ITPro
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
@ -1,79 +1,80 @@
|
||||
---
|
||||
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
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Use the Volume Activation Management Tool
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
**Looking for retail activation?**
|
||||
- [Get Help Activating Microsoft Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
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.
|
||||
|
||||
By using the VAMT, you can automate and centrally manage the volume, retail, and MAK activation process for Windows, Office, and select other Microsoft products. The VAMT can manage volume activation by using MAKs or KMS. It is a standard Microsoft Management Console snap-in, and it can be
|
||||
installed on any computer running Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2.
|
||||
|
||||
The VAMT is distributed as part of the Windows Assessment and Deployment Kit (Windows ADK), which is a free download available from Microsoft Download Center. For more information, see [Windows Assessment and Deployment Kit (Windows ADK) for Windows 10](https://go.microsoft.com/fwlink/p/?LinkId=526740).
|
||||
|
||||
In Windows Server 2012 R2, you can install the VAMT directly from Server Manager without downloading the Windows ADK by selecting the Volume Activation Services role or the Remote Server Administration Tools/Role Administration Tools/Volume Activation Tools feature.
|
||||
|
||||
## Activating with the Volume Activation Management Tool
|
||||
|
||||
You can use the VAMT to complete the activation process in products by using MAK and retail keys, and you can work with computers individually or in groups. The VAMT enables two activation scenarios:
|
||||
- **Online activation**. Online activation enables you to activate over the Internet any products that are installed with MAK, KMS host, or retail product keys. You can activate one or more connected computers within a network. This process requires that each product communicate activation information directly to Microsoft.
|
||||
- **Proxy activation**. This activation method enables you to perform volume activation for products that are installed on client computers that do not have Internet access. The VAMT host computer distributes a MAK, KMS host key, or retail product key to one or more client products and collects the installation ID from each client product. The VAMT host sends the installation IDs to Microsoft on behalf of the client products and obtains the corresponding confirmation IDs. The VAMT host then installs the confirmation IDs on the client products to complete their activation.
|
||||
By using this method, only the VAMT host computer requires Internet access. Proxy activation by using the VAMT is beneficial for isolated network segments and for cases where your organization has a mix of retail, MAK, and KMS-based activations.
|
||||
|
||||
## Tracking products and computers with the Volume Activation Management Tool
|
||||
|
||||
The VAMT provides an overview of the activation and licensing status of computers across your network, as shown in Figure 18. Several prebuilt reports are also available to help you proactively manage licensing.
|
||||
|
||||
|
||||
|
||||
**Figure 18**. The VAMT showing the licensing status of multiple computers
|
||||
|
||||
## Tracking key usage with the Volume Activation Management Tool
|
||||
|
||||
The VAMT makes it easier to track the various keys that are issued to your organization. You can enter each key into VAMT, and then the VAMT can use those keys for online or proxy activation of clients. The tool can also describe what type of key it is and to which product group it belongs. The VAMT is the most convenient way to quickly determine how many activations remain on a MAK. Figure 19 shows an example of key types and usage.
|
||||
|
||||
|
||||
|
||||
**Figure 19**. The VAMT showing key types and usage
|
||||
|
||||
## Other Volume Activation Management Tool features
|
||||
|
||||
The VAMT stores information in a Microsoft SQL Server database for performance and flexibility, and it provides a single graphical user interface for managing activations and performing other activation-related tasks, such as:
|
||||
- **Adding and removing computers**. You can use the VAMT to discover computers in the local environment. The VAMT can discover computers by querying AD DS, workgroups, or individual computer names or IP addresses, or through a general LDAP query.
|
||||
- **Discovering products**. You can use the VAMT to discover Windows, Windows Server, Office, and select other products that are installed on the client computers.
|
||||
- **Managing activation data**. The VAMT stores activation data in a SQL Server database. The tool can export this data in XML format to other VAMT hosts or to an archive.
|
||||
|
||||
For more information, see:
|
||||
- [Volume Activation Management Tool (VAMT) Overview](https://go.microsoft.com/fwlink/p/?LinkId=618266)
|
||||
- [VAMT Step-by-Step Scenarios](https://go.microsoft.com/fwlink/p/?LinkId=618267)
|
||||
|
||||
## See also
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
|
||||
---
|
||||
title: Use the Volume Activation Management Tool (Windows 10)
|
||||
description: The Volume Activation Management Tool (VAMT) provides several useful features, including the ability to track and monitor several types of product keys.
|
||||
ms.assetid: b11f0aee-7b60-44d1-be40-c960fc6c4c47
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: vamt, volume activation, activation, windows activation
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Use the Volume Activation Management Tool
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
**Looking for retail activation?**
|
||||
- [Get Help Activating Microsoft Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
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.
|
||||
|
||||
By using the VAMT, you can automate and centrally manage the volume, retail, and MAK activation process for Windows, Office, and select other Microsoft products. The VAMT can manage volume activation by using MAKs or KMS. It is a standard Microsoft Management Console snap-in, and it can be
|
||||
installed on any computer running Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2.
|
||||
|
||||
The VAMT is distributed as part of the Windows Assessment and Deployment Kit (Windows ADK), which is a free download available from Microsoft Download Center. For more information, see [Windows Assessment and Deployment Kit (Windows ADK) for Windows 10](https://go.microsoft.com/fwlink/p/?LinkId=526740).
|
||||
|
||||
In Windows Server 2012 R2, you can install the VAMT directly from Server Manager without downloading the Windows ADK by selecting the Volume Activation Services role or the Remote Server Administration Tools/Role Administration Tools/Volume Activation Tools feature.
|
||||
|
||||
## Activating with the Volume Activation Management Tool
|
||||
|
||||
You can use the VAMT to complete the activation process in products by using MAK and retail keys, and you can work with computers individually or in groups. The VAMT enables two activation scenarios:
|
||||
- **Online activation**. Online activation enables you to activate over the Internet any products that are installed with MAK, KMS host, or retail product keys. You can activate one or more connected computers within a network. This process requires that each product communicate activation information directly to Microsoft.
|
||||
- **Proxy activation**. This activation method enables you to perform volume activation for products that are installed on client computers that do not have Internet access. The VAMT host computer distributes a MAK, KMS host key, or retail product key to one or more client products and collects the installation ID from each client product. The VAMT host sends the installation IDs to Microsoft on behalf of the client products and obtains the corresponding confirmation IDs. The VAMT host then installs the confirmation IDs on the client products to complete their activation.
|
||||
By using this method, only the VAMT host computer requires Internet access. Proxy activation by using the VAMT is beneficial for isolated network segments and for cases where your organization has a mix of retail, MAK, and KMS-based activations.
|
||||
|
||||
## Tracking products and computers with the Volume Activation Management Tool
|
||||
|
||||
The VAMT provides an overview of the activation and licensing status of computers across your network, as shown in Figure 18. Several prebuilt reports are also available to help you proactively manage licensing.
|
||||
|
||||
|
||||
|
||||
**Figure 18**. The VAMT showing the licensing status of multiple computers
|
||||
|
||||
## Tracking key usage with the Volume Activation Management Tool
|
||||
|
||||
The VAMT makes it easier to track the various keys that are issued to your organization. You can enter each key into VAMT, and then the VAMT can use those keys for online or proxy activation of clients. The tool can also describe what type of key it is and to which product group it belongs. The VAMT is the most convenient way to quickly determine how many activations remain on a MAK. Figure 19 shows an example of key types and usage.
|
||||
|
||||
|
||||
|
||||
**Figure 19**. The VAMT showing key types and usage
|
||||
|
||||
## Other Volume Activation Management Tool features
|
||||
|
||||
The VAMT stores information in a Microsoft SQL Server database for performance and flexibility, and it provides a single graphical user interface for managing activations and performing other activation-related tasks, such as:
|
||||
- **Adding and removing computers**. You can use the VAMT to discover computers in the local environment. The VAMT can discover computers by querying AD DS, workgroups, or individual computer names or IP addresses, or through a general LDAP query.
|
||||
- **Discovering products**. You can use the VAMT to discover Windows, Windows Server, Office, and select other products that are installed on the client computers.
|
||||
- **Managing activation data**. The VAMT stores activation data in a SQL Server database. The tool can export this data in XML format to other VAMT hosts or to an archive.
|
||||
|
||||
For more information, see:
|
||||
- [Volume Activation Management Tool (VAMT) Overview](https://go.microsoft.com/fwlink/p/?LinkId=618266)
|
||||
- [VAMT Step-by-Step Scenarios](https://go.microsoft.com/fwlink/p/?LinkId=618267)
|
||||
|
||||
## See also
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
|
||||
|
||||
@ -1,25 +1,69 @@
|
||||
---
|
||||
title: VAMT Known Issues (Windows 10)
|
||||
description: VAMT Known Issues
|
||||
ms.assetid: 8992f1f3-830a-4ce7-a248-f3a6377ab77f
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# VAMT Known Issues
|
||||
|
||||
The following list contains the current known issues with the Volume Activation Management Tool (VAMT) 3.0.
|
||||
- The VAMT Windows Management Infrastructure (WMI) remote operations may take longer to execute if the target computer is in a sleep or standby state.
|
||||
- Recovery of Non-Genuine computers is a two-step process. VAMT can be used to install a new product key and activate the computer. However, the computer itself must visit the [Windows Genuine Advantage](https://go.microsoft.com/fwlink/p/?linkid=182914) Web site to revalidate the computer's Genuine status. Upon successfully completing this step, the computer will be restored to full functionality. For more information on recovering Non-Genuine Windows computers, go to [Windows Volume Activation](https://go.microsoft.com/fwlink/p/?linkid=184668).
|
||||
- When opening a Computer Information List (.cil file) saved in a previous version of VAMT, the edition information is not shown for each product in the center pane. Users must update the product status again to obtain the edition information.
|
||||
- The remaining activation count can only be retrieved for MAKs.
|
||||
|
||||
|
||||
---
|
||||
title: VAMT known issues (Windows 10)
|
||||
description: Volume Activation Management Tool (VAMT) known issues
|
||||
ms.assetid: 8992f1f3-830a-4ce7-a248-f3a6377ab77f
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 12/17/2019
|
||||
ms.topic: article
|
||||
ms.custom:
|
||||
- CI 111496
|
||||
- CSSTroubleshooting
|
||||
---
|
||||
|
||||
# VAMT known issues
|
||||
|
||||
The following list and the section that follows contain the current known issues regarding the Volume Activation Management Tool (VAMT), versions 3.0. and 3.1.
|
||||
|
||||
- VAMT Windows Management Infrastructure (WMI) remote operations might take longer to execute if the target computer is in a sleep or standby state.
|
||||
- When opening a Computer Information List (CIL file) that was saved by using a previous version of VAMT, the edition information is not shown for each product in the center pane. Users must update the product status again to obtain the edition information.
|
||||
- The remaining activation count can only be retrieved for MAKs.
|
||||
|
||||
## Can't add CSVLKs for Windows 10 activation to VAMT 3.1
|
||||
|
||||
When you try to add a Windows 10 Key Management Service (KMS) Host key (CSVLK) or a Windows Server 2012 R2 for Windows 10 CSVLK into VAMT 3.1 (version 10.0.10240.0), you receive the following error message:
|
||||
|
||||
> The specified product key is invalid, or is unsupported by this version of VAMT. An update to support additional products may be available online.
|
||||
|
||||
|
||||
|
||||
This issue occurs because VAMT 3.1 does not contain the correct Pkconfig files to recognize this kind of key.
|
||||
|
||||
### Workaround
|
||||
|
||||
To work around this issue, use one of the following methods.
|
||||
|
||||
**Method 1**
|
||||
|
||||
Do not add the CSVLK to the VAMT 3.1 tool. Instead, use the **slmgr.vbs /ipk \<*CSVLK*>** command-line tool to install a CSVLK on a KMS host. In this command, \<*CSVLK*> represents the specific key that you want to install. For more information about how to use the Slmgr.vbs tool, see [Slmgr.vbs options for obtaining volume activation information](https://docs.microsoft.com/windows-server/get-started/activation-slmgr-vbs-options).
|
||||
|
||||
**Method 2**
|
||||
|
||||
On the KMS host computer, follow these steps:
|
||||
|
||||
1. Download the hotfix from [July 2016 update rollup for Windows 8.1 and Windows Server 2012 R2](https://support.microsoft.com/help/3172614/).
|
||||
|
||||
1. In Windows Explorer, right-click **485392_intl_x64_zip**, and then extract the hotfix to **C:\KB3058168**.
|
||||
|
||||
1. To extract the contents of the update, open a Command Prompt window and run the following command:
|
||||
|
||||
```cmd
|
||||
expand c:\KB3058168\Windows8.1-KB3058168-x64.msu -f:* C:\KB3058168\
|
||||
```
|
||||
|
||||
1. To extract the contents of Windows8.1-KB3058168-x64.cab, run the following command:
|
||||
|
||||
```cmd
|
||||
expand c:\KB3058168\Windows8.1-KB3058168-x64.cab -f:pkeyconfig-csvlk.xrm-ms c:\KB3058168
|
||||
```
|
||||
|
||||
1. In the "C:\KB3058168\x86_microsoft-windows-s..nent-sku-csvlk-pack_31bf3856ad364e35_6.3.9600.17815_none_bd26b4f34d049716\" folder, copy the **pkeyconfig-csvlk.xrm-ms** file. Paste this file to the "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\VAMT3\pkconfig" folder.
|
||||
|
||||
1. Restart VAMT.
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Volume Activation for Windows 10
|
||||
description: 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.
|
||||
description: Learn how to use volume activation to deploy & activate Windows 10. Includes details for orgs that have used volume activation for earlier versions of Windows.
|
||||
ms.assetid: 6e8cffae-7322-4fd3-882a-cde68187aef2
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows 10 deployment tools
|
||||
description: Learn about the tools available to deploy Windows 10.
|
||||
description: Browse through documentation describing Windows 10 deployment tools. Learn how to use these these tools to successfully deploy Windows 10 to your organization.
|
||||
ms.assetid: 5C4B0AE3-B2D0-4628-9E73-606F3FAA17BB
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
|
||||
@ -1,94 +1,97 @@
|
||||
---
|
||||
title: Windows 10 volume license media
|
||||
description: There are specific infrastructure requirements to deploy and manage Windows 10 that should be in place prior to significant Windows 10 deployments within your organization.
|
||||
keywords: deploy, upgrade, update, software, media
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 10/20/2017
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.audience: itpro
author: greg-lindsay
|
||||
ms.sitesec: library
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Windows 10 volume license media
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
With each release of Windows 10, volume license media is made available on the [Volume Licensing Service Center](https://www.microsoft.com/vlsc) (VLSC) and other relevant channels such as Windows Update for Business, Windows Server Update Services (WSUS), and Visual Studio Subscriptions. This topic provides a description of volume license media, and describes some of the changes that have been implemented with the current release of Windows 10.
|
||||
|
||||
## Windows 10 media
|
||||
|
||||
To download Windows 10 installation media from the VLSC, use the product search filter to find “Windows 10.” A list of products will be displayed. The page then allows you to use your search results to download products, view keys, and view product and key descriptions.
|
||||
|
||||
When you select a product, for example “Windows 10 Enterprise” or “Windows 10 Education”, you can then choose the specific release by clicking **Download** and choosing the **Download Method**, **Language**, and **Operating system Type** (bitness).
|
||||
|
||||
>If you do not see a Windows 10 release available in the list of downloads, verify the [release date](https://technet.microsoft.com/windows/release-info.aspx).
|
||||
|
||||
In Windows 10, version 1709 the packaging of volume licensing media and upgrade packages is different than it has been for previous releases. Instead of having separate media and packages for Windows 10 Pro (volume licensing version), Windows 10 Enterprise, and Windows 10 Education, all three are bundled together. The following section explains this change.
|
||||
|
||||
### Windows 10, version 1709
|
||||
|
||||
Windows 10, version 1709 is available starting on 10/17/2017 in all relevant distribution channels. Note: An updated [Windows ADK for Windows 10](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit) is also available.
|
||||
|
||||
For ISOs that you download from the VLSC or Visual Studio Subscriptions, you can still search for the individual Windows editions. However, each of these editions (Windows 10 Pro, Windows 10 Enterprise, and Windows 10 Education) will point to the same ISO file, so you only need to download the ISO once. A single Windows image (WIM) file is included in the ISO that contains all the volume licensing images:
|
||||
|
||||
|
||||
|
||||
When using the contents of these ISOs with tools such as the Microsoft Deployment Toolkit or System Center Configuration Manager, make sure you select the appropriate image index in any task sequences that you create or update.
|
||||
|
||||
For packages published to Windows Server Update Services (WSUS), you’ll also notice the change because, instead of having separate packages for each Windows edition, there will be just one package:
|
||||
|
||||
<br>
|
||||
|
||||
| Title | Classification | Description |
|
||||
| --- | --- | --- |
|
||||
| Feature update to Windows 10, version 1709, \<language\> | Upgrades | Package to upgrade Windows 10 Pro (VL), Windows 10 Enterprise, or Windows 10 Education to version 1709 |
|
||||
| Windows 7 and 8.1 upgrade to Windows 10, version 1709, \<language\> | Upgrades | Package to upgrade Windows 7 Professional (VL), Windows 7 Enterprise, Windows 8.1 Professional (VL), or Windows 8.1 Enterprise to Windows 10 1709 |
|
||||
|
||||
<br>
|
||||
|
||||
When you approve one of these packages, it applies to all of the editions.
|
||||
|
||||
This Semi-Annual Channel release of Windows 10 continues the Windows as a service methodology. For more information about implementing Windows as a service in your organization in order to stay up to date with Windows, see [Update Windows 10 in the enterprise](https://aka.ms/waas).
|
||||
|
||||
|
||||
### Language packs
|
||||
|
||||
- **Windows 10 versions 1507 and 1511**: you can select **Windows 10 Enterprise Language Pack**, click **Download** and then select **English** and **64-bit** to see these downloads.
|
||||
- **Windows 10 1607 and later**: you must select **Multilanguage** from the drop-down list of languages.
|
||||
|
||||
See the following example for Windows 10, version 1709:
|
||||
|
||||
|
||||
|
||||
### Features on demand
|
||||
|
||||
[Features on demand](https://blogs.technet.microsoft.com/mniehaus/2015/08/31/adding-features-including-net-3-5-to-windows-10/) can be downloaded by searching for "**Windows 10 Enterprise Features on Demand**" and then following the same download process that is described above.
|
||||
|
||||
Features on demand is a method for adding features to your Windows 10 image that aren’t included in the base operating system image.
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
[Microsoft Volume Licensing Service Center (VLSC) User Guide](https://www.microsoft.com/download/details.aspx?id=10585)
|
||||
<br>[Volume Activation for Windows 10](https://docs.microsoft.com/windows/deployment/volume-activation/volume-activation-windows-10)
|
||||
<br>[Plan for volume activation](https://docs.microsoft.com/windows/deployment/volume-activation/plan-for-volume-activation-client)
|
||||
<br>[VLSC downloads FAQ](https://www.microsoft.com/Licensing/servicecenter/Help/FAQDetails.aspx?id=150)
|
||||
<br>[Download and burn an ISO file on the volume licensing site (VLSC)](https://support.microsoft.com/help/2472143/download-and-burn-an-iso-file-on-the-volume-licensing-site-vlsc)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
title: Windows 10 volume license media
|
||||
description: Learn about volume license media in Windows 10, and channels such as the Volume License Service Center (VLSC).
|
||||
keywords: deploy, upgrade, update, software, media
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 10/20/2017
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Windows 10 volume license media
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
With each release of Windows 10, volume license media is made available on the [Volume Licensing Service Center](https://www.microsoft.com/vlsc) (VLSC) and other relevant channels such as Windows Update for Business, Windows Server Update Services (WSUS), and Visual Studio Subscriptions. This topic provides a description of volume license media, and describes some of the changes that have been implemented with the current release of Windows 10.
|
||||
|
||||
## Windows 10 media
|
||||
|
||||
To download Windows 10 installation media from the VLSC, use the product search filter to find “Windows 10.” A list of products will be displayed. The page then allows you to use your search results to download products, view keys, and view product and key descriptions.
|
||||
|
||||
When you select a product, for example “Windows 10 Enterprise” or “Windows 10 Education”, you can then choose the specific release by clicking **Download** and choosing the **Download Method**, **Language**, and **Operating system Type** (bitness).
|
||||
|
||||
> [!NOTE]
|
||||
> If you do not see a Windows 10 release available in the list of downloads, verify the [release date](https://technet.microsoft.com/windows/release-info.aspx).
|
||||
|
||||
In Windows 10, version 1709 the packaging of volume licensing media and upgrade packages is different than it has been for previous releases. Instead of having separate media and packages for Windows 10 Pro (volume licensing version), Windows 10 Enterprise, and Windows 10 Education, all three are bundled together. The following section explains this change.
|
||||
|
||||
### Windows 10, version 1709
|
||||
|
||||
Windows 10, version 1709 is available starting on 10/17/2017 in all relevant distribution channels. Note: An updated [Windows ADK for Windows 10](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit) is also available.
|
||||
|
||||
For ISOs that you download from the VLSC or Visual Studio Subscriptions, you can still search for the individual Windows editions. However, each of these editions (Windows 10 Pro, Windows 10 Enterprise, and Windows 10 Education) will point to the same ISO file, so you only need to download the ISO once. A single Windows image (WIM) file is included in the ISO that contains all the volume licensing images:
|
||||
|
||||
|
||||
|
||||
When using the contents of these ISOs with tools such as the Microsoft Deployment Toolkit or System Center Configuration Manager, make sure you select the appropriate image index in any task sequences that you create or update.
|
||||
|
||||
For packages published to Windows Server Update Services (WSUS), you’ll also notice the change because, instead of having separate packages for each Windows edition, there will be just one package:
|
||||
|
||||
<br>
|
||||
|
||||
| Title | Classification | Description |
|
||||
| --- | --- | --- |
|
||||
| Feature update to Windows 10, version 1709, \<language\> | Upgrades | Package to upgrade Windows 10 Pro (VL), Windows 10 Enterprise, or Windows 10 Education to version 1709 |
|
||||
| Windows 7 and 8.1 upgrade to Windows 10, version 1709, \<language\> | Upgrades | Package to upgrade Windows 7 Professional (VL), Windows 7 Enterprise, Windows 8.1 Professional (VL), or Windows 8.1 Enterprise to Windows 10 1709 |
|
||||
|
||||
<br>
|
||||
|
||||
When you approve one of these packages, it applies to all of the editions.
|
||||
|
||||
This Semi-Annual Channel release of Windows 10 continues the Windows as a service methodology. For more information about implementing Windows as a service in your organization in order to stay up to date with Windows, see [Update Windows 10 in the enterprise](https://aka.ms/waas).
|
||||
|
||||
|
||||
### Language packs
|
||||
|
||||
- **Windows 10 versions 1507 and 1511**: you can select **Windows 10 Enterprise Language Pack**, click **Download** and then select **English** and **64-bit** to see these downloads.
|
||||
- **Windows 10 1607 and later**: you must select **Multilanguage** from the drop-down list of languages.
|
||||
|
||||
See the following example for Windows 10, version 1709:
|
||||
|
||||
|
||||
|
||||
### Features on demand
|
||||
|
||||
[Features on demand](https://blogs.technet.microsoft.com/mniehaus/2015/08/31/adding-features-including-net-3-5-to-windows-10/) can be downloaded by searching for "**Windows 10 Enterprise Features on Demand**" and then following the same download process that is described above.
|
||||
|
||||
Features on demand is a method for adding features to your Windows 10 image that aren’t included in the base operating system image.
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
[Microsoft Volume Licensing Service Center (VLSC) User Guide](https://www.microsoft.com/download/details.aspx?id=10585)
|
||||
<br>[Volume Activation for Windows 10](https://docs.microsoft.com/windows/deployment/volume-activation/volume-activation-windows-10)
|
||||
<br>[Plan for volume activation](https://docs.microsoft.com/windows/deployment/volume-activation/plan-for-volume-activation-client)
|
||||
<br>[VLSC downloads FAQ](https://www.microsoft.com/Licensing/servicecenter/Help/FAQDetails.aspx?id=150)
|
||||
<br>[Download and burn an ISO file on the volume licensing site (VLSC)](https://support.microsoft.com/help/2472143/download-and-burn-an-iso-file-on-the-volume-licensing-site-vlsc)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -63,6 +63,9 @@ Note that the hardware hash also contains details about when it was generated, s
|
||||
|
||||
Starting with System Center Configuration Manager current branch version 1802, the hardware hashes for existing Windows 10 version 1703 and higher devices are automatically collected by Configuration Manager. See the [What’s new in version 1802](https://docs.microsoft.com/sccm/core/plan-design/changes/whats-new-in-version-1802#report-on-windows-autopilot-device-information) documentation for more details. The hash information can be extracted from Configuration Manager into a CSV file.
|
||||
|
||||
> [!Note]
|
||||
> Before uploading the CSV file on Intune, please make sure that the first row contains the device serial number, Windows product ID, hardware hash, group tag, and assigned user. If there is header information on the top of CSV file, please delete that header information. See details at [Enroll Windows devices in Intune](https://docs.microsoft.com/intune/enrollment/enrollment-autopilot).
|
||||
|
||||
### Collecting the hardware ID from existing devices using PowerShell
|
||||
|
||||
The hardware ID, or hardware hash, for an existing device is available through Windows Management Instrumentation (WMI), as long as that device is running Windows 10 version 1703 or later. To help gather this information, as well as the serial number of the device (useful to see at a glance the machine to which it belongs), a PowerShell script called [Get-WindowsAutoPilotInfo.ps1 has been published to the PowerShell Gallery website](https://www.powershellgallery.com/packages/Get-WindowsAutoPilotInfo).
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Windows Autopilot device guidelines
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: Windows Autopilot deployment
|
||||
description: Learn all about hardware, firmware, and software best practices for Windows Autopilot deployment.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -39,6 +39,7 @@ A [glossary](#glossary) of abbreviations used in this article is provided at the
|
||||
| Must I become a CSP to participate in Windows Autopilot? | Top volume OEMs do not, as they can use the OEM Direct API. All others who choose to use MPC to register devices must become CSPs in order to access MPC. |
|
||||
| Do the different CSP levels have all the same capabilities when it comes to Windows Autopilot? | For purposes of Windows Autopilot, there are three different types of CSPs, each with different levels of authority and access: <br><br>1. <b>Direct CSP</b>: Gets direct authorization from the customer to register devices. <br><br>2. <b>Indirect CSP Provider</b>: Gets implicit permission to register devices through the relationship their CSP Reseller partner has with the customer. Indirect CSP Providers register devices through Microsoft Partner Center. <br><br>3. <b>Indirect CSP Reseller</b>: Gets direct authorization from the customer to register devices. At the same time, their indirect CSP Provider partner also gets authorization, which means that either the Indirect Provider or the Indirect Reseller can register devices for the customer. However, the Indirect CSP Reseller must register devices through the MPC UI (manually uploading CSV file), whereas the Indirect CSP Provider has the option to register devices using the MPC APIs. |
|
||||
|
||||
|
||||
## Manufacturing
|
||||
|
||||
| Question | Answer |
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows Autopilot support
|
||||
description: Support information for Windows Autopilot
|
||||
description: Find out who to contact for help with your Windows Autopilot installation.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user