Share via

Testing the installation

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Testing the installation

Some programs installed using change user might not work at first because of the locked-down state of the system. Some 16-bit programs must be able to write to the directory where the program .ini file is stored. Some 32-bit programs create registry entries that are needed for proper operation.

Enable event logging and then log onto the server using a temporary user account created to mimic the user or users that will be accessing the program. Start the program and go through the basic procedures for using it. Then, use Event Viewer to determine which files or directories need Write access and which registry keys require Read access by the user for correct operation.

Note

  • This process might not find all files, directories, and registry keys for which access is required by the application in all user scenarios. The only way to ensure that you have accounted for all access requirements is to perform tasks manually.

Consider creating two user accounts and testing with each account before proceeding. This allows you to make changes to program preferences and templates, while ensuring that those changes do not affect other users of the same group.

Keep track of all files, and any issues that arise. For information about how to tune programs for multisession use, see Program Compatibility.