mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 13:57:22 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into live
# Conflicts: # windows/docfx.json
This commit is contained in:
LizRoss
commit
64d05614fb
@ -1,6 +1,6 @@
|
||||
---
|
||||
Description: Overview information about Microsoft Edge, the default browser for Windows 10. This topic includes links to other Microsoft Edge topics.
|
||||
ms.assetid: 70377735-B2F9-4B0B-9658-4CF7C1D745BB
|
||||
description: Overview information about Microsoft Edge, the default browser for Windows 10. This topic includes links to other Microsoft Edge topics.
|
||||
ms.assetid: 70377735-b2f9-4b0b-9658-4cf7c1d745bb
|
||||
author: eross-msft
|
||||
ms.prod: edge
|
||||
ms.mktglfcycl: general
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
Description: Microsoft Edge works with Group Policy and Microsoft Intune to help you manage your organization's computer settings.
|
||||
ms.assetid: 2E849894-255D-4F68-AE88-C2E4E31FA165
|
||||
description: Microsoft Edge works with Group Policy and Microsoft Intune to help you manage your organization's computer settings.
|
||||
ms.assetid: 2e849894-255d-4f68-ae88-c2e4e31fa165
|
||||
author: eross-msft
|
||||
ms.prod: edge
|
||||
ms.mktglfcycl: explore
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
Description: If you're having problems with Microsoft Edge, this topic tells how to use the Enterprise Mode site list to automatically open sites using IE11.
|
||||
ms.assetid: 89C75F7E-35CA-4CA8-96FA-B3B498B53BE4
|
||||
description: If you're having problems with Microsoft Edge, this topic tells how to use the Enterprise Mode site list to automatically open sites using IE11.
|
||||
ms.assetid: 89c75f7e-35ca-4ca8-96fa-b3b498b53bE4
|
||||
author: eross-msft
|
||||
ms.prod: edge
|
||||
ms.mktglfcycl: support
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
Description: Microsoft Edge is pre-installed on all Windows 10-capable devices that meet the minimum system requirements and are on the supported language list.
|
||||
ms.assetid: 3C5BC4C4-1060-499E-9905-2504EA6DC6AA
|
||||
description: Microsoft Edge is pre-installed on all Windows 10-capable devices that meet the minimum system requirements and are on the supported language list.
|
||||
ms.assetid: 3c5bc4c4-1060-499e-9905-2504ea6dc6aa
|
||||
author: eross-msft
|
||||
ms.prod: edge
|
||||
ms.mktglfcycl: support
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: How to use Group Policy to install ActiveX controls.
|
||||
description: How to use Group Policy to install ActiveX controls.
|
||||
ms.assetid: 59185370-558c-47e0-930c-8a5ed657e9e3
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
Description: You can add multiple sites to your Enterprise Mode site list by creating a custom text (TXT) or Extensible Markup Language (XML) file of problematic sites and then adding it in the Bulk add from file area of the Enterprise Mode Site List Manager tool.
|
||||
ms.assetid: 20AF07C4-051A-451F-9C46-5A052D9AE27C
|
||||
description: You can add multiple sites to your Enterprise Mode site list by creating a custom text (TXT) or Extensible Markup Language (XML) file of problematic sites and then adding it in the Bulk add from file area of the Enterprise Mode Site List Manager tool.
|
||||
ms.assetid: 20aF07c4-051a-451f-9c46-5a052d9Ae27c
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Add multiple sites to your Enterprise Mode site list using a file and the Windows 10 Enterprise Mode Site List Manager tool.
|
||||
description: Add multiple sites to your Enterprise Mode site list using a file and the Windows 10 Enterprise Mode Site List Manager tool.
|
||||
ms.assetid: da659ff5-70d5-4852-995e-4df67c4871dd
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
Description: Enterprise Mode is a compatibility mode that runs on Internet Explorer 11, letting websites render using a modified browser configuration that''s designed to emulate either Windows Internet Explorer 7 or Windows Internet Explorer 8, avoiding the common compatibility problems associated with web apps written and tested on older versions of Internet Explorer.
|
||||
ms.assetid: 042E44E8-568D-4717-8FD3-69DD198BBF26
|
||||
description: Enterprise Mode is a compatibility mode that runs on Internet Explorer 11, letting websites render using a modified browser configuration that's designed to emulate either Windows Internet Explorer 7 or Windows Internet Explorer 8, avoiding the common compatibility problems associated with web apps written and tested on older versions of Internet Explorer.
|
||||
ms.assetid: 042e44e8-568d-4717-8fd3-69dd198bbf26
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Enterprise Mode is a compatibility mode that runs on Internet Explorer 11, letting websites render using a modified browser configuration that''s designed to emulate either Windows Internet Explorer 8 or Windows Internet Explorer 7, avoiding the common compatibility problems associated with web apps written and tested on older versions of Internet Explorer.
|
||||
description: Enterprise Mode is a compatibility mode that runs on Internet Explorer 11, letting websites render using a modified browser configuration that''s designed to emulate either Windows Internet Explorer 8 or Windows Internet Explorer 7, avoiding the common compatibility problems associated with web apps written and tested on older versions of Internet Explorer.
|
||||
ms.assetid: 513e8f3b-fedf-4d57-8d81-1ea4fdf1ac0b
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Administrative templates and Internet Explorer 11
|
||||
description: Administrative templates and Internet Explorer 11
|
||||
ms.assetid: 2b390786-f786-41cc-bddc-c55c8a4c5af3
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Auto configuration and auto proxy problems with Internet Explorer 11
|
||||
description: Auto configuration and auto proxy problems with Internet Explorer 11
|
||||
ms.assetid: 3fbbc2c8-859b-4b2e-abc3-de2c299e0938
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Auto configuration settings for Internet Explorer 11
|
||||
description: Auto configuration settings for Internet Explorer 11
|
||||
ms.assetid: 90308d59-45b9-4639-ab1b-497e5ba19023
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Auto detect settings Internet Explorer 11
|
||||
description: Auto detect settings Internet Explorer 11
|
||||
ms.assetid: c6753cf4-3276-43c5-aae9-200e9e82753f
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Auto proxy configuration settings for Internet Explorer 11
|
||||
description: Auto proxy configuration settings for Internet Explorer 11
|
||||
ms.assetid: 5120aaf9-8ead-438a-8472-3cdd924b7d9e
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Browser cache changes and roaming profiles
|
||||
description: Browser cache changes and roaming profiles
|
||||
ms.assetid: 85f0cd01-6f82-4bd1-9c0b-285af1ce3436
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: You can have centralized control over Enterprise Mode by creating a single, global XML site list that includes the list of websites to render using Enterprise Mode.
|
||||
description: You can have centralized control over Enterprise Mode by creating a single, global XML site list that includes the list of websites to render using Enterprise Mode.
|
||||
ms.assetid: 2bbc7017-622e-4baa-8981-c0bbda10e9df
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Choose how to deploy Internet Explorer 11 (IE11)
|
||||
description: Choose how to deploy Internet Explorer 11 (IE11)
|
||||
ms.assetid: 21b6a301-c222-40bc-ad0b-27f66fc54d9d
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Choose how to install Internet Explorer 11 (IE11)
|
||||
description: Choose how to install Internet Explorer 11 (IE11)
|
||||
ms.assetid: 9572f5f1-5d67-483e-bd63-ffea95053481
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Create packages for multiple operating systems or languages
|
||||
description: Create packages for multiple operating systems or languages
|
||||
ms.assetid: 44051f9d-63a7-43bf-a427-d0a0a1c717da
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Customize Internet Explorer 11 installation packages
|
||||
description: Customize Internet Explorer 11 installation packages
|
||||
ms.assetid: 10a14a09-673b-4f8b-8d12-64036135e7fd
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Delete a single site from your global Enterprise Mode site list.
|
||||
description: Delete a single site from your global Enterprise Mode site list.
|
||||
title: Delete sites from your Enterprise Mode site list in the Enterprise Mode Site List Manager (Internet Explorer 11 for IT Pros)
|
||||
ms.assetid: 41413459-b57f-48da-aedb-4cbec1e2981a
|
||||
author: eross-msft
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: You can deploy Internet Explorer 11 to your users' computers by using your custom browser packages and Automatic Version Synchronization (AVS).
|
||||
description: You can deploy Internet Explorer 11 to your users' computers by using your custom browser packages and Automatic Version Synchronization (AVS).
|
||||
ms.assetid: f51224bd-3371-4551-821d-1d62310e3384
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Deploy Internet Explorer 11 using software distribution tools
|
||||
description: Deploy Internet Explorer 11 using software distribution tools
|
||||
ms.assetid: fd027775-651a-41e1-8ec3-d32eca876d8a
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: You can pin websites to the Windows 8.1 taskbar for quick access using the Microsoft Deployment Toolkit (MDT) 2013.
|
||||
description: You can pin websites to the Windows 8.1 taskbar for quick access using the Microsoft Deployment Toolkit (MDT) 2013.
|
||||
ms.assetid: 24f4dcac-9032-4fe8-bf6d-2d712d61cb0c
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Windows Internet Explorer 8 introduced document modes as a way to move from the proprietary coding of web features to a more standardized type of coding that could run on multiple browsers and devices.
|
||||
description: Windows Internet Explorer 8 introduced document modes as a way to move from the proprietary coding of web features to a more standardized type of coding that could run on multiple browsers and devices.
|
||||
ms.assetid: 00cb1f39-2b20-4d37-9436-62dc03a6320b
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: You can use Internet Explorer 11 and the Enterprise Mode Site List Manager tool to change whether page rendering should use Enterprise Mode or the default Internet Explorer browser configuration. You can also add, remove, or delete associated comments.
|
||||
description: You can use Internet Explorer 11 and the Enterprise Mode Site List Manager tool to change whether page rendering should use Enterprise Mode or the default Internet Explorer browser configuration. You can also add, remove, or delete associated comments.
|
||||
ms.assetid: 76aa9a85-6190-4c3a-bc25-0f914de228ea
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Enable and disable add-ons using administrative templates and group policy
|
||||
description: Enable and disable add-ons using administrative templates and group policy
|
||||
ms.assetid: c6fe1cd3-0bfc-4d23-8016-c9601f674c0b
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Enhanced Protected Mode problems with Internet Explorer
|
||||
description: Enhanced Protected Mode problems with Internet Explorer
|
||||
ms.assetid: 15890ad1-733d-4f7e-a318-10399b389f45
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Use the topics in this section to learn how to set up and use Enterprise Mode and the Enterprise Mode Site List Manager tool in your company.
|
||||
description: Use the topics in this section to learn how to set up and use Enterprise Mode and the Enterprise Mode Site List Manager tool in your company.
|
||||
ms.assetid: d52ba8ba-b3c7-4314-ba14-0610e1d8456e
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
Description: Use the Enterprise Mode Site List Manager tool to create and update your Enterprise Mode site list for devices running Windows 7 or Windows 8.1 Update.
|
||||
ms.assetid: 17C61547-82E3-48F2-908D-137A71938823
|
||||
description: Use the Enterprise Mode Site List Manager tool to create and update your Enterprise Mode site list for devices running Windows 7 or Windows 8.1 Update.
|
||||
ms.assetid: 17c61547-82e3-48f2-908d-137a71938823
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Use the Enterprise Mode Site List Manager tool to create and update your Enterprise Mode site list for devices running Windows 10.
|
||||
description: Use the Enterprise Mode Site List Manager tool to create and update your Enterprise Mode site list for devices running Windows 10.
|
||||
ms.assetid: 909ca359-5654-4df9-b9fb-921232fc05f5
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: After you create your Enterprise Mode site list in the Enterprise Mode Site List Manager, you can export the contents to an Enterprise Mode (.EMIE) file.
|
||||
description: After you create your Enterprise Mode site list in the Enterprise Mode Site List Manager, you can export the contents to an Enterprise Mode (.EMIE) file.
|
||||
ms.assetid: 9ee7c13d-6fca-4446-bc22-d23a0213a95d
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: The Internet Explorer 11 Enterprise Mode site list lets you specify document modes for specific websites, helping you fix compatibility issues without changing a single line of code on the site.
|
||||
description: The Internet Explorer 11 Enterprise Mode site list lets you specify document modes for specific websites, helping you fix compatibility issues without changing a single line of code on the site.
|
||||
ms.assetid: 4b21bb27-aeac-407f-ae58-ab4c6db2baf6
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: When you add multiple sites to your Enterprise Mode site list entries, they’re validated by the Enterprise Mode Site List Manager before they’re entered into your global list.
|
||||
description: When you add multiple sites to your Enterprise Mode site list entries, they’re validated by the Enterprise Mode Site List Manager before they’re entered into your global list.
|
||||
ms.assetid: 9f80e39f-dcf1-4124-8931-131357f31d67
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Overview about Group Policy, Advanced Group Policy Management (AGPM), and Internet Explorer 11
|
||||
description: Overview about Group Policy, Advanced Group Policy Management (AGPM), and Internet Explorer 11
|
||||
ms.assetid: 63a7ef4a-6de2-4d08-aaba-0479131e3406
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Overview about Group Policy, the Group Policy Management Console (GPMC), and Internet Explorer 11
|
||||
description: Overview about Group Policy, the Group Policy Management Console (GPMC), and Internet Explorer 11
|
||||
ms.assetid: ae3d227d-3da7-46b8-8a61-c71bfeae0c63
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Use the topics in this section to learn about Group Policy and how to use it to manage Internet Explorer.
|
||||
description: Use the topics in this section to learn about Group Policy and how to use it to manage Internet Explorer.
|
||||
ms.assetid: 50383d3f-9ac9-4a30-8852-354b6eb9434a
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Group Policy, the Local Group Policy Editor, and Internet Explorer 11
|
||||
description: Group Policy, the Local Group Policy Editor, and Internet Explorer 11
|
||||
ms.assetid: 6fc30e91-efac-4ba5-9ee2-fa77dcd36467
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Group Policy suggestions for compatibility with Internet Explorer 11
|
||||
description: Group Policy suggestions for compatibility with Internet Explorer 11
|
||||
ms.assetid: 7482c99f-5d79-4344-9e1c-aea9f0a68e18
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Overview of the available Group Policy management tools
|
||||
description: Overview of the available Group Policy management tools
|
||||
ms.assetid: e33bbfeb-6b80-4e71-8bba-1d0369a87312
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Info about Group Policy preferences versus Group Policy settings
|
||||
description: Info about Group Policy preferences versus Group Policy settings
|
||||
ms.assetid: f2264c97-7f09-4f28-bb5c-58ab80dcc6ee
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Links to troubleshooting topics and log files that can help address Group Policy problems with Internet Explorer 11.
|
||||
description: Links to troubleshooting topics and log files that can help address Group Policy problems with Internet Explorer 11.
|
||||
ms.assetid: 0da0d9a9-200c-46c4-96be-630e82de017b
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Instructions about how to create and configure shortcut preference extensions to file system objects, URLs, and shell objects.
|
||||
description: Instructions about how to create and configure shortcut preference extensions to file system objects, URLs, and shell objects.
|
||||
ms.assetid: c6fbf990-13e4-4be7-9f08-5bdd43179b3b
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Overview about how Group Policy works with Windows Powershell and Internet Explorer 11
|
||||
description: Overview about how Group Policy works with Windows Powershell and Internet Explorer 11
|
||||
ms.assetid: e3607cde-a498-4e04-9daa-b331412967fc
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: If you need to replace your entire site list because of errors, or simply because it’s out of date, you can import your exported Enterprise Mode site list using the Enterprise Mode Site List Manager.
|
||||
description: If you need to replace your entire site list because of errors, or simply because it’s out of date, you can import your exported Enterprise Mode site list using the Enterprise Mode Site List Manager.
|
||||
ms.assetid: cacd5d68-700b-4a96-b4c9-ca2c40c1ac5f
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Use the topics in this section to learn how to customize your Internet Explorer installation package, how to choose the right method for installation, and how to deploy IE into your environment.
|
||||
description: Use the topics in this section to learn how to customize your Internet Explorer installation package, how to choose the right method for installation, and how to deploy IE into your environment.
|
||||
ms.assetid: caca18c1-d5c4-4404-84f8-d02bc562915f
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: How to add and deploy the Internet Explorer 11 update using Microsoft Intune.
|
||||
description: How to add and deploy the Internet Explorer 11 update using Microsoft Intune.
|
||||
ms.assetid: b2dfc08c-78af-4c22-8867-7be3b92b1616
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: How to install the Internet Explorer 11 update using Microsoft Deployment Toolkit (MDT) and your Windows images.
|
||||
description: How to install the Internet Explorer 11 update using Microsoft Deployment Toolkit (MDT) and your Windows images.
|
||||
ms.assetid: e16f9144-170c-4964-a62d-0d1a16f4cd1f
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: How to install the Internet Explorer 11 update using System Center 2012 R2 Configuration Manager
|
||||
description: How to install the Internet Explorer 11 update using System Center 2012 R2 Configuration Manager
|
||||
ms.assetid: 9ede9722-29b3-4cb7-956d-ffa91e7bedbd
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: How to install the Internet Explorer 11 update using your network
|
||||
description: How to install the Internet Explorer 11 update using your network
|
||||
ms.assetid: 85f6429d-947a-4031-8f93-e26110a35828
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: How to install the Internet Explorer 11 update using third-party tools and command-line options.
|
||||
description: How to install the Internet Explorer 11 update using third-party tools and command-line options.
|
||||
ms.assetid: 30190c66-49f7-4ca4-8b57-a47656aa0c7e
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: How to install the Internet Explorer 11 update using Windows Server Update Services (WSUS)'
|
||||
description: How to install the Internet Explorer 11 update using Windows Server Update Services (WSUS)'
|
||||
ms.assetid: 6cbd6797-c670-4236-8423-e0919478f2ce
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: How to fix intranet search problems with Internet Explorer 11
|
||||
description: How to fix intranet search problems with Internet Explorer 11
|
||||
ms.assetid: 3ee71d93-d9d2-48e1-899e-07932c73faa6
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Use the topics in this section to learn about how to auto detect your settings, auto configure your configuration settings, and auto configure your proxy configuration settings for Internet Explorer.
|
||||
description: Use the topics in this section to learn about how to auto detect your settings, auto configure your configuration settings, and auto configure your proxy configuration settings for Internet Explorer.
|
||||
ms.assetid: eb3cce62-fc7b-41e3-97b6-2916b85bcf55
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: IEM-configured settings have been deprecated for Internet Explorer 10 and newer. Use this topic to learn where to go to fix the affected settings through Group Policy Preferences, Administrative Templates (.admx), or the IEAK.
|
||||
description: IEM-configured settings have been deprecated for Internet Explorer 10 and newer. Use this topic to learn where to go to fix the affected settings through Group Policy Preferences, Administrative Templates (.admx), or the IEAK.
|
||||
ms.assetid: 89084e01-4e3f-46a6-b90e-48ee58d6821c
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Internet Explorer 11 uses the latest standards mode, which simplifies web page compatibility for users by removing the **Compatibility View** button and reducing the number of compatibility options in the F12 developer tools for developers.
|
||||
description: Internet Explorer 11 uses the latest standards mode, which simplifies web page compatibility for users by removing the **Compatibility View** button and reducing the number of compatibility options in the F12 developer tools for developers.
|
||||
ms.assetid: 501c96c9-9f03-4913-9f4b-f67bd9edbb61
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: How to turn managed browser hosting controls back on in Internet Explorer 11.
|
||||
description: How to turn managed browser hosting controls back on in Internet Explorer 11.
|
||||
ms.assetid: b0b7f60f-9099-45ab-84f4-4ac64d7bcb43
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: New group policy settings for Internet Explorer 11
|
||||
description: New group policy settings for Internet Explorer 11
|
||||
ms.assetid: 669cc1a6-e2cb-403f-aa31-c1de52a615d1
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Use out-of-date ActiveX control blocking to help you know when IE prevents a webpage from loading outdated ActiveX controls and to update the outdated control, so that it’s safer to use.
|
||||
description: Use out-of-date ActiveX control blocking to help you know when IE prevents a webpage from loading outdated ActiveX controls and to update the outdated control, so that it’s safer to use.
|
||||
ms.assetid: e61866bb-1ff1-4a8d-96f2-61d3534e8199
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Possible solutions to the problems you might encounter after installing IE11, such as crashing or seeming slow, getting into an unusable state, or problems with adaptive streaming and DRM playback.
|
||||
description: Possible solutions to the problems you might encounter after installing IE11, such as crashing or seeming slow, getting into an unusable state, or problems with adaptive streaming and DRM playback.
|
||||
ms.assetid: c4b75ad3-9c4a-4dd2-9fed-69f776f542e6
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Instructions about how to clear all of the sites from your global Enterprise Mode site list.
|
||||
description: Instructions about how to clear all of the sites from your global Enterprise Mode site list.
|
||||
ms.assetid: 90f38a6c-e0e2-4c93-9a9e-c425eca99e97
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
Description: Instructions about how to remove sites from a local compatibility view list.
|
||||
ms.assetid: F6ECAA75-EBCB-4F8D-8721-4CD6E73C0AC9
|
||||
description: Instructions about how to remove sites from a local compatibility view list.
|
||||
ms.assetid: f6ecaa75-ebcb-4f8d-8721-4cd6e73c0ac9
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
Description: Instructions about how to remove sites from a local Enterprise Mode site list.
|
||||
ms.assetid: C7D6DD0B-E264-42BB-8C9D-AC2F837018D2
|
||||
description: Instructions about how to remove sites from a local Enterprise Mode site list.
|
||||
ms.assetid: c7d6dd0b-e264-42bb-8c9d-ac2f837018d2
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: You can save your current Enterprise Mode compatibility site list as an XML file, for distribution and use by your managed systems.
|
||||
description: You can save your current Enterprise Mode compatibility site list as an XML file, for distribution and use by your managed systems.
|
||||
ms.assetid: 254a986b-494f-4316-92c1-b089ee8b3e0a
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Search to see if a specific site already appears in your global Enterprise Mode site list.
|
||||
description: Search to see if a specific site already appears in your global Enterprise Mode site list.
|
||||
ms.assetid: e399aeaf-6c3b-4cad-93c9-813df6ad47f9
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
Description: Use the Group Policy setting, Set a default associations configuration file, to set the default browser for your company devices running Windows 10.
|
||||
ms.assetid: F486C9DB-0DC9-4CD6-8A0B-8CB872B1D361
|
||||
description: Use the Group Policy setting, Set a default associations configuration file, to set the default browser for your company devices running Windows 10.
|
||||
ms.assetid: f486c9db-0dc9-4cd6-8a0b-8cb872b1d361
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Set up and turn on Enterprise Mode logging and data collection in your organization.
|
||||
description: Set up and turn on Enterprise Mode logging and data collection in your organization.
|
||||
ms.assetid: 2e98a280-f677-422f-ba2e-f670362afcde
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Reviewing log files to learn more about potential setup problems with Internet Explorer 11.
|
||||
description: Reviewing log files to learn more about potential setup problems with Internet Explorer 11.
|
||||
ms.assetid: 2cd79988-17d1-4317-bee9-b3ae2dd110a0
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Lists the minimum system requirements and supported languages for Internet Explorer 11.
|
||||
description: Lists the minimum system requirements and supported languages for Internet Explorer 11.
|
||||
ms.assetid: 27185e3d-c486-4e4a-9c51-5cb317c0006d
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Use the topics in this section to learn how to troubleshoot several of the more common problems experienced with Internet Explorer.
|
||||
description: Use the topics in this section to learn how to troubleshoot several of the more common problems experienced with Internet Explorer.
|
||||
ms.assetid: 0361c1a6-3faa-42b2-a588-92439eebeeab
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: How to turn Enteprrise Mode off temporarily while testing websites and how to turn it off completely if you no longer want to to use it.
|
||||
description: How to turn Enteprrise Mode off temporarily while testing websites and how to turn it off completely if you no longer want to to use it.
|
||||
ms.assetid: 5027c163-71e0-49b8-9dc0-f0a7310c7ae3
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Turn off natural metrics for Internet Explorer 11
|
||||
description: Turn off natural metrics for Internet Explorer 11
|
||||
ms.assetid: e31a27d7-662e-4106-a3d2-c6b0531961d5
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: How to turn on Enterprise Mode and specify a site list.
|
||||
description: How to turn on Enterprise Mode and specify a site list.
|
||||
ms.assetid: 800e9c5a-57a6-4d61-a38a-4cb972d833e1
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Turn on local user control and logging for Enterprise Mode.
|
||||
description: Turn on local user control and logging for Enterprise Mode.
|
||||
ms.assetid: 6622ecce-24b1-497e-894a-e1fd5a8a66d1
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: High-level info about some of the new and updated features for Internet Explorer 11.
|
||||
description: High-level info about some of the new and updated features for Internet Explorer 11.
|
||||
ms.assetid: f53c6f04-7c60-40e7-9fc5-312220f08156
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Use the topics in this section to learn about how to use the Enterprise Mode Site List Manager tool.
|
||||
description: Use the topics in this section to learn about how to use the Enterprise Mode Site List Manager tool.
|
||||
ms.assetid: f4dbed4c-08ff-40b1-ab3f-60d3b6e8ec9b
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Info about where features went in the IEAK11, where the Favorites, Command, and Status bars went, and where the search bar went.
|
||||
description: Info about where features went in the IEAK11, where the Favorites, Command, and Status bars went, and where the search bar went.
|
||||
ms.assetid: 7324faff-ccb6-4e14-ad91-af12dbca575e
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
Description: Use this section to learn about how to turn on and use IE7 Enterprise Mode or IE8 Enterprise Mode.
|
||||
ms.assetid: 238EAD3D-8920-429A-AC23-02F089C4384A
|
||||
description: Use this section to learn about how to turn on and use IE7 Enterprise Mode or IE8 Enterprise Mode.
|
||||
ms.assetid: 238ead3d-8920-429a-ac23-02f089c4384a
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: How to use IEAK 11 while planning, customizing, and building the custom installation package.
|
||||
description: How to use IEAK 11 while planning, customizing, and building the custom installation package.
|
||||
ms.assetid: af93742f-f955-44ab-bfa2-7bf0c99045d3
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: How to use Setup Information (.inf) files to create installation packages.
|
||||
description: How to use Setup Information (.inf) files to create installation packages.
|
||||
ms.assetid: 04fa2ba8-8d84-4af6-ab99-77e4f1961b0e
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Virtualization and compatibility with Internet Explorer 11
|
||||
description: Virtualization and compatibility with Internet Explorer 11
|
||||
ms.assetid: b0388c04-2584-4b6d-a7a8-4e0476773a80
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Info about the features included in Enterprise Mode with Internet Explorer 11.
|
||||
description: Info about the features included in Enterprise Mode with Internet Explorer 11.
|
||||
ms.assetid: 3c77e9f3-eb21-46d9-b5aa-f9b2341cfefa
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: How to download and use the Internet Explorer 11 Blocker Toolkit to turn off the automatic delivery of IE11 through the Automatic Updates feature of Windows Update.
|
||||
description: How to download and use the Internet Explorer 11 Blocker Toolkit to turn off the automatic delivery of IE11 through the Automatic Updates feature of Windows Update.
|
||||
ms.assetid: fafeaaee-171c-4450-99f7-5cc7f8d7ba91
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
Description: Frequently asked questions about Internet Explorer 11 for IT Pros
|
||||
description: Frequently asked questions about Internet Explorer 11 for IT Pros
|
||||
ms.assetid: 140e7d33-584a-44da-8c68-6c1d568e1de3
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
description: The landing page for IE11 that lets you access the documentation.
|
||||
assetid: BE3DC32E-80D9-4D9F-A802-C7DB6C50DBE0
|
||||
assetid: be3dc32e-80d9-4d9f-a802-c7db6c50dbe0
|
||||
author: eross-msft
|
||||
ms.prod: IE11
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
1
mdop/TOC.md
Normal file
1
mdop/TOC.md
Normal file
@ -0,0 +1 @@
|
||||
#[MDOP Placeholder](index.md)
|
||||
24
mdop/docfx.json
Normal file
24
mdop/docfx.json
Normal file
@ -0,0 +1,24 @@
|
||||
{
|
||||
"build": {
|
||||
"content":
|
||||
[
|
||||
{
|
||||
"files": ["**/**.md"],
|
||||
"exclude": ["**/obj/**"]
|
||||
}
|
||||
],
|
||||
"resource": [
|
||||
{
|
||||
"files": ["**/images/**", "**/*.json"],
|
||||
"exclude": ["**/obj/**"]
|
||||
}
|
||||
],
|
||||
"globalMetadata": {
|
||||
"ROBOTS": "INDEX, FOLLOW"
|
||||
},
|
||||
"externalReference": [
|
||||
],
|
||||
"template": "op.html",
|
||||
"dest": "mdop"
|
||||
}
|
||||
}
|
||||
1
mdop/index.md
Normal file
1
mdop/index.md
Normal file
@ -0,0 +1 @@
|
||||
#Placeholder for MDOP content
|
||||
6
windows/TOC.md
Normal file
6
windows/TOC.md
Normal file
@ -0,0 +1,6 @@
|
||||
# [Windows 10 and Windows 10 Mobile](index.md)
|
||||
## [What's new in Windows 10](whats-new/)
|
||||
## [Plan for Windows 10 deployment](plan/)
|
||||
## [Deploy Windows 10](deploy/)
|
||||
## [Keep Windows 10 secure](keep-secure/)
|
||||
## [Manage and update Windows 10](manage/)
|
||||
136
windows/deploy/TOC.md
Normal file
136
windows/deploy/TOC.md
Normal file
@ -0,0 +1,136 @@
|
||||
# [Deploy Windows 10](index.md)
|
||||
## [Change history for Deploy Windows 10](change-history-for-deploy-windows-10.md)
|
||||
## [Windows 10 deployment scenarios](windows-10-deployment-scenarios.md)
|
||||
## [Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md)
|
||||
### [Get started with the Microsoft Deployment Toolkit (MDT)](get-started-with-the-microsoft-deployment-toolkit.md)
|
||||
#### [Key features in MDT 2013 Update 2](key-features-in-mdt-2013.md)
|
||||
#### [MDT 2013 Update 2 Lite Touch components](mdt-2013-lite-touch-components.md)
|
||||
#### [Prepare for deployment with MDT 2013 Update 2](prepare-for-windows-deployment-with-mdt-2013.md)
|
||||
### [Create a Windows 10 reference image](create-a-windows-10-reference-image.md)
|
||||
### [Deploy a Windows 10 image using MDT 2013 Update 2](deploy-a-windows-10-image-using-mdt.md)
|
||||
### [Build a distributed environment for Windows 10 deployment](build-a-distributed-environment-for-windows-10-deployment.md)
|
||||
### [Refresh a Windows 7 computer with Windows 10](refresh-a-windows-7-computer-with-windows-10.md)
|
||||
### [Replace a Windows 7 computer with a Windows 10 computer](replace-a-windows-7-computer-with-a-windows-10-computer.md)
|
||||
### [Configure MDT settings](configure-mdt-2013-settings.md)
|
||||
#### [Set up MDT for BitLocker](set-up-mdt-2013-for-bitlocker.md)
|
||||
#### [Configure MDT deployment share rules](configure-mdt-deployment-share-rules.md)
|
||||
#### [Configure MDT for UserExit scripts](configure-mdt-2013-for-userexit-scripts.md)
|
||||
#### [Simulate a Windows 10 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-2013.md)
|
||||
#### [Use web services in MDT](use-web-services-in-mdt-2013.md)
|
||||
#### [Use Orchestrator runbooks with MDT](use-orchestrator-runbooks-with-mdt-2013.md)
|
||||
## [Deploy Windows 10 with System Center 2012 R2 Configuration Manager](deploy-windows-10-with-system-center-2012-r2-configuration-manager.md)
|
||||
### [Integrate Configuration Manager with MDT 2013 Update 2](integrate-configuration-manager-with-mdt-2013.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](create-a-task-sequence-with-configuration-manager-and-mdt.md)
|
||||
### [Finalize the operating system configuration for Windows 10 deployment with Configuration Manager](finalize-the-os-configuration-for-windows-10-deployment-with-configuration-manager.md)
|
||||
### [Deploy Windows 10 using PXE and Configuration Manager](deploy-windows-10-using-pxe-and-configuration-manager.md)
|
||||
### [Monitor the Windows 10 deployment with Configuration Manager](monitor-windows-10-deployment-with-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)
|
||||
## [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md)
|
||||
## [Upgrade to Windows 10 with System Center Configuration Manager](upgrade-to-windows-10-with-system-center-configuraton-manager.md)
|
||||
## [Windows 10 edition upgrade](windows-10-edition-upgrades.md)
|
||||
## [Deploy Windows To Go in your organization](deploy-windows-to-go.md)
|
||||
## [Update Windows 10 images with provisioning packages](update-windows-10-images-with-provisioning-packages.md)
|
||||
## [Sideload apps in Windows 10](sideload-apps-in-windows-10.md)
|
||||
## [Volume Activation [client]](volume-activation-windows-10.md)
|
||||
### [Plan for volume activation [client]](plan-for-volume-activation-client.md)
|
||||
### [Activate using Key Management Service [client]](activate-using-key-management-service-vamt.md)
|
||||
### [Activate using Active Directory-based activation [client]](activate-using-active-directory-based-activation-client.md)
|
||||
### [Activate clients running Windows 10](activate-windows-10-clients-vamt.md)
|
||||
### [Monitor activation [client]](monitor-activation-client.md)
|
||||
### [Use the Volume Activation Management Tool [client]](use-the-volume-activation-management-tool-client.md)
|
||||
### [Appendix: Information sent to Microsoft during activation [client]](appendix-information-sent-to-microsoft-during-activation-client.md)
|
||||
## [Windows 10 deployment tools reference](windows-10-deployment-tools-reference.md)
|
||||
### [Windows 10 deployment tools](windows-deployment-scenarios-and-tools.md)
|
||||
### [Windows ADK for Windows 10 scenarios for IT Pros](windows-adk-scenarios-for-it-pros.md)
|
||||
### [Volume Activation Management Tool (VAMT) Technical Reference](volume-activation-management-tool.md)
|
||||
#### [Introduction to VAMT](introduction-vamt.md)
|
||||
#### [Active Directory-Based Activation Overview](active-directory-based-activation-overview.md)
|
||||
#### [Install and Configure VAMT](install-configure-vamt.md)
|
||||
##### [VAMT Requirements](vamt-requirements.md)
|
||||
##### [Install VAMT](install-vamt.md)
|
||||
##### [Configure Client Computers](configure-client-computers-vamt.md)
|
||||
#### [Add and Manage Products](add-manage-products-vamt.md)
|
||||
##### [Add and Remove Computers](add-remove-computers-vamt.md)
|
||||
##### [Update Product Status](update-product-status-vamt.md)
|
||||
##### [Remove Products](remove-products-vamt.md)
|
||||
#### [Manage Product Keys](manage-product-keys-vamt.md)
|
||||
##### [Add and Remove a Product Key](add-remove-product-key-vamt.md)
|
||||
##### [Install a Product Key](install-product-key-vamt.md)
|
||||
##### [Install a KMS Client Key](install-kms-client-key-vamt.md)
|
||||
#### [Manage Activations](manage-activations-vamt.md)
|
||||
##### [Perform Online Activation](online-activation-vamt.md)
|
||||
##### [Perform Proxy Activation](proxy-activation-vamt.md)
|
||||
##### [Perform KMS Activation](kms-activation-vamt.md)
|
||||
##### [Perform Local Reactivation](local-reactivation-vamt.md)
|
||||
##### [Activate an Active Directory Forest Online](activate-forest-vamt.md)
|
||||
##### [Activate by Proxy an Active Directory Forest](activate-forest-by-proxy-vamt.md)
|
||||
#### [Manage VAMT Data](manage-vamt-data.md)
|
||||
##### [Import and Export VAMT Data](import-export-vamt-data.md)
|
||||
##### [Use VAMT in Windows PowerShell](use-vamt-in-windows-powershell.md)
|
||||
#### [VAMT Step-by-Step Scenarios](vamt-step-by-step.md)
|
||||
##### [Scenario 1: Online Activation](scenario-online-activation-vamt.md)
|
||||
##### [Scenario 2: Proxy Activation](scenario-proxy-activation-vamt.md)
|
||||
##### [Scenario 3: KMS Client Activation](scenario-kms-activation-vamt.md)
|
||||
#### [VAMT Known Issues](vamt-known-issues.md)
|
||||
### [User State Migration Tool (USMT) Technical Reference](usmt-technical-reference.md)
|
||||
#### [User State Migration Tool (USMT) Overview Topics](usmt-topics.md)
|
||||
##### [User State Migration Tool (USMT) Overview](usmt-overview.md)
|
||||
##### [Getting Started with the User State Migration Tool (USMT)](getting-started-with-the-user-state-migration-tool.md)
|
||||
##### [Windows Upgrade and Migration Considerations](windows-upgrade-and-migration-considerations.md)
|
||||
#### [User State Migration Tool (USMT) How-to topics](usmt-how-to.md)
|
||||
##### [Exclude Files and Settings](usmt-exclude-files-and-settings.md)
|
||||
##### [Extract Files from a Compressed USMT Migration Store](usmt-extract-files-from-a-compressed-migration-store.md)
|
||||
##### [Include Files and Settings](usmt-include-files-and-settings.md)
|
||||
##### [Migrate Application Settings](migrate-application-settings.md)
|
||||
##### [Migrate EFS Files and Certificates](usmt-migrate-efs-files-and-certificates.md)
|
||||
##### [Migrate User Accounts](usmt-migrate-user-accounts.md)
|
||||
##### [Reroute Files and Settings](usmt-reroute-files-and-settings.md)
|
||||
##### [Verify the Condition of a Compressed Migration Store](verify-the-condition-of-a-compressed-migration-store.md)
|
||||
#### [User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md)
|
||||
##### [Common Issues](usmt-common-issues.md)
|
||||
##### [Frequently Asked Questions](usmt-faq.md)
|
||||
##### [Log Files](usmt-log-files.md)
|
||||
##### [Return Codes](usmt-return-codes.md)
|
||||
##### [USMT Resources](usmt-resources.md)
|
||||
#### [User State Migration Toolkit (USMT) Reference](usmt-reference.md)
|
||||
##### [USMT Requirements](usmt-requirements.md)
|
||||
##### [USMT Best Practices](usmt-best-practices.md)
|
||||
##### [How USMT Works](usmt-how-it-works.md)
|
||||
##### [Plan Your Migration](usmt-plan-your-migration.md)
|
||||
###### [Common Migration Scenarios](usmt-common-migration-scenarios.md)
|
||||
###### [What Does USMT Migrate?](usmt-what-does-usmt-migrate.md)
|
||||
###### [Choose a Migration Store Type](usmt-choose-migration-store-type.md)
|
||||
####### [Migration Store Types Overview](migration-store-types-overview.md)
|
||||
####### [Estimate Migration Store Size](usmt-estimate-migration-store-size.md)
|
||||
####### [Hard-Link Migration Store](usmt-hard-link-migration-store.md)
|
||||
####### [Migration Store Encryption](usmt-migration-store-encryption.md)
|
||||
###### [Determine What to Migrate](usmt-determine-what-to-migrate.md)
|
||||
####### [Identify Users](usmt-identify-users.md)
|
||||
####### [Identify Applications Settings](usmt-identify-application-settings.md)
|
||||
####### [Identify Operating System Settings](usmt-identify-operating-system-settings.md)
|
||||
####### [Identify File Types, Files, and Folders](usmt-identify-file-types-files-and-folders.md)
|
||||
###### [Test Your Migration](usmt-test-your-migration.md)
|
||||
##### [User State Migration Tool (USMT) Command-line Syntax](usmt-command-line-syntax.md)
|
||||
###### [ScanState Syntax](usmt-scanstate-syntax.md)
|
||||
###### [LoadState Syntax](usmt-loadstate-syntax.md)
|
||||
###### [UsmtUtils Syntax](usmt-utilities.md)
|
||||
##### [USMT XML Reference](usmt-xml-reference.md)
|
||||
###### [Understanding Migration XML Files](understanding-migration-xml-files.md)
|
||||
###### [Config.xml File](usmt-configxml-file.md)
|
||||
###### [Customize USMT XML Files](usmt-customize-xml-files.md)
|
||||
###### [Custom XML Examples](usmt-custom-xml-examples.md)
|
||||
###### [Conflicts and Precedence](usmt-conflicts-and-precedence.md)
|
||||
###### [General Conventions](usmt-general-conventions.md)
|
||||
###### [XML File Requirements](xml-file-requirements.md)
|
||||
###### [Recognized Environment Variables](usmt-recognized-environment-variables.md)
|
||||
###### [XML Elements Library](usmt-xml-elements-library.md)
|
||||
##### [Offline Migration Reference](offline-migration-reference.md)
|
||||
|
||||
66
windows/deploy/activate-forest-by-proxy-vamt.md
Normal file
66
windows/deploy/activate-forest-by-proxy-vamt.md
Normal file
@ -0,0 +1,66 @@
|
||||
---
|
||||
title: Activate by Proxy an Active Directory Forest (Windows 10)
|
||||
description: Activate by Proxy an Active Directory Forest
|
||||
ms.assetid: 6475fc87-a6f7-4fa8-b0aa-de19f2dea7e5
|
||||
ms.prod: W10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Activate by Proxy an Active Directory Forest
|
||||
You can use the Volume Activation Management Tool (VAMT) Active Directory-Based Activation (ADBA) function to activate by proxy an Active Directory (AD) forest for an isolated workgroup that does not have Internet access. ADBA enables certain volume products to inherit activation from the domain.
|
||||
|
||||
**Important**
|
||||
ADBA is only applicable to Generic Volume License Keys (GVLKs) and KMS Host key (CSVLK). To use ADBA, one or more KMS Host keys (CSVLK) must be installed on the AD forest, and client keys (GVLKs) must be installed on the client products.
|
||||
|
||||
In a typical proxy-activation scenario, the VAMT host computer distributes a product key to one or more client computers and collects the installation ID (IID) from each computer. The VAMT host computer sends the IIDs to Microsoft on behalf of the client computers and obtains the corresponding Confirmation IDs (CIDs). The VAMT host computer then installs the CIDs on the client computer to complete the activation. If you use this activation method, only the VAMT host computer needs to have Internet access.
|
||||
|
||||
**Note**
|
||||
For workgroups that are isolated from any larger network, you can still perform an AD forest activation. This requires installing a second instance of VAMT on a computer in the isolated group and using removable media to transfer activation data between that computer and another VAMT host computer that has Internet access. You can also activate by proxy a KMS Host key (CSVLK) in the core network if you do not want the host computer to connect to Microsoft over the Internet.
|
||||
|
||||
## Requirements
|
||||
Before performing proxy activation, ensure that the network and the VAMT installation meet the following requirements:
|
||||
- There is an instance of VAMT that is installed on a computer that has Internet access. If you are performing proxy activation for an isolated workgroup, you must also have VAMT installed on one of the computers in the workgroup.
|
||||
|
||||
- VAMT has administrative permissions to the Active Directory domain.
|
||||
|
||||
**To perform an Active Directory forest proxy activation**
|
||||
|
||||
1. Open VAMT.
|
||||
|
||||
2. In the left-side pane, click the **Active Directory-Based Activation** node.
|
||||
|
||||
3. In the right-side **Actions** pane, click **Proxy activate forest** to open the **Install Product Key** dialog box.
|
||||
|
||||
4. In the **Install Product Key** dialog box, select the KMS Host key (CSVLK) that you want to activate.
|
||||
|
||||
5. If you want to rename the ADBA object, enter a new Active Directory-Based Activation Object name.
|
||||
|
||||
**Important**
|
||||
If you want to rename the ADBA object, you must do it now. After you click **Install Key**, the name cannot be changed.
|
||||
|
||||
6. Enter the name of the file where you want to save the offline installation ID, or browse to the file location and then click **Open**. If you are activating an AD forest in an isolated workgroup, save the .cilx file to a removable media device.
|
||||
|
||||
7. Click **Install Key**.
|
||||
|
||||
VAMT displays the **Activating Active Directory** dialog box until it completes the requested action. The activated object and the date that it was created appear in the **Active Directory-Based Activation** node in the center pane.
|
||||
|
||||
9. Insert the removable media into the VAMT host that has Internet access. Make sure that you are on the root node, and that the **Volume Activation Management Tool** view is displayed in the center pane.
|
||||
|
||||
10. In the right-side **Actions** pane, click **Acquire confirmation IDs for CILX** to open the **Acquire confirmation IDs for file** dialog box.
|
||||
|
||||
11. In the **Acquire confirmation IDs for file** dialog box, browse to where the .cilx file you exported from the isolated workgroup host computer is located. Select the file, and then click **Open**. VAMT displays an **Acquiring Confirmation IDs** message while it contacts Microsoft and acquires the CIDs.
|
||||
|
||||
12. When the CID collection process is complete, VAMT displays a **Volume Activation Management Tool** message that shows how many confirmation IDs were successfully acquired, and the name of the file to which the IDs were saved. Click **OK** to close the message.
|
||||
|
||||
13. Remove the storage device that contains the .cilx file from the Internet-connected VAMT host computer and insert it into the VAMT host computer in the isolated workgroup.
|
||||
|
||||
14. Open VAMT and then click the **Active Directory-Based Activation** node in the left-side pane.
|
||||
|
||||
15. In the right-side **Actions** pane, click **Apply confirmation ID to Active Directory domain**, browse to the .cilx file and then click **Open**.
|
||||
|
||||
VAMT displays the **Activating Active Directory** dialog box until it completes the requested action. The activated object and the date that it was created appear in the **Active Directory-Based Activation** node in the center pane.
|
||||
|
||||
## Related topics
|
||||
- [Add and Remove Computers](add-remove-computers-vamt.md)
|
||||
50
windows/deploy/activate-forest-vamt.md
Normal file
50
windows/deploy/activate-forest-vamt.md
Normal file
@ -0,0 +1,50 @@
|
||||
---
|
||||
title: Activate an Active Directory Forest Online (Windows 10)
|
||||
description: Activate an Active Directory Forest Online
|
||||
ms.assetid: 9b5bc193-799b-4aa5-9d3e-0e495f7195d3
|
||||
ms.prod: W10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Activate an Active Directory Forest Online
|
||||
You can use the Volume Activation Management Tool (VAMT) Active Directory-Based Activation (ADBA) function to activate an Active Directory (AD) forest over the Internet. ADBA enables certain products to inherit activation from the domain.
|
||||
|
||||
**Important**
|
||||
ADBA is only applicable to Generic Volume License Keys (GVLKs) and KMS Host keys (CSVLKs). To use ADBA, one or more KMS Host keys (CSVLKs) must be installed on the AD forest, and client keys (GVLKs) must be installed on the client products.
|
||||
|
||||
## Requirements
|
||||
Before performing online activation, ensure that the network and the VAMT installation meet the following requirements:
|
||||
|
||||
- VAMT is installed on a host computer that has Internet access.
|
||||
|
||||
- VAMT has administrative permissions to the Active Directory domain.
|
||||
|
||||
- The KMS Host key (CSVLK) you intend to use is added to VAMT in the **Product Keys** node.
|
||||
|
||||
|
||||
**To perform an online Active Directory forest activation**
|
||||
|
||||
1. Open VAMT.
|
||||
|
||||
2. In the left-side pane, click the **Active Directory-Based Activation** node.
|
||||
|
||||
3. In the right-side **Actions** pane, click **Online activate forest** to open the **Install Product Key** dialog box.
|
||||
|
||||
4. In the **Install Product Key** dialog box, select the KMS Host key (CSVLK) that you want to apply to the AD forest.
|
||||
|
||||
5. If required, enter a new Active Directory-Based Activation Object name
|
||||
|
||||
**Important**
|
||||
If you want to rename the ADBA object, you must do it now. After you click **Install Key**, the name cannot be changed.
|
||||
|
||||
6. Click **Install Key**.
|
||||
|
||||
7. VAMT displays the **Activating Active Directory** dialog box until it completes the requested action.
|
||||
|
||||
The activated object and the date that is was created appear in the **Active Directory-Based Activation** node in the center pane.
|
||||
|
||||
## Related topics
|
||||
- [Scenario 1: Online Activation](scenario-online-activation-vamt.md)
|
||||
- [Add and Remove Computers](add-remove-computers-vamt.md)
|
||||
@ -0,0 +1,118 @@
|
||||
---
|
||||
title: Activate using Active Directory-based activation (Windows 10)
|
||||
description: Active Directory-based activation is implemented as a role service that relies on AD DS to store activation objects.
|
||||
ms.assetid: 08cce6b7-7b5b-42cf-b100-66c363a846af
|
||||
keywords: ["vamt", "volume activation", "activation", "windows activation"]
|
||||
ms.prod: W10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
---
|
||||
|
||||
# Activate using Active Directory-based activation
|
||||
**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](http://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
Active Directory-based activation is implemented as a role service that relies on AD DS to store activation objects. Active Directory-based activation requires that the forest schema be updated by adprep.exe on a computer running Windows Server 2012 R2 or Windows Server 2012, but after the schema is updated, older domain controllers can still activate clients.
|
||||
|
||||
Any domain-joined computers running Windows 10, Windows 8.1, Windows 8, Windows Server 2012 R2, or Windows Server 2012 with a GVLK will be activated automatically and transparently. They will stay activated as long as they remain members of the domain and maintain periodic contact with a domain controller. Activation takes place after the Licensing service starts. When this service starts, the computer contacts AD DS automatically, receives the activation object, and is activated without user intervention.
|
||||
|
||||
To allow computers with GVLKs to activate themselves, use the Volume Activation Tools console in Windows Server 2012 R2 or the VAMT in earlier versions of Windows Server to create an object in the AD DS forest. You create this activation object by submitting a KMS host key to Microsoft, as shown in Figure 10.
|
||||
|
||||
The process proceeds as follows:
|
||||
|
||||
1. Perform one of the following tasks:
|
||||
|
||||
- Install the Volume Activation Services server role on a domain controller running Windows Server 2012 R2, and add a KMS host key by using the Volume Activation Tools Wizard.
|
||||
|
||||
- Extend the domain to the Windows Server 2012 R2 schema level, and add a KMS host key by using the VAMT.
|
||||
|
||||
2. Microsoft verifies the KMS host key, and an activation object is created.
|
||||
|
||||
3. Client computers are activated by receiving the activation object from a domain controller during startup.
|
||||
|
||||
|
||||
|
||||
**Figure 10**. The Active Directory-based activation flow
|
||||
|
||||
For environments in which all computers are running Windows 10, Windows 8.1, Windows 8, Windows Server 2012 R2, or Windows Server 2012 R2, and they are joined to a domain, Active Directory-based activation is the best option for activating all client computers and servers, and you may be able to remove any KMS hosts from your environment.
|
||||
|
||||
If an environment will continue to contain earlier volume licensing operating systems and applications or if you have workgroup computers outside the domain, you need to maintain a KMS host to maintain activation status for earlier volume licensing editions of Windows and Office.
|
||||
|
||||
Clients that are activated with Active Directory-based activation will maintain their activated state for up to 180 days since the last contact with the domain, but they will periodically attempt to reactivate before then and at the end of the 180day period. By default, this reactivation event occurs every seven days.
|
||||
|
||||
When a reactivation event occurs, the client queries AD DS for the activation object. Client computers examine the activation object and compare it to the local edition as defined by the GVLK. If the object and GVLK match, reactivation occurs. If the AD DS object cannot be retrieved, client computers use KMS activation. If the computer is removed from the domain, when the computer or the Software Protection service is restarted, the operating system will change the status from activated to not activated, and the computer will try to activate with KMS.
|
||||
|
||||
## Step-by-step configuration: Active Directory-based activation
|
||||
**Note**
|
||||
You must be a member of the local Administrators group on all computers mentioned in these steps. You also need to be a member of the Enterprise Administrators group, because setting up Active Directory-based activation changes forest-wide settings.
|
||||
|
||||
**To configure Active Directory-based activation on Windows Server 2012 R2, complete the following steps:**
|
||||
|
||||
1. Use an account with Domain Administrator and Enterprise Administrator credentials to sign in to a domain controller.
|
||||
|
||||
2. Launch Server Manager.
|
||||
|
||||
3. Add the Volume Activation Services role, as shown in Figure 11.
|
||||
|
||||
|
||||
|
||||
**Figure 11**. Adding the Volume Activation Services role
|
||||
|
||||
4. Click the link to launch the Volume Activation Tools (Figure 12).
|
||||
|
||||
|
||||
|
||||
**Figure 12**. Launching the Volume Activation Tools
|
||||
|
||||
5. Select the **Active Directory-Based Activation** option (Figure 13).
|
||||
|
||||
|
||||
|
||||
**Figure 13**. Selecting Active Directory-Based Activation
|
||||
|
||||
6. Enter your KMS host key and (optionally) a display name (Figure 14).
|
||||
|
||||
|
||||
|
||||
**Figure 14**. Entering your KMS host key
|
||||
|
||||
7. Activate your KMS host key by phone or online (Figure 15).
|
||||
|
||||
|
||||
|
||||
**Figure 15**. Choosing how to activate your product
|
||||
|
||||
8. After activating the key, click **Commit**, and then click **Close**.
|
||||
|
||||
## Verifying the configuration of Active Directory-based activation
|
||||
To verify your Active Directory-based activation configuration, complete the following steps:
|
||||
|
||||
1. After you configure Active Directory-based activation, start a computer that is running an edition of Windows that is configured by volume licensing.
|
||||
|
||||
2. If the computer has been previously configured with a MAK key, replace the MAK key with the GVLK by running the **slmgr.vbs /ipk** command and specifying the GLVK as the new product key.
|
||||
|
||||
3. If the computer is not joined to your domain, join it to the domain.
|
||||
|
||||
4. Sign in to the computer.
|
||||
|
||||
5. Open Windows Explorer, right-click **Computer**, and then click **Properties**.
|
||||
|
||||
6. Scroll down to the **Windows activation** section, and verify that this client has been activated.
|
||||
|
||||
**Note**<br>
|
||||
If you are using both KMS and Active Directory-based activation, it may be difficult to see whether a client has been activated by KMS or by Active Directory-based activation. Consider disabling KMS during the test, or make sure that you are using a client computer that has not already been activated by KMS. The **slmrg.vbs /dlv** command also indicates whether KMS has been used.
|
||||
|
||||
## See also
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
155
windows/deploy/activate-using-key-management-service-vamt.md
Normal file
155
windows/deploy/activate-using-key-management-service-vamt.md
Normal file
@ -0,0 +1,155 @@
|
||||
---
|
||||
title: Activate using Key Management Service (Windows 10)
|
||||
ms.assetid: f2417bfe-7d25-4e82-bc07-de316caa8dac
|
||||
description:
|
||||
keywords: ["vamt", "volume activation", "activation", "windows activation"]
|
||||
ms.prod: W10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Activate using Key Management Service
|
||||
**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](http://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
There are three possible scenarios for volume activation of Windows 10 or Windows Server 2012 R2 by using a Key Management Service (KMS) host:
|
||||
|
||||
- Host KMS on a computer running Windows 10
|
||||
|
||||
- Host KMS on a computer running Windows Server 2012 R2
|
||||
|
||||
- Host KMS on a computer running an earlier version of Windows
|
||||
|
||||
## Key Management Service in Windows 10
|
||||
Installing a KMS host key on a computer running Windows 10 allows you to activate other computers running Windows 10 against this KMS host and earlier versions of the client operating system, such as Windows 8.1 or Windows 7.
|
||||
|
||||
Clients locate the KMS server by using resource records in DNS, so some configuration of DNS may be required. This scenario can be beneficial if your organization uses volume activation for clients and MAK-based activation for a smaller number of servers.
|
||||
|
||||
To enable KMS functionality, a KMS key is installed on a KMS host; then, the host is activated over the Internet or by phone using Microsoft’s activation services.
|
||||
|
||||
**Configure KMS in Windows 10**
|
||||
|
||||
1. Open an elevated command prompt.
|
||||
|
||||
2. Enter one of the following commands.
|
||||
- To install a KMS key, type **slmgr.vbs /ipk <KmsKey>**.
|
||||
- To activate online, type **slmgr.vbs /ato**.
|
||||
- To activate by using the telephone, type **slui.exe 4**.
|
||||
|
||||
3. After activating the KMS key, restart the Software Protection Service.
|
||||
|
||||
For more information, see the information for Windows 7 in [Deploy KMS Activation](http://go.microsoft.com/fwlink/p/?LinkId=717032).
|
||||
|
||||
## Key Management Service in Windows Server 2012 R2
|
||||
Installing a KMS host key on a computer running Windows Server allows you to activate computers running Windows Server 2012 R2, Windows Sever 2008 R2, Windows Server 2008, Windows 10, Windows 8.1, Windows 7, and Windows Vista.
|
||||
|
||||
**Note**
|
||||
You cannot install a client KMS key into the KMS in Windows Server.
|
||||
|
||||
This scenario is commonly used in larger organizations that do not find the overhead of using a server a burden.
|
||||
|
||||
**Note**
|
||||
If you receive error 0xC004F015 when trying to activate Windows 10 Enterprise, see [KB 3086418](http://go.microsoft.com/fwlink/p/?LinkId=620687).
|
||||
|
||||
**Configure KMS in Windows Server 2012 R2**
|
||||
|
||||
1. Sign in to a computer running Windows Server 2012 R2 with an account that has local administrative credentials.
|
||||
|
||||
2. Launch Server Manager.
|
||||
|
||||
3. Add the Volume Activation Services role, as shown in Figure 4.
|
||||
|
||||
|
||||
|
||||
**Figure 4**. Adding the Volume Activation Services role in Server Manager
|
||||
|
||||
4. When the role installation is complete, click the link to launch the Volume Activation Tools (Figure 5).
|
||||
|
||||
|
||||
|
||||
**Figure 5**. Launching the Volume Activation Tools
|
||||
|
||||
5. Select the **Key Management Service (KMS)** option, and specify the computer that will act as the KMS host (Figure 6).
|
||||
|
||||
This can be the same computer on which you installed the role or another computer. For example, it can be a client computer running Windows 10.
|
||||
|
||||
|
||||
|
||||
**Figure 6**. Configuring the computer as a KMS host
|
||||
|
||||
6. Install your KMS host key by typing it in the text box, and then click **Commit** (Figure 7).
|
||||
|
||||
|
||||
|
||||
**Figure 7**. Installing your KMS host key
|
||||
|
||||
7. If asked to confirm replacement of an existing key, click **Yes**.
|
||||
|
||||
8. After the product key is installed, you must activate it. Click **Next** (Figure 8).
|
||||
|
||||
|
||||
|
||||
**Figure 8**. Activating the software
|
||||
|
||||
The KMS key can be activated online or by phone. See Figure 9.
|
||||
|
||||
|
||||
|
||||
**Figure 9**. Choosing to activate online
|
||||
|
||||
Now that the KMS host is configured, it will begin to listen for activation requests. However, it will not activate clients successfully until the activation threshold is met.
|
||||
|
||||
## Verifying the configuration of Key Management Service
|
||||
You can verify KMS volume activation from the KMS host server or from the client computer. KMS volume activation requires a minimum threshold of 25 computers before activation requests will be processed. The verification process described here will increment the activation count each time a client computer contacts the KMS host, but unless the activation threshold is reached, the verification will take the form of an error message rather than a confirmation message.
|
||||
|
||||
**Note**
|
||||
If you configured Active Directory-based activation before configuring KMS activation, you must use a client computer that will not first try to activate itself by using Active Directory-based activation. You could use a workgroup computer that is not joined to a domain or a computer running Windows 7 or Windows Server 2008 R2.
|
||||
|
||||
To verify that KMS volume activation works, complete the following steps:
|
||||
|
||||
1. On the KMS host, open the event log and confirm that DNS publishing is successful.
|
||||
|
||||
2. On a client computer, open a Command Prompt window, type **Slmgr.vbs /ato**, and then press ENTER.<p>
|
||||
The **/ato** command causes the operating system to attempt activation by using whichever key has been installed in the operating system. The response should show the license state and detailed Windows version information.
|
||||
|
||||
3. On a client computer or the KMS host, open an elevated Command Prompt window, type **Slmgr /dlv**, and then press ENTER.<p>
|
||||
The **/dlv** command displays the detailed licensing information. The response should return an error that states that the KMS activation count is too low. This confirms that KMS is functioning correctly, even though the client has not been activated.
|
||||
|
||||
For more information about the use and syntax of slmgr.vbs, see [Slmgr.vbs Options](http://go.microsoft.com/fwlink/p/?LinkId=733639).
|
||||
|
||||
## Key Management Service in earlier versions of Windows
|
||||
If you have already established a KMS infrastructure in your organization for an earlier version of Windows, you may want to continue using that infrastructure to activate computers running Windows 10 or Windows Server 2012 R2. Your existing KMS host must be running Windows 7 or later. To upgrade your KMS host, complete the following steps:
|
||||
|
||||
1. Download and install the correct update for your current KMS host operating system. Restart the computer as directed.
|
||||
|
||||
2. Request a new KMS host key from the Volume Licensing Service Center.
|
||||
|
||||
3. Install the new KMS host key on your KMS host.
|
||||
|
||||
4. Activate the new KMS host key by running the slmrg.vbs script.
|
||||
|
||||
For detailed instructions, see [Update that enables Windows 8.1 and Windows 8 KMS hosts to activate a later version of Windows](http://go.microsoft.com/fwlink/p/?LinkId=618265) and [Update that enables Windows 7 and Windows Server 2008 R2 KMS hosts to activate Windows 10](http://go.microsoft.com/fwlink/p/?LinkId=626590).
|
||||
|
||||
## See also
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
128
windows/deploy/activate-windows-10-clients-vamt.md
Normal file
128
windows/deploy/activate-windows-10-clients-vamt.md
Normal file
@ -0,0 +1,128 @@
|
||||
---
|
||||
title: Activate clients running Windows 10 (Windows 10)
|
||||
description: After you have configured Key Management Service (KMS) or Active Directory-based activation on your network, activating a client running Windows 10 is easy.
|
||||
ms.assetid: 39446e49-ad7c-48dc-9f18-f85a11ded643
|
||||
keywords: ["vamt", "volume activation", "activation", "windows activation"]
|
||||
ms.prod: W10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Activate clients running Windows 10
|
||||
**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](http://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
After you have configured Key Management Service (KMS) or Active Directory-based activation on your network, activating a client running Windows 10 is easy. If the computer has been configured with a Generic Volume License Key (GVLK), neither IT nor the user need take any action. It just works.
|
||||
|
||||
Enterprise edition images and installation media should already be configured with the GVLK. When the client computer starts, the Licensing service examines the current licensing condition of the computer.
|
||||
|
||||
If activation or reactivation is required, the following sequence occurs:
|
||||
|
||||
1. If the computer is a member of a domain, it asks a domain controller for a volume activation object. If Active Directory-based activation is configured, the domain controller returns the object. If the object matches the edition of the software that is installed and the computer has a matching GVLK, the computer is activated (or reactivated), and it will not need to be activated again for 180 days, although the operating system will attempt reactivation at much shorter, regular intervals.
|
||||
|
||||
2. If the computer is not a member of a domain or if the volume activation object is not available, the computer will issue a DNS query to attempt to locate a KMS server. If a KMS server can be contacted, activation occurs if the KMS has a key that matches the computer’s GVLK.
|
||||
|
||||
3. The computer tries to activate against Microsoft servers if it is configured with a MAK.
|
||||
|
||||
If the client is not able to activate itself successfully, it will periodically try again. The frequency of the retry attempts depends on the current licensing state and whether the client computer has been successfully activated in the past. For example, if the client computer had been previously activated by Active Directory-based activation, it will periodically try to contact the domain controller at each restart.
|
||||
|
||||
## How Key Management Service works
|
||||
KMS uses a client–server topology. KMS client computers can locate KMS host computers by using DNS or a static configuration. KMS clients contact the KMS host by using RPCs carried over TCP/IP.
|
||||
|
||||
### Key Management Service activation thresholds
|
||||
You can activate physical computers and virtual machines by contacting a KMS host. To qualify for KMS activation, there must be a minimum number of qualifying computers (called the activation threshold). KMS clients will be activated only after this threshold has been met. Each KMS host counts the number of computers that have requested activation until the threshold is met.
|
||||
|
||||
A KMS host responds to each valid activation request from a KMS client with the count of how many computers have already contacted the KMS host for activation. Client computers that receive a count below the activation threshold are not activated. For example, if the first two computers that contact the KMS host are running Windows 10, the first receives an activation count of 1, and the second receives an activation count of 2. If the next computer is a virtual machine on a computer running Windows 10, it receives an activation count of 3, and so on. None of these computers will be activated, because computers running Windows 10, like other client operating system versions, must receive an activation count of 25 or more.
|
||||
|
||||
When KMS clients are waiting for the KMS to reach the activation threshold, they will connect to the KMS host every two hours to get the current activation count. They will be activated when the threshold is met.
|
||||
|
||||
In our example, if the next computer that contacts the KMS host is running Windows Server 2012 R2, it receives an activation count of 4, because activation counts are cumulative. If a computer running Windows Server 2012 R2 receives an activation count that is 5 or more, it is activated. If a computer running Windows 10 receives an activation count of 25 or more, it is activated.
|
||||
|
||||
### Activation count cache
|
||||
To track the activation threshold, the KMS host keeps a record of the KMS clients that request activation. The KMS host gives each KMS client a client ID designation, and the KMS host saves each client ID in a table. By default, each activation request remains in the table for up to 30 days. When a client renews its activation, the cached client ID is removed from the table, a new record is created, and the 30day period begins again. If a KMS client computer does not renew its activation within 30 days, the KMS host removes the corresponding client ID from the table and reduces the activation count by one.
|
||||
|
||||
However, the KMS host only caches twice the number of client IDs that are required to meet the activation threshold. Therefore, only the 50 most recent client IDs are kept in the table, and a client ID could be removed much sooner than 30 days.
|
||||
|
||||
The total size of the cache is set by the type of client computer that is attempting to activate. If a KMS host receives activation requests only from servers, the cache will hold only 10 client IDs (twice the required 5). If a client computer running Windows 10 contacts that KMS host, KMS increases the cache size to 50 to accommodate the higher threshold. KMS never reduces the cache size.
|
||||
|
||||
### Key Management Service connectivity
|
||||
KMS activation requires TCP/IP connectivity. By default, KMS hosts and clients use DNS to publish and find the KMS. The default settings can be used, which require little or no administrative action, or KMS hosts and client computers can be manually configured based on network configuration and security requirements.
|
||||
|
||||
### Key Management Service activation renewal
|
||||
KMS activations are valid for 180 days (the *activation validity interval*). To remain activated, KMS client computers must renew their activation by connecting to the KMS host at least once every 180 days. By default, KMS client computers attempt to renew their activation every 7 days. If KMS activation fails, the client computer retries every two hours. After a client computer’s activation is renewed, the activation validity interval begins again.
|
||||
|
||||
### Publication of the Key Management Service
|
||||
The KMS uses service (SRV) resource records in DNS to store and communicate the locations of KMS hosts. KMS hosts use the DNS dynamic update protocol, if available, to publish the KMS service (SRV) resource records. If dynamic update is not available or the KMS host does not have rights to publish the resource records, the DNS records must be published manually, or you must configure client computers to connect to specific KMS hosts.
|
||||
|
||||
### Client discovery of the Key Management Service
|
||||
By default, KMS client computers query DNS for KMS information. The first time a KMS client computer queries DNS for KMS information, it randomly chooses a KMS host from the list of service (SRV) resource records that DNS returns. The address of a DNS server that contains the service (SRV) resource records can be listed as a suffixed entry on KMS client computers, which allows one DNS server to advertise the service (SRV) resource records for KMS, and KMS client computers with other primary DNS servers to find it.
|
||||
|
||||
Priority and weight parameters can be added to the DnsDomainPublishList registry value for KMS. Establishing KMS host priority groupings and weighting within each group allows you to specify which KMS host the client computers should try first and balances traffic among multiple KMS hosts. Only Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2 provide these priority and weight parameters.
|
||||
|
||||
If the KMS host that a client computer selects does not respond, the KMS client computer removes that KMS host from its list of service (SRV) resource records and randomly selects another KMS host from the list. When a KMS host responds, the KMS client computer caches the name of the KMS host and uses it for subsequent activation and renewal attempts. If the cached KMS host does not respond on a subsequent renewal, the KMS client computer discovers a new KMS host by querying DNS for KMS service (SRV) resource records.
|
||||
|
||||
By default, client computers connect to the KMS host for activation by using anonymous RPCs through TCP port 1688. (You can change the default port.) After establishing a TCP session with the KMS host, the client computer sends a single request packet. The KMS host responds with the activation count. If the count meets or exceeds the activation threshold for that operating system, the client computer is activated and the session is closed. The KMS client computer uses this same process for renewal requests. 250 bytes are used for communication each way.
|
||||
|
||||
### Domain Name System server configuration
|
||||
The default KMS automatic publishing feature requires the service (SRV) resource record and support for DNS dynamic update protocol. KMS client computer default behavior and the KMS service (SRV) resource record publishing are supported on a DNS server that is running Microsoft software or any other DNS server that supports service (SRV) resource records (per Internet Engineering Task Force \[IETF\] Request for Comments \[RFC\] 2782) and dynamic updates (per IETF RFC 2136). For example, Berkeley Internet Domain Name versions 8.x and 9.x support service (SRV) resource records and dynamic update.
|
||||
|
||||
The KMS host must be configured so that it has the credentials needed to create and update the following resource records on the DNS servers: service (SRV), IPv4 host (A), and IPv6 host (AAAA), or the records need to be created manually. The recommended solution for giving the KMS host the needed credentials is to create a security group in AD DS, then add all KMS hosts to that group. On a DNS server that is running Microsoft software, ensure that this security group is given full control over the \_VLMCS.\_TCP record in each DNS domain that will contain the KMS service (SRV) resource records.
|
||||
|
||||
### Activating the first Key Management Service host
|
||||
KMS hosts on the network need to install a KMS key, and then be activated with Microsoft. Installation of a KMS key enables the KMS on the KMS host. After installing the KMS key, complete the activation of the KMS host by telephone or online. Beyond this initial activation, a KMS host does not communicate any information to Microsoft. KMS keys are only installed on KMS hosts, never on individual KMS client computers.
|
||||
|
||||
### Activating subsequent Key Management Service hosts
|
||||
Each KMS key can be installed on up to six KMS hosts. These hosts can be physical computers or virtual machines. After activating a KMS host, the same host can be reactivated up to nine times with the same key. If the organization needs more than six KMS hosts, you can request additional activations for your organization’s KMS key by calling a Microsoft Volume [Licensing Activation Center](http://go.microsoft.com/fwlink/p/?LinkID=618264) to request an exception.
|
||||
|
||||
## How Multiple Activation Key works
|
||||
A MAK is used for one-time activation with Microsoft’s hosted activation services. Each MAK has a predetermined number of allowed activations. This number is based on volume licensing agreements, and it might not match the organization’s exact license count. Each activation that uses a MAK with the Microsoft hosted activation service counts toward the activation limit.
|
||||
|
||||
You can activate computers by using a MAK in two ways:
|
||||
|
||||
- **MAK independent activation**. Each computer independently connects and is activated with Microsoft over the Internet or by telephone. MAK independent activation is best suited to computers within an organization that do not maintain a connection to the corporate network. MAK independent activation is shown in Figure 16.
|
||||
|
||||
|
||||
|
||||
**Figure 16**. MAK independent activation
|
||||
|
||||
- **MAK proxy activation**. MAK proxy activation enables a centralized activation request on behalf of multiple computers with one connection to Microsoft. You configure MAK proxy activation by using the VAMT. MAK proxy activation is appropriate for environments in which security concerns restrict direct access to the Internet or the corporate network. It is also suited for development and test labs that lack this connectivity. MAK proxy activation with the VAMT is shown in Figure 17.
|
||||
|
||||
|
||||
|
||||
**Figure 17**. MAK proxy activation with the VAMT
|
||||
|
||||
A MAK is recommended for computers that rarely or never connect to the corporate network and for environments in which the number of computers that require activation does not meet the KMS activation threshold.
|
||||
|
||||
You can use a MAK for individual computers or with an image that can be duplicated or installed by using Microsoft deployment solutions. You can also use a MAK on a computer that was originally configured to use KMS activation. This is useful for moving a computer off the core network to a disconnected environment.
|
||||
|
||||
### Multiple Activation Key architecture and activation
|
||||
MAK independent activation installs a MAK product key on a client computer. The key instructs that computer to activate itself with Microsoft servers over the Internet.
|
||||
|
||||
In MAK proxy activation, the VAMT installs a MAK product key on a client computer, obtains the installation ID from the target computer, sends the installation ID to Microsoft on behalf of the client, and obtains a confirmation ID. The tool then activates the client computer by installing the confirmation ID.
|
||||
|
||||
## Activating as a standard user
|
||||
Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2 do not require administrator privileges for activation, but this change does not allow standard user accounts to remove computers running Windows 7 or Windows Server 2008 R2 from the activated state. An administrator account is still required for other activation- or license-related tasks, such as “rearm.”
|
||||
|
||||
## See also
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
32
windows/deploy/active-directory-based-activation-overview.md
Normal file
32
windows/deploy/active-directory-based-activation-overview.md
Normal file
@ -0,0 +1,32 @@
|
||||
---
|
||||
title: Active Directory-Based Activation Overview (Windows 10)
|
||||
description: Active Directory-Based Activation Overview
|
||||
ms.assetid: c1dac3bd-6a86-4c45-83dd-421e63a398c0
|
||||
ms.prod: W10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
---
|
||||
|
||||
# Active Directory-Based Activation Overview
|
||||
Active Directory-Based Activation (ADBA) enables enterprises to activate computers through a connection to their domain. Many companies have computers at offsite locations that use products that are registered to the company. Previously these computers needed to either use a retail key or a Multiple Activation Key (MAK), or physically connect to the network in order to activate their products by using Key Management Services (KMS). ADBA provides a way to activate these products if the computers can join the company’s domain. When the user joins their computer to the domain, the ADBA object automatically activates Windows installed on their computer, as long as the computer has a Generic Volume License Key (GVLK) installed. No single physical computer is required to act as the activation object, because it is distributed throughout the domain.
|
||||
|
||||
## Active Directory-Based Activation Scenarios
|
||||
VAMT enables IT Professionals to manage and activate the Active Directory-Based Activation object. Activation can be performed by using a scenario such as the following:
|
||||
|
||||
- Online activation: To activate an ADBA forest online, the user selects the **Online activate forest** function, selects a KMS Host key (CSVLK) to use, and gives the Active Directory-Based Activation Object a name.
|
||||
|
||||
- Proxy activation: For a proxy activation, the user first selects the **Proxy activate forest** function, selects a KMS Host key (CSVLK) to use, gives the Active Directory-Based Activation Object a name, and provides a file name to save the CILx file that contains the Installation ID. Next, the user takes that file to a computer that is running VAMT with an Internet connection and then selects the **Acquire confirmation IDs for CILX** function on the VAMT landing page, and provides the original CILx file. When VAMT has loaded the Confirmation IDs into the original CILx file, the user takes this file back to the original VAMT instance, where the user completes the proxy activation process by selecting the **Apply confirmation ID to Active Directory domain** function.
|
||||
|
||||
## Related topics
|
||||
- [How to Activate an Active Directory Forest Online](http://go.microsoft.com/fwlink/p/?LinkId=246565)
|
||||
- [How to Proxy Activate an Active Directory Forest](http://go.microsoft.com/fwlink/p/?LinkId=246566)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,75 @@
|
||||
---
|
||||
title: Add a Windows 10 operating system image using Configuration Manager (Windows 10)
|
||||
description: Operating system images are typically the production image used for deployment throughout the organization.
|
||||
ms.assetid: 77f769cc-1a47-4f36-8082-201cd77b8d3b
|
||||
keywords: ["image, deploy, distribute"]
|
||||
ms.prod: W10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
---
|
||||
|
||||
# Add a Windows 10 operating system image using Configuration Manager
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
Operating system images are typically the production image used for deployment throughout the organization. This topic shows you how to add a Windows 10 operating system image created with Microsoft System Center 2012 R2 Configuration Manager, and how to distribute the image to a distribution point.
|
||||
|
||||
For the purposes of this topic, we will use CM01, a machine running Windows Server 2012 R2 Standard, as the distribution point. CM01 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-10-with-the-microsoft-deployment-toolkit.md). Our image is named REFW10-X64-001.wim. For details on building this image, please see [Create a Windows 10 reference image](create-a-windows-10-reference-image.md).
|
||||
|
||||
1. Using File Explorer, in the **E:\\Sources\\OSD\\OS** folder, create a subfolder named **Windows 10 Enterprise x64 RTM**.
|
||||
|
||||
2. Copy the REFW10-X64-001.wim file to the **E:\\Sources\\OSD\\OS\\Windows 10 Enterprise x64 RTM** folder.
|
||||
|
||||
|
||||
|
||||
Figure 17. The Windows 10 image copied to the Sources folder structure.
|
||||
|
||||
3. Using the Configuration Manager Console, in the Software Library workspace, right-click **Operating System Images**, and select **Add Operating System Image**.
|
||||
|
||||
4. On the **Data Source** page, in the **Path:** text box, browse to \\\\CM01\\Sources$\\OSD\\OS\\Windows 10 Enterprise x64 RTM\\REFW10-X64-001.wim and click **Next**.
|
||||
|
||||
5. On the **General** page, assign the name Windows 10 Enterprise x64 RTM and click **Next** twice, and then click **Close**.
|
||||
|
||||
6. Distribute the operating system image to the CM01 distribution point by right-clicking the Windows 10 Enterprise x64 RTM operating system image and selecting **Distribute Content**.
|
||||
|
||||
7. In the Distribute Content Wizard, add the CM01 distribution point.
|
||||
|
||||
8. View the content status for the Windows 10 Enterprise x64 RTM package. Do not continue until the distribution is completed. You also can review the E:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file and look for the **STATMSG: ID=2301** line.
|
||||
|
||||
|
||||
|
||||
Figure 18. The distributed Windows 10 Enterprise x64 RTM package.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Integrate Configuration Manager with MDT 2013 Update 2](integrate-configuration-manager-with-mdt-2013.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)
|
||||
|
||||
[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](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)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,112 @@
|
||||
---
|
||||
title: Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager (Windows 10)
|
||||
description: In this topic, you will learn how to configure the Windows Preinstallation Environment (Windows PE) to include the network drivers required to connect to the deployment share and the storage drivers required to see the local storage on machines.
|
||||
ms.assetid: 97b3ea46-28d9-407e-8c42-ded2e45e8d5c
|
||||
keywords: ["deploy, task sequence"]
|
||||
ms.prod: W10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: CFaw
|
||||
---
|
||||
|
||||
# Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- 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-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**:
|
||||
|
||||
1. Name: Windows 10 x64 - HP EliteBook 8560w
|
||||
|
||||
2. 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 2013 Update 2](integrate-configuration-manager-with-mdt-2013.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](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)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
31
windows/deploy/add-manage-products-vamt.md
Normal file
31
windows/deploy/add-manage-products-vamt.md
Normal file
@ -0,0 +1,31 @@
|
||||
---
|
||||
title: Add and Manage Products (Windows 10)
|
||||
description: Add and Manage Products
|
||||
ms.assetid: a48fbc23-917d-40f7-985c-e49702c05e51
|
||||
ms.prod: W10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Add and Manage Products
|
||||
This section describes how to add client computers into the Volume Activation Management Tool (VAMT). After the computers are added, you can manage the products that are installed on your network.
|
||||
|
||||
## In this Section
|
||||
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Add and Remove Computers](add-remove-computers-vamt.md) |Describes how to add client computers to VAMT. |
|
||||
|[Update Product Status](update-product-status-vamt.md) |Describes how to update the status of product license. |
|
||||
|[Remove Products](remove-products-vamt.md) |Describes how to remove a product from the product list. |
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
75
windows/deploy/add-remove-computers-vamt.md
Normal file
75
windows/deploy/add-remove-computers-vamt.md
Normal file
@ -0,0 +1,75 @@
|
||||
---
|
||||
title: Add and Remove Computers (Windows 10)
|
||||
description: Add and Remove Computers
|
||||
ms.assetid: cb6f3a78-ece0-4dc7-b086-cb003d82cd52
|
||||
ms.prod: W10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Add and Remove Computers
|
||||
You can add computers that have any of the supported Windows or Office products installed to a Volume Activation Management Tool (VAMT) database by using the **Discover products** function. You can search for computers in an Active Directory domain, by individual computer name or IP address, in a workgroup, or by a general LDAP query. You can remove computers from a VAMT database by using the **Delete** function. After you add the computers, you can add the products that are installed on the computers by running the **Update license status** function.
|
||||
|
||||
Before adding computers, ensure that the Windows Management Instrumentation (WMI) firewall exception required by VAMT has been enabled on all target computers. For more information see [Configure Client Computers](configure-client-computers-vamt.md).
|
||||
|
||||
## To add computers to a VAMT database
|
||||
1. Open VAMT.
|
||||
|
||||
2. Click **Discover products** in the **Actions** menu in the right-side pane to open the **Discover Products** dialog box.
|
||||
|
||||
3. In the **Discover products** dialog box, click **Search for computers in the Active Directory** to display the search options, then click the search option you want to use. You can search for computers in an Active Directory domain, by individual computer name or IP address, in a workgroup, or by a general LDAP query.
|
||||
|
||||
- To search for computers in an Active Directory domain, click **Search for computers in the Active Directory**, then under **Domain Filter Criteria**, in the list of domain names click the name of the domain you want to search. You can narrow the search further by typing a name in the **Filter by computer name** field to search for a specific computer within the domain. This filter supports the asterisk (\*) wildcard. For example, typing "a\*" will display only computer names that start with the letter "a".
|
||||
|
||||
- To search by individual computer name or IP address, click **Manually enter name or IP address**, then enter the full name or IP address in the **One or more computer names or IP addresses separated by commas** text box. Separate multiple entries with a comma. Note that VAMT supports both IPv4 and IPV6 addressing.
|
||||
|
||||
- To search for computers in a workgroup, click **Search for computers in the workgroup**, then under **Workgroup Filter Criteria**, in the list of workgroup names click the name of the workgroup you want to search. You can narrow the search further by typing a name in the **Filter by computer name** field to search for a specific computer within the workgroup. This filter supports the asterisk (\*) wildcard. For example, typing "a\*" will display only computer names that start with the letter "a".
|
||||
|
||||
- To search for computers by using a general LDAP query, click **Search with LDAP query** and enter your query in the text box provided. VAMT will validate only the LDAP query syntax, but will otherwise run the query without further checks.
|
||||
|
||||
4. Click **Search**.
|
||||
|
||||
5. VAMT searches for the specified computers and adds them to the VAMT database. During the search, VAMT displays the **Finding computers** message shown below.
|
||||
|
||||
To cancel the search, click **Cancel**. When the search is complete the names of the newly-discovered computers appear in the product list view in the center pane.
|
||||
|
||||
|
||||
|
||||
**Important**
|
||||
This step adds only the computers to the VAMT database, and not the products that are installed on the computers. To add the products, you need to run the **Update license status** function.
|
||||
|
||||
## To add products to VAMT
|
||||
1. In the **Products** list, select the computers that need to have their product information added to the VAMT database.
|
||||
|
||||
2. You can use the **Filter** function to narrow your search for computers by clicking **Filter** in the right-side pane to open the **Filter Products** dialog box.
|
||||
|
||||
3. In the **Filter Products** dialog box, you can filter the list by computer name, product name, product key type, license status, or by any combination of these options.
|
||||
|
||||
- To filter the list by computer name, enter a name in the **Computer Name** box.
|
||||
|
||||
- To filter the list by Product Name, Product Key Type, or License Status, click the list you want to use for the filter and select an option. If necessary, click **clear all filters** to create a new filter.
|
||||
|
||||
4. Click **Filter**. VAMT displays the filtered list in the center pane.
|
||||
|
||||
5. In the right-side **Actions** pane, click **Update license status** and then click a credential option. Choose **Alternate Credentials** only if you are updating products that require administrator credentials different from the ones you used to log into the computer. If you are supplying alternate credentials, in the **Windows Security** dialog box type the appropriate user name and password and click **OK**.
|
||||
|
||||
6. VAMT displays the **Collecting product information** dialog box while it collects the licensing status of all supported products on the selected computers. When the process is finished, the updated licensing status of each product will appear in the product list view in the center pane.
|
||||
|
||||
**Note**
|
||||
If a computer has more than one supported product installed, VAMT adds an entry for each product. The entry appears under the appropriate product heading.
|
||||
|
||||
## To remove computers from a VAMT database
|
||||
You can delete a computer by clicking on it in the product list view, and then clicking **Delete** in the **Selected Item** menu in the right-hand pane. In the **Confirm Delete Selected Products** dialog box that appears, click **Yes** to delete the computer. If a computer has multiple products listed, you must delete each product to completely remove the computer from the VAMT database.
|
||||
|
||||
## Related topics
|
||||
- [Add and Manage Products](add-manage-products-vamt.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
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