ACT Step by Step

8/7/2019 ACT Step by Step

1/33

ACT Guide: Step-By-Step Scenarios

Last Updated: May 22, 2007Applies to: IT Professionals

Abstract: This paper provides step-by-step information, guiding you through the majorscenarios employed while using the Microsoft Application Compatibility Toolkit (ACT).

This information applies to the:

Windows Vista operating system

Microsoft Windows Server 2003 operating systems

Microsoft Windows XP operating systems

Microsoft Windows 2000 operating system


2/33

DisclaimerThe information contained in this document represents the current view of Microsoft Corporation on the issues

discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it

should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the

accuracy of any information presented after the date of publication.

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.

2007 Microsoft Corporation. All rights reserved.

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.


3/33

Contents

Overview .................................................................................................................................. 4How ACT Works .................................................................................................................. 4Prerequisites for Scenario Walkthroughs ............................................................................ 5

ACT Scenarios ......................................................................................................................... 5Scenario 1: Deploying a New Operating System ................................................................ 5

Phase 1: Collecting Your Inventory and Compatibility Data ........................................... 6Phase 2: Analyzing Your Compatibility Data .................................................................. 9

Prioritizing Your Data .......................................................................................... 9Categorizing Your Data .................................................................................... 10Setting Your Assessment ................................................................................. 10Filtering Your Data ............................................................................................ 11Viewing a Report .............................................................................................. 12Adding and Resolving Issues and Solutions ..................................................... 13

Phase 3: Testing and Mitigating Your Issues ............................................................... 13Using the Standalone Setup Analysis Tool (SAT) ............................................ 13Using the Standard User Analyzer (SUA) ......................................................... 14Using the Compatibility Administrator ............................................................... 16

Scenario 2: Applying a Windows Update .......................................................................... 16Phase 1: Collecting Your Inventory and Compatibility Data ......................................... 17Phase 2: Analyzing Your Compatibility Data ................................................................ 20

Prioritizing Your Data ........................................................................................ 20Categorizing Your Data .................................................................................... 20Setting Your Severity ........................................................................................ 21Filtering Your Data ............................................................................................ 22Viewing a Report .............................................................................................. 22

Phase 3: Testing and Mitigating Your Issues ............................................................... 23Using the Standard User Analyzer (SUA) ......................................................... 23Using the Compatibility Administrator ............................................................... 24

Scenario 3: Upgrading Internet Explorer ........................................................................... 25Phase 1: Collecting Your Inventory and Compatibility Data ......................................... 25Phase 2: Analyzing Your Compatibility Data ................................................................ 28

Prioritizing Your Data ........................................................................................ 29Categorizing Your Data .................................................................................... 29Setting Your Assessment ................................................................................. 30Filtering Your Data ............................................................................................ 30Viewing a Report .............................................................................................. 31Adding and Resolving Issues ........................................................................... 31

Phase 3: Testing and Mitigating Your Issues ............................................................... 32Using the Internet Explorer Compatibility Test Tool .......................................... 32


4/33

ACT Guide: Step-By-Step Scenarios 4


OverviewThe purpose of this white paper is to provide clear information about the core usagescenarios for ACT. While following the walkthroughs presented in this guide, you will create

an inventory of currently installed applications, determine which applications might havecompatibility issues, organize the data so that they make sense, and create the solutions toenable the problematic applications to run.

How ACT Works

ACT 5.0 provides a way for you to create an inventory of your organization, including yourinstalled applications, computers, and devices. It also enables you to collect compatibilitydata, to determine the impact of that data in your organization, and, finally, to createmitigation packages to fix the compatibility issues, when possible. There are four steps foreffectively using ACT in your organization. The four steps are:

Configuring and Troubleshooting Your ACT Setup. Before using ACT 5.0 in yourorganization, 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, theinstallation of ACT, the configuration of ACT, or any known ACT Setuptroubleshooting information, see the Microsoft ACT: Configuration and

Troubleshooting ACT Setup white paper, available for download from the RelatedResources section of theMicrosoft Application Compatibility Toolkit 5.0 DownloadWebpage.

Phase 1: Collecting Data. Before analyzing your potential compatibility issues, youmust 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 fordownload from the Related Resources section of theMicrosoft ApplicationCompatibility Toolkit 5.0 DownloadWeb page.

Phase 2: Analyzing Issues. After collecting your inventory and associated compatibilitydata, you can organize and analyze your issues. This includes categorizing, prioritizing,setting your deployment status, and setting your application assessment to createcustomized reports.

Note For more information about organizing, prioritizing, and analyzing your data,

see the Microsoft ACT: Phase 2 - Analyzing Issues white paper, available fordownload from the Related Resources section of theMicrosoft Application

Compatibility Toolkit 5.0 DownloadWeb page.

Phase 3: Testing and Mitigating Issues. After analyzing your compatibility issuereports, you can test your applications to determine if the specified compatibility issues areactually problems within your organization. If you determine that the issues are valid, youcan 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 InternetExplorer 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 theMicrosoft Application Compatibility Toolkit 5.0DownloadWeb page.
http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101


5/33



Prerequisites for Scenario Walkthroughs

To complete the walkthroughs described in this white paper, you must ensure that you:

Are an Administrator on the computer.

Have Internet access.

Have a valid .NET Passport account.

Have an environment of client computers to which you can deploy the data collectionpackages, including providing the required configuration, permissions, and database rolesfor each user account.

Note For specific configuration and permission information, see the Microsoft

ACT: Configuration and Troubleshooting ACT Setup white paper.

