| Lesson 8 || Configuring compatibility script parameters |
| Objective || Configure and run application compatibility scripts. |
Each application compatibility script contains custom parameters that must be configured in order for the application to install and work correctly. For information about specific script capabilities and
how to modify them for custom installation, refer to the notes within the script for the application that you are installing.
You should run compatibility scripts after the application is installed.
Running application compatibility scripts
To run application compatibility scripts, perform the following steps:
- In the systemroot\Application Compatibility Scripts\Install folder, find the script or key file for the application that you are installing.
- Review the files in a text editor, such as Notepad. If path names in the files differ from those you used during the application installation, edit the files to correct the path information.
- At a command prompt, run the script for the application.
The first time an application compatibility script is used, the script checks to see whether Rootdrv.cmd has been edited. Rootdrv.cmd is a script that maps a drive letter to the client's home directory.
For example, if W:\ is specified as the drive letter for mapping, W:\ is mapped to %homedrive%%homepath%. By using this technique, you can specify what appears to be a shared path, such as
W:\mail\mailbox.dat. The drive mapping causes each user to receive a unique copy of the file in their home directory.
Selecting and Changing Drive for Mapping
The application compatibility script launches Notepad and requires you to type a drive letter and then to save and close the file. The application compatibility script resumes. Rootdrv.cmd is launched
only if you have not already mapped a drive letter. Rootdrv.cmd stores the final drive mapping information inRootdrv2.cmd. If you want to change the drive letter at a later time, you should complete the
- Open Rootdrv2.cmd in Notepad, edit the drive letter, and then save and close the file.
Microsoft\WindowsNT\CurrentVersion\Terminal Server\RootDrive registry key with the new drive letter.
Some applications may also require logon scripts. Logon scripts set custom environmental variables for users. For example, the logon script for Microsoft Internet Explorer establishes additional support files so users can have access to personal bookmarks and address books. Logon scripts are located in the systemroot\Application Compatibility Scripts\Logon folder. Logon scripts are not executed
for users who are logged on until they log off and log back on again. Many applications do not behave correctly when they are run before the logon script begins. For this reason, you should install applications when no users are logged on to the system. When you upgrade or add components to an existing installation of an application that has an associated compatibility script, you should rerun the
Next, you will learn how to adjust performance and security settings for remote administration.