mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-19 20:33:42 +00:00
Merge branch 'main' into wufb_do
This commit is contained in:
Angela Fleischmann
GitHub
@ -143,8 +143,8 @@ When you configure your MDT Build Lab deployment share, you can also add applica
|
||||
|
||||
On **MDT01**:
|
||||
|
||||
1. Download the Enterprise distribution version of [Adobe Acrobat Reader DC](https://get.adobe.com/reader/enterprise/) (AcroRdrDC2200320263_en_US.exe) to **D:\\setup\\adobe** on MDT01.
|
||||
2. Extract the .exe file that you downloaded to a .msi (ex: .\AcroRdrDC2200320263_en_US.exe -sfx_o"d:\setup\adobe\install\" -sfx_ne).
|
||||
1. Download the Enterprise distribution version of [Adobe Acrobat Reader DC](https://get.adobe.com/reader/enterprise/) (AcroRdrDC2200320282_en_US.exe) to **D:\\setup\\adobe** on MDT01.
|
||||
2. Extract the .exe file that you downloaded to a .msi (ex: .\AcroRdrDC2200320282_en_US.exe -sfx_o"d:\setup\adobe\install\" -sfx_ne).
|
||||
3. In the Deployment Workbench, expand the **MDT Production** node and navigate to the **Applications** node.
|
||||
4. Right-click the **Applications** node, and create a new folder named **Adobe**.
|
||||
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 61 KiB After Width: | Height: | Size: 50 KiB |
@ -40,7 +40,9 @@ Servicing stack update are released depending on new issues or vulnerabilities.
|
||||
|
||||
Both Windows client and Windows Server use the cumulative update mechanism, in which many fixes to improve the quality and security of Windows are packaged into a single update. Each cumulative update includes the changes and fixes from all previous updates.
|
||||
|
||||
Servicing stack updates must ship separately from the cumulative updates because they modify the component that installs Windows updates. The servicing stack is released separately because the servicing stack itself requires an update. For example, the cumulative update [KB4284880](https://support.microsoft.com/help/4284880/windows-10-update-kb4284880) requires the [May 17, 2018 servicing stack update](https://support.microsoft.com/help/4132216), which includes updates to Windows Update.
|
||||
Servicing stack updates improve the reliability of the update process to mitigate potential issues while installing the latest quality updates and feature updates. If you don't install the latest servicing stack update, there's a risk that your device can't be updated with the latest Microsoft security fixes.
|
||||
|
||||
Beginning with the February 2021 LCU, Microsoft will publish all future cumulative updates and SSUs for Windows 10, version 2004 and later together as one cumulative monthly update to the normal release category in WSUS.
|
||||
|
||||
## Is there any special guidance?
|
||||
|
||||
|
||||
@ -48,7 +48,7 @@ Windows Update for Business enables an IT administrator to receive and manage a
|
||||
Windows Update for Business provides management policies for several types of updates to Windows 10 devices:
|
||||
|
||||
- **Feature updates:** Previously referred to as "upgrades," feature updates contain not only security and quality revisions, but also significant feature additions and changes. Feature updates are released as soon as they become available.
|
||||
- **Quality updates:** Quality updates are traditional operating system updates, typically released on the second Tuesday of each month (though they can be released at any time). These include security, critical, and driver updates. Windows Update for Business also treats non-Windows updates (such as updates for Microsoft Office or Visual Studio) as quality updates. These non-Windows Updates are known as "Microsoft updates" and you can set devices to receive such updates (or not) along with their Windows updates.
|
||||
- **Quality updates:** Quality updates are traditional operating system updates, typically released on the second Tuesday of each month (though they can be released at any time). These include security, critical, and driver updates.
|
||||
- **Driver updates:** Updates for non-Microsoft drivers that are relevant to your devices. Driver updates are on by default, but you can use Windows Update for Business policies to turn them off if you prefer.
|
||||
- **Microsoft product updates**: Updates for other Microsoft products, such as versions of Office that are installed by using Windows Installer (MSI). Versions of Office that are installed by using Click-to-Run can't be updated by using Windows Update for Business. Product updates are off by default. You can turn them on by using Windows Update for Business policies.
|
||||
|
||||
|
||||
@ -34,7 +34,7 @@ This article outlines the general process that you should follow to migrate file
|
||||
|
||||
6. Create a [Config.xml File](usmt-configxml-file.md) if you want to exclude any components from the migration. To create this file, use the [ScanState Syntax](usmt-scanstate-syntax.md) option together with the other .xml files when you use the `ScanState.exe` command. For example, the following command creates a `Config.xml` file by using the `MigDocs.xml` and `MigApp.xml` files:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
ScanState.exe /genconfig:Config.xml /i:MigDocs.xml /i:MigApp.xml /v:13 /l:ScanState.log
|
||||
```
|
||||
|
||||
@ -51,7 +51,7 @@ This article outlines the general process that you should follow to migrate file
|
||||
|
||||
3. Run the `ScanState.exe` command on the source computer to collect files and settings. You should specify all of the .xml files that you want the `ScanState.exe` command to use. For example,
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
ScanState.exe \\server\migration\mystore /config:Config.xml /i:MigDocs.xml /i:MigApp.xml /v:13 /l:ScanState.log
|
||||
```
|
||||
|
||||
@ -78,7 +78,7 @@ This article outlines the general process that you should follow to migrate file
|
||||
|
||||
For example, the following command migrates the files and settings:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
LoadState.exe \\server\migration\mystore /config:Config.xml /i:MigDocs.xml /i:MigApp.xml /v:13 /l:LoadState.log
|
||||
```
|
||||
|
||||
|
||||
@ -131,7 +131,7 @@ On a test computer, install the operating system that will be installed on the d
|
||||
|
||||
To speed up the time it takes to collect and migrate the data, you can migrate only one user at a time, and you can exclude all other components from the migration except the application that you're testing. To specify only **User1** in the migration, enter:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
/ue:*\* /ui:user1
|
||||
```
|
||||
|
||||
|
||||
@ -61,7 +61,7 @@ The following table defines the supported combination of online and offline oper
|
||||
|
||||
User-group membership isn't preserved during offline migrations. You must configure a **<ProfileControl>** section in the `Config.xml` file to specify the groups that the migrated users should be made members of. The following example places all migrated users into the Users group:
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<Configuration>
|
||||
<ProfileControl>
|
||||
<localGroups>
|
||||
@ -146,7 +146,7 @@ Syntax: `<failOnMultipleWinDir>0</failOnMultipleWinDir>`
|
||||
|
||||
The following XML example illustrates some of the elements discussed earlier in this article.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<offline>
|
||||
<winDir>
|
||||
<path>C:\Windows</path>
|
||||
|
||||
@ -164,7 +164,7 @@ You can use multiple XML files with the ScanState and LoadState tools. Each of t
|
||||
|
||||
For example, you can use all of the XML migration file types for a single migration, as in the following example:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
ScanState.exe <store> /config:c:\myFolder\Config.xml /i:migapps.xml /i:MigDocs.xml /i:CustomRules.xml
|
||||
```
|
||||
|
||||
@ -194,14 +194,14 @@ To generate the XML migration rules file for a source computer:
|
||||
|
||||
4. At the command prompt, enter:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
cd /d <USMTpath>
|
||||
ScanState.exe /genmigxml: <filepath.xml>
|
||||
```
|
||||
|
||||
Where *<USMTpath>* is the location on your source computer where you've saved the USMT files and tools, and *<filepath.xml>* is the full path to a file where you can save the report. For example, enter:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
cd /d c:\USMT
|
||||
ScanState.exe /genmigxml:"C:\Documents and Settings\USMT Tester\Desktop\genMig.xml"
|
||||
```
|
||||
@ -230,13 +230,13 @@ The `MigDocs.xml` file calls the `GenerateDocPatterns` function, which takes thr
|
||||
|
||||
**Usage:**
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
MigXmlHelper.GenerateDocPatterns ("<ScanProgramFiles>", "<IncludePatterns>", "<SystemDrive>")
|
||||
```
|
||||
|
||||
To create include data patterns for only the system drive:
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<include filter='MigXmlHelper.IgnoreIrrelevantLinks()'>
|
||||
<objectSet>
|
||||
<script>MigXmlHelper.GenerateDocPatterns ("FALSE","TRUE","TRUE")</script>
|
||||
@ -246,7 +246,7 @@ To create include data patterns for only the system drive:
|
||||
|
||||
To create an include rule to gather files for registered extensions from the %PROGRAMFILES% directory:
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<include filter='MigXmlHelper.IgnoreIrrelevantLinks()'>
|
||||
<objectSet>
|
||||
<script>MigXmlHelper.GenerateDocPatterns ("TRUE","TRUE","FALSE")</script>
|
||||
@ -256,7 +256,7 @@ To create an include rule to gather files for registered extensions from the %PR
|
||||
|
||||
To create exclude data patterns:
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<exclude filter='MigXmlHelper.IgnoreIrrelevantLinks()'>
|
||||
<objectSet>
|
||||
<script>MigXmlHelper.GenerateDocPatterns ("FALSE","FALSE","FALSE")</script>
|
||||
@ -339,7 +339,7 @@ To exclude the new text document.txt file and any .txt files in "new folder", yo
|
||||
|
||||
To exclude Rule 1, there needs to be an exact match of the file name. However, for Rule 2, you can create a pattern to exclude files by using the file name extension.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<exclude>
|
||||
<objectSet>
|
||||
<pattern type="File">D:\Newfolder\[new text document.txt]</pattern>
|
||||
@ -352,7 +352,7 @@ To exclude Rule 1, there needs to be an exact match of the file name. However, f
|
||||
|
||||
If you don't know the file name or location of the file, but you do know the file name extension, you can use the `GenerateDrivePatterns` function. However, the rule will be less specific than the default include rule generated by the `MigDocs.xml` file, so it will not have precedence. You must use the <UnconditionalExclude> element to give this rule precedence over the default include rule. For more information about the order of precedence for XML migration rules, see [Conflicts and Precedence](usmt-conflicts-and-precedence.md).
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<unconditionalExclude>
|
||||
<objectSet>
|
||||
<script>MigXmlHelper.GenerateDrivePatterns ("*[*.txt]", "Fixed")</script>
|
||||
@ -364,7 +364,7 @@ If you don't know the file name or location of the file, but you do know the fil
|
||||
|
||||
If you want the **<UnconditionalExclude>** element to apply to both the system and user context, you can create a third component using the **UserandSystem** context. Rules in this component will be run in both contexts.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<component type="Documents" context="UserandSystem">
|
||||
<displayName>MigDocExcludes</displayName>
|
||||
<role role="Data">
|
||||
@ -389,7 +389,7 @@ The application data directory is the most common location that you would need t
|
||||
|
||||
This rule will include .pst files that are located in the default location, but aren't linked to Microsoft Outlook. Use the user context to run this rule for each user on the computer.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<include filter='MigXmlHelper.IgnoreIrrelevantLinks()'>
|
||||
<objectSet>
|
||||
<pattern type="File">%CSIDL_LOCAL_APPDATA%\Microsoft\Outlook\*[*.pst]</pattern>
|
||||
@ -401,7 +401,7 @@ This rule will include .pst files that are located in the default location, but
|
||||
|
||||
For locations outside the user profile, such as the Program Files folder, you can add the rule to the system context component.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<include filter='MigXmlHelper.IgnoreIrrelevantLinks()'>
|
||||
<objectSet>
|
||||
<pattern type="File">%CSIDL_PROGRAM_FILES%\*[*.pst]</pattern>
|
||||
|
||||
@ -91,7 +91,7 @@ As the authorized administrator, it is your responsibility to protect the privac
|
||||
|
||||
Although it isn't a requirement, it's good practice for **<CustomFileName>** to match the name of the file. For example, the following example is from the `MigApp.xml` file:
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/migapp">
|
||||
```
|
||||
|
||||
@ -107,7 +107,7 @@ To remove encryption from files that have already been migrated incorrectly, you
|
||||
|
||||
**Resolution:** You can use the `/mu` option when you run the **LoadState** tool to specify a new name for the user. For example,
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
LoadState.exe /i:MigApp.xml /i:MigDocs.xml \\server\share\migration\mystore
|
||||
/progress:Progress.log /l:LoadState.log /mu:fareast\user1:farwest\user1
|
||||
```
|
||||
@ -138,7 +138,7 @@ The following sections describe common XML file problems. Expand the section to
|
||||
|
||||
**Resolution:** Install all of the desired applications on the computer before running the `/genconfig` option. Then run `ScanState.exe` with all of the .xml files. For example, run the following command:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
ScanState.exe /genconfig:Config.xml /i:MigDocs.xml /i:MigApp.xml /v:5 /l:ScanState.log
|
||||
```
|
||||
|
||||
@ -248,7 +248,7 @@ The following sections describe common offline migration problems. Expand the se
|
||||
|
||||
**Resolution:** Use a Security Identifier (SID) to include a user when running the **ScanState** tool. For example:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
ScanState.exe /ui:S1-5-21-124525095-708259637-1543119021*
|
||||
```
|
||||
|
||||
@ -262,7 +262,7 @@ You can also use patterns for SIDs that identify generic users or groups. For ex
|
||||
|
||||
**Resolution:** Reboot the computer or unload the registry hive at the command prompt after the **ScanState** tool has finished running. For example, at a command prompt, enter:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
reg.exe unload hklm\$dest$software
|
||||
```
|
||||
|
||||
@ -282,7 +282,7 @@ The following sections describe common hard-link migration problems. Expand the
|
||||
|
||||
**Resolution:** Use the UsmtUtils tool to delete the store or change the store name. For example, at a command prompt, enter:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
UsmtUtils.exe /rd <storedir>
|
||||
```
|
||||
|
||||
|
||||
@ -50,7 +50,7 @@ The following example specifies that all locked files, regardless of their locat
|
||||
|
||||
Additionally, the order in the **<ErrorControl>** section implies priority. In this example, the first **<nonFatal>** tag takes precedence over the second **<fatal>** tag. This precedence is applied, regardless of how many tags are listed.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<ErrorControl>
|
||||
<fileError>
|
||||
<nonFatal errorCode="33">* [*]</nonFatal>
|
||||
@ -152,7 +152,7 @@ The **<HardLinkStoreControl>** sample code below specifies that hard links
|
||||
> [!IMPORTANT]
|
||||
> The **<ErrorControl>** section can be configured to conditionally ignore file access errors, based on the file's location.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<Policy>
|
||||
<HardLinkStoreControl>
|
||||
<fileLocked>
|
||||
|
||||
@ -37,7 +37,7 @@ If you have an **<include>** rule in one component and a **<locationMod
|
||||
|
||||
The following .xml file migrates all files from C:\\Userdocs, including .mp3 files, because the **<exclude>** rule is specified in a separate component.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/UserDocs">
|
||||
<component type="Documents" context="System">
|
||||
<displayName>User Documents</displayName>
|
||||
@ -71,7 +71,7 @@ The following .xml file migrates all files from C:\\Userdocs, including .mp3 fil
|
||||
|
||||
Specifying `migrate="no"` in the `Config.xml` file is the same as deleting the corresponding component from the migration .xml file. However, if you set `migrate="no"` for My Documents, but you have a rule similar to the one shown below in a migration .xml file (which includes all of the .doc files from My Documents), then only the .doc files will be migrated, and all other files will be excluded.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<include>
|
||||
<objectSet>
|
||||
<pattern type="File">%CSIDL_PERSONAL%\* [*.doc] </pattern>
|
||||
@ -103,7 +103,7 @@ If there are conflicting rules within a component, the most specific rule is app
|
||||
|
||||
In the following example, mp3 files won't be excluded from the migration. The mp3 files won't be excluded because directory names take precedence over the file extensions.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<include>
|
||||
<objectSet>
|
||||
<pattern type="File">C:\Data\* [*]</pattern>
|
||||
@ -181,7 +181,7 @@ The destination computer contains the following files:
|
||||
|
||||
You have a custom .xml file that contains the following code:
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<include>
|
||||
<objectSet>
|
||||
<pattern type="File">c:\data\* [*]</pattern>
|
||||
|
||||
@ -22,7 +22,7 @@ The following template is a template for the sections that you need to migrate y
|
||||
<details>
|
||||
<summary>Expand to show <b>Example 1</b> application template:</summary>
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/migtestapp">
|
||||
<component type="Application">
|
||||
<!-- Name of the application -->
|
||||
@ -161,7 +161,7 @@ The sample patterns describe the behavior in the following example .xml file.
|
||||
<details>
|
||||
<summary>Expand to show <b>Example 3</b> XML file:</summary>
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/testfilemig">
|
||||
<component type="Application" context="System">
|
||||
<displayName>File Migration Test</displayName>
|
||||
@ -203,7 +203,7 @@ The behavior for this custom .xml file is described within the `<displayName>` t
|
||||
<details>
|
||||
<summary>Expand to show <b>Example 4</b> XML file:</summary>
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
|
||||
<component type="Documents" context="System">
|
||||
|
||||
@ -47,7 +47,7 @@ To run the ScanState tool on the source computer with USMT installed:
|
||||
|
||||
2. Navigate to the USMT tools. For example, enter:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
cd /d "C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\User State Migration Tool\<architecture>"
|
||||
```
|
||||
|
||||
@ -55,13 +55,13 @@ To run the ScanState tool on the source computer with USMT installed:
|
||||
|
||||
3. Run the **ScanState** tool to generate an XML report of the space requirements. At the command prompt, enter:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
ScanState.exe <StorePath> /p:<path to a file>
|
||||
```
|
||||
|
||||
Where *<StorePath>* is a path to a directory where the migration store will be saved and *<path to a file>* is the path and filename where the XML report for space requirements will be saved. For example:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
ScanState.exe c:\store /p:c:\spaceRequirements.xml
|
||||
```
|
||||
|
||||
|
||||
@ -50,7 +50,7 @@ The migration .xml files, `MigApp.xml`, `MigDocs.xml`, and `MigUser.xml`, contai
|
||||
|
||||
The following .xml file migrates all files located on the C: drive, except any .mp3 files.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/mp3files">
|
||||
<!-- This component migrates all files except those with .mp3 extension-->
|
||||
<component type="Documents" context="UserAndSystem">
|
||||
@ -77,7 +77,7 @@ The following .xml file migrates all files located on the C: drive, except any .
|
||||
|
||||
The following .xml file migrates all files and subfolders in `C:\Data`, except the files and subfolders in `C:\Data\tmp`.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
<component type="Documents" context="System">
|
||||
<displayName _locID="miguser.sharedvideo">Test component</displayName>
|
||||
@ -103,7 +103,7 @@ The following .xml file migrates all files and subfolders in `C:\Data`, except t
|
||||
|
||||
The following .xml file migrates any subfolders in `C:\`EngineeringDrafts`, but excludes all files that are in `C:\EngineeringDrafts`.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
<component type="Documents" context="System">
|
||||
<displayName>Component to migrate all Engineering Drafts Documents without subfolders</displayName>
|
||||
@ -129,7 +129,7 @@ The following .xml file migrates any subfolders in `C:\`EngineeringDrafts`, but
|
||||
|
||||
The following .xml file migrates all files and subfolders in `C:\EngineeringDrafts`, except for the `Sample.doc` file in `C:\EngineeringDrafts`.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
<component type="Documents" context="System">
|
||||
<displayName>Component to migrate all Engineering Drafts Documents except Sample.doc</displayName>
|
||||
@ -155,13 +155,13 @@ The following .xml file migrates all files and subfolders in `C:\EngineeringDraf
|
||||
|
||||
To exclude a Sample.doc file from any location on the C: drive, use the **<pattern>** element. If multiple files exist with the same name on the C: drive, all of these files will be excluded.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<pattern type="File"> C:\* [Sample.doc] </pattern>
|
||||
```
|
||||
|
||||
To exclude a Sample.doc file from any drive on the computer, use the **<script>** element. If multiple files exist with the same name, all of these files will be excluded.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<script>MigXmlHelper.GenerateDrivePatterns("* [sample.doc]", "Fixed")</script>
|
||||
```
|
||||
|
||||
@ -173,7 +173,7 @@ Here are some examples of how to use XML to exclude files, folders, and registry
|
||||
|
||||
The following .xml file excludes all `.mp3` files from the migration:
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/excludefiles">
|
||||
<component context="System" type="Documents">
|
||||
<displayName>Test</displayName>
|
||||
@ -194,7 +194,7 @@ The following .xml file excludes all `.mp3` files from the migration:
|
||||
|
||||
The following .xml file excludes only the files located on the C: drive.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/allfiles">
|
||||
<component type="Documents" context="System">
|
||||
<displayName>Test</displayName>
|
||||
@ -215,7 +215,7 @@ The following .xml file excludes only the files located on the C: drive.
|
||||
|
||||
The following .xml file unconditionally excludes the `HKEY_CURRENT_USER` registry key and all of its subkeys.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/miguser">
|
||||
<component type="Documents" context="User">
|
||||
@ -242,7 +242,7 @@ The following .xml file unconditionally excludes the `HKEY_CURRENT_USER` registr
|
||||
|
||||
The following .xml file unconditionally excludes the system folders of `C:\Windows` and `C:\Program Files`. Note that all `*.docx`, `*.xls` and `*.ppt` files won't be migrated because the **<unconditionalExclude>** element takes precedence over the **<include>** element.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/miguser">
|
||||
<component type="Documents" context="System">
|
||||
|
||||
@ -29,7 +29,7 @@ In addition, you can specify the file patterns that you want to extract by using
|
||||
|
||||
To extract files from the compressed migration store onto the destination computer, use the following UsmtUtils syntax:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
UsmtUtils.exe /extract <filePath> <destinationPath> [/i:<includePattern>] [/e:<excludePattern>] [/l:<logfile>] [/decrypt[:<AlgID>] {/key:<keystring> | /keyfile:<filename>}] [/o]
|
||||
```
|
||||
|
||||
@ -57,7 +57,7 @@ Where the placeholders have the following values:
|
||||
|
||||
To extract everything from a compressed migration store to a file on the `C:\` drive, enter:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
UsmtUtils.exe /extract D:\MyMigrationStore\USMT\store.mig C:\ExtractedStore
|
||||
```
|
||||
|
||||
@ -65,7 +65,7 @@ UsmtUtils.exe /extract D:\MyMigrationStore\USMT\store.mig C:\ExtractedStore
|
||||
|
||||
To extract specific files, such as `.txt` and `.pdf` files, from an encrypted compressed migration store, enter:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
UsmtUtils.exe /extract D:\MyMigrationStore\USMT\store.mig /i:"*.txt,*.pdf" C:\ExtractedStore /decrypt /keyfile:D:\encryptionKey.txt
|
||||
```
|
||||
|
||||
@ -75,7 +75,7 @@ In this example, the file is encrypted and the encryption key is located in a te
|
||||
|
||||
To extract all files except for one file type, such as `.exe` files, from an encrypted compressed migration store, enter:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
UsmtUtils.exe /extract D:\MyMigrationStore\USMT\store.mig /e:*.exe C:\ExtractedStore /decrypt:AES_128 /key:password /l:C:\usmtutilslog.txt
|
||||
```
|
||||
|
||||
@ -83,7 +83,7 @@ UsmtUtils.exe /extract D:\MyMigrationStore\USMT\store.mig /e:*.exe C:\ExtractedS
|
||||
|
||||
To extract files from a compressed migration store, and to exclude files of one type (such as .exe files) while including only specific files, use both the include pattern and the exclude pattern, as in this example:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
UsmtUtils.exe /extract D:\MyMigrationStore\USMT\store.mig /i:myProject.* /e:*.exe C:\ExtractedStore /o
|
||||
```
|
||||
|
||||
|
||||
@ -55,13 +55,13 @@ You can use the XML helper functions in the [XML elements library](usmt-xml-elem
|
||||
|
||||
As with parameters with a default value convention, if you have a NULL parameter at the end of a list, you can leave it out. For example, the following function:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
SomeFunction("My String argument",NULL,NULL)
|
||||
```
|
||||
|
||||
is equivalent to:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
SomeFunction("My String argument")
|
||||
```
|
||||
|
||||
|
||||
@ -92,7 +92,7 @@ It isn't necessary to estimate the size of a hard-link migration store since har
|
||||
|
||||
Separate hard-link migration stores are created on each NTFS volume that contain data being migrated. In this scenario, the primary migration-store location will be specified on the command line, and should be the operating-system volume. Migration stores with identical names and directory names will be created on every volume containing data being migrated. For example:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
ScanState.exe /hardlink c:\USMTMIG […]
|
||||
```
|
||||
|
||||
@ -144,7 +144,7 @@ A new section in the `Config.xml` file allows optional configuration of some of
|
||||
|
||||
The following XML sample specifies that files locked by an application under the `\Users` directory can remain in place during the migration. It also specifies that locked files that aren't located in the `\Users` directory should result in the **File in Use** error. It's important to exercise caution when specifying the paths using the `<createhardlink>`** tag in order to minimize scenarios that make the hard-link migration store more difficult to delete.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<Policies>
|
||||
<HardLinkStoreControl>
|
||||
<fileLocked>
|
||||
|
||||
@ -19,7 +19,7 @@ When you specify the migration .xml files, User State Migration Tool (USMT) 10.0
|
||||
|
||||
The following .xml file migrates a single registry key.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
<component type="Application" context="System">
|
||||
<displayName>Component to migrate only registry value string</displayName>
|
||||
@ -44,7 +44,7 @@ The following examples show how to migrate a folder from a specific drive, and f
|
||||
|
||||
- **Including subfolders.** The following .xml file migrates all files and subfolders from `C:\EngineeringDrafts` to the destination computer.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
<component type="Documents" context="System">
|
||||
<displayName>Component to migrate all Engineering Drafts Documents including subfolders</displayName>
|
||||
@ -63,7 +63,7 @@ The following examples show how to migrate a folder from a specific drive, and f
|
||||
|
||||
- **Excluding subfolders.** The following .xml file migrates all files from `C:\EngineeringDrafts`, but it doesn't migrate any subfolders within `C:\EngineeringDrafts`.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
<component type="Documents" context="System">
|
||||
<displayName>Component to migrate all Engineering Drafts Documents without subfolders</displayName>
|
||||
@ -84,7 +84,7 @@ The following examples show how to migrate a folder from a specific drive, and f
|
||||
|
||||
The following .xml file migrates all files and subfolders of the `EngineeringDrafts` folder from any drive on the computer. If multiple folders exist with the same name, then all files with this name are migrated.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
<component type="Documents" context="System">
|
||||
<displayName>Component to migrate all Engineering Drafts Documents folder on any drive on the computer </displayName>
|
||||
@ -104,7 +104,7 @@ The following .xml file migrates all files and subfolders of the `EngineeringDra
|
||||
|
||||
The following .xml file migrates all files and subfolders of the `EngineeringDrafts` folder from any location on the `C:\` drive. If multiple folders exist with the same name, they're all migrated.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
<component type="Documents" context="System">
|
||||
<displayName>Component to migrate all Engineering Drafts Documents EngineeringDrafts folder from where ever it exists on the C: drive </displayName>
|
||||
@ -126,7 +126,7 @@ The following .xml file migrates all files and subfolders of the `EngineeringDra
|
||||
|
||||
The following .xml file migrates `.mp3` files located in the specified drives on the source computer into the `C:\Music` folder on the destination computer.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
<component type="Documents" context="System">
|
||||
<displayName>All .mp3 files to My Documents</displayName>
|
||||
@ -155,7 +155,7 @@ The following examples show how to migrate a file from a specific folder, and ho
|
||||
|
||||
- **To migrate a file from a folder.** The following .xml file migrates only the `Sample.doc` file from `C:\EngineeringDrafts` on the source computer to the destination computer.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
<component type="Documents" context="System">
|
||||
<displayName>Component to migrate all Engineering Drafts Documents</displayName>
|
||||
@ -174,13 +174,13 @@ The following examples show how to migrate a file from a specific folder, and ho
|
||||
|
||||
- **To migrate a file from any location.** To migrate the `Sample.doc` file from any location on the `C:\` drive, use the **<pattern>** element, as the following example shows. If multiple files exist with the same name on the `C:\` drive, all of files with this name are migrated.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<pattern type="File"> C:\* [Sample.doc] </pattern>
|
||||
```
|
||||
|
||||
To migrate the Sample.doc file from any drive on the computer, use <script> as the following example shows. If multiple files exist with the same name, all files with this name are migrated.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<script>MigXmlHelper.GenerateDrivePatterns("* [sample.doc]", "Fixed")</script>
|
||||
```
|
||||
|
||||
|
||||
@ -104,7 +104,7 @@ The following examples describe common scenarios in which you can use the diagno
|
||||
|
||||
Let's imagine that we have the following directory structure and that we want the **data** directory to be included in the migration along with the **New Text Document.txt** file in the **New Folder**. The directory of `C:\data` contains:
|
||||
|
||||
``` console
|
||||
```console
|
||||
01/21/2009 10:08 PM <DIR> .
|
||||
01/21/2009 10:08 PM <DIR> ..
|
||||
01/21/2009 10:08 PM <DIR> New Folder
|
||||
@ -115,7 +115,7 @@ Let's imagine that we have the following directory structure and that we want th
|
||||
|
||||
The directory of `C:\data\New Folder` contains:
|
||||
|
||||
``` console
|
||||
```console
|
||||
01/21/2009 10:08 PM <DIR> .
|
||||
01/21/2009 10:08 PM <DIR> ..
|
||||
01/21/2009 10:08 PM 0 New Text Document.txt
|
||||
@ -198,7 +198,7 @@ This diagnostic log confirms that the modified **<pattern>** value enables
|
||||
|
||||
In this scenario, you have the following directory structure and you want all files in the **Data** directory to migrate, except for text files. The `C:\Data` folder contains:
|
||||
|
||||
``` console
|
||||
```console
|
||||
Directory of C:\Data
|
||||
|
||||
01/21/2009 10:08 PM <DIR> .
|
||||
@ -211,7 +211,7 @@ Directory of C:\Data
|
||||
|
||||
The `C:\Data\New Folder\` contains:
|
||||
|
||||
``` console
|
||||
```console
|
||||
01/21/2009 10:08 PM <DIR> .
|
||||
01/21/2009 10:08 PM <DIR> ..
|
||||
01/21/2009 10:08 PM 0 New Text Document.txt
|
||||
|
||||
@ -34,7 +34,7 @@ Before using the **ScanState** tool for a migration that includes encrypted file
|
||||
|
||||
You can run the [Cipher.exe](/windows-server/administration/windows-commands/cipher) tool at a Windows command prompt to review and change encryption settings on files and folders. For example, to remove encryption from a folder, at a command prompt enter:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
cipher.exe /D /S:<PATH>
|
||||
```
|
||||
|
||||
|
||||
@ -23,7 +23,7 @@ Links to detailed explanations of commands are available in the [Related article
|
||||
|
||||
2. Enter the following `ScanState.exe` command line in a command prompt window:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
ScanState.exe \\server\share\migration\mystore /i:MigDocs.xml /i:MigApp.xml /o
|
||||
````
|
||||
|
||||
@ -33,13 +33,13 @@ Links to detailed explanations of commands are available in the [Related article
|
||||
|
||||
- If you're migrating domain accounts, enter:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
LoadState.exe \\server\share\migration\mystore /i:MigDocs.xml /i:MigApp.xml
|
||||
```
|
||||
|
||||
- If you're migrating local accounts along with domain accounts, enter:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
LoadState.exe \\server\share\migration\mystore /i:MigDocs.xml /i:MigApp.xml /lac /lae
|
||||
```
|
||||
|
||||
@ -54,7 +54,7 @@ Links to detailed explanations of commands are available in the [Related article
|
||||
|
||||
2. Enter the following `ScanState.exe` command line in a command prompt window:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
ScanState.exe \\server\share\migration\mystore /ue:*\* /ui:contoso\user1 /ui:fabrikam\user2 /i:MigDocs.xml /i:MigApp.xml /o
|
||||
```
|
||||
|
||||
@ -62,7 +62,7 @@ Links to detailed explanations of commands are available in the [Related article
|
||||
|
||||
4. Enter the following `LoadState.exe ` command line in a command prompt window:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
LoadState.exe \\server\share\migration\mystore /i:MigDocs.xml /i:MigApp.xml
|
||||
```
|
||||
|
||||
@ -74,7 +74,7 @@ Links to detailed explanations of commands are available in the [Related article
|
||||
|
||||
2. Enter the following `ScanState.exe` command line in a command prompt window:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
ScanState.exe \\server\share\migration\mystore /ue:*\* /ui:contoso\user1 /ui:contoso\user2 /i:MigDocs.xml /i:MigApp.xml /o
|
||||
```
|
||||
|
||||
@ -82,7 +82,7 @@ Links to detailed explanations of commands are available in the [Related article
|
||||
|
||||
4. Enter the following `LoadState.exe ` command line in a command prompt window:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
LoadState.exe \\server\share\migration\mystore /mu:contoso\user1:fabrikam\user2 /i:MigDocs.xml /i:MigApp.xml
|
||||
```
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ To reroute files and settings, create a custom .xml file and specify the .xml fi
|
||||
|
||||
The following custom .xml file migrates the directories and files from `C:\EngineeringDrafts` into the **My Documents** folder of every user. **%CSIDL_PERSONAL%** is the virtual folder representing the **My Documents** desktop item, which is equivalent to **CSIDL_MYDOCUMENTS**.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
<component type="Documents" context="User">
|
||||
<displayName>Engineering Drafts Documents to Personal Folder</displayName>
|
||||
@ -47,7 +47,7 @@ The following custom .xml file migrates the directories and files from `C:\Engin
|
||||
|
||||
The following custom .xml file reroutes .mp3 files located in the fixed drives on the source computer into the `C:\Music` folder on the destination computer.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
<component type="Documents" context="System">
|
||||
<displayName>All .mp3 files to My Documents</displayName>
|
||||
@ -74,7 +74,7 @@ The following custom .xml file reroutes .mp3 files located in the fixed drives o
|
||||
|
||||
The following custom .xml file migrates the `Sample.doc` file from `C:\EngineeringDrafts` into the **My Documents** folder of every user. **%CSIDL_PERSONAL%** is the virtual folder representing the **My Documents** desktop item, which is equivalent to **CSIDL_MYDOCUMENTS**.
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
|
||||
<component type="Documents" context="User">
|
||||
<displayName>Sample.doc into My Documents</displayName>
|
||||
|
||||
@ -43,7 +43,7 @@ The `ScanState.exe` command's syntax is:
|
||||
|
||||
For example, to create a `Config.xml` file in the current directory, use:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
ScanState.exe /i:MigApp.xml /i:MigDocs.xml /genconfig:Config.xml /v:13
|
||||
```
|
||||
|
||||
|
||||
@ -59,7 +59,7 @@ Where the placeholders have the following values:
|
||||
|
||||
To verify whether the migration store is intact or whether it contains corrupted files or a corrupted catalog, enter:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
UsmtUtils.exe /verify D:\MyMigrationStore\store.mig
|
||||
```
|
||||
|
||||
@ -69,7 +69,7 @@ Because no report type is specified, **UsmtUtils** displays the default summary
|
||||
|
||||
To verify whether the catalog file is corrupted or intact, enter:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
UsmtUtils.exe /verify:catalog D:\MyMigrationStore\store.mig
|
||||
```
|
||||
|
||||
@ -77,7 +77,7 @@ UsmtUtils.exe /verify:catalog D:\MyMigrationStore\store.mig
|
||||
|
||||
To verify whether there are any corrupted files in the compressed migration store, and to specify the name and location of the log file, enter:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
UsmtUtils.exe /verify:all D:\MyMigrationStore\store.mig /decrypt /l:D:\UsmtUtilsLog.txt`
|
||||
```
|
||||
|
||||
@ -87,7 +87,7 @@ In addition to verifying the status of all files, this example decrypts the file
|
||||
|
||||
In this example, the log file will only list the files that became corrupted during the **ScanState** process. This list will include the catalog file if it's also corrupted.
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
UsmtUtils.exe /verify:failureonly D:\MyMigrationStore\USMT\store.mig /decrypt:AES_192 /keyfile:D:\encryptionKey.txt
|
||||
```
|
||||
|
||||
|
||||
@ -17,20 +17,20 @@ When creating custom .xml files, note the following requirements:
|
||||
|
||||
- **The file must be in Unicode Transformation Format-8 (UTF-8).** Save the file in this format, and you must specify the following syntax at the beginning of each .xml file:
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
```
|
||||
|
||||
- **The file must have a unique migration URL ID**. The URL ID of each file that you specify on the command line must be different. If two migration .xml files have the same URL ID, the second .xml file that is specified on the command line won't be processed. The second file won't be processed because USMT uses the URL ID to define the components within the file. For example, you must specify the following syntax at the beginning of each file:
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/<CustomFileName>">
|
||||
```
|
||||
|
||||
- **Each component in the file must have a display name in order for it to appear in the Config.xml file.** This condition is because the `Config.xml` file defines the components by the display name and the migration URL ID. For example, specify the following syntax:
|
||||
|
||||
``` xml
|
||||
```xml
|
||||
<displayName>My Application</displayName>
|
||||
```
|
||||
|
||||
|
||||
@ -33,18 +33,31 @@ Before performing proxy activation, ensure that the network and the VAMT install
|
||||
### To perform an Active Directory forest proxy activation
|
||||
|
||||
1. Open VAMT.
|
||||
|
||||
2. In the left-side pane, select the **Active Directory-Based Activation** node.
|
||||
|
||||
3. In the right-side **Actions** pane, select **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. If you want to rename the ADBA object, you must do it now. After you select **Install Key**, the name can't 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 select **Open**. If you're activating an AD forest in an isolated workgroup, save the `.cilx` file to a removable media device.
|
||||
|
||||
7. Select **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.
|
||||
|
||||
8. 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.
|
||||
|
||||
9. In the right-side **Actions** pane, select **Acquire confirmation IDs for CILX** to open the **Acquire confirmation IDs for file** dialog box.
|
||||
|
||||
10. 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 select **Open**. VAMT displays an **Acquiring Confirmation IDs** message while it contacts Microsoft and acquires the CIDs.
|
||||
|
||||
11. 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. Select **OK** to close the message.
|
||||
|
||||
12. 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.
|
||||
|
||||
13. Open VAMT and then select the **Active Directory-Based Activation** node in the left-side pane.
|
||||
|
||||
14. In the right-side **Actions** pane, select **Apply confirmation ID to Active Directory domain**, browse to the `.cilx` file and then select **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.
|
||||
|
||||
@ -14,7 +14,11 @@ ms.collection: highpri
|
||||
|
||||
# Activate using Active Directory-based activation
|
||||
|
||||
(*Applies to: Windows, Windows Server, Office*)
|
||||
*Applies to:*
|
||||
|
||||
- Windows
|
||||
- Windows Server
|
||||
- Office
|
||||
|
||||
> [!TIP]
|
||||
> Are you looking for information on retail activation?
|
||||
|
||||
@ -14,7 +14,15 @@ ms.technology: itpro-fundamentals
|
||||
|
||||
# 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*)
|
||||
*Applies to:*
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
> [!TIP]
|
||||
> Are you looking for information on retail activation?
|
||||
@ -39,14 +47,20 @@ To enable KMS functionality, a KMS key is installed on a KMS host; then, the hos
|
||||
|
||||
### Configure KMS in Windows 10
|
||||
|
||||
To activate, use the slmgr.vbs command. Open an elevated command prompt and run one of the following commands:
|
||||
To activate, use the `slmgr.vbs` command. Open an elevated command prompt and run one of the following commands:
|
||||
|
||||
- To install the KMS key, run the command `slmgr.vbs /ipk <KmsKey>`.
|
||||
|
||||
- To activate online, run the command `slmgr.vbs /ato`.
|
||||
|
||||
- To install the KMS key, type `slmgr.vbs /ipk <KmsKey>`.
|
||||
- To activate online, type `slmgr.vbs /ato`.
|
||||
- To activate by telephone, follow these steps:
|
||||
|
||||
1. Run `slmgr.vbs /dti` and confirm the installation ID.
|
||||
|
||||
2. Call [Microsoft Licensing Activation Centers worldwide telephone numbers](https://www.microsoft.com/licensing/existing-customer/activation-centers) and follow the voice prompts to enter the installation ID that you obtained in step 1 on your telephone.
|
||||
|
||||
3. Follow the voice prompts and write down the responded 48-digit confirmation ID for OS activation.
|
||||
|
||||
4. Run `slmgr.vbs /atp \<confirmation ID\>`.
|
||||
|
||||
For more information, see the information for Windows 7 in [Deploy KMS Activation](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn502531(v=ws.11)).
|
||||
@ -58,42 +72,43 @@ Installing a KMS host key on a computer running Windows Server allows you to act
|
||||
> [!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.
|
||||
This scenario is commonly used in larger organizations that don't 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](/troubleshoot/windows-server/deployment/error-0xc004f015-activate-windows-10).
|
||||
> If you receive error 0xC004F015 when trying to activate Windows 10 Enterprise, see [Error 0xC004F015 when you activate Windows 10 Enterprise on a Windows Server 2012 R2 KMS host](/troubleshoot/windows-server/deployment/error-0xc004f015-activate-windows-10).
|
||||
|
||||
### 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).
|
||||
4. When the role installation is complete, select 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.
|
||||
5. Select the **Key Management Service (KMS)** option, and specify the computer that will act as the KMS host (Figure 6). This computer 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).
|
||||
6. Install your KMS host key by typing it in the text box, and then select **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).
|
||||
7. If asked to confirm replacement of an existing key, select **Yes**.
|
||||
8. After the product key is installed, you must activate it. Select **Next** (Figure 8).
|
||||
|
||||
|
||||
|
||||
@ -109,7 +124,7 @@ Now that the KMS host is configured, it will begin to listen for activation requ
|
||||
|
||||
## 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.
|
||||
KMS volume activation can be verified 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.
|
||||
@ -117,18 +132,20 @@ You can verify KMS volume activation from the KMS host server or from the client
|
||||
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.
|
||||
|
||||
2. On a client computer, open a Command Prompt window and run the command `Slmgr.vbs /ato`.
|
||||
|
||||
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.vbs /dlv`, and then press ENTER.
|
||||
|
||||
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.
|
||||
3. On a client computer or the KMS host, open an elevated Command Prompt window and run the command `Slmgr.vbs /dlv`.
|
||||
|
||||
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 test confirms that KMS is functioning correctly, even though the client hasn't been activated.
|
||||
|
||||
For more information about the use and syntax of slmgr.vbs, see [Slmgr.vbs Options](/windows-server/get-started/activation-slmgr-vbs-options).
|
||||
|
||||
## 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:
|
||||
If you've 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.
|
||||
|
||||
@ -14,7 +14,15 @@ ms.technology: itpro-fundamentals
|
||||
|
||||
# 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*)
|
||||
*Applies to:*
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
> [!TIP]
|
||||
> Are you looking for information on retail activation?
|
||||
|
||||
@ -14,7 +14,15 @@ ms.topic: article
|
||||
|
||||
# Appendix: Information sent to Microsoft during activation
|
||||
|
||||
(*Applies to: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2*)
|
||||
*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?**
|
||||
|
||||
|
||||
@ -99,7 +99,7 @@ There are several options for organizations to configure the WMI firewall except
|
||||
|
||||
- **Image.** Add the configurations to the master Windows image deployed to all clients.
|
||||
|
||||
- **Group Policy.** If the clients are part of a domain, then all clients can be configured using Group Policy. The Group Policy setting for the WMI firewall exception is found in GPMC.MSC at: **Computer Configuration\\Windows Settings\\Security Settings\\Windows Firewall with Advanced Security\\Windows Firewall with Advanced Security\\Inbound Rules**.
|
||||
- **Group Policy.** If the clients are part of a domain, then all clients can be configured using Group Policy. The Group Policy setting for the WMI firewall exception is found in GPMC.MSC at: **Computer Configuration** > **Windows Settings** > **Security Settings** > **Windows Firewall with Advanced Security** > **Windows Firewall with Advanced Security** > **Inbound Rules**.
|
||||
|
||||
- **Script.** Execute a script using Microsoft Configuration Manager or a third-party remote script execution facility.
|
||||
|
||||
|
||||
@ -14,7 +14,15 @@ ms.date: 11/07/2022
|
||||
|
||||
# Monitor activation
|
||||
|
||||
(*Applies to: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2*)
|
||||
*Applies to:*
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
> [!TIP]
|
||||
> Are you looking for information on retail activation?
|
||||
|
||||
@ -14,7 +14,15 @@ ms.date: 11/07/2022
|
||||
|
||||
# Plan for volume activation
|
||||
|
||||
(*Applies to: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2*)
|
||||
*Applies to:*
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
> [!TIP]
|
||||
> Are you looking for information on retail activation?
|
||||
|
||||
@ -14,7 +14,15 @@ ms.technology: itpro-fundamentals
|
||||
|
||||
# Use the Volume Activation Management Tool
|
||||
|
||||
(*Applies to: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2*)
|
||||
*Applies to:*
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
> [!TIP]
|
||||
> Are you looking for information on retail activation?
|
||||
|
||||
@ -43,7 +43,7 @@ To open PowerShell with administrative credentials, select **Start** and enter `
|
||||
|
||||
For all supported operating systems, you can use the VAMT PowerShell module included with the Windows ADK. By default, the module is installed with the Windows ADK in the VAMT folder. Change directories to the directory where VAMT is located. For example, if the Windows ADK is installed in the default location of `C:\Program Files(x86)\Windows Kits\10`, enter:
|
||||
|
||||
``` powershell
|
||||
```powershell
|
||||
cd "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\VAMT 3.0"
|
||||
```
|
||||
|
||||
@ -51,7 +51,7 @@ For all supported operating systems, you can use the VAMT PowerShell module incl
|
||||
|
||||
To import the VAMT PowerShell module, enter the following command at a PowerShell command prompt:
|
||||
|
||||
``` powershell
|
||||
```powershell
|
||||
Import-Module .\VAMT.psd1
|
||||
```
|
||||
|
||||
@ -61,13 +61,13 @@ To import the VAMT PowerShell module, enter the following command at a PowerShel
|
||||
|
||||
You can view all of the help sections for a VAMT PowerShell cmdlet, or you can view only the section that you're interested in. To view all of the Help content for a VAMT cmdlet, enter:
|
||||
|
||||
``` powershell
|
||||
```powershell
|
||||
get-help <cmdlet name> -all
|
||||
```
|
||||
|
||||
For example, enter:
|
||||
|
||||
``` powershell
|
||||
```powershell
|
||||
get-help get-VamtProduct -all
|
||||
```
|
||||
|
||||
@ -78,24 +78,24 @@ get-help get-VamtProduct -all
|
||||
|
||||
1. To get the syntax to use with a cmdlet, enter the following command at a PowerShell command prompt:
|
||||
|
||||
``` powershell
|
||||
```powershell
|
||||
get-help <cmdlet name>
|
||||
```
|
||||
|
||||
For example, enter:
|
||||
|
||||
``` powershell
|
||||
```powershell
|
||||
get-help get-VamtProduct
|
||||
```
|
||||
|
||||
2. To see examples using a cmdlet, enter:
|
||||
|
||||
``` powershell
|
||||
```powershell
|
||||
get-help <cmdlet name> -examples
|
||||
```
|
||||
|
||||
For example, enter:
|
||||
|
||||
``` powershell
|
||||
```powershell
|
||||
get-help get-VamtProduct -examples
|
||||
```
|
||||
|
||||
@ -46,13 +46,13 @@ On the KMS host computer, perform the following steps:
|
||||
|
||||
3. To extract the contents of the update, run the following command:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
expand c:\KB3058168\Windows8.1-KB3058168-x64.msu -f:* C:\KB3058168\
|
||||
```
|
||||
|
||||
4. To extract the contents of Windows8.1-KB3058168-x64.cab, run the following command:
|
||||
|
||||
``` syntax
|
||||
```cmd
|
||||
expand c:\KB3058168\Windows8.1-KB3058168-x64.cab -f:pkeyconfig-csvlk.xrm-ms c:\KB3058168
|
||||
```
|
||||
|
||||
|
||||
@ -14,7 +14,15 @@ ms.technology: itpro-fundamentals
|
||||
|
||||
# Volume Activation for Windows 10
|
||||
|
||||
(*Applies to: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2*)
|
||||
*Applies to:*
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
> [!TIP]
|
||||
> Are you looking for volume licensing information?
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Fix issues found by the Readiness assessment tool
|
||||
description: This article details how to fix issues found by the Readiness assessment tool
|
||||
ms.date: 05/30/2022
|
||||
ms.date: 11/17/2022
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: how-to
|
||||
@ -14,7 +14,9 @@ msreviewer: hathind
|
||||
|
||||
# Fix issues found by the Readiness assessment tool
|
||||
|
||||
Seeing issues with your tenant? This article details how to remediate issues found with your tenant.
|
||||
Seeing issues with your tenant? This article details how to remediate issues found with your tenant.
|
||||
|
||||
If you need more assistance with tenant enrollment, you can submit a [tenant enrollment support request](#submit-a-support-request).
|
||||
|
||||
## Check results
|
||||
|
||||
@ -70,3 +72,27 @@ Windows Autopatch requires the following licenses:
|
||||
| Result | Meaning |
|
||||
| ----- | ----- |
|
||||
| Not ready | Windows Autopatch requires Windows 10/11 Enterprise E3 (or higher) to be assigned to your users. Additionally, Azure Active Directory Premium, and Microsoft Intune are required. For more information, see [more about licenses](../prepare/windows-autopatch-prerequisites.md#more-about-licenses). |
|
||||
|
||||
## Submit a support request
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Make sure you've [added and verified your admin contacts](../deploy/windows-autopatch-admin-contacts.md). The Windows Autopatch Service Engineering Team will contact these individuals for assistance with troubleshooting issues.
|
||||
|
||||
If you need more assistance with tenant enrollment, you can submit support tickets to the Windows Autopatch Service Engineering Team in the Windows Autopatch enrollment tool. Email is the recommended approach to interact with the Windows Autopatch Service Engineering Team.
|
||||
|
||||
**To submit a new support request:**
|
||||
|
||||
1. If the Readiness assessment tool fails, remediation steps can be found by selecting **View details** under **Management settings** and then selecting the individual check. The **Contact Support** button will be available below remediation instructions in the fly-in-pane.
|
||||
2. Enter your question(s) and/or a description of the problem.
|
||||
3. Review all the information you provided for accuracy.
|
||||
4. When you're ready, select **Create**.
|
||||
|
||||
### Manage an active support request
|
||||
|
||||
The primary contact for the support request will receive email notifications when a case is created, assigned to a service engineer to investigate, and mitigated. If you have a question about the case, the best way to get in touch is to reply directly to one of the emails. If we have questions about your request or need more details, we'll email the primary contact listed in the support request.
|
||||
|
||||
**To view all your active pre-enrollment support requests:**
|
||||
|
||||
1. Sign into the [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) and navigate to the **Tenant Administration** menu.
|
||||
1. In the **Windows Autopatch** section, select **Tenant Enrollment**.
|
||||
1. Select the **Support history** tab. You can view the list of all support cases, or select an individual case to view the details.
|
||||
|
||||
@ -47,6 +47,9 @@ You'll need the following components to complete this lab:
|
||||
|**Hyper-V or a physical device running Windows 10**|The guide assumes that you'll use a Hyper-V VM, and provides instructions to install and configure Hyper-V if needed. To use a physical device, skip the steps to install and configure Hyper-V.|
|
||||
|**An account with Azure Active Directory (Azure AD) Premium license**|This guide will describe how to get a free 30-day trial Azure AD Premium subscription that can be used to complete the lab.|
|
||||
|
||||
> [!NOTE]
|
||||
> When using a VM for Autopilot testing, assign at least two processors and 4 GB of memory.
|
||||
|
||||
## Procedures
|
||||
|
||||
A summary of the sections and procedures in the lab is provided below. Follow each section in the order it's presented, skipping the sections that don't apply to you. Optional procedures are provided in the appendices.
|
||||
|
||||
Reference in New Issue
Block a user