Install any application, including Internet Explorer 7 (if you are using the InternetExplorer-related data collection package, for which you require compatibility data on yourspecified client computers).

Install and configure the Application Compatibility Toolkit 5.0, based on the informationin the Microsoft ACT: Configuration and Troubleshooting ACT Setup white paper.

Plan your deployment strategy, including where and how to deploy the data collectionpackages.

ACT ScenariosThere are three core usage scenarios for ACT 5.0 in an enterprise environment. These threescenarios comprise assessing and mitigating compatibility issues with:

Deploying a new operating system.

Deploying a Windows update.

Upgrading the version of Internet Explorer.This section presents you with step-by-step walkthroughs for each of the scenarios listedabove, including common organizational, analytical, and mitigation procedures.

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 customizedaccording 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 compatibilityissue.

Important Each walkthrough assumes that you have already installed and configured theApplication Compatibility Toolkit, as described in the Microsoft ACT: Configuration andTroubleshooting ACT Setup white paper.

Scenario 1: Deploying a New Operating System

This scenario covers an organization that is planning to deploy a new operating system intoits environment, but first requires a more detailed assessment of the potential compatibility

issues. You must deploy the associated DCP only to client computers running one of thefollowing operating systems.

Windows XP with Service Pack 2 (SP2)

Windows Vista

Windows Server 2003 with Service Pack 1 (SP1)

Windows 2000 with Service Pack 4 (SP4) and Update Rollup 1


6/33



Phase 1: Collecting Your Inventory and Compatibility Data

In this phase, you will create a new data collection package that will collect your computer,device, installed applications, and associated compatibility issues.

To collect your inventory and compatibility data

1. On the taskbar, click Start, point to All Programs, point to Microsoft ApplicationCompatibility Toolkit 5.0, and then click Application Compatibility Manager.

2. On the Collect screen, double-click the By Name pane.

The New dialog box appears.

3. In the PackageName box, type Inventory_Collection.

4. In the Evaluate compatibility when area, click Deploying a new Operating System orService Pack.

5. Click Advanced.

The Advanced Settings dialog box appears.

6. Clear the User Account Control Compatibility Evaluator and Windows VistaCompatibility Evaluators check boxes, and then click OK.

The Advanced Setting dialog box closes.

7. In the When to monitor application usage area, keep the default options, but changethe Duration to 10 Minutes.

8. In the Output Location box, keep your default value, previously specified in the ACTConfiguration 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 InstallationSoftware, logon scripts, or any customized deployment method already used within yourorganization.

Note 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 abouthow to repackage your DCPs, seeHow to create a Setup package by using Visual Studio.NET,How to publish non-MSI programs with .zap files, andUsing the WiX Toolset toIntegrate Setup into Your Development Process.

For detailed deployment methodology, including determining where and when todeploy 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 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.
http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90668http://go.microsoft.com/fwlink/?LinkId=90668http://go.microsoft.com/fwlink/?LinkId=90668http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90668http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90667


7/33



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.

The Confirm dialog box appears.

17. Click View the specific applications to be shared with the ACT Community .

The dialog box changes to display the applications that will send and will receiveinformation from Microsoft during the synchronization process.


8/33



Important You can disable specific applications from the synchronization

process, so that you do not share the related issue data with Microsoft or the ACTCommunity.

18. Click Send Data.

Data synchronization occurs between your computer and the Microsoft Compatibility

Exchange.

19. Return to the Analyze screen and review the updated issue data for your applications.




9/33



21. In the PackageName box, type OS_Deployment.

22. In the Evaluate compatibility when area, click Deploying a new Operating System orService Pack.

Note This evaluator option includes the Inventory Collector, the UACCE, and theWVCE, by default.

23. Keep the default values in the When to monitor application usage area and in theOutput Location box.



26. Repeat steps 11-19 to deploy your DCP and to synchronize your data.

Phase 2: Analyzing Your Compatibility Data

In this phase, you will organize your data by using categories and subcategories, priorities,

and assessment ratings. After organizing your data, you will be able to filter yourcompatibility data, to determine which applications might have compatibility issues, and toview the information in customized reports.

Prioritizing Your Data

In this section, you will prioritize your application compatibility data, based on the importanceof the application to your organization. The available priority levels are:

Business Critical. The highest priority level. Business critical items are so important toyour organization that, unless you certify them, you cannot deploy the updated operatingsystem.

Important. The priority level for applications, Web sites, and updates that yourorganization regularly uses but can continue to function without. You can choose to deploythe updated operating system without requiring certification.

Nice to Have. The priority level for applications, Web sites, and updates that do not fallinto the previous two categories but should appear in your ACT compatibility reports. Youwill deploy the updated operating system regardless of certification.

Unimportant. The priority level for applications, Web sites, and updates that is irrelevantto your organization's daily operations. You can use this priority level to filter theunimportant 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 applicationsthat have not yet been reviewed for deployment.

To prioritize your applications

1. In the Quick Reports pane of the Analyze screen, click Applications below theWindows Vista Reports heading.

The Windows Vista Application Report screen appears.

2. Click Microsoft Application Compatibility Toolkit 5.0 in the Windows Vista

Application Report screen.

3. On the Actions menu, click Priority.

The Assign Priority dialog box appears.


10/33



4. Click Priority 1 Business Critical, and then click OK.

Categorizing Your Data

In this section, you will create and will assign categories and subcategories to an application.

To create a new category and subcategory

1. In the Windows Vista - Application Report screen, click Microsoft Application

