Installing Applications for Windows Server 2. Terminal Services. Purchase and download the full PDF and e. Pub versions of this e. Book only $9. 9. 9The previous chapter covered the basic installation and configuration of Terminal Services on Windows Server 2. Once this task has been completed the next step is to install applications on the Windows Server 2. It is important to note that, firstly, applications must be installed specifically for use by Terminal Services users and, secondly, that not all applications are designed to be run by multiple concurrent users. With these constraints in mind, this chapter will cover the basics of safely installing applications on Windows Server 2. Terminal Services. To have each remote application run within its own window on the local client it will be necessary to configure the applications as Remote. Apps, a topic which is covered in detail in the Configuring Remote. Apps on Windows Server 2. I want to install a special program that will be available for one user. Server 2003 w/Terminal Server for one user. Thinstuff XP/VS Terminal Server for. You must put a Terminal Services server in Install mode to. Panel to add or remove a program, or by using the change user command. Terminal Services are in Execute mode when a client are connected and applications are being executed by users. Install mode is entered when applications are being installed for use by client users. Essentially, when in Install mode Windows ensures that the appropriate registry entries and . If an installation needs to be performed from the command prompt the mode can be changed using the switch user command. The following example switches to Install mode, performs the installation and then reverts to Execute mode. C: \Users\Administrator> change user /install. User session is ready to install applications. To install an application for Terminal Services invoke this tool by clicking on the icon. If the application to be installed is contained on CDROM or DVD media, insert the media into the appropriate drive and click on Next. If the installation executable is on a disk drive or network location click on Next and wait while the tool searches for the installation media. When none is found the tool will provide the option to browse for the installer. Click on the Browse.. Once selected click on Next to begin the installation. The installer will then run as usual. Once installation is complete, click on the Finish button in the Install Application on Terminal Server wizard. WIN2. 8BOX< /google>. If the application is designed for multi- user use it is now ready for use by remote users via Terminal Services. Applications which are not multi- user compatible may need to use compatibility scripts. For example, user Bill might have drive letter E: mapped to C: \users\bill\data while user Joe would have E: mapped to C: \users\joe\data. Windows Server 2. System. Root%\Application Compatibility Scripts. Root. Drv. cmd maps a drive letter to the home directory of the user executing the script enabling the trick outlined above to be performed automatically. By default the script converts the following paths to the corresponding environment variables. Path Environment Variable. All Users: Startup COMMON. The next chapter will look at using Remote. Apps display remote applications in their own windows on a client desktop. Glad you were a able to figure this one out. I figured out the permission thing, so now users cant install program or change services to stopped/running etc. But NOT to install programs? She doesn't know how to get into the actual Services window. She does it from the software. But not install, or shutdown/reboot the server?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |