deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 02:43:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

test migration of everything

Browse Source
This commit is contained in:
Brian Lich
2016-03-07 16:53:55 -08:00
parent db8fb9a516
commit afab4332a6
655 changed files with 51217 additions and 59 deletions
Download Patch File Download Diff File Expand all files Collapse all files

115
windows/plan/TOC.md
View File

@ -1 +1,114 @@
#[Plan](placeholder.md)
# [Plan for Windows 10 deployment](planning-for-windows-10-deployment.md)
## [Change history for Plan for Windows 10 deployment](change-history-for-plan-for-windows-10-deployment.md)
## [Windows 10 servicing options](windows-10-servicing-model.md)
## [Windows 10 deployment considerations](windows-10-deployment-considerations.md)
## [Windows 10 compatibility](windows-10-compatibility.md)
## [Windows 10 infrastructure requirements](windows-10-infrastructure-requirements.md)
## [Windows Update for Business](windows-update-for-business.md)
### [Setup and deployment](setup-and-deployment.md)
### [Integration with management solutions](integration-with-management-solutions-.md)
## [Guidance for education environments](guidance-for-education-environments.md)
### [Chromebook migration guide](chromebook-migration-guide.md)
## [Windows To Go: feature overview](windows-to-go-feature-overview-scenario.md)
### [Best practice recommendations for Windows To Go](best-practice-recommendations-for-windows-to-go.md)
### [Deployment considerations for Windows To Go](deployment-considerations-for-windows-to-go.md)
### [Prepare your organization for Windows To Go](prepare-your-organization-for-windows-to-go.md)
### [Security and data protection considerations for Windows To Go](security-and-data-protection-considerations-for-windows-to-go.md)
### [Windows To Go: frequently asked questions](windows-to-go-frequently-asked-questions.md)
## [Application Compatibility Toolkit (ACT) Technical Reference](application-compatibility-toolkit--act--technical-reference.md)
### [Welcome to ACT](welcome-to-act.md)
#### [What's New in ACT 6.1](whats-new-in-act-60.md)
#### [Software Requirements for ACT](software-requirements-for-act.md)
#### [Software Requirements for RAP](software-requirements-for-rap.md)
### [Configuring ACT](configuring-act.md)
#### [ACT Tools, Packages, and Services](act-tools-packages-and-services.md)
#### [ACT Deployment Options](act-deployment-options.md)
#### [ACT Database Configuration](act-database-configuration.md)
#### [ACT Database Migration](act-database-migration.md)
#### [ACT LPS Share Permissions](act-lps-share-permissions.md)
### [Using ACT](using-act.md)
#### [Taking Inventory of Your Organization](taking-inventory-of-your-organization.md)
##### [Identifying Computers for Inventory Collection](identifying-computers-for-inventory-collection.md)
##### [Creating an Inventory-Collector Package](creating-an-inventory-collector-package.md)
##### [Deploying an Inventory-Collector Package](deploying-an-inventory-collector-package.md)
#### [Testing Compatibility on the Target Platform](testing-compatibility-on-the-target-platform.md)
##### [Deciding Which Applications to Test](deciding-which-applications-to-test.md)
##### [Creating an Enterprise Environment for Compatibility Testing](creating-an-enterprise-environment-for-compatibility-testing.md)
##### [Creating a Runtime-Analysis Package](creating-a-runtime-analysis-package.md)
##### [Deploying a Runtime-Analysis Package](deploying-a-runtime-analysis-package.md)
##### [Compatibility Monitor User's Guide](compatibility-monitor-users-guide.md)
###### [Using Compatibility Monitor to Send Feedback](using-compatibility-monitor-to-send-feedback.md)
###### [Common Compatibility Issues](common-compatibility-issues.md)
#### [Managing Your Data-Collection Packages](managing-your-data-collection-packages.md)
##### [Log File Locations for Data-Collection Packages](log-file-locations-for-data-collection-packages.md)
##### [Exporting a Data-Collection Package](exporting-a-data-collection-package.md)
##### [Deleting a Data-Collection Package](deleting-a-data-collection-package.md)
##### [Labeling Data in ACM](labeling-data-in-acm.md)
#### [Analyzing Your Compatibility Data](analyzing-your-compatibility-data.md)
##### [Viewing Your Compatibility Reports](viewing-your-compatibility-reports.md)
###### [<OperatingSystem> - Application Report](operatingsystem---application-report.md)
####### [<Application> Dialog Box](application-dialog-box.md)
###### [<OperatingSystem> - Computer Report](operatingsystem---computer-report.md)
####### [<Computer> Dialog Box](computer-dialog-box.md)
###### [<OperatingSystem> - Device Report](operatingsystem---device-report.md)
####### [<Device> Dialog Box](device-dialog-box.md)
###### [Internet Explorer - Web Site Report](internet-explorer---web-site-report.md)
####### [<WebsiteURL> Dialog Box](websiteurl-dialog-box.md)
###### [Saving, Opening, and Exporting Reports](saving-opening-and-exporting-reports.md)
###### [Customizing Your Report Views](customizing-your-report-views.md)
##### [Organizing Your Compatibility Data](organizing-your-compatibility-data.md)
###### [Organizational Tasks for Each Report Type](organizational-tasks-for-each-report-type.md)
###### [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)
####### [Adding or Editing an Issue](adding-or-editing-an-issue.md)
####### [Adding or Editing a Solution](adding-or-editing-a-solution.md)
####### [Resolving an Issue](resolving-an-issue.md)
##### [Filtering Your Compatibility Data](filtering-your-compatibility-data.md)
###### [Example Filter Queries](example-filter-queries.md)
##### [Sending and Receiving Compatibility Data](sending-and-receiving-compatibility-data.md)
###### [Data Sent Through the Microsoft Compatibility Exchange](data-sent-through-the-microsoft-compatibility-exchange.md)
###### [ACT Community Ratings and Process](act-community-ratings-and-process.md)
#### [Fixing Compatibility Issues](fixing-compatibility-issues.md)
##### [Deciding Whether to Fix an Application or Deploy a Workaround](deciding-whether-to-fix-an-application-or-deploy-a-workaround.md)
##### [SUA User's Guide](sua-users-guide.md)
###### [Using the SUA Wizard](using-the-sua-wizard.md)
###### [Using the SUA Tool](using-the-sua-tool.md)
####### [Tabs on the SUA Tool Interface](tabs-on-the-sua-tool-interface.md)
####### [Showing Messages Generated by the SUA Tool](showing-messages-generated-by-the-sua-tool.md)
####### [Applying Filters to Data in the SUA Tool](applying-filters-to-data-in-the-sua-tool.md)
####### [Fixing Applications by Using the SUA Tool](fixing-applications-by-using-the-sua-tool.md)
##### [Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
###### [Using the Compatibility Administrator Tool](using-the-compatibility-administrator-tool.md)
####### [Available Data Types and Operators in Compatibility Administrator](available-data-types-and-operators-in-compatibility-administrator.md)
####### [Searching for Fixed Applications in Compatibility Administrator](searching-for-fixed-applications-in-compatibility-administrator.md)
####### [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)
####### [Creating a Custom Compatibility Fix in Compatibility Administrator](creating-a-custom-compatibility-fix-in-compatibility-administrator.md)
####### [Creating a Custom Compatibility Mode in Compatibility Administrator](creating-a-custom-compatibility-mode-in-compatibility-administrator.md)
####### [Creating an AppHelp Message in Compatibility Administrator](creating-an-apphelp-message-in-compatibility-administrator.md)
####### [Viewing the Events Screen in Compatibility Administrator](viewing-the-events-screen-in-compatibility-administrator.md)
####### [Enabling and Disabling Compatibility Fixes in Compatibility Administrator](enabling-and-disabling-compatibility-fixes-in-compatibility-administrator.md)
####### [Installing and Uninstalling Custom Compatibility Databases in Compatibility Administrator](installing-and-uninstalling-custom-compatibility-databases-in-compatibility-administrator.md)
###### [Managing Application-Compatibility Fixes and Custom Fix Databases](managing-application-compatibility-fixes-and-custom-fix-databases.md)
####### [Understanding and Using Compatibility Fixes](understanding-and-using-compatibility-fixes.md)
####### [Compatibility Fix Database Management Strategies and Deployment](compatibility-fix-database-management-strategies-and-deployment.md)
####### [Testing Your Application Mitigation Packages](testing-your-application-mitigation-packages.md)
###### [Using the Sdbinst.exe Command-Line Tool](using-the-sdbinstexe-command-line-tool.md)
### [Troubleshooting ACT](troubleshooting-act.md)
#### [Troubleshooting the ACT Configuration Wizard](troubleshooting-the-act-configuration-wizard.md)
#### [Troubleshooting the ACT Log Processing Service](troubleshooting-the-act-log-processing-service.md)
#### [Troubleshooting ACT Database Issues](troubleshooting-act-database-issues.md)
### [ACT User Interface Reference](act-user-interface-reference.md)
#### [Toolbar Icons in ACM](toolbar-icons-in-acm-win-8.md)
#### [Ratings Icons in ACM](ratings-icons-in-acm.md)
#### [Activating and Closing Windows in ACM](activating-and-closing-windows-in-acm.md)
#### [Settings for ACM](settings-for-acm.md)
##### [Settings Dialog Box - Settings Tab](settings-dialog-box---settings-tab.md)
##### [Settings Dialog Box - Preferences Tab](settings-dialog-box---preferences-tab.md)
### [ACT Product and Documentation Resources](act-product-and-documentation-resources.md)
### [ACT Glossary](act-glossary.md)
### [Compatibility Fixes for Windows 10, Windows 8, Windows 7, and Windows Vista](compatibility-fixes-for-windows-8-windows-7-and-windows-vista.md)

47
windows/plan/act-community-ratings-and-process.md Normal file
View File

@ -0,0 +1,47 @@
---
title: ACT Community Ratings and Process (Windows 10)
description: The Application Compatibility Toolkit (ACT) Community uses the Microsoft® Compatibility Exchange to share compatibility ratings between all registered ACT Community members.
ms.assetid: be6c8c71-785b-4adf-a375-64ca7d24e26c
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# ACT Community Ratings and Process
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
The Application Compatibility Toolkit (ACT) Community uses the Microsoft® Compatibility Exchange to share compatibility ratings between all registered ACT Community members.
When you access the Microsoft Compatibility Exchange as a registered ACT Community member, you can upload your compatibility data to the community and download issues from other ACT Community members. For information about how compatibility ratings are entered, see [Selecting Your Compatibility Rating](selecting-your-compatibility-rating.md).
ACT takes your information and combines it with all of the information provided by the other ACT Community users and shows the average rating as a color gradient from one to five bars.
![act community](images/dep-win8-e-act-communityexample.gif)
## Process for Synchronizing Compatibility Ratings
The following diagram shows the process for synchronizing compatibility ratings with the ACT Community.
You have the option to exclude applications from being shared with the Microsoft Compatibility Exchange. However, you will not get compatibility ratings from the ACT Community for any application that you exclude. For more information, see [Sending and Receiving Compatibility Data](sending-and-receiving-compatibility-data.md).
![act community workflow](images/dep-win8-l-act-communityworkflowdiagram.jpg)
 
 

84
windows/plan/act-database-configuration.md Normal file
View File

@ -0,0 +1,84 @@
---
title: ACT Database Configuration (Windows 10)
description: The Application Compatibility Toolkit (ACT) uses a Microsoft® SQL Server® database for storing and sharing compatibility issue data.
ms.assetid: 032bbfe0-86fa-48ff-b638-b9d6a908c45e
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# ACT Database Configuration
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
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 Creation
You can create the ACT database by using one of the following methods:
- Run Application Compatibility Manager (ACM), and then use the ACT Configuration Wizard to create a new database.
-or-
- Run the CreateDB.sql file, located at %SYSTEMDRIVE%\\ProgramData\\Microsoft\\Application Compatibility Toolkit\\CreateDB.sql.
### ACT Database Permissions
You must assign the following database roles to the following accounts.
- To the user and local service accounts that will run the ACT Log Processing Service (LPS), assign the db\_datareader, db\_datawriter, and db\_owner database roles.
- To the user account that will run Application Compatibility Manager (ACM), assign the db\_datareader and db\_datawriter database roles.
Alternatively, grant the following explicit permissions to each user that will run the ACT LPS or ACM.
- SELECT
- INSERT
- UPDATE
- DELETE
- EXECUTE
### ACT Database Recommendations
We also recommend that you make the following changes to the database as part of your deployment planning:
- **Create a larger database, including a larger log file–size setting, and then set the growth increments appropriately**. If you create a database with the default setting for data storage, the data portion of the database will have an initial size of 1 megabyte (MB), and a growth increment of 1 MB. If you create a database with the default setting for log file storage, the log file portion of the database will have an initial size of 1 MB and a growth increment of 10 percent. We recommend that you maintain a data-to-log file ratio of 5:1 or 4:1. For example, if your data portion is 5 gigabytes (GB), your log file portion should be 1 GB.
- **Change the recovery model of your database**. The default recovery model is **Full**, but we recommend that you change the recovery model to **Simple** to improve performance and reduce disk space requirements.
- **Store the data portion and log file portion of your ACT database on separate hard drives**. Unless otherwise specified by your SQL Administrator, the default is for the data and log files to be stored on the same hard drive. We recommend separating the data from the log files to reduce disk I/O contention.
## Related topics
[ACT Tools, Packages, and Services](act-tools-packages-and-services.md)
[ACT Deployment Options](act-deployment-options.md)
[ACT Database Migration](act-database-migration.md)
[ACT LPS Share Permissions](act-lps-share-permissions.md)
 
 

67
windows/plan/act-database-migration.md Normal file
View File

@ -0,0 +1,67 @@
---
title: ACT Database Migration (Windows 10)
description: The schema for an ACT database can change when ACT is updated or when a new version of ACT is released.
ms.assetid: b13369b4-1fb7-4889-b0b8-6d0ab61aac3d
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# ACT Database Migration
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
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.
To create the new database, you must have database-creation permissions on the instance of SQL Server.
## Migrating Compatibility Data from an ACT Database
You can migrate compatibility data from an ACT database to a new database by using one of the following methods:
- Run Application Compatibility Manager (ACM), and then use the ACT Configuration Wizard to open the database. The wizard guides you through migrating the compatibility data to a new database.
- Run the MigrateDB.sql file, located at %SYSTEMDRIVE%\\ProgramData\\Microsoft\\Application Compatibility Toolkit\\MigrateDB.sql.. The following table shows the location of the MigrateDB.sql file.
## Database Migration from ACT 5.6
When you migrate compatibility data from an ACT 5.6 database to a new database, the following information is excluded from the migration:
- Issues that were reported by ACT 5.6 data-collection packages (DCPs).
- Solutions that correspond to issues reported by ACT 5.6 DCPs.
- Lists of file names that ACT 5.6 associated with each application.
You cannot migrate any compatibility data from ACT databases that were created on a version of ACT before ACT 5.6.
## Related topics
[ACT Tools, Packages, and Services](act-tools-packages-and-services.md)
[ACT Deployment Options](act-deployment-options.md)
[ACT Database Configuration](act-database-configuration.md)
[ACT LPS Share Permissions](act-lps-share-permissions.md)
 
 

60
windows/plan/act-deployment-options.md Normal file
View File

@ -0,0 +1,60 @@
---
title: ACT Deployment Options (Windows 10)
description: While planning your deployment of the Application Compatibility Toolkit (ACT), consider which computers you want running the various tools, packages, and services for ACT.
ms.assetid: 90d56dd8-8d57-44e8-bf7a-29aabede45ba
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# ACT Deployment Options
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
While planning your deployment of the Application Compatibility Toolkit (ACT), consider which computers you want running the various tools, packages, and services for ACT.
The following diagram shows supported deployment options for an ACT installation. The options listed first are the most highly recommended.
![act supported topologies](images/dep-win8-l-act-supportedtopologies.jpg)
## Collecting Data Across Domains
If you plan to deploy inventory-collector packages to computers running Windows XP, where some of the computers are on a different domain than the ACT LPS share, do one of the following:
- Set up a separate ACT LPS share on each domain and configure the inventory-collector package to upload log files to the ACT LPS share on the same domain.
- Set up a single ACT LPS share on one computer. On the computer that hosts the share, use Group Policy to allow connections from anonymous users.
These steps are not necessary if the computers where you deploy inventory-collector packages are running Windows Vista, Windows 7, Windows 8, Windows 8.1, or Windows 10.
If you choose to have distributed logging with a subsequent step of moving log files to your central share, move the files to the central share before processing the files. You can move the files manually or use a technology like Distributed File-System Replication (DFSR).
## Related topics
[ACT Tools, Packages, and Services](act-tools-packages-and-services.md)
[ACT Database Configuration](act-database-configuration.md)
[ACT Database Migration](act-database-migration.md)
[ACT LPS Share Permissions](act-lps-share-permissions.md)
 
 

117
windows/plan/act-glossary.md Normal file
View File

@ -0,0 +1,117 @@
---
title: ACT Glossary (Windows 10)
description: The following table lists terms and definitions used by the Application Compatibility Toolkit (ACT).
ms.assetid: 984d1cce-c1ac-4aa8-839a-a23e15da6f32
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# ACT Glossary
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
The following table lists terms and definitions used by the Application Compatibility Toolkit (ACT).
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Term</th>
<th align="left">Definition</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>ACT Community</p></td>
<td align="left"><p>An online environment that enables ACT users to share issues and solution data with other registered ACT users.</p></td>
</tr>
<tr class="even">
<td align="left"><p>ACT Log Processing Service (LPS)</p></td>
<td align="left"><p>The service that processes the log files uploaded from your client computers, adding the information to your ACT database.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>AppHelp message</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Application Compatibility Manager (ACM)</p></td>
<td align="left"><p>The user interface that enables you to view reports generated from the ACT database. This is also where you create data-collection packages.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Compatibility Administrator</p></td>
<td align="left"><p>A tool that enables you to create and deploy compatibility fixes, compatibility modes, and AppHelp messages, to resolve your compatibility issues.</p></td>
</tr>
<tr class="even">
<td align="left"><p>compatibility fix</p></td>
<td align="left"><p>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 &quot;shim&quot;.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>compatibility mode</p></td>
<td align="left"><p>Group of compatibility fixes found to resolve many common application compatibility issues.</p></td>
</tr>
<tr class="even">
<td align="left"><p>compatibility solution</p></td>
<td align="left"><p>The solution to a known compatibility issue, as entered by the user, Microsoft, or a vendor.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>data-collection package</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="even">
<td align="left"><p>deployment</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>independent software vendor (ISV)</p></td>
<td align="left"><p>An individual or an organization that independently creates computer software.</p></td>
</tr>
<tr class="even">
<td align="left"><p>inventory-collector package</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Microsoft Compatibility Exchange</p></td>
<td align="left"><p>A web service that transfers compatibility information between Microsoft and the ACT database.</p></td>
</tr>
<tr class="even">
<td align="left"><p>runtime-analysis package</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>session 0</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="even">
<td align="left"><p>shim</p></td>
<td align="left"><p>See Other Term: compatibility fix</p></td>
</tr>
<tr class="odd">
<td align="left"><p>User Account Control (UAC)</p></td>
<td align="left"><p>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.</p></td>
</tr>
</tbody>
</table>
 
 
 

75
windows/plan/act-lps-share-permissions.md Normal file
View File

@ -0,0 +1,75 @@
---
title: ACT LPS Share Permissions (Windows 10)
description: To upload log files to the ACT Log Processing Service (LPS) share, certain permissions must be set at the share level and folder level.
ms.assetid: 51f6ddf7-f424-4abe-a0e0-71fe616f9e84
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# ACT LPS Share Permissions
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
To upload log files to the ACT Log Processing Service (LPS) share, certain permissions must be set at the share level and folder level.
## Share-Level Permissions
The **Everyone** group must have **Change** and **Read** permissions to the ACT LPS share.
**To set the share-level permissions**
1. Browse to the ACT LPS share, right-click the folder, and select **Properties**.
2. Click the **Sharing** tab, share the folder, and then click **Permissions**.
3. Add the **Everyone** group if it is not already listed, and then select the **Change** and **Read** check boxes in the **Allow** column.
## Folder-Level Permissions (NTFS Only)
The **Everyone** group must have **Write** access to the ACT LPS share.
The ACT Log Processing Service account must have **List Folder Contents**, **Read**, and **Write** permissions.
- If the ACT Log Processing Service account is **Local System Account**, apply the permissions to the *&lt;domain&gt;*\\*&lt;computer&gt;*$ account.
- If the ACT Log Processing Service is a user account, apply the permissions to the specific user.
**To set the folder-level permissions**
1. In Windows Explorer, right-click the folder for the ACT LPS share, and then click **Properties**.
2. Click the **Security** tab, add the account that runs the ACT Log Processing Service, and then select the **List Folder Contents**, **Read**, and **Write** check boxes in the **Allow** column.
3. Add the **Everyone** group if it is not already listed, and then select the **Write** check box in the **Allow** column.
## Related topics
[ACT Tools, Packages, and Services](act-tools-packages-and-services.md)
[ACT Deployment Options](act-deployment-options.md)
[ACT Database Configuration](act-database-configuration.md)
[ACT Database Migration](act-database-migration.md)
 
 

66
windows/plan/act-product-and-documentation-resources.md Normal file
View File

