Windows 7 / Getting Started

---

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 below describes the command-line options for Sdbinst.exe, which has the following syntax:

sdbinst [-?] [-q] filename.sdb [-u] [-g {guid}] [-n name]

Sdbinst.exe Command-Line Options

Option	Description
-?	Displays Help text
-q	Runs quietly with no message boxes
filename.sdb	Specifies the file name of the database to install
-u	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.