Terminal Server Application Installation Tips

Make sure your Windows Server OS and Active Directory Infrastructure are setup securely.

Make sure the application you want to install is supported in a Terminal Services Environment, and on your specific version of Windows Server. Although it is possible to get just about any 32 bit Windows application to run on a Terminal Server, it's best to check with the software manufacturer before testing your application, as they may have specific instructions for a terminal services installation.

Always test the software you plan on deploying (via Terminal Services or Citrix) in a lab environment before installing it on a production application server.

Make sure you have a backup (preferably image based) of your production application servers before installing new programs.

Make sure your terminal server is in Application Server Mode (Windows 2000 Server) or has the role of Terminal Server (Windows Server 2003) before installing your software (unless this server is used specifically for remote administration)

Make sure the terminal server is in "Install Mode" before installing software. This can be accomplished by initiating the install routine via "Add/Remove Programs" or by manually placing the server in "Install Mode" with the cmd prompt utlility "change user /install". After the install is complete you place the server back in "execute mode" via "change user /execute".

If you're using Citrix MetaFrame Presentation Server XP Enterprise Edition, Presentation Server 3.0 Enterprise Edition, or Presentation Server 4.0 Enterprise Edition, use the Installation Manager to deploy your applications from an Administrative Installation Point to selected servers in your farm.