Compatibility Toolkit 5.0.

2. On the Actions menu, click Categories.

The Assign Categories dialog box appears.

3. Click Master Category List.

The Master Category List dialog box appears.

4. In the Categories area, click Add, type Location, and then press ENTER.

5. In the Subcategories area, click Add, type United States, and then press ENTER.

6. In the Subcategories area, click Add, type Europe, and then press ENTER.

7. Click OK.

The Master Category List dialog box closes.

8. Click OK.

The Assign Categories dialog box closes.

To assign a category and a subcategory

1. In the Windows Vista - Application Report screen, click Microsoft ApplicationCompatibility Toolkit 5.0.



3. Select the United States check box, and then click OK.

Important Although United States is a subcategory, when you select the checkbox, it automatically selects the parent category. You must assign a subcategory if

you assign a category.


Setting Your Assessment

In this section, you will set your organization's assessment rating for an application. Yourassessment rating enables you to specify which applications might be problematic whilegoing through your organization's testing process. Your application assessments originate

from authoritative sources, such as Microsoft and the application vendor, from your owntesting, and from the Application Compatibility Toolkit (ACT) Community if you are amember.

The following table describes the icons that appear in the My Assessment and CommunityAssessment columns on the Analyze screen.

Icon Description

Denotes applications that work properly and function as expected.


11/33



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.

BlankDenotes applications that do not have any application assessment data. In thiscase, either the application does not match any information in the database or nouser has submitted an assessment.

The following table describes the icons that appear in the Vendor Assessment column onthe Analyze screen.

Icon Description

Denotes that the application received logo certification.

Denotes applications that work as they are but have not received logocertification from Microsoft.

Denotes applications with minor issues or with issues that have known solutions.

To set your assessment rating

1. In the Windows Vista - Application Report screen, click Microsoft ApplicationCompatibility Toolkit 5.0.

2. On the Actions menu, click Assessment.The Set Assessment dialog box appears.

3. Click Works, and then click OK.

Filtering Your Data

In this section, you will create a single filter to display your compatibility data based on acategory, a subcategory, a priority, and an assessment rating. After filtering your data, youcan view the results as a customized report, tailored to your organizational requirements.


12/33



To create a custom filter

1. In the Windows Vista - Application Report screen, click Toggle Filter.

2. In the Field list, click Priority.

3. In the Operator list, click Equals.

4. In the Value box, type Priority 1 - Business Critical.

5. Press the TAB key to create a new query row.

6. In the And/Or list, click And.

7. In the Field list, click My Assessment.


9. In the Value box, click Works.



12. In the Field list, click Categories (+).

13. In the Operator list, click Exists.


Important Do not enter text into the Value box.


16. In the Field list, click Category Name.


18. In the Value box, type Location.



21. In the Field list, click Subcategory Name.


23. In the Value box, type United States.

24. Right-click anywhere in the row, and then click Execute.

The filter sorts your data to display the Microsoft Application Compatibility Toolkit 5.0because it is the only application that fulfills all the filter criteria.

Viewing a Report

In this section, you will view an report screen and an dialog box. The report screen enables you to view your data by

individual operating system, such as Windows XP or Windows Vista. The application detailsdialog box enables you to view more deeply detailed data, such as the assessment rating,known issues and solutions, application properties, or computer details.

To view an Application report and an application details dialog

box1. In the Quick Reports pane of the Analyze screen, click Applications below the

Windows Vista Reports heading

The Windows Vista Applications Report screen appears.


13/33



2. Double-click Microsoft Application Compatibility Toolkit 5.0.

The Microsoft Application Compatibility Toolkit 5.0 dialog box appears, displayingthe assessment details for the application.

3. Click the Issues, Application Properties, and Computers tab for more informationabout the application as it relates to that heading.

Adding and Resolving Issues and Solutions

In this section, you will add a new compatibility issue and a new solution, and then you willresolve the issue for your organization.

To add and resolve a compatibility issue

1. In the Microsoft Application Compatibility Toolkit 5.0 dialog box, click Add Issue onthe Actions menu.

The Microsoft Application Compatibility Toolkit 5.0 New Issue dialog box appears.

2. In the Title box, type Example_Issue.

3. In the Priority list, click Priority 3 Nice to Fix.

4. In the Severity list, click Severity 3

Minor functionality loss.5. In the Symptom list, click Application has impaired functionality.

6. In the Cause list, click Application requires a deprecated component.

7. In the Affected Operating Systems box, keep the default value (Windows Vista)

selected.

8. In the Issue Description box, type This is the issue description text.

9. On the File menu, click Save.

10. On the Actions menu in the Microsoft Application Compatibility Toolkit 5.0 Example_Issue dialog box, click Add Solution.

The Microsoft Application Compatibility Toolkit 5.0 Add Solution dialog boxappears.

11. In the Title box, type Example_Solution.

12. In the Solution Type box, click Application configuration change.

13. In the Solution Details box, type This is the solution details text.

14. Click Save.

15. On the Actions menu in the Microsoft Application Compatibility Toolkit 5.0 Example_Issue dialog box, click Resolve.

The issue is resolved, changing the red x to a green check mark.

Phase 3: Testing and Mitigating Your Issues

In this phase, you will test and will mitigate your issues by using the Setup Analysis Tool(SAT), the Standard User Analyzer (SUA), and the Compatibility Administrator.

Using the Standalone Setup Analysis Tool (SAT)

In this section, you will use the standalone Setup Analysis Tool (SAT) to run your applicationinstallations while monitoring the actions performed by each applications installer. You can

