Professional Documents
Culture Documents
Abstract: This paper provides step-by-step information, guiding you through the major
scenarios employed while using the Microsoft® Application Compatibility Toolkit (ACT).
This white paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR
IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under
copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or
transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for
any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights
covering subject matter in this document. Except as expressly provided in any written license agreement from
Microsoft, the furnishing of this document does not give you any license to these patents, trademarks,
copyrights, or other intellectual property.
Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses,
logos, people, places and events depicted herein are fictitious, and no association with any real company,
organization, product, domain name, e-mail address, logo, person, place or event is intended or should be
inferred.
Microsoft, Win32, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft
Corporation in the United States or other countries or regions.
The names of actual companies and products mentioned herein may be the trademarks of their respective
owners.
Contents
Overview .................................................................................................................................. 4
How ACT Works .................................................................................................................. 4
Prerequisites for Scenario Walkthroughs ............................................................................ 5
ACT Scenarios ......................................................................................................................... 5
Scenario 1: Deploying a New Operating System ................................................................ 5
Phase 1: Collecting Your Inventory and Compatibility Data ........................................... 6
Phase 2: Analyzing Your Compatibility Data .................................................................. 9
Prioritizing Your Data .......................................................................................... 9
Categorizing Your Data .................................................................................... 10
Setting Your Assessment ................................................................................. 10
Filtering Your Data ............................................................................................ 11
Viewing a Report .............................................................................................. 12
Adding and Resolving Issues and Solutions ..................................................... 13
Phase 3: Testing and Mitigating Your Issues ............................................................... 13
Using the Standalone Setup Analysis Tool (SAT) ............................................ 13
Using the Standard User Analyzer (SUA) ......................................................... 14
Using the Compatibility Administrator ............................................................... 16
Scenario 2: Applying a Windows Update .......................................................................... 16
Phase 1: Collecting Your Inventory and Compatibility Data ......................................... 17
Phase 2: Analyzing Your Compatibility Data ................................................................ 20
Prioritizing Your Data ........................................................................................ 20
Categorizing Your Data .................................................................................... 20
Setting Your Severity ........................................................................................ 21
Filtering Your Data ............................................................................................ 22
Viewing a Report .............................................................................................. 22
Phase 3: Testing and Mitigating Your Issues ............................................................... 23
Using the Standard User Analyzer (SUA) ......................................................... 23
Using the Compatibility Administrator ............................................................... 24
Scenario 3: Upgrading Internet Explorer ........................................................................... 25
Phase 1: Collecting Your Inventory and Compatibility Data ......................................... 25
Phase 2: Analyzing Your Compatibility Data ................................................................ 28
Prioritizing Your Data ........................................................................................ 29
Categorizing Your Data .................................................................................... 29
Setting Your Assessment ................................................................................. 30
Filtering Your Data ............................................................................................ 30
Viewing a Report .............................................................................................. 31
Adding and Resolving Issues ........................................................................... 31
Phase 3: Testing and Mitigating Your Issues ............................................................... 32
Using the Internet Explorer Compatibility Test Tool .......................................... 32
ACT Guide: Step-By-Step Scenarios 4
Overview
The purpose of this white paper is to provide clear information about the core usage
scenarios for ACT. While following the walkthroughs presented in this guide, you will create
an inventory of currently installed applications, determine which applications might have
compatibility issues, organize the data so that they make sense, and create the solutions to
enable the problematic applications to run.
Configuring and Troubleshooting Your ACT Setup. Before using ACT 5.0 in your
organization, you must ensure that your organization can support the hardware, software,
permission, and database role requirements. You must then install and configure the tool.
Note For more information about software and hardware requirements, the
installation of ACT, the configuration of ACT, or any known ACT Setup
troubleshooting information, see the Microsoft ACT: Configuration and
Troubleshooting ACT Setup white paper, available for download from the Related
Resources section of the Microsoft Application Compatibility Toolkit 5.0 Download Web
page.
Phase 1: Collecting Data. Before analyzing your potential compatibility issues, you
must first collect your organization's inventory and the associated compatibility issues.
Note For more information about creating and deploying data collection packages,
see the Microsoft ACT: Phase 1 - Collecting Data white paper, available for
download from the Related Resources section of the Microsoft Application
Compatibility Toolkit 5.0 Download Web page.
Phase 2: Analyzing Issues. After collecting your inventory and associated compatibility
data, you can organize and analyze your issues. This includes categorizing, prioritizing,
setting your deployment status, and setting your application assessment to create
customized reports.
Note For more information about organizing, prioritizing, and analyzing your data,
see the Microsoft ACT: Phase 2 - Analyzing Issues white paper, available for
download from the Related Resources section of the Microsoft Application
Compatibility Toolkit 5.0 Download Web page.
Phase 3: Testing and Mitigating Issues. After analyzing your compatibility issue
reports, you can test your applications to determine if the specified compatibility issues are
actually problems within your organization. If you determine that the issues are valid, you
can create mitigation packages to fix the issues, by using the Compatibility Administrator.
You can also use the other developer tools, provided with ACT, including the Internet
Explorer Compatibility Tool, the Setup Analysis Tool, and the Standard User Analyzer tool,
to determine additional issues and possible mitigation strategies.
Note For more information about mitigating your issues using the Compatibility
Administrator, or how to use the developer tools, see the Microsoft ACT: Phase 3 –
Testing and Mitigating Issues white paper, available for download from the
Related Resources section of the Microsoft Application Compatibility Toolkit 5.0
Download Web page.
ACT Scenarios
There are three core usage scenarios for ACT 5.0 in an enterprise environment. These three
scenarios comprise assessing and mitigating compatibility issues with:
At the end of each walkthrough, you will have created an inventory of your organization's
hardware and software collection, organized the collected data so that it is customized
according to the needs of your organization, defined an application that might have a
compatibility issue, and created and deployed a mitigation package to fix that compatibility
issue.
Important Each walkthrough assumes that you have already installed and configured the
Application Compatibility Toolkit, as described in the Microsoft ACT: Configuration and
Troubleshooting ACT Setup white paper.
15. On the Analyze screen of your client computers, click Send and Receive.
16. In the Sign-in to Compatibility Data Exchange dialog box, enter the required Microsoft
.NET Passport details, and then click Sign In.
19. Return to the Analyze screen and review the updated issue data for your applications.
20. On the Collect screen, double-click the By Name pane.
The New <default_package_name> dialog box appears.
In this section, you will prioritize your application compatibility data, based on the importance
of the application to your organization. The available priority levels are:
Business Critical. The highest priority level. Business critical items are so important to
your organization that, unless you certify them, you cannot deploy the updated operating
system.
Important. The priority level for applications, Web sites, and updates that your
organization regularly uses but can continue to function without. You can choose to deploy
the updated operating system without requiring certification.
Nice to Have. The priority level for applications, Web sites, and updates that do not fall
into the previous two categories but should appear in your ACT compatibility reports. You
will deploy the updated operating system regardless of certification.
Unimportant. The priority level for applications, Web sites, and updates that is irrelevant
to your organization's daily operations. You can use this priority level to filter the
unimportant items from your reports.
Unspecified. The default priority level that is automatically assigned to all applications,
Web sites, and updates. Your organization can use this priority level to denote applications
that have not yet been reviewed for deployment.
In this section, you will create and will assign categories and subcategories to an application.
In this section, you will set your organization's assessment rating for an application. Your
assessment rating enables you to specify which applications might be problematic while
going through your organization's testing process. Your application assessments originate
from authoritative sources, such as Microsoft and the application vendor, from your own
testing, and from the Application Compatibility Toolkit (ACT) Community if you are a
member.
The following table describes the icons that appear in the My Assessment and Community
Assessment columns on the Analyze screen.
Icon Description
Icon Description
Denotes applications with minor issues or with issues that have known solutions.
Denotes applications with major issues, such as data loss or severely impaired
functionality.
Denotes applications that do not have any application assessment data. In this
Blank case, either the application does not match any information in the database or no
user has submitted an assessment.
The following table describes the icons that appear in the Vendor Assessment column on
the Analyze screen.
Icon Description
Denotes applications that work as they are but have not received logo
certification from Microsoft.
Denotes applications with minor issues or with issues that have known solutions.
In this section, you will create a single filter to display your compatibility data based on a
category, a subcategory, a priority, and an assessment rating. After filtering your data, you
can view the results as a customized report, tailored to your organizational requirements.
Viewing a Report
In this section, you will view an <operating_system> report screen and an <application
name> dialog box. The <operating_system> report screen enables you to view your data by
individual operating system, such as Windows XP or Windows Vista. The application details
dialog box enables you to view more deeply detailed data, such as the assessment rating,
known issues and solutions, application properties, or computer details.
In this section, you will use the standalone Setup Analysis Tool (SAT) to run your application
installations while monitoring the actions performed by each application’s installer. You can
use a virtual version of the SAT. There are two versions of the SAT, a standalone version
and a virtual version. The standalone version of SAT does not require a virtual environment
and can monitor any MSI-based installers and third-party installers. We recommend that you
use the standalone version and a test computer for monitoring a single, application-
installation file.
Note For more information about the virtual SAT tool, see the Using the Virtual Setup
Analysis Tool section of the Microsoft ACT: Phase 3 – Testing and Mitigating Issues
white paper, available for download from the Related Resources section of the Microsoft
Application Compatibility Toolkit 5.0 Download Web page.
The standalone SAT components and driver run on the following operating systems.
Windows 2000 Update Rollup 1 (RU1) for Service Pack 4 (SP4)
Windows XP with Service Pack 2 (SP2)
Windows Server 2003 with Service Pack 1 (SP1)
In this section, you will use the Standard User Analyzer (SUA) tool to test your applications
and to monitor API calls to detect potential compatibility issues due to the new User Account
Control (UAC) feature in Windows Vista.
Note For more information about SUA, see the Using the Standard User Analyzer section
of the Microsoft ACT: Phase 3 – Testing and Mitigating Issues white paper, available for
download from the Related Resources section of the Microsoft Application Compatibility
Toolkit 5.0 Download Web page.
Note For more information about using the Compatibility Administrator, including the other
available mitigation options, see the Using the Compatibility Administrator section of the
Microsoft ACT: Phase 3 – Testing and Mitigating Issues white paper, available for
download from the Related Resources section of the Microsoft Application Compatibility
Toolkit 5.0 Download Web page.
issues. You must deploy the associated DCP only to client computers running one of the
following operating systems.
12. By using the method determined in step 11, deploy the DCP to your specified client
computer's desktops.
Note We recommend that you collect your data from about 10,000 computers, if
you have a large number of available client computers in your organization.
13. Double-click the packaged DCP from each identified client computer's desktop.
The DCP runs on the client computer.
14. In the Quick Reports pane of the Application Compatibility Manager, click Analyze.
The Analyze screen appears.
15. On the Analyze screen of your client computers, click Send and Receive.
16. In the Sign-in to Compatibility Data Exchange dialog box, enter the required Microsoft
.NET Passport details, and then click Sign In.
19. Return to the Analyze screen and review the updated security data for your
applications.
20. On the Collect screen, double-click the By Name pane.
The New <default_package_name> dialog box appears.
In this section, you will prioritize your application compatibility data, based on the importance
of the application to your organization. The available priority levels are:
Business Critical. The highest priority level. Business critical items are so important to
your organization that, unless you certify them, you cannot deploy the updated operating
system.
Important. The priority level for applications, Web sites, and updates that your
organization regularly uses but can continue to function without. You can choose to deploy
the updated operating system without requiring certification.
Nice to Have. The priority level for applications, Web sites, and updates that do not fall
into the previous two categories but should appear in your ACT compatibility reports. You
will deploy the updated operating system regardless of certification.
Unimportant. The priority level for applications, Web sites, and updates that is irrelevant
to your organization's daily operations. You can use this priority level to filter the
unimportant items from your reports.
Unspecified. The default priority level that is automatically assigned to all applications,
Web sites, and updates. Your organization can use this priority level to denote applications
that have not yet been reviewed for deployment.
In this section, you will set your organization's severity rating for the Windows update. Your
severity rating enables you to specify which updates might be problematic while going
through your organization's testing process.
Important You can only set your severity rating for a Windows update, in the Updates
screen. You cannot set a severity rating for an application or Web site.
In this section, you will create a single filter to display your compatibility data based on a
category, a subcategory, a priority, and an assessment rating. After you filter your data, you
can view the results as a customized report, tailored to your organizational requirements.
Viewing a Report
In this section, you will view an Update Impact Reports - Applications report screen, an
application details dialog box, an Updates report screen and a security update dialog box.
3. Click the Intersecting Updates, Application Properties, and Computers tab for more
information about the application as it relates to that heading.
In this section, you will use the Standard User Analyzer (SUA) tool to test your applications
and monitor API calls to detect potential compatibility issues due to the new User Account
Control (UAC) feature in Windows Vista.
Note For more information about SUA, see the Using the Standard User Analyzer section
of the Microsoft ACT: Phase 3 – Testing and Mitigating Issues white paper, available for
download from the Related Resources section of the Microsoft Application Compatibility
Toolkit 5.0 Download Web page.
Note For more information about using the Compatibility Administrator, including the other
mitigation options available, see the Using the Compatibility Administrator section of the
Microsoft ACT: Phase 3 – Testing and Mitigating Issues white paper, available for
download from the Related Resources section of the Microsoft Application Compatibility
Toolkit 5.0 Download Web page.
2. Right-click the New Database(n) [Untitled_n] entry, click Rename, type Custom
Database 2, and then press ENTER.
3. Right-click the Custom Database Compatibility Mode database, click Create new, and
then click Compatibility Mode.
The Create a Custom Compatibility Mode wizard appears.
4. Type Compatibility Mode Example into the Name of the compatibility mode box.
5. Click AlwaysActiveMenus, and then click >.
6. Click CorrectBitmapHeader, click >, and then click OK.
7. On the File menu, click Save As.
8. Keep the default location, type ACMCompatMode into the File name box, and then
click Save.
9. At the command prompt, change directories to %Program Files%\Microsoft Application
Compatibility Toolkit 5\Application Compatibility Manager directory.
10. Type sdbinst.exe ACMCompatMode.sdb.
The compatibility mode is applied to your local computer.
Windows Vista
Windows XP with Service Pack 2 (SP2)
Windows Server 2003 with Service Pack 1 (SP1)
Important You must have Internet Explorer 7 installed on any client computer to
which you will deploy the DCP.
7. In the When to monitor application usage area, keep the default options, but change
the Duration to 10 Minutes.
8. In the Output Location box, keep your default value, previously specified in the ACT
Configuration Wizard.
9. On the File menu, click Save and Create Package.
10. Save the compiled DCP to your desktop.
Note The Application Compatibility Manager saves the DCP as an executable
(.exe) file.
11. Determine which method you will use to deploy your DCP. These methods include
Microsoft Systems Management Server 2003 (SMS 2003), Group Policy Installation
Software, logon scripts, or any customized deployment method already used within your
organization.
Notes The suggested deployment methods might require that you repackage the
DCP, which is an .exe file format, into an .msi file format. For more information about
how to repackage your DCPs, see How to create a Setup package by using Visual Studio
.NET, How to publish non-MSI programs with .zap files, and Using the WiX Toolset to
Integrate Setup into Your Development Process .
For detailed deployment methodology, including determining where and when to
deploy the DCP, see the Microsoft ACT: Phase 1 – Collecting Data white paper.
12. By using the method determined in step 11, deploy the DCP to your specified client
computer's desktops.
Note We recommend that you deploy the DCP to a controlled test environment, to
minimize the number of computers to which you must deploy and increase the yield
of the returned data.
13. Double-click the packaged DCP from each identified client computer's desktop.
14. The DCP runs on the client computer.
15. In the Quick Reports pane of the Application Compatibility Manager, click Analyze.
The Analyze screen appears.
16. On the Analyze screen of your client computers, click Send and Receive.
17. In the Sign-in to Compatibility Data Exchange dialog box, enter the required Microsoft
.NET Passport details, and then click Sign In.
The dialog box changes to display the applications that will send and will receive
information from Microsoft during the synchronization process.
Important You can disable specific applications from the synchronization
process, so that you do not share the related issue data with Microsoft or the ACT
Community.
21. Return to the Analyze screen and review the updated software and hardware data.
22. On the Collect screen, double-click the By Name pane.
The New <default_package_name> dialog box appears.
23. In the Package Name box, type IE_Upgrade.
24. In the Evaluate compatibility when area, click Updating to a new version of Internet
Explorer.
Note This evaluator option includes the Inventory Collector and the IECE, by
default.
25. Keep the default values in the When to monitor application usage area and in the
Output Location box.
26. On the File menu, click Save and Create Package.
27. Save the compiled DCP to your desktop.
28. Repeat steps 11-14 to deploy your DCP.
29. On the client computer, open an Internet Explorer 7 browser window.
30. Visit the Microsoft Worldwide Web site, click Europe from the Web Sites drop-down list,
and then click Go.
31. Visit the Microsoft Volume Licensing Sites Worldwide Web site, click United States from the
Web Sites drop-down list, and then click Go.
32. Visit the Games for Windows Web site.
33. Close the Internet Explorer 7 browser window.
In this section, you will prioritize your Web sites, based on the importance of the site to your
organization. The available priority levels are:
Business Critical. The highest priority level. Business critical items are so important to
your organization that, unless you certify them, you cannot deploy the updated operating
system.
Important. The priority level for applications, Web sites, and updates that your
organization regularly uses but can continue to function without. You can choose to
deploy the updated operating system without requiring certification.
Nice to Have. The priority level for applications, Web sites, and updates that do not fall
into the previous two categories but should appear in your ACT compatibility reports.
You will deploy the updated operating system regardless of certification.
Unimportant. The priority level for applications, Web sites, and updates that is irrelevant
to your organization's daily operations. You can use this priority level to filter the
unimportant items from your reports.
Unspecified. The default priority level that is automatically assigned to all applications,
Web sites, and updates. Your organization can use this priority level to denote
applications that have not yet been reviewed for deployment.
In this section, you will set your organization's assessment rating for a Web site. Your
assessment rating enables you to specify which sites might be problematic while going
through your organization's testing process.
The following table describes the icons that appear in the My Assessment column on the
Analyze screen.
Icon Description
Denotes Web sites with minor issues or with issues that have known solutions.
Denotes Web sites with major issues, such as data loss or severely impaired
functionality.
Denotes Web sites that do not have any application assessment data. In this
Blank case, either the site does not match any information in the database or no user
has submitted an assessment.
In this section, you will create a single filter to display your compatibility data based on a
category, a subcategory, a priority, and an assessment rating. After filtering your data, you
can view the results as a customized report, tailored to your organizational requirements.
Viewing a Report
In this section, you will view an Internet Explorer 7 – Web Site Report screen and a Web
site details dialog box.
To view an Internet Explorer 7 – Web Site Report and a Web site details dialog box
1. In the Quick Reports pane of the Analyze screen, click Web Sites below the Internet
Explorer 7 heading.
The Internet Explorer 7 – Web Site Report screen appears.
2. Double-click http://www.microsoft.com/worldwide/.
The http://www.microsoft.com/worldwide/ dialog box appears, displaying the Web
site issues.
In this section, you will add a new compatibility issue and a new solution, and then you will
resolve the issue for your organization.
In this section, you will use the Internet Explorer Compatibility Test Tool to collect, in real-
time, the potential Web site and Web application issues that might occur due to running Web
sites and Web applications in Internet Explorer 7.
Note For more information about the Internet Explorer Compatibility Test Tool, see
the Microsoft ACT: Phase 3 – Testing and Mitigating Issues white paper and the
Internet Explorer Compatibility Test Tool topics in the ACT online Help system.
The Internet Explorer Compatibility Test Tool runs on the following operating systems.
Windows XP
Windows Server 2003
Windows Vista