• Home
• About
• Animals and Rescues
• Computer Issues
• Computer parts
• Computer parts install instructions
• Contact
• Definitions
• DOS Commands
• Downloads
• Hardware questions
• How to use software
• How to use Windows
• How to perform tasks and other information
• Humor
• Internet info and help
• Madison High School Yearbooks
• Madison High School Alumni and teacher's deaths
• Military reunions, events and other info
• How to use Microsoft Office
• Network setup, and other info
• Information on operating systems
• Reinstall operating system
• Remote Services
• Service cost           
• Safety Tips
• Tips
• Troubleshooting Tools
• Info on Websites and/or Businesses
• 
  I have put this website up for your convenience.  The website and email service is free, but if you find this site helpful and would like to make a donation, click on the donate button above. Thank you!
  

Change user

This page is from Microsoft

Updated: January 21, 2005

Syntax

Parameters

Remarks

• Use change user/install before installing an application to create .ini files for the application in the system directory. These files are used as master copies for user-specific .ini files. After installing the application, use change user/execute to revert to standard .ini file mapping.
• The first time you run the application, it searches the home directory for its .ini files. If the .ini files are not found in the home directory, but are found in the system directory, Terminal Services copies the .ini files to the home directory, ensuring that each user has a unique copy of the application .ini files. Any new .ini files are created in the home directory.
• Each user should have a unique copy of the .ini files for an application. This prevents instances where different users might have incompatible application configurations (for example, different default directories or screen resolutions).
• When the system is in install mode (that is, change user/install), several things occur. All registry entries that are created are shadowed under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT  \CurrentVersion\TerminalServer\Install. Keys added to HKEY_CURRENT_USER are copied under the \SOFTWARE key, and keys added to HKEY_LOCAL_MACHINE are copied under \MACHINE. If the application queries the Windows directory using system calls, such as GetWindowsDirectory, the terminal server returns the systemroot directory. If any .ini file entries are added using system calls, such as WritePrivateProfileString, they are added to the .ini files under the systemroot directory.
• When the system returns to execution mode (that is, change user/execute), and the application tries to read a registry entry under HKEY_CURRENT_USER that does not exist, Terminal Services checks to see whether a copy of the key exists under the \TerminalServer\Install key. If it does, the keys are copied to the appropriate location under HKEY_CURRENT_USER. If the application tries to read from an .ini file that does not exist, Terminal Services searches for that .ini file under the system root. If the .ini file is in the system root, it is copied to the \Windows subdirectory of the user's home directory. If the application queries the Windows directory, the terminal server returns the \Windows subdirectory of the user's home directory.
• When you log on, Terminal Services checks whether its system .ini files are newer than the .ini files on your computer. If the system version is newer, your .ini file is either replaced or merged with the newer version. This depends on whether or not the INISYNC bit, 0x40, is set for this .ini file. Your previous version of the .ini file is renamed as Inifile.ctx. If the system registry values under the \TerminalServer\Install key are newer than your version under HKEY_CURRENT_USER, your version of the keys is deleted and replaced with the new keys from \TerminalServer\Install.

Examples

Formatting legend