Yes, you do. That old chestnut from the Terminal Services days is still a core part of Remote Desktop Services (RDS) on Windows Server 2025. It might seem like a relic, but if you want your applications to work correctly for every user on your Session Host, you absolutely can’t skip it.
The Modern Caveat: MSI vs. EXE
While the process is still required, some software deployment tools and package types are getting smarter.
- MSI Packages: Microsoft Installer packages are generally aware they are running on an RDSH server and often switch to install mode automatically (and then switch back). Many admins skip the
change usercommand for MSI files and everything works fine - EXE Installers: Traditional, non-Windows-Installer executables are the risk. If you are installing an old or custom EXE setup, you must manually use
change user /installto ensure proper user-specific configuration
Why Change To Install Mode?
The fundamental problem with installing applications on a multi-user environment like a Remote Desktop Session Host (RDSH) hasn’t changed. When you install most software, it writes settings specific to the user running the installer (in HKEY_CURRENT_USER – HKCU). But on an RDSH server, these settings need to be available as a master copy for all users.
The change user /install command (or “install mode”) forces the operating system to perform a critical piece of magic:
- It redirects all writes to
HKEY_CURRENT_USER(HKCU) to a special master location underHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install - It also redirects any
.inifile writes to the system directory, not the user’s profile - When a user logs in and runs the app for the first time, the OS sees the master settings and automatically copies them to that user’s specific profile/registry hive
If you don’t do this, the application will likely only work for the admin account who installed it, and you’ll be left scratching your head when your users complain about missing settings or crashes.
How To Change RDS To Install Mode
You have two ways to execute this ancient, yet powerful, process on your Windows Server 2025 Session Host:
Method 1: The Command-Line Way
This is the fastest and most reliable method, especially if you’re scripting or using deployment tools.
| Step | Command | Result |
| 1. Enable Install Mode | change user /install | The server is now recording registry and file changes |
| 2. Install Application | Run your setup/installer | Install the application as you normally would |
| 3. Disable Install Mode | change user /execute | The server reverts to normal user execution mode. Don’t forget this! |
| 4. Check Status (Optional) | change user /query | Confirms the current mode (Install or Execute) |
Method 2: The Lazy GUI Way (The Admin Favorite)
You can let the OS handle the switching for you using the dedicated applet.
- Open Control Panel, switch the view to Small Icons
- Click on Install Application on Remote Desktop Server
- Follow the wizard. It will temporarily switch to install mode, prompt you to find and run your installer, and then switch back to execute mode once the installation is finished
The Wrap
The change user /install process is a Windows Server RDS requirement, not just an artifact of Windows 2000. It’s the mechanism that ensures applications are installed once but function correctly for multiple users.
On Windows Server 2025, just stick to the rule: If you’re installing software on an RDSH, put the server in install mode first. Don’t be the admin who learns this the hard way at 2 a.m. when users can’t run their key finance app. It’s simple, it works, and it’s non-negotiable for a healthy RDS farm.
0 Comments