@ -0,0 +1,66 @@
---
title: ACT Product and Documentation Resources (Windows 10)
description: The following sections provide links to resources and reference material for the Application Compatibility Toolkit (ACT).
ms.assetid: c7954b5a-164d-4548-af58-cd3a1de5cc43
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# ACT Product and Documentation Resources
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
The following sections provide links to resources and reference material for the Application Compatibility Toolkit (ACT).
## Information Related to the Application Compatibility Toolkit
- [Microsoft SQL Server](http://go.microsoft.com/fwlink/p/?LinkId=184584). Use Microsoft SQL Server to take full advantage of ACT features. Visit the SQL Server home page for product information, technical resources, and support.
- [Microsoft SQL Server Express Edition](http://go.microsoft.com/fwlink/p/?LinkId=690325). If you are not already running SQL Server, download a free version of SQL Server Express and its management tools.
- [Microsoft System Center Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=690326). Visit the System Center Configuration Manager home page for product information, technical resources, and support.
- [Microsoft Application Verifier](http://go.microsoft.com/fwlink/p/?LinkId=52529). Application Verifier is required by the Standard User Analyzer tool.
## Information About Application Compatibility
- [Application Compatibility home page](http://go.microsoft.com/fwlink/p/?LinkId=184586). Go here for general application compatibility information, including videos, key resources, advice, and technical guidance.
- [Windows Developer Center home page](http://go.microsoft.com/fwlink/p/?LinkId=184587). Find information about the Windows SDK, including how to develop your application, how to get help with compatibility issues, and other development-related content.
## Information About Windows Deployment
- [Microsoft Deployment Toolkit](http://go.microsoft.com/fwlink/p/?LinkId=618117). Download the latest version of the Microsoft Deployment Toolkit (MDT) to assist with image creation and automated installation, reduce deployment time, standardize desktop and server images, limit service disruptions, reduce post-deployment help desk costs, and improve security and ongoing configuration management.
- [Windows website](http://go.microsoft.com/fwlink/p/?LinkId=731). Visit the Windows home page for product information, technical resources, and support.
## Related topics
[Troubleshooting ACT](troubleshooting-act.md)
[Using ACT](using-act.md)
[Software Requirements for ACT](software-requirements-for-act.md)
 
 

59
windows/plan/act-tools-packages-and-services.md Normal file
View File

@ -0,0 +1,59 @@
---
title: ACT Tools, Packages, and Services (Windows 10)
description: The Application Compatibility Toolkit is included with the Windows ADK. Download the Windows ADK.
ms.assetid: f5a16548-7d7b-4be9-835e-c06158dd0b89
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# ACT Tools, Packages, and Services
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
The Application Compatibility Toolkit is included with the Windows ADK. [Download the Windows ADK.](http://go.microsoft.com/fwlink/p/?LinkId=526740)
ACT includes the following:
- **Application Compatibility Manager (ACM):** A tool that you can use to create your data-collection packages and analyze the collected inventory and compatibility data.
- **Inventory-collector package:** A data-collection package that can be deployed to computers to gather inventory data that will be uploaded to the ACT database.
- **Runtime-analysis package:** A data-collection package that can be deployed to computers in a test environment for compatibility testing on the new operating system.
- **ACT Log Processing Service (LPS):** A service that is used to process the ACT log files uploaded from the computers where your data-collection packages have been installed. The service adds the information to your ACT database.
- **ACT LPS share:** A file share that is accessed by the ACT LPS, to store the log files that will be processed and added to the ACT database.
- **ACT database:** A Microsoft® SQL Server database that stores the collected inventory and compatibility data. You can use ACM to view the information stored in the ACT database.
- **Microsoft Compatibility Exchange:** A web service that propagates application-compatibility issues.
## Related topics
[ACT Deployment Options](act-deployment-options.md)
[ACT Database Configuration](act-database-configuration.md)
[ACT Database Migration](act-database-migration.md)
[ACT LPS Share Permissions](act-lps-share-permissions.md)
 
 

73
windows/plan/act-user-interface-reference.md Normal file
View File

@ -0,0 +1,73 @@
---
title: ACT User Interface Reference (Windows 10)
description: This section contains information about the user interface for Application Compatibility Manager (ACM), which is a tool in the Application Compatibility Toolkit (ACT).
ms.assetid: 303d3dd7-2cc1-4f5f-b032-b7e288b04893
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# ACT User Interface Reference
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
This section contains information about the user interface for Application Compatibility Manager (ACM), which is a tool in the Application Compatibility Toolkit (ACT).
## In this section
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Topic</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[Toolbar Icons in ACM](toolbar-icons-in-acm-win-8.md)</p></td>
<td align="left"><p>The following table shows icons that appear on toolbars and navigational elements in Application Compatibility Manager (ACM).</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Ratings Icons in ACM](ratings-icons-in-acm.md)</p></td>
<td align="left"><p>Compatibility ratings can originate from Microsoft, the application vendor, your organization, and from the Application Compatibility Toolkit (ACT) community.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Activating and Closing Windows in ACM](activating-and-closing-windows-in-acm.md)</p></td>
<td align="left"><p>The <strong>Windows</strong> dialog box shows the windows that are open in Application Compatibility Manager (ACM).</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Settings for ACM](settings-for-acm.md)</p></td>
<td align="left"><p>This section provides information about settings that you can configure in Application Compatibility Manager (ACM).</p></td>
</tr>
</tbody>
</table>
 
## Related topics
[Using ACT](using-act.md)
 
 

51
windows/plan/activating-and-closing-windows-in-acm.md Normal file
View File

@ -0,0 +1,51 @@
---
title: Activating and Closing Windows in ACM (Windows 10)
description: The Windows dialog box shows the windows that are open in Application Compatibility Manager (ACM).
ms.assetid: 747bf356-d861-4ce7-933e-fa4ecfac7be5
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Activating and Closing Windows in ACM
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
The **Windows** dialog box shows the windows that are open in Application Compatibility Manager (ACM).
**To view a list of the open windows in ACM**
- On the **Window** menu, click **Windows**.
**To show an open window in ACM**
- In the **Windows** dialog box, click the window name from the list of open windows, and then click **Activate**.
The selected window appears on top of any others on your screen.
**To close one or more windows in ACM**
- In the **Windows** dialog box, click one or more window names from the list of open windows, and then click **Close Window(s)**.
## Related topics
[Managing Your Data-Collection Packages](managing-your-data-collection-packages.md)
 
 

104
windows/plan/adding-or-editing-a-solution.md Normal file
View File

@ -0,0 +1,104 @@
---
title: Adding or Editing a Solution (Windows 10)
description: 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.
ms.assetid: 86cb8804-d577-4af6-b96f-5e0409784a23
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Adding or Editing a Solution
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
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.
## Adding Solutions for Compatibility Issues with Your Applications and Websites
You can view or add solutions only for applications or websites.
**Note**  
The following examples use the **&lt;Application\_Name&gt;** dialog box. The procedures for websites are similar.
 
**To add a solution**
1. On the **&lt;Operating\_System&gt; - Application Report** screen, double-click the name of the application to display the **&lt;Application\_Name&gt;** dialog box.
2. Click the **Issues** tab.
3. On the **Actions** menu, click **Add Solution**.
4. Enter the information from the following table, and then click **Save**.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Field</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Title</p></td>
<td align="left"><p>Can be up to 100 characters in length.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Solution Type</p></td>
<td align="left"><p>You must select a value from the list.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Solution Details</p></td>
<td align="left"><p>Information about your solution, including the steps to reproduce your fix.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Solution Details URL</p></td>
<td align="left"><p>URL for a page that shows more information about the solution.</p></td>
</tr>
</tbody>
</table>
 
**To edit an existing solution**
1. On the **&lt;Operating\_System&gt; - Application Report** screen, double-click the name of the application to display the &lt;Application\_Name&gt; dialog box.
2. Click the **Issues** tab.
3. Double-click the issue that includes the solution that you want to modify.
4. Click the **Solutions** tab.
5. Double-click the solution to edit.
6. Modify the information about the solution, and then click **Save**.
**Note**  
You can only modify your own solutions. You cannot modify solutions entered by other users.
 
 
 

114
windows/plan/adding-or-editing-an-issue.md Normal file
View File

@ -0,0 +1,114 @@
---
title: Adding or Editing an Issue (Windows 10)
description: In Application Compatibility Manager (ACM), you can enter information about the compatibility issues that you discover.
ms.assetid: 8a9fff79-9f88-4ce2-a4e6-b9382f28143d
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Adding or Editing an Issue
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
In Application Compatibility Manager (ACM), you can enter information about the compatibility issues that you discover.
You can use the Microsoft Compatibility Exchange to share compatibility information with others. For information about the Microsoft Compatibility Exchange, see [Sending and Receiving Compatibility Data](sending-and-receiving-compatibility-data.md).
## Adding Issues for Your Applications and Websites
You can view or add issues only for applications or websites.
**Note**  
The following examples use the **&lt;Application\_Name&gt;** dialog box. The procedures are similar for websites.
 
**To add an issue**
1. On the **&lt;Operating\_System&gt; - Application Report** screen, double-click the name of the application to display the **&lt;Application\_Name&gt;** dialog box.
2. On the **Actions** menu, click **Add Issue**.
3. Enter the information from the following table, and then click **Save**.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Field</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Title</p></td>
<td align="left"><p>Can be up to 256 characters in length.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Priority</p></td>
<td align="left"><p>You must select a value from the list.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Severity</p></td>
<td align="left"><p>You must select a value from the list.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Symptom</p></td>
<td align="left"><p>You must select a value from the list.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Cause</p></td>
<td align="left"><p>You must select a value from the list.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Affected Operating Systems</p></td>
<td align="left"><p>Operating systems on which the issue occurs. You must select at least one operating system.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Issue Description</p></td>
<td align="left"><p>Description of the issue, including the steps to reproduce the problem.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Link to More Information</p></td>
<td align="left"><p>URL for a page that shows more information about the issue.</p></td>
</tr>
</tbody>
</table>
 
**To edit an existing issue**
1. On the **&lt;Operating\_System&gt; - Application Report** screen, double-click the name of the application that includes the issue you want to modify.
2. In the **&lt;Application\_Name&gt;** dialog box, click the **Issues** tab, and then double-click the specific issue to be edited.
3. Modify the issue information, and then click **Save**.
**Note**  
You can modify your own issues. You cannot modify issues entered by another user.
 
 
 

79
windows/plan/analyzing-your-compatibility-data.md Normal file
View File

@ -0,0 +1,79 @@
---
title: Analyzing Your Compatibility Data (Windows 10)
description: This section provides information about viewing and working with your compatibility data in Application Compatibility Manager (ACM).
ms.assetid: b98f3d74-fe22-41a2-afe8-2eb2799933a1
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Analyzing Your Compatibility Data
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
This section provides information about viewing and working with your compatibility data in Application Compatibility Manager (ACM).
## In this section
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Topic</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[Viewing Your Compatibility Reports](viewing-your-compatibility-reports.md)</p></td>
<td align="left"><p>This section describes the compatibility reports in Application Compatibility Manager (ACM) and how you can work with the reports.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Organizing Your Compatibility Data](organizing-your-compatibility-data.md)</p></td>
<td align="left"><p>This section provides step-by-step instructions for organizing your compatibility data in Application Compatibility Manager (ACM).</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Filtering Your Compatibility Data](filtering-your-compatibility-data.md)</p></td>
<td align="left"><p>You can use Query Builder to filter your compatibility-issue data or reports by selecting specific restriction criteria.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Sending and Receiving Compatibility Data](sending-and-receiving-compatibility-data.md)</p></td>
<td align="left"><p>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.</p></td>
</tr>
</tbody>
</table>
 
## Related topics
[Taking Inventory of Your Organization](taking-inventory-of-your-organization.md)
[Testing Compatibility on the Target Platform](testing-compatibility-on-the-target-platform.md)
[Managing Your Data-Collection Packages](managing-your-data-collection-packages.md)
[Fixing Compatibility Issues](fixing-compatibility-issues.md)
 
 

88
windows/plan/application-compatibility-toolkit--act--technical-reference.md Normal file
View File

@ -0,0 +1,88 @@
---
title: Application Compatibility Toolkit (ACT) Technical Reference (Windows 10)
description: 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.
ms.assetid: d90d38b2-2718-4481-90eb-4480719627ba
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Application Compatibility Toolkit (ACT) Technical Reference
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
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.
By using 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 you deploy a version of Windows to your organization.
ACT is available in the [Windows Assessment and Deployment Kit (ADK) for Windows 10](http://go.microsoft.com/fwlink/p/?LinkId=526740).
## In this section
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Topic</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[Welcome to ACT](welcome-to-act.md)</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Configuring ACT](configuring-act.md)</p></td>
<td align="left"><p>This section provides information about setting up the Application Compatibility Toolkit (ACT) in your organization.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Using ACT](using-act.md)</p></td>
<td align="left"><p>This section describes how to use the Application Compatibility Toolkit (ACT) in your organization.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Troubleshooting ACT](troubleshooting-act.md)</p></td>
<td align="left"><p>This section provides troubleshooting information for the Application Compatibility Toolkit (ACT).</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[ACT User Interface Reference](act-user-interface-reference.md)</p></td>
<td align="left"><p>This section contains information about the user interface for Application Compatibility Manager (ACM), which is a tool in the Application Compatibility Toolkit (ACT).</p></td>
</tr>
<tr class="even">
<td align="left"><p>[ACT Product and Documentation Resources](act-product-and-documentation-resources.md)</p></td>
<td align="left"><p>The following sections provide links to resources and reference material for the Application Compatibility Toolkit (ACT).</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[ACT Glossary](act-glossary.md)</p></td>
<td align="left"><p>The following table lists terms and definitions used by the Application Compatibility Toolkit (ACT).</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Compatibility Fixes for Windows 10, Windows 8, Windows 7, and Windows Vista](compatibility-fixes-for-windows-8-windows-7-and-windows-vista.md)</p></td>
<td align="left"><p>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.</p></td>
</tr>
</tbody>
</table>
 
 
 

125
windows/plan/application-dialog-box.md Normal file
View File

@ -0,0 +1,125 @@
---
title: &lt;Application&gt; Dialog Box (Windows 10)
description: In Application Compatibility Manager (ACM), the &lt;Application&gt; dialog box shows information about the selected application.
ms.assetid: a43e85a6-3cd4-4235-bc4d-01e4d097db7e
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# &lt;Application&gt; Dialog Box
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
In Application Compatibility Manager (ACM), the *&lt;Application&gt;* dialog box shows information about the selected application.
**To open the &lt;Application&gt; dialog box**
1. In ACM, in the **Quick Reports** pane, click **Analyze**.
2. Under an operating system heading, click **Applications**.
3. Double-click the name of an application.
## Tabs in the &lt;Application&gt; dialog box
The following table shows the information available in the *&lt;Application&gt;* dialog box.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Tab</th>
<th align="left">Information</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Assessment</p></td>
<td align="left"><p>Shows the compatibility ratings for the application from the application vendor, your internal organization, and the ACT Community.</p>
<p>For more information, see [Selecting Your Compatibility Rating](selecting-your-compatibility-rating.md).</p></td>
</tr>
<tr class="even">
<td align="left"><p>Issues</p></td>
<td align="left"><p>For each issue associated with the selected application, shows:</p>
<ul>
<li><p>The issue status, either active (a red X) or resolved (a green check mark).</p></li>
<li><p>The provider who created the record of the issue.</p></li>
<li><p>The severity of the issue as entered by the provider.</p></li>
<li><p>The symptom of the issue as entered by the provider.</p></li>
<li><p>The date on which the issue was added to the ACT database.</p></li>
</ul>
<p>For more information, see [Creating and Editing Issues and Solutions](creating-and-editing-issues-and-solutions.md).</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Application Properties</p></td>
<td align="left"><p>Shows the following properties for the selected application:</p>
<ul>
<li><p><strong>MSI</strong>. Shows the installer name, vendor, version, language, and so on.</p></li>
<li><p><strong>Add/Remove Programs</strong>. Shows the application name that appears in Control Panel, vendor, registry path, and string for uninstalling.</p></li>
<li><p><strong>Shell</strong>. Shows the shortcuts for the application and where the shortcuts appear on the <strong>Start</strong> menu.</p></li>
<li><p><strong>Registry</strong>. Shows the registry name for the application, registry path, file name, and so on.</p></li>
<li><p><strong>Service Control Manager</strong>. Shows the entries in the <strong>Services</strong> console that correspond to the application.</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>Computers</p></td>
<td align="left"><p>Shows the following information for each of the computers that have the specified application installed:</p>
<ul>
<li><p>Computer name, domain, and operating system.</p></li>
<li><p>Media Access Control (MAC) address for the computer.</p></li>
<li><p>Manufacturer of the computer.</p></li>
</ul></td>
</tr>
<tr class="odd">
<td align="left"><p>Labels</p></td>
<td align="left"><p>Shows the label for the selected application.</p>
<p>For information about labels, see [Labeling Data in ACM](labeling-data-in-acm.md).</p></td>
</tr>
<tr class="even">
<td align="left"><p>Feedback</p></td>
<td align="left"><p>Shows feedback that your testers have submitted to the ACT database for the selected application.</p></td>
</tr>
</tbody>
</table>
 
## Using the &lt;Application&gt; Dialog Box
In the **&lt;Application&gt;** dialog box, you can perform the following actions:
- Select your compatibility rating for the application. For more information, see [Selecting Your Compatibility Rating](selecting-your-compatibility-rating.md).
- Select your deployment status for the application. For more information, see [Selecting Your Deployment Status](selecting-your-deployment-status.md).
- Assign categories and subcategories to the application. For more information, see [Categorizing Your Compatibility Data](categorizing-your-compatibility-data.md).
- Specify the importance of the application to your organization. For more information, see [Prioritizing Your Compatibility Data](prioritizing-your-compatibility-data.md).
- Choose whether to synchronize data for the application with the Microsoft Compatibility Exchange. For more information, see [Selecting the Send and Receive Status for an Application](selecting-the-send-and-receive-status-for-an-application.md).
- Add, edit, or resolve an issue for the selected application, and add or edit solutions. For more information, see [Creating and Editing Issues and Solutions](creating-and-editing-issues-and-solutions.md).
 
 

94
windows/plan/applying-filters-to-data-in-the-sua-tool.md Normal file
View File

@ -0,0 +1,94 @@
---
title: Applying Filters to Data in the SUA Tool (Windows 10)
description: On the user interface for the Standard User Analyzer (SUA) tool, you can apply filters to the issues that the tool has found so that you can view only the information that interests you.
ms.assetid: 48c39919-3501-405d-bcf5-d2784cbb011f
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Applying Filters to Data in the SUA Tool
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
On the user interface for the Standard User Analyzer (SUA) tool, you can apply filters to the issues that the tool has found so that you can view only the information that interests you.
**To apply filters to data in the SUA tool**
1. Use the SUA tool to test an application. For more information, see [Using the SUA Tool](using-the-sua-tool.md).
2. After you finish testing, in the SUA tool, click a tab that shows issues that the SUA tool has found. All tabs except the **App Info** tab can show issues.
3. On the **Options** menu, click a command that corresponds to the filter that you want to apply. The following table describes the commands.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Options menu command</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p><strong>Filter Noise</strong></p></td>
<td align="left"><p>Filters noise from the issues.</p>
<p>This command is selected by default.</p></td>
</tr>
<tr class="even">
<td align="left"><p><strong>Load Noise Filter File</strong></p></td>
<td align="left"><p>Opens the <strong>Open Noise Filter File</strong> dialog box, in which you can load an existing noise filter (.xml) file.</p></td>
</tr>
<tr class="odd">
<td align="left"><p><strong>Export Noise Filter File</strong></p></td>
<td align="left"><p>Opens the <strong>Save Noise Filter File</strong> dialog box, in which you can save filter settings as a noise filter (.xml) file.</p></td>
</tr>
<tr class="even">
<td align="left"><p><strong>Only Display Records with Application Name in StackTrace</strong></p></td>
<td align="left"><p>Filters out records that do not have the application name in the stack trace.</p>
<p>However, because the SUA tool captures only the first 32 stack frames, this command can also filter out real issues with the application where the call stack is deeper than 32 frames.</p></td>
</tr>
<tr class="odd">
<td align="left"><p><strong>Show More Details in StackTrace</strong></p></td>
<td align="left"><p>Shows additional stack frames that are related to the SUA tool, but not related to the diagnosed application.</p></td>
</tr>
<tr class="even">
<td align="left"><p><strong>Warn Before Deleting AppVerifier Logs</strong></p></td>
<td align="left"><p>Displays a warning message before the SUA tool deletes all of the existing SUA-related log files on the computer.</p>
<p>This command is selected by default.</p></td>
</tr>
<tr class="odd">
<td align="left"><p><strong>Logging</strong></p></td>
<td align="left"><p>Provides the following logging-related options:</p>
<ul>
<li><p>Show or hide log errors.</p></li>
<li><p>Show or hide log warnings.</p></li>
<li><p>Show or hide log information.</p></li>
</ul>
<p>To maintain a manageable file size, we recommend that you do not select the option to show informational messages.</p></td>
</tr>
</tbody>
</table>
 
 
 

235
windows/plan/available-data-types-and-operators-in-compatibility-administrator.md Normal file
View File

@ -0,0 +1,235 @@
---
title: Available Data Types and Operators in Compatibility Administrator (Windows 10)
description: The Compatibility Administrator tool provides a way to query your custom-compatibility databases.
ms.assetid: 67d9c03e-ab9d-4fda-8a55-8c5b90266d3b
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Available Data Types and Operators in Compatibility Administrator
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
The Compatibility Administrator tool provides a way to query your custom-compatibility databases.
## Available Data Types
Customized-compatibility databases in Compatibility Administrator contain the following data types.
- **Integer**. A numerical value with no fractional part. All integers are unsigned because none of the attributes can have a negative value.
- **String**. A series of alphanumeric characters manipulated as a group.
- **Boolean**. A value of True or False.
## Available Attributes
The following table shows the attributes you can use for querying your customized-compatibility databases in Compatibility Administrator.
<table>
<colgroup>
<col width="33%" />
<col width="33%" />
<col width="33%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Attribute</th>
<th align="left">Description</th>
<th align="left">Data type</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>APP_NAME</p></td>
<td align="left"><p>Name of the application.</p></td>
<td align="left"><p>String</p></td>
</tr>
<tr class="even">
<td align="left"><p>DATABASE_GUID</p></td>
<td align="left"><p>Unique ID for your compatibility database.</p></td>
<td align="left"><p>String</p></td>
</tr>
<tr class="odd">
<td align="left"><p>DATABASE_INSTALLED</p></td>
<td align="left"><p>Specifies if you have installed the database.</p></td>
<td align="left"><p>Boolean</p></td>
</tr>
<tr class="even">
<td align="left"><p>DATABASE_NAME</p></td>
<td align="left"><p>Descriptive name of your database.</p></td>
<td align="left"><p>String</p></td>
</tr>
<tr class="odd">
<td align="left"><p>DATABASE_PATH</p></td>
<td align="left"><p>Location of the database on your computer.</p></td>
<td align="left"><p>String</p></td>
</tr>
<tr class="even">
<td align="left"><p>FIX_COUNT</p></td>
<td align="left"><p>Number of compatibility fixes applied to a specific application.</p></td>
<td align="left"><p>Integer</p></td>
</tr>
<tr class="odd">
<td align="left"><p>FIX_NAME</p></td>
<td align="left"><p>Name of your compatibility fix.</p></td>
<td align="left"><p>String</p></td>
</tr>
<tr class="even">
<td align="left"><p>MATCH_COUNT</p></td>
<td align="left"><p>Number of matching files for a specific, fixed application.</p></td>
<td align="left"><p>Integer</p></td>
</tr>
<tr class="odd">
<td align="left"><p>MATCHFILE_NAME</p></td>
<td align="left"><p>Name of a matching file used to identify a specific, fixed application.</p></td>
<td align="left"><p>String</p></td>
</tr>
<tr class="even">
<td align="left"><p>MODE_COUNT</p></td>
<td align="left"><p>Number of compatibility modes applied to a specific, fixed application.</p></td>
<td align="left"><p>Integer</p></td>
</tr>
<tr class="odd">
<td align="left"><p>MODE_NAME</p></td>
<td align="left"><p>Name of your compatibility mode.</p></td>
<td align="left"><p>String</p></td>
</tr>
<tr class="even">
<td align="left"><p>PROGRAM_APPHELPTYPE</p></td>
<td align="left"><p>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.</p></td>
<td align="left"><p>Integer</p></td>
</tr>
<tr class="odd">
<td align="left"><p>PROGRAM_DISABLED</p></td>
<td align="left"><p>Specifies if you disabled the compatibility fix for an application. If True, Compatibility Administrator does not apply the fixes to the application.</p></td>
<td align="left"><p>Boolean</p></td>
</tr>
<tr class="even">
<td align="left"><p>PROGRAM_GUID</p></td>
<td align="left"><p>Unique ID for an application.</p></td>
<td align="left"><p>String</p></td>
</tr>
<tr class="odd">
<td align="left"><p>PROGRAM_NAME</p></td>
<td align="left"><p>Name of the application that you are fixing.</p></td>
<td align="left"><p>String</p></td>
</tr>
</tbody>
</table>
 
## Available Operators
The following table shows the operators that you can use for querying your customized-compatibility databases in the Compatibility Administrator.
<table>
<colgroup>
<col width="25%" />
<col width="25%" />
<col width="25%" />
<col width="25%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Symbol</th>
<th align="left">Description</th>
<th align="left">Data type</th>
<th align="left">Precedence</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>&gt;</p></td>
<td align="left"><p>Greater than</p></td>
<td align="left"><p>Integer or string</p></td>
<td align="left"><p>1</p></td>
</tr>
<tr class="even">
<td align="left"><p>&gt;=</p></td>
<td align="left"><p>Greater than or equal to</p></td>
<td align="left"><p>Integer or string</p></td>
<td align="left"><p>1</p></td>
</tr>
<tr class="odd">
<td align="left"><p>&lt;</p></td>
<td align="left"><p>Less than</p></td>
<td align="left"><p>Integer or string</p></td>
<td align="left"><p>1</p></td>
</tr>
<tr class="even">
<td align="left"><p>&lt;=</p></td>
<td align="left"><p>Less than or equal to</p></td>
<td align="left"><p>Integer or string</p></td>
<td align="left"><p>1</p></td>
</tr>
<tr class="odd">
<td align="left"><p>&lt;&gt;</p></td>
<td align="left"><p>Not equal to</p></td>
<td align="left"><p>Integer or string</p></td>
<td align="left"><p>1</p></td>
</tr>
<tr class="even">
<td align="left"><p>=</p></td>
<td align="left"><p>Equal to</p></td>
<td align="left"><p>Integer, string, or Boolean</p></td>
<td align="left"><p>1</p></td>
</tr>
<tr class="odd">
<td align="left"><p>HAS</p></td>
<td align="left"><p>A special SQL operator used to check if the left-hand operand contains a substring specified by the right-hand operand.</p></td>
<td align="left"><p><strong>Left-hand operand</strong>. MATCHFILE_NAME, MODE_NAME, FIX_NAME</p>
<div class="alert">
<strong>Note</strong>  
<p>Only the HAS operator can be applied to the MATCHFILE_NAME, MODE_NAME, and FIX_NAME attributes.</p>
</div>
<div>
 
</div>
<p><strong>Right-hand operand</strong>. String</p></td>
<td align="left"><p>1</p></td>
</tr>
<tr class="even">
<td align="left"><p>OR</p></td>
<td align="left"><p>Logical OR operator</p></td>
<td align="left"><p>Boolean</p></td>
<td align="left"><p>2</p></td>
</tr>
<tr class="odd">
<td align="left"><p>AND</p></td>
<td align="left"><p>Logical AND operator</p></td>
<td align="left"><p>Boolean</p></td>
<td align="left"><p>2</p></td>
</tr>
</tbody>
</table>
 
## Related topics
[Using the Compatibility Administrator Tool](using-the-compatibility-administrator-tool.md)
 
 

55
windows/plan/best-practice-recommendations-for-windows-to-go.md Normal file
View File

@ -0,0 +1,55 @@
---
title: Best practice recommendations for Windows To Go (Windows 10)
description: Best practice recommendations for Windows To Go
ms.assetid: 05e6e0ab-94ed-4c0c-a195-0abd006f0a86
keywords: ["best practices, USB, device, boot"]
ms.prod: w10
ms.mktglfcycl: deploy
ms.sitesec: library
author: TrudyHa
---
# Best practice recommendations for Windows To Go
**Applies to**
- Windows 10
The following are the best practice recommendations for using Windows To Go:
- Always shut down Windows and wait for shutdown to complete before removing the Windows To Go drive.
- Do not insert the Windows To Go drive into a running computer.
- Do not boot the Windows To Go drive from a USB hub. Always insert the Windows To Go drive directly into a port on the computer.
- If available, use a USB 3.0 port with Windows To Go.
- Do not install non-Microsoft core USB drivers on Windows To Go.
- Suspend BitLocker on Windows host computers before changing the BIOS settings to boot from USB and then resume BitLocker protection.
Additionally, we recommend that when you plan your deployment you should also plan a standard operating procedure for answering questions about which USB drives can be used for Windows To Go and how to enable booting from USB to assist your IT department or help desk in supporting users and work groups that want to use Windows To Go. It may be very helpful for your organization to work with your hardware vendors to create an IT standard for USB drives for use with Windows To Go, so that if groups within your organization want to purchase drives they can quickly determine which ones they should obtain.
## More information
[Windows To Go: feature overview](windows-to-go-feature-overview-scenario.md)
[Prepare your organization for Windows To Go](prepare-your-organization-for-windows-to-go.md)
[Deployment considerations for Windows To Go](deployment-considerations-for-windows-to-go.md)
[Security and data protection considerations for Windows To Go](security-and-data-protection-considerations-for-windows-to-go.md)
[Windows To Go: frequently asked questions](windows-to-go-frequently-asked-questions.md)
 
 

