IT: How to Correctly Install Applications on a Remote Desktop Server
- Taylor Gibb
@taybgibb
When installing an application on a Terminal Server, because multiple people will be using the application at once, there is actually a special method that you should use to install the applications. Here’s two methods to do it the right way.
Note: this is part of our ongoing series teaching IT administration basics, and might not apply to everybody.
Getting ready
We need to install a program onto our RDSH server. This box is running Windows Server 2016 and is already part of our RDS environment. We will also need, of course, the application installer files that we intend to launch.
How to do it…
One way to properly install programs onto an RDSH is by using Control Panel to install the application:
- Right-click on your Start flag and choose to open Control Panel
- Click on Programs
- Choose the button that says Install Application on Remote Desktop…:
- Click Next and you will be able to specify the location of your installer file for the application:
- Click Next, and your program will install. When finished, make sure you click the Finish button on the Install Mode mini-wizard screen, so that the RDSH is placed back into Execute Mode and is ready for normal operation:
The second way to place an RDSH into Install Mode is by using the command prompt:
- Right-click on the Start flag and choose to open Command Prompt [Admin].
- Type change user /install and press Enter:
- Now find your program installer file and launch it. Walk through the installation steps in the same way you would on any regular server or computer.
- Once the program has finished installing, head back to the command prompt window and now type change user /execute. Then press Enter. This takes the RDSH out of the special Install Mode and places it back into normal Execute Mode:
Restarting the server also automatically places it back into Execute Mode. So if your application installer asks you to restart as part of the installation process, your RDSH will be placed back into Execute Mode when it boots, and in that case, you do not have to enter the command manually.
Installing applications on RD Session Host servers
Whether you are providing session-based virtual desktops or RemoteApp programs, you need to ensure that apps are installed properly on the RD Session Host servers. Before you attempt to install the app in a production environment, you need to verify that it works properly when installed on an RD Session Host server. When you install the app on an RD Session Host server, you need to follow a specific installation process.
The following are some considerations for deploying apps on RD Session Host servers:
- Suitability for multiuser environments:
This is the most important consideration for apps installed on RD Session Host servers. Historically, most end-user apps function well in multiuser environments, but this isn't always the case. Ideally, the app vendor officially will support installation on RD Session Host servers. In some cases, you may need to obtain an update from the app vendor that enables an app to run properly on an RD Session Host server. If an app can't run on RD Session Host servers, then you'll need to install it on desktops or consider using an alternative app.
Note:
Many apps that aren't officially supported for RD Session Host servers run properly, but the vendor hasn't done the necessary testing. You can choose to install the app anyway and accept the risk of unforeseen failures. Whether you do this depends on the organizational benefits of putting the app on RD Session Host servers versus the cost of potential failure in the future. - App compatibility:
You need to investigate whether apps have compatibility issues when coexisting on RD Session Host servers. Ensure that you thoroughly test apps before you put them into a production environment. You might need collections with separate pools of RD Session Host servers to run incompatible applications separately from one another. - App dependencies:
Install related apps or apps that have dependencies on other local apps on the same RD Session Host server. For example, all the apps in a suite such as Microsoft Office should be installed on the same RD Session Host server unless otherwise prescribed by the vendor. - Capacity requirements:
There are no firm numbers on how many clients a single RD Session Host server can support. Resource requirements depend on the number of apps that are being used simultaneously and the resource requirements of individual apps. Adding a new app to an RD Session Host server will increase the load on the server. Don't assume that because the number of clients remains the same, the load won't increase. - Licensing requirements:
The licensing requirements for apps vary widely among vendors and apps. In many cases, installing an app on an RD Session Host server means that you need to purchase licenses for every user who has access to session-based virtual desktops. In a large RDS deployment, this can be very expensive. You may be able to mitigate this by using RemoteApp programs, which can be controlled by user groups. Some vendors have specific licensing for RDS deployments.
Installing an app on an RD Session Host server is different from installing an app on a traditional desktop. RD Session Host servers operate in two modes: install mode and execute mode. You must put a server in install mode to install multiuser apps properly. In install mode, the Windows operating system ensures that appropriate registry entries and initialization [.ini] file settings are configured for an app to function in multiuser environments. After an app successfully installs, the server must be placed back into execute mode.
The Windows Installer Service is RDS-aware. This means that Windows Installer packaged apps [.msi] automatically are installed properly. Windows Installer switches to install mode and back to execute mode as part of the installation process. Most apps are distributed as Windows Installer packages as for installation, but you should verify before installing.
If the app isn't distributed as a Windows Installer package, then you need to ensure that you install it by using the proper process. One way to install the application properly is by using the Install Application On Remote Desktop Server option in the Programs area of Control Panel. This option is added to all RD Session Host servers. Using this option opens a wizard that prompts you for the location of the installation files and puts the server into install mode while performing the installation.
Alternatively, you can use a command prompt to manually put the RD Session Host server into install mode by using the following command:
change user /installAfter the RD Session Host server is switched to install mode, install the application. Then, change the RD Session Host server back to execute mode by using the following command:
change user /executeYou also can check the current server mode by using the following command:
change user /queryYou also can use apps deployed by using Microsoft Application Virtualization [App-V] for sessionbased virtual desktops and RemoteApp programs. Using App-V can mitigate some compatibility issues and simplify application deployment and updates.
When you toggle Terminal Services to Application Server mode, some programs may stop working
- Article
- 09/24/2021
- 4 minutes to read
- 4 contributors
Is this page helpful?
Yes No
Any additional feedback?
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.
Submit
Thank you.
In this article
This article describes the issue that some programs may stop working, when you toggle Terminal Services to Application Server mode.
Applies to: Windows 2000
Original KB number: 252330
Note
This article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center is a starting point for planning your migration strategy from Windows 2000. For more information, see the Microsoft Support Lifecycle Policy.
how to add more software on remote desktop server?
Hello, I have server 2019 and quick setup RDS server on it.
I was able to see and start default apps like notepad, wordpad, and paint. so it seems the server functional.
question.
1. Purpose of this server was to serve our enterprise applications to users. so this brings up another question, how do I add new/additional software on RDWEB? do I have to install it on the server? which is not possible because a lot of our software isn't designed for servers.
If I have to install the software on the server, can I uninstall it after the icon on rdweb is created?
how is licensing issue managed? do we have to purchase an extra license peruser?
Thankyou very much
remote-desktop-servicesComment
Comment Show 0
Comment
5 |1600 characters needed characters left characters exceeded
▼
- Visible to all users
- Visible to the original poster & Microsoft
- Viewable by moderators
- Viewable by moderators and the original poster
- Advanced visibility
Attachments: Up to 10 attachments [including images] can be used with a maximum of 3.0 MiB each and 30.0 MiB total.
KarlieWeng-MSFT answered • May 20, '21
Hello @EncamiJamal-3850
1.Add new/additional software on RDWEB:
To Publish RemoteApp Programs click on the link and the wizard retrieves a list of applications that are available on the RDSH. If you want to publish programs that are not in this list use the Add button to browse to the program you want to publish. Note that you need to browse to a UNC path, not a local disk on the RD Session Host.
2.Can I uninstall it after the icon on rdweb is created
Users actually will be directed to session host server and use that app, so you cann't delete that published App.
3.do we have to purchase an extra license peruser
If you already have Rds per-user CAL, then you don't , otherwise yes. Server CAL is not enough.
You can read here about Cal.
Best Regards
Karlie
If the Answer is helpful, please click "Accept Answer" and upvote it.
image.png [122.9 KiB]
image.png [202.5 KiB]
image.png [163.3 KiB]
image.png [100.1 KiB]
Comment
Comment Show 0
Comment
5 |1600 characters needed characters left characters exceeded
▼
- Visible to all users
- Visible to the original poster & Microsoft
- Viewable by moderators
- Viewable by moderators and the original poster
- Advanced visibility
Attachments: Up to 10 attachments [including images] can be used with a maximum of 3.0 MiB each and 30.0 MiB total.
7 Replies
· · ·
Ghost Chili
OP
Best Answer
Jul 10, 2012 at 10:04 UTC
You can do this, but as we all know, many users will try something stupid and only realize that after they've been told [by us or the system] it's a no-go. I would wait myself. You may also want a reboot and to patch that application to current after the install as well, which will result in grumpy users if you do that while they're connected :-]
4
· · ·
Mace
OP
Jul 10, 2012 at 10:04 UTC
I'd seriously wait till end of day, just in case a botched install happens.
2
· · ·
Serrano
OP
Jul 10, 2012 at 10:11 UTC
In my opinion wait till everyone is logged off. this will eliminate the possibility of having a process called for before it is installed completely [yes this has happened to me before]. This will ensure any errors you may or may not get will be true errors and not caused by an active application calling for a resource that has only been partially installed. As a general rule any major change / install should be carried out during non peak times to eliminate the "everything just got realy slow" calls you may receive during the install. Again this is all an opinion.
1
· · ·
Ghost Chili
OP
Jul 10, 2012 at 10:17 UTC
Technically it's possible, but as others have said, you should wait until after-hours to do this, for numerous reasons.
If something does go wrong, you'll need to down the server. The install might take up a lot of resources and slow users down. The install might require a reboot.
All of this makes users angry, and angry users are not fun users to work with.
But, from a technical standpoint it's possible.
0
· · ·
Mace
OP
Jul 10, 2012 at 10:55 UTC
We had lots of issues when updating something when people are logged in.
Log everyone off or wait to EOD and install from Console. Don't install from RDP, Console is muchpreferred.
0
· · ·
Cayenne
OP
Jul 10, 2012 at 11:17 UTC
You will spend more time fixing the install than you would if you can wait until everyone is off. It is not worth the time. We no longer install anything unless all users are logged off of the terminal servers.
1
· · ·
Serrano
OP
Jul 12, 2012 at 08:25 UTC
Votes for best / helpful and close the issue?
0
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.