Deploying Application Mitigation Packages

Distribution of the custom compatibility databases (. sdb files) can be facilitated using a variety of methods such as logon scripts, System Center Configuration Manager 2007, injection into disk images, and so on . After the file is on the target system, the actual installation of the custom databases is done using a tool that ships with the operating system called Sdbinst.exe. After the file exists on the target computer, the custom database file must be installed (registered) before the operating system will identify the fixes present when starting the affected applications . (For example, the command line might be sdbinst C:\Windows\AppPatch\Myapp.sdb .) After the database file is registered on a computer, the compatibility information will be used any time the application is started. Table 5-4 describes the command-line options for Sdbinst. exe, which has the following syntax:

sdbinst [-?] [-q] filename.sdb [-u] [-g {guid}] [-n name] table 5-4 Sdbinst .exe Command-Line Options


sdbinst [-?] [-q] filename.sdb [-u] [-g {guid}] [-n name] table 5-4 Sdbinst .exe Command-Line Options


Displays Help text


Runs quietly with no message boxes


Specifies the file name of the database to install


Uninstalls the database

-g {guid}

Specifies the globally unique identifier (GUID) of the database to uninstall

-n name

Specifies the name of the database to uninstall

The Sdbinst exe command can be written into a machine logon script to automatically install the custom database from a share network location when the users log on to their computers This process could even be accomplished as part of a custom job to be pushed out to the desktops via System Center Configuration Manager 2007 or another third-party management application One of the best methods of distribution of these custom databases is to include them in your disk image Installing them as part of the original image before adding the application that needs the fixes ensures that the application will run the first time the user needs it


For many companies, issues with application compatibility prevent them from fully taking advantage of the technology that they are already paying for, such as Windows 7. Many of the issues are related to fear, uncertainty, and doubt as to whether the applications in their environment are compatible with Windows 7. You can help overcome these concerns by creating an application inventory and then rationalizing it. In the case of application compatibility, knowledge helps companies overcome challenges.

This chapter described the primary tool that Microsoft provides for gaining this understanding and then putting it to use by creating a rationalized application portfolio as well as testing and mitigating compatibility issues. That tool is the ACT, and it is available as a free download from the Microsoft Download Center.

Additional Resources

These resources contain additional information and tools related to this chapter

■ Chapter 7, "Migrating User State Data," describes how to migrate users' documents and settings as part of a Windows 7 deployment.

■ Chapter 8, "Deploying Applications," describes how to deploy applications as part of a Windows 7 deployment.

■ "Application Compatibility" in the Windows Client TechCenter on Microsoft TechNet at

■ "Microsoft Assessment and Planning (MAP) Toolkit 4.0" at /en-us/solutionaccelerators/dd537566.aspx.

■ "Microsoft Application Compatibility Toolkit (ACT) Version 5 . 5" at describes the ACT.

■ "Microsoft Application Compatibility Toolkit 5 .5" at /details.aspx?FamilyId=24DA89E9-B581-47B0-B45E-492DD6DA2971&displaylang=en contains the ACT download

■ Chris Jackson's blog at

■ Aaron Margosis's blog at


Was this article helpful?

0 0

Post a comment