|Lesson 8||Configuring compatibility script parameters|
|Objective||Configure and run application compatibility scripts.|
To run application compatibility scripts, perform the following steps:
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.
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 following tasks:
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'll learn how to adjust performance and security settings for remote administration.