| Parameter | +Required | +Value | +
|---|---|---|
errorCode |
+No |
+"any" or "specify system error message here" |
+
| Parameter | +Required | +Value | +
|---|---|---|
<errorCode> |
+No |
+"any" or "specify system error message here". If system error messages are not specified, the default behavior applies the parameter to all system error messages. |
+
| Parameter | +Required | +Value | +
|---|---|---|
<errorCode> |
+No |
+"any" or "specify system error message here". If system error messages are not specified, the default behavior applies the parameter to all system error messages. |
+
| Parameter | +Required | +Value | +
|---|---|---|
From |
+Yes |
+A valid local group on the source machine that contains users selected for migration on the command line. |
+
To |
+Yes |
+A local group that the users are to be moved to during the migration. |
+
appliesTo |
+Yes |
+nonmigratedUsers, migratedUsers, AllUsers. This value defines which users the change group operation should apply to. |
+
| If you have the following code in the same component | +Resulting behavior | +Explanation | +
|---|---|---|
|
+Migrates all files and subfolders in Dir1 (including all .txt files in C:). |
+The <exclude> rule does not affect the migration because the <include> rule is more specific. |
+
|
+Migrates all files and subfolders in C:\Dir1, except the .txt files in C:\Dir1\Dir2 and its subfolders. |
+Both rules are processed as intended. |
+
|
+Migrates all files and subfolders in C:\Dir1, except the .txt files in C:\Dir1 and its subfolders. |
+Both rules are processed as intended. |
+
|
+Nothing will be migrated. |
+The rules are equally specific, so the <exclude> rule takes precedence over the <include> rule. |
+
|
+Migrates the .txt files in Dir1 and the .txt files from subfolders other than Dir2. +No files are migrated from Dir2 or its subfolders. |
+Both rules are processed as intended. |
+
|
+Migrates all files and subfolders of Dir2, except the .txt files from Dir1 and any subfolders of Dir1 (including Dir2). |
+Both rules are processed as intended. |
+
| If you have the following code in different components | +Resulting behavior | +Explanation | +
|---|---|---|
Component 1: +
Component 2: +
|
+Migrates all files and subfolders of C:\Dir1\ (including C:\Dir1\Dir2). |
+Rules that are in different components do not affect each other, except for the <unconditionalExclude> rule. Therefore, in this example, although some .txt files were excluded when Component 1 was processed, they were included when Component 2 was processed. |
+
Component 1: +
Component 2: +
|
+Migrates all files and subfolders from Dir2 except the .txt files in C:\Dir1 and its subfolders. |
+Both rules are processed as intended. |
+
Component 1: +
Component 2: +
|
+Migrates all .txt files in Dir1 and any subfolders. |
+Component 1 does not contain an <include> rule, so the <exclude> rule is not processed. |
+
| If you have the following code in the same component | +Resulting behavior | +Explanation | +
|---|---|---|
|
+Migrates all keys in HKLM\Software\Microsoft\Command Processor except DefaultColor. |
+Both rules are processed as intended. |
+
|
+Migrates only DefaultColor in HKLM\Software\Microsoft\Command Processor. |
+DefaultColor is migrated because the <include> rule is more specific than the <exclude> rule. |
+
|
+Does not migrate DefaultColor. |
+The rules are equally specific, so the <exclude> rule takes precedence over the <include> rule. |
+
| If you have the following code in different components | +Resulting behavior | +Explanation | +
|---|---|---|
Component 1: +
Component 2: +
|
+Migrates all the keys/values under HKLM\Software\Microsoft\Command Processor. |
+Rules that are in different components do not affect each other, except for the <unconditionalExclude> rule. Therefore, in this example, the objects that were excluded when Component 1 was processed were included when Component 2 was processed. |
+
| If you specify the following code | +Resulting behavior | +
|---|---|
|
+During ScanState, all the files will be added to the store. +During LoadState, only C:\Data\SampleA.txt will be restored. |
+
|
+During ScanState, all the files will be added to the store. +During LoadState, all the files will be restored, overwriting the existing files on the destination computer. |
+
|
+During ScanState, all the files will be added to the store. +During LoadState, the following will occur: +
|
+
| Code | +Behavior | +
|---|---|
|
+Verifies that My Videos exists on the source computer. |
+
|
+Filters out the shortcuts in My Videos that do not resolve on the destination computer. This has no effect on files that are not shortcuts. For example, if there is a shortcut in My Videos on the source computer that points to C:\Folder1, that shortcut will be migrated only if C:\Folder1 exists on the destination computer. However, all other files, such as .mp3 files, migrate without any filtering. |
+
|
+Migrates My Videos for all users. |
+
| Code | +Behavior | +
|---|---|
|
+Migrates all instances of the file Usmttestfile.txt from all sub-directories under %ProgramFiles%\USMTTestFolder. |
+
|
+Migrates the whole directory under %ProgramFiles%\USMTDIRTestFolder. |
+
|
+Migrates all instances of MyKey under HKCU\Software\USMTTESTKEY. |
+
|
+Migrates the entire registry hive under HKLM\Software\USMTTESTKEY. |
+
| Topic | +Description | +
|---|---|
[Change history for Deploy Windows 10](change-history-for-deploy-windows-10.md) |
+This topic lists new and updated topics in the Deploy Windows 10 documentation for [Windows 10 and Windows 10 Mobile](../index.md). |
+
[Windows 10 deployment scenarios](windows-10-deployment-scenarios.md) |
+To successfully deploy the Windows 10 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the key capabilities and limitations of each, is a key task. |
+
[Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-81-with-the-microsoft-deployment-toolkit.md) |
+This guide will walk you through the process of deploying Windows 10 in an enterprise environment using the Microsoft Deployment Toolkit (MDT), and MDT 2013 Update 1 specifically. |
+
[Deploy Windows 10 with System Center 2012 R2 Configuration Manager](deploy-windows-81-with-system-center-2012-r2-configuration-manager.md) |
+If you have Microsoft System Center 2012 R2 Configuration Manager in your environment, you will most likely want to use it to deploy Windows 10. This topic will show you how to set up Configuration Manager for operating system deployment and how to integrate Configuration Manager with the Microsoft Deployment Toolkit (MDT) or, more specifically, MDT 2013 Update 1. |
+
[Upgrade to Windows 10 with the Microsoft Deployment Toolkit](upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md) |
+The simplest path to upgrade PCs that are currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. You can use a Microsoft Deployment Toolkit (MDT) 2013 Update 1 task sequence to completely automate the process. |
+
[Upgrade to Windows 10 with System Center Configuration Manager](upgrade-to-windows-10-with-system-center-configuraton-manager.md) |
+The simplest path to upgrade PCs currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. You can use a System Center Configuration Manager task sequence to completely automate the process. |
+
[Windows 10 edition upgrade](windows-10-edition-upgrades.md) |
+With Windows 10, you can quickly upgrade from one edition of Windows 10 to another, provided the upgrade path is supported. |
+
[Deploy Windows To Go in your organization](deploy-windows-to-go-in-your-organization-small-scenario.md) |
+This topic helps you to deploy Windows To Go in your organization. Before you begin deployment, make sure that you have reviewed the topics [Windows To Go: feature overview](../plan/windows-to-go-feature-overview-scenario.md) and [Prepare your organization for Windows To Go](../plan/prepare-your-organization-for-windows-to-go.md) to ensure that you have the correct hardware and are prepared to complete the deployment. You can then use the steps in this topic to start your Windows To Go deployment. |
+
[Update Windows 10 images with provisioning packages](update-windows-10-images-with-provisioning-packages.md) |
+Use a provisioning package to apply settings, profiles, and file assets to a Windows 10 image. |
+
[Sideload apps in Windows 10](sideload-apps-in-windows-10.md) |
+Sideload line-of-business apps in Windows 10. |
+
[Volume Activation [client]](volume-activation-for-windows-81-client.md) |
+This guide is designed to help organizations that are planning to use volume activation to deploy and activate Windows 10, including organizations that have used volume activation for earlier versions of Windows. |
+
[Windows 10 deployment tools reference](windows-10-deployment-tools-reference.md) |
+Learn about the tools available to deploy Windows 10. |
+
[Identify Users](identify-users-usmt-win7-usmt-win8.md) |
+Use command-line options to specify which users to migrate and how they should be migrated. |
+
[Identify Applications Settings](identify-applications-settings-usmt-win7-usmt-win8.md) |
+Determine which applications you want to migrate and prepare a list of application settings to be migrated. |
+
[Identify Operating System Settings](identify-operating-system-settings-usmt-win7-usmt-win8.md) |
+Use migration to create a new standard environment on each of the destination computers. |
+
[Identify File Types, Files, and Folders](identify-file-types-files-and-folders-usmt-win8.md) |
+Determine and locate the standard, company-specified, and non-standard locations of the file types, files, folders, and settings that you want to migrate. |
+
<Policies> |
+This element contains elements that describe the policies that USMT follows while creating a migration store. |
+
<HardLinkStoreControl> |
+This element contains elements that describe how to handle files during the creation of a hard link migration store. |
+
<fileLocked> |
+This element contains elements that describe how to handle files that are locked for editing. |
+
<createHardLink> |
+This element defines a standard MigXML pattern that describes file paths where hard links should be created, even if the file is locked for editing by another application. +Syntax: <createHardLink> [pattern] </createHardLink> |
+
<errorHardLink> |
+This element defines a standard MigXML pattern that describes file paths where hard links should not be created, if the file is locked for editing by another application. +<errorHardLink> [pattern] </errorHardLink> |
+
[VAMT Requirements](vamt-requirements-vamt-30-win8.md) |
+Provides system requirements for installing VAMT on a host computer. |
+
[Install VAMT](install-vamt-vamt-30-win8.md) |
+Describes how to get and install VAMT. |
+
[Configure Client Computers](configure-client-computers-vamt-30-win8.md) |
+Describes how to configure client computers on your network to work with VAMT. |
+
| Command-Line Option | +Description | +
|---|---|
StorePath |
+Indicates the folder where the files and settings data are stored. You must specify StorePath when using the LoadState command. You cannot specify more than one StorePath. |
+
/decrypt /key:KeyString +or +/decrypt /key:"Key String" +or +/decrypt /keyfile:[Path\]FileName |
+Decrypts the store with the specified key. With this option, you will need to specify the encryption key in one of the following ways: +
KeyString cannot exceed 256 characters. +The /key and /keyfile options cannot be used on the same command line. +The /decrypt and /nocompress options cannot be used on the same command line. +
+Important
+
+Use caution with this option, because anyone who has access to the LoadState command-line script will also have access to the encryption key. +
+
+
+For example: +
|
+
/decrypt:"encryption strength" |
+The /decrypt option accepts a command-line parameter to define the encryption strength specified for the migration store encryption. For more information about supported encryption algorithms, see [Migration Store Encryption](migration-store-encryption-usmt-win8.md). |
+
/hardlink |
+Enables user-state data to be restored from a hard-link migration store. The /nocompress parameter must be specified with /hardlink option. |
+
/nocompress |
+Specifies that the store is not compressed. You should only use this option in testing environments. We recommend that you use a compressed store during your actual migration. This option cannot be used with the /decrypt option. +For example: +
|
+
| Command-Line Option | +Description | +
|---|---|
/i:[Path\]FileName |
+(include) +Specifies an .xml file that contains rules that define what state to migrate. You can specify this option multiple times to include all of your .xml files (MigApp.xml, MigSys.xml, MigDocs.xml and any custom .xml files that you create). Path can be either a relative or full path. If you do not specify the Path variable, then FileName must be located in the current directory. +For more information about which files to specify, see the "XML files" section of the [Frequently Asked Questions](frequently-asked-questions-usmt-win7-usmt-win8.md) topic. |
+
/config:[Path\]FileName |
+Specifies the Config.xml file that the LoadState command should use. You cannot specify this option more than once on the command line. Path can be either a relative or full path. If you do not specify the Path variable, then the FileName must be located in the current directory. +This example migrates the files and settings based on the rules in the Config.xml, MigDocs.xml, and MigApp.xml files: +
|
+
/auto:"path to script files" |
+This option enables you to specify the location of the default .xml files and then launch your migration. If no path is specified, USMT will use the directory where the USMT binaries are located. The /auto option has the same effect as using the following options: /i:MigDocs.xml /i:MigApp.xml /v:5. |
+
| Command-Line Option | +Description | +||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
/l:[Path\]FileName |
+Specifies the location and name of the LoadState log. You cannot store any of the log files in StorePath. Path can be either a relative or full path. If you do not specify the Path variable, then the log will be created in the current directory. You can specify the /v option to adjust the amount of output. +If you run the LoadState command from a shared network resource, you must specify this option or USMT will fail with the error: "USMT was unable to create the log file(s)". To fix this issue, use the /l:load.log option. |
+||||||||||||||||||
/v:<VerbosityLevel> |
+(Verbosity) +Enables verbose output in the LoadState log file. The default value is 0. +You can set the VerbosityLevel to one of the following levels: +
+ For example: +
|
+||||||||||||||||||
/progress:[Path\]FileName |
+Creates the optional progress log. You cannot store any of the log files in StorePath. Path can be either a relative or full path. If you do not specify the Path variable, then FileName will be created in the current directory. +For example: +
|
+||||||||||||||||||
/c |
+When this option is specified, the LoadState command will continue to run, even if non-fatal errors occur. Any files or settings that cause an error are logged in the progress log. For example, if there is a large file that will not fit on the computer, the LoadState command will log an error and continue with the migration. Without the /c option, the LoadState command will exit on the first error. You can use the new <ErrorControl> section in the Config.xml file to specify which file or registry read/write errors can be safely ignored and which might cause the migration to fail. This enables the /c command-line option to safely skip all input/output (I/O) errors in your environment. In addition, the /genconfig option now generates a sample <ErrorControl> section that is enabled by specifying error messages and desired behaviors in the Config.xml file. |
+||||||||||||||||||
/r:<TimesToRetry> |
+(Retry) +Specifies the number of times to retry when an error occurs while migrating the user state from a server. The default is three times. This option is useful in environments where network connectivity is not reliable. +While restoring the user state, the /r option will not recover data that is lost due to a network-hardware failure, such as a faulty or disconnected network cable, or when a virtual private network (VPN) connection fails. The retry option is intended for large, busy networks where connectivity is satisfactory, but communication latency is a problem. |
+||||||||||||||||||
/w:<SecondsBeforeRetry> |
+(Wait) +Specifies the time to wait, in seconds, before retrying a network file operation. The default is 1 second. |
+||||||||||||||||||
/? or /help |
+Displays Help on the command line. |
+
| Command-Line Option | +Description | +
|---|---|
/all |
+Migrates all of the users on the computer. +USMT migrates all user accounts on the computer, unless you specifically exclude an account with the /ue or /uel options. For this reason, you do not need to specify this option on the command line. However, if you choose to use the /all option, you cannot also use the /ui, /ue or /uel options. |
+
/ui:DomainName\UserName +or +/ui:"DomainName\User Name" +or +/ui:ComputerName\LocalUserName |
+(User include) +Migrates the specified user. By default, all users are included in the migration. Therefore, this option is helpful only when used with the /ue option. You can specify multiple /ui options, but you cannot use the /ui option with the /all option. DomainName and UserName can contain the asterisk (*) wildcard character. When you specify a user name that contains spaces, you will need to surround it with quotations marks. +For example: +
+Note
+
+If a user is specified for inclusion with the /ui option, and also is specified to be excluded with either the /ue or /uel options, the user will be included in the migration. +
+
+
+For more examples, see the descriptions of the /uel, /ue, and /ui options in this table. |
+
/uel:<NumberOfDays> +or +/uel:<YYYY/MM/DD> +or +/uel:0 |
+(User exclude based on last logon) +Migrates only the users that logged onto the source computer within the specified time period, based on the Last Modified date of the Ntuser.dat file on the source computer. The /uel option acts as an include rule. For example, the /uel:30 option migrates users who logged on, or whose user account was modified, within the last 30 days from the date when the ScanState command is run. You can specify a number of days or you can specify a date. You cannot use this option with the /all option. USMT retrieves the last logon information from the local computer, so the computer does not need to be connected to the network when you run this option. In addition, if a domain user has logged onto another computer, that logon instance is not considered by USMT. +
+Note
+
+The /uel option is not valid in offline migrations. +
+
+
+Examples: +
For example: +
|
+
/ue:DomainName\UserName +or +/ue:"DomainName\User Name" +or +/ue:ComputerName\LocalUserName |
+(User exclude) +Excludes the specified users from the migration. You can specify multiple /ue options but you cannot use the /ue option with the /all option. DomainName and UserName can contain the asterisk (*) wildcard character. When you specify a user name that contains spaces, you will need to surround it with quotation marks. +For example: +
For more examples, see the descriptions of the /uel, /ue, and /ui options in this table. |
+
/md:OldDomain:NewDomain +or +/md:LocalComputerName:NewDomain |
+(move domain) +Specifies a new domain for the user. Use this option to change the domain for users on a computer or to migrate a local user to a domain account. OldDomain may contain the asterisk (*) wildcard character. +You can specify this option more than once. You may want to specify multiple /md options if you are consolidating users across multiple domains to a single domain. For example, you could specify the following to consolidate the users from the Corporate and FarNorth domains into the Fabrikam domain: If there are conflicts between two /md commands, the first rule that you specify is applied. For example, if you specify the
+Note
+
+If you specify an OldDomain that did not exist on the source computer, the LoadState command will appear to complete successfully, without an error or warning. However, in this case, users will not be moved to NewDomain but will remain in their original domain. For example, if you misspell "contoso" and you specify "/md:contso:fabrikam", the users will remain in contoso on the destination computer. +
+
+
+For example: +
|
+
/mu:OldDomain\OldUserName:[NewDomain\]NewUserName +or +/mu:OldLocalUserName:NewDomain\NewUserName |
+Specifies a new user name for the specified user. If the store contains more than one user, you can specify multiple /mu options. You cannot use wildcard characters with this option. +For example: +
|
+
/lac:[Password] |
+(local account create) +Specifies that if a user account is a local (non-domain) account, and it does not exist on the destination computer, USMT will create the account on the destination computer but it will be disabled. To enable the account, you must also use the /lae option. +If the /lac option is not specified, any local user accounts that do not already exist on the destination computer will not be migrated. +Password is the password for the newly created account. An empty password is used by default. +
+Caution
+
+Use the Password variable with caution because it is provided in plain text and can be obtained by anyone with access to the computer that is running the LoadState command. +Also, if the computer has multiple users, all migrated users will have the same password. +
+
+
+For example: +
For instructions, see [Migrate User Accounts](migrate-user-accounts-usmt.md). |
+
/lae |
+(local account enable) +Enables the account that was created with the /lac option. You must specify the /lac option with this option. +For example: +
For instructions, see [Migrate User Accounts](migrate-user-accounts-usmt.md). |
+
| Behavior | +Command | +
|---|---|
Exclude the user named User One in the Corporate domain. |
+
|
+
Exclude the user named User1 in the Corporate domain. |
+
|
+
Exclude the local user named User1. |
+
|
+
Exclude all domain users. |
+
|
+
Exclude all local users. |
+
|
+
Exclude users in all domains named User1, User2, and so on. |
+
|
+
| Behavior | +Command | +
|---|---|
Include only User2 from the Fabrikam domain and exclude all other users. |
+
|
+
Include only the local user named User1 and exclude all other users. |
+
|
+
Include only the domain users from Contoso, except Contoso\User1. |
+This behavior cannot be completed using a single command. Instead, to migrate this set of users, you will need to specify the following: +
|
+
Include only local (non-domain) users. |
+
|
+
| Command-Line Option | +/keyfile | +/nocompress | +/genconfig | +/all | +
|---|---|---|---|---|
/i |
++ | + | + | + |
/v |
++ | + | + | + |
/nocompress |
++ | N/A |
+X |
++ |
/key |
+X |
++ | X |
++ |
/decrypt |
+Required* |
+X |
+X |
++ |
/keyfile |
+N/A |
++ | X |
++ |
/l |
++ | + | + | + |
/progress |
++ | + | X |
++ |
/r |
++ | + | X |
++ |
/w |
++ | + | X |
++ |
/c |
++ | + | X |
++ |
/p |
++ | + | X |
+N/A |
+
/all |
++ | + | X |
++ |
/ui |
++ | + | X |
+X |
+
/ue |
++ | + | X |
+X |
+
/uel |
++ | + | X |
+X |
+
/genconfig |
++ | + | N/A |
++ |
/config |
++ | + | X |
++ |
StorePath |
++ | + | + | + |
/md |
++ | + | + | + |
/mu |
++ | + | + | + |
/lae |
++ | + | + | + |
/lac |
++ | + | + | + |
| Command line Option | +File Name | +Description | +
|---|---|---|
/l[Path\]FileName |
+Scanstate.log or LoadState.log |
+Specifies the path and file name of the ScanState.log or LoadState log. |
+
/progress[Path\]FileName |
+Specifies the path and file name of the Progress log. |
+Provides information about the status of the migration, by percentage complete. |
+
/v[VerbosityLevel] |
+Not applicable |
+See the "Monitoring Options" section in [ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md). |
+
/listfiles[Path\]FileName |
+Specifies the path and file name of the Listfiles log. |
+Provides a list of the files that were migrated. |
+
Set the environment variable MIG_ENABLE_DIAG to a path to an XML file. |
+USMTDiag.xml |
+The diagnostic log contains detailed system environment information, user environment information, and information about the migration units (migunits) being gathered and their contents. |
+
| Key | +Value | +
|---|---|
program |
+ScanState.exe or LoadState.exe. |
+
productVersion |
+The full product version number of USMT. |
+
computerName |
+The name of the source or destination computer on which USMT was run. |
+
commandLine |
+The full command used to run USMT. |
+
PHASE |
+Reports that a new phase in the migration is starting. This can be one of the following: +
|
+
detectedUser |
+
|
+
includedInMigration |
+Defines whether the user profile/component is included for migration. Valid values are Yes or No. |
+
forUser |
+Specifies either of the following: +
|
+
detectedComponent |
+Specifies a component detected by USMT. +
|
+
totalSizeInMBToTransfer |
+Total size of the files and settings to migrate in megabytes (MB). |
+
totalPercentageCompleted |
+Total percentage of the migration that has been completed by either ScanState or LoadState. |
+
collectingUser |
+Specifies which user ScanState is collecting files and settings for. |
+
totalMinutesRemaining |
+Time estimate, in minutes, for the migration to complete. |
+
error |
+Type of non-fatal error that occurred. This can be one of the following: +
|
+
objectName |
+The name of the file or setting that caused the non-fatal error. |
+
action |
+Action taken by USMT for the non-fatal error. The values are: +
|
+
errorCode |
+The errorCode or return value. |
+
numberOfIgnoredErrors |
+The total number of non-fatal errors that USMT ignored. |
+
message |
+The message corresponding to the errorCode. |
+
[Perform Online Activation](perform-online-activation-vamt-30-win8.md) |
+Describes how to activate a client computer over the Internet. |
+
[Perform Proxy Activation](perform-proxy-activation-vamt-30-win8.md) |
+Describes how to perform volume activation for client products that do not have Internet access. |
+
[Perform KMS Activation](perform-kms-activation-vamt-30-win8.md) |
+Describes how perform volume activation using the Key Management Service (KMS). |
+
[Perform Local Reactivation](perform-local-reactivation-vamt-30-win8.md) |
+Describes how to reactivate an operating system or Office program that was reinstalled. |
+
[Activate an Active Directory Forest Online](activate-an-active-directory-forest-online.md) |
+Describes how to use Active Directory-Based Activation to online activate an Active Directory forest. |
+
[Activate by Proxy an Active Directory Forest](activate-by-proxy-an-active-directory-forest.md) |
+Describes how to use Active Directory-Based Activation to proxy activate an Active Directory forest that is not connected to the Internet. |
+
[Add and Remove a Product Key](add-and-remove-a-product-key-vamt-30-win8.md) |
+Describes how to add a product key to the VAMT database. |
+
[Install a Product Key](install-a-product-key-vamt-30-win8.md) |
+Describes how to install a product key for specific product. |
+
[Install a KMS Client Key](install-a-kms-client-key-vamt-30-win8.md) |
+Describes how to install a GVLK (KMS client) key. |
+
[Import and Export VAMT Data](import-and-export-vamt-data-vamt-30-win8.md) |
+Describes how to import and export VAMT data. |
+
[Use VAMT in Windows PowerShell](use-vamt-in-windows-powershell.md) |
+Describes how to access Windows PowerShell and how to import the VAMT PowerShell module. |
+
| Component | +Option | +Description | +
|---|---|---|
ScanState |
+/encrypt<AES, AES_128, AES_192, AES_256, 3DES, 3DES_112> |
+This option and argument specify that the migration store is encrypted and which algorithm to use. When the algorithm argument is not provided, the ScanState tool employs the 3DES algorithm. |
+
LoadState |
+/decrypt<AES, AES_128, AES_192, AES_256, 3DES, 3DES_112> |
+This option and argument specify that the store must be decrypted and which algorithm to use. When the algorithm argument is not provided, the LoadState tool employs the 3DES algorithm. |
+
| Running Operating System | +Offline Operating System | +
|---|---|
WinPE 5.0 or greater, with the MSXML library |
+Windows Vista, Windows 7, Windows 8, Windows 10 |
+
Windows 7, Windows 8, Windows 10 |
+Windows.old directory |
+
| Component | +Option | +Description | +
|---|---|---|
ScanState.exe |
+/offline:<path to offline.xml> |
+This command-line option enables the offline-migration mode and requires a path to an Offline.xml configuration file. |
+
ScanState.exe |
+/offlineWinDir:<Windows directory> |
+This command-line option enables the offline-migration mode and starts the migration from the location specified. It is only for use in WinPE offline scenarios where the migration is occurring from a Windows directory. |
+
ScanState.exe |
+/OfflineWinOld:<Windows.old directory> |
+This command-line option enables the offline migration mode and starts the migration from the location specified. It is only intended to be used in Windows.old migration scenarios, where the migration is occurring from a Windows.old directory. |
+
| Variable | +Value | +Scenario | +
|---|---|---|
USMT_WORKING_DIR |
+Full path to a working directory |
+Required when USMT binaries are located on read-only media, which does not support the creation of log files or temporary storage. To set the system environment variable, at a command prompt type the following: + |
+
MIG_OFFLINE_PLATFORM_ARCH |
+32 or 64 |
+While operating offline, this environment variable defines the architecture of the offline system, if the system does not match the WinPE and Scanstate.exe architecture. This environment variable enables the 32-bit ScanState application to gather data from a computer with 64-bit architecture, or the 64-bit ScanState application to gather data from a computer with 32-bit architecture. This is required when auto-detection of the offline architecture doesn’t function properly, for example, when the source system is running a 64-bit version of Windows XP. For example, to set this system environment variable for a 32-bit architecture, at a command prompt type the following: + |
+
| Criterion | +Activation method | +Number of computers | +
|---|---|---|
Number of domain-joined computers that support Active Directory-based activation (computers running Windows 10, Windows 8.1, Windows 8, Windows Server 2012 R2, or Windows Server 2012 R2) and will connect to a domain controller at least every 180 days. Computers can be mobile, semi-isolated, or located in a branch office or the core network. |
+Active Directory-based activation |
++ |
Number of computers in the core network that will connect (directly or through a VPN) at least every 180 days +Note: The core network must meet the KMS activation threshold. |
+KMS (central) |
++ |
Number of computers that do not connect to the network at least once every 180 days (or if no network meets the activation threshold) |
+MAM |
++ |
Number of computers in semi-isolated networks that have connectivity to the KMS in the core network |
+KMS (central) |
++ |
Number of computers in isolated networks where the KMS activation threshold is met |
+KMS (local) |
++ |
Number of computers in isolated networks where the KMS activation threshold is not met |
+MAK |
++ |
Number of computers in test and development labs that will not be activated |
+None |
++ |
Number of computers that do not have a retail volume license |
+Retail (online or phone) |
++ |
Number of computers that do not have an OEM volume license |
+OEM (at factory) |
++ |
Total number of computer activations +Note: This total should match the total number of licensed computers in your organization. |
++ | + |
[Common Migration Scenarios](common-migration-scenarios-usmt-win7-usmt-win8.md) |
+Determine whether you will perform a refresh migration or a replace migration. |
+
[What Does USMT Migrate?](what-does-usmt-migrate-usmt-win7-usmt-win8.md) |
+Learn which applications, user data, and operating system components USMT migrates. |
+
[Choose a Migration Store Type](choose-a-migration-store-type-usmt-win7-usmt-win8.md) |
+Choose an uncompressed, compressed, or hard-link migration store. |
+
[Determine What to Migrate](determine-what-to-migrate-usmt-win7-usmt-win8.md) |
+Identify user accounts, application settings, operating system settings, and files that you want to migrate inside your organization. |
+
[Test Your Migration](test-your-migration-usmt-win7-usmt-win8.md) |
+Test your migration before you deploy Windows to all users. |
+
| Variable | +Explanation | +
|---|---|
ALLUSERSAPPDATA |
+Same as CSIDL_COMMON_APPDATA. |
+
ALLUSERSPROFILE |
+Refers to %PROFILESFOLDER%\Public or %PROFILESFOLDER%\all users. |
+
COMMONPROGRAMFILES |
+Same as CSIDL_PROGRAM_FILES_COMMON. |
+
COMMONPROGRAMFILES(X86) |
+Refers to the C:\Program Files (x86)\Common Files folder on 64-bit systems. |
+
CSIDL_COMMON_ADMINTOOLS |
+Version 10.0. The file-system directory that contains administrative tools for all users of the computer. |
+
CSIDL_COMMON_ALTSTARTUP |
+The file-system directory that corresponds to the non-localized Startup program group for all users. |
+
CSIDL_COMMON_APPDATA |
+The file-system directory that contains application data for all users. A typical path Windows is C:\ProgramData. |
+
CSIDL_COMMON_DESKTOPDIRECTORY |
+The file-system directory that contains files and folders that appear on the desktop for all users. A typical Windows® XP path is C:\Documents and Settings\All Users\Desktop. A typical path is C:\Users\Public\Desktop. |
+
CSIDL_COMMON_DOCUMENTS |
+The file-system directory that contains documents that are common to all users. A typical path in Windows XP is C:\Documents and Settings\All Users\Documents. A typical path is C:\Users\Public\Documents. |
+
CSIDL_COMMON_FAVORITES |
+The file-system directory that serves as a common repository for favorites common to all users. A typical path is C:\Users\Public\Favorites. |
+
CSIDL_COMMON_MUSIC |
+The file-system directory that serves as a repository for music files common to all users. A typical path is C:\Users\Public\Music. |
+
CSIDL_COMMON_PICTURES |
+The file-system directory that serves as a repository for image files common to all users. A typical path is C:\Users\Public\Pictures. |
+
CSIDL_COMMON_PROGRAMS |
+The file-system directory that contains the directories for the common program groups that appear on the Start menu for all users. A typical path is C:\ProgramData\Microsoft\Windows\Start Menu\Programs. |
+
CSIDL_COMMON_STARTMENU |
+The file-system directory that contains the programs and folders which appear on the Start menu for all users. A typical path in Windows is C:\ProgramData\Microsoft\Windows\Start Menu. |
+
CSIDL_COMMON_STARTUP |
+The file-system directory that contains the programs that appear in the Startup folder for all users. A typical path in Windows XP is C:\Documents and Settings\All Users\Start Menu\Programs\Startup. A typical path is C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup. |
+
CSIDL_COMMON_TEMPLATES |
+The file-system directory that contains the templates that are available to all users. A typical path is C:\ProgramData\Microsoft\Windows\Templates. |
+
CSIDL_COMMON_VIDEO |
+The file-system directory that serves as a repository for video files common to all users. A typical path is C:\Users\Public\Videos. |
+
CSIDL_DEFAULT_APPDATA |
+Refers to the Appdata folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_LOCAL_APPDATA |
+Refers to the local Appdata folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_COOKIES |
+Refers to the Cookies folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_CONTACTS |
+Refers to the Contacts folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_DESKTOP |
+Refers to the Desktop folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_DOWNLOADS |
+Refers to the Downloads folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_FAVORITES |
+Refers to the Favorites folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_HISTORY |
+Refers to the History folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_INTERNET_CACHE |
+Refers to the Internet Cache folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_PERSONAL |
+Refers to the Personal folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_MYDOCUMENTS |
+Refers to the My Documents folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_MYPICTURES |
+Refers to the My Pictures folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_MYMUSIC |
+Refers to the My Music folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_MYVIDEO |
+Refers to the My Videos folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_RECENT |
+Refers to the Recent folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_SENDTO |
+Refers to the Send To folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_STARTMENU |
+Refers to the Start Menu folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_PROGRAMS |
+Refers to the Programs folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_STARTUP |
+Refers to the Startup folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_TEMPLATES |
+Refers to the Templates folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_DEFAULT_QUICKLAUNCH |
+Refers to the Quick Launch folder inside %DEFAULTUSERPROFILE%. |
+
CSIDL_FONTS |
+A virtual folder containing fonts. A typical path is C:\Windows\Fonts. |
+
CSIDL_PROGRAM_FILESX86 |
+The Program Files folder on 64-bit systems. A typical path is C:\Program Files(86). |
+
CSIDL_PROGRAM_FILES_COMMONX86 |
+A folder for components that are shared across applications on 64-bit systems. A typical path is C:\Program Files(86)\Common. |
+
CSIDL_PROGRAM_FILES |
+The Program Files folder. A typical path is C:\Program Files. |
+
CSIDL_PROGRAM_FILES_COMMON |
+A folder for components that are shared across applications. A typical path is C:\Program Files\Common. |
+
CSIDL_RESOURCES |
+The file-system directory that contains resource data. A typical path is C:\Windows\Resources. |
+
CSIDL_SYSTEM |
+The Windows System folder. A typical path is C:\Windows\System32. |
+
CSIDL_WINDOWS |
+The Windows directory or system root. This corresponds to the %WINDIR% or %SYSTEMROOT% environment variables. A typical path is C:\Windows. |
+
DEFAULTUSERPROFILE |
+Refers to the value in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList [DefaultUserProfile]. |
+
PROFILESFOLDER |
+Refers to the value in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList [ProfilesDirectory]. |
+
PROGRAMFILES |
+Same as CSIDL_PROGRAM_FILES. |
+
PROGRAMFILES(X86) |
+Refers to the C:\Program Files (x86) folder on 64-bit systems. |
+
SYSTEM |
+Refers to %WINDIR%\system32. |
+
SYSTEM16 |
+Refers to %WINDIR%\system. |
+
SYSTEM32 |
+Refers to %WINDIR%\system32. |
+
SYSTEMPROFILE |
+Refers to the value in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-18 [ProfileImagePath]. |
+
SYSTEMROOT |
+Refers to the root of the system drive. |
+
WINDIR |
+Refers to the Windows folder located on the system drive. |
+
| Variable | +Explanation | +
|---|---|
APPDATA |
+Same as CSIDL_APPDATA. |
+
CSIDL_ADMINTOOLS |
+The file-system directory that is used to store administrative tools for an individual user. The Microsoft® Management Console (MMC) saves customized consoles to this directory, which roams with the user profile. |
+
CSIDL_ALTSTARTUP |
+The file-system directory that corresponds to the user's non-localized Startup program group. |
+
CSIDL_APPDATA |
+The file-system directory that serves as a common repository for application-specific data. A typical path is C:\Documents and Settings\username\Application Data or C:\Users\username\AppData\Roaming. |
+
CSIDL_BITBUCKET |
+The virtual folder that contains the objects in the user's Recycle Bin. |
+
CSIDL_CDBURN_AREA |
+The file-system directory acting as a staging area for files waiting to be written to CD. A typical path is C:\Users\username\AppData\Local\Microsoft\Windows\MasteredBurning\Disc Burning. |
+
CSIDL_CONNECTIONS |
+The virtual folder representing Network Connections that contains network and dial-up connections. |
+
CSIDL_CONTACTS |
+This refers to the Contacts folder in %CSIDL_PROFILE%. |
+
CSIDL_CONTROLS |
+The virtual folder that contains icons for the Control Panel items. |
+
CSIDL_COOKIES |
+The file-system directory that serves as a common repository for Internet cookies. A typical path is C:\Users\username\AppData\Roaming\Microsoft\Windows\Cookies. |
+
CSIDL_DESKTOP |
+The virtual folder representing the Windows desktop. |
+
CSIDL_DESKTOPDIRECTORY |
+The file-system directory used to physically store file objects on the desktop, which should not be confused with the desktop folder itself. A typical path is C:\Users\username\Desktop. |
+
CSIDL_DRIVES |
+The virtual folder representing My Computer that contains everything on the local computer: storage devices, printers, and Control Panel. The folder may also contain mapped network drives. |
+
CSIDL_FAVORITES |
+The file-system directory that serves as a common repository for the user's favorites. A typical path is C:\Users\Username\Favorites. |
+
CSIDL_HISTORY |
+The file-system directory that serves as a common repository for Internet history items. |
+
CSIDL_INTERNET |
+A virtual folder for Internet Explorer. |
+
CSIDL_INTERNET_CACHE |
+The file-system directory that serves as a common repository for temporary Internet files. A typical path is C:\Users\username\AppData\Local\Microsoft\Windows\Temporary Internet Files |
+
CSIDL_LOCAL_APPDATA |
+The file-system directory that serves as a data repository for local, non-roaming applications. A typical path is C:\Users\username\AppData\Local. |
+
CSIDL_MYDOCUMENTS |
+The virtual folder representing My Documents.A typical path is C:\Users\Username\Documents. |
+
CSIDL_MYMUSIC |
+The file-system directory that serves as a common repository for music files. A typical path is C:\Users\Username\Music. |
+
CSIDL_MYPICTURES |
+The file-system directory that serves as a common repository for image files. A typical path is C:\Users\Username\Pictures. |
+
CSIDL_MYVIDEO |
+The file-system directory that serves as a common repository for video files. A typical path is C:\Users\Username\Videos. |
+
CSIDL_NETHOOD |
+A file-system directory that contains the link objects that may exist in the My Network Places virtual folder. It is not the same as CSIDL_NETWORK, which represents the network namespace root. A typical path is C:\Users\Username\AppData\Roaming\Microsoft\Windows\Network Shortcuts. |
+
CSIDL_NETWORK |
+A virtual folder representing My Network Places, the root of the network namespace hierarchy. |
+
CSIDL_PERSONAL |
+The virtual folder representing the My Documents desktop item. This is equivalent to CSIDL_MYDOCUMENTS. +A typical path is C:\Documents and Settings\username\My Documents. |
+
CSIDL_PLAYLISTS |
+The virtual folder used to store play albums, typically C:\Users\username\My Music\Playlists. |
+
CSIDL_PRINTERS |
+The virtual folder that contains installed printers. |
+
CSIDL_PRINTHOOD |
+The file-system directory that contains the link objects that can exist in the Printers virtual folder. A typical path is C:\Users\username\AppData\Roaming\Microsoft\Windows\Printer Shortcuts. |
+
CSIDL_PROFILE |
+The user's profile folder. A typical path is C:\Users\Username. |
+
CSIDL_PROGRAMS |
+The file-system directory that contains the user's program groups, which are themselves file-system directories. A typical path is C:\Users\Username\AppData\Roaming\Microsoft\Windows\Start Menu\Programs. |
+
CSIDL_RECENT |
+The file-system directory that contains shortcuts to the user's most recently used documents. A typical path is C:\Users\Username\AppData\Roaming\Microsoft\Windows\Recent. |
+
CSIDL_SENDTO |
+The file-system directory that contains Send To menu items. A typical path is C:\Users\username\AppData\Roaming\Microsoft\Windows\SendTo. |
+
CSIDL_STARTMENU |
+The file-system directory that contains Start menu items. A typical path in Windows XP is C:\Documents and Settings\username\Start Menu. A typical path in Windows Vista, Windows 7, or Windows 8 is C:\Users\Username\AppData\Roaming\Microsoft\Windows\Start Menu. |
+
CSIDL_STARTUP |
+The file-system directory that corresponds to the user's Startup program group. A typical path is C:\Users\Username\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup. |
+
CSIDL_TEMPLATES |
+The file-system directory that serves as a common repository for document templates. A typical path is C:\Users\username\AppData\Roaming\Microsoft\Windows\Templates. |
+
HOMEPATH |
+Same as the standard environment variable. |
+
TEMP |
+The temporary folder on the computer. A typical path is %USERPROFILE%\AppData\Local\Temp. |
+
TMP |
+The temporary folder on the computer. A typical path is %USERPROFILE%\AppData\Local\Temp. |
+
USERPROFILE |
+Same as CSIDL_PROFILE. |
+
USERSID |
+Represents the current user-account security identifier (SID). For example, +S-1-5-21-1714567821-1326601894-715345443-1026. |
+
| Return code value | +Return code | +Error message | +Troubleshooting, mitigation, workarounds | +Category | +
|---|---|---|---|---|
0 |
+USMT_SUCCESS |
+Successful run |
+Not applicable |
+Success or Cancel |
+
1 |
+USMT_DISPLAY_HELP |
+Command line help requested |
+Not applicable |
+Success or Cancel |
+
2 |
+USMT_STATUS_CANCELED |
+Gather was aborted because of an EFS file |
+Not applicable |
++ |
| + | + | User chose to cancel (such as pressing CTRL+C) |
+Not applicable |
+Success or Cancel |
+
3 |
+USMT_WOULD_HAVE_FAILED |
+At least one error was skipped as a result of /c |
+Review ScanState, LoadState, or UsmtUtils log for details about command-line errors. |
++ |
11 |
+USMT_INVALID_PARAMETERS |
+/all conflicts with /ui, /ue or /uel |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | /auto expects an optional parameter for the script folder |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | /encrypt can't be used with /nocompress |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | /encrypt requires /key or /keyfile |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | /genconfig can't be used with most other options |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | /genmigxml can't be used with most other options |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | /hardlink requires /nocompress |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | /key and /keyfile both specified |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | /key or /keyfile used without enabling encryption |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | /lae is only used with /lac |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | /listfiles cannot be used with /p |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | /offline requires a valid path to an XML file describing offline paths |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | /offlinewindir requires a valid path to offline windows folder |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | /offlinewinold requires a valid path to offline windows folder |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | A command was already specified |
+Verify that the command-line syntax is correct and that there are no duplicate commands. |
++ |
| + | + | An option argument is missing |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | An option is specified more than once and is ambiguous |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | By default /auto selects all users and uses the highest log verbosity level. Switches like /all, /ui, /ue, /v are not allowed. |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | Command line arguments are required. Specify /? for options. |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | Command line option is not valid |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | EFS parameter specified is not valid for /efs |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | File argument is invalid for /genconfig |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | File argument is invalid for /genmigxml |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | Invalid space estimate path. Check the parameters and/or file system permissions |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | List file path argument is invalid for /listfiles |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | Retry argument must be an integer |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | Settings store argument specified is invalid |
+Review ScanState log or LoadState log for details about command-line errors. Make sure that the store path is accessible and that the proper permission levels are set. |
++ |
| + | + | Specified encryption algorithm is not supported |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | The /efs:hardlink requires /hardlink |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | The /targetWindows7 option is only available for Windows XP, Windows Vista, and Windows 7 |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | The store parameter is required but not specified |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | The source-to-target domain mapping is invalid for /md |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | The source-to-target user account mapping is invalid for /mu |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | Undefined or incomplete command line option |
+Review ScanState log or LoadState log for details about command-line errors. |
+Invalid Command Lines |
+
| + | + | Use /nocompress, or provide an XML file path with /p"pathtoafile" to get a compressed store size estimate |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | User exclusion argument is invalid |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | Verbosity level must be specified as a sum of the desired log options: Verbose (0x01), Record Objects (0x04), Echo to debug port (0x08) |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | Volume shadow copy feature is not supported with a hardlink store |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
| + | + | Wait delay argument must be an integer |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
12 |
+USMT_ERROR_OPTION_PARAM_TOO_LARGE |
+Command line arguments cannot exceed 256 characters |
+Review ScanState log or LoadState log for details about command-line errors. |
+Invalid Command Lines |
+
| + | + | Specified settings store path exceeds the maximum allowed length of 256 characters |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
13 |
+USMT_INIT_LOGFILE_FAILED |
+Log path argument is invalid for /l |
+When /l is specified in the ScanState command line, USMT validates the path. Verify that the drive and other information, for example file system characters, are correct. |
+Invalid Command Lines |
+
14 |
+USMT_ERROR_USE_LAC |
+Unable to create a local account because /lac was not specified |
+When creating local accounts, the command-line options /lac and /lae should be used. |
+Invalid Command Lines |
+
26 |
+USMT_INIT_ERROR |
+Multiple Windows installations found |
+Listfiles.txt could not be created. Verify that the location you specified for the creation of this file is valid. |
+Setup and Initialization |
+
| + | + | Software malfunction or unknown exception |
+Check all loaded .xml files for errors, common error when using /I to load the Config.xml file. |
++ |
| + | + | Unable to find a valid Windows directory to proceed with requested offline operation; Check if offline input file is present and has valid entries |
+Verify that the offline input file is present and that it has valid entries. USMT could not find valid offline operating system. Verify your offline directory mapping. |
++ |
27 |
+USMT_INVALID_STORE_LOCATION |
+A store path can't be used because an existing store exists; specify /o to overwrite |
+Specify /o to overwrite an existing intermediate or migration store. |
+Setup and Initialization |
+
| + | + | A store path is missing or has incomplete data |
+Make sure that the store path is accessible and that the proper permission levels are set. |
++ |
| + | + | An error occurred during store creation |
+Make sure that the store path is accessible and that the proper permission levels are set. Specify /o to overwrite an existing intermediate or migration store. |
++ |
| + | + | An inappropriate device such as a floppy disk was specified for the store |
+Make sure that the store path is accessible and that the proper permission levels are set. |
++ |
| + | + | Invalid store path; check the store parameter and/or file system permissions |
+Invalid store path; check the store parameter and/or file system permissions |
++ |
| + | + | The file layout and/or file content is not recognized as a valid store |
+Make sure that the store path is accessible and that the proper permission levels are set. Specify /o to overwrite an existing intermediate or migration store. |
++ |
| + | + | The store path holds a store incompatible with the current USMT version |
+Make sure that the store path is accessible and that the proper permission levels are set. |
++ |
| + | + | The store save location is read-only or does not support a requested storage option |
+Make sure that the store path is accessible and that the proper permission levels are set. |
++ |
28 |
+USMT_UNABLE_GET_SCRIPTFILES |
+Script file is invalid for /i |
+Check all specified migration .xml files for errors. This is a common error when using /i to load the Config.xml file. |
+Setup and Initialization |
+
| + | + | Unable to find a script file specified by /i |
+Verify the location of your script files, and ensure that the command-line options are correct. |
++ |
29 |
+USMT_FAILED_MIGSTARTUP |
+A minimum of 250 MB of free space is required for temporary files |
+Verify that the system meets the minimum temporary disk space requirement of 250 MB. As a workaround, you can set the environment variable USMT_WORKING_DIR=<path> to redirect the temporary files working directory. |
+Setup and Initialization |
+
| + | + | Another process is preventing migration; only one migration tool can run at a time |
+Check the ScanState log file for migration .xml file errors. |
++ |
| + | + | Failed to start main processing, look in log for system errors or check the installation |
+Check the ScanState log file for migration .xml file errors. |
++ |
| + | + | Migration failed because of an XML error; look in the log for specific details |
+Check the ScanState log file for migration .xml file errors. |
++ |
| + | + | Unable to automatically map the drive letters to match the online drive letter layout; Use /offline to provide a mapping table |
+Check the ScanState log file for migration .xml file errors. |
++ |
31 |
+USMT_UNABLE_FINDMIGUNITS |
+An error occurred during the discover phase; the log should have more specific information |
+Check the ScanState log file for migration .xml file errors. |
+Setup and Initialization |
+
32 |
+USMT_FAILED_SETMIGRATIONTYPE |
+An error occurred processing the migration system |
+Check the ScanState log file for migration .xml file errors, or use online Help by typing /? on the command line. |
+Setup and Initialization |
+
33 |
+USMT_UNABLE_READKEY |
+Error accessing the file specified by the /keyfile parameter |
+Check the ScanState log file for migration .xml file errors, or use online Help by typing /? on the command line. |
+Setup and Initialization |
+
| + | + | The encryption key must have at least one character |
+Check the ScanState log file for migration .xml file errors, or use online Help by typing /? on the command line. |
++ |
34 |
+USMT_ERROR_INSUFFICIENT_RIGHTS |
+Directory removal requires elevated privileges |
+Log on as Administrator, and run with elevated privileges. |
+Setup and Initialization |
+
| + | + | No rights to create user profiles; log in as Administrator; run with elevated privileges |
+Log on as Administrator, and run with elevated privileges. |
++ |
| + | + | No rights to read or delete user profiles; log in as Administrator, run with elevated privileges |
+Log on as Administrator, and run with elevated privileges. |
++ |
35 |
+USMT_UNABLE_DELETE_STORE |
+A reboot is required to remove the store |
+Reboot to delete any files that could not be deleted when the command was executed. |
+Setup and Initialization |
+
| + | + | A store path can't be used because it contains data that could not be overwritten |
+A migration store could not be deleted. If you are using a hardlink migration store you might have a locked file in it. You should manually delete the store, or use USMTUtils /rd command to delete the store. |
++ |
| + | + | There was an error removing the store |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
36 |
+USMT_ERROR_UNSUPPORTED_PLATFORM |
+Compliance check failure; please check the logs for details |
+Investigate whether there is an active temporary profile on the system. |
+Setup and Initialization |
+
| + | + | Use of /offline is not supported during apply |
+The /offline command was not used while running in the Windows Preinstallation Environment (WinPE). |
++ |
| + | + | Use /offline to run gather on this platform |
+The /offline command was not used while running in WinPE. |
++ |
37 |
+USMT_ERROR_NO_INVALID_KEY |
+The store holds encrypted data but the correct encryption key was not provided |
+Verify that you have included the correct encryption /key or /keyfile. |
+Setup and Initialization |
+
38 |
+USMT_ERROR_CORRUPTED_NOTENCRYPTED_STORE |
+An error occurred during store access |
+Review ScanState log or LoadState log for details about command-line errors. Make sure that the store path is accessible and that the proper permission levels are set. |
+Setup and Initialization |
+
39 |
+USMT_UNABLE_TO_READ_CONFIG_FILE |
+Error reading Config.xml |
+Review ScanState log or LoadState log for details about command-line errors in the Config.xml file. |
+Setup and Initialization |
+
| + | + | File argument is invalid for /config |
+Check the command line you used to load the Config.xml file. You can use online Help by typing /? on the command line. |
++ |
40 |
+USMT_ERROR_UNABLE_CREATE_PROGRESS_LOG |
+Error writing to the progress log |
+The Progress log could not be created. Verify that the location is valid and that you have write access. |
+Setup and Initialization |
+
| + | + | Progress log argument is invalid for /progress |
+The Progress log could not be created. Verify that the location is valid and that you have write access. |
++ |
41 |
+USMT_PREFLIGHT_FILE_CREATION_FAILED |
+Can't overwrite existing file |
+The Progress log could not be created. Verify that the location is valid and that you have write access. |
+Setup and Initialization |
+
| + | + | Invalid space estimate path. Check the parameters and/or file system permissions |
+Review ScanState log or LoadState log for details about command-line errors. |
++ |
42 |
+USMT_ERROR_CORRUPTED_STORE |
+The store contains one or more corrupted files |
+Review UsmtUtils log for details about the corrupted files. For information on how to extract the files that are not corrupted, see [Extract Files from a Compressed USMT Migration Store](extract-files-from-a-compressed-usmt-migration-store.md). |
++ |
61 |
+USMT_MIGRATION_STOPPED_NONFATAL |
+Processing stopped due to an I/O error |
+USMT exited but can continue with the /c command-line option, with the optional configurable <ErrorControl> section or by using the /vsc command-line option. |
+Non-fatal Errors |
+
71 |
+USMT_INIT_OPERATING_ENVIRONMENT_FAILED |
+A Windows Win32 API error occurred |
+Data transfer has begun, and there was an error during the creation of migration store or during the apply phase. Review the ScanState log or LoadState log for details. |
+Fatal Errors |
+
| + | + | An error occurred when attempting to initialize the diagnostic mechanisms such as the log |
+Data transfer has begun, and there was an error during the creation of migration store or during the apply phase. Review the ScanState log or LoadState log for details. |
++ |
| + | + | Failed to record diagnostic information |
+Data transfer has begun, and there was an error during the creation of migration store or during the apply phase. Review the ScanState log or LoadState log for details. |
++ |
| + | + | Unable to start. Make sure you are running USMT with elevated privileges |
+Exit USMT and log in again with elevated privileges. |
++ |
72 |
+USMT_UNABLE_DOMIGRATION |
+An error occurred closing the store |
+Data transfer has begun, and there was an error during migration-store creation or during the apply phase. Review the ScanState log or LoadState log for details. |
+Fatal Errors |
+
| + | + | An error occurred in the apply process |
+Data transfer has begun, and there was an error during migration-store creation or during the apply phase. Review the ScanState log or LoadState log for details. |
++ |
| + | + | An error occurred in the gather process |
+Data transfer has begun, and there was an error during migration-store creation or during the apply phase. Review the ScanState log or LoadState log for details. |
++ |
| + | + | Out of disk space while writing the store |
+Data transfer has begun, and there was an error during migration-store creation or during the apply phase. Review the ScanState log or LoadState log for details. |
++ |
| + | + | Out of temporary disk space on the local system |
+Data transfer has begun, and there was an error during migration-store creation or during the apply phase. Review the ScanState log or LoadState log for details. |
++ |
| Command-Line Option | +Description | +
|---|---|
StorePath |
+Indicates a folder where files and settings will be saved. Note that StorePath cannot be c:\. You must specify the StorePath option in the ScanState command, except when using the /genconfig option. You cannot specify more than one StorePath location. |
+
/o |
+Required to overwrite any existing data in the migration store or Config.xml file. If not specified, the ScanState command will fail if the migration store already contains data. You cannot use this option more than once on a command line. |
+
/vsc |
+This option enables the volume shadow-copy service to migrate files that are locked or in use. This command-line option eliminates most file-locking errors that are typically encountered by the <ErrorControl> section. +This option can be used only with the ScanState executable file and cannot be combined with the /hardlink option. |
+
/hardlink |
+Enables the creation of a hard-link migration store at the specified location. The /nocompress option must be specified with the /hardlink option. |
+
/encrypt [{/key:<KeyString> | /keyfile:<file>]} |
+Encrypts the store with the specified key. Encryption is disabled by default. With this option, you will need to specify the encryption key in one of the following ways: +
We recommend that KeyString be at least eight characters long, but it cannot exceed 256 characters. The /key and /keyfile options cannot be used on the same command line. The /encrypt and /nocompress options cannot be used on the same command line. +
+Important
+
+You should use caution with this option, because anyone who has access to the ScanState command-line script will also have access to the encryption key. +
+
+
+The following example shows the ScanState command and the /key option: +
|
+
/encrypt:<EncryptionStrength> |
+The /encrypt option accepts a command-line parameter to define the encryption strength to be used for encryption of the migration store. For more information about supported encryption algorithms, see [Migration Store Encryption](migration-store-encryption-usmt-win8.md). |
+
/nocompress |
+Disables compression of data and saves the files to a hidden folder named "File" at StorePath\USMT. Compression is enabled by default. Combining the /nocompress option with the /hardlink option generates a hard-link migration store. You can use the uncompressed store to view what USMT stored, troubleshoot a problem, or run an antivirus utility against the files. You should use this option only in testing environments, because we recommend that you use a compressed store during your actual migration, unless you are combining the /nocompress option with the /hardlink option. +The /nocompress and /encrypt options cannot be used together in one statement on the command line. However, if you do choose to migrate an uncompressed store, the LoadState command will migrate each file directly from the store to the correct location on the destination computer without a temporary location. +For example: +
|
+
| Command-Line Option | +Definition | +
|---|---|
/offline:"path to an offline.xml file" |
+This option is used to define a path to an offline .xml file that might specify other offline migration options, for example, an offline Windows directory or any domain or folder redirection required in your migration. |
+
/offlinewindir:"path to a Windows directory" |
+This option specifies the offline Windows directory that the ScanState command gathers user state from. The offline directory can be Windows.old when you run the ScanState command in Windows or a Windows directory when you run the ScanState command in WinPE. |
+
/offlinewinold:"Windows.old directory" |
+This command-line option enables the offline migration mode and starts the migration from the location specified. It is only intended to be used in Windows.old migration scenarios, where the migration is occurring from a Windows.old directory. |
+
| Command-Line Option | +Description | +||||||||
|---|---|---|---|---|---|---|---|---|---|
/i:[Path\]FileName |
+(include) +Specifies an .xml file that contains rules that define what user, application or system state to migrate. You can specify this option multiple times to include all of your .xml files (MigApp.xml, MigDocs.xml, and any custom .xml files that you create). Path can be either a relative or full path. If you do not specify the Path variable, then FileName must be located in the current directory. For more information about which files to specify, see the "XML Files" section of the [Frequently Asked Questions](frequently-asked-questions-usmt-win7-usmt-win8.md) topic. |
+||||||||
/genconfig:[Path\]FileName |
+(Generate Config.xml) +Generates the optional Config.xml file, but does not create a migration store. To ensure that this file contains every component, application and setting that can be migrated, you should create this file on a source computer that contains all the components, applications and settings that will be present on the destination computers. In addition, you should specify the other migration .xml files, using the /i option, when you specify this option. +After you create this file, you will need to make use of it with the ScanState command using the /config option. +The only options that you can specify with this option are the /i, /v, and /l options. You cannot specify StorePath, because the /genconfig option does not create a store. Path can be either a relative or full path. If you do not specify the Path variable, then FileName will be created in the current directory. +Examples: +
|
+||||||||
/config:[Path\]FileName |
+Specifies the Config.xml file that the ScanState command should use to create the store. You cannot use this option more than once on the command line. Path can be either a relative or full path. If you do not specify the Path variable, then FileName must be located in the current directory. +The following example creates a store using the Config.xml file, MigDocs.xml, and MigApp.xml files: +
The following example migrates the files and settings to the destination computer using the Config.xml, MigDocs.xml, and MigApp.xml files: +
|
+||||||||
/auto:path to script files |
+This option enables you to specify the location of the default .xml files and then begin the migration. If no path is specified, USMT will reference the directory where the USMT binaries are located. The /auto option has the same effect as using the following options: /i:MigDocs.xml /i:MigApp.xml /v:5. |
+||||||||
/genmigxml:path to a file |
+This option specifies that the ScanState command should use the document finder to create and export an .xml file that defines how to migrate all of the files on the computer on which the ScanState command is running. |
+||||||||
/targetwindows8 |
+Optimizes Scanstate.exe when using USMT 10.0 to migrate a user state to Windows 8 or Windows 8.1 instead of Windows 10. You should use this command line option in the following scenarios: +
|
+||||||||
/targetwindows7 |
+Optimizes Scanstate.exe when using USMT 10.0 to migrate a user state to Windows 7 instead of Windows 10. You should use this command line option in the following scenarios: +
|
+||||||||
/localonly |
+Migrates only files that are stored on the local computer, regardless of the rules in the .xml files that you specify on the command line. You should use this option when you want to exclude the data from removable drives on the source computer, such as USB flash drives (UFDs), some external hard drives, and so on, and when there are network drives mapped on the source computer. If the /localonly option is not specified, then the ScanState command will copy files from these removable or network drives into the store. +Anything that is not considered a fixed drive by the OS will be excluded by /localonly. In some cases large external hard drives are considered fixed drives. These drives can be explicitly excluded from migration by using a custom.xml file. For more information about how to exclude all files on a specific drive, see [Exclude Files and Settings](exclude-files-and-settings-usmt.md). +The /localonly command-line option includes or excludes data in the migration as identified in the following table: +
|
+
| Command-Line Option | +Description | +||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
/listfiles:<FileName> |
+You can use the /listfiles command-line option with the ScanState command to generate a text file that lists all of the files included in the migration. |
+||||||||||||||||||
/l:[Path\]FileName |
+Specifies the location and name of the ScanState log. +You cannot store any of the log files in StorePath. Path can be either a relative or full path. If you do not specify the Path variable, then the log will be created in the current directory. You can use the /v option to adjust the amount of output. +If you run the ScanState or LoadState commands from a shared network resource, you must specify this option or USMT will fail with the following error: "USMT was unable to create the log file(s)". To fix this issue, use the /l:scan.log command. |
+||||||||||||||||||
/v:<VerbosityLevel> |
+(Verbosity) +Enables verbose output in the ScanState log file. The default value is 0. +You can set the VerbosityLevel to one of the following levels: +
+ For example: +
|
+||||||||||||||||||
/progress:[Path\]FileName |
+Creates the optional progress log. You cannot store any of the log files in StorePath. Path can be either a relative or full path. If you do not specify the Path variable, then FileName will be created in the current directory. +For example: +
|
+||||||||||||||||||
/c |
+When this option is specified, the ScanState command will continue to run, even if non-fatal errors occur. Any files or settings that cause an error are logged in the progress log. For example, if there is a large file that will not fit in the store, the ScanState command will log an error and continue with the migration. In addition, if a file is open or in use by an application, USMT may not be able to migrate the file and will log an error. Without the /c option, the ScanState command will exit on the first error. +You can use the new <ErrorControl> section in the Config.xml file to specify which file or registry read/write errors can be safely ignored and which might cause the migration to fail. This enables the /c command-line option to safely skip all input/output (I/O) errors in your environment. In addition, the /genconfig option now generates a sample <ErrorControl> section that is enabled by specifying error messages and desired behaviors in the Config.xml file. |
+||||||||||||||||||
/r:<TimesToRetry> |
+(Retry) +Specifies the number of times to retry when an error occurs while saving the user state to a server. The default is three times. This option is useful in environments where network connectivity is not reliable. +While storing the user state, the /r option will not be able to recover data that is lost due to a network-hardware failure, such as a faulty or disconnected network cable, or when a virtual private network (VPN) connection fails. The retry option is intended for large, busy networks where connectivity is satisfactory, but communication latency is a problem. |
+||||||||||||||||||
/w:<SecondsBeforeRetry> |
+(Wait) +Specifies the time to wait, in seconds, before retrying a network file operation. The default is 1 second. |
+||||||||||||||||||
/p:<pathToFile> |
+When the ScanState command runs, it will create an .xml file in the path specified. This .xml file includes improved space estimations for the migration store. The following example shows how to create this .xml file: +
For more information, see [Estimate Migration Store Size](estimate-migration-store-size-usmt-win7-usmt-win8.md). +To preserve the functionality of existing applications or scripts that require the previous behavior of USMT, you can use the /p option, without specifying "pathtoafile", in USMT. If you specify only the /p option, the storage space estimations are created in the same manner as with USMT3.x releases. |
+||||||||||||||||||
/? or /help |
+Displays Help at the command line. |
+
| Command-Line Option | +Description | +
|---|---|
/all |
+Migrates all of the users on the computer. +USMT migrates all user accounts on the computer, unless you specifically exclude an account with either the /ue or /uel options. For this reason, you do not need to specify this option on the command line. However, if you choose to specify the /all option, you cannot also use the /ui, /ue or /uel options. |
+
/ui:<DomainName>\<UserName> +or +/ui:<ComputerName>\<LocalUserName> |
+(User include) +Migrates the specified users. By default, all users are included in the migration. Therefore, this option is helpful only when used with the /ue or /uel options. You can specify multiple /ui options, but you cannot use the /ui option with the /all option. DomainName and UserName can contain the asterisk (*) wildcard character. When you specify a user name that contains spaces, you will need to surround it with quotation marks. +
+Note
+
+If a user is specified for inclusion with the /ui option, and also is specified to be excluded with either the /ue or /uel options, the user will be included in the migration. +
+
+
+For example: +
For more examples, see the descriptions of the /ue and /ui options in this table. |
+
/uel:<NumberOfDays> +or +/uel:<YYYY/MM/DD> +or +/uel:0 |
+(User exclude based on last logon) +Migrates the users that logged onto the source computer within the specified time period, based on the Last Modified date of the Ntuser.dat file on the source computer. The /uel option acts as an include rule. For example, the /uel:30 option migrates users who logged on, or whose account was modified, within the last 30 days from the date when the ScanState command is run. +You can specify a number of days or you can specify a date. You cannot use this option with the /all option. USMT retrieves the last logon information from the local computer, so the computer does not need to be connected to the network when you run this option. In addition, if a domain user has logged onto another computer, that logon instance is not considered by USMT. +
+Note
+
+The /uel option is not valid in offline migrations. +
+
+
+
For example: +
|
+
/ue:<DomainName>\<UserName> +-or- + +/ue:<ComputerName>\<LocalUserName> |
+(User exclude) +Excludes the specified users from the migration. You can specify multiple /ue options. You cannot use this option with the /all option. <DomainName> and <UserName> can contain the asterisk (*) wildcard character. When you specify a user name that contains spaces, you need to surround it with quotation marks. +For example: +
|
+
| Behavior | +Command | +
|---|---|
Exclude the user named User One in the Fabrikam domain. |
+
|
+
Exclude the user named User1 in the Fabrikam domain. |
+
|
+
Exclude the local user named User1. |
+
|
+
Exclude all domain users. |
+
|
+
Exclude all local users. |
+
|
+
Exclude users in all domains named User1, User2, and so on. |
+
|
+
| Behavior | +Command | +
|---|---|
Include only User2 from the Fabrikam domain and exclude all other users. |
+
|
+
Include only the local user named User1 and exclude all other users. |
+
|
+
Include only the domain users from Contoso, except Contoso\User1. |
+This behavior cannot be completed using a single command. Instead, to migrate this set of users, you will need to specify the following: +
|
+
Include only local (non-domain) users. |
+
|
+
| Command-Line Option | +Explanation | +
|---|---|
/efs:hardlink |
+Creates a hard link to the EFS file instead of copying it. Use only with the /hardlink and the /nocompress options. |
+
/efs:abort |
+Causes the ScanState command to fail with an error code, if an Encrypting File System (EFS) file is found on the source computer. Enabled by default. |
+
/efs:skip |
+Causes the ScanState command to ignore EFS files. |
+
/efs:decryptcopy |
+Causes the ScanState command to decrypt the file, if possible, before saving it to the migration store, and to fail if the file cannot be decrypted. If the ScanState command succeeds, the file will be unencrypted in the migration store, and once you run the LoadState command, the file will be copied to the destination computer. |
+
/efs:copyraw |
+Causes the ScanState command to copy the files in the encrypted format. The files will be inaccessible on the destination computer until the EFS certificates are migrated. EFS certificates will be automatically migrated; however, by default USMT fails if an encrypted file is found, unless you specify an /efs option. Therefore you should specify the /efs:copyraw option with the ScanState command to migrate the encrypted file. Then, when you run the LoadState command, the encrypted file and the EFS certificate will be automatically migrated. +For example: +
+Important
+
+All files must be encrypted if the parent folder is encrypted. If the encryption attribute on a file inside an encrypted folder has been removed, the file will be encrypted during the migration using the credentials of the account used to run the LoadState tool. For more information, see [Migrate EFS Files and Certificates](migrate-efs-files-and-certificates-umst.md). +
+
+ |
+
| Command-Line Option | +/keyfile | +/nocompress | +/genconfig | +/all | +
|---|---|---|---|---|
/i |
++ | + | + | + |
/o |
++ | + | + | + |
/v |
++ | + | + | + |
/nocompress |
++ | + | X |
+N/A |
+
/localonly |
++ | + | X |
++ |
/key |
+X |
++ | X |
++ |
/encrypt |
+Required* |
+X |
+X |
++ |
/keyfile |
+N/A |
++ | X |
++ |
/l |
++ | + | + | + |
/progress |
++ | + | X |
++ |
/r |
++ | + | X |
++ |
/w |
++ | + | X |
++ |
/c |
++ | + | X |
++ |
/p |
++ | + | X |
+N/A |
+
/all |
++ | + | X |
++ |
/ui |
++ | + | X |
+X |
+
/ue |
++ | + | X |
+X |
+
/uel |
++ | + | X |
+X |
+
/efs:<option> |
++ | + | X |
++ |
/genconfig |
++ | + | N/A |
++ |
/config |
++ | + | X |
++ |
<StorePath> |
++ | + | X |
++ |
| XML migration file | +Modifies the following components: | +
|---|---|
Config.xml file |
+Operating-system components such as desktop wallpaper and background theme. +You can also overload config.xml to include some application and document settings by generating the config.xml file with the other default XML files. For more information, see [Customize USMT XML Files](customize-usmt-xml-files-usmt-win7-usmt-win8.md) and [Config.xml File](configxml-file-usmt-win7-usmt-win8.md). |
+
MigApps.xml file |
+Applications settings. |
+
MigUser.xml or MigDocs.xml files |
+User files and profile settings. |
+
Custom XML files |
+Application settings, user profile settings, or user files, beyond the rules contained in the other XML files. |
+
| Setting | +Value | +Default Value | +
|---|---|---|
ScanProgramFiles |
+The ScanProgramFiles argument is valid only when the GenerateDocPatterns function is called in a system context. This argument determines whether or not to scan the Program Files directory to gather registered file name extensions for known applications. +For example, when set to TRUE, the function discovers and migrates .doc files under the Microsoft Office directory, because .doc is a file name extension registered to a Microsoft Office application. The GenerateDocPatterns function generates this inclusion pattern for .doc files: +If a child folder of an included folder contains an installed application, ScanProgramFiles will also create an exclusion rule for the child folder. All folders under the application folder will be scanned recursively for registered file name extensions. |
+False |
+
IncludePatterns |
+The IncludePatterns argument determines whether to generate exclude or include patterns in the XML. When this argument is set to TRUE, the GenerateDocPatterns function generates include patterns and the function must be added under the <include> element. Changing this argument to FALSE generates exclude patterns and the function must be added under the <exclude> element. |
+True |
+
SystemDrive |
+The SystemDrive argument determines whether to generate patterns for all fixed drives or only for the system drive. Changing this argument to TRUE restricts all patterns to the system drive. |
+False |
+
Rule 1 |
+ |
+
Rule 2 |
+ |
+
[ScanState Syntax](scanstate-syntax-usmt-win7-usmt-win8.md) |
+Lists the command-line options for using the ScanState tool. |
+
[LoadState Syntax](loadstate-syntax-usmt-win7-usmt-win8.md) |
+Lists the command-line options for using the LoadState tool. |
+
[UsmtUtils Syntax](usmtutils-syntax-usmt-win8.md) |
+Lists the command-line options for using the UsmtUtils tool. |
+
[Exclude Files and Settings](exclude-files-and-settings-usmt.md) |
+Create a custom .xml file to exclude files, file types, folders, or registry settings from your migration. |
+
[Extract Files from a Compressed USMT Migration Store](extract-files-from-a-compressed-usmt-migration-store.md) |
+Recover files from a compressed migration store after installing the operating system. |
+
[Include Files and Settings](include-files-and-settings-usmt.md) |
+Create a custom .xml file to include files, file types, folders, or registry settings in your migration. |
+
[Migrate Application Settings](migrate-application-settings.md) |
+Migrate the settings of an application that the MigApp.xml file does not include by default. |
+
[Migrate EFS Files and Certificates](migrate-efs-files-and-certificates-umst.md) |
+Migrate Encrypting File System (EFS) certificates by using USMT. |
+
[Migrate User Accounts](migrate-user-accounts-usmt.md) |
+Specify the users to include and exclude in your migration. |
+
[Reroute Files and Settings](reroute-files-and-settings-usmt.md) |
+Create a custom .xml file to reroute files and settings during a migration. |
+
[Verify the Condition of a Compressed Migration Store](verify-the-condition-of-a-compressed-migration-store.md) |
+Determine whether a compressed migration store is intact, or whether it contains corrupt files or a corrupt catalog. |
+
[User State Migration Tool (USMT) Overview](user-state-migration-tool--usmt--overview.md) |
+Describes the benefits and limitations of using USMT. |
+
[Getting Started with the User State Migration Tool (USMT)](getting-started-with-the-user-state-migration-tool--usmt-.md) |
+Describes the general process to follow to migrate files and settings, and provides links to more information. |
+
[Windows Upgrade and Migration Considerations](windows-upgrade-and-migration-considerations-win8.md) |
+Discusses the Microsoft® tools you can use to move files and settings between installations, as well as special considerations for performing an upgrade or migration. |
+
[User State Migration Tool (USMT) Overview Topics](user-state-migration-tool--usmt--overview-topics.md) |
+Describes what’s new in USMT, how to get started with USMT, and the benefits and limitations of using USMT. |
+
[User State Migration Tool (USMT) How-to topics](user-state-migration-tool--usmt--how-to-topics.md) |
+Includes step-by-step instructions for using USMT, as well as how-to topics for conducting tasks in USMT. |
+
[User State Migration Tool (USMT) Troubleshooting](user-state-migration-tool--usmt--troubleshooting.md) |
+Provides answers to frequently asked questions and common issues in USMT, as well as a reference for return codes used in USMT. |
+
[User State Migration Toolkit (USMT) Reference](user-state-migration-toolkit--usmt--reference.md) |
+Includes reference information for migration planning, migration best practices, command-line syntax, using XML, and requirements for using USMT. |
+
[Common Issues](common-issues-usmt-win8.md) |
+Find troubleshooting solutions for common problems in USMT. |
+
[Frequently Asked Questions](frequently-asked-questions-usmt-win7-usmt-win8.md) |
+Find answers to questions about how to use USMT. |
+
[Log Files](log-files-usmt-win7-usmt-win8.md) |
+Learn how to enable logging to help you troubleshoot issues in USMT. |
+
[Return Codes](return-codes-usmt-win8.md) |
+Learn how to use return codes to identify problems in USMT. |
+
[USMT Resources](usmt-resources-usmt-win8.md) |
+Find more information and support for using USMT. |
+
[USMT Requirements](usmt-requirements-usmt-win7-usmt-win8.md) |
+Describes operating system, hardware, and software requirements, and user prerequisites. |
+
[USMT Best Practices](usmt-best-practices-usmt-win7-usmt-win8.md) |
+Discusses general and security-related best practices when using USMT. |
+
[How USMT Works](how-usmt-works-usmt-win7-usmt-win8.md) |
+Learn about the processes behind the ScanState and LoadState tools. |
+
[Plan Your Migration](plan-your-migration-usmt-win7-usmt-win8.md) |
+Choose what to migrate and the best migration scenario for your enterprise. |
+
[User State Migration Tool (USMT) Command-line Syntax](user-state-migration-tool--usmt--command-line-syntax.md) |
+Explore command-line options for the ScanState, LoadState, and UsmtUtils tools. |
+
[USMT XML Reference](usmt-xml-reference-usmt-win7-usmt-win8.md) |
+Learn about customizing a migration with XML files. |
+
[Offline Migration Reference](offline-migration-reference.md) |
+Find requirements, best practices, and other considerations for performing a migration offline. |
+
| Operating Systems | +ScanState (source computer) | +LoadState (destination computer) | +
|---|---|---|
Windows® XP Professional |
+X |
++ |
Windows XP Professional x64 Edition |
+X |
++ |
32-bit versions of Windows Vista |
+X |
+X |
+
64-bit versions of Windows Vista |
+X |
+X |
+
32-bit versions of Windows 7 |
+X |
+X |
+
64-bit versions of Windows 7 |
+X |
+X |
+
32-bit versions of Windows 8 |
+X |
+X |
+
64-bit versions of Windows 8 |
+X |
+X |
+
32-bit versions of Windows 10 |
+X |
+X |
+
64-bit versions of Windows 10 |
+X |
+X |
+
[Understanding Migration XML Files](understanding-migration-xml-files.md) |
+Provides an overview of the default and custom migration XML files and includes guidelines for creating and editing a customized version of the MigDocs.xml file. |
+
[Config.xml File](configxml-file-usmt-win7-usmt-win8.md) |
+Describes the Config.xml file and policies concerning its configuration. |
+
[Customize USMT XML Files](customize-usmt-xml-files-usmt-win7-usmt-win8.md) |
+Describes how to customize USMT XML files. |
+
[Custom XML Examples](custom-xml-examples-usmt-win7-usmt-win8.md) |
+Gives examples of XML files for various migration scenarios. |
+
[Conflicts and Precedence](conflicts-and-precedence-usmt-win7-usmt-win8.md) |
+Describes the precedence of migration rules and how conflicts are handled. |
+
[General Conventions](general-conventions-usmt-win7-usmt-win8.md) |
+Describes the XML helper functions. |
+
[XML File Requirements](xml-file-requirements.md) |
+Describes the requirements for custom XML files. |
+
[Recognized Environment Variables](recognized-environment-variables-usmt-win7-usmt-win8.md) |
+Describes environment variables recognized by USMT. |
+
[XML Elements Library](xml-elements-library-usmt-win7-usmt-win8.md) |
+Describes the XML elements and helper functions for authoring migration XML files to use with USMT. |
+
| Command-line Option | +Description | +
|---|---|
/ec |
+Returns a list of supported cryptographic algorithms (AlgIDs) on the current system. You can use this on a destination computer to determine which algorithm to use with the /encrypt command before you run the ScanState tool on the source computer. |
+
/rd<storeDir> |
+Removes the directory path specified by the <storeDir> argument on the computer. You can use this command to delete hard-link migration stores that cannot otherwise be deleted at a command prompt due to a sharing lock. If the migration store spans multiple volumes on a given drive, it will be deleted from all of these volumes. +For example: +
|
+
/y |
+Overrides the accept deletions prompt when used with the /rd option. When you use the /y option with the /rd option, you will not be prompted to accept the deletions before USMT deletes the directories. |
+
/verify |
+Returns information on whether the compressed migration store is intact or whether it contains corrupted files or a corrupted catalog. +See [Verify Options](#BKMK_VerifyOptions) for syntax and options to use with /verify. |
+
/extract |
+Recovers files from a compressed USMT migration store. +See [Extract Options](#BKMK_ExtractOptions) for syntax and options to use with /extract. |
+
| Command-line Option | +Description | +||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
<reportType> |
+Specifies whether to report on all files, corrupted files only, or the status of the catalog. +
|
+||||||||||||||||||
| /l:
+ <logfilePath> |
+Specifies the location and name of the log file. |
+||||||||||||||||||
/v:<VerbosityLevel> |
+(Verbosity) +Enables verbose output in the UsmtUtils log file. The default value is 0. +You can set the VerbosityLevel to one of the following levels: +
|
+||||||||||||||||||
/decrypt<AlgID>/:<KeyString> +or +/decrypt<AlgID>/:<“Key String”> +or +/decrypt:<AlgID>/keyfile:<FileName> |
+Specifies that the /encrypt option was used to create the migration store with the ScanState tool. To decrypt the migration store, specify a /key or /keyfile option as follows: +
For more information about supported encryption algorithms, see [Migration Store Encryption](migration-store-encryption-usmt-win8.md) |
+
| Command-line Option | +Description | +||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
<filePath> |
+Path to the USMT migration store. +For example: +
|
+||||||||||||||||||
<destinationPath> |
+Path to the folder where the tool puts the individual files. |
+||||||||||||||||||
/i:<includePattern> |
+Specifies a pattern for files to include in the extraction. You can specify more than one pattern. Separate patterns with a comma or a semicolon. You can use /i: <includePattern> and /e: <excludePattern> options in the same command. When both include and exclude patterns are used on the command line, include patterns take precedence over exclude patterns. |
+||||||||||||||||||
/e:<excludePattern> |
+Specifies a pattern for files to omit from the extraction. You can specify more than one pattern. Separate patterns with a comma or a semicolon. You can use /i: <includePattern> and /e: <excludePattern> options in the same command. When both include and exclude patterns are used on the command line, include patterns take precedence over exclude patterns. |
+||||||||||||||||||
/l:<logfilePath> |
+Specifies the location and name of the log file. |
+||||||||||||||||||
/v:<VerbosityLevel> |
+(Verbosity) +Enables verbose output in the UsmtUtils log file. The default value is 0. +You can set the VerbosityLevel to one of the following levels: +
|
+||||||||||||||||||
/decrypt<AlgID>/key:<KeyString> +or +/decrypt<AlgID>/:<“Key String”> +or +/decrypt:<AlgID>/keyfile:<FileName> |
+Specifies that the /encrypt option was used to create the migration store with the ScanState tool. To decrypt the migration store, you must also specify a /key or /keyfile option as follows: +
For more information about supported encryption algorithms, see [Migration Store Encryption](migration-store-encryption-usmt-win8.md). |
+||||||||||||||||||
/o |
+Overwrites existing output files. |
+
| Product Key Type | +Where to Obtain | +
|---|---|
|
+Volume licensing keys can only be obtained with a signed contract from Microsoft. For more info, see the [Microsoft Volume Licensing portal](http://go.microsoft.com/fwlink/p/?LinkId=227282). |
+
Retail product keys |
+Obtained at time of product purchase. |
+
Computer and Processor |
+1 GHz x86 or x64 processor |
+
Memory |
+1 GB RAM for x86 or 2 GB RAM for x64 |
+
Hard Disk |
+16 GB available hard disk space for x86 or 20 GB for x64 |
+
External Drive |
+Removable media (Optional) |
+
Display |
+1024x768 or higher resolution monitor |
+
Network |
+Connectivity to remote computers via Windows® Management Instrumentation (TCP/IP) and Microsoft® Activation Web Service on the Internet via HTTPS |
+
Operating System |
+Windows 7, Windows 8, Windows 8.1, Windows 10, Windows Server 2008 R2, or Windows Server 2012. |
+
Additional Requirements |
+
|
+
[Scenario 1: Online Activation](scenario-1-online-activation-vamt-30-win8.md) |
+Describes how to distribute Multiple Activation Keys (MAKs) to products installed on one or more connected computers within a network, and how to instruct these products to contact Microsoft over the Internet for activation. |
+
[Scenario 2: Proxy Activation](scenario-2-proxy-activation-vamt-30-win8.md) |
+Describes how to use two VAMT host computers — the first one with Internet access and a second computer within an isolated workgroup — as proxies to perform MAK volume activation for workgroup computers that do not have Internet access. |
+
[Scenario 3: KMS Client Activation](scenario-3-kms-client-activation-vamt-30-win8.md) |
+Describes how to use VAMT to configure client products for Key Management Service (KMS) activation. By default, volume license editions of Windows 10, Windows Vista, Windows® 7, Windows 8, Windows Server 2008, Windows Server 2008 R2, or Windows Server® 2012, and Microsoft® Office 2010 use KMS for activation. |
+
[Introduction to VAMT](introduction-to-vamtvamt-30-win8.md) |
+Provides a description of VAMT and common usages. |
+
[Active Directory-Based Activation Overview](active-directory-based-activation-overview.md) |
+Describes Active Directory-Based Activation scenarios. |
+
[Install and Configure VAMT](install-and-configure-vamt-vamt-30-win8.md) |
+Describes how to install VAMT and use it to configure client computers on your network. |
+
[Add and Manage Products](add-and-manage-products-vamt-30-win8.md) |
+Describes how to add client computers into VAMT. + |
+
[Manage Product Keys](manage-product-keys-vamt-30-win8.md) |
+Describes how to add and remove a product key from VAMT. |
+
[Manage Activations](manage-activations-vamt-30-win8.md) |
+Describes how to activate a client computer by using a variety of activation methods. |
+
[Manage VAMT Data](manage-vamt-data-vamt-30-win8.md) |
+Describes how to save, import, export, and merge a Computer Information List (CILX) file using VAMT. |
+
[VAMT Step-by-Step Scenarios](vamt-step-by-step-scenarios-vamt-30-win8.md) |
+Provides step-by-step instructions for using VAMT in typical environments. |
+
[VAMT Known Issues](vamt-known-issues-vamt-30-win8.md) |
+Lists known issues in VAMT. |
+
| Product | +Version | +
|---|---|
Adobe Acrobat Reader |
+9 |
+
AOL Instant Messenger |
+6.8 |
+
Adobe Creative Suite |
+2 |
+
Adobe Photoshop CS |
+8, 9 |
+
Adobe ImageReady CS |
++ |
Apple iTunes |
+6, 7, 8 |
+
Apple QuickTime Player |
+5, 6, 7 |
+
Apple Safari |
+3.1.2 |
+
Google Chrome |
+beta |
+
Google Picasa |
+3 |
+
Google Talk |
+beta |
+
IBM Lotus 1-2-3 |
+9 |
+
IBM Lotus Notes |
+6,7, 8 |
+
IBM Lotus Organizer |
+5 |
+
IBM Lotus WordPro |
+9.9 |
+
Intuit Quicken Deluxe |
+2009 |
+
Money Plus Business |
+2008 |
+
Money Plus Home |
+2008 |
+
Mozilla Firefox |
+3 |
+
Microsoft Office |
+2003, 2007, 2010 |
+
Microsoft Office Access® |
+2003, 2007, 2010 |
+
Microsoft Office Excel® |
+2003, 2007, 2010 |
+
Microsoft Office FrontPage® |
+2003, 2007, 2010 |
+
Microsoft Office OneNote® |
+2003, 2007, 2010 |
+
Microsoft Office Outlook® |
+2003, 2007, 2010 |
+
Microsoft Office PowerPoint® |
+2003, 2007, 2010 |
+
Microsoft Office Publisher |
+2003, 2007, 2010 |
+
Microsoft Office Word |
+2003, 2007, 2010 |
+
Opera Software Opera |
+9.5 |
+
Microsoft Outlook Express |
+(only mailbox file) |
+
Microsoft Project |
+2003, 2007 |
+
Microsoft Office Visio® |
+2003, 2007 |
+
RealPlayer Basic |
+11 |
+
Sage Peachtree |
+2009 |
+
Skype |
+3.8 |
+
Windows Live Mail |
+12, 14 |
+
Windows Live Messenger |
+8.5, 14 |
+
Windows Live MovieMaker |
+14 |
+
Windows Live Photo Gallery |
+12, 14 |
+
Windows Live Writer |
+12, 14 |
+
Windows Mail |
+(Windows 7 and 8) |
+
Microsoft Works |
+9 |
+
Yahoo Messenger |
+9 |
+
Microsoft Zune™ Software |
+3 |
+
| Topic | +Description | +
|---|---|
[Windows 10 deployment tools](windows-deployment-scenarios-and-tools.md) |
+To successfully deploy the Windows 10 operating system and applications for your organization, it is essential that you know about the available tools to help with the process. In this topic, you will learn about the most commonly used tools for Windows 10 deployment. |
+
[Windows ADK for Windows 10 scenarios for IT Pros](windows-adk-scenarios-for-it-pros.md) |
+The Windows Assessment and Deployment Kit (Windows ADK) contains tools that can be used by IT Pros to deploy Windows. |
+
[Volume Activation Management Tool (VAMT) Technical Reference](volume-activation-management-tool--vamt--overview-vamt-30-win8.md) |
+The Volume Activation Management Tool (VAMT) enables network administrators and other IT professionals to automate and centrally manage the Windows®, Microsoft® Office, and select other Microsoft products volume and retail-activation process. |
+
[User State Migration Tool (USMT) Technical Reference](user-state-migration-tool--usmt--technical-reference.md) |
+The User State Migration Tool (USMT) 10.0 is included with the Windows Assessment and Deployment Kit (Windows ADK) for Windows 10. USMT provides a highly customizable user-profile migration experience for IT professionals. |
+
| Elements A-K | +Elements L-Z | +Helper functions | +
|---|---|---|
[<addObjects>](#addObjects) +[<attributes>](#attribute) +[<bytes>](#bytes) +[<commandLine>](#commandLine) +[<component>](#component) +[<condition>](#condition) +[<conditions>](#conditions) +[<content>](#content) +[<contentModify>](#contentModify) +[<description>](#description) +[<destinationCleanup>](#destinationCleanup) +[<detect>](#detect) +[<detects>](#detects) +[<detection>](#detection) +[<displayName>](#displayName) +[<environment>](#BKMK_environment) +[<exclude>](#exclude) +[<excludeAttributes>](#excludeAttributes) +[<extensions>](#extensions) +[<extension>](#extension) +[<externalProcess>](#externalProcess) +[<icon>](#icon) +[<include>](#include) +[<includeAttribute>](#includeAttributes) |
+[<library>](#library) +[<location>](#location) +[<locationModify>](#locationModify) +[<_locDefinition>](#locDefinition) +[<manufacturer>](#manufacturer) +[<merge>](#merge) +[<migration>](#migration) +[<namedElements>](#namedElements) +[<object>](#object) +[<objectSet>](#objectSet) +[<path>](#path) +[<paths>](#paths) +[<pattern>](#pattern) +[<processing>](#processing) +[<plugin>](#plugin) +[<role>](#role) +[<rules>](#rules) +[<script>](#script) +[<text>](#text) +[<unconditionalExclude>](#unconditionalExclude) +[<variable>](#variable) +[<version>](#version) +[<windowsObjects>](#windowsObjects) |
+[<condition> functions](#ConditionFunctions) +[<content> functions](#ContentFunctions) +[<contentModify> functions](#ContentModifyFunctions) +[<include> and <exclude> filter functions](#PersistFilterFunctions) +[<locationModify> functions](#LocationModifyFunctions) +[<merge> functions](#MergeFunctions) +[<script> functions](#ScriptFunctions) +[Internal USMT functions](#InternalUSMTFunctions) |
+
| Setting | +Required? | +Value | +
|---|---|---|
Content |
+Yes |
+The content depends on the type of object specified. +
|
+
| Setting | +Required? | +Value | +
|---|---|---|
string |
+No, default is No |
+Determines whether Content should be interpreted as a string or as bytes. |
+
expand |
+No (default = Yes |
+When the expand parameter is Yes, the content of the <bytes> element is first expanded in the context of the source computer and then interpreted. |
+
Content |
+Yes |
+Depends on the value of the string. +
|
+
| Setting | +Required? | +Value | +
|---|---|---|
CommandLineString |
+Yes |
+A valid command line. |
+
| Setting | +Required? | +Value | +
|---|---|---|
type |
+Yes |
+You can use the following to group settings, and define the type of the component. +
|
+
context |
+No +Default = UserAndSystem |
+Defines the scope of this parameter; that is, whether to process this component in the context of the specific user, across the entire operating system, or both. +The largest possible scope is set by the <component> element. For example, if a <component> element has a context of User and a <rules> element had a context of UserAndSystem, then the <rules> element would act as though it has a context of User. If a <rules> element has a context of System, it would act as though the <rules> element is not there. +
|
+
defaultSupported |
+No +(default = TRUE) |
+Can be any of TRUE, FALSE, YES or NO. If this parameter is FALSE (or NO), the component will not be migrated unless there is an equivalent component on the destination computer. +When type="System" and defaultSupported="FALSE" the settings will not migrate unless there is an equivalent component in the .xml files that are specified on the LoadState command line. For example, the default MigSys.xml file contains components with type="System" and defaultSupported="FALSE". If you specify this file on the ScanState command line, you must also specify the file on the LoadState command line for the settings to migrate. This is because the LoadState tool must detect an equivalent component. That is, the component must have the same migration urlid of the .xml file and an identical display name or the LoadState tool will not migrate those settings from the store. This is helpful when the source computer is running Windows XP, and you are migrating to both Windows Vista and Windows XP because you can use the same store for both destination computers. |
+
hidden |
+
|
+This parameter is for internal USMT use only. |
+
| Setting | +Required? | +Value | +
|---|---|---|
negation |
+No +Default = No |
+"Yes" reverses the True/False value of the condition. |
+
ScriptName |
+Yes |
+A script that has been defined within this migration section. |
+
| Setting | +Required? | +Value | +
|---|---|---|
OSType |
+ Yes |
+ The only valid value for this setting is NT. Note, however, that you must set this setting for the <condition> functions to work correctly. |
+
OSVersion |
+ Yes |
+ The major version, minor version, build number and corrected service diskette version separated by periods. For example, |
+
| Setting | +Required? | +Value | +
|---|---|---|
OSType |
+ Yes |
+ Can be 9x or NT. If OSType does not match the type of the current operating system, then it returns FALSE. For example, if the current operating system is Windows NT-based and OSType is “9x”, the result will be FALSE. |
+
OSVersion |
+ Yes |
+ The major version, minor version, build number, and corrected service diskette version separated by periods. For example, The IsOSLaterThan function returns TRUE if the current operating system is later than or equal to OSVersion. |
+
| Setting | +Required? | +Value | +
|---|---|---|
OSType |
+ Yes |
+ Can be 9x or NT. If OSType does not match the type of the current operating system, then it returns FALSE. For example, if the current operating system is Windows NT-based and OSType is “9x” the result will be FALSE. |
+
OSVersion |
+ Yes |
+ The major version, minor version, build number, and corrected service diskette version separated by periods. For example, The IsOSEarlierThan function returns TRUE if the current operating system is earlier than OSVersion. |
+
| Setting | +Required? | +Value | +
|---|---|---|
ObjectType |
+ Yes |
+ Defines the object type. Can be File or Registry. |
+
EncodedLocationPattern |
+ Yes |
+ The [location pattern](#locations). Environment variables are allowed. |
+
| Setting | +Required? | +Value | +
|---|---|---|
EncodedFileLocation |
+ Yes |
+ The [location pattern](#locations) for the file that will be checked. Environment variables are allowed. |
+
VersionTag |
+ Yes |
+ The [version tag](#Allowed) value that will be checked. |
+
VersionValue |
+ Yes |
+ A string pattern. For example, "Microsoft*". |
+
| Setting | +Required? | +Value | +
|---|---|---|
EncodedFileLocation |
+ Yes |
+ The [location pattern](#locations) for the file that will be checked. Environment variables are allowed. |
+
VersionTag |
+ Yes |
+ The [version tag](#Allowed) value that will be checked. |
+
VersionValue |
+ Yes |
+ The value to compare to. You cannot specify a pattern. |
+
| Setting | +Required? | +Value | +
|---|---|---|
EncodedFileLocation |
+ Yes |
+ The [location pattern](#locations) for the file that will be checked. Environment variables are allowed. |
+
VersionTag |
+ Yes |
+ The [version tag](#Allowed) value that will be checked. |
+
VersionValue |
+ Yes |
+ The value to compare to. You cannot specify a pattern. |
+
| Setting | +Required? | +Value | +
|---|---|---|
ObjectType |
+ Yes |
+ Defines the type of object. Can be File or Registry. |
+
EncodedLocationPattern |
+ Yes |
+ The [encoded location](#locations) for the object that will be examined. You can specify environment variables. |
+
StringContent |
+ Yes |
+ The string that will be checked against. |
+
| Setting | +Required? | +Value | +
|---|---|---|
ObjectType |
+ Yes |
+ Defines the type of object. Can be File or Registry. |
+
EncodedLocationPattern |
+ Yes |
+ The [encoded location](#locations) for the object that will be examined. You can specify environment variables. |
+
StrToFind |
+ Yes |
+ A string that will be searched inside the content of the given object. |
+
| Setting | +Required? | +Value | +
|---|---|---|
ObjectType |
+ Yes |
+ Defines the type of object. Can be File or Registry. |
+
EncodedLocation1 |
+ Yes |
+ The [encoded location](#locations) for the first object. You can specify environment variables. |
+
EncodedLocation2 |
+ Yes |
+ The [encoded location](#locations) for the second object. You can specify environment variables. |
+
| Setting | +Required? | +Value | +
|---|---|---|
ObjectType1 |
+ Yes |
+ Defines the type of the first object. Can be File or Registry. |
+
EncodedLocation1 |
+ Yes |
+ The [encoded location](#locations) for the first object. You can specify environment variables. |
+
ObjectType2 |
+ Yes |
+ Defines the type of the second object. Can be File or Registry. |
+
EncodedLocation2 |
+ Yes |
+ The [encoded location](#locations) for the second object. You can specify environment variables. |
+
| Setting | +Required? | +Value | +
|---|---|---|
ObjectType1 |
+ Yes |
+ Defines the type of the first object. Can be File or Registry. |
+
EncodedLocation1 |
+ Yes |
+ The [encoded location](#locations) for the first object. You can specify environment variables. |
+
ObjectType2 |
+ Yes |
+ Defines the type of the second object. Can be File or Registry. |
+
EncodedLocation2 |
+ Yes |
+ The [encoded location](#locations) for the second object. You can specify environment variables. |
+
| Setting | +Required? | +Value | +
|---|---|---|
operation |
+No, default = AND |
+Defines the Boolean operation that is performed on the results that are obtained from the child elements. |
+
| Setting | +Required? | +Value | +
|---|---|---|
filter |
+Yes |
+A script followed by any number of string arguments that are separated by a comma and enclosed in parenthesis. For example The script is called for each object that is enumerated by the object sets in the <include> rule. The filter script returns a Boolean value. If the return value is TRUE, the object will be migrated. If it is FALSE, it will not be migrated. |
+
| Setting | +Required? | +Value | +
|---|---|---|
Separators |
+ Yes |
+ A list of possible separators that might follow the file specification in this registry value name. For example, if the content is "C:\Windows\Notepad.exe,-2", the separator is a comma. You can specify NULL. |
+
PathHints |
+ Yes |
+ A list of extra paths, separated by colons (;), where the function will look for a file matching the current content. For example, if the content is "Notepad.exe" and the path is the %Path% environment variable, the function will find Notepad.exe in %windir% and returns "c:\Windows [Notepad.exe]". You can specify NULL. |
+
| Setting | +Required? | +Value | +
|---|---|---|
Separators |
+ Yes |
+ A list of possible separators that might follow the file specification in this registry value name. For example, if the content is "C:\Windows\Notepad.exe,-2", the separator is a comma. This parameter must be NULL when processing MULTI-SZ registry values. |
+
PathHints |
+ Yes |
+ A list of extra paths, separated by colons (;), where the function will look for a file matching the current content. For example, if the content is "Notepad.exe" and the path is the %Path% environment variable, the function will find Notepad.exe in %windir% and returns "c:\Windows [Notepad.exe]". You can specify NULL. |
+
| Setting | +Required? | +Value | +
|---|---|---|
Separators |
+ No |
+ A list of possible separators that might follow the file specification in this registry value name. For example, if the content is "C:\Windows\Notepad.exe,-2", the separator is a comma. You must specify NULL when processing MULTI-SZ registry values. |
+
LevelsToTrim |
+ Yes |
+ The number of levels to delete from the end of the directory specification. Use this function to extract a root directory when you have a registry value that points inside that root directory in a known location. |
+
PatternSuffix |
+ Yes |
+ The pattern to add to the directory specification. For example, |
+
| Setting | +Required? | +Value | +
|---|---|---|
script |
+Yes |
+A script followed by any number of string arguments that are separated by a comma and enclosed in parenthesis. For example The script will be called for each object that is enumerated by the object sets in the include rule. The filter script returns a Boolean value. If the return value is TRUE, the object will be migrated. If it is FALSE, it will not be migrated. |
+
| Setting | +Required? | +Value | +
|---|---|---|
DefaultValueOnError |
+ No |
+ The value that will be written into the value name if the conversion fails. You can specify NULL, and 0 will be written if the conversion fails. |
+
| Setting | +Required? | +Value | +
|---|---|---|
DefaultValueOnError |
+ No |
+ The value that will be written into the value name if the conversion fails. You can specify NULL, and 0 will be written if the conversion fails. |
+
| Setting | +Required? | +Value | +
|---|---|---|
Value |
+ Yes |
+ The string representation of a numeric value. It can be positive or negative. For example, |
+
| Setting | +Required? | +Value | +
|---|---|---|
SourceTable |
+ Yes |
+ A list of values separated by commas that are possible for the source registry values. |
+
DestinationTable |
+ No |
+ A list of translated values separated by commas. |
+
DefaultValueOnError |
+ No |
+ The value that will be applied to the destination computer if either 1) the value for the source computer does not match SourceTable, or 2) DestinationTable has no equivalent value. +If DefaultValueOnError is NULL, the value will not be changed on the destination computer. |
+
| Setting | +Required? | +Value | +
|---|---|---|
OptionString |
+ Yes |
+ OptionString can be Security, TimeFields, or FileAttrib:Letter. You can specify one of each type of OptionStrings. Do not specify multiple OptionStrings with the same value. If you do, the right-most option of that type will be kept. For example, do not specify ("FileAttrib:H", "FileAttrib:R") because only Read-only will be evaluated. Instead specify ("FileAttrib:HR") and both Hidden and Read-only attributes will be kept on the destination computer. +
|
+
| Setting | +Required? | +Value | +
|---|---|---|
Instruction |
+ Yes |
+ Can be one of the following: +
|
+
String |
+ Yes |
+ The string to be added or removed. |
+
| Setting | +Required? | +Value | +
|---|---|---|
Delimiters |
+ Yes |
+ A single character that will be used to separate the content of the object that is being processed. The content will be considered as a list of elements that is separated by the Delimiters. +For example, "." will separate the string based on a period. |
+
Instruction |
+ Yes |
+ Can one of the following: +
|
+
String |
+ Yes |
+ The string to be added or removed. |
+
| Setting | +Required? | +Value | +
|---|---|---|
ComponentDescription |
+Yes |
+The description of the component. |
+
| Setting | +Required? | +Value | +
|---|---|---|
filter |
+Yes |
+A script followed by any number of string arguments that are separated by a comma and enclosed in parenthesis. For example The script will be called for each object that is enumerated by the object sets in the include rule. The filter script returns a Boolean value. If the return value is TRUE, the object will be migrated. If it is FALSE, it will not be migrated. |
+
| Setting | +Required? | +Value | +
|---|---|---|
name |
+Yes, when <detect> is a child to <namedElements> +No, when <detect> is a child to <detects> |
+When ID is specified, any child elements are not processed. Instead, any other <detect> elements with the same name that are declared within the <namedElements> element are processed. |
+
context |
+No +(default = UserAndSystem) |
+Defines the scope of this parameter: whether to process this component in the context of the specific user, across the entire operating system, or both. +The largest possible scope is set by the component element. For example, if a <component> element has a context of User, and a <rules> element had a context of UserAndSystem, then the <rules> element would act as though it had a context of User. If the <rules> element had a context of System, it would act as though the <rules> element were not there. +
|
+
| Setting | +Required? | +Value | +
|---|---|---|
name |
+Yes, when <detects> is a child to <namedElements> +No, when <detects> is a child to <role> or <rules> |
+When ID is specified, no child <detect> elements are processed. Instead, any other <detects> elements with the same name that are declared within the <namedElements> element are processed. |
+
context |
+No +(default = UserAndSystem) |
+Defines the scope of this parameter: whether to process this component in the context of the specific user, across the entire operating system, or both. +The largest possible scope is set by the <component element>. For example, if a <component> element has a context of User and a <rules> element had a context of UserAndSystem, then the <rules> element would act as though it had a context of User. If the <rules> element had a context of System, it would act as though the <rules> element were not there. +
The context parameter is ignored for <detects> elements that are inside <rules> elements. |
+
| Setting | +Required? | +Value | +
|---|---|---|
name |
+
|
+If declared, the content of the <detection> element is ignored and the content of the <detection> element with the same name that is declared in the <namedElements> element will be evaluated. |
+
context |
+No, default = UserAndSystem |
+Defines the scope of this parameter: whether to process this component in the context of the specific user, across the entire operating system, or both. +
|
+
| Setting | +Required? | +Value | +
|---|---|---|
locID |
+No |
+This parameter is for internal USMT use. Do not use this parameter. |
+
ComponentName |
+Yes |
+The name for the component. |
+
| Setting | +Required? | +Value | +
|---|---|---|
name |
+Yes, when <environment> is a child of <namedElements> +No, when <environment> is a child of <role> or <component> |
+When declared as a child of the <role> or <component> elements, if ID is declared, USMT ignores the content of the <environment> element and the content of the <environment> element with the same name declared in the <namedElements> element is processed. |
+
context |
+No +(default = UserAndSystem) |
+Defines the scope of this parameter: whether to process this component in the context of the specific user, across the entire operating system, or both. +The largest possible scope is set by the <component> element. For example, if a <component> element has a context of User and a <rules> element had a context of UserAndSystem, then the <rules> element would act as though it had a context of User. If the <rules> element had a context of System, it would act as though <rules> were not there. +
|
+
| Setting | +Required? | +Value | +
|---|---|---|
filter |
+No +(default = No) |
+A script followed by any number of string arguments that are separated by a comma and enclosed in parenthesis. For example The script will be called for each object that is enumerated by the object sets in the include rule. The filter script returns a Boolean value. If the return value is TRUE, the object will be migrated. If it is FALSE, it will not be migrated. |
+
| Parameter | +Required? | +Value | +
|---|---|---|
attributes |
+Yes |
+Specifies the attributes to be excluded. You can specify one of the following, or both separated by quotes; for example,
|
+
| Setting | +Required? | +Value | +
|---|---|---|
FilenameExtension |
+Yes |
+A file name extension. |
+
| Setting | +Required? | +Value | +
|---|---|---|
when |
+Yes |
+Indicates when the command line should be run. This value can be one of the following: +
|
+
| Setting | +Required? | +Value | +
|---|---|---|
filter |
+No. +If this parameter is not specified, then all patterns that are inside the child <ObjectSet> element will be processed. |
+A script followed by any number of string arguments that are separated by a comma and enclosed in parenthesis. For example The script will be called for each object that is enumerated by the object sets in the <include> rule. The filter script returns a Boolean value. If the return value is TRUE, the object will be migrated. If it is FALSE, it will not be migrated. |
+
| Setting | +Required? | +Value | +
|---|---|---|
StringContent |
+ Yes |
+ The string to check against. |
+
CompareType |
+ Yes |
+ A string. Use one of the following values: +
|
+
| Setting | +Required? | +Value | +
|---|---|---|
attributes |
+Yes |
+Specifies the attributes to be included with a migrated object. You can specify one of the following, or both separated by quotes; for example,
|
+
| Setting | +Required? | +Value | +
|---|---|---|
type |
+Yes |
+typeID can be Registry or File. |
+
ObjectLocation |
+Yes |
+The location of the object. |
+
| Setting | +Required? | +Value | +
|---|---|---|
script |
+Yes |
+A script followed by any number of string arguments that are separated by a comma and enclosed in parenthesis. For example The script will be called for each object that is enumerated by the object sets in the include rule. The filter script returns a Boolean value. If the return value is TRUE, the object will be migrated. If it is FALSE, it will not be migrated. |
+
| Setting | +Required? | +Value | +
|---|---|---|
ObjectEncodedLocation |
+ Yes |
+ The destination [location](#locations) for all of the source objects. |
+
| Setting | +Required? | +Value | +
|---|---|---|
DestinationRoot |
+ Yes |
+ The location where the source objects will be moved. If needed, this function will create any subdirectories that were above the longest CSIDL in the source object name. |
+
| Setting | +Required? | +Value | +
|---|---|---|
SourceRoot |
+ Yes |
+ The location from where the objects will be moved. Any source objects that are enumerated by the parent <ObjectSet> element that are not in this location will not be moved. |
+
DestinationRoot |
+ Yes |
+ The location where the source objects will be moved to on the destination computer. If needed, this function will create any subdirectories that were above SourceRoot. |
+
| Setting | +Required? | +Value | +
|---|---|---|
Name |
+Yes |
+The name of the manufacturer for the component. |
+
| Setting | +Required? | +Value | +
|---|---|---|
script |
+Yes |
+A script followed by any number of string arguments that are separated by a comma and enclosed in parenthesis. For example The script will be called for each object that is enumerated by the object sets in the <include> rule. The filter script returns a Boolean value. If the return value is TRUE, the object will be migrated. If it is FALSE, it will not be migrated. |
+
| Setting | +Required? | +Value | +
|---|---|---|
FilePattern |
+ Yes |
+
For example, |
+
| Setting | +Required? | +Value | +
|---|---|---|
VersionTag |
+ Yes |
+ The version field that will be checked. This can be "FileVersion" or "ProductVersion". The file with the highest VersionTag version determines which conflicts will be resolved based on the file's version. For example, if Myfile.txt contains FileVersion 1 and the same file on the destination computer contains FileVersion 2, the file on destination will remain. |
+
| Setting | +Required? | +Value | +
|---|---|---|
urlid |
+Yes |
+UrlID is a string identifier that uniquely identifies this .xml file. This parameter must be a no-colon-name as defined by the XML Namespaces specification. Each migration .xml file must have a unique urlid. If two migration .xml files have the same urlid, the second .xml file that is specified on the command line will not be processed. For more information about XML Namespaces, see [Use XML Namespaces](http://go.microsoft.com/fwlink/p/?LinkId=220938). |
+
Name |
+No |
+Although not required, it is good practice to use the name of the .xml file. |
+
| Helper Function | +MigXMLHelper.FileProperties (property, operator, valueToCompare) | +
|---|---|
Property |
+filesize, dateCreated, dateModified, dateAccessed |
+
Operator |
+range, neq, lte, lt, eq, gte, gt |
+
valueToCompare |
+The value we are comparing. For example: +Date: “2008/05/15-2005/05/17”, “2008/05/15” +Size: A numeral with B, KB, MB, or GB at the end. “5GB”, “1KB-1MB” |
+
| Setting | +Required? | +Value | +
|---|---|---|
type |
+Yes |
+typeID can be Registry, File, or Ini. If typeId is Ini, then you cannot have a space between Path and object. For example, the following is correct when type="Ini": +<pattern type="Ini">%WinAmp5InstPath%\Winamp.ini|WinAmp[keeponscreen]</pattern> |
+
Path [object] |
+Yes |
+A valid registry or file path pattern, followed by at least one space, followed by brackets [] that contain the object to be migrated. +
|
+
| Setting | +Required? | +Value | +
|---|---|---|
when |
+Yes |
+Indicates when the script should be run. This value can be one of the following: +
|
+
| Setting | +Required? | +Value | +
|---|---|---|
role |
+Yes |
+Defines the role for the component. Role can be one of: +
You can either: +
|
+
| Setting | +Required? | +Value | +
|---|---|---|
name |
+Yes, when <rules> is a child to <namedElements> +No, when <rules> is a child to any other element |
+When ID is specified, any child elements are not processed. Instead, any other <rules> elements with the same name that are declared within <namedElements> are processed. |
+
context |
+No +(default = UserAndSystem) |
+Defines the scope of this parameter — whether to process this component in the context of the specific user, across the entire operating system, or both. +The largest possible scope is set by the component element. For example, if a <component> element has a context of User and a <rules> element had a context of UserAndSystem, then the <rules> element would act as though it has a context of User. If <rules> had a context of System, it would act as though <rules> was not there. +
|
+
| Setting | +Required? | +Value | +
|---|---|---|
ScriptWithArguments |
+Yes |
+A script followed by any number of string arguments that are separated by a comma and enclosed in parenthesis. For example The script will be called for each object that is enumerated by the object sets in the <include> rule. The filter script returns a Boolean value. If the return value is TRUE, the object will be migrated. If it is FALSE, it will not be migrated. +The return value that is required by <script> depends on the parent element. +
|
+
| Setting | +Required? | +Value | +
|---|---|---|
ObjectType |
+ Yes |
+ The type of object. Can be Registry or Ini (for an .ini file). |
+
EncodedLocationPattern |
+ Yes |
+
|
+
ExpandContent |
+ No (default=TRUE) |
+ Can be TRUE or FALSE. If FALSE, then the given location will not be expanded before it is returned. |
+
| Setting | +Required? | +Value | +
|---|---|---|
PatternSegment |
+ Yes |
+ The suffix of an encoded pattern. It will be concatenated with a drive specification, such as "c:\", to form a complete [encoded file pattern](#locations). For example, "* [*.doc]". PatternSegment cannot be an environment variable. |
+
DriveType |
+ Yes |
+ The drive type for which the patterns are to be generated. You can specify one of: +
|
+
| Setting | +Required? | +Value | +
|---|---|---|
ObjectType |
+ Yes |
+ Defines the object type. Can be File or Registry. |
+
EncodedLocationPattern |
+ Yes |
+ The [location pattern](#locations). Environment variables are allowed. |
+
ProcessCurrentUser |
+ Yes |
+ Can be TRUE or FALSE. Indicates if the patterns should be generated for the current user. |
+
| Setting | +Required? | +Value | +
|---|---|---|
ScanProgramFiles |
+No (default = FALSE) |
+Can be TRUE or FALSE. The ScanProgramFiles parameter determines whether or not the document finder scans the Program Files directory to gather registered file extensions for known applications. For example, when set to TRUE it will discover and migrate .jpg files under the Photoshop directory, if .jpg is a file extension registered to Photoshop. |
+
IncludePatterns |
+No (default = TRUE) |
+Can be TRUE or FALSE. TRUE will generate include patterns and can be added under the <include> element. FALSE will generate exclude patterns and can be added under the <exclude> element. |
+
SystemDrive |
+No (default = FALSE) |
+Can be TRUE or FALSE. If TRUE, restricts all patterns to the system drive. |
+
| Setting | +Value | +
|---|---|
NormalText |
+This is interpreted as normal text. |
+
| Setting | +Required? | +Value | +
|---|---|---|
name |
+Yes |
+ID is a string value that is the name used to reference the environment variable. We recommend that ID start with the component’s name to avoid namespace collisions. For example, if your component’s name is MyComponent, and you want a variable that is your component’s install path, you could specify |
+
remap |
+No, default = FALSE |
+Specifies whether to evaluate this environment variable as a remapping environment variable. Objects that are located in a path that is underneath this environment variable’s value are automatically moved to where the environment variable points on the destination computer. |
+
| Setting | +Required? | +Value | +
|---|---|---|
ComponentVersion |
+Yes |
+The version of the component, which can contain patterns. |
+
| Action | +Online-licensed app | +Offline-licensed app | +
|---|---|---|
Assign to employees |
+X |
++ |
Add to private store |
+X |
++ |
Remove from private store |
+X |
++ |
View license details |
+X |
++ |
View product details |
+X |
+X |
+
Download for offline use |
++ | X |
+
| New or changed topic | +Description | +
|---|---|
| [Join Windows 10 Mobile to Azure Active Directory](join-windows-10-mobile-to-azure-active-directory.md) | +New |
+
| New or changed topic | +Description | +
|---|---|
| [Configure telemetry and other settings in your organization](manage-privacy-for-windows-10-in-your-company.md) | +Added call history and email to the Settings > Privacy section. +Added the Turn off Windows Mail application Group Policy to the Mail synchronization section. |
+
| [Customize and export Start layout](customize-and-export-start-layout.md) | +Added a note to clarify that partial Start layout is only supported in Windows 10, Version 1511 and later | +
| [Customize Windows 10 Start with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management--mdm-.md) | +Added instructions for replacing markup characters with escape characters in Start layout XML | +
| [Introduction to configuration service providers (CSPs) for IT pros](how-it-pros-can-use-configuration-service-providers--csps--.md) | +New | +
| [Windows 10 Mobile and MDM](windows-10-mobile-and-mdm.md) | +New | +
| [Windows 10 servicing options for updates and upgrades](introduction-to-windows-10-servicing.md) | +Added information on servicing options for Windows 10 Mobile, Windows 10 Mobile Enterprise, and Windows 10 IoT Core (IoT Core). | +
| New or changed topic | +Description | +
|---|---|
| [Cortana integration in your business or enterprise](manage-cortana-in-your-enterprise.md) | +New | +
| [Manage Wi-Fi Sense in your company](manage-wi-fi-sense-in-your-company.md) | +New | +
| Customize Windows 10 Start with mobile device management (MDM) | ++ |
| Policy | +Notes | +
|---|---|
| Clear history of recently opened documents on exit | +Documents that the user opens are tracked during the session. When the user signs off, the history of opened documents is deleted. | +
| Do not allow pinning items in Jump Lists | +Jump Lists are lists of recently opened items, such as files, folders, or websites, organized by the program that you use to open them. This policy prevents users from pinning items to any Jump List. | +
| Do not display or track items in Jump Lists from remote locations | +When this policy is applied, only items local on the computer are shown in Jump Lists. | +
| Do not keep history of recently opened documents | +Documents that the user opens are not tracked during the session. | +
| Prevent changes to Taskbar and Start Menu Settings | +In Windows 10, this disables all of the settings in Settings > Personalization > Start as well as the options in dialog available via right-click Taskbar > Properties | +
| Prevent users from customizing their Start Screen | +Use this policy in conjunction with [CopyProfile](http://go.microsoft.com/fwlink/p/?LinkId=623229) or other methods for configuring the layout of Start to prevent users from changing it |
+
| Prevent users from uninstalling applications from Start | +In Windows 10, this removes the uninstall button in the context menu. It does not prevent users from uninstalling the app through other entry points (e.g. PowerShell) | +
| Remove All Programs list from the Start menu | +In Windows 10, this removes the All apps button. | +
| Remove and prevent access to the Shut Down, Restart, Sleep, and Hibernate commands | +This removes the Shut Down, Restart, Sleep, and Hibernate commands from the Start Menu, Start Menu power button, CTRL+ALT+DEL screen, and Alt+F4 Shut Down Windows menu. | +
| Remove common program groups from Start Menu | +As in earlier versions of Windows, this removes apps specified in the All Users profile from Start | +
| Remove frequent programs list from the Start Menu | +In Windows 10, this removes the top left Most used group of apps. | +
| Remove Logoff on the Start Menu | +Logoff has been changed to Sign Out in the user interface, however the functionality is the same. | +
| Remove pinned programs list from the Start Menu | +In Windows 10, this removes the bottom left group of apps (by default, only File Explorer and Settings are pinned). | +
| Show "Run as different user" command on Start | +This enables the Run as different user option in the right-click menu for apps. | +
| Start Layout | +This applies a specific Start layout, and it also prevents users from changing the layout. This policy can be configured in User Configuration or Computer Configuration. +
+Note
+
+Start Layout policy setting applies only to Windows 10 Enterprise and Windows 10 Education. +
+
+ |
+
| Force Start to be either full screen size or menu size | +This applies a specific size for Start. | +
| XML | +
|---|
|
+
| XML | +
|---|
|
+
| Topic | +Description | +
|---|---|
[Add unsigned app to code integrity policy](add-unsigned-app-to-code-integrity-policy.md) |
+When you want to add an unsigned app to a code integrity policy, you need to start with a code integrity policy created from a reference device. Then, create the catalog files for your unsigned app, sign the catalog files, and then merge the default policy that includes your signing certificate with existing code integrity policies. |
+
[Sign code integrity policy with Device Guard signing](sign-code-integrity-policy-with-device-guard-signing.md) |
+Signing code integrity policies prevents policies from being tampered with after they're deployed. You can sign code integrity policies with the Device Guard signing portal. |
+
| Topic | +Description | +
|---|---|
[Distribute apps using your private store](distribute-apps-from-your-private-store.md) |
+The private store is a feature in Store for Business that organizations receive during the sign up process. When admins add apps to the private store, all employees in the organization can view and download the apps. Your private store is available as a tab in the Windows Store, and is usually named for your company or organization. Only apps with online licenses can be added to the private store. |
+
[Assign apps to employees](assign-apps-to-employees.md) |
+Administrators can assign online-licensed apps to employees in their organization. |
+
[Distribute apps with a management tool](distribute-apps-with-a-management-tool.md) |
+You can configure a mobile device management (MDM) tool to synchronize your Store for Business inventory. Store for Business management tool services work with MDM tools to manage content. |
+
[Distribute offline apps](distribute-offline-apps.md) |
+Offline licensing is a new licensing option for Windows 10. With offline licenses, organizations can download apps and their licenses to deploy within their network, or on devices that are not connected to the Internet. ISVs or devs can opt-in their apps for offline licensing when they submit them to the Windows Dev Center. Only apps that are opted in to offline licensing will show that they are available for offline licensing in the Store for Business. This model means organizations can deploy apps when users or devices do not have connectivity to the Store. |
+
| Topic | +Description | +
|---|---|
[Apps in the Windows Store for Business](apps-in-the-windows-store-for-business.md) |
+Store for Business has thousands of apps from many different categories. |
+
[Working with line-of-business apps](working-with-line-of-business-apps.md) |
+Your company can make line-of-business (LOB) applications available through Store for Business. These apps are custom to your company – they might be internal business apps, or apps specific to your business or industry. |
+
| Topic | +Description | +
|---|---|
[Set up a device for anyone to use (kiosk mode)](set-up-a-device-for-anyone-to-use.md) |
+You can configure a device running Windows 10 Pro, Windows 10 Enterprise, Windows 10 Education, Windows 10 Mobile, or Windows 10 Mobile Enterprise as a kiosk device, so that users can only interact with a single application that you select. |
+
[Lock down Windows 10 to specific apps](lock-down-windows-10-to-specific-apps.md) |
+Learn how to configure a device running Windows 10 Enterprise or Windows 10 Education so that users can only run a few specific apps. The result is similar to [a kiosk device](set-up-a-device-for-anyone-to-use.md), but with multiple apps available. For example, you might set up a library computer so that users can search the catalog and browse the Internet, but can't run any other apps or change computer settings. |
+
[Configure telemetry and other settings in your organization](manage-privacy-for-windows-10-in-your-company.md) |
+Learn about the telemetry that Microsoft gathers, the network connections that Windows components make to Microsoft, and also the privacy settings that affect data that is shared with either Microsoft or apps and how they can be managed by an IT Pro. |
+
[Configure access to Windows Store](stop-employees-from-using-the-windows-store.md) |
+IT Pros can configure access to Windows Store for client computers in their organization. For some organizations, business policies require blocking access to Windows Store. |
+
[Manage Wi-Fi Sense in your company](manage-wi-fi-sense-in-your-company.md) |
+Wi-Fi Sense automatically connects you to Wi-Fi, so you can get online quickly in more places. It can connect you to open Wi-Fi hotspots it knows about through crowdsourcing, or to Wi-Fi networks your contacts have shared with you by using Wi-Fi Sense. +The initial settings for Wi-Fi Sense are determined by the options you chose when you first set up your PC with Windows 10. |
+
[Configure Windows 10 Mobile using Lockdown XML](lockdown-xml.md) |
+Windows 10 Mobile allows enterprises to lock down a device, define multiple user roles, and configure custom layouts on a device. |
+
[Reset a Windows 10 Mobile device](reset-a-windows-10-mobile-device.md) |
+There are two methods for resetting a Windows 10 Mobile device: factory reset and "wipe and persist" reset. |
+
| Topic | +Description | +
|---|---|
[Change history for Manage and update Windows 10](change-history-for-manage-and-update-windows-10.md) |
+This topic lists new and updated topics in the Manage and update Windows 10 documentation for [Windows 10 and Windows 10 Mobile](../index.md). |
+
[Administrative Tools in Windows 10](administrative-tools-in-windows-10.md) |
+Administrative Tools is a folder in Control Panel that contains tools for system administrators and advanced users. |
+
[Cortana integration in your business or enterprise](manage-cortana-in-your-enterprise.md) |
+The world’s first personal digital assistant helps users get things done, even at work. Cortana includes powerful configuration options specifically to optimize for unique small to medium-sized business and enterprise environments. |
+
[Manage corporate devices](manage-corporate-devices.md) |
+You can use the same management tools to manage all device types running Windows 10 : desktops, laptops, tablets, and phones. And your current management tools, such as Group Policy, Windows Management Instrumentation (WMI), Windows PowerShell scripts, Orchestrator runbooks, System Center tools, and so on, will continue to work for Windows 10 on desktop editions. |
+
[Manage Windows 10 Start layout options](windows-10-start-layout-options-and-policies.md) |
+Organizations might want to deploy a customized Start screen and menu to devices running Windows 10 Enterprise or Windows 10 Education. A standard Start layout can be useful on devices that are common to multiple users and devices that are locked down for specialized purposes. |
+
[Lock down Windows 10](lock-down-windows-10.md) |
+Enterprises often need to manage how people use corporate devices. Windows 10 provides a number of features and methods to help you lock down specific parts of a Windows 10 device. |
+
[Join Windows 10 Mobile to Azure Active Directory](join-windows-10-mobile-to-azure-active-directory.md) |
+Devices running Windows 10 Mobile can join Azure Active Directory (Azure AD) when the device is configured during the out-of-box experience (OOBE). |
+
[Configure devices without MDM](configure-devices-without-mdm.md) |
+Create a runtime provisioning package to apply settings, profiles, and file assets to a device running Windows 10 Pro, Windows 10 Enterprise, Windows 10 Education, Windows 10 Mobile, or Windows 10 Mobile Enterprise. |
+
[Windows 10 servicing options for updates and upgrades](introduction-to-windows-10-servicing.md) |
+This article describes the new servicing options available in Windows 10, Windows 10 Mobile, and Windows 10 IoT Core (IoT Core) and how they enable enterprises to keep their devices current with the latest feature upgrades. It also covers related topics, such as how enterprises can make better use of Windows Update, and what the new servicing options mean for support lifecycles. |
+
[Windows Store for Business](windows-store-for-business.md) |
+Welcome to the Windows Store for Business! You can use the Store for Business, to find, acquire, distribute, and manage apps for your organization. |
+
| Topic | +Description | +
|---|---|
[Manage access to private store](manage-access-to-private-store.md) |
+You can manage access to your private store in Store for Business. |
+
[App inventory managemement for Windows Store for Business](app-inventory-managemement-for-windows-store-for-business.md) |
+You can manage all apps that you've acquired on your Inventory page. |
+
[Manage private store settings](manage-private-store-settings.md) |
+The private store is a feature in the Store for Business that organizations receive during the sign up process. When admins add apps to the private store, all employees in the organization can view and download the apps. Only online-licensed apps can be distributed from your private store. |
+
[Configure MDM provider](configure-mdm-provider.md) |
+For companies or organizations using mobile device management (MDM) tools, those tools can synchronize with Store for Business inventory to manage apps with offline licenses. Store for Business management tool services work with your third-party management tool to manage content. |
+
| Product version | +Windows 10 support | +
|---|---|
[Microsoft System Center Configuration Manager Technical Preview](http://go.microsoft.com/fwlink/p/?LinkId=613622) |
+Client deployment, upgrade, and management with new and existing features |
+
Configuration Manager and Configuration Manager SP1 |
+Deployment, upgrade, and management with existing features |
+
Configuration Manager 2007 |
+Management with existing features |
+
| Group Policy | +MDM policy | +Description | +
|---|---|---|
Computer Configuration\Administrative Templates\Windows Components\Search\Allow Cortana |
+Experience/AllowCortana |
+Specifies whether employees can use Cortana. +
+Note
+
+Employees can still perform searches even with Cortana turned off. +
+
+ |
+
Computer Configuration\Administrative Templates\Control Panel\Regional and Language Options\Allow input personalization |
+Privacy/AllowInput Personalization |
+Specifies whether to turn on automatic learning, which allows the collection of speech and handwriting patterns, typing history, contacts, and recent calendar information. It is required for the use of Cortana. +
+Important
+
+Cortana won’t work if this setting is turned off (disabled). +
+
+ |
+
None |
+System/AllowLocation |
+Specifies whether to allow app access to the Location service. |
+
Computer Configuration\Administrative Templates\Windows Components\Search\Don't search the web or display web results |
+None |
+Specifies whether search can perform queries on the web and if the web results are displayed in search. +
+Important
+
+Cortana won’t work if this setting is turned off (disabled). +
+
+ |
+
Computer Configuration\Administrative Templates\Windows Components\Search\Allow search and Cortana to use location |
+Search/AllowSearchToUse Location |
+Specifies whether search and Cortana can provide location aware search and Cortana results. +
+Important
+
+Cortana won’t work if this setting is turned off (disabled). +
+
+ |
+
Computer Configuration\Administrative Templates\Windows Components\Search\Set the SafeSearch setting for Search |
+Search/SafeSearch Permissions |
+Specifies what level of safe search (filtering adult content) is required. +
+Note
+
+This setting only applies to Windows 10 Mobile. +
+
+ |
+
User Configuration\Administrative Templates\Windows Components\File Explorer\Turn off display of recent search entries in the File Explorer search box |
+None |
+Specifies whether the search box can suggest recent queries and prevent entries from being stored in the registry for future reference. +
+Important
+
+Cortana won’t work if this setting is turned off (disabled). +
+
+ |
+
User Configuration\Administrative Templates\Start Menu and Taskbar\Do not search for files |
+None |
+Specifies whether the Start menu search box searches for files. +
+Important
+
+Cortana won’t work if this setting is turned off (disabled). +
+
+ |
+
User Configuration\Administrative Templates\Start Menu and Taskbar\Do not search programs and Control Panel items |
+None |
+Specifies whether the Start menu search box searches for programs or Control Panel items. +
+Important
+
+Cortana won’t work if this setting is turned off (disabled). +
+
+ |
+
User Configuration\Administrative Templates\Start Menu and Taskbar\Do not search communications |
+None |
+Specifies whether the Start menu search box searches communications. +
+Important
+
+Cortana won’t work if this setting is turned off (disabled). +
+
+ |
+
| Policy | +Description | +
|---|---|
Allow Cortana |
+Choose whether to let Cortana install and run on the device. +Default: Enabled |
+
Allow search and Cortana to use location |
+Choose whether Cortana and Search can provide location-aware search results. +Default: Enabled |
+
Do not allow web search |
+Choose whether to search the web from Windows Desktop Search. +Default: Disabled |
+
Don't search the web or display web results in Search |
+Choose whether to search the web from Cortana. +Default: Disabled |
+
Set what information is shared in Search |
+Control what information is shared with Bing in Search. |
+
| Policy | +Description | +
|---|---|
Experience/AllowCortana |
+Choose whether to let Cortana install and run on the device. +Default: Allowed |
+
Search/AllowSearchToUseLocation |
+Choose whether Cortana and Search can provide location-aware search results. +Default: Allowed |
+
| Policy | +Description | +
|---|---|
Turn on Suggested Sites |
+Choose whether an employee can configure Suggested Sites. +Default: Enabled +You can also turn this off in the UI by clearing the Internet Options > Advanced > Enable Suggested Sites check box. |
+
Allow Microsoft services to provide enhanced suggestions as the user types in the Address Bar |
+Choose whether an employee can configure enhanced suggestions, which are presented to the employee as they type in the address bar. +Default: Enabled |
+
Turn off the auto-complete feature for web addresses |
+Choose whether auto-complete suggests possible matches when employees are typing web address in the address bar. +Default: Disabled +You can also turn this off in the UI by clearing the Internet Options > Advanced > Use inline AutoComplete in the Internet Explorer Address Bar and Open Dialog check box. |
+
Disable Periodic Check for Internet Explorer software updates |
+Choose whether Internet Explorer periodically checks for a new version. +Default: Enabled |
+
Turn off browser geolocation |
+Choose whether websites can request location data from Internet Explorer. +Default: Disabled |
+
| Policy | +Description | +
|---|---|
Turn off autofill |
+Choose whether employees can use autofill on websites. +Default: Enabled |
+
Allow employees to send Do Not Track headers |
+Choose whether employees can send Do Not Track headers. +Default: Disabled |
+
Turn off password manager |
+Choose whether employees can save passwords locally on their devices. +Default: Enabled |
+
Turn off address bar search suggestions |
+Choose whether the address bar shows search suggestions. +Default: Enabled |
+
Turn off the SmartScreen Filter |
+Choose whether SmartScreen is turned on or off. +Default: Enabled |
+
Open a new tab with an empty tab |
+Choose whether a new tab page appears. +Default: Enabled |
+
Configure corporate Home pages |
+Choose the corporate Home page for domain-joined devices. +Set this to about:blank |
+
| Policy | +Description | +
|---|---|
Browser/AllowAutoFill |
+Choose whether employees can use autofill on websites. +Default: Allowed |
+
Browser/AllowDoNotTrack |
+Choose whether employees can send Do Not Track headers. +Default: Not allowed |
+
Browser/AllowPasswordManager |
+Choose whether employees can save passwords locally on their devices. +Default: Allowed |
+
Browser/AllowSearchSuggestionsinAddressBar |
+Choose whether the address bar shows search suggestions. +Default: Allowed |
+
Browser/AllowSmartScreen |
+Choose whether SmartScreen is turned on or off. +Default: Allowed |
+
| Policy | +Description | +
|---|---|
Download Mode |
+Lets you choose where Delivery Optimization gets or sends updates and apps, including +
|
+
Group ID |
+Lets you provide a Group ID that limits which PCs can share apps and updates. +
+Note
+
+This ID must be a GUID. +
+
+ |
+
Max Cache Age |
+Lets you specify the maximum time (in seconds) that a file is held in the Delivery Optimization cache. +The default value is 259200 seconds (3 days). |
+
Max Cache Size |
+Lets you specify the maximum cache size as a percentage of disk size. +The default value is 20, which represents 20% of the disk. |
+
Max Upload Bandwidth |
+Lets you specify the maximum upload bandwidth (in KB/second) that a device uses across all concurrent upload activity. +The default value is 0, which means unlimited possible bandwidth. |
+
| Policy | +Description | +
|---|---|
DeliveryOptimization/DODownloadMode |
+Lets you configure where Delivery Optimization gets or sends updates and apps, including: +
|
+
DeliveryOptimization/DOGroupID |
+Lets you provide a Group ID that limits which PCs can share apps and updates. +
+Note
+
+This ID must be a GUID. +
+
+ |
+
DeliveryOptimization/DOMaxCacheAge |
+Lets you specify the maximum time (in seconds) that a file is held in the Delivery Optimization cache. +The default value is 259200 seconds (3 days). |
+
DeliveryOptimization/DOMaxCacheSize |
+Lets you specify the maximum cache size as a percentage of disk size. +The default value is 20, which represents 20% of the disk. |
+
DeliveryOptimization/DOMaxUploadBandwidth |
+Lets you specify the maximum upload bandwidth (in KB/second) that a device uses across all concurrent upload activity. +The default value is 0, which means unlimited possible bandwidth. |
+
| Topic | +Description | +
|---|---|
[Update Windows Store for Business account settings](update-windows-store-for-business-account-settings-.md) |
+The Account information page in Windows Store for Business shows information about your organization that you can update, including: country or region, organization name, default domain, and language preference. These are settings in the Azure AD directory that you used when signing up for Store for Business |
+
[Manage user accounts in Windows Store for Business](manage-users-and-groups-in-the-windows-store-for-business.md) |
+Store for Business manages permissions with a set of roles. Currently, you can [assign these roles to individuals in your organization](roles-and-permissions-in-the-windows-store-for-business.md), but not to groups. |
+
| App | +Product ID | +AUMID | +
|---|---|---|
| Alarms and clock | +44F7D2B4-553D-4BEC-A8B7-634CE897ED5F | +Microsoft.WindowsAlarms_8wekyb3d8bbwe!App | +
| Calculator | +B58171C6-C70C-4266-A2E8-8F9C994F4456 | +Microsoft.WindowsCalculator_8wekyb3d8bbwe!App | +
| Camera | +F0D8FEFD-31CD-43A1-A45A-D0276DB069F1 | +Microsoft.WindowsCamera_8wekyb3d8bbwe!App | +
| Contact Support | +0DB5FCFF-4544-458A-B320-E352DFD9CA2B | +Windows.ContactSupport_cw5n1h2txyewy!App | +
| Cortana | +FD68DCF4-166F-4C55-A4CA-348020F71B94 | +Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI | +
| Excel | +EAD3E7C0-FAE6-4603-8699-6A448138F4DC | +Microsoft.Office.Excel_8wekyb3d8bbwe!microsoft.excel | +
| 82A23635-5BD9-DF11-A844-00237DE2DB9E | +Microsoft.MSFacebook_8wekyb3d8bbwe!x82a236355bd9df11a84400237de2db9e | +|
| File Explorer | +C5E2524A-EA46-4F67-841F-6A9465D9D515 | +c5e2524a-ea46-4f67-841f-6a9465d9d515_cw5n1h2txyewy!App | +
| FM Radio | +F725010E-455D-4C09-AC48-BCDEF0D4B626 | +N/A | +
| Get Started | +B3726308-3D74-4A14-A84C-867C8C735C3C | +Microsoft.Getstarted_8wekyb3d8bbwe!App | +
| Groove Music | +D2B6A184-DA39-4C9A-9E0A-8B589B03DEC0 | +Microsoft.ZuneMusic_8wekyb3d8bbwe!Microsoft.ZuneMusic | +
| Maps | +ED27A07E-AF57-416B-BC0C-2596B622EF7D | +Microsoft.WindowsMaps_8wekyb3d8bbwe!App | +
| Messaging | +27E26F40-E031-48A6-B130-D1F20388991A | +Microsoft.Messaging_8wekyb3d8bbwe!x27e26f40ye031y48a6yb130yd1f20388991ax | +
| Microsoft Edge | +395589FB-5884-4709-B9DF-F7D558663FFD | +Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge | +
| Money | +1E0440F1-7ABF-4B9A-863D-177970EEFB5E | +Microsoft.BingFinance_8wekyb3d8bbwe!AppexFinance | +
| Movies and TV | +6AFFE59E-0467-4701-851F-7AC026E21665 | +Microsoft.ZuneVideo_8wekyb3d8bbwe!Microsoft.ZuneVideo | +
| News | +9C3E8CAD-6702-4842-8F61-B8B33CC9CAF1 | +Microsoft.BingNews_8wekyb3d8bbwe!AppexNews | +
| OneDrive | +AD543082-80EC-45BB-AA02-FFE7F4182BA8 | +Microsoft.MicrosoftSkydrive_8wekyb3d8bbwe!App | +
| OneNote | +CA05B3AB-F157-450C-8C49-A1F127F5E71D | +Microsoft.Office.OneNote_8wekyb3d8bbwe!microsoft.onenoteim | +
| Outlook Calendar | +A558FEBA-85D7-4665-B5D8-A2FF9C19799B |
+Microsoft.WindowsCommunicationsApps_8wekyb3d8bbwe!Microsoft.WindowsLive.Calendar |
+
| Outlook Mail | +A558FEBA-85D7-4665-B5D8-A2FF9C19799B |
+Microsoft.WindowsCommunicationsApps_8wekyb3d8bbwe!Microsoft.WindowsLive.Mail |
+
| People | +60BE1FB8-3291-4B21-BD39-2221AB166481 | +Microsoft.People_8wekyb3d8bbwe!xb94d6231y84ddy49a8yace3ybc955e769e85x | +
| Phone (dialer) | +F41B5D0E-EE94-4F47-9CFE-3D3934C5A2C7 | +Microsoft.CommsPhone_8wekyb3d8bbwe!App | +
| Photos | +FCA55E1B-B9A4-4289-882F-084EF4145005 | +Microsoft.Windows.Photos_8wekyb3d8bbwe!App | +
| Podcasts | +C3215724-B279-4206-8C3E-61D1A9D63ED3 | +Microsoft.MSPodcast_8wekyb3d8bbwe!xc3215724yb279y4206y8c3ey61d1a9d63ed3x | +
| Powerpoint | +B50483C4-8046-4E1B-81BA-590B24935798 | +Microsoft.Office.PowerPoint_8wekyb3d8bbwe!microsoft.pptim | +
| Settings | +2A4E62D8-8809-4787-89F8-69D0F01654FB | +2a4e62d8-8809-4787-89f8-69d0f01654fb_8wekyb3d8bbwe!App | +
| Skype | +C3F8E570-68B3-4D6A-BDBB-C0A3F4360A51 | +Microsoft.SkypeApp_kzf8qxf38zg5c!Skype.AppId | +
| Skype Video | +27E26F40-E031-48A6-B130-D1F20388991A | +Microsoft.Messaging_8wekyb3d8bbwe!App | +
| Sports | +0F4C8C7E-7114-4E1E-A84C-50664DB13B17 | +Microsoft.BingSports_8wekyb3d8bbwe!AppexSports | +
| Storage | +5B04B775-356B-4AA0-AAF8-6491FFEA564D | +N/A | +
| Store | +7D47D89A-7900-47C5-93F2-46EB6D94C159 | +Microsoft.WindowsStore_8wekyb3d8bbwe!App | +
| Voice recorder | +7311B9C5-A4E9-4C74-BC3C-55B06BA95AD0 | +Microsoft.WindowsSoundRecorder_8wekyb3d8bbwe!App | +
| Wallet | +587A4577-7868-4745-A29E-F996203F1462 | +Microsoft.MicrosoftWallet_8wekyb3d8bbwe!App | +
| Weather | +63C2A117-8604-44E7-8CEF-DF10BE3A57C8 | +Microsoft.BingWeather_8wekyb3d8bbwe!App | +
| Windows Feedback | +7604089D-D13F-4A2D-9998-33FC02B63CE3 | +Microsoft.WindowsFeedback_8wekyb3d8bbwe!App | +
| Word | +258F115C-48F4-4ADB-9A68-1387E634459B | +Microsoft.Office.Word_8wekyb3d8bbwe!microsoft.word | +
| Xbox | +B806836F-EEBE-41C9-8669-19E243B81B83 | +Microsoft.XboxApp_8wekyb3d8bbwe!Microsoft.XboxApp | +
| + | Global Administrator | +User Administrator | +Billing Administrator | +
|---|---|---|---|
Sign up for Store for Business |
+X |
++ | + |
Assign roles |
+X |
+X |
++ |
Modify company profile settings |
+X |
++ | + |
Manage Store for Business settings |
+X |
++ | + |
Acquire apps |
+X |
++ | X |
+
Distribute apps |
+X |
++ | X |
+
Sign policies and catalogs |
+X |
++ | + |
| + | Admin | +Purchaser | +Device Guard signer | +
|---|---|---|---|
Sign up for Store for Business |
++ | + | + |
Assign roles |
++ | + | + |
Modify company profile settings |
++ | + | + |
Manage Store for Business settings |
+X |
++ | + |
Acquire apps |
+X |
+X |
++ |
Distribute apps |
+X |
+X |
++ |
Sign policies and catalogs |
+X |
++ | + |
Sign Device Guard changes |
++ | + | X |
+
| Topic | +Description | +
|---|---|
[Set up a kiosk on Windows 10 Pro, Enterprise, or Education](set-up-a-kiosk-for-windows-10-for-desktop-editions.md) |
+A single-use device is easy to set up in Windows 10 for desktop editions (Pro, Enterprise, and Education). For a kiosk device to run a Universal Windows app, use the assigned access feature. For a kiosk device (Windows 10 Enterprise or Education) to run a Classic Windows application, use Shell Launcher to set a custom user interface as the shell. |
+
[Set up a kiosk on Windows 10 Mobile or Windows 10 Mobile Enterprise](set-up-a-kiosk-for-windows-10-for-mobile-edition.md) |
+A device in kiosk mode runs a specified app with no access to other device functions, menus, or settings. You configure a device running Windows 10 Mobile or Windows 10 Mobile Enterprise for kiosk mode by using the Apps Corner feature. You can also use the Enterprise Assigned Access configuration service provider (CSP) to configure a kiosk experience. |
+
|
+
|
+
| Main menu | +Sub-menu | +Page name | +
|---|---|---|
| System | ++ | SettingsPageGroupPCSystem | +
| + | Display | +SettingsPageDisplay | +
| + | Notifications and actions | +SettingsPageAppsNotifications | +
| + | Phone | +SettingsPageCalls | +
| + | Message | +SettingsPageMessaging | +
| + | Battery saver | +SettingsPageBatterySaver | +
| + | Storage | +SettingsPageStorageSenseStorageOverview | +
| + | Device encryption | +SettingsPageGroupPCSystemDeviceEncryption | +
| + | Driving mode | +SettingsPageDrivingMode | +
| + | Offline maps | +SettingsPageMaps | +
| + | About | +SettingsPagePCSystemInfo | +
| Devices | ++ | SettingsPageGroupDevices | +
| + | Default camera | +SettingsPagePhotos | +
| + | Bluetooth | +SettingsPagePCSystemBluetooth | +
| + | NFC | +SettingsPagePhoneNFC | +
| + | Mouse | +SettingsPageMouseTouchpad | +
| + | USB | +SettingsPageUsb | +
| Network and wireless | ++ | SettingsPageGroupNetwork | +
| + | Cellular and sim | +SettingsPageNetworkCellular | +
| + | Wi-Fi | +SettingsPageNetworkWiFi | +
| + | Airplane mode | +SettingsPageNetworkAirplaneMode | +
| + | Data usage | +SettingsPageDataSenseOverview | +
| + | Mobile hotspot | +SettingsPageInternetSharing | +
| + | VPN | +SettingsPageNetworkVPN | +
| Personalization | ++ | SettingsPageGroupPersonalization | +
| + | Start | +SettingsPageBackGround | +
| + | Colors | +SettingsPageColors | +
| + | Sounds | +SettingsPageSounds | +
| + | Lock screen | +SettingsPageLockscreen | +
| + | Theme | +SettingsPageStartTheme | +
| Accounts | ++ | SettingsPageGroupAccounts | +
| + | Your account | +SettingsPageAccountsPicture | +
| + | Sign-in options | +SettingsPageAccountsSignInOptions | +
| + | Work access | +SettingsPageAccountsWorkplace | +
| + | Sync your settings | +SettingsPageAccountsSync | +
| + | Kid's corner +(disabled in Assigned Access) |
+SettingsPageKidsCorner | +
| + | Apps corner +(disabled in Assigned Access) |
+SettingsPageAppsCorner | +
| + | Provisioning | +SettingsPageProvisioningPage | +
| Time and language | ++ | SettingsPageGroupTimeRegion | +
| + | Date and time | +SettingsPageTimeRegionDateTime | +
| + | Language | +SettingsPageTimeLanguage | +
| + | Region | +SettingsPageTimeRegion | +
| + | Keyboard | +SettingsPageKeyboard | +
| + | Speech | +SettingsPageSpeech | +
| Ease of access | ++ | SettingsPageGroupEaseOfAccess | +
| + | Narrator | +SettingsPageEaseoOfAccessNarrator | +
| + | Magnifier | +SettingsPageEaseoOfAccessMagnifier | +
| + | High contracts | +SettingsPageEaseoOfAccessHighContrast | +
| + | Closed captions | +SettingsPageEaseoOfAccessClosedCaptioning | +
| + | More options | +SettingsPageEaseoOfAccessMoreOptions | +
| Privacy | ++ | SettingsPageGroupPrivacy | +
| + | Location | +SettingsPagePrivacyLocation | +
| + | Camera | +SettingsPagePrivacyWebcam | +
| + | Microphone | +SettingsPagePrivacyMicrophone | +
| + | Motion | +SettingsPagePrivacyMotionData | +
| + | Speech inking and typing | +SettingsPagePrivacyPersonalization | +
| + | Account info | +SettingsPagePrivacyAccountInfo | +
| + | Contacts | +SettingsPagePrivacyContacts | +
| + | Calendar | +SettingsPagePrivacyCalendar | +
| + | Messaging | +SettingsPagePrivacyMessaging | +
| + | Radios | +SettingsPagePrivacyRadios | +
| + | Background apps | +SettingsPagePrivacyBackgroundApps | +
| + | Accessory app0s | +SettingsPagePrivacyAccessories | +
| + | Advertising ID | +SettingsPagePrivacyAdvertisingId | +
| + | Other devices | +SettingsPagePrivacyCustomPeripherals | +
| + | Feedback and diagnostics | +SettingsPagePrivacySIUFSettings | +
| Update and security | ++ | SettingsPageGroupRestore | +
| + | Phone update | +SettingsPageRestoreMusUpdate | +
| + | Backup | +SettingsPageRestoreOneBackup | +
| + | Find my phone | +SettingsPageFindMyDevice | +
| + | For developers | +SettingsSystemDeveloperOptions | +
| OEM | ++ | SettingsPageGroupExtensibility | +
| + | Extensibility | +SettingsPageExtensibility | +
| Topic | +Description | +
|---|---|
[Prerequisites for Windows Store for Business](prerequisites-for-windows-store-for-business.md) |
+There are a few prerequisites for using Store for Business. |
+
[Sign up for Windows Store for Business](sign-up-for-windows-store-for-business.md) |
+Before you sign up for Store for Business, at a minimum, you'll need an Azure Active Directory (AD) account for your organization, and you'll need to be the global administrator for your organization. If your organization is already using Azure AD, you can go ahead and sign up for Store for Business. If not, we'll help you create an Azure AD account and directory as part of the sign up process. |
+
[Roles and permissions in the Windows Store for Business](roles-and-permissions-in-the-windows-store-for-business.md) |
+The first person to sign in to Store for Business must be a Global Admin of the Azure Active Directory (AD) tenant. Once the Global Admin has signed in, they can give permissions to others employees. |
+
[Settings reference: Windows Store for Business](settings-reference--windows-store-for-business.md) |
+The Store for Business has a group of settings that admins use to manage the store. |
+
| + | Personal devices | +Corporate devices | +
| Ownership | +User | +Organization | +
| Primary use | +Personal | +Work | +
| Deployment | +The primary identity on the device is a personal identity. A Microsoft account is the default option for Windows 10 Mobile. | +The primary identity on the device is an organizational identity. An Azure AD account is the default option for Windows 10 Mobile. | +
| + | Personal identity | +Corporate identity | +
| First account on the device | +Microsoft account | +Azure AD account | +
| Device sign-in | +Users cannot sign in to devices with Azure AD credentials, even if they add the credentials after initial activation with a Microsoft account. | +Users can unlock devices with an Azure AD account. Organizations can block the addition of a personal identity. | +
| User settings and data roaming across devices | +User and app settings roam across devices activated with the same personal identity over personal OneDrive. | +Windows 10 Mobile currently does not support users and app settings roaming over the enterprise cloud. It can block the roaming of personal cloud settings. | +
| Ability to block the use of a personal identity on the device | +No | +Yes | +
| Level of control | +Organization can apply most* restrictive policies to devices, but they cannot remove the Microsoft account from them. Device users can reclaim full control over their devices by un-enrolling them from the organization’s MDM solution. +
+Note
+
+* MDM functionality on personal devices might be limited in the future. +
+
+ |
+Organizations are free to apply the restrictive policies to devices that policy standards and compliance regulations require and prevent the user from un-enrolling the device from the enterprise. | +
| Setting | +Description | +
|---|---|
| Device Password Enabled | +Specifies whether users are required to use a device lock password +
+Note
+
+
+
+
+ |
+
| Allow Simple Device Password | +Whether users can use a simple password (for example, 1111 or 1234) | +
| Alphanumeric Device Password Required | +Whether users need to use an alphanumeric password When configured, Windows prompts the user with a full device keyboard to enter a complex password. When not configured, the user will be able to enter a numeric PIN on the keyboard. | +
| Min Device Password Complex Characters | +The number of password element types (in other words, uppercase letters, lowercase letters, numbers, or punctuation) required to create strong passwords | +
| Device Password Expiration | +The number of days before a password expires (Biometric data does not expire.) | +
| Device Password History | +The number of passwords Windows 10 Mobile remembers in the password history (Users cannot reuse passwords in the history to create new passwords.) | +
| Min Device Password Length | +The minimum number of characters required to create new passwords | +
| Max Inactivity Time Device Lock | +The number of minutes of inactivity before devices are locked and require a password to unlock | +
| Allow Idle Return Without Password | +Whether users are required to re-authenticate when their devices return from a sleep state, before the inactivity time was reached | +
| Max Device Password Failed Attempts | +The number of authentication failures allowed before a device is wiped (A value of zero disables device wipe functionality.) | +
| Screen Timeout While Locked | +The number of minutes before the lock screen times out (This policy influences the device’s power management.) | +
| Allow Screen Timeout While Locked User Configuration | +Whether users can manually configure screen timeout while the device is on the lock screen (Windows 10 Mobile ignores the Screen Timeout While Locked setting if you disable this setting.) | +
| Setting | +Description | +
|---|---|
| SSID | +The case-sensitive name of the Wi-Fi network (service set identifier [SSID]) | +
| Security type | +The type of security the Wi-Fi network uses; can be one of the following authentication types:
+
|
+
| Authentication encryption | +The type of encryption the authentication uses; can be one of the following encryption methods:
+
|
+
| Extensible Authentication Protocol Transport Layer Security (EAP-TLS) | +WPA-Enterprise 802.11 and WPA2-Enterprise 802.11 security types can use EAP-TLS with certificates for authentication | +
| Protected Extensible Authentication Protocol with Microsoft Challenge Handshake Authentication Protocol version 2 (PEAP-MSCHAPv2) | +WPA-Enterprise 802.11 and WPA2-Enterprise 802.11 security types can use PEAP-MSCHAPv2 with a user name and password for authentication | +
| Shared key | +WPA-Personal 802.11 and WPA2-Personal 802.11 security types can use a shared key for authentication. | +
| Proxy | +The configuration of any network proxy that the Wi-Fi connection requires (To specify the proxy server, use its fully qualified domain name [FQDN], Internet Protocol version 4 [IPv4] address, IP version 6 [IPv6] address, or IPvFuture address.) | +
| Disable Internet connectivity checks | +Whether the Wi-Fi connection should check for Internet connectivity | +
| Proxy auto-configuration URL | +A URL that specifies the proxy auto-configuration file | +
| Enable Web Proxy Auto-Discovery Protocol (WPAD) | +Specifies whether WPAD is enabled | +
| Settings | +Configuration | +
|---|---|
| Proxy name | +The unique name of the proxy connection | +
| Proxy ID | +The unique identifier for the proxy connection | +
| Name | +The user-friendly name of the proxy connection | +
| Server address | +The address of the proxy server, which can be the server FQDN or IP address | +
| IP address type | +The IP address type that identifies the proxy server, which can be one of the following values:
+
|
+
| Proxy connection type | +The proxy connection type, which can be one of the following values:
+
|
+
| Ports | +The port information for the proxy connection; includes the following settings:
+
|
+
| Configuration reference | +The connection reference information for the proxy connection. The corporation determines the information in this optional setting. | +
| Setting | +Description | +
|---|---|
| Native VPN protocol profile | +The configuration information when the VPN uses native Windows 10 Mobile VPN protocols (such as IKEv2, PPTP, or L2TP); includes the following settings: +
|
+
| VPN plugin profile | +Windows Store–based VPN plug-ins for the VPN connection; includes the following settings:
+
|
+
| Always on connection | +Whether the VPN connects at user sign-in and stays connected until the user manually disconnects the VPN connection. | +
| App trigger list | +A list of apps that automatically initiate the VPN connection. Each app trigger in the list includes the following settings:
+
|
+
| DNS suffixes | +A comma-separated list of DNS suffixes for the VPN connection. Any DNS suffixes in this list are automatically added to Suffix Search List. | +
| LockDown VPN profile | +Whether this VPN connection is a LockDown profile. A LockDown VPN profile has the following characteristics:
+
You must delete a LockDown VPN profile before you can add, remove, or connect other VPN profiles. |
+
| Name Resolution Policy Table rules | +A list of Name Resolution Policy Table rules for the VPN connection. Each rule in the list includes the following settings:
+
|
+
| Proxy | +Any post connection proxy support required for the VPN connection; includes the following settings:
+
|
+
| Remember credentials | +Whether the VPN connection caches credentials. | +
| Route list | +A list of routes to add to the routing table for the VPN connection. Each route in the list includes the following settings:
+
|
+
| Traffic filter list | +A list of traffic rules that define the traffic that can be sent through the VPN connection. Each rule in the list includes the following settings:
+
|
+
| Trusted network detection | +A comma-separated list of trusted networks that causes the VPN not to connect when the intranet is directly accessible. | +
| Setting | +Description | +
|---|---|
| APN name | +The APN name | +
| IP connection type | +The IP connection type; set to one of the following values:
+
|
+
| LTE attached | +Whether the APN should be attached as part of an LTE Attach | +
| APN class ID | +The globally unique identifier that defines the APN class to the modem | +
| APN authentication type | +The APN authentication type; set to one of the following values:
+
|
+
| User name | +The user account when users select Password Authentication Protocol (PAP), CHAP, or MSCHAPv2 authentication in APN authentication type | +
| Password | +The password for the user account specified in User name | +
| Integrated circuit card ID | +The integrated circuit card ID associated with the cellular connection profile | +
| Setting | +Description | +
|---|---|
| Allow Storage Card | +Whether users can use storage cards for device storage (This setting does not prevent programmatic access to the storage cards.) | +
| Require Device Encryption | +Whether internal storage is encrypted (When a device is encrypted, you cannot use a policy to turn encryption off.) | +
| Encryption method | +Specifies the BitLocker drive encryption method and cipher strength; can be one of the following values:
+
|
+
| Allow Federal Information Processing Standard (FIPS) algorithm policy | +Whether the device allows or disallows the FIPS algorithm policy | +
| SSL cipher suites | +Specifies a list of the allowed cryptographic cipher algorithms for SSL connections | +
| Restrict app data to the system volume | +Specifies whether app data is restricted to the system drive | +
| Restrict apps to the system volume | +Specifies whether apps are restricted to the system drive | +
| Setting | +Description | +
|---|---|
| Allow automatic update | +The automatic update behavior for scanning, downloading, and installing updates; the behavior can be one of the following:
+
|
+
| Allow non Microsoft signed update | +Whether automatic updates will accept updates that entities other than Microsoft have signed | +
| Allow update service | +Whether devices can obtain updates from Windows Update, WSUS, or Windows Store | +
| Monthly security updates deferred | +Whether monthly updates (for example, security patches) are deferred (You can defer updates up to 4 weeks.) | +
| Nonsecurity upgrades deferred | +Whether nonsecurity upgrades are deferred (You can defer upgrades up to 8 months.) | +
| Pause update deferrals | +Whether the device should skip an update cycle (This setting is valid only when you configure devices to defer updates or upgrades.) | +
| Require update approval | +Whether approval is required before updates can be installed on devices (If approval is required, any updates that have an End User License Agreement [EULA] are automatically accepted on the user’s behalf.) | +
| Schedule install time | +The scheduled time at which updates are installed | +
| Scheduled install day | +The schedule of days on which updates are installed | +
| Update deferral period | +How long updates should be deferred | +
| Update service URL | +The name of a WSUS server from which to download updates instead of Windows Update | +
| Upgrade deferral period | +How long Windows 10 Mobile upgrades should be deferred | +
| Setting | +Description | +
|---|---|
| Approved updates | +A list of approved updates. Each update in the list includes the Approved Time setting, which specifies the update approval time. Any approved updates automatically accept EULAs on behalf of users. | +
| Failed updates | +A list of updates that failed during installation. Each update in the list includes the following settings:
+
|
+
| Installed updates | +A list of updates that are installed on the device. | +
| Installable updates | +A list of updates that are available for installation. Each update in the list includes the following settings:
+
|
+
| Pending reboot updates | +A list of updates that require a restart to complete update installation. Each update in the last has the Installed Time setting enabled, which specifies installation time for the update. | +
| Last successful scan time | +The last time a successful update scan was completed. | +
| Defer upgrade | +Whether the upgrade is deferred until the next update cycle. | +
| Start | +Policy | +Setting | +
|---|---|---|
| User tile | +Group Policy: Remove Logoff on the Start menu | ++ |
| Most used | +Group Policy: Remove frequent programs from the Start menu | +Settings > Personalization > Start > Show most used apps | +
Suggestions +-and- +Dynamically inserted app tile |
+MDM: Allow Windows Consumer Features +Group Policy: Computer Configuration\Administrative Templates\Windows Components\Cloud Content\Turn off Microsoft consumer experiences +
+Note
+
+This policy also enables or disables notifications for a user's Microsoft account and app tiles from Microsoft dynamically inserted in the default Start menu. +
+
+ |
+Settings > Personalization > Start > Occasionally show suggestions in Start | +
| Recently added | ++ | Settings > Personalization > Start > Show recently added apps | +
| Pinned folders | ++ | Settings > Personalization > Start > Choose which folders appear on Start | +
| Power | +Group Policy: Remove and prevent access to the Shut Down, Restart, Sleep, and Hibernate commands | +None | +
| All apps | +Group Policy: Remove All Programs list from the Start menu | +None | +
| Start layout | +MDM: Start layout +Group Policy: Start layout +Group Policy: Prevent users from customizing their Start Screen +
+Warning
+
+Start layout can only be applied to a device using the same architecture (32-bit or 64-bit) as the device on which Start layout was created. When a Start screen layout is imported with Group Policy or MDM, the users cannot pin, unpin, or uninstall apps from the Start screen. Users can view and open all apps in the All Apps view, but they cannot pin any apps to the Start screen. +
+
+ |
+None | +
| Jump lists | +Group Policy: Do not keep history of recently opened documents | +Settings > Personalization > Start > Show recently opened items in Jump Lists on Start or the taskbar | +
| Start size | +MDM: Force Start size +Group Policy: Force Start to be either full screen size or menu size |
+Settings > Personalization > Start > Use Start full screen | +
| All Settings | +Group Policy: Prevent changes to Taskbar and Start Menu Settings | +None | +
| Topic | +Description | +
|---|---|
[Sign up and get started](sign-up-and-get-started.md) |
+IT admins can sign up for the Store for Business, and get started working with apps. |
+
[Find and acquire apps](find-and-acquire-apps.md) |
+Use the Store for Business to find apps for your organization. You can also work with developers to create line-of-business apps that are only available to your organization. |
+
[Distribute apps to your employees from the Windows Store for Business](distribute-apps-to-your-employees-from-the-windows-store-for-business.md) |
+Distribute apps to your employees from Store for Business. You can assign apps to employees, or let employees install them from your private store. |
+
[Manage apps](manage-apps.md) |
+Manage settings and access to apps in Store for Business. |
+
[Device Guard signing portal](device-guard-signing-portal.md) |
+Device Guard signing is a Device Guard feature that is available in the Store for Business. It gives admins a single place to sign catalog files and code integrity policies. After admins have created catalog files for unsigned apps and signed the catalog files, they can add the signers to a code integrity policy. You can merge the code integrity policy with your existing policy to include your custom signing certificate. This allows you to trust the catalog files. |
+
[Manage settings in the Windows Store for Business](manage-settings-in-the-windows-store-for-business.md) |
+You can add users and groups, as well as update some of the settings associated with the Azure Active Directory (AD) tenant |
+
[Troubleshoot Windows Store for Business](troubleshoot.md) |
+Troubleshooting topics for Store for Business. |
+
| Term | +Definition | +
|---|---|
ACT Community |
+An online environment that enables ACT users to share issues and solution data with other registered ACT users. |
+
ACT Log Processing Service (LPS) |
+The service that processes the log files uploaded from your client computers, adding the information to your ACT database. |
+
AppHelp message |
+A type of compatibility fix. An AppHelp message is designed to appear when a user starts an application that has compatibility issues. The message can prevent the application from starting, or simply provide information about compatibility issues in the application. |
+
Application Compatibility Manager (ACM) |
+The user interface that enables you to view reports generated from the ACT database. This is also where you create data-collection packages. |
+
Compatibility Administrator |
+A tool that enables you to create and deploy compatibility fixes, compatibility modes, and AppHelp messages, to resolve your compatibility issues. |
+
compatibility fix |
+A small piece of code that intercepts API calls from applications, transforming them so that Windows will provide the same product support for the application as previous versions of the operating system. Previously known as a "shim". |
+
compatibility mode |
+Group of compatibility fixes found to resolve many common application compatibility issues. |
+
compatibility solution |
+The solution to a known compatibility issue, as entered by the user, Microsoft, or a vendor. |
+
data-collection package |
+A Windows installer (.msi) file created by Application Compatibility Manager (ACM) for deploying to each of your client computers. Data-collection packages include inventory collection packages and runtime analysis packages. |
+
deployment |
+The process of distributing and installing a software program throughout an entire organization. A deployment is not the same as a pilot, which is where you provide the software application to a smaller group of users to identify and evaluate problems that might occur during the actual deployment. |
+
independent software vendor (ISV) |
+An individual or an organization that independently creates computer software. |
+
inventory-collector package |
+A package that examines each of your organization's computers to identify the installed applications and system information. You can view the results on the Analyze screen in ACM. |
+
Microsoft Compatibility Exchange |
+A web service that transfers compatibility information between Microsoft and the ACT database. |
+
runtime-analysis package |
+A data-collection package that you deploy to computers in a test environment for compatibility testing. The runtime-analysis package includes tools for monitoring applications for compatibility issues and submitting compatibility feedback. |
+
session 0 |
+The session that is used for all of the system services. Previously, users could run in Session 0 without issues; however, this was changed in Windows Vista so that all users are now required to run in Session 1 or later. |
+
shim |
+See Other Term: compatibility fix |
+
User Account Control (UAC) |
+A security feature that helps prevent unauthorized changes to a computer, by asking the user for permission or administrator credentials before performing actions that could potentially affect the computer's operation or that change settings that affect multiple users. |
+
| Topic | +Description | +
|---|---|
[Toolbar Icons in ACM](toolbar-icons-in-acm-win-8.md) |
+The following table shows icons that appear on toolbars and navigational elements in Application Compatibility Manager (ACM). |
+
[Ratings Icons in ACM](ratings-icons-in-acm.md) |
+Compatibility ratings can originate from Microsoft, the application vendor, your organization, and from the Application Compatibility Toolkit (ACT) community. |
+
[Activating and Closing Windows in ACM](activating-and-closing-windows-in-acm.md) |
+The Windows dialog box shows the windows that are open in Application Compatibility Manager (ACM). |
+
[Settings for ACM](settings-for-acm.md) |
+This section provides information about settings that you can configure in Application Compatibility Manager (ACM). |
+
| Field | +Description | +
|---|---|
Title |
+ Can be up to 100 characters in length. |
+
Solution Type |
+ You must select a value from the list. |
+
Solution Details |
+ Information about your solution, including the steps to reproduce your fix. |
+
Solution Details URL |
+ URL for a page that shows more information about the solution. |
+
| Field | +Description | +
|---|---|
Title |
+ Can be up to 256 characters in length. |
+
Priority |
+ You must select a value from the list. |
+
Severity |
+ You must select a value from the list. |
+
Symptom |
+ You must select a value from the list. |
+
Cause |
+ You must select a value from the list. |
+
Affected Operating Systems |
+ Operating systems on which the issue occurs. You must select at least one operating system. |
+
Issue Description |
+ Description of the issue, including the steps to reproduce the problem. |
+
Link to More Information |
+ URL for a page that shows more information about the issue. |
+
| Topic | +Description | +
|---|---|
[Viewing Your Compatibility Reports](viewing-your-compatibility-reports.md) |
+This section describes the compatibility reports in Application Compatibility Manager (ACM) and how you can work with the reports. |
+
[Organizing Your Compatibility Data](organizing-your-compatibility-data.md) |
+This section provides step-by-step instructions for organizing your compatibility data in Application Compatibility Manager (ACM). |
+
[Filtering Your Compatibility Data](filtering-your-compatibility-data.md) |
+You can use Query Builder to filter your compatibility-issue data or reports by selecting specific restriction criteria. |
+
[Sending and Receiving Compatibility Data](sending-and-receiving-compatibility-data.md) |
+The Microsoft® Compatibility Exchange is a web service that propagates application compatibility issues between various data sources, for example Microsoft Corporation, independent software vendors (ISVs) and the ACT Community. This process involves checking for updated compatibility information from Microsoft over the Internet. You can send and receive data to keep Application Compatibility Manager (ACM) updated with the latest compatibility information. |
+
| Topic | +Description | +
|---|---|
[Welcome to ACT](welcome-to-act.md) |
+The Application Compatibility Toolkit (ACT) helps you determine whether the applications, devices, and computers in your organization are compatible with versions of the Windows® operating system. With ACT, you can obtain compatibility information from Microsoft and software vendors, identify compatibility issues within your own organization, and share compatibility ratings with other ACT users. The tools in ACT help you analyze and mitigate compatibility issues before deploying a version of Windows to your organization. |
+
[Configuring ACT](configuring-act.md) |
+This section provides information about setting up the Application Compatibility Toolkit (ACT) in your organization. |
+
[Using ACT](using-act.md) |
+This section describes how to use the Application Compatibility Toolkit (ACT) in your organization. |
+
[Troubleshooting ACT](troubleshooting-act.md) |
+This section provides troubleshooting information for the Application Compatibility Toolkit (ACT). |
+
[ACT User Interface Reference](act-user-interface-reference.md) |
+This section contains information about the user interface for Application Compatibility Manager (ACM), which is a tool in the Application Compatibility Toolkit (ACT). |
+
[ACT Product and Documentation Resources](act-product-and-documentation-resources.md) |
+The following sections provide links to resources and reference material for the Application Compatibility Toolkit (ACT). |
+
[ACT Glossary](act-glossary.md) |
+The following table lists terms and definitions used by the Application Compatibility Toolkit (ACT). |
+
[Compatibility Fixes for Windows 10, Windows 8, Windows 7, and Windows Vista](compatibility-fixes-for-windows-8-windows-7-and-windows-vista.md) |
+You can fix some compatibility issues that are due to the changes made between Windows operating system versions. These issues can include User Account Control (UAC) restrictions. |
+
| Tab | +Information | +
|---|---|
Assessment |
+Shows the compatibility ratings for the application from the application vendor, your internal organization, and the ACT Community. +For more information, see [Selecting Your Compatibility Rating](selecting-your-compatibility-rating.md). |
+
Issues |
+For each issue associated with the selected application, shows: +
For more information, see [Creating and Editing Issues and Solutions](creating-and-editing-issues-and-solutions.md). |
+
Application Properties |
+Shows the following properties for the selected application: +
|
+
Computers |
+Shows the following information for each of the computers that have the specified application installed: +
|
+
Labels |
+Shows the label for the selected application. +For information about labels, see [Labeling Data in ACM](labeling-data-in-acm.md). |
+
Feedback |
+Shows feedback that your testers have submitted to the ACT database for the selected application. |
+
| Options menu command | +Description | +
|---|---|
Filter Noise |
+ Filters noise from the issues. +This command is selected by default. |
+
Load Noise Filter File |
+ Opens the Open Noise Filter File dialog box, in which you can load an existing noise filter (.xml) file. |
+
Export Noise Filter File |
+ Opens the Save Noise Filter File dialog box, in which you can save filter settings as a noise filter (.xml) file. |
+
Only Display Records with Application Name in StackTrace |
+ Filters out records that do not have the application name in the stack trace. +However, because the SUA tool captures only the first 32 stack frames, this command can also filter out real issues with the application where the call stack is deeper than 32 frames. |
+
Show More Details in StackTrace |
+ Shows additional stack frames that are related to the SUA tool, but not related to the diagnosed application. |
+
Warn Before Deleting AppVerifier Logs |
+ Displays a warning message before the SUA tool deletes all of the existing SUA-related log files on the computer. +This command is selected by default. |
+
Logging |
+ Provides the following logging-related options: +
To maintain a manageable file size, we recommend that you do not select the option to show informational messages. |
+
| Attribute | +Description | +Data type | +
|---|---|---|
APP_NAME |
+Name of the application. |
+String |
+
DATABASE_GUID |
+Unique ID for your compatibility database. |
+String |
+
DATABASE_INSTALLED |
+Specifies if you have installed the database. |
+Boolean |
+
DATABASE_NAME |
+Descriptive name of your database. |
+String |
+
DATABASE_PATH |
+Location of the database on your computer. |
+String |
+
FIX_COUNT |
+Number of compatibility fixes applied to a specific application. |
+Integer |
+
FIX_NAME |
+Name of your compatibility fix. |
+String |
+
MATCH_COUNT |
+Number of matching files for a specific, fixed application. |
+Integer |
+
MATCHFILE_NAME |
+Name of a matching file used to identify a specific, fixed application. |
+String |
+
MODE_COUNT |
+Number of compatibility modes applied to a specific, fixed application. |
+Integer |
+
MODE_NAME |
+Name of your compatibility mode. |
+String |
+
PROGRAM_APPHELPTYPE |
+Type of AppHelp message applied to an entry. The value can be 1 or 2, where 1 enables the program to run and 2 blocks the program. |
+Integer |
+
PROGRAM_DISABLED |
+Specifies if you disabled the compatibility fix for an application. If True, Compatibility Administrator does not apply the fixes to the application. |
+Boolean |
+
PROGRAM_GUID |
+Unique ID for an application. |
+String |
+
PROGRAM_NAME |
+Name of the application that you are fixing. |
+String |
+
| Symbol | +Description | +Data type | +Precedence | +
|---|---|---|---|
> |
+Greater than |
+Integer or string |
+1 |
+
>= |
+Greater than or equal to |
+Integer or string |
+1 |
+
< |
+Less than |
+Integer or string |
+1 |
+
<= |
+Less than or equal to |
+Integer or string |
+1 |
+
<> |
+Not equal to |
+Integer or string |
+1 |
+
= |
+Equal to |
+Integer, string, or Boolean |
+1 |
+
HAS |
+A special SQL operator used to check if the left-hand operand contains a substring specified by the right-hand operand. |
+Left-hand operand. MATCHFILE_NAME, MODE_NAME, FIX_NAME +
+Note
+
+Only the HAS operator can be applied to the MATCHFILE_NAME, MODE_NAME, and FIX_NAME attributes. +
+
+
+Right-hand operand. String |
+1 |
+
OR |
+Logical OR operator |
+Boolean |
+2 |
+
AND |
+Logical AND operator |
+Boolean |
+2 |
+
| Section | +Settings | +
|---|---|
| Network | +These settings configure the network connections for Chromebook devices and include the following settings categories: +
|
+
| Mobile | +These settings configure and manage companion devices (such as smartphones or tablets) that are used in conjunction with the Chromebook devices and include the following settings categories: +
|
+
| Chrome management | +These settings configure and manage companion devices (such as smartphones or tablets) that are used in conjunction with the Chromebook devices and include the following settings categories: +
|
+
| Section | +Settings | +
|---|---|
Basic settings |
+These settings configure password management and whether or not two-factor authentication (2FA) is configured. You can set the minimum password length, the maximum password length, if non-admin users can recover their own passwords, and enable 2FA. +Record these settings and use them to help configure your on-premises Active Directory or Azure Active Directory (Azure AD) to mirror the current behavior of your Chromebook environment. |
+
Password monitoring |
+This section is used to monitor the strength of user passwords. You don’t need to migrate any settings in this section. |
+
API reference |
+This section is used to enable access to various Google Apps Administrative APIs. You don’t need to migrate any settings in this section. |
+
Set up single sign-on (SSO) |
+This section is used to configure SSO for Google web-based apps (such as Google Apps Gmail or Google Apps Calendar). While you don’t need to migrate any settings in this section, you probably will want to configure Azure Active Directory synchronization to replace Google-based SSO. |
+
Advanced settings |
+This section is used to configure administrative access to user data and to configure the Google Secure Data Connector (which allows Google Apps to access data on your local network). You don’t need to migrate any settings in this section. |
+
| If you plan to... | +On-premises AD DS | +Azure AD | +Hybrid | +
|---|---|---|---|
| Use Office 365 | ++ | X | +X | +
| Use Intune for management | ++ | X | +X | +
| Use System Center 2012 R2 Configuration Manager for management | +X | ++ | X | +
| Use Group Policy for management | +X | ++ | X | +
| Have devices that are domain-joined | +X | ++ | X | +
| Allow faculty and students to Bring Your Own Device (BYOD) which are not domain-joined | ++ | X | +X | +
| Desired feature | +Windows provisioning packages | +Group Policy | +Configuration Manager | +Intune | +MDT | +Windows Software Update Services | +
|---|---|---|---|---|---|---|
| Deploy operating system images | +X | ++ | X | ++ | X | ++ |
| Deploy apps during operating system deployment | +X | ++ | X | ++ | X | ++ |
| Deploy apps after operating system deployment | +X | +X | +X | ++ | + | + |
| Deploy software updates during operating system deployment | ++ | + | X | ++ | X | ++ |
| Deploy software updates after operating system deployment | +X | +X | +X | +X | ++ | X | +
| Support devices that are domain-joined | +X | +X | +X | +X | +X | ++ |
| Support devices that are not domain-joined | +X | ++ | + | X | +X | ++ |
| Use on-premises resources | +X | +X | +X | ++ | X | ++ |
| Use cloud-based services | ++ | + | + | X | ++ | + |
| Product or technology | +Resources | +
|---|---|
| DHCP | +
|
+
| DNS | +
|
+
| Product or technology | +Resources | +
|---|---|
| AD DS | +
|
+
| Azure AD | +
|
+
| Management system | +Resources | +
|---|---|
| Windows provisioning packages | +
|
+
| Group Policy | +
|
+
| Configuration Manager | +
|
+
| Intune | +
|
+
| MDT | +
|
+
| Management system | +Resources | +
|---|---|
| Group Policy | +
|
+
| Configuration Manager | +
|
+
| Intune | +
|
+
| Topic | +Description | +
|---|---|
[Using the Compatibility Administrator Tool](using-the-compatibility-administrator-tool.md) |
+This section provides information about using the Compatibility Administrator tool. |
+
[Managing Application-Compatibility Fixes and Custom Fix Databases](managing-application-compatibility-fixes-and-custom-fix-databases.md) |
+This section provides information about managing your application-compatibility fixes and custom-compatibility fix databases. This section explains the reasons for using compatibility fixes and how to deploy custom-compatibility fix databases. |
+
[Using the Sdbinst.exe Command-Line Tool](using-the-sdbinstexe-command-line-tool.md) |
+You must deploy your customized database (.sdb) files to other computers in your organization before your compatibility fixes, compatibility modes, and AppHelp messages are applied. You can deploy your customized database files in several ways, including by using a logon script, by using Group Policy, or by performing file copy operations. |
+
| Fix | +Fix Description | +
|---|---|
8And16BitAggregateBlts |
+Applications that are mitigated by 8/16-bit mitigation can exhibit performance issues. This layer aggregates all the blt operations and improves performance. |
+
8And16BitDXMaxWinMode |
+Applications that use DX8/9 and are mitigated by the 8/16-bit mitigation are run in a maximized windowed mode. This layer mitigates applications that exhibit graphical corruption in full screen mode. |
+
8And16BitGDIRedraw |
+This fix repairs applications that use GDI and that work in 8-bit color mode. The application is forced to repaint its window on RealizePalette. |
+
AccelGdipFlush |
+This fix increases the speed of GdipFlush, which has perf issues in DWM. |
+
AoaMp4Converter |
+This fix resolves a display issue for the AoA Mp4 Converter. |
+
BIOSRead |
+This problem is indicated when an application cannot access the Device\PhysicalMemory object beyond the kernel-mode drivers, on any of the Windows Server® 2003 operating systems. +The fix enables OEM executable (.exe) files to use the GetSystemFirmwareTable function instead of the NtOpenSection function when the BIOS is queried for the \\Device\Physical memory information.. |
+
BlockRunasInteractiveUser |
+This problem occurs when InstallShield creates installers and uninstallers that fail to complete and that generate error messages or warnings. +The fix blocks InstallShield from setting the value of RunAs registry keys to InteractiveUser Because InteractiveUser no longer has Administrator rights. +
+Note
+
+For more detailed information about this application fix, see [Using the BlockRunAsInteractiveUser Fix](http://go.microsoft.com/fwlink/p/?LinkId=690328). +
+
+ |
+
ChangeFolderPathToXPStyle |
+This fix is required when an application cannot return shell folder paths when it uses the SHGetFolder API. +The fix intercepts the SHGetFolder path request to the common appdata file path and returns the Windows® XP-style file path instead of the Windows Vista-style file path. |
+
ClearLastErrorStatusonIntializeCriticalSection |
+This fix is indicated when an application fails to start. +The fix modifies the InitializeCriticalSection function call so that it checks the NTSTATUS error code, and then sets the last error to ERROR_SUCCESS. |
+
CopyHKCUSettingsFromOtherUsers |
+This problem occurs when an application's installer must run in elevated mode and depends on the HKCU settings that are provided for other users. +The fix scans the existing user profiles and tries to copy the specified keys into the HKEY_CURRENT_USER registry area. +You can control this fix further by entering the relevant registry keys as parameters that are separated by the ^ Symbol; for example:
+Note
+
+For more detailed information about this application fix, see [Using the CopyHKCUSettingsFromOtherUsers Fix](http://go.microsoft.com/fwlink/p/?LinkId=690329). +
+
+ |
+
CorrectCreateBrushIndirectHatch |
+The problem is indicated by an access violation error message that displays and when the application fails when you select or crop an image. +The fix corrects the brush style hatch value, which is passed to the CreateBrushIndirect() function and enables the information to be correctly interpreted. |
+
CorrectFilePaths |
+The problem is indicated when an application tries to write files to the hard disk and is denied access or receives a file not found or path not found error message. +The fix modifies the file path names to point to a new location on the hard disk. +
+Note
+
+For more detailed information about the CorrectFilePaths application fix, see [Using the CorrectFilePaths Fix](http://go.microsoft.com/fwlink/p/?LinkId=690330). We recommend that you use this fix together with the CorrectFilePathsUninstall fix if you are applying it to a setup installation file. +
+
+ |
+
CorrectFilePathsUninstall |
+This problem occurs when an uninstalled application leaves behind files, directories, and links. +The fix corrects the file paths that are used by the uninstallation process of an application. +
+Note
+
+For more detailed information about this fix, see [Using the CorrectFilePathsUninstall Fix](http://go.microsoft.com/fwlink/p/?LinkId=690331). We recommend that you use this fix together with the CorrectFilePaths fix if you are applying it to a setup installation file. +
+
+ |
+
CorrectShellExecuteHWND |
+This problem occurs when you start an executable (.exe) and a taskbar item blinks instead of an elevation prompt being opened, or when the application does not provide a valid HWND value when it calls the ShellExecute(Ex) function. +The fix intercepts the ShellExecute(Ex) calls, and then inspects the HWND value. If the value is invalid, this fix enables the call to use the currently active HWND value. +
+Note
+
+For more detailed information about the CorrectShellExecuteHWND application fix, see [Using the CorrectShellExecuteHWND Fix](http://go.microsoft.com/fwlink/p/?LinkId=690332). +
+
+ |
+
CustomNCRender |
+This fix instructs DWM to not render the non-client area, thereby forcing the application to do its own NC rendering. This often gives windows an XP look. |
+
DelayApplyFlag |
+This fix applies a KERNEL, USER, or PROCESS flag if the specified DLL is loaded. +You can control this fix further by typing the following command at the command prompt: +DLL_Name;Flag_Type;Hexidecimal_Value +Where the DLL_Name is the name of the specific DLL, including the file extension. Flag_Type is KERNEL, USER, or PROCESS, and a Hexidecimal_Value, starting with 0x and up to 64-bits long. +
+Note
+
+The PROCESS flag type can have a 32-bit length only. You can separate multiple entries with a backslash (). +
+
+ |
+
DeprecatedServiceShim |
+The problem is indicated when an application tries to install a service that has a dependency on a deprecated service. An error message displays. +The fix intercepts the CreateService function calls and removes the deprecated dependency service from the lpDependencies parameter. +You can control this fix further by typing the following command at the command prompt: +Deprecated_Service\App_Service/Deprecated_Service2 \App_Service2 +Where Deprecated_Service is the name of the service that has been deprecated and App_Service is the name of the specific application service that is to be modified; for example, NtLmSsp\WMI. +
+Note
+
+If you do not provide an App_Service name, the deprecated service will be removed from all newly created services. +
+
+
+
+Note
+
+You can separate multiple entries with a forward slash (/). +
+
+ |
+
DirectXVersionLie |
+This problem occurs when an application fails because it does not find the correct version number for DirectX®. +The fix modifies the DXDIAGN GetProp function call to return the correct DirectX version. +You can control this fix further by typing the following command at the command prompt: +MAJORVERSION.MINORVERSION.LETTER +For example, |
+
DetectorDWM8And16Bit |
+This fix offeres mitigation for applications that work in 8/16-bit display color mode because these legacy color modes are not supported in Windows 8 . |
+
Disable8And16BitD3D |
+This fix improves performance of 8/16-bit color applications that render using D3D and do not mix directdraw. |
+
Disable8And16BitModes |
+This fix disables 8/16-bit color mitigation and enumeration of 8/16-bit color modes. |
+
DisableDWM |
+The problem occurs when some objects are not drawn or object artifacts remain on the screen in an application. +The fix temporarily disables the Windows Aero menu theme functionality for unsupported applications. +
+Note
+
+For more detailed information about this application fix, see [Using the DisableDWM Fix]( http://go.microsoft.com/fwlink/p/?LinkId=690334). +
+
+ |
+
DisableFadeAnimations |
+The problem is indicated when an application fade animations, buttons, or other controls do not function properly. +The fix disables the fade animations functionality for unsupported applications. |
+
DisableThemeMenus |
+The problem is indicated by an application that behaves unpredictably when it tries to detect and use the correct Windows settings. +The fix temporarily disables the Windows Aero menu theme functionality for unsupported applications. |
+
DisableWindowsDefender |
+The fix disables Windows Defender for security applications that do not work with Windows Defender. |
+
DWM8And16BitMitigation |
+The fix offers mitigation for applications that work in 8/16-bit display color mode because these legacy color modes are not supported in Windows 8. |
+
DXGICompat |
+The fix allows application-specific compatibility instructions to be passed to the DirectX engine. |
+
DXMaximizedWindowedMode |
+Applications that use DX8/9 are run in a maximized windowed mode. This is required for applications that use GDI/DirectDraw in addition to Direct3D. |
+
ElevateCreateProcess |
+The problem is indicated when installations, de-installations, or updates fail because the host process calls the CreateProcess function and it returns an ERROR_ELEVATION_REQUIRED error message. +The fix handles the error code and attempts to recall the CreateProcess function together with requested elevation. If the fixed application already has a UAC manifest, the error code will be returned unchanged. +
+Note
+
+For more detailed information about this application fix, see [Using the ElevateCreateProcess Fix](http://go.microsoft.com/fwlink/p/?LinkId=690335). +
+
+ |
+
EmulateOldPathIsUNC |
+The problem occurs when an application fails because of an incorrect UNC path. +The fix changes the PathIsUNC function to return a value of True for UNC paths in Windows. |
+
EmulateGetDiskFreeSpace |
+The problem is indicated when an application fails to install or to run, and it generates an error message that there is not enough free disk space to install or use the application, even though there is enough free disk space to meet the application requirements. +The fix determines the amount of free space, so that if the amount of free space is larger than 2 GB, the compatibility fix returns a value of 2 GB, but if the amount of free space is smaller than 2 GB, the compatibility fix returns the actual free space amount. +
+Note
+
+For more detailed information about this application fix, see [Using the EmulateGetDiskFreeSpace Fix](http://go.microsoft.com/fwlink/p/?LinkId=690336). +
+
+ |
+
EmulateSorting |
+The problem occurs when an application experiences search functionality issues. +The fix forces applications that use the CompareStringW/LCMapString sorting table to use an older version of the table. +
+Note
+
+For more detailed information about this e application fix, see [Using the EmulateSorting Fix](http://go.microsoft.com/fwlink/p/?LinkId=690337). +
+
+ |
+
EmulateSortingWindows61 |
+The fix emulates the sorting order of Windows 7 and Windows Server 2008 R2 for various APIs. |
+
EnableRestarts |
+The problem is indicated when an application and computer appear to hang because processes cannot end to allow the computer to complete its restart processes. +The fix enables the computer to restart and finish the installation process by verifying and enabling that the SeShutdownPrivilege service privilege exists. +
+Note
+
+For more detailed information about this application fix, see [Using the EnableRestarts Fix](http://go.microsoft.com/fwlink/p/?LinkId=690338). +
+
+ |
+
ExtraAddRefDesktopFolder |
+The problem occurs when an application invokes the Release() method too many times and causes an object to be prematurely destroyed. +The fix counteracts the application's tries to obtain the shell desktop folder by invoking the AddRef() method on the Desktop folder, which is returned by the SHGetDesktopFolder function. |
+
FailObsoleteShellAPIs |
+The problem occurs when an application fails because it generated deprecated API calls. +The fix either fully implements the obsolete functions or implements the obsolete functions with stubs that fail. +
+Note
+
+You can type FailAll=1 at the command prompt to suppress the function implementation and force all functions to fail. +
+
+ |
+
FailRemoveDirectory |
+The problem occurs when an application uninstallation process does not remove all of the application files and folders. +This fix fails calls to RemoveDirectory() when called with a path matching the one specified in the shim command-line. Only a single path is supported. The path can contain environment variables, but must be an exact path – no partial paths are supported. +The fix can resolve an issue where an application expects RemoveDirectory() to delete a folder immediately even though a handle is open to it. |
+
FakeLunaTheme |
+The problem occurs when a theme application does not properly display: the colors are washed out or the user interface is not detailed. +The fix intercepts the GetCurrentThemeName API and returns the value for the Windows XP default theme, (Luna). +
+Note
+
+For more detailed information about the FakeLunaTheme application fix, see [Using the FakeLunaTheme Fix](http://go.microsoft.com/fwlink/p/?LinkId=690339). +
+
+ |
+
FlushFile |
+This problem is indicated when a file is updated and changes do not immediately appear on the hard disk. Applications cannot see the file changes. +The fix enables the WriteFile function to call to the FlushFileBuffers APIs, which flush the file cache onto the hard disk. |
+
FontMigration |
+The fix replaces an application-requested font with a better font selection, to avoid text truncation. |
+
ForceAdminAccess |
+The problem occurs when an application fails to function during an explicit administrator check. +The fix allows the user to temporarily imitate being a part of the Administrators group by returning a value of True during the administrator check. +
+Note
+
+For more detailed information about this application fix, see [Using the ForceAdminAccess Fix](http://go.microsoft.com/fwlink/p/?LinkId=690342). +
+
+ |
+
ForceInvalidateOnClose |
+The fix invalidates any windows that exist under a closing or hiding window for applications that rely on the invalidation messages. |
+
ForceLoadMirrorDrvMitigation |
+The fix loads the Windows 8 mirror driver mitigation for applications where the mitigation is not automatically applied. |
+
FreestyleBMX |
+The fix resolves an application race condition that is related to window message order. |
+
GetDriveTypeWHook |
+The application presents unusual behavior during installation; for example, the setup program states that it cannot install to a user-specified location. +The fix changes GetDriveType() so that only the root information appears for the file path. This is required when an application passes an incomplete or badly-formed file path when it tries to retrieve the drive type on which the file path exists. |
+
GlobalMemoryStatusLie |
+The problem is indicated by a Computer memory full error message that displays when you start an application. +The fix modifies the memory status structure, so that it reports a swap file that is 400 MB, regardless of the true swap file size. |
+
HandleBadPtr |
+The problem is indicated by an access violation error message that displays because an API is performing pointer validation before it uses a parameter. +The fix supports using lpBuffer validation from the InternetSetOptionA and InternetSetOptionW functions to perform the additional parameter validation. |
+
HandleMarkedContentNotIndexed |
+The problem is indicated by an application that fails when it changes an attribute on a file or directory. +The fix intercepts any API calls that return file attributes and directories that are invoked from the %TEMP% directory, and resets the FILE_ATTRIBUTE_NOT_CONTENT_INDEXED attribute to its original state. |
+
HeapClearAllocation |
+The problem is indicated when the allocation process shuts down unexpectedly. +The fix uses zeros to clear out the heap allocation for an application. |
+
IgnoreAltTab |
+The problem occurs when an application fails to function when special key combinations are used. +The fix intercepts the RegisterRawInputDevices API and prevents the delivery of the WM_INPUT messages. This delivery failure forces the included hooks to be ignored and forces DInput to use Windows-specific hooks. +
+Note
+
+For more detailed information about this application fix, see [Using the IgnoreAltTab Fix](http://go.microsoft.com/fwlink/p/?LinkId=690343). +
+
+ |
+
IgnoreChromeSandbox |
+The fix allows Google Chrome to run on systems that have ntdll loaded above 4GB. |
+
IgnoreDirectoryJunction |
+The problem is indicated by a read or access violation error message that displays when an application tries to find or open files. +The fix links the FindNextFileW, FindNextFileA, FindFirstFileExW, FindFirstFileExA, FindFirstFileW and FindFirstFileA APIs to prevent them from returning directory junctions. +
+Note
+
+Symbolic links appear starting in Windows Vista. +
+
+ |
+
IgnoreException |
+The problem is indicated when an application stops functioning immediately after it starts, or the application starts with only a cursor appearing on the screen. +The fix enables the application to ignore specified exceptions. By default, this fix ignores privileged-mode exceptions; however, it can be configured to ignore any exception. +You can control this fix further by typing the following command at the command prompt: +Exception1;Exception2 +Where Exception1 and Exception2 are specific exceptions to be ignored. For example: ACCESS_VIOLATION_READ:1;ACCESS_VIOLATION_WRITE:1. +
+Important
+
+You should use this compatibility fix only if you are certain that it is acceptable to ignore the exception. You might experience additional compatibility issues if you choose to incorrectly ignore an exception. +
+
+
+
+Note
+
+For more detailed information about this application fix, see [Using the IgnoreException Fix](http://go.microsoft.com/fwlink/p/?LinkId=690344). +
+
+ |
+
IgnoreFloatingPointRoundingControl |
+This fix enables an application to ignore the rounding control request and to behave as expected in previous versions of the application. +Before floating point SSE2 support in the C runtime library, the rounding control request was being ignored which would use round to nearest option by default. This shim ignores the rounding control request to support applications relying on old behavior. |
+
IgnoreFontQuality |
+The problem occurs when application text appears to be distorted. +The fix enables color-keyed fonts to properly work with anti-aliasing. |
+
IgnoreMessageBox |
+The problem is indicated by a message box that displays with debugging or extraneous content when the application runs on an unexpected operating system. +The fix intercepts the MessageBox* APIs and inspects them for specific message text. If matching text is found, the application continues without showing the message box. +
+Note
+
+For more detailed information about this application fix, see [Using the IgnoreMessageBox Fix](http://go.microsoft.com/fwlink/p/?LinkId=690345). +
+
+ |
+
IgnoreMSOXMLMF |
+The problem is indicated by an error message that states that the operating system cannot locate the MSVCR80D.DLL file. +The fix ignores the registered MSOXMLMF.DLL object, which Microsoft® Office 2007 loads into the operating system any time that you load an XML file, and then it fails the CoGetClassObject for its CLSID. This compatibility fix will just ignore the registered MSOXMLMF and fail the CoGetClassObject for its CLSID. |
+
IgnoreSetROP2 |
+The fix ignores read-modify-write operations on the desktop to avoid performance issues. |
+
InstallComponent |
+The fix prompts the user to install.Net 3.5 or .Net 2.0 because .Net is not included with Windows 8. |
+
LoadLibraryRedirect |
+The fix forces an application to load system versions of libraries instead of loading redistributable versions that shipped with the application. |
+
LocalMappedObject |
+The problem occurs when an application unsuccessfully tries to create an object in the Global namespace. +The fix intercepts the function call to create the object and replaces the word Global with Local. +
+Note
+
+For more detailed information about this application fix, see [Using the LocalMappedObject Fix](http://go.microsoft.com/fwlink/p/?LinkId=690346). +
+
+ |
+
MakeShortcutRunas |
+The problem is indicated when an application fails to uninstall because of access-related errors. +The fix locates any RunDLL.exe-based uninstallers and forces them to run with different credentials during the application installation. After it applies this fix, the installer will create a shortcut that specifies a matching string to run during the application installation, thereby enabling the uninstallation to occur later. +
+Note
+
+For more detailed information about this application fix, see [Using the MakeShortcutRunas Fix]( http://go.microsoft.com/fwlink/p/?LinkId=690347) +
+
+ |
+
ManageLinks |
+The fix intercepts common APIs that are going to a directory or to an executable (.exe) file, and then converts any symbolic or directory junctions before passing it back to the original APIs. |
+
MirrorDriverWithComposition |
+The fix allows mirror drivers to work properly with acceptable performance with desktop composition. |
+
MoveToCopyFileShim |
+The problem occurs when an application experiences security access issues during setup. +The fix forces the CopyFile APIs to run instead of the MoveFile APIs. CopyFile APIs avoid moving the security descriptor, which enables the application files to get the default descriptor of the destination folder and prevents the security access issue. |
+
OpenDirectoryAcl |
+The problem is indicated by an error message that states that you do not have the appropriate permissions to access the application. +The fix reduces the security privilege levels on a specified set of files and folders. +
+Note
+
+For more detailed information about this application fix, see [Using the OpenDirectoryACL Fix](http://go.microsoft.com/fwlink/p/?LinkId=690348). +
+
+ |
+
PopCapGamesForceResPerf |
+The fix resolves the performance issues in PopCap games like Bejeweled2. The performance issues are visible in certain low-end cards at certain resolutions where the 1024x768 buffer is scaled to fit the display resolution. |
+
PreInstallDriver |
+The fix preinstalls drivers for applications that would otherwise try to install or start drivers during the initial start process. |
+
PreInstallSmarteSECURE |
+The fix preinstalls computer-wide CLSIDs for applications that use SmartSECURE copy protection, which would otherwise try to install the CLSIDs during the initial start process. |
+
ProcessPerfData |
+The problem is indicated by an Unhandled Exception error message because the application tried to read the process performance data registry value to determine if another instance of the application is running. +The fix handles the failure case by passing a fake process performance data registry key, so that the application perceives that it is the only instance running. +
+Note
+
+This issue seems to occur most frequently with .NET applications. +
+
+ |
+
PromoteDAM |
+The fix registers an application for power state change notifications. |
+
PropagateProcessHistory |
+The problem occurs when an application incorrectly fails to apply an application fix. +The fix sets the _PROCESS_HISTORY environment variable so that child processes can look in the parent directory for matching information while searching for application fixes. |
+
ProtectedAdminCheck |
+The problem occurs when an application fails to run because of incorrect Protected Administrator permissions. +The fix addresses the issues that occur when applications use non-standard Administrator checks, thereby generating false positives for user accounts that are being run as Protected Administrators. In this case, the associated SID exists, but it is set as deny-only. |
+
RedirectCRTTempFile |
+The fix intercepts failing CRT calls that try to create a temporary file at the root of the volume, thereby redirecting the calls to a temporary file in the user's temporary directory. |
+
RedirectHKCUKeys |
+The problem occurs when an application cannot be accessed because of User Account Control (UAC) restrictions. +The fix duplicates any newly created HKCU keys to other users' HKCU accounts. This fix is generic for UAC restrictions, whereby the HKCU keys are required, but are unavailable to an application at runtime. |
+
RedirectMP3Codec |
+This problem occurs when you cannot play MP3 files. +The fix intercepts the CoCreateInstance call for the missing filter and then redirects it to a supported version. |
+
RedirectShortcut |
+The problem occurs when an application cannot be accessed by its shortcut, or application shortcuts are not removed during the application uninstallation process. +The fix redirects all of the shortcuts created during the application setup to appear according to a specified path. +
This issue occurs because of UAC restrictions: specifically, when an application setup runs by using elevated privileges and stores the shortcuts according to the elevated user's context. In this situation, a restricted user cannot access the shortcuts. +You cannot apply this fix to an .exe file that includes a manifest and provides a runlevel. |
+
RelaunchElevated |
+The problem occurs when installers, uninstallers, or updaters fail when they are started from a host application. +The fix enables a child .exe file to run with elevated privileges when it is difficult to determine the parent process with either the ElevateCreateProcess fix or by marking the .exe files to RunAsAdmin. +
+Note
+
+For more detailed information about this application fix, see [Using the RelaunchElevated Fix](http://go.microsoft.com/fwlink/p/?LinkId=690349). +
+
+ |
+
RetryOpenSCManagerWithReadAccess |
+The problem occurs when an application tries to open the Service Control Manager (SCM) and receives an Access Denied error message. +The fix retries the call and requests a more restricted set of rights that include the following: +
|
+
RetryOpenServiceWithReadAccess |
+The problem occurs when an Unable to open service due to your application using the OpenService() API to test for the existence of a particular service error message displays. +The fix retries the OpenService() API call and verifies that the user has Administrator rights, is not a Protected Administrator, and by using read-only access. Applications can test for the existence of a service by calling the OpenService() API but some applications ask for all access when making this check. This fix retries the call but only asking for read-only access. The user needs to be an administrator for this to work +
+Note
+
+For more detailed information about this application fix, see [Using the RetryOpenServiceWithReadAccess Fix](http://go.microsoft.com/fwlink/p/?LinkId=690351). +
+
+ |
+
RunAsAdmin |
+The problem occurs when an application fails to function by using the Standard User or Protected Administrator account. +The fix enables the application to run by using elevated privileges. The fix is the equivalent of specifying requireAdministrator in an application manifest. +
+Note
+
+For more detailed information about this application fix, see [Using the RunAsAdmin Fix](http://go.microsoft.com/fwlink/p/?LinkId=690353). +
+
+ |
+
RunAsHighest |
+The problem occurs when administrators cannot view the read/write version of an application that presents a read-only view to standard users. +The fix enables the application to run by using the highest available permissions. This is the equivalent of specifying highestAvailable in an application manifest. +
+Note
+
+For more detailed information about this application fix, see [Using the RunAsHighest Fix](http://go.microsoft.com/fwlink/p/?LinkId=690355). +
+
+ |
+
RunAsInvoker |
+The problem occurs when an application is not detected as requiring elevation. +The fix enables the application to run by using the privileges that are associated with the creation process, without requiring elevation. This is the equivalent of specifying asInvoker in an application manifest. +
+Note
+
+For more detailed information about this application fix, see [Using the RunAsInvoker Fix](http://go.microsoft.com/fwlink/p/?LinkId=690356). +
+
+ |
+
SecuROM7 |
+The fix repairs applications by using SecuROM7 for copy protection. |
+
SessionShim |
+The fix intercepts API calls from applications that are trying to interact with services that are running in another session, by using the terminal service name prefix (Global or Local) as the parameter. +At the command prompt, you can supply a list of objects to modify, separating the values by a double backslash (\). Or, you can choose not to include any parameters, so that all of the objects are modified. +
+Important
+
+Users cannot log in as Session 0 (Global Session) in Windows Vista and later. Therefore, applications that require access to Session 0 automatically fail. +
+
+
+
+Note
+
+For more detailed information about this application fix, see [Using the SessionShim Fix](http://go.microsoft.com/fwlink/p/?LinkId=690358). +
+
+ |
+
SetProtocolHandler |
+The fix registers an application as a protocol handler. +You can control this fix further by typing the following command at the command prompt: +Client;Protocol;App +Where the Client is the name of the email protocol, Protocol is mailto, and App is the name of the application. +
+Note
+
+Only the mail client and the mailto protocol are supported. You can separate multiple clients by using a backslash (). +
+
+ |
+
SetupCommitFileQueueIgnoreWow |
+The problem occurs when a 32-bit setup program fails to install because it requires 64-bit drivers. +The fix disables the Wow64 file system that is used by the 64-bit editions of Windows, to prevent 32-bit applications from accessing 64-bit file systems during the application setup. |
+
SharePointDesigner2007 |
+The fix resolves an application bug that severely slows the application when it runs in DWM. |
+
ShimViaEAT |
+The problem occurs when an application fails, even after applying acompatibility fix that is known to fix an issue. Applications that use unicows.dll or copy protection often present this issue. +The fix applies the specified compatibility fixes by modifying the export table and by nullifying the use of module inclusion and exclusion. +
+Note
+
+For more information about this application fix, see [Using the ShimViaEAT Fix](http://go.microsoft.com/fwlink/p/?LinkId=690359). +
+
+ |
+
ShowWindowIE |
+The problem occurs when a web application experiences navigation and display issues because of the tabbing feature. +The fix intercepts the ShowWindow API call to address the issues that can occur when a web application determines that it is in a child window. This fix calls the real ShowWindow API on the top-level parent window. |
+
SierraWirelessHideCDROM |
+The fix repairs the Sierra Wireless Driver installation, thereby preventing bugcheck. |
+
Sonique2 |
+The application uses an invalid window style, which breaks in DWM. This fix replaces the window style with a valid value. |
+
SpecificInstaller |
+The problem occurs when an application installation file fails to be picked up by the GenericInstaller function. +The fix flags the application as being an installer file (for example, setup.exe), and then prompts for elevation. +
+Note
+
+For more detailed information about this application fix, see [Using the SpecificInstaller Fix]( http://go.microsoft.com/fwlink/p/?LinkId=690361). +
+
+ |
+
SpecificNonInstaller |
+The problem occurs when an application that is not an installer (and has sufficient privileges) generates a false positive from the GenericInstaller function. +The fix flags the application to exclude it from detection by the GenericInstaller function. +
+Note
+
+For more detailed information about this application fix, see [Using the SpecificNonInstaller Fix](http://go.microsoft.com/fwlink/p/?LinkId=690363). +
+
+ |
+
SystemMetricsLie |
+The fix replaces SystemMetrics values and SystemParametersInfo values with the values of previous Windows versions. |
+
TextArt |
+The application receives different mouse coordinates with DWM ON versus DWM OFF, which causes the application to hang. This fix resolves the issue. |
+
TrimDisplayDeviceNames |
+The fix trims the names of the display devices that are returned by the EnumDisplayDevices API. |
+
UIPICompatLogging |
+The fix enables the logging of Windows messages from Internet Explorer and other processes. |
+
UIPIEnableCustomMsgs |
+The problem occurs when an application does not properly communicate with other processes because customized Windows messages are not delivered. +The fix enables customized Windows messages to pass through to the current process from a lower Desktop integrity level. This fix is the equivalent of calling the RegisterWindowMessage function, followed by the ChangeWindowMessageFilter function in the code. +You can control this fix further by typing the following command at the command prompt: +MessageString1 MessageString2 +Where MessageString1 and MessageString2 reflect the message strings that can pass. +
+Note
+
+Multiple message strings must be separated by spaces. For more detailed information about this application fix, see [Using the UIPIEnableCustomMsgs Fix](http://go.microsoft.com/fwlink/p/?LinkId=690365). +
+
+ |
+
UIPIEnableStandardMsgs |
+The problem occurs when an application does not communicate properly with other processes because standard Windows messages are not delivered. +The fix enables standard Windows messages to pass through to the current process from a lower Desktop integrity level. This fix is the equivalent of calling the ChangeWindowMessageFilter function in the code. +You can control this fix further by typing the following command at the command prompt: +1055 1056 1069 +Where 1055 reflects the first message ID, 1056 reflects the second message ID, and 1069 reflects the third message ID that can pass. +
+Note
+
+Multiple messages can be separated by spaces. For more detailed information about this application fix, see [Using the UIPIEnableStandardMsgs Fix [act]](http://go.microsoft.com/fwlink/p/?LinkId=690367). +
+
+ |
+
VirtualizeDeleteFileLayer |
+The fix virtualizes DeleteFile operations for applications that try to delete protected files. |
+
VirtualizeDesktopPainting |
+This fix improves the performance of a number of operations on the Desktop DC while using DWM. |
+
VirtualRegistry |
+The problem is indicated when a Component failed to be located error message displays when an application is started. +The fix enables the registry functions to allow for virtualization, redirection, expansion values, version spoofing, the simulation of performance data counters, and so on. +For more detailed information about this application fix, see [Using the VirtualRegistry Fix](http://go.microsoft.com/fwlink/p/?LinkId=690368). |
+
VirtualizeDeleteFile |
+The problem occurs when several error messages display and the application cannot delete files. +The fix makes the application's DeleteFile function call a virtual call in an effort to remedy the UAC and file virtualization issues that were introduced with Windows Vista. This fix also links other file APIs (for example, GetFileAttributes) to ensure that the virtualization of the file is deleted. +
+Note
+
+For more detailed information about this application fix, see [Using the VirtualizeDeleteFile Fix](http://go.microsoft.com/fwlink/p/?LinkId=690369). +
+
+ |
+
VirtualizeHKCRLite |
+The problem occurs when an application fails to register COM components at runtime. +The fix redirects the HKCR write calls (HKLM) to the HKCU hive for a per-user COM registration. This operates much like the VirtualRegistry fix when you use the VirtualizeHKCR parameter; however, VirtualizeHKCRLite provides better performance. +HKCR is a virtual merge of the HKCU\Software\Classes and HKLM\Software\Classes directories. The use of HKCU is preferred if an application is not elevated and is ignored if the application is elevated. +You typically will use this compatibility fix in conjunction with the VirtualizeRegisterTypeLib fix. +For more detailed information about this application fix, see [Using the VirtualizeHKCRLite Fix](http://go.microsoft.com/fwlink/p/?LinkId=690370). |
+
VirtualizeRegisterTypeLib |
+The fix, when it is used with the VirtualizeHKCRLite fix, ensures that the type library and the COM class registration happen simultaneously. This functions much like the RegistryTypeLib fix when the RegisterTypeLibForUser parameter is used. +
+Note
+
+For more detailed information about this application fix, see [Using the VirtualizeRegisterTypelib Fix](http://go.microsoft.com/fwlink/p/?LinkId=690371). +
+
+ |
+
WaveOutIgnoreBadFormat |
+This problem is indicated by an error message that states: Unable to initialize sound device from your audio driver; the application then closes. +The fix enables the application to ignore the format error and continue to function properly. |
+
WerDisableReportException |
+The fix turns off the silent reporting of exceptions to the Windows Error Reporting tool, including those that are reported by Object Linking and Embedding-Database (OLE DB). The fix intercepts the RtlReportException API and returns a STATUS_NOT_SUPPORTED error message. |
+
Win7RTM/Win8RTM |
+The layer provides the application with Windows 7/Windows 8 compatibility mode. |
+
WinxxRTMVersionLie |
+The problem occurs when an application fails because it does not find the correct version number for the required Windows operating system. +All version lie compatibility fixes address the issue whereby an application fails to function because it is checking for, but not finding, a specific version of the operating system. The version lie fix returns the appropriate operating system version information. For example, the VistaRTMVersionLie returns the Windows Vista version information to the application, regardless of the actual operating system version that is running on the computer. |
+
Wing32SystoSys32 |
+The problem is indicated by an error message that states that the WinG library was not properly installed. +The fix detects whether the WinG32 library exists in the correct directory. If the library is located in the wrong location, this fix copies the information (typically during the runtime of the application) into the %WINDIR% \system32 directory. +
+Important
+
+The application must have Administrator privileges for this fix to work. +
+
+ |
+
WinSrv08R2RTM |
++ |
WinXPSP2VersionLie |
+The problem occurs when an application experiences issues because of a VB runtime DLL. +The fix forces the application to follow these steps: +
|
+
WRPDllRegister |
+The application fails when it tries to register a COM component that is released together with Windows Vista and later. +The fix skips the processes of registering and unregistering WRP-protected COM components when calling the DLLRegisterServer and DLLUnregisterServer functions. +You can control this fix further by typing the following command at the command prompt: +Component1.dll;Component2.dll +Where Component1.dll and Component2.dll reflect the components to be skipped. +
+Note
+
+For more detailed information about this application fix, see [Using the WRPDllRegister Fix](http://go.microsoft.com/fwlink/p/?LinkId=690375). +
+
+ |
+
WRPMitigation |
+The problem is indicated when an access denied error message displays when the application tries to access a protected operating system resource by using more than read-only access. +The fix emulates the successful authentication and modification of file and registry APIs, so that the application can continue. +
+Note
+
+For more detailed information about WRPMitigation, see [Using the WRPMitigation Fix](http://go.microsoft.com/fwlink/p/?LinkId=690376). +
+
+ |
+
WRPRegDeleteKey |
+The problem is indicated by an access denied error message that displays when the application tries to delete a registry key. +The fix verifies whether the registry key is WRP-protected. If the key is protected, this fix emulates the deletion process. |
+
XPAfxIsValidAddress |
+The fix emulates the behavior of Windows XP for MFC42!AfxIsValidAddress. |
+
| Compatibility Mode Name | +Description | +Included Compatibility Fixes | +
|---|---|---|
WinSrv03 |
+Emulates the Windows Server 2003 operating system. |
+
|
+
WinSrv03Sp1 |
+Emulates the Windows Server 2003 with Service Pack 1 (SP1) operating system. |
+
|
+
| Topic | +Description | +
|---|---|
[Using Compatibility Monitor to Send Feedback](using-compatibility-monitor-to-send-feedback.md) |
+The Microsoft Compatibility Monitor tool is installed as part of the runtime-analysis package. From the computers in your test environment, you can use Compatibility Monitor to submit compatibility information to the Application Compatibility Toolkit (ACT) database for your organization. |
+
[Common Compatibility Issues](common-compatibility-issues.md) |
+Compatibility issues tend to occur with the following technologies: |
+
| Tab | +Information | +
|---|---|
Details |
+Shows the following information for the selected computer: +
|
+
Applications |
+Shows the following information for each of the applications installed on the selected computer: +
|
+
Devices |
+Shows the following information for each of the devices installed on the selected computer: +
|
+
Labels |
+Shows the label for the selected computer. +For information about labels, see [Labeling Data in ACM](labeling-data-in-acm.md). |
+
| Topic | +Description | +
|---|---|
[ACT Tools, Packages, and Services](act-tools-packages-and-services.md) |
+The Application Compatibility Toolkit is included with the Windows ADK. [Download the Windows ADK.](http://go.microsoft.com/fwlink/p/?LinkId=526740) |
+
[ACT Deployment Options](act-deployment-options.md) |
+While planning your deployment of the Application Compatibility Toolkit (ACT), consider which computers you want running the various tools, packages, and services for ACT. |
+
[ACT Database Configuration](act-database-configuration.md) |
+The Application Compatibility Toolkit (ACT) uses a Microsoft® SQL Server® database for storing and sharing compatibility issue data. If you do not use Microsoft SQL Server, you can download and install Microsoft SQL Server Express. For information about creating Microsoft SQL Server databases, see [Administering the Database Engine](http://go.microsoft.com/fwlink/p/?LinkId=64169). |
+
[ACT Database Migration](act-database-migration.md) |
+The schema for an ACT database can change when ACT is updated or when a new version of ACT is released. If the schema for an ACT database does not match the current schema, you can migrate the compatibility data to a new database. You can then use the current version of ACT to open the new database. |
+
[ACT LPS Share Permissions](act-lps-share-permissions.md) |
+To upload log files to the ACT Log Processing Service (LPS) share, certain permissions must be set at the share level and folder level. |
+
| Advantages | +Disadvantages | +
|---|---|
|
+
|
+
| Topic | +Description | +
|---|---|
[Adding or Editing an Issue](adding-or-editing-an-issue.md) |
+In Application Compatibility Manager (ACM), you can enter information about the compatibility issues that you discover. |
+
[Adding or Editing a Solution](adding-or-editing-a-solution.md) |
+If you find your own solutions to compatibility issues, you can enter the solutions in Application Compatibility Manager (ACM). You can use the Microsoft Compatibility Exchange to upload solutions to Microsoft Corporation. |
+
[Resolving an Issue](resolving-an-issue.md) |
+You can use Application Compatibility Manager (ACM) to flag issues as resolved. Resolving an issue changes the status of the issue from a red x to a green check mark on your report and report detail screens. |
+
| Screen | +Default columns | +Additional columns | +
|---|---|---|
[<OperatingSystem> - Application Report](operatingsystem---application-report.md) |
+
|
+
|
+
[<OperatingSystem> - Computer Report](operatingsystem---computer-report.md) |
+
|
+
|
+
[<OperatingSystem> - Device Report](operatingsystem---device-report.md) |
+
|
+
|
+
[Internet Explorer - Web Site Report](internet-explorer---web-site-report.md) |
+
|
+
|
+
| Data | +Description | +
|---|---|
Risk assessment |
+The determination of whether the application has compatibility issues. |
+
Symptom |
+Behavior exhibited by the application. |
+
Cause |
+Reason for the failure. |
+
Provider and subprovider |
+Source of the compatibility issue. |
+
Issue ID |
+A unique ID number for the compatibility issue. |
+
Severity |
+Impact this issue has on the application experience. |
+
Priority |
+Degree of impact that this issue has on your organization. |
+
Published Date |
+Date that the source entered the data into the database. |
+
Operating system name |
+Friendly name of the installed operating system. |
+
Major version |
+Major version number of the operating system. |
+
Minor version |
+Minor version number of the operating system. |
+
Locale |
+Language ID of the application to which the compatibility issue applies. |
+
Title |
+Short title of the compatibility issue. |
+
Summary |
+Description of the compatibility issue. |
+
Service pack major |
+Major version number of the operating system service pack. |
+
Service pack minor |
+Minor version number of the operating system service pack. |
+
URL HREF |
+URL of any links provided for the compatibility issue. |
+
Provider and subprovider IDs |
+IDs for the source of the compatibility issue's solution. |
+
Solution type |
+Type of solution provided for the compatibility issue. |
+
Locale |
+Language ID of the application to which the solution applies. |
+
Title |
+Short title of the solution. |
+
Details |
+Description of the solution. |
+
URL HREF |
+URL of any links provided for the compatibility issue solution. |
+
| Data | +Description | +
|---|---|
Works |
+The count of Works ratings, for 32-bit and 64-bit operating systems. |
+
Works with Minor Issues or has Solutions |
+The count of Works with Minor Issues or has Solutions ratings, for 32-bit and 64-bit operating systems. |
+
Does Not Work |
+The count of Does Not Work ratings, for 32-bit and 64-bit operating systems. |
+
Vendor name |
+Product description |
+HWID |
+Windows Update availability |
+
Broadcom |
+802.11abgn Wireless SDIO adapter |
+sd\vid_02d0&pid_4330&fn_1 |
+Contact the system OEM or Broadcom for driver availability. |
+
Broadcom |
+802.11n Network Adapter |
+pci\ven_14e4&dev_4331&subsys_00d6106b&rev_02 |
+Contact the system OEM or Broadcom for driver availability. |
+
Broadcom |
+802.11n Network Adapter |
+pci\ven_14e4&dev_4331&subsys_00f5106b&rev_02 |
+Contact the system OEM or Broadcom for driver availability. |
+
Broadcom |
+802.11n Network Adapter |
+pci\ven_14e4&dev_4331&subsys_00ef106b&rev_02 |
+Contact the system OEM or Broadcom for driver availability. |
+
Broadcom |
+802.11n Network Adapter |
+pci\ven_14e4&dev_4331&subsys_00f4106b&rev_02 |
+Contact the system OEM or Broadcom for driver availability. |
+
Broadcom |
+802.11n Network Adapter |
+pci\ven_14e4&dev_4331&subsys_010e106b&rev_02 |
+Contact the system OEM or Broadcom for driver availability. |
+
Broadcom |
+802.11n Network Adapter |
+pci\ven_14e4&dev_4331&subsys_00e4106b&rev_02 |
+Contact the system OEM or Broadcom for driver availability. |
+
Broadcom |
+802.11n Network Adapter |
+pci\ven_14e4&dev_4331&subsys_433114e4&rev_02 |
+Contact the system OEM or Broadcom for driver availability. |
+
Broadcom |
+802.11n Network Adapter |
+pci\ven_14e4&dev_4331&subsys_010f106b&rev_02 |
+Contact the system OEM or Broadcom for driver availability. |
+
Marvell |
+Yukon 88E8001/8003/8010 PCI Gigabit Ethernet |
+pci\ven_11ab&dev_4320&subsys_811a1043 |
+[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619080) +[64-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619082) |
+
Marvell |
+Libertas 802.11b/g Wireless |
+pci\ven_11ab&dev_1faa&subsys_6b001385&rev_03 |
+[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619128) +[64-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619129) |
+
Qualcomm |
+Atheros AR6004 Wireless LAN Adapter |
+sd\vid_0271&pid_0401 |
+[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619086) +64-bit driver not available |
+
Qualcomm |
+Atheros AR5BWB222 Wireless Network Adapter |
+pci\ven_168c&dev_0034&subsys_20031a56 |
+[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619348) +64-bit driver not available |
+
Qualcomm |
+Atheros AR5BWB222 Wireless Network Adapter |
+pci\ven_168c&dev_0034&subsys_020a1028&rev_01 |
+Contact the system OEM or Qualcom for driver availability. |
+
Qualcomm |
+Atheros AR5005G Wireless Network Adapter |
+pci\ven_168c&dev_001a&subsys_04181468&rev_01 |
+[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619349) +[64-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619091) |
+
Ralink |
+Wireless-G PCI Adapter |
+pci\ven_1814&dev_0301&subsys_00551737&rev_00 |
+[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619092) +[64-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619093) |
+
Ralink |
+Turbo Wireless LAN Card |
+pci\ven_1814&dev_0301&subsys_25611814&rev_00 |
+[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619094) +[64-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619095) |
+
Ralink |
+Wireless LAN Card V1 |
+pci\ven_1814&dev_0302&subsys_3a711186&rev_00 |
+[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619097) +[64-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619098) |
+
Ralink |
+D-Link AirPlus G DWL-G510 Wireless PCI Adapter(rev.C) |
+pci\ven_1814&dev_0302&subsys_3c091186&rev_00 |
+[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619099) +[64-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619100) |
+
| Tab | +Information | +
|---|---|
Details |
+Shows the following information for the selected device: +
|
+
Computers |
+Shows the following information for each of the computers on which the device is installed: +
|
+
| Column | +Description | +
|---|---|
And/Or |
+If you select And, your data must match all query rows to appear as a returned result. +If you select Or, your data can match any query row to appear as a returned result. |
+
Field |
+Select filter criteria. |
+
Operator |
+Select an operator. The available operators depend on the field that you choose. |
+
Value |
+Type or select a value. |
+
| Mitigation menu command | +Description | +
|---|---|
Apply Mitigations |
+ Opens the Mitigate AppCompat Issues dialog box, in which you can select the fixes that you intend to apply to the application. |
+
Undo Mitigations |
+ Removes the application fixes that you just applied. +This option is available only after you apply an application fix and before you close the SUA tool. Alternatively, you can manually remove application fixes by using Programs and Features in Control Panel. |
+
Export Mitigations as Windows Installer file |
+ Exports your application fixes as a Windows® Installer (.msi) file, which can then be deployed to other computers that are running the application. |
+
| Topic | +Description | +
|---|---|
[Deciding Whether to Fix an Application or Deploy a Workaround](deciding-whether-to-fix-an-application-or-deploy-a-workaround.md) |
+You can fix a compatibility issue by changing the code for the application or by deploying a workaround. |
+
[SUA User's Guide](sua-users-guide.md) |
+You can use Standard User Analyzer (SUA) to test your applications and monitor API calls to detect compatibility issues related to the User Account Control (UAC) feature in Windows. |
+
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md) |
+The Compatibility Administrator tool helps you resolve potential application-compatibility issues before deploying a new version of Windows to your organization. Compatibility Administrator provides the following: |
+
| Topic | +Description | +
|---|---|
[Chromebook migration guide](chromebook-migration-guide.md) |
+In this guide you will learn how to migrate a Google Chromebook-based learning environment to a Windows 10-based learning environment. You will learn how to perform the necessary planning steps, including Windows device deployment, migration of user and device settings, app migration or replacement, and cloud storage migration. You will then learn the best method to perform the migration by using automated deployment and migration tools. |
+
| Topic | +Description | +
|---|---|
[Understanding and Using Compatibility Fixes](understanding-and-using-compatibility-fixes.md) |
+As the Windows operating system evolves to support new technology and functionality, the implementations of some functions may change. This can cause problems for applications that relied upon the original implementation. You can avoid compatibility issues by using the Microsoft Windows Application Compatibility (Compatibility Fix) infrastructure to create a specific application fix for a particular version of an application. |
+
[Compatibility Fix Database Management Strategies and Deployment](compatibility-fix-database-management-strategies-and-deployment.md) |
+After you determine that you will use compatibility fixes in your application-compatibility mitigation strategy, you must define a strategy to manage your custom compatibility-fix database. Typically, you can use one of two approaches: |
+
[Testing Your Application Mitigation Packages](testing-your-application-mitigation-packages.md) |
+This topic provides details about testing your application-mitigation packages, including recommendations about how to report your information and how to resolve any outstanding issues. |
+
| Topic | +Description | +
|---|---|
[Log File Locations for Data-Collection Packages](log-file-locations-for-data-collection-packages.md) |
+When you create a data-collection package in Application Compatibility Manager (ACM), you can select an output location for your log files. You have the following options: |
+
[Exporting a Data-Collection Package](exporting-a-data-collection-package.md) |
+In Application Compatibility Manager (ACM), you can export a data-collection package as a Windows installer (.msi) file. You can then use the .msi file to install the data-collection package on the computers from which you want to gather data. |
+
[Deleting a Data-Collection Package](deleting-a-data-collection-package.md) |
+In Application Compatibility Manager (ACM), you can delete any of your existing data-collection packages from the database. |
+
[Labeling Data in ACM](labeling-data-in-acm.md) |
+Application data and its associated compatibility issues can vary within an organization. For example, the applications used by a Human Resources (HR) department might differ from the applications used by a Sales department. Even for applications that are used across an organization, different compatibility issues might be found for each business group because of the unique application use by each business group. |
+
| Report | +[Selecting Your Compatibility Rating](selecting-your-compatibility-rating.md) | +[Selecting Your Deployment Status](selecting-your-deployment-status.md) | +[Categorizing Your Compatibility Data](categorizing-your-compatibility-data.md) | +[Prioritizing Your Compatibility Data](prioritizing-your-compatibility-data.md) | +[Selecting the Send and Receive Status for an Application](selecting-the-send-and-receive-status-for-an-application.md) | +[Creating and Editing Issues and Solutions](creating-and-editing-issues-and-solutions.md) | +
|---|---|---|---|---|---|---|
[<OperatingSystem> - Application Report](operatingsystem---application-report.md) |
+Yes |
+Yes |
+Yes |
+Yes |
+Yes |
+Yes |
+
[<OperatingSystem> - Computer Report](operatingsystem---computer-report.md) |
+No |
+No |
+Yes |
+Yes |
+No |
+No |
+
[<OperatingSystem> - Device Report](operatingsystem---device-report.md) |
+No |
+No |
+Yes |
+Yes |
+No |
+No |
+
[<WebsiteURL> Dialog Box](websiteurl-dialog-box.md) |
+Yes |
+Yes |
+Yes |
+Yes |
+Yes |
+Yes |
+
| Topic | +Description | +
|---|---|
[Organizational Tasks for Each Report Type](organizational-tasks-for-each-report-type.md) |
+The following table shows which tasks can be performed for each report type. |
+
[Selecting Your Compatibility Rating](selecting-your-compatibility-rating.md) |
+You can rate the compatibility of your applications, installation packages, or websites, based on whether they run successfully on a 32-bit or 64-bit operating system. Your rating applies to your entire organization and is based on your own testing results and organizational requirements. |
+
[Selecting Your Deployment Status](selecting-your-deployment-status.md) |
+In Application Compatibility Manager (ACM), you can track the deployment status of your applications and websites. |
+
[Categorizing Your Compatibility Data](categorizing-your-compatibility-data.md) |
+To customize and filter your compatibility reports, you can create categories and subcategories to assign to your applications, computers, devices, and websites. By default, Microsoft provides the following categories: |
+
[Prioritizing Your Compatibility Data](prioritizing-your-compatibility-data.md) |
+You can prioritize your applications, websites, computers, and devices to help customize and filter your compatibility reports. The priority levels are: |
+
[Selecting the Send and Receive Status for an Application](selecting-the-send-and-receive-status-for-an-application.md) |
+For each application listed in Application Compatibility Manager (ACM), you can select whether to send and receive specific application data through the Microsoft Compatibility Exchange |
+
[Creating and Editing Issues and Solutions](creating-and-editing-issues-and-solutions.md) |
+This section provides step-by-step instructions for adding and editing application compatibility issues and solutions. Your issue and solution data can be uploaded to Microsoft through the Microsoft® Compatibility Exchange. |
+
| Topic | +Description | +
|---|---|
[Change history for Plan for Windows 10 deployment](change-history-for-plan-for-windows-10-deployment.md) |
+This topic lists new and updated topics in the Plan for Windows 10 deployment documentation for [Windows 10 and Windows 10 Mobile](../index.md). |
+
[Windows 10 servicing options](windows-10-servicing-model.md) |
+Windows 10 provides a new model for organizations to deploy and upgrade Windows by providing updates to features and capabilities through a continual process. |
+
[Windows 10 deployment considerations](windows-10-deployment-considerations.md) |
+There are new deployment options in Windows 10 that help you simplify the deployment process and automate migration of existing settings and applications. |
+
[Windows 10 compatibility](windows-10-compatibility.md) |
+Windows 10 will be compatible with most existing PC hardware; most devices running Windows 7, Windows 8, or Windows 8.1 will meet the requirements for Windows 10. |
+
[Windows 10 infrastructure requirements](windows-10-infrastructure-requirements.md) |
+There are specific infrastructure requirements to deploy and manage Windows 10 that should be in place prior to significant Windows 10 deployments within your organization. |
+
[Windows Update for Business](windows-update-for-business.md) |
+Get an overview of how you can implement and deploy a Windows Update for Business solution and how to maintain enrolled systems. |
+
[Guidance for education environments](guidance-for-education-environments.md) |
+Find resources to help you plan your deployment of Windows 10 to desktops, laptops, tablets, and other devices in educational institutions. |
+
[Windows To Go: feature overview](windows-to-go-feature-overview-scenario.md) |
+Windows To Go is a feature in Windows 10 Enterprise and Windows 10 Education that enables the creation of a Windows To Go workspace that can be booted from a USB-connected external drive on PCs. |
+
[Application Compatibility Toolkit (ACT) Technical Reference](application-compatibility-toolkit--act--technical-reference.md) |
+The Microsoft® Application Compatibility Toolkit (ACT) helps you determine whether the applications, devices, and computers in your organization are compatible with versions of the Windows® operating system. |
+
| And/Or | +Field | +Operator | +Value | +
|---|---|---|---|
And |
+ Priority |
+ Equals |
+ Priority 1 - Business Critical |
+
Or |
+ Priority |
+ Equals |
+ Priority 2 - Important |
+
| Icon | +Description | +
|---|---|
 |
+Application, device, or website functions as expected on a 32-bit operating system. |
+
 |
+Application, device, or website functions as expected on a 64-bit operating system. |
+
 |
+Application, device, or website with issues that are minor or have known solutions on a 32-bit operating system. Severity 3 issues are considered minor issues. |
+
 |
+Application, device, or website with issues that are minor or have known solutions on a 64-bit operating system. |
+
 |
+Application, device, or website with major issues, such as data loss or severely impaired functionality, on 32-bit operating systems. Severity 1 and Severity 2 issues are considered major issues. |
+
 |
+Application, device, or website with major issues, such as data loss or severely impaired functionality, on 64-bit operating systems. |
+
 |
+Application, device, or website that does not have any application assessment data for 32-bit operating systems. The item does not match any information in the database, or no assessments have been submitted. |
+
 |
+Application, device, or website that does not have any application assessment data for 64-bit operating systems. |
+
| And/Or | +Field | +Operator | +Value | +
|---|---|---|---|
And |
+ Send and Receive Status |
+ Equals |
+ Do not send to Microsoft |
+
| And/Or | +Field | +Operator | +Value | +
|---|---|---|---|
And |
+ My Assessment |
+ Equals |
+ Works |
+
Or |
+ My Assessment |
+ Equals |
+ Works with minor issues or has solutions |
+
| And/Or | +Field | +Operator | +Value | +
|---|---|---|---|
And |
+ Deployment Status |
+ Equals |
+ Mitigating |
+
Or |
+ Deployment Status |
+ Equals |
+ Ready to Deploy |
+
| Topic | +Description | +
|---|---|
[Settings Dialog Box - Settings Tab](settings-dialog-box---settings-tab.md) |
+To display the Settings dialog box, in Application Compatibility Manager (ACM), on the Tools menu, click Settings. |
+
[Settings Dialog Box - Preferences Tab](settings-dialog-box---preferences-tab.md) |
+To display the Settings dialog box, in Application Compatibility Manager (ACM), on the Tools menu, click Settings. |
+
Group Policy keys |
+HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\Pause |
+
MDM +./Vendor/MSFT/Update/DeferUpgrade |
+Software\Microsoft\PolicyManager\current\Update\Pause +
|
+
| View menu command | +Description | +
|---|---|
Error Messages |
+ When this command is selected, the user interface shows error messages that the SUA tool has generated. Error messages are highlighted in pink. +This command is selected by default. |
+
Warning Messages |
+ When this command is selected, the user interface shows warning messages that the SUA tool has generated. Warning messages are highlighted in yellow. |
+
Information Messages |
+ When this command is selected, the user interface shows informational messages that the SUA tool has generated. Informational messages are highlighted in green. |
+
Detailed Information |
+ When this command is selected, the user interface shows information that the SUA tool has generated, such as debug, stack trace, stop code, and severity information. |
+
| Topic | +Description | +
|---|---|
[Using the SUA Wizard](using-the-sua-wizard.md) |
+The Standard User Analyzer (SUA) Wizard works much like the SUA tool to evaluate User Account Control (UAC) issues. However, the SUA Wizard does not offer detailed analysis, and it cannot disable virtualization or elevate your permissions. |
+
[Using the SUA Tool](using-the-sua-tool.md) |
+By using the Standard User Analyzer (SUA) tool, you can test your applications and monitor API calls to detect compatibility issues with the User Account Control (UAC) feature. |
+
| Tab name | +Description | +
|---|---|
App Info |
+Provides the following information for the selected application: +
|
+
File |
+Provides information about access to the file system. +For example, this tab might show an attempt to write to a file that only administrators can typically access. |
+
Registry |
+Provides information about access to the system registry. +For example, this tab might show an attempt to write to a registry key that only administrators can typically access. |
+
INI |
+Provides information about WriteProfile API issues. +For example, in the Calculator tool (Calc.exe) in Windows® XP, when you change the view from Standard to Scientific, Calc.exe calls the WriteProfile API to write to the Windows\Win.ini file. The Win.ini file is writable only for administrators. |
+
Token |
+Provides information about access-token checking. +For example, this tab might show an explicit check for the Builtin\Administrators security identifier (SID) in the user's access token. This operation may not work for a standard user. |
+
Privilege |
+Provides information about permissions. +For example, this tab might show an attempt to explicitly enable permissions that do not work for a standard user. |
+
Name Space |
+Provides information about creation of system objects. +For example, this tab might show an attempt to create a new system object, such as an event or a memory map, in a restricted namespace. Applications that attempt this kind of operation do not function for a standard user. |
+
Other Objects |
+Provides information related to applications accessing objects other than files and registry keys. |
+
Process |
+Provides information about process elevation. +For example, this tab might show the use of the CreateProcess API to open an executable (.exe) file that, in turn, requires process elevation that will not function for a standard user. |
+
| Topic | +Description | +
|---|---|
[Identifying Computers for Inventory Collection](identifying-computers-for-inventory-collection.md) |
+An inventory-collector package gathers inventory data from the computers on which it is installed. This data includes the following: |
+
[Creating an Inventory-Collector Package](creating-an-inventory-collector-package.md) |
+You can use Application Compatibility Manager (ACM) to create an inventory-collector package. You can then deploy the inventory-collector package to other computers to gather inventory data. The package uploads inventory data to the Application Compatibility Toolkit (ACT) database. |
+
[Deploying an Inventory-Collector Package](deploying-an-inventory-collector-package.md) |
+You can use the following methods to deploy an inventory-collector package to the destination computers: |
+
| Topic | +Description | +
|---|---|
[Deciding Which Applications to Test](deciding-which-applications-to-test.md) |
+Before starting your compatibility testing on the version of Windows that you want to deploy, you can use the Application Compatibility Toolkit (ACT) to identify which applications should be the focus of your testing. |
+
[Creating an Enterprise Environment for Compatibility Testing](creating-an-enterprise-environment-for-compatibility-testing.md) |
+The goal of the test environment is to model the operating system that you want to deploy and assess compatibility before deploying the operating system to your production environment. Your test environment is composed of computers on which the new operating system is installed. Your test environment can be a long-term investment. Consider retaining the test environment after deployment to assist in future deployment projects. |
+
[Creating a Runtime-Analysis Package](creating-a-runtime-analysis-package.md) |
+In Application Compatibility Manager (ACM), you can create runtime-analysis packages, which you can then deploy to computers for compatibility testing in your test environment. |
+
[Deploying a Runtime-Analysis Package](deploying-a-runtime-analysis-package.md) |
+When you deploy a runtime-analysis package, you are deploying it to your test environment for compatibility testing. |
+
[Compatibility Monitor User's Guide](compatibility-monitor-users-guide.md) |
+Compatibility Monitor is a tool in the runtime analysis package that you can use to monitor applications for compatibility issues. You can also use the Compatibility Monitor tool to submit compatibility feedback. |
+
| Icon | +Description | +Location | +
|---|---|---|
 |
+Opens the Application Compatibility Manager Overview screen. |
+
|
+
 |
+Opens the New Data Collection Package dialog box. +For more information, see [Creating a Runtime-Analysis Package](creating-a-runtime-analysis-package.md). |
+
|
+
 |
+Exports your data-collection package settings. +For more information, see [Exporting a Data-Collection Package](exporting-a-data-collection-package.md). |
+
|
+
 |
+Deletes a data-collection package that has not yet run on your client computers. +For more information, see [Deleting a Data-Collection Package](deleting-a-data-collection-package.md). |
+
|
+
 |
+Imports an existing compatibility report. +For more information, see [Saving, Opening, and Exporting Reports](saving-opening-and-exporting-reports.md). |
+
|
+
 |
+Saves a compatibility report, including your preferences and settings. +For more information, see [Saving, Opening, and Exporting Reports](saving-opening-and-exporting-reports.md). |
+
|
+
 |
+Exports your report data to a Microsoft® Excel® spreadsheet (.xls) file. +For more information, see [Saving, Opening, and Exporting Reports](saving-opening-and-exporting-reports.md). |
+
|
+
 |
+Synchronizes your compatibility data with the Microsoft Compatibility Exchange. +For more information, see [Sending and Receiving Compatibility Data](sending-and-receiving-compatibility-data.md). |
+
|
+
 |
+Turns the query builder on or off. +For more information, see [Filtering Your Compatibility Data](filtering-your-compatibility-data.md). |
+
|
+
 |
+Opens the Set Assessment dialog box. +For more information, see [Selecting Your Compatibility Rating](selecting-your-compatibility-rating.md). |
+
|
+
 |
+Opens the Set Deployment Status dialog box. +For more information, see [Selecting Your Deployment Status](selecting-your-deployment-status.md). |
+
|
+
 |
+Opens the Assign Categories dialog box. +For more information, see [Categorizing Your Compatibility Data](categorizing-your-compatibility-data.md). |
+
|
+
 |
+Opens the Assign Priorities dialog box. +For more information, see [Prioritizing Your Compatibility Data](prioritizing-your-compatibility-data.md). |
+
|
+
 |
+Opens the Send and Receive Status dialog box. +For more information, see [Selecting the Send and Receive Status for an Application](selecting-the-send-and-receive-status-for-an-application.md). |
+
|
+
 |
+Opens the Add Issue dialog box. +For more information, see [Adding or Editing an Issue](adding-or-editing-an-issue.md). |
+
|
+
 |
+Opens the Add Solution dialog box. +For more information, see [Adding or Editing a Solution](adding-or-editing-a-solution.md). |
+
|
+
 |
+Saves a compatibility issue. |
+
|
+
 |
+Reactivates a resolved compatibility issue. +For more information, see [Resolving an Issue](resolving-an-issue.md). |
+
|
+
 |
+Refreshes the screen. If you are using the query builder, updates the screen with the query results. |
+
|
+
 |
+Enables you to scroll up and down the screen or dialog box information, showing the related details. +This button may not be available for all issues or information. |
+
|
+
 |
+Opens the online Help system. |
+
|
+
| Topic | +Description | +
|---|---|
[Troubleshooting the ACT Configuration Wizard](troubleshooting-the-act-configuration-wizard.md) |
+When you start Application Compatibility Manager (ACM) for the first time, the Application Compatibility Toolkit (ACT) Configuration Wizard appears. The wizard helps you configure your ACT database, your shared folder for ACT log files, and your ACT Log Processing Service account. |
+
[Troubleshooting the ACT Log Processing Service](troubleshooting-the-act-log-processing-service.md) |
+The following solutions may help you resolve issues that are related to the Application Compatibility Toolkit (ACT) Log Processing Service. |
+
[Troubleshooting ACT Database Issues](troubleshooting-act-database-issues.md) |
+The following solutions may help you resolve issues that are related to your Microsoft® SQL Server® database for the Application Compatibility Toolkit (ACT). |
+
| Topic | +Description | +
|---|---|
[Taking Inventory of Your Organization](taking-inventory-of-your-organization.md) |
+This section provides information about how to use the Application Compatibility Toolkit (ACT) to identify applications and devices that are installed in your organization. |
+
[Testing Compatibility on the Target Platform](testing-compatibility-on-the-target-platform.md) |
+This section provides information about setting up a test environment for compatibility testing, and about creating and deploying runtime-analysis packages to the test environment. |
+
[Managing Your Data-Collection Packages](managing-your-data-collection-packages.md) |
+This section provides information about using Application Compatibility Manager (ACM) to manage your data-collection packages. Data-collection packages include inventory-collector packages and runtime-analysis packages. The following procedures apply to both package types. |
+
[Analyzing Your Compatibility Data](analyzing-your-compatibility-data.md) |
+This section provides information about viewing and working with your compatibility data in Application Compatibility Manager (ACM). |
+
[Fixing Compatibility Issues](fixing-compatibility-issues.md) |
+This section provides step-by-step instructions and describes development tools that you can use to help fix your compatibility issues. |
+
| Topic | +Description | +
|---|---|
[Available Data Types and Operators in Compatibility Administrator](available-data-types-and-operators-in-compatibility-administrator.md) |
+The Compatibility Administrator tool provides a way to query your custom-compatibility databases. |
+
[Searching for Fixed Applications in Compatibility Administrator](searching-for-fixed-applications-in-compatibility-administrator.md) |
+With the search functionality in Compatibility Administrator, you can locate specific executable (.exe) files with previously applied compatibility fixes, compatibility modes, or AppHelp messages. This is particularly useful if you are trying to identify applications with a specific compatibility fix or identifying which fixes are applied to a specific application. |
+
[Searching for Installed Compatibility Fixes with the Query Tool in Compatibility Administrator](searching-for-installed-compatibility-fixes-with-the-query-tool-in-compatibility-administrator.md) |
+You can access the Query tool from within Compatibility Administrator. The Query tool provides the same functionality as using the Search feature. |
+
[Creating a Custom Compatibility Fix in Compatibility Administrator](creating-a-custom-compatibility-fix-in-compatibility-administrator.md) |
+The Compatibility Administrator tool uses the term fix to describe the combination of compatibility information added to a customized database for a specific application. This combination can include single application fixes, groups of fixes that work together as a compatibility mode, and blocking and non-blocking AppHelp messages. |
+
[Creating a Custom Compatibility Mode in Compatibility Administrator](creating-a-custom-compatibility-mode-in-compatibility-administrator.md) |
+Windows® provides several compatibility modes, groups of compatibility fixes found to resolve many common application-compatibility issues. While working with Compatibility Administrator, you might decide to group some of your individual compatibility fixes into a custom-compatibility mode, which you can then deploy and use on any of your compatibility databases. |
+
[Creating an AppHelp Message in Compatibility Administrator](creating-an-apphelp-message-in-compatibility-administrator.md) |
+The Compatibility Administrator tool enables you to create an AppHelp text message. This is a blocking or non-blocking message that appears when a user starts an application that you know has major functionality issues on the Windows® operating system. |
+
[Viewing the Events Screen in Compatibility Administrator](viewing-the-events-screen-in-compatibility-administrator.md) |
+The Events screen enables you to record and to view your activities in the Compatibility Administrator tool, provided that the screen is open while you perform the activities. |
+
[Enabling and Disabling Compatibility Fixes in Compatibility Administrator](enabling-and-disabling-compatibility-fixes-in-compatibility-administrator.md) |
+You can disable and enable individual compatibility fixes in your customized databases for testing and troubleshooting purposes. |
+
[Installing and Uninstalling Custom Compatibility Databases in Compatibility Administrator](installing-and-uninstalling-custom-compatibility-databases-in-compatibility-administrator.md) |
+The Compatibility Administrator tool enables the creation and the use of custom-compatibility and standard-compatibility databases. Both the custom databases and the standard databases store the known compatibility fixes, compatibility modes, and AppHelp messages. They also store the required application-matching information for installation on your local computers. |
+
| Option | +Description | +
|---|---|
-q |
+Performs a silent installation with no visible window, status, or warning information. Fatal errors appear only in Event Viewer (Eventvwr.exe). +For example, +
|
+
-u filepath |
+Performs an uninstallation of the specified database. +For example, +
|
+
-g GUID |
+Specifies the customized database to uninstall by a globally unique identifier (GUID). +For example, +
|
+
-n "name" |
+Specifies the customized database to uninstall by file name. +For example, +
|
+
-? |
+Displays the Help for the Sdbinst.exe tool. +For example, +
|
+
| Topic | +Description | +
|---|---|
[<OperatingSystem> - Application Report](operatingsystem---application-report.md) |
+This section describes the compatibility reports in Application Compatibility Manager (ACM) and how you can work with the reports. |
+
[<OperatingSystem> - Computer Report](operatingsystem---computer-report.md) |
+The <OperatingSystem> - Computer Report screen shows the following information for each computer in your organization: |
+
[<OperatingSystem> - Device Report](operatingsystem---device-report.md) |
+The <OperatingSystem> - Device Report screen shows the following information for each device installed in your organization: |
+
[Internet Explorer - Web Site Report](internet-explorer---web-site-report.md) |
+The Internet Explorer - Web Site Report screen shows the following information for each of the websites visited in your organization: |
+
[Saving, Opening, and Exporting Reports](saving-opening-and-exporting-reports.md) |
+You can perform several common reporting tasks from the Analyze screen, including saving a compatibility report, opening a saved compatibility report (.adq) file, and exporting your report data to a spreadsheet (.xls) file. |
+
[Customizing Your Report Views](customizing-your-report-views.md) |
+You can customize how you view your report data in Application Compatibility Manager (ACM). |
+
| Topic | +Description | +
|---|---|
[What's New in ACT 6.1](whats-new-in-act-60.md) |
+Two major updates have been released since ACT 6.1. They are ACT 6.1 Update and ACT 6.1 Update 2. The following table lists changes made in the Application Compatibility Toolkit (ACT), which is included in the Windows Assessment and Deployment Kit (ADK) download. |
+
[Software Requirements for ACT](software-requirements-for-act.md) |
+The Application Compatibility Toolkit (ACT) has the following software requirements. |
+
[Software Requirements for RAP](software-requirements-for-rap.md) |
+The runtime-analysis package (RAP) has the following software requirements. |
+
| Version | +Changes | +
| ACT 6.1 Update | +
|
+
| ACT 6.1 Update 2 | +Bug fixes: this version of ACT addresses the following bugs: +
|
+
| Consider ... | +For these scenarios | +
|---|---|
| In-place upgrade | +
|
+
| Traditional wipe-and-load | +
|
+
| Dynamic provisioning | +
|
+
| For a PC that uses… | +Changing to… | +You need to: | +
|---|---|---|
| Windows Insider Program | +Current Branch | +Wait for the final Current Branch release. | +
| + | Current Branch for Business | +Not directly possible, because Windows Insider Program machines are automatically upgraded to the Current Branch release at the end of the development cycle. | +
| + | Long-Term Servicing Branch | +Not directly possible (requires wipe-and-load). | +
| Current Branch | +Insider | +Use the Settings app to enroll the device in the Windows Insider Program. | +
| + | Current Branch for Business | +Select the Defer upgrade setting, or move the PC to a target group or flight that will not receive the next upgrade until it is business ready. Note that this change will not have any immediate impact; it only prevents the installation of the next Current Branch release. | +
| + | Long-Term Servicing Branch | +Not directly possible (requires wipe-and-load). | +
| Current Branch for Business | +Insider | +Use the Settings app to enroll the device in the Windows Insider Program. | +
| + | Current Branch | +Disable the Defer upgrade setting, or move the PC to a target group or flight that will receive the latest Current Branch release. | +
| + | Long-Term Servicing Branch | +Not directly possible (requires wipe-and-load). | +
| Long-Term Servicing Branch | +Insider | +Use media to upgrade to the latest Windows Insider Program build. | +
| + | Current Branch | +Use media to upgrade to a later Current Branch build. (Note that the Current Branch build must be a later build.) | +
| + | Current Branch for Business | +Use media to upgrade to a later Current Branch for Business build (Current Branch build plus fixes). Note that it must be a later build. | +
| Item | +Requirement | +
|---|---|
Boot process |
+Capable of USB boot |
+
Firmware |
+USB boot enabled. (PCs certified for use with Windows 7 or later can be configured to boot directly from USB, check with the hardware manufacturer if you are unsure of the ability of your PC to boot from USB) |
+
Processor architecture |
+Must support the image on the Windows To Go drive |
+
External USB Hubs |
+Not supported; connect the Windows To Go drive directly to the host machine |
+
Processor |
+1 Ghz or faster |
+
RAM |
+2 GB or greater |
+
Graphics |
+DirectX 9 graphics device with WDDM 1.2 or greater driver |
+
USB port |
+USB 2.0 port or greater |
+
| Host PC Firmware Type | +Host PC Processor Architecture | +Compatible Windows To Go Image Architecture | +
|---|---|---|
Legacy BIOS |
+32-bit |
+32-bit only |
+
Legacy BIOS |
+64-bit |
+32-bit and 64-bit |
+
UEFI BIOS |
+32-bit |
+32-bit only |
+
UEFI BIOS |
+64-bit |
+64-bit only |
+
[Dialog Filter](http://go.microsoft.com/fwlink/p/?LinkId=626762): suppress system dialogs and control which processes can run
Dialog Filter has been deprecated for Windows 10. Dialog Filter provided two capabilities; the ability to control which processes were able to run, and the ability to prevent dialogs (in practice, system dialogs) from appearing.
Control over which processes are able to run will now be provided by AppLocker.
diff --git a/windows/whats-new/microsoft-passport.md b/windows/whats-new/microsoft-passport.md
index 5ff80aaab9..e684f2be3b 100644
--- a/windows/whats-new/microsoft-passport.md
+++ b/windows/whats-new/microsoft-passport.md
@@ -30,12 +30,12 @@ Microsoft Passport also enables Windows 10 Mobile devices to be used as a remot
- **Security**. Microsoft Passport helps protect user identities and user credentials. Because no passwords are used, it helps circumvent phishing and brute force attacks. It also helps prevent server breaches because Microsoft Passport credentials are an asymmetric key pair, which helps prevent replay attacks when these keys are generated within isolated environments of Trusted Platform Modules (TPMs).
-[Learn how to implement and manage Microsoft Passport in your organization.](/windows/keep-secure/implement-microsoft-passport-in-your-organization.md)
+[Learn how to implement and manage Microsoft Passport in your organization.](../keep-secure/implement-microsoft-passport-in-your-organization.md)
## Learn more
-[Why a PIN is better than a password](/windows/keep-secure/why-a-pin-is-better-than-a-password.md)
+[Why a PIN is better than a password](../keep-secure/why-a-pin-is-better-than-a-password.md)
[Windows 10: Disrupting the Revolution of Cyber-Threats with Revolutionary Security!](http://go.microsoft.com/fwlink/p/?LinkId=533890)
diff --git a/windows/whats-new/provisioning-and-upgrade.md b/windows/whats-new/provisioning-and-upgrade.md
index cd4848c2e9..676106047c 100644
--- a/windows/whats-new/provisioning-and-upgrade.md
+++ b/windows/whats-new/provisioning-and-upgrade.md
@@ -93,9 +93,9 @@ Provisioning packages can be applied both during image deployment and during run
## Related topics
-[Update Windows 10 images with provisioning packages](/windows/deploy/update-windows-10-images-with-provisioning-packages.md)
+[Update Windows 10 images with provisioning packages](../deploy/update-windows-10-images-with-provisioning-packages.md)
-[Configure devices without MDM](/windows/manage/configure-devices-without-mdm.md)
+[Configure devices without MDM](../manage/configure-devices-without-mdm.md)
diff --git a/windows/whats-new/security-auditing.md b/windows/whats-new/security-auditing.md
index 7667144023..3368032ca3 100644
--- a/windows/whats-new/security-auditing.md
+++ b/windows/whats-new/security-auditing.md
@@ -35,11 +35,11 @@ In Windows 10, security auditing has added some improvements:
In Windows 10, two new audit subcategories were added to the Advanced Audit Policy Configuration to provide greater granularity in audit events:
-- [Audit Group Membership](/windows/keep-secure/audit-group-membership.md) Found in the Logon/Logoff audit category, the Audit Group Membership subcategory allows you to audit the group membership information in a user's logon token. Events in this subcategory are generated when group memberships are enumerated or queried on the PC where the logon session was created. For an interactive logon, the security audit event is generated on the PC that the user logged on to. For a network logon, such as accessing a shared folder on the network, the security audit event is generated on the PC hosting the resource.
+- [Audit Group Membership](../keep-secure/audit-group-membership.md) Found in the Logon/Logoff audit category, the Audit Group Membership subcategory allows you to audit the group membership information in a user's logon token. Events in this subcategory are generated when group memberships are enumerated or queried on the PC where the logon session was created. For an interactive logon, the security audit event is generated on the PC that the user logged on to. For a network logon, such as accessing a shared folder on the network, the security audit event is generated on the PC hosting the resource.
When this setting is configured, one or more security audit events are generated for each successful logon. You must also enable the **Audit Logon** setting under **Advanced Audit Policy Configuration\\System Audit Policies\\Logon/Logoff**. Multiple events are generated if the group membership information cannot fit in a single security audit event.
-- [Audit PNP Activity](/windows/keep-secure/audit-pnp-activity.md) Found in the Detailed Tracking category, the Audit PNP Activity subcategory allows you to audit when plug and play detects an external device.
+- [Audit PNP Activity](../keep-secure/audit-pnp-activity.md) Found in the Detailed Tracking category, the Audit PNP Activity subcategory allows you to audit when plug and play detects an external device.
Only Success audits are recorded for this category. If you do not configure this policy setting, no audit event is generated when an external device is detected by plug and play.
@@ -166,7 +166,7 @@ Event ID 4826 has been added to track the following changes to the Boot Configur
Event ID 6416 has been added to track when an external device is detected through Plug and Play. One important scenario is if an external device that contains malware is inserted into a high-value machine that doesn’t expect this type of action, such as a domain controller.
-[Learn how to manage your security audit policies within your organization](/windows/keep-secure/security-auditing-overview-glbl.md).
+[Learn how to manage your security audit policies within your organization](../keep-secure/security-auditing-overview-glbl.md).
diff --git a/windows/whats-new/security.md b/windows/whats-new/security.md
index cc2dccc49f..8250797922 100644
--- a/windows/whats-new/security.md
+++ b/windows/whats-new/security.md
@@ -68,7 +68,7 @@ New desktops and laptops will be available to expedite your Device Guard impleme
- **Not supported for Device Guard**. Many current devices cannot take advantage of all Device Guard features because they don’t have the required hardware components or HVCI-compatible drivers. However, most of these devices can enable some Device Guard features, such as configurable code integrity.
-For more information about how to prepare for, manage, and deploy Device Guard, see the [Device Guard deployment guide](/windows/keep-secure/device-guard-deployment-guide.md).
+For more information about how to prepare for, manage, and deploy Device Guard, see the [Device Guard deployment guide](../keep-secure/device-guard-deployment-guide.md).
### Configurable code integrity
@@ -86,7 +86,7 @@ Configurable code integrity is not intended to replace technologies that allow o
Configurable code integrity is not limited to Windows Store applications. In fact, it is not even limited to existing signed applications. Windows 10 gives you a way to sign line-of-business or third-party applications without having to repackage them: you can monitor the application’s installation and initial execution to create a list of binaries called a catalog file. When created, you sign these catalog files and add the signing certificate to the code integrity policy so that those binaries contained within the catalog files are allowed to execute. Then, you can use Group Policy, Configuration Manager, or any other familiar management tool to distribute these catalog files to your client machines. Historically, most malware has been unsigned; simply by deploying code integrity policies, your organization can immediately protect itself against unsigned malware, which is responsible for most modern attacks.
**Note**
-For detailed deployment and planning information about configurable code integrity, see the [Device Guard deployment guide](/windows/keep-secure/device-guard-deployment-guide.md).
+For detailed deployment and planning information about configurable code integrity, see the [Device Guard deployment guide](../keep-secure/device-guard-deployment-guide.md).
@@ -107,7 +107,7 @@ Configurable code integrity is available in Windows 10 Enterprise and Windows
-You can enable configurable code integrity as part of a Device Guard deployment or as a stand-alone component. In addition, you can run configurable code integrity on hardware that is compatible with the Windows 7 operating system, even if such hardware is not Device Guard ready. Code integrity policies can align with an existing application catalog, existing corporate imaging strategy, or with any other method that provides the organization’s desired levels of restriction. For more information about configurable code integrity with Device Guard, see the [Device Guard deployment guide](/windows/keep-secure/device-guard-deployment-guide.md).
+You can enable configurable code integrity as part of a Device Guard deployment or as a stand-alone component. In addition, you can run configurable code integrity on hardware that is compatible with the Windows 7 operating system, even if such hardware is not Device Guard ready. Code integrity policies can align with an existing application catalog, existing corporate imaging strategy, or with any other method that provides the organization’s desired levels of restriction. For more information about configurable code integrity with Device Guard, see the [Device Guard deployment guide](../keep-secure/device-guard-deployment-guide.md).
### Measured Boot and remote attestation
@@ -210,7 +210,7 @@ Because it requires isolated user mode and a Hyper-V hypervisor, you cannot conf
-The Credential Guard feature is targeted at resisting the use of pass-the-hash and pass-the-ticket techniques. By employing a MFA option such as Microsoft Passport with Credential Guard, you can gain additional protection against such threats. For more in-depth information about how Credential Guard works and the specific mitigations it provides, see [Protect derived domain credentials with Credential Guard](/windows/keep-secure/credential-guard.md).
+The Credential Guard feature is targeted at resisting the use of pass-the-hash and pass-the-ticket techniques. By employing a MFA option such as Microsoft Passport with Credential Guard, you can gain additional protection against such threats. For more in-depth information about how Credential Guard works and the specific mitigations it provides, see [Protect derived domain credentials with Credential Guard](../keep-secure/credential-guard.md).
## Windows 10 hardware considerations
@@ -247,13 +247,13 @@ In this table, **R** stands for *recommended*, **Y** means that the hardware com
[Making Windows 10 More Personal and More Secure with Windows Hello](http://go.microsoft.com/fwlink/p/?LinkId=717551)
-[Protect BitLocker from pre-boot attacks](/windows/keep-secure/protect-bitlocker-from-pre-boot-attacks.md)
+[Protect BitLocker from pre-boot attacks](../keep-secure/protect-bitlocker-from-pre-boot-attacks.md)
-[BitLocker Countermeasures](/windows/keep-secure/bitlocker-countermeasures.md)
+[BitLocker Countermeasures](../keep-secure/bitlocker-countermeasures.md)
-[Device Guard deployment guide](/windows/keep-secure/device-guard-deployment-guide.md)
+[Device Guard deployment guide](../keep-secure/device-guard-deployment-guide.md)
-[Protect derived domain credentials with Credential Guard](/windows/keep-secure/credential-guard.md)
+[Protect derived domain credentials with Credential Guard](../keep-secure/credential-guard.md)
diff --git a/windows/whats-new/trusted-platform-module.md b/windows/whats-new/trusted-platform-module.md
index 43b2c111d7..1cde0948c8 100644
--- a/windows/whats-new/trusted-platform-module.md
+++ b/windows/whats-new/trusted-platform-module.md
@@ -48,7 +48,7 @@ Some things that you can check on the device are:
-[Learn how to deploy and manage TPM within your organization](/windows/keep-secure/trusted-platform-module-technology-overview.md).
+[Learn how to deploy and manage TPM within your organization](../keep-secure/trusted-platform-module-technology-overview.md).
diff --git a/windows/whats-new/user-account-control.md b/windows/whats-new/user-account-control.md
index de2d2ddfd7..911bd1fcba 100644
--- a/windows/whats-new/user-account-control.md
+++ b/windows/whats-new/user-account-control.md
@@ -24,7 +24,7 @@ In Windows 10, User Account Control has added some improvements.
- **Integration with the Antimalware Scan Interface (AMSI)**. The [AMSI](http://msdn.microsoft.com/library/windows/desktop/dn889587.aspx) scans all UAC elevation requests for malware. If malware is detected, the admin privilege is blocked.
-[Learn how to manage User Account Control within your organization](/windows/keep-secure/user-account-control-overview.md).
+[Learn how to manage User Account Control within your organization](../keep-secure/user-account-control-overview.md).
diff --git a/windows/whats-new/windows-spotlight.md b/windows/whats-new/windows-spotlight.md
index e659d8726c..304f847ce9 100644
--- a/windows/whats-new/windows-spotlight.md
+++ b/windows/whats-new/windows-spotlight.md
@@ -59,7 +59,7 @@ Pay attention to the checkbox in **Options**. In addition to providing the path
## Related topics
-[Manage Windows 10 Start layout options](/windows/manage/windows-10-start-layout-options-and-policies.md)
+[Manage Windows 10 Start layout options](../manage/windows-10-start-layout-options-and-policies.md)
diff --git a/windows/whats-new/windows-update-for-busines.md b/windows/whats-new/windows-update-for-busines.md
index 5c10a0289c..e18fe862c7 100644
--- a/windows/whats-new/windows-update-for-busines.md
+++ b/windows/whats-new/windows-update-for-busines.md
@@ -33,11 +33,11 @@ Together, these Windows Update for Business features help reduce device manageme
## Learn more
-[Windows Update for Business](/windows/plan/windows-update-for-business.md)
+[Windows Update for Business](../plan/windows-update-for-business.md)
-[Setup and deployment](/windows/plan/setup-and-deployment.md)
+[Setup and deployment](../plan/setup-and-deployment.md)
-[Integration with management solutions](/windows/plan/integration-with-management-solutions-.md)
+[Integration with management solutions](../plan/integration-with-management-solutions-.md)