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

Removed content, updated YAML, redirected

Browse Source
This commit is contained in:
LizRoss
2016-07-20 09:55:48 -07:00
parent 2662c9434b
commit 6aba6dde50
13 changed files with 28 additions and 1027 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1,85 +1,5 @@
---
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: plan
ms.pagetype: appcompat
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)
 
 
redirect_url: https://technet.microsoft.com/en-us/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-analytics.md
---

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

@ -1,68 +1,5 @@
---
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: plan
ms.pagetype: appcompat
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)
 
 
redirect_url: https://technet.microsoft.com/en-us/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-analytics.md
---

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

@ -1,61 +1,5 @@
---
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: plan
ms.pagetype: appcompat
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)
 
 
redirect_url: https://technet.microsoft.com/en-us/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-analytics.md
---

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

@ -1,76 +1,5 @@
---
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: plan
ms.pagetype: appcompat
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 *<domain>*\\*<computer>*$ 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)
 
 
redirect_url: https://technet.microsoft.com/en-us/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-analytics.md
---

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

@ -1,60 +1,5 @@
---
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: plan
ms.pagetype: appcompat
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)
 
 
redirect_url: https://technet.microsoft.com/en-us/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-analytics.md
---

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

@ -1,90 +1,5 @@
---
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: plan
ms.pagetype: appcompat
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)
 
 
redirect_url: https://technet.microsoft.com/en-us/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-analytics.md
---

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

@ -1,58 +1,5 @@
---
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: plan
ms.pagetype: appcompat
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)
 
 
redirect_url: https://technet.microsoft.com/en-us/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-analytics.md
---

143
windows/plan/deploying-an-inventory-collector-package.md
View File

@ -1,142 +1,5 @@
---
title: Deploying an Inventory-Collector Package (Windows 10)
ms.assetid: 8726ff71-0d17-4449-bdb7-66957ae51c62
description:
ms.prod: w10
ms.mktglfcycl: plan
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)
 
 
description: How to deploy an inventory-collector package to your destination computers.
redirect_url: https://technet.microsoft.com/en-us/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-analytics.md
---

105
windows/plan/identifying-computers-for-inventory-collection.md
View File

@ -1,104 +1,5 @@
---
title: Identifying Computers for Inventory Collection (Windows 10)
ms.assetid: f5bf2d89-fff2-4960-a153-dc1146b442fb
description:
ms.prod: w10
ms.mktglfcycl: plan
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
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)
## <a href="" id="bmk-managedunmanaged"></a>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.
## <a href="" id="bmk-rolebasedapplications"></a>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.
## <a href="" id="bmk-softwaredistribution"></a>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.
## <a href="" id="bmk-geographicdistribution"></a>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.
## <a href="" id="bmk-computertypes"></a>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)
 
 
description: 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.
redirect_url: https://technet.microsoft.com/en-us/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-analytics.md
---

69
windows/plan/software-requirements-for-rap.md
View File

@ -1,70 +1,5 @@
---
title: Software Requirements for RAP (Windows 10)
description: The runtime-analysis package (RAP) has the following software requirements.
ms.assetid: 0163ce70-f5ba-400c-bdd5-a25511aac91f
ms.prod: w10
ms.mktglfcycl: plan
ms.pagetype: appcompat
ms.sitesec: library
author: TrudyHa
---
# Software Requirements for RAP
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
The runtime-analysis package (RAP) has the following software requirements.
## Compatibility Monitor Supported Operating Systems
The Microsoft Compatibility Monitor tool is included in the runtime-analysis package. You can use the Compatibility Monitor on the following operating systems:
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
## SUA Tool and Compatibility Administrator Supported Operating Systems
The Standard User Analyzer (SUA) tool and wizard and the Compatibility Administrator tool are included in the runtime-analysis package. You can use the tools on the following operating systems:
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
## Related topics
[What's New in Act 6.1](whats-new-in-act-60.md)
[Software Requirements for ACT](software-requirements-for-act.md)
 
 
redirect_url: https://technet.microsoft.com/en-us/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-analytics.md
---

75
windows/plan/taking-inventory-of-your-organization.md
View File

@ -1,76 +1,5 @@
---
title: Taking Inventory of Your Organization (Windows 10)
description: This section provides information about how to use the Application Compatibility Toolkit (ACT) to identify applications and devices that are installed in your organization.
ms.assetid: d52f138d-c6b2-4ab1-bb38-5b036311a51d
ms.prod: w10
ms.mktglfcycl: plan
ms.pagetype: appcompat
ms.sitesec: library
author: TrudyHa
---
# Taking Inventory of Your Organization
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
This section provides information about how to use the Application Compatibility Toolkit (ACT) to identify applications and devices that are installed 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>[Identifying Computers for Inventory Collection](identifying-computers-for-inventory-collection.md)</p></td>
<td align="left"><p>An inventory-collector package gathers inventory data from the computers on which it is installed. This data includes the following:</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Creating an Inventory-Collector Package](creating-an-inventory-collector-package.md)</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Deploying an Inventory-Collector Package](deploying-an-inventory-collector-package.md)</p></td>
<td align="left"><p>You can use the following methods to deploy an inventory-collector package to the destination computers:</p></td>
</tr>
</tbody>
</table>
 
