Execu/Tech Systems, Inc.
IndexBookmarkPrint This Article

Home > Execu/Suite Hotel PMS > Setup Execu/Suite Hotel PMS > Installation > Running as RemoteApp

  This is a general guide for running the Execu/Suite software as a RemoteApp and is provided as a reference for those who are not familiar with RemoteApp. We can't provide any assistance outside of this document. We are not RemoteApp experts.

RemoteApp is not an Execu/Tech product and it's configuration is the responsibility of the customer's IT professionals. 

Hopefully this will help. These instructions were created using information provided by Google searches combined with the Execu/Suite shortcut instructions. This guide is not a replacement for doing your own Google search to learn how RemoteApp works. There are many step by step guides as well as videos that provide the same information we used to create these steps.

RemoteApp Information

These links will provide you with information on what RemoteApp is and how to use it.



Creating an Execu/Suite RemoteApp in Windows Server 2008 / R2

Each installer you create should be named for the terminal (Terminal Name), like HOTEL 01, or POS 02, etc. Use this in place of the “User Name” mentioned below. This page mentions the terminal numbers in the “Installing on the Client” section in this document - Software Installation . Every terminal has a 2 digit terminal number specified as part of the command line arguments. Once completed, the installers can be run at each terminal. Windows credentials will be required but you can save them so they only need to enter the ExecuTech user credentials the next time they run the app.
  1. Make sure the server is configured to support RemoteApps.

  2. On the server, click Start >Administrative Tools >Remote Desktop Services > RemoteApp Manager.

  3. The RD Session Host Server Setting must show the proper domain. Using the menu to the right, click Add RemoteApp Programs.

  4. Click Next.

  5. Click Browse and select wrun32.exe on the customer’s drive in the HOTEL folder.

  6. Click Properties.

  7. Change RemoteApp program name to be the same as the Terminal Name. 

  8. Change the Alias to the same as the Terminal Name.

  9. Click Always use the following command-line arguments.

  10. Add the command line arguments for the proper terminal and purpose (hotel or pos) using the instructions in the “Installing on the Client” section in this document - Software Installation.

  11. Click Ok.

  12. Click Next then click Finish.

  13. Click the newly created RemoteApp.

  14. In the menu to the right, click Create Windows Installer Package.

  15.  Click Next.

  16. In the Shortcut icons section, check Desktop and Start menu folder.

  17. In the field for Start menu folder, type “ExecuTech”.

  18. Click Next then click Finish.

  19. Repeat this for each terminal. 

  20. If desired, you can install signing certificate and an SSL to remove any security warnings during installation and running at the client. We don't offer assistance with this.

Creating an Execu/Suite RemoteApp in Windows Server 2012 / R2

Based on Microsoft's published enhancements in Remote Desktop and RemoteApp in Server 2012 R2 over Server 2012, it seems that you will have a vastly superior experience with Server 2012 R2. However, you and your IT professional responsible for this decision.

The instructiuons are similar to the ones for 2008, but follow the steps:

Publish: http://social.technet.microsoft.com/wiki/contents/articles/10817.publishing-remoteapps-in-windows-server-2012.aspx 

Distribute: http://social.technet.microsoft.com/wiki/contents/articles/14488.distribution-of-remote-apps-and-desktops-in-windows-server-2012.aspx

Article ID
Last Modified
 3/18/2014 10:07 AM