Skip to main content
InSource Solutions

TN IT178 Deploying a Read-Only InTouch Application



***  Internal Use Only  ***



This tech note details the challenges involved in deploying a read-only InTouch application.  In this case, one InTouchViewApp template is maintained.  The read-only clients sessions are running on the same terminal servers as the regular view clients.


  • Author: Rich Brooks
  • Published: 11/9/2015
  • Applies to: InTouch v11.1 and higher




  1. Start on the IDE from the development server.  Make the required modifications.  Check-in the template to save the changes.
  2. Export the master InTouchViewApp object from the IDE.
  3. Temporarily rename the master InTouchViewApp in the IDE.  Renaming is required to import a second copy of the same object into the IDE.
  4. Import the exported InTouchViewApp object back into the IDE.
  5. Rename the imported object to add an _RO suffix.
  6. Rename the master InTouchViewApp template back to what it was before the rename.
  7. Double-click the _RO InTouchViewApp object to launch the WindowMaker.
  8. Select Special – Configure- Remote Access.. from the menu.Pic1.png
  9. Click on the radio button for ‘Restrict all users to READ ONLY access’ and then click the OK button.
  10. Save and close the InTouch application.
  11. Go to the server with administrative access to ThinManager.
  12. Launch ThinManager and disable the read only terminals that are currently running on the servers.  The disable button is found on the Tools menu.
  13. Open Remote Desktop Services Manager from the Windows start button.Pic2.png
  14. Highlight and reset all of the read only sessions.  Wait for them to drop off the list before continuing.
  15. Return to the IDE from the development server.
  16. Undeploy and delete the read only instances of the InTouchViewApp.
  17. Delete the old read only InTouchViewApp template.
  18. Rename the new read only template by changing the _RO suffix to an _ReadOnly suffix.
  19. Create new instances from the _ReadOnly InTouchViewApp template as required.
  20. Deploy each of the instances separately.
  21. Return to the server with access to ThinManager.
  22. Enable the disabled terminals.
  23. Launch WindowViewer for each of the clients.
  24. Check to be sure everything looks ok from runtime.