89
windows/plan/categorizing-your-compatibility-data.md Normal file
View File

@ -0,0 +1,89 @@
---
title: Categorizing Your Compatibility Data (Windows 10)
ms.assetid: 6420f012-316f-4ef0-bfbb-14baaa664e6e
description:
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Categorizing Your Compatibility Data
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
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:
- **Software Vendor**. In this category, you can, for example, create a subcategory for each vendor. You can then use this category to generate reports by software vendor, which can be helpful when having discussions with a specific vendor or evaluating the vendor’s performance relative to your compatibility requirements.
- **Test Complexity**. You can use this category to help with planning and assigning test resources. You can, for example, create subcategories like Critical and Nice-to-Have.
Categories are extensible, multiple-selection string values, so you can use them for almost anything. For example, you can create a category for signoff from multiple owners so that software can be authorized only when all categories have been selected, indicating that each group has signed off.
As another example, you can create a category for unit of deployment. You can use subcategories such as Division and Region. You can use this category to track the software needs of a specific deployment unit. This way, you can see when the software required by the unit has been tested, approved, and is ready for deployment to the unit.
**Note**  
The following examples use the **&lt;Operating\_System&gt; - Application Report** screen. You can alternatively use the **&lt;Application\_Name&gt;** dialog box. You can also complete these procedures in the reports for computers, devices, and websites.
 
## Creating, Renaming, or Deleting Categories and Subcategories
You can manage your categories and subcategories from both the report screen and report-details screen.
**To create, rename, or delete a category or subcategory**
1. On the **&lt;Operating\_System&gt; - Application Report** screen, click any application name.
2. On the **Actions** menu, click **Assign Categories**.
3. Click **Category List**.
4. In the **Categories** or **Subcategories** area, do any or all of the following:
- Add a category or subcategory, by clicking **Add**. Type the name of your new category or subcategory, and then click outside the active text area.
You must create at least one subcategory before a category will appear in the **Assign Categories** dialog box.
- Rename a category or subcategory, by selecting the item and then clicking **Rename**. Type the new name, and then click outside the active text area.
- Delete a category or subcategory, by selecting the item and then clicking **Remove**.
5. After you have finished adding, renaming, and deleting categories and subcategories, click **OK** to close the **Category List** dialog box.
## Assigning Data to a Category and Subcategory
You can assign categories and subcategories from both the report screen and report-details screen.
**To assign and unassign categories and subcategories**
1. On the **&lt;Operating\_System&gt; - Application Report** screen, click the application name.
2. On the **Actions** menu, click **Assign Categories**.
3. To assign a category, select the check box next to the applicable category or subcategory.
To unassign a category, clear the check box.
4. Click **OK**.
You can use the query builder to filter based on this information.
 
 

54
windows/plan/change-history-for-plan-for-windows-10-deployment.md Normal file
View File

@ -0,0 +1,54 @@
---
title: Change history for Plan for Windows 10 deployment (Windows 10)
description: This topic lists new and updated topics in the Plan for Windows 10 deployment documentation for Windows 10 and Windows 10 Mobile.
ms.assetid: 70D9F4F8-F2A4-4FB4-9459-5B2BE7BCAC66
ms.prod: W10
ms.mktglfcycl: deploy
ms.sitesec: library
author: TrudyHa
---
# Change history for Plan for Windows 10 deployment
This topic lists new and updated topics in the [Plan for Windows 10 deployment](planning-for-windows-10-deployment.md) documentation for [Windows 10 and Windows 10 Mobile](../index.md).
## December 2015
| New or changed topic | Description |
|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
| [Application Compatibility Toolkit (ACT) Technical Reference](application-compatibility-toolkit--act--technical-reference.md) (multiple topics) | New |
 
## November 2015
| New or changed topic | Description |
|--------------------------------------------------------------------------------------------------|-------------|
| [Chromebook migration guide](chromebook-migration-guide.md) | New |
| [Windows Update for Business](windows-update-for-business.md) (multiple topics) | New |
| [Windows To Go: feature overview](windows-to-go-feature-overview-scenario.md) (multiple topics) | Updated |
 