use a virtual version of the SAT. There are two versions of the SAT, a standalone versionand 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


14/33



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 Toolsection of the Microsoft ACT: Phase 3 Testing and Mitigating Issueswhite paper, available for download from the Related Resources section of theMicrosoft

Application Compatibility Toolkit 5.0 DownloadWeb page.The standalone SAT components and driver run on the following operating systems.

Windows 2000 Update Rollup 1 (RU1) for Service Pack 4 (SP4)



To install and use the SAT1. Open a Command Prompt window, change directories to the \%Program

Files%\Microsoft Application Compatibility Toolkit 5\Setup Analysis Tool directory, andthen type satinstall.exe.

The Setup Analysis Tool Installation Wizard appears.

2. Click Next.The wizard displays the SAT Installation Modes.

3. Click the Standalone SAT option, and then click Next.

The wizard displays the SAT Installation Actions.

4. Click the Install option, and then click Next.

The SAT collects information from your computer and prepares to start installation.

5. Click Next to begin the SAT installation process.

The Setup Analysis Tool appears next to the Setup Analysis Tool Installation Wizard.

6. Click Next in the Setup Analysis Tool Installation Wizard, and then click Finish.

The Setup Analysis Tool Installation Wizard closes.

7. In the Setup Analysis Tool, type c:\setup.exe (where c:\ is your primary system drive) inthe Type the setup file location box.

8. Clear the Shut down the computer after the SAT completes its processes check box

so that your computer does not shut down after the SAT completes its processes.

9. Select the Prevent setup programs from restarting the computer check box toprevent the setup programs from restarting the computer.

10. Type the location of your ACT Log Processing share, which should be a local folder ifyou performed a default installation of the ACT.

11. Click Run.

The SAT runs your command and begins to profile the specified setup programs to

determine what application installation issues might exist with Windows Vista.

Using the Standard User Analyzer (SUA)

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 AccountControl (UAC) feature in Windows Vista.
http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101http://go.microsoft.com/fwlink/?LinkID=82101


15/33



Note For more information about SUA, see the Using the Standard User Analyzersection

of the Microsoft ACT: Phase 3 Testing and Mitigating Issues white paper, available for

download from the Related Resources section of theMicrosoft Application CompatibilityToolkit 5.0 DownloadWeb page.

To test an application by using SUA

1. Log on the computer with a Standard User account.

2. On the taskbar, click Start, and then click Run.

3. Type calc.exe, and then press ENTER.

The Microsoft Calculator appears in Standard mode.

4. On the View menu, click Scientific.

The Microsoft Calculator changes to Scientific mode.

5. Click Close.

6. Reopen the calculator application, noting that the calculator has returned to Standard

mode and that your settings are not saved.

7. Log off the computer.

8. Log on the computer with an Administrator account.






12. Click Close.

13. Reopen the calculator application, noting that the calculator remains in Scientific mode

and that your settings are saved. Because the Microsoft Calculator behaves differentlyfor Standard Users and Administrators, we can conclude that a UAC issue exists.

Note The calculator issue described for this example is no longer an issue in

Windows Vista.

14. Click Start, point to All Programs, point to Microsoft Application CompatibilityToolkit 5.0, point to Developer and Tester Tools, and then click Standard UserAnalyzer.

15. In the Target Application box, type C:\Windows\System32\calc.exe.

16. In the Symbols Path box, type C:\Windows\Symbols.

17. Click Launch.

The Microsoft Calculator appears in Scientific mode.

18. On the View menu, click Standard, and then close the calculator.

19. Click through each of the SUA tabs, reviewing the detected issues. You should seeentries on the INI and File tabs.

20. Click the File tab.

21. Review the file information, specifically the Work with Virtualization column.

A Yes in this column indicates that any attempt to write to the file is virtualized with the

Program Compatibility Assistant in Windows Vista. Virtualization is an inbox mitigation,which can fix the issue until the application developers update the application.


16/33



22. On the View menu, click Detailed Information.

23. Review the information, including the Stack Trace details area.

24. On the Mitigation menu, click Apply Mitigations.

The Mitigate AppCompat Issues dialog box appears with the recommended

mitigations for the issue.

25. Click Apply.

Using the Compatibility Administrator

In this section, you will use the Compatibility Administrator tool to resolve one of yourcompatibility issues, by creating and applying a compatibility fix.

Note For more information about using the Compatibility Administrator, including the other

available mitigation options, see the Using the Compatibility Administratorsection of theMicrosoft ACT: Phase 3 Testing and Mitigating Issues white paper, available for

download from the Related Resources section of theMicrosoft Application Compatibility

Toolkit 5.0 DownloadWeb page.

To use the Compatibility Administrator1. On the Compatibility Administrator toolbar, click New.

The New Database(n) [Untitled_n] entry appears below the Custom Databasesheading in the left pane.

2. Right-click the New Database(n) [Untitled_n] entry, click Rename, type CustomDatabase 1, and then press ENTER.

3. Right-click the Custom Database Application Fix database, click Create new, andthen click Application Fix.

The Create new Application Fix wizard appears.

4. Type Microsoft Application Compatibility Toolkit 5.0 in the Name of the program tobe fixed box, type Microsoft in the Name of the vendor for this program box, browse

to the ACM.exe file, located in the %Program Files%\Microsoft Application CompatibilityToolkit 5\Application Compatibility Manager directory, and then click Next.

5. Click Microsoft Windows 2000, select the DisableThemes check box, and then click

