From fa2e3779e1972b3f7af5498c53fafe8aada8c52d Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 1 Nov 2016 14:41:20 -0700 Subject: [PATCH] Fixing broken bookmarks --- windows/deploy/introduction-vamt.md | 8 ++++---- windows/deploy/usmt-exclude-files-and-settings.md | 2 +- ...guring-uev-with-system-center-configuration-manager.md | 4 ++-- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/windows/deploy/introduction-vamt.md b/windows/deploy/introduction-vamt.md index 3d51c0dd02..133b8e6966 100644 --- a/windows/deploy/introduction-vamt.md +++ b/windows/deploy/introduction-vamt.md @@ -22,18 +22,18 @@ VAMT can be installed on, and can manage, physical or virtual instances. VAMT ca - [Enterprise Environment](#bkmk-enterpriseenvironment) - [VAMT User Interface](#bkmk-userinterface) -## Managing Multiple Activation Key (MAK) and Retail Activation +## Managing Multiple Activation Key (MAK) and Retail Activation You can use a MAK or a retail product key to activate Windows, Windows Server, or Office on an individual computer or a group of computers. VAMT enables two different activation scenarios: - **Online activation.** Many enterprises maintain a single Windows system image or Office installation package for deployment across the enterprise. Occasionally there is also a need to use retail product keys in special situations. Online activation enables you to activate over the Internet any products installed with MAK, KMS host, or retail product keys on one or more connected computers within a network. This process requires that each product communicate activation information directly to Microsoft. - **Proxy activation.** This activation method enables you to perform volume activation for products installed on client computers that do not have Internet access. The VAMT host computer distributes a MAK, KMS Host key (CSVLK), or retail product key to one or more client products and collects the installation ID (IID) from each client product. The VAMT host sends the IIDs to Microsoft on behalf of the client products and obtains the corresponding Confirmation IDs (CIDs). The VAMT host then installs the CIDs on the client products to complete the activation. Using this method, only the VAMT host computer needs Internet access. You can also activate products installed on computers in a workgroup that is completely isolated from any larger network, by installing a second instance of VAMT on a computer within the workgroup. Then, use removable media to transfer activation data between this new instance of VAMT and the Internet-connected VAMT host. -## Managing Key Management Service (KMS) Activation +## Managing Key Management Service (KMS) Activation In addition to MAK or retail activation, you can use VAMT to perform volume activation using the Key Management Service (KMS). VAMT can install and activate GVLK (KMS client) keys on client products. GVLKs are the default product keys used by Volume License editions of Windows Vista, Windows 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012 as well as Microsoft Office 2010. VAMT treats a KMS Host key (CSVLK) product key identically to a retail-type product key; therefore, the experience for product key entry and activation management are identical for both these product key types. -## Enterprise Environment +## Enterprise Environment VAMT is commonly implemented in enterprise environments. The following illustrates three common environments—Core Network, Secure Zone, and Isolated Lab. @@ -42,7 +42,7 @@ VAMT is commonly implemented in enterprise environments. The following illustrat In the Core Network environment, all computers are within a common network managed by Active Directory® Domain Services (AD DS). The Secure Zone represents higher-security Core Network computers that have additional firewall protection. The Isolated Lab environment is a workgroup that is physically separate from the Core Network, and its computers do not have Internet access. The network security policy states that no information that could identify a specific computer or user may be transferred out of the Isolated Lab. -## VAMT User Interface +## VAMT User Interface The following screenshot shows the VAMT graphical user interface. diff --git a/windows/deploy/usmt-exclude-files-and-settings.md b/windows/deploy/usmt-exclude-files-and-settings.md index e856679334..a70c486b1f 100644 --- a/windows/deploy/usmt-exclude-files-and-settings.md +++ b/windows/deploy/usmt-exclude-files-and-settings.md @@ -246,7 +246,7 @@ The following .xml file unconditionally excludes the system folders of `C:\Windo ``` -## Create a Config.xml File +## Create a Config XML File You can create and modify a Config.xml file if you want to exclude components from the migration. Excluding components using this file is easier than modifying the migration .xml files because you do not need to be familiar with the migration rules and syntax. Config.xml is an optional file that you can create using the **/genconfig** command-line option with the ScanState tool. For example, you can use the Config.xml file to exclude the settings for one of the default applications. In addition, creating and modifying this file is the only way to exclude the operating-system settings that are migrated to computers running Windows. - **To exclude the settings for a default application:** Specify `migrate="no"` for the application under the <Applications> section of the Config.xml file. diff --git a/windows/manage/uev-configuring-uev-with-system-center-configuration-manager.md b/windows/manage/uev-configuring-uev-with-system-center-configuration-manager.md index c81a7384be..ec06465c51 100644 --- a/windows/manage/uev-configuring-uev-with-system-center-configuration-manager.md +++ b/windows/manage/uev-configuring-uev-with-system-center-configuration-manager.md @@ -104,7 +104,7 @@ It might be necessary to change the PowerShell execution policy to allow these s 2. In the **User Agent** tab, set the **PowerShell Execution Policy** to **Bypass**   -**Create the first UE-V policy configuration item** +**Create the first UE-V policy configuration item** 1. Copy the default settings configuration file from the UE-V Config Pack installation directory to a location visible to your ConfigMgr Admin Console: @@ -171,7 +171,7 @@ It might be necessary to change the PowerShell execution policy to allow these s 3. Reimport the CAB file. The version in ConfigMgr will be updated. -## Generate a UE-V Template Baseline +## Generate a UE-V Template Baseline UE-V templates are distributed using a baseline containing multiple configuration items. Each configuration item contains the discovery and remediation scripts needed to install one UE-V template. The actual UE-V template is embedded within the remediation script for distribution using standard Configuration Item functionality.