Launching mstsc.exe using Slingshot and Generic TCP Proxy webApps

Launching mstsc.exe using Slingshot and Generic TCP Proxy webApps

Issue:

The old SSLVPN RDS webApp to launch mstsc.exe no longer works after upgrading to 6.4, due to the Java plug-in going away with modern browsers, and other security enhancements.


Solution:

Create a set of webApps that open a TCP proxy port, and use the new Slingshot application launcher to start mstsc.exe.* **

*This option requires opening the chosen port in the firewall, between the user's workstation and the UW relay.
**SSO is not supported with the Microsoft RDS Client, due to security changes by Microsoft.


Please use the following steps to configure the two webApps necessary to open the TCP proxy port on the UW relay, then launch mstsc:


Create the webApp to open Proxy port:

Create Host object:
  1. Open webAdmin
  2. Right-click on Applications Admin
  3. Choose Create Host
  4. Enter the Host Name that will appear in webAdmin
  5. Click Next
  6. Click Close on the success message

On the Host object:
  1. Enter the host address of the server
  2. Enter the RDS connection port of the server, 3389 is the default RDS port

Create webApp object:
  1. Open webAdmin
  2. Right-click on Applications Admin
  3. Choose Publish Other Application
  4. Enter the Application Name that will appear in webAdmin
  5. Click Next
  6. Click Close on the success message

On the webApp object:
  1. Select the Properties tab
  2. Set the Application Type to Generic TCP Proxy
  3. Set External TCP Port to 3390
  4. Set Time to Live to 45
  5. Click the green + next to Assigned Host, and browse to the host previously created
  6. Click the green + next to Assigned Relay, and browse to your relay objects
  7. Select the Options tab
  8. Check the box for Keep Session Alive
  9. Click the Save button

Create/assign the link for this webApp:
  1. Select the Access Control tab
  2. Enter the Link Name that will appear in webAdmin
  3. Enter the Link Description that users will see under the tile that appears on their desktop, as this is the link that will initate the whole RDS process, this should be named appropriately
  4. Click the green + next to Menu, and browse to the menu folder you would like the link to appear in
  5. Click the green + next to Assign To, and browse to the users you would like to have access to the link
  6. Check box to Open link in new window
  7. Click the Save button
  8. Click OK on the warning about the link being created.
  9. Refresh webAdmin


Create Slingshot webApp to launch mstsc.exe:
  1. Open webAdmin
  2. Right-click on Applications Admin
  3. Choose Publish Slingshot Application
  4. Enter the Application Name that will appear in webAdmin
  5. Click Next
  6. Leave context set to Use Default Context
  7. Click Next
  8. Enter the path to the application: c:\windows\system32\mstsc.exe
  9. Enter the Command Line Parameters to connect to the proxy port: /v:PORTALADDRESS:3390
  10. Click Next
  11. Leave virtual App field blank.
  12. Click Next
  13. Select the Menu where you would like the link to appear in
  14. Leve box checked to open link in new window
  15. Click Next
  16. Select the users you would like to have access to the link
  17. Click Next
  18. Click Done on the success message


Set the Slingshot link to not be visable to users:
  1. Open webAdmin
  2. Expand Link-Menu admin
  3. Browse to, and select, the Slinghost link created earlier by the wizard
  4. Select the Options tab
  5. uncheck all the options for the Link Properties field
  6. Click the Save button


Set the Proxy webApp to call the Slingshot webApp, after opening the proxy port:
  1. Open webAdmin
  2. Expand Applications Admin
  3. Select the Slingshot webApp object created earlier
  4. Highlight and copy the webApp's dn from the dop of the page, example: cn=Slingshot mstsc-App,o=stoneware
  5. Select the proxy webApp object created earlier
  6. Paste the previously copied dn into the Startup URL field, example: cn=Slingshot mstsc-App,o=stoneware
  7. Preface the dn in the Startup URL field with: /StartWebApplication/
    Example: /StartWebApplication/cn=Slingshot mstsc-App,o=stoneware
  8. Click Save

Logout/Login to UW and test the webApp

    Can't find the KB

    Unable to find the KB to address your issue ?  

      • Recent Articles

      • Lenovo Unified Workspace End-of-Life Questions and Answers

        Will the shutdown of LUW servers and access to downloads affect my server licensing? No, the shutdown of the customer servers and access to the product and licensing downloads will not affect your server licensing. This license is downloaded and ...
      • How do I determine my Unified Workspace license expiration date?

        The best method for determining the licensing information including the expiration date of your Unified Workspace license: Login to your 8090 management console on each server This may take remoting into each LUW server and relay, opening a browser, ...
      • Lenovo Unified Workspace 7.0.2.13 Released

        Highlights of Unified Workspace 7.0.2.13 Before you install: Please view the installation notes here. 7.0.2.13 requires a 7.0 license file. Below is a list of enhancements and fixes released in Unified Workspace 7.0.2.13 Fixed external storage ...
      • LanSchool Documentation Guides

        LanSchool Classic Teacher Console The LanSchool Teacher Console is the interface teachers will use to manage their classroom and students. It contains all the tools necessary for a teacher to effectively interact with students and create a ...
      • Lenovo Unified Workspace 7.0.1.41 Released

        Highlights of Unified Workspace 7.0.1.41 Before you install: Please view the installation notes here. 7.0.1.41 requires a 7.0 license file. Below is a list of enhancements and fixes for Unified Workspace 7.0.1.41 Updated Log4j Updated Java Updated ...
      • Related Articles

      • Using Terminal Server Proxy webapps with Round Robin DNS

        My Terminal Server Proxy webapp does not always connect to my backend server, when using the Round Robin DNS name. If we go directly to one of the relays, we can connect 100% of the time. Assign individual DNS names to your relay IP addresses.  ...
      • Slingshot installation error swlauncher.exe is not marked for installation

        Issue: The user receives an error launching Slingshot webApps. The error is a Windows error message: Error 2753 The File ‘swlauncher.exe’ is not marked for installation. Solution: The webNetwork Slingshot utility is already installed on the ...
      • How to SSO into Microsoft MSTSC Native Client

        A few years ago Microsoft changed the RDP client to not allow that native client ( mstsc.exe ) to accept command line parameters for authentication along with removing the same feature from the saved .RDP file. This means that when you use the native ...
      • js error when launching RDP webapps

        The customer is getting a js error when launching an RDP webapp. The error says: Expected end of statement and type mismatch ’startRDP’ The customer had double quotes in the parameter list for the webapp. This caused the issues. Once removed, things ...
      • Slingshot can't launch application

        The customer has a Virtual Application launcher webapp configured that uses Java and want to switch to the new slingshot method. They changed the webapp to Local Application but when it runs it says it can't find the file. They are trying to drop ...