Next.

6. Select the CorrectFilePaths compatibility fix, and then click Next.

7. Click Auto-Generate to automatically select the files that the Compatibility Administratorrecommends to represent your application, and then click Finish.

8. On the File menu, click Save As.

9. Keep the default location, type ACMCompatFix into the File name box, and then clickSave.

10. At the command prompt, change directories to %Program Files%\Microsoft Application

Compatibility Toolkit 5\Application Compatibility Manager directory.

11. Type sdbinst.exe ACTCompatFix.sdb.

The application fix is applied to your local computer.

Scenario 2: Applying a Windows Update

This scenario covers an organization that is planning to deploy a Windows update into itsenvironment, but first requires a more detailed assessment of the potential compatibility


17/33



issues. You must deploy the associated DCP only to client computers running one of thefollowing operating systems.



Windows 2000 with Service Pack 4 (SP4) and Update Rollup 1

Important ACT does not supportthe UCE on earlier versions of the previouslylisted operating systems, Windows Vista, Windows NT, Windows Server Code

Name "Longhorn," or any 64-bit operating system.


In this phase, you will create a new data collection package that will collect your hardwareand software inventory and then visit several Web sites to view the associated compatibilitydata.

To collect your inventory and compatibility data1. On the taskbar, click Start, point to All Programs, point to Microsoft Application

Compatibility Toolkit 5.0, and then click Application Compatibility Manager.



3. In the PackageName box, type Inventory_for_Updates.

4. In the Evaluate compatibility when area, click Applying Windows Updates.

5. Click Advanced.

The Advanced Settings dialog box appears

6. Clear the Update Compatibility Evaluator check box, and then click OK.

The Advanced Settings dialog box closes.

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.



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 InstallationSoftware, logon scripts, or any customized deployment method already used within your

organization.

Note The suggested deployment methods might require that you repackage theDCP, which is an .exe file format, into an .msi file format. For more information abouthow to repackage your DCPs, seeHow to create a Setup package by using Visual Studio

.NET,How to publish non-MSI programs with .zap files, andUsing the WiX Toolset toIntegrate 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.
http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90668http://go.microsoft.com/fwlink/?LinkId=90668http://go.microsoft.com/fwlink/?LinkId=90668http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90668http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90667


18/33





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.


The DCP runs on the client computer.14. In the Quick Reports pane of the Application Compatibility Manager, click Analyze.



16. In the Sign-in to Compatibility Data Exchange dialog box, enter the required Microsoft.NET Passport details, and then click Sign In.


17. Click View the specific applications to be shared with the ACT Community .

The dialog box changes to display the applications that will send and will receive

information from Microsoft during the synchronization process.


19/33






Data synchronization occurs between your computer and the Microsoft Compatibility

Exchange.

19. Return to the Analyze screen and review the updated security data for yourapplications.




20/33



21. In the PackageName box, type Update_Deployment.

22. In the Evaluate compatibility when area, click Applying Windows Updates.

Note This evaluator option includes the Inventory Collector and the UCE, by

default.

23. Keep the default values in the When to monitor application usage area and in the

Output Location box.24. On the File menu, click Save and Create Package.


26. Repeat steps 11-19 to deploy your DCP and to synchronize your data.


In this phase, you will organize your data by using categories and subcategories, priorities,

and severities. After organizing your data, you will be able to fi lter your compatibility data, to

determine which applications might have compatibility issues, and to view the information incustomized reports.


In this section, you will prioritize your application compatibility data, based on the importanceof the application to your organization. The available priority levels are:

Business Critical. The highest priority level. Business critical items are so important toyour organization that, unless you certify them, you cannot deploy the updated operatingsystem.

Important. The priority level for applications, Web sites, and updates that yourorganization regularly uses but can continue to function without. You can choose to deploythe updated operating system without requiring certification.

Nice to Have. The priority level for applications, Web sites, and updates that do not fallinto the previous two categories but should appear in your ACT compatibility reports. Youwill deploy the updated operating system regardless of certification.


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 applicationsthat have not yet been reviewed for deployment.

To prioritize your applications1. In the Quick Reports pane of the Analyze screen, click Applications below the Update

Impact Reports heading.

2. The Update Impact Reports - Applications screen appears.

3. Click MicrosoftApplication Compatibility Toolkit Data Collector 5.0 in the Update

Impact Reports

Applications screen.


5. The Assign Priority dialog box appears.

6. Click Priority 2 Important, and then click OK.


In this section, you will create and will assign categories and subcategories to an application.


21/33




1. In the Update Impact Reports - Applications screen, click Microsoft ApplicationCompatibility Toolkit Data Collector 5.0.



3. Click Master Category List.The Master Category List dialog box appears.

4. In the Categories area, click Add, type Department, and then press ENTER.

5. In the Subcategories area, click Add, type Sales, and then press ENTER.

6. In the Subcategories area, click Add, type Marketing, and then press ENTER.

7. Click OK.


8. Click OK.


To assign a category and a subcategory1. In the Update Impact Reports - Applications screen, click Microsoft Application

Compatibility Toolkit Data Collector 5.0.



3. Select the Sales check box, and then click OK.

Important Although Sales is a subcategory, when you select the check box, it

automatically selects the parent category. You must assign a subcategory if youassign a category.


Setting Your Severity

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 goingthrough 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.

To set your severity rating

1. On the Quick Reports pane of the Analyze screen, click Updates below the UpdateImpact Reports heading.

The Updates screen appears.

2. In the Updates screen, click the top-most Windows update in the right-hand pane.