## Related topics
[Change history for What's new in Windows 10](../whats-new/change-history-for-what-s-new-in-windows-10.md)
[Change history for Deploy Windows 10](../deploy/change-history-for-deploy-windows-10.md)
[Change history for Keep Windows 10 secure](../keep-secure/change-history-for-keep-windows-10-secure.md)
[Change history for Manage and update Windows 10](../manage/change-history-for-manage-and-update-windows-10.md)
 
 

983
windows/plan/chromebook-migration-guide.md Normal file
View File

@ -0,0 +1,983 @@
---
title: Chromebook migration guide (Windows 10)
description: In this guide you will learn how to migrate a Google Chromebook-based learning environment to a Windows 10-based learning environment.
ms.assetid: 7A1FA48A-C44A-4F59-B895-86D4D77F8BEA
keywords: ["migrate", "automate", "device"]
ms.prod: W10
ms.mktglfcycl: plan
ms.sitesec: library
author: TrudyHa
---
# Chromebook migration guide
**Applies to**
- Windows 10
**In this article**
- [Plan Chromebook migration](#plan_migration)
- [Plan for app migration or replacement](#plan_app_migrate_replace)
- [Plan for migration of user and device settings](#plan_migrate_user_device_settings)
- [Plan for email migration](#plan_email_migrate)
- [Plan for cloud storage migration](#plan_cloud_storage_migration)
- [Plan for cloud services migration](#plan_cloud_services)
- [Plan for Windows device deployment](#plan_windevice_deploy)
- [Perform Chromebook migration](#perform_chromebook_migration)
- [Perform network infrastructure remediation](#network_infra_remediation)
- [Perform AD DS and Azure AD services deployment or remediation](#perform_ad_ds_and_azure_ad_services_deployment_or_remediation)
- [Prepare device, user, and app management systems](#prepare_device__user__and_app_management_systems)
- [Perform app migration or replacement](#perform_app_migration_or_replacement_)
- [Perform migration of user and device settings](#migrate_user_device_settings)
- [Perform email migration](#perform_email_migration)
- [Perform cloud storage migration](#perform_cloud_storage_migration)
- [Perform cloud services migration](#perform_cloud_services_migration)
- [Perform Windows device deployment](#perform_windows_device_deployment)
- [Related topics](#related_topics)
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.
## Plan Chromebook migration
Before you begin to migrate Chromebook devices, plan your migration. As with most projects, there can be an urge to immediately start doing before planning. When you plan your Chromebook migration before you perform the migration, you can save countless hours of frustration and mistakes during the migration process.
In the planning portion of this guide, you will identify all the decisions that you need to make and how to make each decision. At the end of the planning section, you will have a list of information you need to collect and what you need to do with the information. You will be ready to perform your Chromebook migration.
## Plan for app migration or replacement
App migration or replacement is an essential part of your Chromebook migration. In this section you will plan how you will migrate or replace Chromebook (Chrome OS) apps that are currently in use with the same or equivalent Windows apps. At the end of this section, you will have a list of the active Chrome OS apps and the Windows app counterparts.
**Identify the apps currently in use on Chromebook devices**
Before you can do any analysis or make decisions about which apps to migrate or replace, you need to identify which apps are currently in use on the Chromebook devices. You will create a list of apps that are currently in use (also called an app portfolio).
**Note**  
The majority of Chromebook apps are web apps. For these apps you need to first perform Microsoft Edge compatibility testing and then publish the web app URL to the Windows users. For more information, see the [Perform app compatibility testing for web apps](#perform_testing_webapps) section.
 
You can divide the apps into the following categories:
- **Apps installed and managed by the institution.** These apps are typically managed in the Apps section in the Google Admin Console. You can record the list of these apps in your app portfolio.
- **Apps installed by faculty or students.** Faculty or students might have installed these apps as a part of a classroom curriculum. Obtain the list of these apps from faculty or students. Ensure you only record apps that are legitimately used as a part of classroom curriculum (and not for personal entertainment or use).
Record the following information about each app in your app portfolio:
- App name
- App type (such as offline app, online app, web app, and so on)
- App publisher or developer
- App version currently in use
- App priority (how necessary is the app to the day-to-day process of the institution or a classroom? Rank as high, medium, or low)
Throughout the entire app migration or replacement process, focus on the higher priority apps. Focus on lower priority apps only after you have determined what you will do with the higher priority apps.
###
**Select Google Apps replacements**
Table 1 lists the Windows device app replacements for the common Google Apps on Chromebook devices. If your users rely on any of these Google Apps, use the corresponding app on the Windows device. Use the information in Table 1 to select the Google App replacement on a Windows device.
Table 1. Google App replacements
| If you use this Google app on a Chromebook | Use this app on a Windows device |
|--------------------------------------------|--------------------------------------|
| Google Docs | Word 2016 or Word Online |
| Google Sheets | Excel 2016 or Excel Online |
| Google Slides | PowerPoint 2016 or PowerPoint Online |
| Google Apps Gmail | Outlook 2016 or Outlook Web App |
| Google Hangouts | Microsoft Skype for Business |
| Chrome | Microsoft Edge |
| Google Drive | Microsoft OneDrive for Business |
 
It may be that you will decide to replace Google Apps after you deploy Windows devices. For more information on making this decision, see the [Select cloud services migration strategy](#select_CS_migrationstrat) section of this guide.
**Find the same or similar apps in the Windows Store**
In many instances, software vendors will create a version of their app for multiple platforms. You can search the Windows Store to find the same or similar apps to any apps not identified in the [Select Google Apps replacements](#select_googleapps) section.
In other instances, the offline app does not have a version written for the Windows Store or is not a web app. In these cases, look for an app that provides similar functions. For example, you might have a graphing calculator offline Android app published on the Chrome OS, but the software publisher does not have a version for Windows devices. Search the Windows Store for a graphing calculator app that provides similar features and functionality. Use that Windows Store app as a replacement for the graphing calculator offline Android app published on the Chrome OS.
Record the Windows app that replaces the Chromebook app in your app portfolio.
###
**Perform app compatibility testing for web apps**
The majority of Chromebook apps are web apps. Because you cannot run native offline Chromebook apps on a Windows device, there is no reason to perform app compatibility testing for offline Chromebook apps. However, you may have a number of web apps that will run on both platforms.
Ensure that you test these web apps in Microsoft Edge. Record the level of compatibility for each web app in Microsoft Edge in your app portfolio.
## Plan for migration of user and device settings
Some institutions have configured the Chromebook devices to make the devices easier to use by using the Google Chrome Admin Console. You have also probably configured the Chromebook devices to help ensure the user data access and ensure that the devices themselves are secure by using the Google Chrome Admin Console.
However, in addition to your centralized configuration in the Google Admin Console, Chromebook users have probably customized their device. In some instances, users may have changed the web content that is displayed when the Chrome browser starts. Or they may have bookmarked websites for future reference. Or users may have installed apps for use in the classroom.
In this section, you will identify the user and device configuration settings for your Chromebook users and devices. Then you will prioritize these settings to focus on the configuration settings that are essential to your educational institution.
At the end of this section, you should have a list of Chromebook user and device settings that you want to migrate to Windows, as well as a level of priority for each setting. You may discover at the end of this section that you have few or no higher priority settings to be migrated. If this is the case, you can skip the [Perform migration of user and device settings](#migrate_user_device_settings) section of this guide.
**Identify Google Admin Console settings to migrate**
You use the Google Admin Console (as shown in Figure 1) to manage user and device settings. These settings are applied to all the Chromebook devices in your institution that are enrolled in the Google Admin Console. Review the user and device settings in the Google Admin Console and determine which settings are appropriate for your Windows devices.
![figure 1](images/chromebook-fig1-googleadmin.png)
Figure 1. Google Admin Console
Table 2 lists the settings in the Device Management node in the Google Admin Console. Review the settings and determine which settings you will migrate to Windows.
Table 2. Settings in the Device Management node in the Google Admin Console
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Section</th>
<th align="left">Settings</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left">Network</td>
<td align="left"><p>These settings configure the network connections for Chromebook devices and include the following settings categories:</p>
<ul>
<li><p><strong>Wi-Fi.</strong> Configures the Wi-Fi connections that are available. The Windows devices will need these configuration settings to connect to the same Wi-Fi networks.</p></li>
<li><p><strong>Ethernet.</strong> Configures authentication for secured, wired Ethernet connections (802.1x). The Windows devices will need these configuration settings to connect to the network.</p></li>
<li><p><strong>VPN.</strong> Specifies the VPN network connections used by devices when not directly connected to your intranet. The Windows devices will need the same VPN network connections for users to remotely connect to your intranet.</p></li>
<li><p><strong>Certificates.</strong> Contains the certificates used for network authentication. The Windows devices will need these certificates to connect to the network.</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left">Mobile</td>
<td align="left"><p>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:</p>
<ul>
<li><p><strong>Device management settings.</strong> Configures settings for mobile (companion) devices, such as device synchronization, password settings, auditing, enable remote wipe, and other settings. Record these settings so that you can ensure the same settings are applied when the devices are being managed by Microsoft Intune or another mobile device management (MDM) provider.</p></li>
<li><p><strong>Device activation.</strong> Contains a list of mobile (companion) devices that need to be approved for management by using the Google Admin Console. Approve or block any devices in this list so that the list of managed devices accurately reflects active managed devices.</p></li>
<li><p><strong>Managed devices.</strong> Performs management tasks on mobile (companion) devices that are managed by the Google Admin Console. Record the list of companion devices on this page so that you can ensure the same devices are managed by Intune or another MDM provider.</p></li>
<li><p><strong>Set Up Apple Push Certificate.</strong> Configures the certificate that is essentially the digital signature that lets the Google Admin Console manage iOS devices. You will need this certificate if you plan to manage iOS devices by using Intune or another MDM provider.</p></li>
<li><p><strong>Set Up Android for Work.</strong> Authorizes the Google Admin Console to be the MDM provider for Android devices by providing an Enterprise Mobility Management (EMM) token. You will need this token if you plan to manage Android devices by using another MDM provider.</p></li>
</ul></td>
</tr>
<tr class="odd">
<td align="left">Chrome management</td>
<td align="left"><p>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:</p>
<ul>
<li><p><strong>User settings.</strong> Configures user-based settings for the Chrome browser and Chromebook devices. Most of these Chromebook user-based settings can be mapped to a corresponding setting in Windows. Record the settings and then map them to settings in Group Policy or Intune.</p></li>
<li><p><strong>Public session settings.</strong> Configures Public Sessions for Chrome devices that are used as kiosks, loaner devices, shared computers, or for any other work or school-related purpose for which users don't need to sign in with their credentials. You can configure Windows devices similarly by using Assigned Access. Record the settings and apps that are available in Public Sessions so that you can provide similar configuration in Assigned Access.</p></li>
<li><p><strong>Device settings.</strong> Configures device-based settings for the Chrome browser and Chromebook devices. You can map most of these Chromebook device-based settings to a corresponding setting in Windows. Record the settings and then map them to settings in Group Policy or Intune.</p></li>
<li><p><strong>Devices.</strong> Manages Chrome device management licenses. The number of licenses recorded here should correspond to the number of licenses you will need for your new management system, such as Intune. Record the number of licenses and use those to determine how many licenses you will need to manage your Windows devices.</p></li>
<li><p><strong>App Management.</strong> Provides configuration settings for Chrome apps. Record the settings for any apps that you have identified that will run on Windows devices.</p></li>
</ul></td>
</tr>
</tbody>
</table>
 
Table 3 lists the settings in the Security node in the Google Admin Console. Review the settings and determine which settings you will migrate to Windows.
Table 3. Settings in the Security node in the Google Admin Console
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Section</th>
<th align="left">Settings</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Basic settings</p></td>
<td align="left"><p>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.</p>
<p>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.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Password monitoring</p></td>
<td align="left"><p>This section is used to monitor the strength of user passwords. You don’t need to migrate any settings in this section.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>API reference</p></td>
<td align="left"><p>This section is used to enable access to various Google Apps Administrative APIs. You don’t need to migrate any settings in this section.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Set up single sign-on (SSO)</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Advanced settings</p></td>
<td align="left"><p>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.</p></td>
</tr>
</tbody>
</table>
 
**Identify locally-configured settings to migrate**
In addition to the settings configured in the Google Admin Console, users may have locally configured their devices based on their own personal preferences (as shown in Figure 2). Table 4 lists the Chromebook user and device settings that you can locally configure. Review the settings and determine which settings you will migrate to Windows. Some of the settings listed in Table 4 can only be seen when you click the **Show advanced settings** link (as shown in Figure 2).
![figure 2](images/fig2-locallyconfig.png)
Figure 2. Locally-configured settings on Chromebook
Table 4. Locally-configured settings
| Section | Settings |
|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Internet connections | These settings configure the Internet connection for the devices, such as Wi-Fi and VPN connections. Record the network connection currently in use and configure the Windows device to use the same network connection settings. |
| Appearances | These settings affect the appearance of the desktop. Record the wallpaper image file that is used. Migrate the image file to the Windows device and configure as the user’s wallpaper to maintain similar user experience. |
| Search | These settings configure which search engine is used to search for content. Record this setting so that you can use as the search engine on the Windows device. |
| Advanced sync settings | These settings configure which user settings are synchronized with the Google cloud, such as Apps, Extensions, History, Passwords, Settings, and so on. Record these settings and configure the Windows device with the same settings if you decide to continue to use Google Apps and other cloud services after you migrate to Windows devices. |
| Date and time | These settings configure the time zone and if 24-hour clock time should be used. Record these settings and configure the Windows device to use these settings. |
| Privacy | These settings configure Google Chrome web browser privacy settings (such as prediction service, phishing and malware protection, spelling errors, resource pre-fetch, and so on). Record these settings and configure Microsoft Edge, Internet Explorer, or the web browser of your choice with these settings. |
| Bluetooth | This setting configures whether or not Bluetooth is enabled on the device. Record this setting and configure the Windows device similarly. |
| Passwords and forms | These settings configure Google Chrome web browser to enable autofill of web forms and to save web passwords. Record these settings and configure Microsoft Edge, Internet Explorer, or the web browser of your choice with these settings. |
| Smart lock | These settings configure the Chromebook when the user’s Android phone is nearby and unlocked, which eliminates the need to type a password. You don’t need to migrate settings in this section. |
| Web content | These settings configure how the Chrome web browser displays content (such as font size and page zoom). Record these settings and configure Microsoft Edge, Internet Explorer, or the web browser of your choice with these settings. |
| Languages | These settings configure the language in use for the Chromebook. Record these settings and configure the Windows device to support the same language. |
| Downloads | These settings configure the default folder for file download, if the user should be prompted where to save files, and if the Google Drive account should be disconnected. Record these settings and configure the Windows device with similar settings. |
| HTTPS/SSL | These settings configure client-side certificates that are used to authenticate the device. Depending on the services or apps that use these certificates, you may need to export and then migrate these certificates to the Windows device. Contact the service or app provider to determine if you can use the existing certificate or if a new certificate needs to be issued. Record these settings and migrate the certificate to the Windows device or enroll for a new certificate as required by the service or app. |
| Google Cloud Print | These settings configure the printers that are available to the user. Record the list of printers available to the user and configure the Windows device to have the same printers available. Ensure that the user-friendly printer names in Windows are the same as for the Chromebook device. For example, if the Chromebook device has a printer named “Laser Printer in Registrar’s Office”, use that same name in Windows. |
| On startup | These settings configure which web pages are opened when the Chrome web browser starts. Record these settings and configure Microsoft Edge, Internet Explorer, or the web browser of your choice with these settings. |
| Accessibility | These settings configure the Chromebook ease of use (such as display of large mouse cursor, use of high contrast mode, enablement of the screen magnifier, and so on). Record these settings and configure the Windows device with similar settings. |
| Powerwash | This action removes all user accounts and resets the Chromebook device back to factory settings. You don’t have to migrate any settings in this section. |
| Reset settings | This action retains all user accounts, but restores all settings back to their default values. You don’t have to migrate any settings in this section. |
 
Determine how many users have similar settings and then consider managing those settings centrally. For example, a large number of users may have many of the same Chrome web browser settings. You can centrally manage these settings in Windows after migration.
Also, as a part of this planning process, consider settings that may not be currently managed centrally, but should be managed centrally. Record the settings that are currently being locally managed, but you want to manage centrally after the migration.
**Prioritize settings to migrate**
After you have collected all the Chromebook user, app, and device settings that you want to migrate, you need to prioritize each setting. Evaluate each setting and assign a priority to the setting based on the levels of high, medium, and low.
Assign the setting-migration priority based on how critical the setting is to the faculty performing their day-to-day tasks and how the setting affects the curriculum in the classrooms. Focus on the migration of higher priority settings and put less effort into the migration of lower priority settings. There may be some settings that are not necessary at all and can be dropped from your list of settings entirely. Record the setting priority in the list of settings you plan to migrate.
## Plan for email migration
Many of your users may be using Google Apps Gmail to manage their email, calendars, and contacts. You need to create the list of users you will migrate and the best time to perform the migration.
Office 365 supports automated migration from Google Apps Gmail to Office 365. For more information, see [Migrate Google Apps mailboxes to Office 365](http://go.microsoft.com/fwlink/p/?LinkId=690252).
**Identify the list of user mailboxes to migrate**
In regards to creating the list of users you will migrate, it might seem that the answer “all the users” might be the best one. However, depending on the time you select for migration, only a subset of the users may need to be migrated. For example, you may not persist student email accounts between semesters or between academic years. In this case you would only need to migrate faculty and staff.
Also, when you perform a migration it is a great time to verify that all user mailboxes are active. In many environments there are a significant number of mailboxes that were provisioned for users that are no longer a part of the institution (such as interns or student assistants). You can eliminate these users from your list of user mailboxes to migrate.
Create your list of user mailboxes to migrate in Excel 2016 based on the format described in step 7 in [Create a list of Gmail mailboxes to migrate](http://go.microsoft.com/fwlink/p/?LinkId=690253). If you follow this format, you can use the Microsoft Excel spreadsheet to perform the actual migration later in the process.
**Identify companion devices that access Google Apps Gmail**
In addition to Chromebook devices, users may have companion devices (smartphones, tablets, desktops, laptops, and so on) that also access the Google Apps Gmail mailbox. You will need to identify those companion devices and identify the proper configuration for those devices to access Office 365 mailboxes.
After you have identified each companion device, verify the settings for the device that are used to access Office 365. You only need to test one type of each companion device. For example, if users use Android phones to access Google Apps Gmail mailboxes, configure the device to access Office 365 and then record those settings. You can publish those settings on a website or to your helpdesk staff so that users will know how to access their Office 365 mailbox.
In most instances, users will only need to provide in their Office 365 email account and password. However, you should verify this on each type of companion device. For more information about how to configure a companion device to work with Office 365, see [Compare how different mobile devices work with Office 365](http://go.microsoft.com/fwlink/p/?LinkId=690254).
**Identify the optimal timing for the migration**
Typically, the best time to perform the migration is between academic years or during semester breaks. Select the time of least activity for your institution. And during that time, the optimal time to perform the migration might be during an evening or over a weekend.
Ensure that you communicate the time the migration will occur to your users well in advance. Also, ensure that users know how to access their Office 365 email after the migration is complete. Finally, ensure that your users know how to perform the common tasks they performed in Google Apps Gmail in Office 365 and/or Outlook 2016.
## Plan for cloud storage migration
Chromebook devices have limited local storage. So, most of your users will store data in cloud storage, such as Google Drive. You will need to plan how to migrate your cloud storage as a part of the Chromebook migration process.
In this section, you will create a list of the existing cloud services, select the Microsoft cloud services that best meet your needs, and then optimize your cloud storage services migration plan.
**Identify cloud storage services currently in use**
Typically, most Chromebook users use Google Drive for cloud storage services because your educational institution purchased other Google cloud services and Google Drive is a part of those services. However, some users may use cloud storage services from other vendors. For each member of your faculty and staff and for each student, create a list of cloud storage services that includes the following:
- Name of the cloud storage service
- Cloud storage service vendor
- Associated licensing costs or fees
- Approximate storage currently in use per user
Use this information as the requirements for your cloud storage services after you migrate to Windows devices. If at the end of this discovery you determine there is no essential data being stored in cloud storage services that requires migration, then you can skip to the [Plan for cloud services migration](#plan_cloud_services) section.
**Optimize cloud storage services migration plan**
Now that you know the current cloud storage services configuration, you need to optimize your cloud storage services migration plan for Microsoft OneDrive for Business. Optimization helps ensure that your use only the cloud storage services resources that are necessary for your requirements.
Consider the following to help optimize your cloud storage services migration plan:
- **Eliminate inactive user storage.** Before you perform the cloud storage services migration, identify cloud storage that is currently allocated to inactive users. Remove this storage from your list of cloud storage to migrate.
- **Eliminate or archive inactive files.** Review cloud storage to identify files that are inactive (have not been accessed for some period of time). Eliminate or archive these files so that they do not consume cloud storage.
- **Consolidate cloud storage services.** If multiple cloud storage services are in use, reduce the number of cloud storage services and standardize on one cloud storage service. This will help reduce management complexity, support time, and typically will reduce cloud storage costs.
Record your optimization changes in your cloud storage services migration plan.
## Plan for cloud services migration
Many of your users may use cloud services on their Chromebook device, such as Google Apps, Google Drive, or Google Apps Gmail. You have planned for these individual cloud services in the [Plan for app migration or replacement](#plan_app_migrate_replace), [Plan for Google Apps Gmail to Office 365 migration](#plan_email_migrate), and [Plan for cloud storage migration](#plan_cloud_storage_migration) sections.
In this section, you will create a combined list of these cloud services and then select the appropriate strategy to migrate these cloud services.
###
**Identify cloud services currently in use**
You have already identified the individual cloud services that are currently in use in your educational institution in the [Plan for app migration or replacement](#plan_app_migrate_replace), [Plan for Google Apps Gmail to Office 365 migration](#plan_email_migrate), and [Plan for cloud storage migration](#plan_cloud_storage_migration) sections. Create a unified list of these cloud services and record the following about each service:
- Cloud service name
- Cloud service provider
- Number of users that use the cloud service
**Select cloud services to migrate**
One of the first questions you should ask after you identify the cloud services currently in use is, “Why do we need to migrate from these cloud services?” The answer to this question largely comes down to finances and features.
Here is a list of reasons that describe why you might want to migrate from an existing cloud service to Microsoft cloud services:
- **Better integration with Office 365.** If your long-term strategy is to migrate to Office 365 apps (such as Word 2016 or Excel 2016) then a migration to Microsoft cloud services will provide better integration with these apps. The use of existing cloud services may not be as intuitive for users. For example, Office 365 apps will integrate better with OneDrive for Business compared to Google Drive.
- **Online apps offer better document compatibility.** Microsoft Office online apps (such as Word Online and Excel Online) provide the highest level of compatibility with Microsoft Office documents. The Office online apps allow you to open and edit documents directly from SharePoint or OneDrive for Business. Users can access the Office online app from any device with Internet connectivity.
- **Reduce licensing costs.** If you pay for Office 365 licenses, then Office 365 apps and cloud storage are included in those licenses. Although you could keep existing cloud services, you probably would pay more to keep those services.
- **Improve storage capacity and cross-platform features.** Microsoft cloud services provide competitive storage capacity and provide more Windows-centric features than other cloud services providers. While the Microsoft cloud services user experience is highly optimized for Windows devices, Microsoft cloud services are also highly optimized for companion devices (such as iOS or Android devices).
Review the list of existing cloud services that you created in the [Identify cloud services currently in use](#identify_cloud_services_inuse) section and identify the cloud services that you want to migrate to Microsoft cloud services. If you determine at the end of this task that there are no cloud services to be migrated, then skip to the [Plan for Windows device deployment](#plan_windevice_deploy) section. Also, skip the [Perform cloud services migration](#perform_cloud_services_migration) section later in this guide.
**Prioritize cloud services**
After you have created your aggregated list of cloud services currently in use by Chromebook users, prioritize each cloud service. Evaluate each cloud service and assign a priority based on the levels of high, medium, and low.
Assign the priority based on how critical the cloud service is to the faculty and staff performing their day-to-day tasks and how the cloud service affects the curriculum in the classrooms. Also, make cloud services that are causing pain for the users a higher priority. For example, if users experience outages with a specific cloud service, then make migration of that cloud service a higher priority.
Focus on the migration of higher priority cloud services first and put less effort into the migration of lower priority cloud services. There may be some cloud services that are unnecessary and you can remove them from your list of cloud services to migrate entirely. Record the cloud service migration priority in the list of cloud services you plan to migrate.
###
**Select cloud services migration strategy**
When you deploy the Windows devices, should you migrate the faculty, staff, and students to the new cloud services? Perhaps. But, in most instances you will want to select a migration strategy that introduces a number of small changes over a period of time.
Consider the following when you create your cloud services migration strategy:
- **Introduce small changes.** The move from Chrome OS to Windows will be simple for most users as most will have exposure to Windows from home, friends, or family. However, users may not be as familiar with the apps or cloud services. Consider the move to Windows first, and then make other changes as time progresses.
- **Start off by using existing apps and cloud services.** Immediately after the migration to Windows devices, you may want to consider running the existing apps and cloud services (such Google Apps, Google Apps Gmail, and Google Drive). This gives users a familiar method to perform their day-to-day tasks.
- **Resolve pain points.** If some existing apps or cloud services cause problems, you may want to migrate them sooner rather than later. In most instances, users will be happy to go through the learning curve of a new app or cloud service if it is more reliable or intuitive for them to use.
- **Migrate classrooms or users with common curriculum.** Migrate to Windows devices for an entire classroom or for multiple classrooms that share common curriculum. You must ensure that the necessary apps and cloud services are available for the curriculum prior to the migration of one or more classrooms.
- **Migrate when the fewest number of active users are affected.** Migrate your cloud services at the end of an academic year or end of a semester. This will ensure you have minimal impact on faculty, staff, and students. Also, a migration during this time will minimize the learning curve for users as they are probably dealing with new curriculum for the next semester. Also, you may not need to migrate student apps and data because many educational institutions do not preserve data between semesters or academic years.
- **Overlap existing and new cloud services.** For faculty and staff, consider overlapping the existing and new cloud services (having both services available) for one business cycle (end of semester or academic year) after migration. This allows you to easily recover any data that might not have migrated successfully from the existing cloud services. At a minimum, overlap the user of existing and new cloud services until the user can verify the migration. Of course, the tradeoff for using this strategy is the cost of the existing cloud services. However, depending on when license renewal occurs, the cost may be minimal.
## Plan for Windows device deployment
You need to plan for Windows device deployment to help ensure that the devices are successfully installed and configured to replace the Chromebook devices. Even if the vendor that provides the devices pre-loads Windows 10 on them, you still will need to perform other tasks.
In this section you will select a Windows device deployment strategy; plan for Active Directory Domain Services (AD DS) and Azure AD services; plan for device, user, and app management; and plan for any necessary network infrastructure remediation.
###
**Select a Windows device deployment strategy**
What decisions need to be made about Windows device deployment? You just put the device on a desk, hook up power, connect to Wi-Fi, and then let the users operate the device, right? That is essentially correct, but depending on the extent of your deployment and other factors, you need to consider different deployment strategies.
For each classroom that has Chromebook devices, select a combination of the following device deployment strategies:
- **Deploy one classroom at a time.** In most cases you will want to perform your deployment in batches of devices and a classroom is an excellent way to batch devices. You can treat each classroom as a unit and check each classroom off your list after you have deployed the devices.
- **Deploy based on curriculum.** Deploy the Windows devices after you have confirmed that the curriculum is ready for the Windows devices. If you deploy Windows devices without the curriculum installed and tested, you could significantly reduce the ability for students and teachers to perform effectively in the classroom. Also, deployment based on curriculum has the advantage of letting you move from classroom to classroom quickly if multiple classrooms use the same curriculum.
- **Deploy side-by-side.** In some instances you may need to have both the Chromebook and Windows devices in one or more classrooms. You can use this strategy if some of the curriculum only works on Chromebook and other parts of the curriculum works on Windows devices. This is a good method to help prevent delays in Windows device deployment, while ensuring that students and teachers can make optimal use of technology in their curriculum.
- **Deploy after apps and cloud services migration.** If you deploy a Windows device without the necessary apps and cloud services to support the curriculum, this provides only a portion of your complete solution. Ensure that the apps and cloud services are tested, provisioned, and ready for use prior to the deployment of Windows devices.
- **Deploy after the migration of user and device settings.** Ensure that you have identified the user and device settings that you plan to migrate and that those settings are ready to be applied to the new Windows devices. For example, you would want to create Group Policy Objects (GPOs) to apply the user and device settings to Windows devices.
If you ensure that Windows devices closely mirror the Chromebook device configuration, you will ease user learning curve and create a sense of familiarity. Also, when you have the settings ready to be applied to the devices, it helps ensure you will deploy your new Windows devices in a secure configuration.
Record the combination of Windows device deployment strategies that you selected.
###
**Plan for AD DS and Azure AD services**
The next decision you will need to make concerns AD DS and Azure AD services. You can run AD DS on-premises, in the cloud by using Azure AD, or a combination of both (hybrid). The decision about which of these options is best is closely tied to how you will manage your users, apps, and devices and if you will use Office 365 and other Azure-based cloud services.
In the hybrid configuration, your on-premises AD DS user and group objects are synchronized with Azure AD (including passwords). The synchronization happens both directions so that changes are made in both your on-premises AD DS and Azure AD.
Table 5 is a decision matrix that helps you decide if you can use only on-premises AD DS, only Azure AD, or a combination of both (hybrid). If the requirements you select from the table require on-premises AD DS and Azure AD, then you should select hybrid. For example, if you plan to use Office 365 and use Group Policy for management, then you would select hybrid. However, if you plan to use Office 365 and use Intune for management, then you would select only Azure AD.
Table 5. Select on-premises AD DS, Azure AD, or hybrid
<table>
<colgroup>
<col width="25%" />
<col width="25%" />
<col width="25%" />
<col width="25%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">If you plan to...</th>
<th align="left">On-premises AD DS</th>
<th align="left">Azure AD</th>
<th align="left">Hybrid</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left">Use Office 365</td>
<td align="left"></td>
<td align="left">X</td>
<td align="left">X</td>
</tr>
<tr class="even">
<td align="left">Use Intune for management</td>
<td align="left"></td>
<td align="left">X</td>
<td align="left">X</td>
</tr>
<tr class="odd">
<td align="left">Use System Center 2012 R2 Configuration Manager for management</td>
<td align="left">X</td>
<td align="left"></td>
<td align="left">X</td>
</tr>
<tr class="even">
<td align="left">Use Group Policy for management</td>
<td align="left">X</td>
<td align="left"></td>
<td align="left">X</td>
</tr>
<tr class="odd">
<td align="left">Have devices that are domain-joined</td>
<td align="left">X</td>
<td align="left"></td>
<td align="left">X</td>
</tr>
<tr class="even">
<td align="left">Allow faculty and students to Bring Your Own Device (BYOD) which are not domain-joined</td>
<td align="left"></td>
<td align="left">X</td>
<td align="left">X</td>
</tr>
</tbody>
</table>
 
###
**Plan device, user, and app management**
You may ask the question, “Why plan for device, user, and app management before you deploy the device?” The answer is that you will only deploy the device once, but you will manage the device throughout the remainder of the device's lifecycle.
Also, planning management before deployment is essential to being ready to support the devices as you deploy them. You want to have your management processes and technology in place when the first teachers, facility, or students start using their new Windows device.
Table 6 is a decision matrix that lists the device, user, and app management products and technologies and the features supported by each product or technology. The primary device, user, and app management products and technologies include Group Policy, System Center Configuration Manager, Intune, and the Microsoft Deployment Toolkit (MDT). Use this decision matrix to help you select the right combination of products and technologies for your plan.
Table 6. Device, user, and app management products and technologies
<table style="width:100%;">
<colgroup>
<col width="14%" />
<col width="14%" />
<col width="14%" />
<col width="14%" />
<col width="14%" />
<col width="14%" />
<col width="14%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Desired feature</th>
<th align="left">Windows provisioning packages</th>
<th align="left">Group Policy</th>
<th align="left">Configuration Manager</th>
<th align="left">Intune</th>
<th align="left">MDT</th>
<th align="left">Windows Software Update Services</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left">Deploy operating system images</td>
<td align="left">X</td>
<td align="left"></td>
<td align="left">X</td>
<td align="left"></td>
<td align="left">X</td>
<td align="left"></td>
</tr>
<tr class="even">
<td align="left">Deploy apps during operating system deployment</td>
<td align="left">X</td>
<td align="left"></td>
<td align="left">X</td>
<td align="left"></td>
<td align="left">X</td>
<td align="left"></td>
</tr>
<tr class="odd">
<td align="left">Deploy apps after operating system deployment</td>
<td align="left">X</td>
<td align="left">X</td>
<td align="left">X</td>
<td align="left"></td>
<td align="left"></td>
<td align="left"></td>
</tr>
<tr class="even">
<td align="left">Deploy software updates during operating system deployment</td>
<td align="left"></td>
<td align="left"></td>
<td align="left">X</td>
<td align="left"></td>
<td align="left">X</td>
<td align="left"></td>
</tr>
<tr class="odd">
<td align="left">Deploy software updates after operating system deployment</td>
<td align="left">X</td>
<td align="left">X</td>
<td align="left">X</td>
<td align="left">X</td>
<td align="left"></td>
<td align="left">X</td>
</tr>
<tr class="even">
<td align="left">Support devices that are domain-joined</td>
<td align="left">X</td>
<td align="left">X</td>
<td align="left">X</td>
<td align="left">X</td>
<td align="left">X</td>
<td align="left"></td>
</tr>
<tr class="odd">
<td align="left">Support devices that are not domain-joined</td>
<td align="left">X</td>
<td align="left"></td>
<td align="left"></td>
<td align="left">X</td>
<td align="left">X</td>
<td align="left"></td>
</tr>
<tr class="even">
<td align="left">Use on-premises resources</td>
<td align="left">X</td>
<td align="left">X</td>
<td align="left">X</td>
<td align="left"></td>
<td align="left">X</td>
<td align="left"></td>
</tr>
<tr class="odd">
<td align="left">Use cloud-based services</td>
<td align="left"></td>
<td align="left"></td>
<td align="left"></td>
<td align="left">X</td>
<td align="left"></td>
<td align="left"></td>
</tr>
</tbody>
</table>
 
You can use Configuration Manager and Intune in conjunction with each other to provide features from both products and technologies. In some instances you may need only one of these products or technologies. In other instances, you may need two or more to meet the device, user, and app management needs for your institution.
Record the device, user, and app management products and technologies that you selected.
###
**Plan network infrastructure remediation**
In addition to AD DS, Azure AD, and management components, there are other network infrastructure services that Windows devices need. In most instances, Windows devices have the same network infrastructure requirements as the existing Chromebook devices.
Examine each of the following network infrastructure technologies and services and determine if any remediation is necessary:
- **Domain Name System (DNS)** provides translation between a device name and its associated IP address. For Chromebook devices, public facing, Internet DNS services are the most important. For Windows devices that only access the Internet, they have the same requirements.
However, if you intend to communicate between Windows devices (peer-to-peer or client/server) then you will need local DNS services. Windows devices will register their name and IP address with the local DNS services so that Windows devices can locate each other.
- **Dynamic Host Configuration Protocol (DHCP)** provides automatic IP configuration for devices. Your existing Chromebook devices probably use DHCP for configuration. If you plan to immediately replace the Chromebook devices with Windows devices, then you only need to release all the DHCP reservations for the Chromebook devices prior to the deployment of Windows devices.
If you plan to run Chromebook and Windows devices side-by-side, then you need to ensure that your DHCP service has adequate IP addresses available for both sets of devices.
- **Wi-Fi.** Chromebook devices are designed to connect to Wi-Fi networks. Windows devices are the same. Your existing Wi-Fi network for the Chromebook devices should be adequate for the same number of Windows devices.
If you plan to significantly increase the number of Windows devices or you plan to run Chromebook and Windows devices side-by-side, then you need to ensure that Wi-Fi network can support the number of devices.
- **Internet bandwidth.** Chromebook devices consume more Internet bandwidth (up to 700 times more) than Windows devices. This means that if your existing Internet bandwidth is adequate for the Chromebook devices, then the bandwidth will be more than adequate for Windows devices.
However, if you plan to significantly increase the number of Windows devices or you plan to run Chromebook and Windows devices side-by-side, then you need to ensure that your Internet connection can support the number of devices.
For more information that compares Internet bandwidth consumption for Chromebook and Windows devices, see the following resources:
- [Chromebook vs. Windows Notebook Network Traffic Analysis](http://go.microsoft.com/fwlink/p/?LinkId=690255)
- [Hidden Cost of Chromebook Deployments](http://go.microsoft.com/fwlink/p/?LinkId=690256)
- [Microsoft Windows 8.1 Notebook vs. Chromebooks for Education](http://go.microsoft.com/fwlink/p/?LinkId=690257)
- **Power.** Although not specifically a network infrastructure, you need to ensure your classrooms have adequate power. Chromebook and Windows devices should consume similar amounts of power. This means that your existing power outlets should support the same number of Windows devices.
If you plan to significantly increase the number of Windows devices or you plan to run Chromebook and Windows devices side-by-side, you need to ensure that the power outlets, power strips, and other power management components can support the number of devices.
At the end of this process, you may determine that no network infrastructure remediation is necessary. If so, you can skip the [Perform network infrastructure remediation](#network_infra_remediation) section of this guide.
## Perform Chromebook migration
Thus far, planning has been the primary focus. Believe it or not most of the work is now done. The rest of the Chromebook migration is just the implementation of the plan you have created.
In this section you will perform the necessary steps for the Chromebook device migration. You will perform the migration based on the planning decision that you made in the [Plan Chromebook migration](#plan_migration) section earlier in this guide.
You must perform some of the steps in this section in a specific sequence. Each section has guidance about when to perform a step. You can perform other steps before, during, or after the migration. Again, each section will tell you if the sequence is important.
## Perform network infrastructure remediation
The first migration task is to perform any network infrastructure remediation. In the [Plan network infrastructure remediation](#plan_network_infra_remediation) section, you determined the network infrastructure remediation (if any) that you needed to perform.
It is important that you perform any network infrastructure remediation first because the remaining migration steps are dependent on the network infrastructure. Table 7 lists the Microsoft network infrastructure products and technologies and deployment resources for each.
Table 7. Network infrastructure products and technologies and deployment resources
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Product or technology</th>
<th align="left">Resources</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left">DHCP</td>
<td align="left"><ul>
<li><p>[Core Network Guide](http://go.microsoft.com/fwlink/p/?LinkId=733920)</p></li>
<li><p>[DHCP Deployment Guide](http://go.microsoft.com/fwlink/p/?LinkId=734021)</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left">DNS</td>
<td align="left"><ul>
<li><p>[Core Network Guide](http://go.microsoft.com/fwlink/p/?LinkId=733920)</p></li>
<li><p>[Deploying Domain Name System (DNS)](http://go.microsoft.com/fwlink/p/?LinkId=734022)</p></li>
</ul></td>
</tr>
</tbody>
</table>
 
If you use network infrastructure products and technologies from other vendors, refer to the vendor documentation on how to perform the necessary remediation. If you determined that no remediation is necessary, you can skip this section.
## Perform AD DS and Azure AD services deployment or remediation
It is important that you perform AD DS and Azure AD services deployment or remediation right after you finish network infrastructure remediation. Many of the remaining migration steps are dependent on you having your identity system (AD DS or Azure AD) in place and up to necessary expectations.
In the [Plan for Active Directory services](#plan_ADservices) section, you determined the AD DS and/or Azure AD deployment or remediation (if any) that needed to be performed. Table 8 list AD DS, Azure AD, and the deployment resources for both. Use the resources in this table to deploy or remediate on-premises AD DS, Azure AD, or both.
Table 8. AD DS, Azure AD and deployment resources
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Product or technology</th>
<th align="left">Resources</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left">AD DS</td>
<td align="left"><ul>
<li><p>[Core Network Guide](http://go.microsoft.com/fwlink/p/?LinkId=733920)</p></li>
<li><p>[Active Directory Domain Services Overview](http://go.microsoft.com/fwlink/p/?LinkId=733909)</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left">Azure AD</td>
<td align="left"><ul>
<li><p>[Azure Active Directory documentation](http://go.microsoft.com/fwlink/p/?LinkId=690258)</p></li>
<li><p>[Manage and support Azure Active Directory Premium](http://go.microsoft.com/fwlink/p/?LinkId=690259)</p></li>
<li><p>[Guidelines for Deploying Windows Server Active Directory on Azure Virtual Machines](http://go.microsoft.com/fwlink/p/?LinkId=690260)</p></li>
</ul></td>
</tr>
</tbody>
</table>
 
If you decided not to migrate to AD DS or Azure AD as a part of the migration, or if you determined that no remediation is necessary, you can skip this section. If you use identity products and technologies from another vendor, refer to the vendor documentation on how to perform the necessary steps.
## Prepare device, user, and app management systems
In the [Plan device, user, and app management](#plan_userdevapp_manage) section of this guide, you selected the products and technologies that you will use to manage devices, users, and apps on Windows devices. You need to prepare your management systems prior to Windows 10 device deployment. You will use these management systems to manage the user and device settings that you selected to migrate in the [Plan for migration of user and device settings](#plan_migrate_user_device_settings) section. You need to prepare these systems prior to the migration of user and device settings.
Table 9 lists the Microsoft management systems and the deployment resources for each. Use the resources in this table to prepare (deploy or remediate) these management systems.
Table 9. Management systems and deployment resources
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Management system</th>
<th align="left">Resources</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left">Windows provisioning packages</td>
<td align="left"><ul>
<li><p>[Build and apply a provisioning package](http://go.microsoft.com/fwlink/p/?LinkId=733918)</p></li>
<li><p>[Windows Imaging and Configuration Designer](http://go.microsoft.com/fwlink/p/?LinkId=733911)</p></li>
<li><p>[Step-By-Step: Building Windows 10 Provisioning Packages](http://go.microsoft.com/fwlink/p/?LinkId=690261)</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left">Group Policy</td>
<td align="left"><ul>
<li><p>[Core Network Companion Guide: Group Policy Deployment](http://go.microsoft.com/fwlink/p/?LinkId=733915)</p></li>
<li><p>[Deploying Group Policy](http://go.microsoft.com/fwlink/p/?LinkId=734024)</p></li>
</ul></td>
</tr>
<tr class="odd">
<td align="left">Configuration Manager</td>
<td align="left"><ul>
<li><p>[Site Administration for System Center 2012 Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=733914)</p></li>
<li><p>[Deploying Clients for System Center 2012 Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=733919)</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left">Intune</td>
<td align="left"><ul>
<li><p>[Set up and manage devices with Microsoft Intune](http://go.microsoft.com/fwlink/p/?LinkId=690262)</p></li>
<li><p>[Smoother Management Of Office 365 Deployments with Windows Intune](http://go.microsoft.com/fwlink/p/?LinkId=690263)</p></li>
<li><p>[System Center 2012 R2 Configuration Manager &amp; Windows Intune](http://go.microsoft.com/fwlink/p/?LinkId=690264)</p></li>
</ul></td>
</tr>
<tr class="odd">
<td align="left">MDT</td>
<td align="left"><ul>
<li><p>[MDT documentation in the Microsoft Deployment Toolkit (MDT) 2013](http://go.microsoft.com/fwlink/p/?LinkId=690324)</p></li>
<li><p>[Step-By-Step: Installing Windows 8.1 From A USB Key](http://go.microsoft.com/fwlink/p/?LinkId=690265)</p></li>
</ul></td>
</tr>
</tbody>
</table>
 
If you determined that no new management system or no remediation of existing systems is necessary, you can skip this section. If you use a management system from another vendor, refer to the vendor documentation on how to perform the necessary steps.
## Perform app migration or replacement
In the [Plan for app migration or replacement](#plan_app_migrate_replace) section, you identified the apps currently in use on Chromebook devices and selected the Windows apps that will replace the Chromebook apps. You also performed app compatibility testing for web apps to ensure that web apps on the Chromebook devices would run on Microsoft Edge and Internet Explorer.
In this step, you need to configure your management system to deploy the apps to the appropriate Windows users and devices. Table 10 lists the Microsoft management systems and the app deployment resources for each. Use the resources in this table to configure these management systems to deploy the apps that you selected in the [Plan for app migration or replacement](#plan_app_migrate_replace) section of this guide.
Table 10. Management systems and app deployment resources
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Management system</th>
<th align="left">Resources</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left">Group Policy</td>
<td align="left"><ul>
<li><p>[Editing an AppLocker Policy](http://go.microsoft.com/fwlink/p/?LinkId=734025)</p></li>
<li><p>[Group Policy Software Deployment Background](http://go.microsoft.com/fwlink/p/?LinkId=734026)</p></li>
<li><p>[Assigning and Publishing Software](http://go.microsoft.com/fwlink/p/?LinkId=734027)</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left">Configuration Manager</td>
<td align="left"><ul>
<li><p>[How to Deploy Applications in Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=733917)</p></li>
<li><p>[Application Management in Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=733907)</p></li>
</ul></td>
</tr>
<tr class="odd">
<td align="left">Intune</td>
<td align="left"><ul>
<li><p>[Deploy apps to mobile devices in Microsoft Intune](http://go.microsoft.com/fwlink/p/?LinkId=733913)</p></li>
<li><p>[Manage apps with Microsoft Intune](http://go.microsoft.com/fwlink/p/?LinkId=733910)</p></li>
</ul></td>
</tr>
</tbody>
</table>
 
If you determined that no deployment of apps is necessary, you can skip this section. If you use a management system from another vendor, refer to the vendor documentation on how to perform the necessary steps.
## Perform migration of user and device settings
In the [Plan for migration of user and device settings](#plan_migrate_user_device_settings) section, you determined the user and device settings that you want to migrate. You selected settings that are configured in the Google Admin Console and locally on the Chromebook device.
Perform the user and device setting migration by using the following steps:
1. From the list of institution-wide settings that you created in the [Plan for migration of user and device settings](#plan_migrate_user_device_settings) section, configure as many as possible in your management system (such as Group Policy, Configuration Manager, or Intune).
2. From the list of device-specific settings that you created in the [Plan for migration of user and device settings](#plan_migrate_user_device_settings) section, configure device-specific setting for higher priority settings.
3. From the list of user-specific settings that you created in the [Plan for migration of user and device settings](#plan_migrate_user_device_settings) section, configure user-specific setting for higher priority settings.
4. Verify that all higher-priority user and device settings have been configured in your management system.
If you do no want to migrate any user or device settings from the Chromebook devices to the Windows devices, you can skip this section.
## Perform email migration
In the [Plan for email migration](#plan_email_migrate) section, you identified the user mailboxes to migrate, identified the companion devices that access Google Apps Gmail, and identified the optimal timing for migration. You can perform this migration before or after you deploy the Windows devices.
Office 365 supports automated migration from Google Apps Gmail to Office 365. For more information on how to automate the migration from Google Apps Gmail to Office 365, see [Migrate Google Apps mailboxes to Office 365](http://go.microsoft.com/fwlink/p/?LinkId=690252).
Alternatively, if you want to migrate to Office 365 from:
- **On-premises Microsoft Exchange Server.** Use the following resources to migrate to Office 365 from an on-premises Microsoft Exchange Server:
- [Cutover Exchange Migration and Single Sign-On](http://go.microsoft.com/fwlink/p/?LinkId=690266)
- [Step-By-Step: Migration of Exchange 2003 Server to Office 365](http://go.microsoft.com/fwlink/p/?LinkId=690267)
- [Step-By-Step: Migrating from Exchange 2007 to Office 365](http://go.microsoft.com/fwlink/p/?LinkId=690268)
- **Another on-premises or cloud-based email service.** Follow the guidance from that vendor.
## Perform cloud storage migration
In the [Plan for cloud storage migration](#plan_cloud_storage_migration) section, you identified the cloud storage services currently in use, selected the Microsoft cloud storage services that you will use, and optimized your cloud storage services migration plan. You can perform the cloud storage migration before or after you deploy the Windows devices.
Manually migrate the cloud storage migration by using the following steps:
1. Install both Google Drive app and OneDrive for Business or OneDrive app on a device.
2. Sign in as the user in the Google Drive app.
3. Sign in as the user in the OneDrive for Business or OneDrive app.
4. Copy the data from the Google Drive storage to the OneDrive for Business or OneDrive storage.
5. Optionally uninstall the Google Drive app.
There are also a number of software vendors who provide software that helps automate the migration from Google Drive to OneDrive for Business, Office 365 SharePoint, or OneDrive. For more information about these automated migration tools, contact the vendors.
## Perform cloud services migration
In the [Plan for cloud services migration](#plan_cloud_services)section, you identified the cloud services currently in use, selected the cloud services that you want to migrate, prioritized the cloud services to migrate, and then selected the cloud services migration strategy. You can perform the cloud services migration before or after you deploy the Windows devices.
Migrate the cloud services that you currently use to the Microsoft cloud services that you selected. For example, you could migrate from a collaboration website to Office 365 SharePoint. Perform the cloud services migration based on the existing cloud services and the Microsoft cloud services that you selected.
There are also a number of software vendors who provide software that helps automate the migration from other cloud services to Microsoft cloud services. For more information about these automated migration tools, contact the vendors.
## Perform Windows device deployment
In the [Select a Windows device deployment strategy](#select_windows_device_deploy) section, you selected how you wanted to deploy Windows 10 devices. The other migration task that you designed in the [Plan for Windows device deployment](#plan_windevice_deploy) section have already been performed. Now it's time to deploy the actual devices.
For example, if you selected to deploy Windows devices by each classroom, start with the first classroom and then proceed through all of the classrooms until you’ve deployed all Windows devices.
In some instances, you may receive the devices with Windows 10 already deployed, and want to use provisioning packages. In other cases, you may have a custom Windows 10 image that you want to deploy to the devices by using Configuration Manager and/or MDT. For information on how to deploy Windows 10 images to the devices, see the following resources:
- [Windows Imaging and Configuration Designer](http://go.microsoft.com/fwlink/p/?LinkId=733911)
- [Build and apply a provisioning package](http://go.microsoft.com/fwlink/p/?LinkId=733918)
- [MDT documentation in the Microsoft Deployment Toolkit (MDT) 2013](http://go.microsoft.com/fwlink/p/?LinkId=690324)
- [Step-By-Step: Installing Windows 8.1 From A USB Key](http://go.microsoft.com/fwlink/p/?LinkId=690265)
- [Operating System Deployment in Configuration Manager](http://go.microsoft.com/fwlink/p/?LinkId=733916)
In addition to the Windows 10 image deployment, you may need to perform the following tasks as a part of device deployment:
- Enroll the device with your management system.
- Ensure that Windows Defender is enabled and configured to receive updates.
- Ensure that Windows Update is enabled and configured to receive updates.
- Deploy any apps that you want the user to immediately be able to access when they start the device (such as Word 2016 or Excel 2016).
After you complete these steps, your management system should take over the day-to-day maintenance tasks for the Windows 10 devices. Verify that the user and device settings migrated correctly as you deploy each batch of Windows 10 devices. Continue this process until you deploy all Windows 10 devices.
## Related topics
[Try it out: Windows 10 deployment (for education)](http://go.microsoft.com/fwlink/p/?LinkId=623254)
[Try it out: Windows 10 in the classroom](http://go.microsoft.com/fwlink/p/?LinkId=623255)
 
 

57
windows/plan/common-compatibility-issues.md Normal file
View File

@ -0,0 +1,57 @@
---
title: Common Compatibility Issues (Windows 10)
ms.assetid: f5ad621d-bda2-45b5-ae85-bc92970f602f
description:
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Common Compatibility Issues
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
Compatibility issues tend to occur with the following technologies:
- **User Account Control (UAC)**: Adds security to Windows by limiting administrator-level access to the computer, restricting most users to running as Standard Users. UAC limits the context in which a process executes to minimize the ability of the user to inadvertently expose the computer to viruses or other malware. UAC affects any application installer or update that requires Administrator permissions to run, performs Administrator checks or actions, or attempts to write to a non-virtualized registry location.
- **Windows Resource Protection (WRP)**: Enables applications to function properly even if an application attempts to write to protected system files or registry locations. WRP creates a temporary work area and redirects write actions for the application session. WRP affects any application installation that attempts to replace, modify, or delete protected operating system files or registry keys. Attempts typically fail and return an Access Denied error.
- **Internet Explorer Protected Mode**: Helps to defend against elevation-of-privilege attacks by restricting the ability to write to any local-computer-zone resources other than temporary Internet files. This mode affects any website or web application that attempts to modify user files or registry keys or that attempts to open a new window in another domain.
- **Deprecation**: Any application that uses .dll files, executable (.exe) files, COM objects, registry keys, APIs, or other files that have been deprecated from previous versions of Windows may lose functionality or fail to start.
- **Graphical Identification and Authentication (GINA) DLL**: Prior to the release of Windows Vista, independent software vendors (ISVs) were able to modify authentication by installing a GINA DLL. The GINA DLL performed the user identification and authentication.
The current authentication model does not require the GINA DLL and ignores all previous GINA DLLs. This change affects any application or hardware component that attempts to log on by using customized logon applications, including biometric devices (fingerprint readers), customized user interfaces, and virtual private network (VPN) solutions for remote users with customized logon user interfaces.
- **Session 0**: Prior to the release of Windows Vista, the first user who logged on to a computer ran in Session 0, which is the same session that is used for system services. The current model requires all users to run in Session 1 or later so that no user runs in the same session as the system services. Applications will fail to start if they depend on *interactive services*. An interactive service is any service that attempts to send a window message, attempts to locate a window or additional service, or attempts to run any user processes that open the same named object, unless it is a globally named object.
- **Windows Filtering Platform (WFP)**: WFP is an API that enables developers to create code that interacts with the filtering that occurs at several layers in the networking stack and throughout the operating system. If you are using a previous version of the WFP API in your environment, you might experience failures when running network-scanning, antivirus, or firewall applications.
- **Operating System Version Changes**: The operating system version number changes with each operating system release. The **GetVersion** function returns the version number when queried by an application. This change affects any application or application installer that specifically checks for the operating system version and might prevent the installation from occurring or the application from running.
- **Windows 64-bit**: 64-bit versions of Windows use the Windows on Windows 64 (WOW64) emulator. This emulator enables the 64-bit operating system to run 32-bit applications. The use of this emulator might cause an application or a component that uses 16-bit executables or installers, or 32-bit kernel drivers, to fail to start or to function incorrectly.
## Related topics
[Using Compatibility Monitor to Send Feedback](using-compatibility-monitor-to-send-feedback.md)
 
 

79
windows/plan/compatibility-administrator-users-guide.md Normal file
View File

@ -0,0 +1,79 @@
---
title: Compatibility Administrator User's Guide (Windows 10)
ms.assetid: 0ce05f66-9009-4739-a789-60f3ce380e76
description:
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Compatibility Administrator User's Guide
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
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:
- Compatibility fixes, compatibility modes, and AppHelp messages that you can use to resolve specific compatibility issues.
- Tools for creating customized compatibility fixes, compatibility modes, AppHelp messages, and compatibility databases.
- A query tool that you can use to search for installed compatibility fixes on your local computers.
The following flowchart shows the steps for using the Compatibility Administrator tool to create your compatibility fixes, compatibility modes, and AppHelp messages.
![act compatibility admin flowchart](images/dep-win8-l-act-compatadminflowchart.jpg)
**Important**  
Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version of the Compatibility Administrator tool. You must use the 32-bit version to create and work with custom databases for 32-bit applications, and the 64-bit version to create and work with custom databases for 64-bit applications.
 
## In this section
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Topic</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[Using the Compatibility Administrator Tool](using-the-compatibility-administrator-tool.md)</p></td>
<td align="left"><p>This section provides information about using the Compatibility Administrator tool.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Managing Application-Compatibility Fixes and Custom Fix Databases](managing-application-compatibility-fixes-and-custom-fix-databases.md)</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Using the Sdbinst.exe Command-Line Tool](using-the-sdbinstexe-command-line-tool.md)</p></td>
<td align="left"><p>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.</p></td>
</tr>
</tbody>
</table>
 
 
 

174
windows/plan/compatibility-fix-database-management-strategies-and-deployment.md Normal file
View File

@ -0,0 +1,174 @@
---
title: Compatibility Fix Database Management Strategies and Deployment (Windows 10)
ms.assetid: fdfbf02f-c4c4-4739-a400-782204fd3c6c
description:
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Compatibility Fix Database Management Strategies and Deployment
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
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:
- Deploying your compatibility fixes as part of an application-installation package.
- Deploying your compatibility fixes through a centralized compatibility-fix database.
Regardless of which approach you decide to use in your organization, Microsoft provides the following general recommendations for improving the management of your custom compatibility-fix databases:
- **Define standards for when you will apply compatibility fixes.**
You must define the standards and scenarios for using compatibility fixes, based on your specific business and technology needs.
- **Define standards for your custom compatibility-fix databases.**
You must define how to associate your compatibility fixes to particular applications. For example, you might want to ensure that your compatibility fixes always include a version check, so that a fix will not be applied to newer versions of your applications.
- **Define your resources responsible for addressing questions and enforcing your standards.**
You must determine who will be responsible for staying current with the technology and standards related to your compatibility fixes and custom compatibility-fix databases. As your databases are managed over time, you must ensure that someone in your organization stays current with the relevant technology.
## Strategies for Deploying Your Compatibility Fixes
We recommend that you use one of two strategies to deploy your compatibility fixes into your organization. They are:
- Deploying your compatibility fixes as part of an application-installation package.
- Deploying your compatibility fixes through a centralized compatibility-fix database.
You must determine which method best meets your organization's deployment needs.
### Deploying Fixes as Part of an Application-Installation Package
One strategy for deploying compatibility fixes is to create a custom compatibility-fix database that contains a single entry that is applied directly to the application-installation package. While this is the most straightforward method of deployment, it has been shown that this method can become overly complex, especially if you are fixing a large number of applications.
If the following considerations apply to your organization, you should avoid this strategy and instead consider using a centralized compatibility-fix database, as described in the next section.
- **How many applications require compatibility fixes?**
Custom compatibility-fix databases are actual databases. Therefore, if you have 1000 applications to be fixed, it will take longer to open and query 1000 single-row databases for a match, instead of a single database with 1000 rows.
- **Will you be able to track which applications are installed on which computer?**
You might determine that your initial set of compatibility fixes is not comprehensive, and that you must deploy an updated version of the compatibility-fix database to resolve the additional issues. If you deployed the initial set by using the application-installation package, you will be required to locate each client computer that is running the application and replace the compatibility fix.
### Deploying Fixes Through a Centralized Compatibility-Fix Database
The other recommended strategy for deploying compatibility fixes into your organization is to create and manage either a single custom compatibility-fix database, or else to create and manage several custom databases for large subsets of your organization. This strategy will help to enforce your company policy and to provide consistent updates for application fixes that you discover later.
This approach tends to work best for organizations that have a well-developed deployment infrastructure in place, with centralized ownership of the process. We recommend that you consider the following before using this approach:
- Does your organization have the tools required to deploy and update a compatibility-fix database for all of the effected computers?
If you intend to manage a centralized compatibility-fix database, you must verify that your organization has the required tools to deploy and update all of the affected computers in your organization.
- Do you have centralized resources that can manage and update the centralized compatibility-fix database?
You must ensure that you have identified the appropriate owners for the deployment process, for the applications, and for the database updates, in addition to determining the process by which compatibility issues can be deployed to specific computers.
### Merging Centralized Compatibility-Fix Databases
If you decide to use the centralized compatibility-fix database deployment strategy, you can merge any of your individual compatibility-fix databases. This enables you to create a single custom compatibility-fix database that can be used to search for and determine whether Windows® should apply a fix to a specific executable (.exe) file. We recommend merging your databases based on the following process.
**To merge your custom-compatibility databases**
1. Verify that your application-compatibility testers are performing their tests on computers with the latest version of your compatibility-fix database. For example, Custom DB1.
2. If the tester determines that an application requires an additional compatibility fix that is not a part of the original compatibility-fix database, he or she must create a new custom compatibility database with all of the required information for that single fix. For example, Custom DB2.
3. The tester applies the new Custom DB2 information to the application and then tests for both the functionality and integration, to ensure that the compatibility issues are addressed.
4. After the application passes all of the required functionality and integration tests, the tester can send Custom DB2 to the team that manages the central compatibility-fix database.
5. The team that manages the centralized database opens Custom DB1 and uses the Compatibility Administrator to include the new compatibility fixes that were included in Custom DB2.
**Note**  
Custom DB1 contains a unique GUID that makes updating the database easier. For example, if you install a new version of the custom compatibility-fix database that uses the same GUID as the previous version, the computer will automatically uninstall the old version.
 
6. The centralized management team then redeploys the new version of Custom DB1 to all of the end users in your organization.
### Deploying Your Custom Compatibility-Fix Databases
Deploying your custom compatibility-fix database into your organization requires you to perform the following actions:
1. Store your custom compatibility-fix database (.sdb file) in a location that is accessible to all of your organization’s computers.
2. Use the Sdbinst.exe command-line tool to install the custom compatibility-fix database locally.
In order to meet the two requirements above, we recommend that you use one of the following two methods:
- **Using a Windows Installer package and a custom script**
You can package your .sdb file and a custom deployment script into an .msi file, and then deploy the .msi file into your organization.
**Important**  
You must ensure that you mark your custom script so that it does not impersonate the calling user. For example, if you use Microsoft® Visual Basic® Scripting Edition (VBScript), the custom action type would be:
 
``` syntax
msidbCustomActionTypeVBScript + msidbCustomActionTypeInScript + msidbCustomActionTypeNoImpersonate = 0x0006 + 0x0400 + 0x0800 = 0x0C06 = 3078 decimal)
```
- **Using a network share and a custom script**
You can store your .sdb file on your network share and then call to a script that resides on your specified computers.
**Important**  
You must ensure that you call the script at a time when it will receive elevated rights. For example, you should call the script by using computer startup scripts instead of a user logon script. You must also ensure that the installation of the custom compatibility-fix database occurs with Administrator rights.
 
### Example Script for an Installation of the .sdb File based on an .msi File
The following examples show an installation of a custom compatibility-fix database based on an .msi file.
``` syntax
'InstallSDB.vbs
Function Install
Dim WshShell
Set WshShell = CreateObject("WScript.Shell")
WshShell.Run "sdbinst.exe -q " & CHR(34) & "%ProgramFiles%\MyOrganizationSDB\MyOrg.sdb" & CHR(34), 0, true
WshShell.Run "cmd.exe /c " & CHR(34) & "del " & CHR(34) & "%ProgramFiles%\MyOrganizationSDB\MyOrg.sdb" & CHR(34) & CHR(34), 0
WshShell.Run "reg.exe delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{guidFromMyOrgsSdb}.sdb /f", 0
End Function
Function UnInstall
Dim WshShell
Set WshShell = CreateObject("WScript.Shell")
WshShell.Run "sdbinst.exe -q -u -g {guidFromMyOrgsSdb}", 0
End Function
```
### Initial Deployment and Updates
Most of your testing of application-compatibility issues will happen prior to the deployment of a new Windows operating system into your environment. As such, a common approach is to include the custom compatibility-fix database, which includes all of your known issues, in your corporate image. Then, as you update your compatibility-fix database, you can provide the updates by using one of the two mechanisms described in the "Deploying Your Custom Compatibility Fix Databases" section earlier in this topic.
## Related topics
[Managing Application-Compatibility Fixes and Custom Fix Databases](managing-application-compatibility-fixes-and-custom-fix-databases.md)
 
 

1022
windows/plan/compatibility-fixes-for-windows-8-windows-7-and-windows-vista.md Normal file
View File

File diff suppressed because it is too large Load Diff

71
windows/plan/compatibility-monitor-users-guide.md Normal file
View File

@ -0,0 +1,71 @@
---
title: Compatibility Monitor User's Guide (Windows 10)
description: 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.
ms.assetid: 67d6eff0-1576-44bd-99b4-a3ffa5e205ac
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Compatibility Monitor User's Guide
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
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.
## In this section
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Topic</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[Using Compatibility Monitor to Send Feedback](using-compatibility-monitor-to-send-feedback.md)</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Common Compatibility Issues](common-compatibility-issues.md)</p></td>
<td align="left"><p>Compatibility issues tend to occur with the following technologies:</p></td>
</tr>
</tbody>
</table>
 
## Related topics
[Deciding Which Applications to Test](deciding-which-applications-to-test.md)
[Creating an Enterprise Environment for Compatibility Testing](creating-an-enterprise-environment-for-compatibility-testing.md)
[Creating a Runtime-Analysis Package](creating-a-runtime-analysis-package.md)
[Deploying a Runtime-Analysis Package](deploying-a-runtime-analysis-package.md)
 
 

108
windows/plan/computer-dialog-box.md Normal file
View File

@ -0,0 +1,108 @@
---
title: &lt;Computer&gt; Dialog Box (Windows 10)
description: In Application Compatibility Manager (ACM), the &lt;Computer&gt; dialog box shows information about the selected computer.
ms.assetid: f89cbb28-adcd-41cd-9a54-402bc4aaffd9
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# &lt;Computer&gt; Dialog Box
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
In Application Compatibility Manager (ACM), the *&lt;Computer&gt;* dialog box shows information about the selected computer.
**To open the &lt;Computer&gt; dialog box**
1. In ACM, in the **Quick Reports** pane, click **Analyze**.
2. Under an operating system heading, click **Computers**.
3. Double-click the name of a computer.
## Tabs in the &lt;Computer&gt; dialog box
The following table shows the information available in the *&lt;Computer&gt;* dialog box.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Tab</th>
<th align="left">Information</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Details</p></td>
<td align="left"><p>Shows the following information for the selected computer:</p>
<ul>
<li><p>The computer name, operating system, architecture, and domain.</p></li>
<li><p>The IP address, Media Access Control (MAC) address, and hardware identifier.</p></li>
<li><p>The manufacturer, asset tag, and system number.</p></li>
<li><p>The hardware specifications.</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>Applications</p></td>
<td align="left"><p>Shows the following information for each of the applications installed on the selected computer:</p>
<ul>
<li><p>The application name, version number, and application vendor.</p></li>
<li><p>The compatibility rating for the application as determined by your organization.</p></li>
<li><p>The compatibility information from the application vendor.</p></li>
<li><p>The compatibility information from the ACT Community, which you can view if you are a member of the ACT Community. For more information, see [Settings Dialog Box - Preferences Tab](settings-dialog-box---preferences-tab.md).</p></li>
<li><p>The issues that have been opened for the application.</p></li>
<li><p>The count of computers in your organization on which the application is installed.</p></li>
</ul></td>
</tr>
<tr class="odd">
<td align="left"><p>Devices</p></td>
<td align="left"><p>Shows the following information for each of the devices installed on the selected computer:</p>
<ul>
<li><p>The model and manufacturer of the device.</p></li>
<li><p>An evaluation of whether the device works on a 32-bit operating system or a 64-bit operating system.</p></li>
<li><p>The class of device, as reported by the device.</p></li>
<li><p>The count of computers in your organization on which the device is installed.</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>Labels</p></td>
<td align="left"><p>Shows the label for the selected computer.</p>
<p>For information about labels, see [Labeling Data in ACM](labeling-data-in-acm.md).</p></td>
</tr>
</tbody>
</table>
 
## Using the &lt;Computer&gt; Dialog Box
In the *&lt;Computer&gt;* dialog box, you can perform the following actions:
- Assign categories and subcategories to the computer. For more information, see [Categorizing Your Compatibility Data](categorizing-your-compatibility-data.md).
- Specify the importance of the computer to your organization. For more information, see [Prioritizing Your Compatibility Data](prioritizing-your-compatibility-data.md).
 
 

89
windows/plan/configuring-act.md Normal file
View File

@ -0,0 +1,89 @@
---
title: Configuring ACT (Windows 10)
description: This section provides information about setting up the Application Compatibility Toolkit (ACT) in your organization.
ms.assetid: aacbe35e-ea40-47ac-bebf-ed2660c8fd86
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Configuring ACT
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
This section provides information about setting up the Application Compatibility Toolkit (ACT) in your organization.
## In this section
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Topic</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[ACT Tools, Packages, and Services](act-tools-packages-and-services.md)</p></td>
<td align="left"><p>The Application Compatibility Toolkit is included with the Windows ADK. [Download the Windows ADK.](http://go.microsoft.com/fwlink/p/?LinkId=526740)</p></td>
</tr>
<tr class="even">
<td align="left"><p>[ACT Deployment Options](act-deployment-options.md)</p></td>
<td align="left"><p>While planning your deployment of the Application Compatibility Toolkit (ACT), consider which computers you want running the various tools, packages, and services for ACT.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[ACT Database Configuration](act-database-configuration.md)</p></td>
<td align="left"><p>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).</p></td>
</tr>
<tr class="even">
<td align="left"><p>[ACT Database Migration](act-database-migration.md)</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[ACT LPS Share Permissions](act-lps-share-permissions.md)</p></td>
<td align="left"><p>To upload log files to the ACT Log Processing Service (LPS) share, certain permissions must be set at the share level and folder level.</p></td>
</tr>
</tbody>
</table>
 
## Related topics
[Welcome to ACT](welcome-to-act.md)
[Using ACT](using-act.md)
[Troubleshooting ACT](troubleshooting-act.md)
[ACT User Interface Reference](act-user-interface-reference.md)
[ACT Product and Documentation Resources](act-product-and-documentation-resources.md)
[ACT Glossary](act-glossary.md)
[Compatibility Fixes for Windows 10, Windows 8, Windows 7, and Windows Vista](compatibility-fixes-for-windows-8-windows-7-and-windows-vista.md)
 
 

89
windows/plan/creating-a-custom-compatibility-fix-in-compatibility-administrator.md Normal file
View File

@ -0,0 +1,89 @@
---
title: Creating a Custom Compatibility Fix in Compatibility Administrator (Windows 10)
description: The Compatibility Administrator tool uses the term fix to describe the combination of compatibility information added to a customized database for a specific application.
ms.assetid: e4f2853a-0e46-49c5-afd7-0ed12f1fe0c2
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Creating a Custom Compatibility Fix in Compatibility Administrator
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
**In this article**
- [What is a Compatibility Fix?](#what_is_a_compatibility_fix_)
- [Searching for Existing Compatibility Fixes](#searching_for_existing_compatibility_fixes)
- [Creating a New Compatibility Fix](#creating_a_new_compatibility_fix)
- [Related topics](#related_topics)
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.
**Important**  
Fixes apply to a single application only; therefore, you must create multiple fixes if you need to fix the same issue in multiple applications.
 
## What is a Compatibility Fix?
A compatibility fix, previously known as a shim, is a small piece of code that intercepts API calls from applications. The fix transforms the API calls so that the current version of the operating system supports the application in the same way as previous versions of the operating system. This can mean anything from disabling a new feature in the current version of the operating system to emulating a particular behavior of an older version of the Windows API.
## Searching for Existing Compatibility Fixes
The Compatibility Administrator tool has preloaded fixes for many common applications, including known compatibility fixes, compatibility modes, and AppHelp messages. Before you create a new compatibility fix, you can search for an existing application and then copy and paste the known fixes into your customized database.
**Important**  
Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version of the Compatibility Administrator tool. You must use the 32-bit version to create custom databases for 32-bit applications and the 64-bit version to create custom databases for 64-bit applications.
 
**To search for an existing application**
1. In the left-side pane of Compatibility Administrator, expand the **Applications** folder and search for your application name.
2. Click the application name to view the preloaded compatibility fixes, compatibility modes, or AppHelp messages.
## Creating a New Compatibility Fix
If you are unable to find a preloaded compatibility fix for your application, you can create a new one for use by your customized database.
**To create a new compatibility fix**
1. In the left-side pane of Compatibility Administrator underneath the **Custom Databases** heading, right-click the name of the database to which you want to apply the compatibility fix, click **Create New**, and then click **Application Fix**.
2. Type the name of the application to which the compatibility fix applies, type the name of the application vendor, browse to the location of the application file (.exe) on your computer, and then click **Next**.
3. Select the operating system for which your compatibility fix applies, click any applicable compatibility modes to apply to your compatibility fix, and then click **Next**.
4. Select any additional compatibility fixes to apply to your compatibility fix, and then click **Next**.
5. Select any additional criteria to use to match your applications to the AppHelp message, and then click **Finish**.
By default, Compatibility Administrator selects the basic matching criteria for your application. As a best practice, use a limited set of matching information to represent your application, because it reduces the size of the database. However, make sure you have enough information to correctly identify your application.
## Related topics
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
 
 

94
windows/plan/creating-a-custom-compatibility-mode-in-compatibility-administrator.md Normal file
View File

@ -0,0 +1,94 @@
---
title: Creating a Custom Compatibility Mode in Compatibility Administrator (Windows 10)
description: Windows® provides several compatibility modes, groups of compatibility fixes found to resolve many common application-compatibility issues.
ms.assetid: 661a1c0d-267f-4a79-8445-62a9a98d09b0
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Creating a Custom Compatibility Mode in Compatibility Administrator
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
**In this article**
- [What Is a Compatibility Mode?](#what_is_a_compatibility_mode_)
- [Searching for Existing Compatibility Modes](#searching_for_existing_compatibility_modes)
- [Creating a New Compatibility Mode](#creating_a_new_compatibility_mode)
- [Related topics](#related_topics)
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.
## What Is a Compatibility Mode?
A compatibility mode is a group of compatibility fixes. A compatibility fix, previously known as a shim, is a small piece of code that intercepts API calls from applications. The fix transforms the API calls so that the current version of the operating system supports the application in the same way as previous versions of the operating system. This can be anything from disabling a new feature in Windows to emulating a particular behavior of an older version of the Windows API.
## Searching for Existing Compatibility Modes
The Compatibility Administrator tool has preloaded fixes for many common applications, including known compatibility fixes, compatibility modes, and AppHelp messages. Before you create a new compatibility mode, you can search for an existing application and then copy and paste the known fixes into your custom database.
**Important**  
Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version of the Compatibility Administrator tool. You must use the 32-bit version to create custom databases for 32-bit applications and the 64-bit version to create custom databases for 64-bit applications.
 
**To search for an existing application**
1. In the left-side pane of Compatibility Administrator, expand the **Applications** folder and search for your application name.
2. Click the application name to view the preloaded compatibility modes, compatibility fixes, or AppHelp messages.
## Creating a New Compatibility Mode
If you are unable to find a preloaded compatibility mode for your application, you can create a new one for use by your custom database.
**Important**  
A compatibility mode includes a set of compatibility fixes and must be deployed as a group. Therefore, you should include only fixes that you intend to deploy together to the database.
 
**To create a new compatibility mode**
1. In the left-side pane of Compatibility Administrator, underneath the **Custom Databases** heading, right-click the name of the database to which you will apply the compatibility mode, click **Create New**, and then click **Compatibility Mode**.
2. Type the name of your custom-compatibility mode into the **Name of the compatibility mode** text box.
3. Select each of the available compatibility fixes to include in your custom-compatibility mode and then click **&gt;**.
**Important**  
If you are unsure which compatibility fixes to add, you can click **Copy Mode**. The **Select Compatibility Mode** dialog box appears and enables you to select from the preloaded compatibility modes. After you select a compatibility mode and click **OK**, any compatibility fixes that are included in the preloaded compatibility mode will be automatically added to your custom-compatibility mode.
 
If you have any compatibility fixes that require additional parameters, you can select the fix, and then click **Parameters**. The **Options for &lt;Compatibility\_Fix\_Name&gt;** dialog box appears, enabling you to update the parameter fields.
4. After you are done selecting the compatibility fixes to include, click **OK**.
The compatibility mode is added to your custom database.
## Related topics
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
 
 

61
windows/plan/creating-a-runtime-analysis-package.md Normal file
View File

@ -0,0 +1,61 @@
---
title: Creating a Runtime-Analysis Package (Windows 10)
description: 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.
ms.assetid: 3c703ebe-46b3-4dcd-b355-b28344bc159b
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Creating a Runtime-Analysis Package
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
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.
**To create a runtime-analysis package**
1. In ACM, click **Collect** to open the Collect screen.
2. On the **File** menu, click **New**.
3. Click **Runtime application testing**.
4. Provide the information that is requested for the package, and then click **Create**.
5. Navigate to the location where you want to save the Windows installer (.msi) file for the package.
This .msi file is the file that you can use to install the runtime-analysis package on each computer in your test environment.
6. Type a file name for the .msi file, and then click **Save**.
7. Click **Finish**.
## Related topics
[Deciding Which Applications to Test](deciding-which-applications-to-test.md)
[Creating an Enterprise Environment for Compatibility Testing](creating-an-enterprise-environment-for-compatibility-testing.md)
[Deploying a Runtime-Analysis Package](deploying-a-runtime-analysis-package.md)
[Compatibility Monitor User's Guide](compatibility-monitor-users-guide.md)
 
 

110
windows/plan/creating-an-apphelp-message-in-compatibility-administrator.md Normal file
View File

@ -0,0 +1,110 @@
---
title: Creating an AppHelp Message in Compatibility Administrator (Windows 10)
description: The Compatibility Administrator tool enables you to create an AppHelp text message. This is a blocking or non-blocking message that appears when a user starts an application that you know has major functionality issues on the Windows® operating system.
ms.assetid: 5c6e89f5-1942-4aa4-8439-ccf0ecd02848
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Creating an AppHelp Message in Compatibility Administrator
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
**In this article**
- [Blocking Versus Non-Blocking AppHelp Messages](#blocking_versus_non-blocking_apphelp_messages)
- [Searching for Existing Compatibility Fixes](#searching_for_existing_compatibility_fixes)
- [Creating a New AppHelp Message](#creating_a_new_apphelp_message)
- [Issues with AppHelp Messages and Computers Running Windows 2000](#issues_with_apphelp_messages_and_computers_running_windows_2000)
- [Related topics](#related_topics)
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.
## Blocking Versus Non-Blocking AppHelp Messages
A blocking AppHelp message prevents the application from starting and displays a message to the user. You can define a specific URL where the user can download an updated driver or other fix to resolve the issue. When using a blocking AppHelp message, you must also define the file-matching information to identify the version of the application and enable the corrected version to continue.
A non-blocking AppHelp message does not prevent the application from starting, but provides a message to the user including information such as security issues, updates to the application, or changes to the location of network resources.
## Searching for Existing Compatibility Fixes
The Compatibility Administrator tool has preloaded fixes for many common applications, including known compatibility fixes, compatibility modes, and AppHelp messages. Before you create a new AppHelp message, you can search for an existing application and then copy and paste the known fixes into your custom database.
**Important**  
Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version of the Compatibility Administrator tool. You must use the 32-bit version to create custom databases for 32-bit applications and the 64-bit version to create custom databases for 64-bit applications.
 
**To search for an existing application**
1. In the left-side pane of Compatibility Administrator, expand the **Applications** folder and search for your application name.
2. Click the application name to view the preloaded AppHelp messages, compatibility fixes, and compatibility modes.
## Creating a New AppHelp Message
If you are unable to find a preloaded AppHelp message for your application, you can create a new one for use by your custom database.
**To create a new AppHelp message**
1. In the left-side pane of Compatibility Administrator, below the **Custom Databases** heading, right-click the name of the database to which you will apply the AppHelp message, click **Create New**, and then click **AppHelp Message**.
2. Type the name of the application to which this AppHelp message applies, type the name of the application vendor, browse to the location of the application file (.exe) on your computer, and then click **Next**.
The wizard shows the known **Matching Information**, which is used for program identification.
3. Select any additional criteria to use to match your applications to the AppHelp message, and then click **Next**.
By default, Compatibility Administrator selects the basic matching criteria for your application.
The wizard shows the **Enter Message Type** options.
4. Click one of the following options:
- **Display a message and allow this program to run**. This is a non-blocking message, which means that you can alert the user that there might be a problem, but the application is not prevented from starting.
- **Display a message and do not allow this program to run**. This is a blocking message, which means that the application will not start. Instead, this message points the user to a location that provides more information about fixing the issue.
5. Click **Next**.
The wizard then shows the **Enter Message Information** fields.
6. Type the website URL and the message text to appear when the user starts the application, and then click **Finish**.
## Issues with AppHelp Messages and Computers Running Windows 2000
The following issues might occur with computers running Windows 2000:
- You might be unable to create a custom AppHelp message.
- The AppHelp message text used for system database entries might not appear.
- Copying an AppHelp entry for a system database or a custom-compatibility fix from a system database might cause Compatibility Administrator to hide the descriptive text.
## Related topics
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
 
 

122
windows/plan/creating-an-enterprise-environment-for-compatibility-testing.md Normal file
View File

@ -0,0 +1,122 @@
---
title: Creating an Enterprise Environment for Compatibility Testing (Windows 10)
description: 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.
ms.assetid: cbf6d8b6-7ebc-4faa-bbbd-e02653ed4adb
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Creating an Enterprise Environment for Compatibility Testing
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
**In this article**
- [Modeling the Production Environment](#modeling_the_production_environment)
- [Configuring the Test Environment for Automated Testing](#configuring_the_test_environment_for_automated_testing)
- [Determining When Virtualization Is Appropriate](#determining_when_virtualization_is_appropriate)
- [Testing Methodology](#testing_methodology)
- [Related topics](#related_topics)
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.
## Modeling the Production Environment
We recommend the following practices for setting up your test environment:
- Physically separate your test environment from your production environment. Physical separation helps ensure that activity in the test environment does not affect the production environment.
- On the computers in your test environment, install the new operating system.
- Perform all of your tests by using accounts that have similar permissions to the accounts in your production environment. This approach helps to ensure that you can determine potential security issues.
## Configuring the Test Environment for Automated Testing
Typically, tests are run more than once, which requires being able to revert your test environment to a previous state. We recommend the following practices to ensure consistency in testing and consistency in restoring the state of your test environment:
- Use disk-imaging software to create physical disk images.
- Use software virtualization features to reverse changes to virtualized hard disks.
## Determining When Virtualization Is Appropriate
The following table shows some of the advantages and disadvantages of virtualization.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Advantages</th>
<th align="left">Disadvantages</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><ul>
<li><p>Supports a large number of servers in a limited amount of physical space. You can run as many virtual servers as the physical computer’s resources allow.</p></li>
<li><p>Easily shares your test environment between teams. For example, your test team can create a virtualized test environment and then provide a copy to your development team for use in its development processes.</p></li>
<li><p>Supports multiple users performing simultaneous testing, mimicking the ability for each user to have a dedicated test environment.</p></li>
<li><p>Easily restores your environment to a previous state. For example, you can revert to a previous state by using the <strong>Undo Disks</strong> option.</p></li>
</ul></td>
<td align="left"><ul>
<li><p>May reduce performance. Virtualized servers may be slower than their physical counterparts. The performance of virtualized servers is reduced because physical resources such as disks are virtualized.</p></li>
<li><p>May not support all applications and device drivers. Some hardware-specific device drivers and applications are not supported in virtualized servers.</p></li>
</ul></td>
</tr>
</tbody>
</table>
 
## Testing Methodology
When testing an application in a new operating system, we recommend the following methods:
- Retain the default security-feature selections.
- Use test automation tools to run your test cases in a consistent, reproducible way.
- Use your application in the same way that you use it in your production environment.
- Use the Compatibility Monitor tool in the runtime-analysis package to gather compatibility feedback.
- Send and receive compatibility data to obtain data and solutions through the Microsoft Compatibility Exchange.
- When testing a website or a web application, include both intranet and extranet sites, prioritizing the list based on how critical the site or the application is to your organization.
## Related topics
[Deciding Which Applications to Test](deciding-which-applications-to-test.md)
[Creating a Runtime-Analysis Package](creating-a-runtime-analysis-package.md)
[Deploying a Runtime-Analysis Package](deploying-a-runtime-analysis-package.md)
[Compatibility Monitor User's Guide](compatibility-monitor-users-guide.md)
 
 

57
windows/plan/creating-an-inventory-collector-package.md Normal file
View File

@ -0,0 +1,57 @@
---
title: Creating an Inventory-Collector Package (Windows 10)
description: You can use Application Compatibility Manager (ACM) to create an inventory-collector package.
ms.assetid: 61d041d6-e308-47b3-921b-709d72926d6d
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Creating an Inventory-Collector Package
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
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.
**To create an inventory-collector package**
1. In ACM, click **Collect** to open the **Collect** screen.
2. On the **File** menu, click **New**.
3. Click **Application inventory**.
4. Provide the information that is requested for the package, and then click **Create**.
5. Browse to the location where you want to save the Windows® Installer (.msi) file for the package.
You can use this .msi file to install the inventory-collector package on each computer for which you want to gather inventory data.
6. Type a file name for the .msi file, and then click **Save**.
7. Click **Finish**.
## Related topics
[Identifying Computers for Inventory Collection](identifying-computers-for-inventory-collection.md)
[Deploying an Inventory-Collector Package](deploying-an-inventory-collector-package.md)
 
 

64
windows/plan/creating-and-editing-issues-and-solutions.md Normal file
View File

@ -0,0 +1,64 @@
---
title: Creating and Editing Issues and Solutions (Windows 10)
description: 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.
ms.assetid: b64fe4e0-24bd-4bbd-9645-80ae5644e774
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Creating and Editing Issues and Solutions
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
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.
## In this section
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Topic</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[Adding or Editing an Issue](adding-or-editing-an-issue.md)</p></td>
<td align="left"><p>In Application Compatibility Manager (ACM), you can enter information about the compatibility issues that you discover.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Adding or Editing a Solution](adding-or-editing-a-solution.md)</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Resolving an Issue](resolving-an-issue.md)</p></td>
<td align="left"><p>You can use Application Compatibility Manager (ACM) to flag issues as resolved. Resolving an issue changes the status of the issue from a red <strong>x</strong> to a green check mark on your report and report detail screens.</p></td>
</tr>
</tbody>
</table>
 
 
 

148
windows/plan/customizing-your-report-views.md Normal file
View File

@ -0,0 +1,148 @@
---
title: Customizing Your Report Views (Windows 10)
description: You can customize how you view your report data in Application Compatibility Manager (ACM).
ms.assetid: ba8da888-6749-43b4-8efb-4f26c7954721
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Customizing Your Report Views
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
You can customize how you view your report data in Application Compatibility Manager (ACM).
## Modifying the &lt;Operating\_System&gt; Reports View
You can choose which operating systems ACM shows in the compatibility reports. For operating systems that you exclude from the reports, the data continues to be collected but ACM does not display it.
If you are using ACM on multiple computers that access the same ACT database, when you remove an operating system from your reports, all of the computers running ACM no longer show the operating system.
**To add or remove an operating system from the Quick Reports pane**
1. On the **Analyze** screen, at the bottom of the **Quick Reports** pane, click **Customize this view**.
2. In the **Deployment Reports** area, select the check boxes for the operating systems you want to show in your reports, and then click **OK**.
3. Select the architectures, **32-bit**, **64-bit**, or **Both**, for which you want to see compatibility ratings in the report screens.
## Adding and Removing Columns from the Report Views
You can add and remove columns from most of the report screens. In the report dialog boxes, you cannot add or remove columns, but you can reorder the columns.
**To add or remove a column**
1. On the selected report screen, right-click the column headings, and then click **Column Options**.
2. Select the check box next to any column that you want to add, and clear the check box next to any column that you want to remove.
3. If you want, reorder the columns by using the **Move Up** and **Move Down** buttons.
4. Click **OK**.
### Columns by Screen
The following table shows the columns that are available for each screen.
<table>
<colgroup>
<col width="33%" />
<col width="33%" />
<col width="33%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Screen</th>
<th align="left">Default columns</th>
<th align="left">Additional columns</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[&lt;OperatingSystem&gt; - Application Report](operatingsystem---application-report.md)</p></td>
<td align="left"><ul>
<li><p>Application Name</p></li>
<li><p>Version</p></li>
<li><p>Company</p></li>
<li><p>My Assessment</p></li>
<li><p>User Assessment</p></li>
<li><p>Send/Receive Status</p></li>
<li><p>Vendor Assessment</p></li>
<li><p>Community Assessment</p></li>
<li><p>Active Issues</p></li>
<li><p>Computers</p></li>
</ul></td>
<td align="left"><ul>
<li><p>Resolved Issues</p></li>
<li><p>Language</p></li>
<li><p>Priority</p></li>
<li><p>Deployment Status</p></li>
<li><p>Issues with Solutions</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>[&lt;OperatingSystem&gt; - Computer Report](operatingsystem---computer-report.md)</p></td>
<td align="left"><ul>
<li><p>Computer Name</p></li>
<li><p>Applications with Issues</p></li>
<li><p>Devices with Issues</p></li>
<li><p>Operating System</p></li>
<li><p>Domain</p></li>
<li><p>Applications</p></li>
<li><p>Devices</p></li>
</ul></td>
<td align="left"><ul>
<li><p>Priority</p></li>
</ul></td>
</tr>
<tr class="odd">
<td align="left"><p>[&lt;OperatingSystem&gt; - Device Report](operatingsystem---device-report.md)</p></td>
<td align="left"><ul>
<li><p>Model</p></li>
<li><p>Manufacturer</p></li>
<li><p>Assessment</p></li>
<li><p>Device Class</p></li>
<li><p>Computers</p></li>
</ul></td>
<td align="left"><ul>
<li><p>Assessment</p></li>
<li><p>Priority</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>[Internet Explorer - Web Site Report](internet-explorer---web-site-report.md)</p></td>
<td align="left"><ul>
<li><p>Web Site</p></li>
<li><p>My Assessment</p></li>
<li><p>Active Issues</p></li>
<li><p>Resolved Issues</p></li>
</ul></td>
<td align="left"><ul>
<li><p>None</p></li>
</ul></td>
</tr>
</tbody>
</table>
 
 
 

238
windows/plan/data-sent-through-the-microsoft-compatibility-exchange.md Normal file
View File

@ -0,0 +1,238 @@
---
title: Data Sent Through the Microsoft Compatibility Exchange (Windows 10)
description: The Microsoft Compatibility Exchange propagates data of various types between Microsoft Corporation, independent software vendors (ISVs) and the Application Compatibility Toolkit (ACT) Community.
ms.assetid: 3ec61e33-9db8-4367-99d5-e05c2f50e144
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Data Sent Through the Microsoft Compatibility Exchange
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
The Microsoft Compatibility Exchange propagates data of various types between Microsoft Corporation, independent software vendors (ISVs) and the Application Compatibility Toolkit (ACT) Community.
## Data Sent to Microsoft
During synchronization, the Microsoft Compatibility Exchange sends the following information to Microsoft Corporation:
- **Application information and properties**. This data includes the application name, the vendor, the version number, the language, and the deployment type.
The data-synchronization process does not send your list of URLs visited as part of the information exchange.
## Data Sent to the ACT Community
The Microsoft Compatibility Exchange sends the following information to the ACT Community for each application that you decide to share with the ACT Community:
- **Application information and properties**. This data includes the application name, the vendor, the version number, the language, and the deployment type.
- **Miscellaneous data**. This data includes:
- The database GUID that identifies the organization that is the source of the data.
- The issue data.
- The issue ID.
- The platform and destination operating system.
- The severity.
- The cause.
- The symptom.
- The solution data.
- The solution type.
- The issue and solution provider.
- The issue and solution subprovider.
- The issue and solution published date.
- Your risk assessment.
The data-synchronization process does not send your list of URLs visited as part of the information exchange.
## Data Matching
After you send your data, the Microsoft Compatibility Exchange matches your application properties against the known issues listed in the Application Profile database. The Microsoft Compatibility Exchange downloads any issues and corresponding solutions that match your application set and then stores the information in your ACT database.
## Data Sent From Microsoft and ISVs
For each application that matches an application in the Application Profile database, the Microsoft Compatibility Exchange returns the following information, provided by authoritative sources including Microsoft Corporation and independent software vendors (ISVs).
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Data</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Risk assessment</p></td>
<td align="left"><p>The determination of whether the application has compatibility issues.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Symptom</p></td>
<td align="left"><p>Behavior exhibited by the application.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Cause</p></td>
<td align="left"><p>Reason for the failure.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Provider and subprovider</p></td>
<td align="left"><p>Source of the compatibility issue.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Issue ID</p></td>
<td align="left"><p>A unique ID number for the compatibility issue.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Severity</p></td>
<td align="left"><p>Impact this issue has on the application experience.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Priority</p></td>
<td align="left"><p>Degree of impact that this issue has on your organization.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Published Date</p></td>
<td align="left"><p>Date that the source entered the data into the database.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Operating system name</p></td>
<td align="left"><p>Friendly name of the installed operating system.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Major version</p></td>
<td align="left"><p>Major version number of the operating system.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Minor version</p></td>
<td align="left"><p>Minor version number of the operating system.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Locale</p></td>
<td align="left"><p>Language ID of the application to which the compatibility issue applies.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Title</p></td>
<td align="left"><p>Short title of the compatibility issue.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Summary</p></td>
<td align="left"><p>Description of the compatibility issue.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Service pack major</p></td>
<td align="left"><p>Major version number of the operating system service pack.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Service pack minor</p></td>
<td align="left"><p>Minor version number of the operating system service pack.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>URL HREF</p></td>
<td align="left"><p>URL of any links provided for the compatibility issue.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Provider and subprovider IDs</p></td>
<td align="left"><p>IDs for the source of the compatibility issue's solution.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Solution type</p></td>
<td align="left"><p>Type of solution provided for the compatibility issue.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Locale</p></td>
<td align="left"><p>Language ID of the application to which the solution applies.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Title</p></td>
<td align="left"><p>Short title of the solution.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Details</p></td>
<td align="left"><p>Description of the solution.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>URL HREF</p></td>
<td align="left"><p>URL of any links provided for the compatibility issue solution.</p></td>
</tr>
</tbody>
</table>
 
## Data Sent From the ACT Community
For each application that matches an application in the Application Profile database, the Microsoft Compatibility Exchange returns the following ACT Community information, which you receive only if you are a member of the ACT Community:
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Data</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p><strong>Works</strong></p></td>
<td align="left"><p>The count of <strong>Works</strong> ratings, for 32-bit and 64-bit operating systems.</p></td>
</tr>
<tr class="even">
<td align="left"><p><strong>Works with Minor Issues or has Solutions</strong></p></td>
<td align="left"><p>The count of <strong>Works with Minor Issues or has Solutions</strong> ratings, for 32-bit and 64-bit operating systems.</p></td>
</tr>
<tr class="odd">
<td align="left"><p><strong>Does Not Work</strong></p></td>
<td align="left"><p>The count of <strong>Does Not Work</strong> ratings, for 32-bit and 64-bit operating systems.</p></td>
</tr>
</tbody>
</table>
 
## Related topics
[Selecting the Send and Receive Status for an Application](selecting-the-send-and-receive-status-for-an-application.md)
[Sending and Receiving Compatibility Data](sending-and-receiving-compatibility-data.md)
 
 

53
windows/plan/deciding-whether-to-fix-an-application-or-deploy-a-workaround.md Normal file
View File

@ -0,0 +1,53 @@
---
title: Deciding Whether to Fix an Application or Deploy a Workaround (Windows 10)
description: You can fix a compatibility issue by changing the code for the application or by deploying a workaround.
ms.assetid: e495d0c8-bfba-4537-bccd-64c4b52206f1
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Deciding Whether to Fix an Application or Deploy a Workaround
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
You can fix a compatibility issue by changing the code for the application or by deploying a workaround.
## Fixing an Application
Fixing an application by changing the code is often the recommended way to address a compatibility issue. Although applying a fix to the code might involve higher initial costs or additional development time, it can limit long-term maintenance or operational costs. After you change the code, all users can use the application without encountering the issue.
If you do not have access to the code, or if you do not have the time and resources to apply a fix, an alternative approach is to deploy a workaround.
## Deploying a Workaround
A workaround involves applying alternative registry settings to address a compatibility issue. Deploying a workaround might be quicker and easier than changing the code, but you can incur long-term maintenance or operational costs. For example, you must make sure that new users have the correct set of features enabled or disabled on their computers. Using a workaround might also make your application or systems less secure. However, the overall security enhancement associated with deploying the newer version of Windows® may more than offset this reduction in security.
Consider changing registry settings as a short-term solution while you develop the long-term solution of changing the code.
## Related topics
[SUA User's Guide](sua-users-guide.md)
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
 
 

53
windows/plan/deciding-which-applications-to-test.md Normal file
View File

@ -0,0 +1,53 @@
---
title: Deciding Which Applications to Test (Windows 10)
description: 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.
ms.assetid: d7c1c28f-b7b4-43ac-bf87-2910a2b603bf
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Deciding Which Applications to Test
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
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.
**To choose the applications to include in compatibility testing**
1. Gather your application and device inventory. For more information, see [Taking Inventory of Your Organization](taking-inventory-of-your-organization.md).
2. Use the Microsoft Compatibility Exchange to get the latest compatibility ratings. For more information, see [Sending and Receiving Compatibility Data](sending-and-receiving-compatibility-data.md).
3. Organize and group your applications, and determine which applications need to be tested. For more information, see [Organizing Your Compatibility Data](organizing-your-compatibility-data.md).
After completing these steps, you can then start creating and deploying your runtime-analysis packages to the test environment for your compatibility testing.
## Related topics
[Creating an Enterprise Environment for Compatibility Testing](creating-an-enterprise-environment-for-compatibility-testing.md)
[Creating a Runtime-Analysis Package](creating-a-runtime-analysis-package.md)
[Deploying a Runtime-Analysis Package](deploying-a-runtime-analysis-package.md)
[Compatibility Monitor User's Guide](compatibility-monitor-users-guide.md)
 
 

51
windows/plan/deleting-a-data-collection-package.md Normal file
View File

@ -0,0 +1,51 @@
---
title: Deleting a Data-Collection Package (Windows 10)
description: In Application Compatibility Manager (ACM), you can delete any of your existing data-collection packages from the database.
ms.assetid: 1b397d7a-7216-4078-93d9-47c7becbf73e
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Deleting a Data-Collection Package
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
In Application Compatibility Manager (ACM), you can delete any of your existing data-collection packages from the database.
You cannot undo the deletion of a data-collection package. If you mistakenly delete a data-collection package, you must create a new package to replace the deleted package.
**To delete a data-collection package**
1. In ACM, click **Collect** to open the Collect screen.
2. Select the data-collection package that you want to delete, and then press the DELETE key.
3. In the confirmation box, click **Yes**.
## Related topics
[Log File Locations for Data-Collection Packages](log-file-locations-for-data-collection-packages.md)
[Exporting a Data-Collection Package](exporting-a-data-collection-package.md)
[Labeling Data in ACM](labeling-data-in-acm.md)
 
 

47
windows/plan/deploying-a-runtime-analysis-package.md Normal file
View File

@ -0,0 +1,47 @@
---
title: Deploying a Runtime-Analysis Package (Windows 10)
description: When you deploy a runtime-analysis package, you are deploying it to your test environment for compatibility testing.
ms.assetid: 304bf0be-0e7c-4c5f-baac-bed7f8bef509
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Deploying a Runtime-Analysis Package
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
When you deploy a runtime-analysis package, you are deploying it to your test environment for compatibility testing.
For information about creating the test environment, see [Creating an Enterprise Environment for Compatibility Testing](creating-an-enterprise-environment-for-compatibility-testing.md).
To deploy a runtime-analysis package, you can use the same deployment methods that you might use to deploy an inventory-collector package. For information about deployment methods, see [Deploying an Inventory-Collector Package](deploying-an-inventory-collector-package.md).
## Related topics
[Deciding Which Applications to Test](deciding-which-applications-to-test.md)
[Creating an Enterprise Environment for Compatibility Testing](creating-an-enterprise-environment-for-compatibility-testing.md)
[Creating a Runtime-Analysis Package](creating-a-runtime-analysis-package.md)
[Compatibility Monitor User's Guide](compatibility-monitor-users-guide.md)
 
 

142
windows/plan/deploying-an-inventory-collector-package.md Normal file
View File

@ -0,0 +1,142 @@
---
title: Deploying an Inventory-Collector Package (Windows 10)
ms.assetid: 8726ff71-0d17-4449-bdb7-66957ae51c62
description:
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Deploying an Inventory-Collector Package
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
You can use the following methods to deploy an inventory-collector package to the destination computers:
- **Group Policy Software Installation.** This is a feature of Active Directory Domain Services in Windows Server. All computers to which you deploy the package must be part of the Active Directory forest.
- **Logon script.** You can use Windows Script Host to create a logon script. Installing by using a logon script requires administrator credentials on the local computer.
- **Microsoft® System Center Configuration Manager.** For information about how to use System Center Configuration Manager, see the product documentation.
- **Manual distribution.** You can use a file server on the network as a software distribution point, or you can distribute removable media. User installation of an inventory-collector package requires administrator credentials on the local computer.
**To deploy an inventory-collector package by using Group Policy Software Installation**
1. Ensure that the computers to which you want to deploy the inventory-collector package are members of the Active Directory forest.
2. Create a Group Policy Object (GPO) for publishing the inventory-collector package.
3. Assign the GPO to the organizational units (OUs) that contain the set of computers.
4. Create and publish a new software installation package by using Group Policy Software Installation.
For information about the Group Policy Software Installation process, see [Best practices for Group Policy Software Installation](http://go.microsoft.com/fwlink/p/?LinkId=87996).
**To assign a logon script for installing an inventory-collector package to an organizational unit**
1. Create the logon script. The following script is an example.
``` syntax
Set ws = WScript.CreateObject("WScript.Shell")
ws.Run("\\servername\collector\package_name.exe")
```
To keep the installation from running repeatedly, your script must create a marker.
For more information about logon scripts, see [Assign a Logon Script to a User in the Active Directory](http://go.microsoft.com/fwlink/p/?LinkId=87997).
2. Save your script in the SYSVOL\\Scripts folder.
3. Open the Active Directory Users and Computers console by clicking **Start**, clicking **All Programs**, clicking **Administrative Tools**, and then clicking **Active Directory Users and Computers**.
4. Right-click the OU to which you intend to assign the logon script, click **Properties**, and then click the **Group Policy** tab.
5. Click **New** to add a new GPO, or select an existing GPO and then click **Edit**.
6. In the left pane, expand the **User Configuration** object, expand the **Windows Setting** object, and then click **Scripts (Logon/Logoff)**.
7. In the right pane, double-click the **Logon** script.
8. Click **Add**.
9. Click **Browse**, browse to the \\\\*&lt;domain&gt;*\\Sysvol\\Scripts folder, select your script, and then click **Open**.
10. Click **OK** to close the **Logon Properties** dialog box.
11. Close the Group Policy Management console and the Active Directory Users and Computers console.
12. On a computer that is a member of the domain and a part of the OU, log on as an OU user.
13. Open a **Command Prompt** window, and then type `GPUPDATE /force` to force the update of the Group Policy setting.
14. At the command prompt, type `RSOP.msc` to verify your Group Policy assignment.
15. In the left pane, expand the **Computer Configuration** object, expand the **Windows Setting** object, and then click **Security Settings**.
16. Expand **Account Policies**, click **Password Policy**, and verify the assigned Group Policy setting.
17. Close the Resultant Set of Policy console and the **Command Prompt** window.
**To deploy an inventory-collector package by using System Center Configuration Manager**
1. Verify that the computers to which you want to deploy the package are included in your Configuration Manager inventory.
2. Create a Configuration Manager computer collection that includes the computers.
3. Create a shared folder that contains the source image of the inventory-collector package.
4. Create a Configuration Manager package that is based on the source image from the shared folder.
For more information, see [How to Create a Package](http://go.microsoft.com/fwlink/p/?LinkId=131355).
5. Specify the Configuration Manager software distribution points.
6. Create a Configuration Manager program that includes the required commands and command-line options to deploy the inventory-collector package.
For more information, see [How to Create a Program](http://go.microsoft.com/fwlink/p/?LinkId=131356).
7. Create a Configuration Manager advertisement that instructs Configuration Manager clients to run the program that you specified in the previous step.
For more information, see [How to Create an Advertisement](http://go.microsoft.com/fwlink/p/?LinkId=131357).
**To deploy an inventory-collector package from a network share**
1. Store your package (.msi) file in a shared folder on the network.
2. Notify the users of the computers that require the inventory-collector package to run the .msi file. For example, you might send an email message that includes a hyperlink to the shared folder.
**To deploy an inventory-collector package to offline computers**
1. In your inventory-collector package, specify a local output path for the log file.
2. Burn your.msi file to removable media.
3. Send the removable media to users of the offline computers.
4. Instruct the users to run the .msi file and then return the generated log file. For example, the users might send the log file in an email message or place the file on a network share.
## Related topics
[Identifying Computers for Inventory Collection](identifying-computers-for-inventory-collection.md)
[Creating an Inventory-Collector Package](creating-an-inventory-collector-package.md)
 
 

332
windows/plan/deployment-considerations-for-windows-to-go.md Normal file
View File

@ -0,0 +1,332 @@
---
title: Deployment considerations for Windows To Go (Windows 10)
description: Deployment considerations for Windows To Go
ms.assetid: dcfc5d96-b96b-44cd-ab65-416b5611c65e
keywords: ["deploy, mobile, device, USB, boot, image, workspace, driver"]
ms.prod: W10
ms.mktglfcycl: deploy
ms.sitesec: library
author: TrudyHa
---
# Deployment considerations for Windows To Go
**Applies to**
- Windows 10
From the start, Windows To Go was designed to minimize differences between the user experience of working on a laptop and Windows To Go booted from a USB drive. Given that Windows To Go was designed as an enterprise solution, extra consideration was given to the deployment workflows that enterprises already have in place. Additionally, there has been a focus on minimizing the number of differences in deployment between Windows To Go workspaces and laptop PCs.
**Note**  
Windows To Go does not support operating system upgrades. Windows To Go is designed as a feature that is managed centrally. IT departments that plan to transition from one operating system version to a later version will need to incorporate re-imaging their existing Windows To Go drives as part of their upgrade deployment process.
 
The following sections discuss the boot experience, deployment methods, and tools that you can use with Windows To Go.
- [Initial boot experiences](#wtg_initboot)
- [Image deployment and drive provisioning considerations](#wtg_imagedep)
- [Application installation and domain join](#wtg_appinstall)
- [Management of Windows To Go using Group Policy](#BKMK_wtggp)
- [Supporting booting from USB](#wtg_bootusb)
- [Updating firmware](#stg_firmware)
- [Configure Windows To Go startup options](#wtg_startup)
- [Change firmware settings](#wtg_changefirmware)
## Initial boot experiences
The following diagrams illustrate the two different methods you could use to provide Windows To Go drives to your users. The experiences differ depending on whether the user will be booting the device initially on-premises or off-premises:
![initial boot on-premises](images/wtg-first-boot-work.gif)
When a Windows To Go workspace is first used at the workplace, the Windows To Go workspace can be joined to the domain through the normal procedures that occur when a new computer is introduced. It obtains a lease, applicable policies are applied and set, and user account tokens are placed appropriately. BitLocker protection can be applied and the BitLocker recovery key automatically stored in Active Directory Domain Services. The user can access network resources to install software and get access to data sources. When the workspace is subsequently booted at a different location either on or off premises, the configuration required for it to connect back to the work network using either DirectAccess or a virtual private network connection can be configured. It is not necessary to configure the workspace for offline domain join. DirectAccess can make connecting to organizational resources easier, but is not required.
![initial boot off-premises](images/wtg-first-boot-home.gif)
When the Windows To Go workspace is going to be used first on an off-premises computer, such as one at the employee’s home, then the IT professional preparing the Windows To Go drives should configure the drive to be able to connect to organizational resources and to maintain the security of the workspace. In this situation, the Windows To Go workspace needs to be configured for offline domain join and BitLocker needs to be enabled before the workspace has been initialized.
**Tip**  
Applying BitLocker Drive Encryption to the drives before provisioning is a much faster process than encrypting the drives after data has already been stored on them due to a new feature called used-disk space only encryption. For more information, see [What's New in BitLocker](http://go.microsoft.com/fwlink/p/?LinkId=619076).
 
DirectAccess can be used to ensure that the user can login with their domain credentials without needing a local account. For instructions on setting up a DirectAccess solution, for a small pilot deployment see [Deploy a Single Remote Access Server using the Getting Started Wizard](http://go.microsoft.com/fwlink/p/?LinkId=619077) for a larger scale deployment, see [Deploy Remote Access in an Enterprise](http://go.microsoft.com/fwlink/p/?LinkId=619078). If you do not want to use DirectAccess as an alternative users could log on using a local user account on the Windows To Go workspace and then use a virtual private network for remote access to your organizational network.
### Image deployment and drive provisioning considerations
The Image Deployment process can be accomplished either by a centralized IT process for your organization or by individual users creating their own Windows To Go workspaces. You must have local Administrator access and access to a Windows 10 Enterprise or Windows 10 Education image to create a Windows To Go workspace, or you must be using System Center Configuration Manager 2012 Service Pack 1 or later to distribute Windows To Go workspaces to users. The image deployment process takes a blank USB drive and a Windows 10 Enterprise image (WIM) and turns it into a Windows To Go drive.
![windows to go image deployment](images/wtg-image-deployment.gif)
The simplest way to provision a Windows To Go drive is to use the Windows To Go Creator. After a single Windows To Go workspace has been created, it can be duplicated as many times as necessary using widely available USB duplicator products as long as the device has not been booted. After the Windows To Go drive is initialized, it should not be duplicated. Alternatively, Windows To Go Workspace Creator can be run multiple times to create multiple Windows To Go drives.
**Tip**  
When you create your Windows To Go image use sysprep /generalize, just as you do when you deploy Windows 10 to a standard PC. In fact, if appropriate, use the same image for both deployments.
 
**Driver considerations**
Windows includes most of the drivers that you will need to support a wide variety of host computers. However, you will occasionally need to download drivers from Windows Update to take advantage of the full functionality of a device. If you are using Windows To Go on a set of known host computers, you can add any additional drivers to the image used on Windows To Go to make Windows To Go drives more quickly usable by your employees. Especially ensure that network drivers are available so that the user can connect to Windows Update to get additional drivers if necessary.
Wi-Fi network adapter drivers are one of the most important drivers to make sure that you include in your standard image so that users can easily connect to the internet for any additional updates. IT administrators that are attempting to build Windows 10 images for use with Windows To Go should consider adding additional Wi-Fi drivers to their image to ensure that their users have the best chance of still having basic network connectivity when roaming between systems.
The following list of commonly used Wi-Fi network adapters that are not supported by the default drivers provided with Windows 10 is provided to help you ascertain whether or not you need to add drivers to your image.
<table>
<colgroup>
<col width="25%" />
<col width="25%" />
<col width="25%" />
<col width="25%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p><strong>Vendor name</strong></p></td>
<td align="left"><p><strong>Product description</strong></p></td>
<td align="left"><p><strong>HWID</strong></p></td>
<td align="left"><p><strong>Windows Update availability</strong></p></td>
</tr>
<tr class="even">
<td align="left"><p>Broadcom</p></td>
<td align="left"><p>802.11abgn Wireless SDIO adapter</p></td>
<td align="left"><p>sd\vid_02d0&amp;pid_4330&amp;fn_1</p></td>
<td align="left"><p>Contact the system OEM or Broadcom for driver availability.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Broadcom</p></td>
<td align="left"><p>802.11n Network Adapter</p></td>
<td align="left"><p>pci\ven_14e4&amp;dev_4331&amp;subsys_00d6106b&amp;rev_02</p></td>
<td align="left"><p>Contact the system OEM or Broadcom for driver availability.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Broadcom</p></td>
<td align="left"><p>802.11n Network Adapter</p></td>
<td align="left"><p>pci\ven_14e4&amp;dev_4331&amp;subsys_00f5106b&amp;rev_02</p></td>
<td align="left"><p>Contact the system OEM or Broadcom for driver availability.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Broadcom</p></td>
<td align="left"><p>802.11n Network Adapter</p></td>
<td align="left"><p>pci\ven_14e4&amp;dev_4331&amp;subsys_00ef106b&amp;rev_02</p></td>
<td align="left"><p>Contact the system OEM or Broadcom for driver availability.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Broadcom</p></td>
<td align="left"><p>802.11n Network Adapter</p></td>
<td align="left"><p>pci\ven_14e4&amp;dev_4331&amp;subsys_00f4106b&amp;rev_02</p></td>
<td align="left"><p>Contact the system OEM or Broadcom for driver availability.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Broadcom</p></td>
<td align="left"><p>802.11n Network Adapter</p></td>
<td align="left"><p>pci\ven_14e4&amp;dev_4331&amp;subsys_010e106b&amp;rev_02</p></td>
<td align="left"><p>Contact the system OEM or Broadcom for driver availability.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Broadcom</p></td>
<td align="left"><p>802.11n Network Adapter</p></td>
<td align="left"><p>pci\ven_14e4&amp;dev_4331&amp;subsys_00e4106b&amp;rev_02</p></td>
<td align="left"><p>Contact the system OEM or Broadcom for driver availability.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Broadcom</p></td>
<td align="left"><p>802.11n Network Adapter</p></td>
<td align="left"><p>pci\ven_14e4&amp;dev_4331&amp;subsys_433114e4&amp;rev_02</p></td>
<td align="left"><p>Contact the system OEM or Broadcom for driver availability.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Broadcom</p></td>
<td align="left"><p>802.11n Network Adapter</p></td>
<td align="left"><p>pci\ven_14e4&amp;dev_4331&amp;subsys_010f106b&amp;rev_02</p></td>
<td align="left"><p>Contact the system OEM or Broadcom for driver availability.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Marvell</p></td>
<td align="left"><p>Yukon 88E8001/8003/8010 PCI Gigabit Ethernet</p></td>
<td align="left"><p>pci\ven_11ab&amp;dev_4320&amp;subsys_811a1043</p></td>
<td align="left"><p>[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619080)</p>
<p>[64-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619082)</p></td>
</tr>
<tr class="even">
<td align="left"><p>Marvell</p></td>
<td align="left"><p>Libertas 802.11b/g Wireless</p></td>
<td align="left"><p>pci\ven_11ab&amp;dev_1faa&amp;subsys_6b001385&amp;rev_03</p></td>
<td align="left"><p>[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619128)</p>
<p>[64-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619129)</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Qualcomm</p></td>
<td align="left"><p>Atheros AR6004 Wireless LAN Adapter</p></td>
<td align="left"><p>sd\vid_0271&amp;pid_0401</p></td>
<td align="left"><p>[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619086)</p>
<p>64-bit driver not available</p></td>
</tr>
<tr class="even">
<td align="left"><p>Qualcomm</p></td>
<td align="left"><p>Atheros AR5BWB222 Wireless Network Adapter</p></td>
<td align="left"><p>pci\ven_168c&amp;dev_0034&amp;subsys_20031a56</p></td>
<td align="left"><p>[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619348)</p>
<p>64-bit driver not available</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Qualcomm</p></td>
<td align="left"><p>Atheros AR5BWB222 Wireless Network Adapter</p></td>
<td align="left"><p>pci\ven_168c&amp;dev_0034&amp;subsys_020a1028&amp;rev_01</p></td>
<td align="left"><p>Contact the system OEM or Qualcom for driver availability.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Qualcomm</p></td>
<td align="left"><p>Atheros AR5005G Wireless Network Adapter</p></td>
<td align="left"><p>pci\ven_168c&amp;dev_001a&amp;subsys_04181468&amp;rev_01</p></td>
<td align="left"><p>[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619349)</p>
<p>[64-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619091)</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Ralink</p></td>
<td align="left"><p>Wireless-G PCI Adapter</p></td>
<td align="left"><p>pci\ven_1814&amp;dev_0301&amp;subsys_00551737&amp;rev_00</p></td>
<td align="left"><p>[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619092)</p>
<p>[64-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619093)</p></td>
</tr>
<tr class="even">
<td align="left"><p>Ralink</p></td>
<td align="left"><p>Turbo Wireless LAN Card</p></td>
<td align="left"><p>pci\ven_1814&amp;dev_0301&amp;subsys_25611814&amp;rev_00</p></td>
<td align="left"><p>[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619094)</p>
<p>[64-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619095)</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Ralink</p></td>
<td align="left"><p>Wireless LAN Card V1</p></td>
<td align="left"><p>pci\ven_1814&amp;dev_0302&amp;subsys_3a711186&amp;rev_00</p></td>
<td align="left"><p>[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619097)</p>
<p>[64-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619098)</p></td>
</tr>
<tr class="even">
<td align="left"><p>Ralink</p></td>
<td align="left"><p>D-Link AirPlus G DWL-G510 Wireless PCI Adapter(rev.C)</p></td>
<td align="left"><p>pci\ven_1814&amp;dev_0302&amp;subsys_3c091186&amp;rev_00</p></td>
<td align="left"><p>[32-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619099)</p>
<p>[64-bit driver](http://go.microsoft.com/fwlink/p/?LinkId=619100)</p></td>
</tr>
</tbody>
</table>
 
IT administrators that want to target Windows To Go images for specific systems should test their images to ensure that the necessary system drivers are in the image, especially for critical functionality like Wi-Fi that is not supported by class drivers. Some consumer devices require OEM specific driver packages, which may not be available on Windows Update. For more information on how to add a driver to a Windows Image, please refer to the [Basic Windows Deployment Step-by-Step Guide](http://go.microsoft.com/fwlink/p/?LinkId=619079).
### Application installation and domain join
Unless you are using a customized Windows image that includes unattended installation settings, the initial Windows To Go workspace will not be domain joined and will not contain applications. This is exactly like a new installation of Windows on a desktop or laptop computer. When planning your deployment, you should develop methods to join Windows to Go drives to the domain and install the standard applications that users in your organization require. These methods probably will be similar to the ones used for setting up desktop and laptop computers with domain privileges and applications
### Management of Windows To Go using Group Policy
In general, management of Windows To Go workspaces is same as that for desktop and laptop computers. There are Windows To Go specific Group Policy settings that should be considered as part of Windows To Go deployment. Windows To Go Group Policy settings are located at `\\Computer Configuration\Administrative Templates\Windows Components\Portable Operating System\` in the Local Group Policy Editor.
The use of the Store on Windows To Go workspaces that are running Windows 8 can also be controlled by Group Policy. This policy setting is located at `\\Computer Configuration\Administrative Templates\Windows Components\Store\` in the Local Group Policy Editor. The policy settings have specific implications for Windows To Go that you should be aware of when planning your deployment:
**Settings for workspaces**
- **Allow hibernate (S4) when started from a Windows To Go workspace**
This policy setting specifies whether the PC can use the hibernation sleep state (S4) when started from a Windows To Go workspace. By default, hibernation is disabled when using Windows To Go workspace, so enabling this setting explicitly turns this ability back on. When a computer enters hibernation, the contents of memory are written to disk. When the disk is resumed, it is important that the hardware attached to the system, as well as the disk itself, are unchanged. This is inherently incompatible with roaming between PC hosts. Hibernation should only be used when the Windows To Go workspace is not being used to roam between host PCs.
**Important**  
For the host-PC to resume correctly when hibernation is enabled the Windows To Go workspace must continue to use the same USB port.
 
- **Disallow standby sleep states (S1-S3) when starting from a Windows To Go workspace**
This policy setting specifies whether the PC can use standby sleep states (S1–S3) when started from a Windows To Go workspace. The Sleep state also presents a unique challenge to Windows To Go users. When a computer goes to sleep, it appears as if it is shut down. It could be very easy for a user to think that a Windows To Go workspace in sleep mode was actually shut down and they could remove the Windows To Go drive and take it home. Removing the Windows To Go drive in this scenario is equivalent to an unclean shutdown which may result in the loss of unsaved user data or the corruption on the drive. Moreover, if the user now boots the drive on another PC and brings it back to the first PC which still happens to be in the sleep state, it will lead to an arbitrary crash and eventually corruption of the drive and result in the workspace becoming unusable. If you enable this policy setting, the Windows To Go workspace cannot use the standby states to cause the PC to enter sleep mode. If you disable or do not configure this policy setting, the Windows To Go workspace can place the PC in sleep mode.
**Settings for host PCs**
- **Windows To Go Default Startup Options**
This policy setting controls whether the host computer will boot to Windows To Go if a USB device containing a Windows To Go workspace is connected, and controls whether users can make changes using the **Windows To Go Startup Options** settings dialog. If you enable this policy setting, booting to Windows To Go when a USB device is connected will be enabled and users will not be able to make changes using the **Windows To Go Startup Options** settings dialog. If you disable this policy setting, booting to Windows To Go when a USB device is connected will not be enabled unless a user configures the option manually in the firmware. If you do not configure this policy setting, users who are members of the local Administrators group can enable or disable booting from USB using the **Windows To Go Startup Options** settings dialog.
**Important**  
Enabling this policy setting will cause PCs running Windows to attempt to boot from any USB device that is inserted into the PC before it is started.
 
## Supporting booting from USB
The biggest hurdle for a user wanting to use Windows To Go is configuring their computer to boot from USB. This is traditionally done by entering the firmware and configuring the appropriate boot order options. To ease the process of making the firmware modifications required for Windows To Go, Windows includes a feature named **Windows To Go Startup Options** that allows a user to configure their computer to boot from USB from within Windows—without ever entering their firmware, as long as their firmware supports booting from USB.
**Note**  
Enabling a system to always boot from USB first has implications that you should consider. For example, a USB device that includes malware could be booted inadvertently to compromise the system, or multiple USB drives could be plugged in to cause a boot conflict. For this reason, the Windows To Go startup options are disabled by default. In addition, administrator privileges are required to configure Windows To Go startup options.
 
If you are going to be using a Windows 7 computer as a host-PC, see the wiki article [Tips for configuring your BIOS settings to work with Windows To Go](http://go.microsoft.com/fwlink/p/?LinkID=618951).
### Roaming between different firmware types
Windows supports two types of PC firmware: Unified Extensible Firmware Interface (UEFI), which is the new standard, and legacy BIOS firmware, which was used in most PCs shipping with Windows 7 or earlier version of Windows. Each firmware type has completely different Windows boot components that are incompatible with each other. Beyond the different boot components, Windows supports different partition styles and layout requirements for each type of firmware as shown in the following diagrams.
![bios layout](images/wtg-mbr-bios.gif)![uefi layout](images/wtg-gpt-uefi.gif)
This presented a unique challenge for Windows To Go because the firmware type is not easily determined by end-users—a UEFI computer looks just like a legacy BIOS computer and Windows To Go must boot on both types of firmware.
To enable booting Windows To Go on both types of firmware, a new disk layout is provided for Windows 8 or later that contains both sets of boot components on a FAT32 system partition and a new command-line option was added to bcdboot.exe to support this configuration. The **/f** option is used with the **bcdboot /s** command to specify the firmware type of the target system partition by appending either **UEFI**, **BIOS** or **ALL**. When creating Windows To Go drives manually you must use the **ALL** parameter to provide the Windows To Go drive the ability to boot on both types of firmware. For example, on volume H: (your Windows To Go USB drive letter), you would use the command **bcdboot C:\\windows /s H: /f ALL**. The following diagram illustrates the disk layout that results from that command:
![firmware roaming disk layout](images/wtg-mbr-firmware-roaming.gif)
This is the only supported disk configuration for Windows To Go. With this disk configuration, a single Windows To Go drive can be booted on computers with UEFI and legacy BIOS firmware.
### Configure Windows To Go startup options
Windows To Go Startup Options is a setting available on Windows 10-based PCs that enables the computer to be booted from a USB without manually changing the firmware settings of the PC. To configure Windows To Go Startup Options you must have administrative rights on the computer and the **Windows To Go Default Startup Options** Group Policy setting must not be configured.
**To configure Windows To Go startup options**
1. On the Start screen, type, type **Windows To Go Startup Options**, click **Settings** and then press Enter.
![windows to go startup options](images/wtg-startup-options.gif)
2. Select **Yes** to enable the startup options.
**Tip**  
If your computer is part of a domain, the Group Policy setting can be used to enable the startup options instead of the dialog.
 
3. Click **Save Changes**. If the User Account Control dialog box is displayed, confirm that the action it displays is what you want, and then click **Yes**.
### Change firmware settings
If you choose to not use the Windows To Go startup options or are using a PC running Windows 7 as your host computer you will need to manually configure the firmware settings. The process used to accomplish this will depend on the firmware type and manufacturer. If your host computer is protected by BitLocker and running Windows 7 you should suspend BitLocker before making the change to the firmware settings. After the firmware settings have been successfully reconfigured, resume BitLocker protection. If you do not suspend BitLocker first, BitLocker will assume that the computer has been tampered with and will boot into BitLocker recovery mode.
## Related topics
[Windows To Go: feature overview](windows-to-go-feature-overview-scenario.md)
[Prepare your organization for Windows To Go](prepare-your-organization-for-windows-to-go.md)
[Security and data protection considerations for Windows To Go](security-and-data-protection-considerations-for-windows-to-go.md)
[Windows To Go: frequently asked questions](windows-to-go-frequently-asked-questions.md)
 
 

89
windows/plan/device-dialog-box.md Normal file
View File

@ -0,0 +1,89 @@
---
title: &lt;Device&gt; Dialog Box (Windows 10)
description: In Application Compatibility Manager (ACM), the &lt;Device&gt; dialog box shows information about the selected device.
ms.assetid: 5bd7cfda-31ea-4967-8b64-6c0425092f4e
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# &lt;Device&gt; Dialog Box
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
In Application Compatibility Manager (ACM), the *&lt;Device&gt;* dialog box shows information about the selected device.
**To open the &lt;Device&gt; dialog box**
1. In ACM, in the **Quick Reports** pane, click **Analyze**.
2. Under an operating system heading, click **Devices**.
3. Double-click the name of a device.
## Tabs in the &lt;Device&gt; dialog box
The following table shows the information available in the *&lt;Device&gt;* dialog box.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Tab</th>
<th align="left">Information</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Details</p></td>
<td align="left"><p>Shows the following information for the selected device:</p>
<ul>
<li><p>The model and manufacturer of the device.</p></li>
<li><p>The class of device, as reported by the device.</p></li>
<li><p>An evaluation of whether the device works on a 32-bit operating system or a 64-bit operating system.</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>Computers</p></td>
<td align="left"><p>Shows the following information for each of the computers on which the device is installed:</p>
<ul>
<li><p>Computer name, domain, and operating system.</p></li>
<li><p>The count of installed applications and devices.</p></li>
<li><p>The count of installed applications and devices that have issues.</p></li>
</ul></td>
</tr>
</tbody>
</table>
 
## Using the &lt;Device&gt; Dialog Box
In the *&lt;Device&gt;* dialog box, you can perform the following actions:
- Assign categories and subcategories to the device. For more information, see [Categorizing Your Compatibility Data](categorizing-your-compatibility-data.md).
- Specify the importance of the device to your organization. For more information, see [Prioritizing Your Compatibility Data](prioritizing-your-compatibility-data.md).
 
 

73
windows/plan/enabling-and-disabling-compatibility-fixes-in-compatibility-administrator.md Normal file
View File

@ -0,0 +1,73 @@
---
title: Enabling and Disabling Compatibility Fixes in Compatibility Administrator (Windows 10)
description: You can disable and enable individual compatibility fixes in your customized databases for testing and troubleshooting purposes.
ms.assetid: 6bd4a7c5-0ed9-4a35-948c-c438aa4d6cb6
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Enabling and Disabling Compatibility Fixes in Compatibility Administrator
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
You can disable and enable individual compatibility fixes in your customized databases for testing and troubleshooting purposes.
## Disabling Compatibility Fixes
Customized compatibility databases can become quite complex as you add your fixes for the multiple applications found in your organization. Over time, you may find you need to disable a particular fix in your customized database. For example, if a software vendor releases a fix for an issue addressed in one of your compatibility fixes, you must validate that the vendor's fix is correct and that it resolves your issue. To do this, you must temporarily disable the compatibility fix and then test your application.
**Important**  
Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version of the Compatibility Administrator tool. You must use the 32-bit version to work with custom databases for 32-bit applications and the 64-bit version to work with custom databases for 64-bit applications.
 
**To disable a compatibility fix within a database**
1. In the left-sde pane of Compatibility Administrator, expand the custom database that includes the compatibility fix that you want to disable, and then select the specific compatibility fix.
The compatibility fix details appear in the right-hand pane.
2. On the **Database** menu, click **Disable Entry**.
**Important**  
When you disable an entry, it will remain disabled even if you do not save the database file.
 
## Enabling Compatibility Fixes
You can enable your disabled compatibility fixes at any time.
**To enable a compatibility fix within a database**
1. In the left-side pane of Compatibility Administrator, expand the custom database that includes the compatibility fix that you want to enable, and then select the specific compatibility fix.
The compatibility fix details appear in the right-side pane.
2. On the **Database** menu, click **Enable Entry**.
## Related topics
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
 
 

78
windows/plan/example-filter-queries.md Normal file
View File

@ -0,0 +1,78 @@
---
title: Example Filter Queries (Windows 10)
description: You can filter your compatibility-issue data or reports by selecting specific restriction criteria.
ms.assetid: eae59380-56cc-4d57-bd2c-11a0e3c689c9
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Example Filter Queries
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
You can filter your compatibility-issue data or reports by selecting specific restriction criteria.
## Example Queries
The following sections show example queries created by using the Query Builder.
### All Applications with Issues
The following example query returns all applications that have one or more known issues.
![act filter example all apps with issues](images/dep-win8-e-act-filterexampleallappswissues.gif)
### All Applications with Solutions for Known Issues
The following example query returns all applications that have solutions for their known issues.
![act filter examples for issues with solutions](images/dep-win8-e-act-filterexampleforissueswsolutions.gif)
### All Applications with Specific Solution Types
The following example query returns all applications that have a solution type of Application Update or Application Configuration.
![act filter example for specific solutions](images/dep-win8-e-act-filterexampleforspecificsolutions.gif)
### All Applications with No Known Issues
The following example query returns all applications that have no known issues.
![act filter example all apps with no issues](images/dep-win8-e-act-filterexampleallapps0issues.gif)
### All Applications with No Active Issues
The following example query returns all applications that have no active issues.
![act filter example all apps with no active issues](images/dep-win8-e-act-filterexampleallapps0activeissues.gif)
### All Applications Appearing in a Specific Category and Subcategory
The following example query returns all applications that have a category of Department and a subcategory of either Human Resources or Finance.
![act filter example category](images/dep-win8-e-act-filterexamplecategory.gif)
## Related topics
[Filtering Your Compatibility Data](filtering-your-compatibility-data.md)
 
 

53
windows/plan/exporting-a-data-collection-package.md Normal file
View File

@ -0,0 +1,53 @@
---
title: Exporting a Data-Collection Package (Windows 10)
description: 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.
ms.assetid: 98fe19e4-9533-4ffc-a275-8b3776ee93ed
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Exporting a Data-Collection Package
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
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.
You can export only one data-collection package at a time.
**To export a data-collection package**
1. In ACM, click **Collect** to open the Collect screen.
2. Select the data-collection package that you want to export.
3. On the **File** menu, click **Export**.
4. Navigate to the folder where you want to store the Windows installer (.msi) file for the data-collection package, and then click **Save**.
## Related topics
[Log File Locations for Data-Collection Packages](log-file-locations-for-data-collection-packages.md)
[Deleting a Data-Collection Package](deleting-a-data-collection-package.md)
[Labeling Data in ACM](labeling-data-in-acm.md)
 
 

114
windows/plan/filtering-your-compatibility-data.md Normal file
View File

@ -0,0 +1,114 @@
---
title: Filtering Your Compatibility Data (Windows 10)
description: You can use Query Builder to filter your compatibility-issue data or reports by selecting specific restriction criteria.
ms.assetid: b64267b5-83c0-4b4d-a075-0975d3a359c8
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Filtering Your Compatibility Data
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
You can use Query Builder to filter your compatibility-issue data or reports by selecting specific restriction criteria.
The following table shows the columns in Query Builder.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Column</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>And/Or</p></td>
<td align="left"><p>If you select <strong>And</strong>, your data must match all query rows to appear as a returned result.</p>
<p>If you select <strong>Or</strong>, your data can match any query row to appear as a returned result.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Field</p></td>
<td align="left"><p>Select filter criteria.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Operator</p></td>
<td align="left"><p>Select an operator. The available operators depend on the field that you choose.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Value</p></td>
<td align="left"><p>Type or select a value.</p></td>
</tr>
</tbody>
</table>
 
## Creating Basic Queries
You can insert as many query clauses as you want to create a customized view of your compatibility data.
**Note**  
The following examples use the **&lt;Operating\_System&gt; - Application Report** screen. The process is the same for other report types.
 
**To create a basic query**
1. On the **&lt;Operating\_System&gt; - Application Report** screen, click **Toggle Filter**.
2. In the Query Builder, enter your filter criteria, pressing the Tab key to add clauses.
To delete a clause, right-click the row, and then click **Delete Clause**.
3. Click **Refresh**.
Your filtered results appear. To close the Query Builder, click **Toggle Filter** again.
## Querying on Objects
You can query your compatibility data based on its relationship with other objects. For example, in the applications report, you can query for applications that have corresponding issues. Fields that have a (+) suffix in Query Builder are collections of objects.
**To query for a collection of objects**
1. In Query Builder, in the **Field** column, click any field that contains a plus sign (+) as suffix.
2. In the **Operator** column, select **Exists**, **Not Exists**, or **All Have**.
Query Builder creates a group clause, which is shown by a bracket that spans the rows that are included in the group.
3. Move your cursor to the next row in the group clause, and then in the **Field** column, select a field.
4. In the **Operator** column, select an operator.
5. In the **Value** column, enter a value, and then click **Refresh**.
## Related topics
[Example Filter Queries](example-filter-queries.md)
 
 

70
windows/plan/fixing-applications-by-using-the-sua-tool.md Normal file
View File

@ -0,0 +1,70 @@
---
title: Fixing Applications by Using the SUA Tool (Windows 10)
description: On the user interface for the Standard User Analyzer (SUA) tool, you can apply fixes to an application.
ms.assetid: 7f5947b1-977b-4d7e-bb52-fbe8e76f6b8b
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Fixing Applications by Using the SUA Tool
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
On the user interface for the Standard User Analyzer (SUA) tool, you can apply fixes to an application.
**To fix an application by using the SUA tool**
1. Use the SUA tool to test an application. For more information, see [Using the SUA Tool](using-the-sua-tool.md).
2. After you finish testing, open the SUA tool.
3. On the **Mitigation** menu, click the command that corresponds to the action that you want to take. The following table describes the commands.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Mitigation menu command</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p><strong>Apply Mitigations</strong></p></td>
<td align="left"><p>Opens the <strong>Mitigate AppCompat Issues</strong> dialog box, in which you can select the fixes that you intend to apply to the application.</p></td>
</tr>
<tr class="even">
<td align="left"><p><strong>Undo Mitigations</strong></p></td>
<td align="left"><p>Removes the application fixes that you just applied.</p>
<p>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 <strong>Programs and Features</strong> in Control Panel.</p></td>
</tr>
<tr class="odd">
<td align="left"><p><strong>Export Mitigations as Windows Installer file</strong></p></td>
<td align="left"><p>Exports your application fixes as a Windows® Installer (.msi) file, which can then be deployed to other computers that are running the application.</p></td>
</tr>
</tbody>
</table>
 
 
 

77
windows/plan/fixing-compatibility-issues.md Normal file
View File

@ -0,0 +1,77 @@
---
title: Fixing Compatibility Issues (Windows 10)
description: This section provides step-by-step instructions and describes development tools that you can use to help fix your compatibility issues.
ms.assetid: 30ba8d14-a41a-41b3-9019-e8658d6974de
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Fixing Compatibility Issues
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
This section provides step-by-step instructions and describes development tools that you can use to help fix your compatibility issues.
## In this section
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Topic</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[Deciding Whether to Fix an Application or Deploy a Workaround](deciding-whether-to-fix-an-application-or-deploy-a-workaround.md)</p></td>
<td align="left"><p>You can fix a compatibility issue by changing the code for the application or by deploying a workaround.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[SUA User's Guide](sua-users-guide.md)</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)</p></td>
<td align="left"><p>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:</p></td>
</tr>
</tbody>
</table>
 
## Related topics
[Taking Inventory of Your Organization](taking-inventory-of-your-organization.md)
[Testing Compatibility on the Target Platform](testing-compatibility-on-the-target-platform.md)
[Managing Your Data-Collection Packages](managing-your-data-collection-packages.md)
[Analyzing Your Compatibility Data](analyzing-your-compatibility-data.md)
[Troubleshooting ACT](troubleshooting-act.md)
 
 

47
windows/plan/guidance-for-education-environments.md Normal file
View File

@ -0,0 +1,47 @@
---
title: Guidance for education environments (Windows 10)
description: Find resources to help you plan your deployment of Windows 10 to desktops, laptops, tablets, and other devices in educational institutions.
ms.assetid: 225C9D6F-9329-4DDF-B447-6CE7804E314E
ms.prod: W10
ms.mktglfcycl: plan
ms.sitesec: library
author: TrudyHa
---
# Guidance for education environments
Find resources to help you plan your deployment of Windows 10 to desktops, laptops, tablets, and other devices in educational institutions.
## In this section
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Topic</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[Chromebook migration guide](chromebook-migration-guide.md)</p></td>
<td align="left"><p>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.</p></td>
</tr>
</tbody>
</table>
 
 
 

113
windows/plan/identifying-computers-for-inventory-collection.md Normal file
View File

@ -0,0 +1,113 @@
---
title: Identifying Computers for Inventory Collection (Windows 10)
ms.assetid: f5bf2d89-fff2-4960-a153-dc1146b442fb
description:
ms.prod: W10
ms.mktglfcycl: operate
ms.sitesec: library
author: TrudyHa
---
# Identifying Computers for Inventory Collection
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
**In this article**
- [Managed and Unmanaged Environments](#BMK_ManagedUnmanaged)
- [Role-Based Applications](#BMK_RolebasedApplications)
- [Software Distribution](#BMK_SoftwareDistribution)
- [Geographic Distribution](#BMK_GeographicDistribution)
- [Computer Types](#BMK_ComputerTypes)
- [Related topics](#related_topics)
An inventory-collector package gathers inventory data from the computers on which it is installed. This data includes the following:
- **System inventory.** Information about the client computer. This information includes the memory capacity, the processor speed, and the processor architecture.
- **Device inventory.** Information about the devices that are installed on the client computer. This information includes the model, the manufacturer, and the device class.
- **Software inventory.** An inventory of the applications that are installed on the computer. This information includes system technologies such as Windows® Installer.
To generate a complete inventory and obtain a comprehensive view of your organization, inventory all computers. However, remember that deploying inventory-collector packages to all computers in your organization will require the additional work of analyzing and reducing a larger list of applications. If you do not have the resources to deploy to all computers or you cannot process a larger list of applications, consider deploying inventory-collector packages to representative subsets of computers instead.
If you decide to deploy inventory-collector packages to representative subsets of computers in your organization, consider the following:
- [Managed and Unmanaged Environments](#BMK_ManagedUnmanaged)
- [Role-Based Applications](#BMK_RolebasedApplications)
- [Software Distribution](#BMK_SoftwareDistribution)
- [Geographic Distribution](#BMK_GeographicDistribution)
- [Computer Types](#BMK_ComputerTypes)
## Managed and Unmanaged Environments
In your organization, you may have managed environments and unmanaged environments.
In a managed environment, IT administrators strictly control and manage the installation and use of applications. In this environment, you can discover the full inventory by deploying inventory-collector packages to a limited subset of computers.
In an unmanaged environment, users have administrator permissions and can install applications at their own discretion. To obtain the full inventory, you must deploy your inventory-collector packages to more computers.
## Role-Based Applications
Your organization may use role-based applications that relate to job function. For example, accountants may use finance-related applications. Reviewing application use together with job function helps you better identify which subsets of computers need inventory-collector packages.
## Software Distribution
You can distribute applications in various ways within an organization. For example, you can use Group Policy, Microsoft® IntelliMirror®, Microsoft System Center Configuration Manager, or a customized distribution method. Reviewing the policies for your software distribution system helps you better identify which subsets of computers need inventory-collector packages.
## Geographic Distribution
While you plan for inventory collection, consider the geographic distribution of your organization, and consider application use within each region. Be sure to account for divisional applications, localized applications, and applications that are specific to the geographic location and export restrictions. Consult with technical and business leaders from each region to understand the differences and determine which subsets of computers need inventory-collector packages.
## Computer Types
Computer types can be an important factor in the deployment of inventory-collector packages. The following sections describe common computer types.
### Mobile Computers
Mobile users are frequently offline, occasionally synchronizing with the corporate network through a LAN or VPN connection. The user must be online for the inventory-collector package to be downloaded and installed, and must be online again for the logged data to be uploaded.
### Multiuser Computers
Multiuser computers are typically in university computer labs, libraries, and organizations that enable job sharing. These computers include a core set of applications that are always available, in addition to many applications that can be installed and removed as necessary. Because these computers typically have a core set of applications, you can identify a narrow subset of computers to receive the inventory-collector package.
### AppStations and TaskStations
AppStations that run vertical applications are typically for marketing, claims and loan processing, and customer service. TaskStations are typically dedicated to running a single application in a location such as a manufacturing floor (as an entry terminal) or a call center. Because AppStations and TaskStations do not typically enable users to add or remove applications, you can identify a narrow subset of computers to receive the inventory-collector package.
### Kiosks
Kiosks are generally in public areas. These computers run unattended. They also generally run a single application by using a single-use account and automatic logon. Because these computers typically run a single application, you can identify a narrow subset of computers to receive the inventory-collector package.
## Related topics
[Creating an Inventory-Collector Package](creating-an-inventory-collector-package.md)
[Deploying an Inventory-Collector Package](deploying-an-inventory-collector-package.md)
 
 

BIN
windows/plan/images/branch.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 33 KiB

BIN
windows/plan/images/chromebook-fig1-googleadmin.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 92 KiB

BIN
windows/plan/images/dep-win8-e-act-addissue.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.0 KiB

BIN
windows/plan/images/dep-win8-e-act-addsolution.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.0 KiB

BIN
windows/plan/images/dep-win8-e-act-categorize.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 577 B

BIN
windows/plan/images/dep-win8-e-act-communityexample.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.8 KiB

BIN
windows/plan/images/dep-win8-e-act-createnewdcp.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 587 B

BIN
windows/plan/images/dep-win8-e-act-delete.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 568 B

BIN
windows/plan/images/dep-win8-e-act-deploymentstatus.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 628 B

BIN
windows/plan/images/dep-win8-e-act-doesnotwork64icon.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.2 KiB

BIN
windows/plan/images/dep-win8-e-act-doesnotworkicon.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.2 KiB

BIN
windows/plan/images/dep-win8-e-act-exportdcp.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 576 B

BIN
windows/plan/images/dep-win8-e-act-exportreportdata.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 630 B

BIN
windows/plan/images/dep-win8-e-act-filterdata.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.2 KiB

BIN
windows/plan/images/dep-win8-e-act-filterexampleallapps0activeissues.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 3.3 KiB

BIN
windows/plan/images/dep-win8-e-act-filterexampleallapps0issues.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 4.3 KiB

BIN
windows/plan/images/dep-win8-e-act-filterexampleallappswissues.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 3.9 KiB

BIN
windows/plan/images/dep-win8-e-act-filterexamplecategory.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 7.1 KiB

BIN
windows/plan/images/dep-win8-e-act-filterexampleforissueswsolutions.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 5.2 KiB

BIN
windows/plan/images/dep-win8-e-act-filterexampleforspecificsolutions.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 8.0 KiB

BIN
windows/plan/images/dep-win8-e-act-greenworks64icon.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 697 B

BIN
windows/plan/images/dep-win8-e-act-greenworksicon.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 694 B

BIN
windows/plan/images/dep-win8-e-act-help.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1008 B

BIN
windows/plan/images/dep-win8-e-act-home.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 609 B

BIN
windows/plan/images/dep-win8-e-act-info64icon.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.2 KiB

BIN
windows/plan/images/dep-win8-e-act-infoicon.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.2 KiB

BIN
windows/plan/images/dep-win8-e-act-minorissues64icon.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.1 KiB

BIN
windows/plan/images/dep-win8-e-act-minorissuesicon.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 910 B

BIN
windows/plan/images/dep-win8-e-act-moveupanddown.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 194 B

BIN
windows/plan/images/dep-win8-e-act-open.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 591 B

BIN
windows/plan/images/dep-win8-e-act-prioritize.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 615 B

BIN
windows/plan/images/dep-win8-e-act-reactivate-resolved-issue.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 372 B

BIN
windows/plan/images/dep-win8-e-act-refresh.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 608 B

BIN
windows/plan/images/dep-win8-e-act-riskassessment.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 596 B

BIN
windows/plan/images/dep-win8-e-act-save.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 632 B

BIN
windows/plan/images/dep-win8-e-act-savereport.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.0 KiB

BIN
windows/plan/images/dep-win8-e-act-sendandreceive.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.3 KiB

BIN
windows/plan/images/dep-win8-e-act-sendandreceiveicon.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 311 B

BIN
windows/plan/images/dep-win8-l-act-appcallosthroughiat.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 79 KiB

BIN
windows/plan/images/dep-win8-l-act-appredirectwithcompatfix.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 90 KiB

BIN
windows/plan/images/dep-win8-l-act-communityworkflowdiagram.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 147 KiB

BIN
windows/plan/images/dep-win8-l-act-compatadminflowchart.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 103 KiB

BIN
windows/plan/images/dep-win8-l-act-suaflowchart.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 101 KiB

BIN
windows/plan/images/dep-win8-l-act-suawizardflowchart.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 91 KiB

BIN
windows/plan/images/dep-win8-l-act-supportedtopologies.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 297 KiB

BIN
windows/plan/images/fig1-deferupgrades.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 78 KiB

BIN
windows/plan/images/fig2-deploymenttimeline.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 92 KiB

Some files were not shown because too many files have changed in this diff Show More