## Related topics
[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)
[Fixing Compatibility Issues](fixing-compatibility-issues.md)
 
 
redirect_url: https://technet.microsoft.com/en-us/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-analytics.md
---

83
windows/plan/testing-compatibility-on-the-target-platform.md
View File

@ -1,84 +1,5 @@
---
title: Testing Compatibility on the Target Platform (Windows 10)
description: This section provides information about setting up a test environment for compatibility testing, and about creating and deploying runtime-analysis packages to the test environment.
ms.assetid: 8f3e9d58-37c2-41ea-a216-32712baf6cf4
ms.prod: w10
ms.mktglfcycl: plan
ms.pagetype: appcompat
ms.sitesec: library
author: TrudyHa
---
# Testing Compatibility on the Target Platform
**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 a test environment for compatibility testing, and about creating and deploying runtime-analysis packages to the test environment.
## 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 Which Applications to Test](deciding-which-applications-to-test.md)</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Creating an Enterprise Environment for Compatibility Testing](creating-an-enterprise-environment-for-compatibility-testing.md)</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Creating a Runtime-Analysis Package](creating-a-runtime-analysis-package.md)</p></td>
<td align="left"><p>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.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Deploying a Runtime-Analysis Package](deploying-a-runtime-analysis-package.md)</p></td>
<td align="left"><p>When you deploy a runtime-analysis package, you are deploying it to your test environment for compatibility testing.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Compatibility Monitor User's Guide](compatibility-monitor-users-guide.md)</p></td>
<td align="left"><p>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.</p></td>
</tr>
</tbody>
</table>
 
## Related topics
[Taking Inventory of Your Organization](taking-inventory-of-your-organization.md)
[Managing Your Data-Collection Packages](managing-your-data-collection-packages.md)
[Analyzing Your Compatibility Data](analyzing-your-compatibility-data.md)
[Fixing Compatibility Issues](fixing-compatibility-issues.md)
 
 
redirect_url: https://technet.microsoft.com/en-us/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-analytics.md
---

89
windows/plan/using-act.md
View File

@ -1,90 +1,5 @@
---
title: Using ACT (Windows 10)
description: This section describes how to use the Application Compatibility Toolkit (ACT) in your organization.
ms.assetid: e6a68f44-7503-450d-a000-a04fbb93a146
ms.prod: w10
ms.mktglfcycl: plan
ms.pagetype: appcompat
ms.sitesec: library
author: TrudyHa
---
# Using ACT
**Applies to**
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2012
- Windows Server 2008 R2
This section describes how to use 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>[Taking Inventory of Your Organization](taking-inventory-of-your-organization.md)</p></td>
<td align="left"><p>This section provides information about how to use the Application Compatibility Toolkit (ACT) to identify applications and devices that are installed in your organization.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Testing Compatibility on the Target Platform](testing-compatibility-on-the-target-platform.md)</p></td>
<td align="left"><p>This section provides information about setting up a test environment for compatibility testing, and about creating and deploying runtime-analysis packages to the test environment.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Managing Your Data-Collection Packages](managing-your-data-collection-packages.md)</p></td>
<td align="left"><p>This section provides information about using Application Compatibility Manager (ACM) to manage your data-collection packages. Data-collection packages include inventory-collector packages and runtime-analysis packages. The following procedures apply to both package types.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Analyzing Your Compatibility Data](analyzing-your-compatibility-data.md)</p></td>
<td align="left"><p>This section provides information about viewing and working with your compatibility data in Application Compatibility Manager (ACM).</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[Fixing Compatibility Issues](fixing-compatibility-issues.md)</p></td>
<td align="left"><p>This section provides step-by-step instructions and describes development tools that you can use to help fix your compatibility issues.</p></td>
</tr>
</tbody>
</table>
 
## Related topics
[Welcome to ACT](welcome-to-act.md)
[Configuring ACT](configuring-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)
 
 
redirect_url: https://technet.microsoft.com/en-us/itpro/windows/deploy/manage-windows-upgrades-with-upgrade-analytics.md
---