3. On the Actions menu, click Set My Severity.

The Set My Severity dialog box appears.

4. In the Select your Severity list, click Moderate, and then click OK.

Note You can create your own severities for inclusion in the Select your Severity

list.


22/33



Filtering Your Data

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, youcan view the results as a customized report, tailored to your organizational requirements.


1. In the Update Impact Reports Applications screen, click Toggle Filter.



4. In the Value box, type Priority 2 - Important.





9. In the Value box, type Sales.

10. Press the TAB key to create a new query row.11. In the And/Or list, click And.








18. In the Value box, type Department.


The filter sorts your data to display the Microsoft Application Compatibility Toolkit Data

Collector 5.0 because it is the only application that fulfills all the filter criteria.

Viewing a Report

In this section, you will view an Update Impact Reports - Applications report screen, anapplication details dialog box, an Updates report screen and a security update dialog box.

To view an Update Impact Reports - Application report and an application details

dialog box1. In the Quick Reports pane of the Analyze screen, click Applications below the Update

Impact Reports heading.The Update Impact Reports - Applications screen appears.

2. Double-click Microsoft Application Compatibility Toolkit Data Collector 5.0.

The Microsoft Application Compatibility Toolkit Data Collector 5.0 dialog boxappears, displaying the assessment details for the application.


23/33



3. Click the Intersecting Updates, Application Properties, and Computers tab for more

information about the application as it relates to that heading.

To view an Updates report and a security update dialog box

1. In the Quick Reports pane of the Analyze screen, click Updates below the Update

Impact Reports heading.

The Updates screen appears.

2. Double-click the top-most Windows update in the right-hand pane.

The security update dialog box appears, displaying the details for the update.

3. Click the Intersecting Applications, Update Properties, and Computers tab for moreinformation about the update as it relates to that heading.


In the following sections, you will test and will mitigate your issues by using the StandardUser Analyzer (SUA) and the Compatibility Administrator.

Using the Standard User Analyzer (SUA)

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 AccountControl (UAC) feature in Windows Vista.

Note For more information about SUA, see the Using the Standard User Analyzersection

of the Microsoft ACT: Phase 3 Testing and Mitigating Issues white paper, available fordownload from the Related Resources section of theMicrosoft Application Compatibility


To test an application by using SUA

1. Log on the computer with a Standard User account.






5. Click Close.

6. Reopen the calculator application, noting that the calculator has returned to Standardmode and that your settings are not saved.

7. Log off the computer.

8. Log on the computer with an Administrator account.

9. On the taskbar, click Start, and then click Run.10. Type calc.exe, and then press ENTER.





24/33



12. Click Close.

13. Reopen the calculator application, noting that the calculator remains in Scientific modeand that your settings are saved. Because the Microsoft Calculator behaves differently

for Standard Users and Administrators, we can conclude that a UAC issue exists.

Note The calculator issue described for this example is no longer an issue in

Windows Vista.14. Click Start, point to All Programs, point to Microsoft Application Compatibility

Toolkit 5.0, point to Developer and Tester Tools, and then click Standard UserAnalyzer.

15. In the Target Application box, type C:\Windows\System32\calc.exe.

16. In the Symbols Path box, type C:\Windows\Symbols.

17. Click Launch.

The Microsoft Calculator appears in Scientific mode.

18. On the View menu, click Standard, and then close the calculator.

19. Click through each of the SUA tabs, reviewing the detected issues. You should seeentries on the INI and File tabs.

20. Click the File tab.

21. Review the file information, specifically the Work with Virtualization column.

A Yes in this column indicates that any attempt to write to the file is virtualized with the

Program Compatibility Assistant in Windows Vista. Virtualization is an inbox mitigation,which can fix the issue until the application developers update the application.

22. On the View menu, click Detailed Information.

23. Review the information, including the Stack Trace details area.

24. On the Mitigation menu, click Apply Mitigations.

The Mitigate AppCompat Issues dialog box appears with the recommendedmitigations for the issue.

25. Click Apply.

Using the Compatibility Administrator

In this section, you will use the Compatibility Administrator tool to resolve one of yourcompatibility issues, by creating and applying a compatibility mode.

Note For more information about using the Compatibility Administrator, including the othermitigation options available, see the Using the Compatibility Administratorsection of the

Microsoft ACT: Phase 3 Testing and Mitigating Issues white paper, available fordownload from the Related Resources section of theMicrosoft Application Compatibility


To use the Compatibility Administrator1. On the Compatibility Administrator toolbar, click New.

The New Database(n) [Untitled_n] entry appears below the Custom Databases

heading in the left pane.


25/33



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.

Scenario 3: Upgrading Internet Explorer

This scenario covers an organization that is planning to upgrade to Internet Explorer 7, butfirst requires a more detailed assessment of the potential compatibility issues. You must

deploy the associated DCP only to client computers running one of the following operatingsystems.

Windows Vista



Important You must have Internet Explorer 7 installed on any client computer to

which you will deploy the DCP.


In this phase, you will create a new data collection package that will collect yourorganization's inventory. After ACT collects your inventory and while the DCP is still

deployed and collecting data, you will visit several of your required Web sites to view anyknown compatibility issues.

To collect your inventory and compatibility data

1. On the taskbar, click Start, point to All Programs, point to Microsoft ApplicationCompatibility Toolkit 5.0, and then click Application Compatibility Manager.



3. In the Package Name box, type Inventory_for_IE7.

4. In the Evaluate compatibility when area, click Updating to a new version of InternetExplorer.

