Hi,
is there a way to use the microsoft RDP client without the juniper Active X stuff or java applets?
Reason I want to do this I have certain problems that i have encountered. These problems do not occur when I use the microsoft MSTSC client...
thanks!
If you enable "Remote Desktop Launcher" in the Terminal Services options on the user role, this enables an RDP browsing bar at the topmost section of the Terminal Services bookmarks in the User's Bookmark Page and if you launch your RDP sessions from this launcher by typing in the IP or host name of the host you are connecting to, the connection will be launched via the native mstsc.exe process instead of the Juniper Terminal Services client which is used for any Terminal Services bookmarks.
Be sure that you have a Terminal Services Access Policy that allows access to multiple hosts, if necessary, by defining an ACL that allows access to all hosts in the entire subnet such as 192.168.0.0/24.
Actually, this does not guarantee 100% of the time that the system will use the native RDP client to launch the session. I'm having mixed results after further testing. It seems that if the ActiveX control with the Setup Client gets installed that we always try and download and install the Juniper Terminal Services Client without trying to launch the native RDP client and that it does work sometimes if you use Java as the fallback delivery method, but it is not consistent.
I would have to test this further and have more consistent results before confirming that enabling the Remote Desktop Launcher actually invokes the native RDP client.
You'd be better off using Network Connect to have it secure traffic to your remote desktops because then, you could launch mstsc.exe yourself and this would guarantee you'd be using the native RDP client every time.
Hi kmaybe,
thanks for your reply! I have some problems with the dstermserv.exe in combination with MS Easy Print on X64 systems.
Is there any x64 version available?
Thanks!
Hi,
I would recommend using network connect or Junos pulse to setup a L3 VPN tunnel to the terminal servers, once the L3 VPN is established, you can use mstsc.exe to launch the remote terminal servers
Thanks,
Jay