5. Click Advanced.

The Advanced Settings dialog box appears

6. Clear the Internet Explorer Compatibility Evaluator check box, and then click OK.

The Advanced Settings dialog box closes.


26/33



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.


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 includeMicrosoft Systems Management Server 2003 (SMS 2003), Group Policy Installation

Software, logon scripts, or any customized deployment method already used within yourorganization.

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 abouthow to repackage your DCPs, seeHow to create a Setup package by using Visual Studio

.NET,How to publish non-MSI programs with .zap files, and Using the WiX Toolset toIntegrate Setup into Your Development Process.

For detailed deployment methodology, including determining where and when todeploy the DCP, see the Microsoft ACT: Phase 1 Collecting Data white paper.



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 yieldof the returned data.


14. The DCP runs on the client computer.

15. In the Quick Reports pane of the Application Compatibility Manager, click Analyze.


http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90668http://go.microsoft.com/fwlink/?LinkId=90668http://go.microsoft.com/fwlink/?LinkId=90668http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90669http://go.microsoft.com/fwlink/?LinkId=90668http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90667http://go.microsoft.com/fwlink/?LinkId=90667


27/33



17. In the Sign-in to Compatibility Data Exchange dialog box, enter the required Microsoft

.NET Passport details, and then click Sign In.


18. Click Viewthe specific applications to be shared with the ACT Community.

The dialog box changes to display the applications that will send and will receiveinformation from Microsoft during the synchronization process.




28/33




20. Data synchronization occurs between your computer and the Microsoft CompatibilityExchange.

21. Return to the Analyze screen and review the updated software and hardware data.



23. In the Package Name box, type IE_Upgrade.

24. In the Evaluate compatibility when area, click Updating to a new version of InternetExplorer.

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 theOutput Location box.



28. Repeat steps 11-14 to deploy your DCP.

29. On the client computer, open an Internet Explorer 7 browser window.

30. Visit theMicrosoft Worldwide Web site, click Europe from the Web Sites drop-down list,and then click Go.

31. Visit theMicrosoft Volume Licensing Sites Worldwide Web site, click United States from theWeb Sites drop-down list, and then click Go.

32. Visit theGames for Windows Web site.

33. Close the Internet Explorer 7 browser window.


In this phase, you will organize your data by using categories and subcategories, priorities,and assessment ratings. After organizing your data, you will be able to filter your

compatibility data, to determine which Web sites might have compatibility issues, and to viewthe information in customized reports.
http://go.microsoft.com/fwlink/?LinkID=75733http://go.microsoft.com/fwlink/?LinkID=75733http://go.microsoft.com/fwlink/?LinkID=75733http://go.microsoft.com/fwlink/?LinkId=88573http://go.microsoft.com/fwlink/?LinkId=88573http://go.microsoft.com/fwlink/?LinkId=88573http://www.gamesforwindows.com/en-US/Pages/default.aspxhttp://www.gamesforwindows.com/en-US/Pages/default.aspxhttp://www.gamesforwindows.com/en-US/Pages/default.aspxhttp://www.gamesforwindows.com/en-US/Pages/default.aspxhttp://go.microsoft.com/fwlink/?LinkId=88573http://go.microsoft.com/fwlink/?LinkID=75733


29/33




In this section, you will prioritize your Web sites, based on the importance of the site to yourorganization. The available priority levels are:

Business Critical. The highest priority level. Business critical items are so important toyour organization that, unless you certify them, you cannot deploy the updated operating

system.Important. The priority level for applications, Web sites, and updates that yourorganization regularly uses but can continue to function without. You can choose todeploy the updated operating system without requiring certification.

Nice to Have. The priority level for applications, Web sites, and updates that do not fallinto the previous two categories but should appear in your ACT compatibility reports.You will deploy the updated operating system regardless of certification.


Unspecified. The default priority level that is automatically assigned to all applications,Web sites, and updates. Your organization can use this priority level to denoteapplications that have not yet been reviewed for deployment.

To prioritize your applications

1. In the Quick Reports pane of the Analyze screen, click Web Sites below the InternetExplorer 7 heading.

The Internet Explorer 7 Web Site Report screen appears.

2. Click http://www.microsoft.com/worldwide/ in the Internet Explorer 7 Web SiteReport screen.


The Assign Priority dialog box appears.

4. Click Priority 3 Nice to Have, and then click OK.


In this section, you will create and assign categories and subcategories to a Web site.


1. In the Internet Explorer 7 Web Site Report screen, clickhttp://www.microsoft.com/worldwide/.



3. Click Master Category List.

The Master Category List dialog box appears.

4. In the Categories area, click Add, type Visited By, and then press ENTER.5. In the Subcategories area, click Add, type Management, and then press ENTER.

6. In the Subcategories area, click Add, type Employees, and then press ENTER.

7. Click OK.


8. Click OK.

http://www.microsoft.com/worldwide/http://www.microsoft.com/worldwide/http://www.microsoft.com/worldwide/


30/33



To assign a category and a subcategory

1. In the Internet Explorer 7 Web Site Report screen, clickhttp://www.microsoft.com/worldwide/.



3. Select the Manager check box, and then click OK.Important Although Manager is a subcategory, when you select the check box, it

automatically selects the parent category. You must assign a subcategory if youassign a category.


Setting Your Assessment

In this section, you will set your organization's assessment rating for a Web site. Yourassessment rating enables you to specify which sites might be problematic while goingthrough 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 that work properly and function as expected.

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 impairedfunctionality.

Blank

Denotes Web sites that do not have any application assessment data. In this

case, either the site does not match any information in the database or no userhas submitted an assessment.

To set your assessment rating1. In the Internet Explorer 7 Web Site Report screen, click

http://www.microsoft.com/worldwide/.

2. On the Actions menu, click Assessment.

The Set Assessment dialog box appears.

3. Click Works, and then click OK.

Filtering Your Data

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, youcan view the results as a customized report, tailored to your organizational requirements.
http://www.microsoft.com/worldwide/http://www.microsoft.com/worldwide/http://www.microsoft.com/worldwide/


31/33




1. In the Internet Explorer 7 Web Site Report screen, click Toggle Filter.



4. In the Value box, type Priority 3 Nice to Have.



7. In the Field list, click My Assessment.


9. In the Value box, type Works.









17. In the Value box, type Visited By.





22. In the Value box, type Management.


The filter sorts your data to display the http://www.microsoft.com/worldwide/ Web site

because it is the only site that fulfills all the filter criteria.

Viewing a Report

In this section, you will view an Internet Explorer 7 Web Site Report screen and a Website 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 InternetExplorer 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.

Adding and Resolving Issues

In this section, you will add a new compatibility issue and a new solution, and then you willresolve the issue for your organization.


32/33



To add and resolve a compatibility issue

1. In the http://www.microsoft.com/worldwide/ dialog box, click Add Issue on theActions menu.

2. The http://www.microsoft.com/worldwide/New Issue dialog box appears.

3. In the Title box, type Example_Website_Issue.

4. In the Priority list, click Priority 3

Nice to Fix.5. In the Severity list, click Severity 3 Minor functionality loss.

6. In the Symptom list, click Application has impaired functionality.

7. In the Cause list, click Internet Explorer Protected Mode.

8. In the Affected Operating Systems box, keep the default value (Windows Vista)

selected.

9. In the Issue Description box, type This is the issue description text.

10. On the File menu, click Save.

11. On the Actions menu in the http://www.microsoft.com/worldwide/ -Example_Website_Issue dialog box, click Add Solution.

12. The http://www.microsoft.com/worldwide/ - Add Solution dialog box appears.13. In the Title box, type Example_Website_Solution.

14. In the Solution Type box, click Other.

15. In the Solution Details box, type This is the solution details text.

16. Click Save.

17. On the Actions menu in the http://www.microsoft.com/worldwide/ -Example_Website_Issue dialog box, click Resolve.

The issue is resolved, changing the red x to a green check mark.


In this phase, you will test your Web site issues by using the Internet Explorer CompatibilityTool.

Using the Internet Explorer Compatibility Test Tool

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 Websites 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 theInternet Explorer Compatibility Test Tooltopics 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


33/33


To use the Internet Explorer Compatibility Test Tool

1. On the taskbar, click Start, point to All Programs, point to Microsoft ApplicationCompatibility Toolkit 5.0, point to Developer and Tester Tools, and then click

Internet Explorer Compatibility Test Tool.

2. Click Enable.

3. Open an Internet Explorer 7 browser window and visit theMicrosoft Worldwide Web site,click Europe from the Web Sites drop-down list, and then click Go.

4. Visit theMicrosoft Volume Licensing Sites Worldwide Web site, click United States from theWeb Sites drop-down list, and then click Go.

5. Visit theGames for Windows Web site.

The test tool logs any potential issues associated with the visited Web sites.

Important You must use Internet Explorer 7 while running the Internet Explorer

Compatibility Test Tool.

6. Select the first issue, of the issue type Windows Restrictions, on the Live Data tab.

7. Review the associated information in the Issue Description area.

8. Click Filter.

The Issues Filter dialog box appears.

9. Clear the Windows Restrictions check box, and then click OK.

The data changes to display only the Games for Windows Web site results because it

is the only site with CSS Fixes issues.

10. On the File menu, click Upload.

Note You will see several status messages, stating that various ACT components

are finishing.

11. In the Save As dialog box, browse to your ACT Log Processing share location, and then

type IE_Test_Results.

12. Click Save.

By default, the ACT saves the IE_Test_Results.cab file in the Internet ExplorerCompatibility Test Tool folder. After the save completes, the test tool clears the results.

13. Click Disable, and then close the Internet Explorer Compatibility Test Tool.

14. On the taskbar, click Start, point to All Programs, point to Microsoft Application

Compatibility Toolkit 5.0, and then click Application Compatibility Manager.

15. In the Quick Reports pane, click Analyze.


16. In the Quick Reports pane, click Web Sites in the Internet Explorer 7 section.

The Internet Explorer 7 Web Site Report screen appears, enabling you to review yourcompatibility issues.
http://go.microsoft.com/fwlink/?LinkID=75733http://go.microsoft.com/fwlink/?LinkID=75733http://go.microsoft.com/fwlink/?LinkID=75733http://go.microsoft.com/fwlink/?LinkId=88573http://go.microsoft.com/fwlink/?LinkId=88573http://go.microsoft.com/fwlink/?LinkId=88573http://www.gamesforwindows.com/en-US/Pages/default.aspxhttp://www.gamesforwindows.com/en-US/Pages/default.aspxhttp://www.gamesforwindows.com/en-US/Pages/default.aspxhttp://www.gamesforwindows.com/en-US/Pages/default.aspxhttp://go.microsoft.com/fwlink/?LinkId=88573http://go.microsoft.com/fwlink/?LinkID=75733

Documents

ACT Step by Step