Just installed 7.0R1 on my test box and things are looking good so far. The Hob RDP applet is installed by default and the good news is that it's quick - properly quick. It also lets users configure per-session resolution and colour depth options which is a useful step forward.
However, similar issues still exist as in 6.x in terms of consistency of the user-experience across platforms - which is very frustrating.
For example: the Quick Launch functionality for Terminal Sessions launches Hob RDP on Linux and Mac OS clients, but launches the older platform-specific client for WIndows users. I cannot force it to use Hob for Windows users too, so I can't deliver a consistent user-experience with just one set of documentation.
Terminal services bookmarks only work for Windows clients, not for Linux or Mac OS X clients.
Frankly, this is a bloody mess, and forces me to write several different sets of instructions for users of different platforms, or to consider forcing terminal services through JSAM, the setup of which is another nightmare.
Any ideas? Comment from Juniper would be welcome too (obviously...)
I agree completely. The Hoblink client is much better in terms of performance and features when compared with the ProperJava RDP, but it is a major let down to not be able to use it for user-created bookmarks. I've opened a case with Juniper to validate that there is no way to do this.
I've opened a case with Juniper to validate that there is no way to do this.
Do you got any answer from Juniper about that?
Thx and br,
"Terminal services bookmarks only work for Windows clients, not for Linux or Mac OS X clients."
You are correct that user-created bookmarks are Windows-only (ActiveX control); however, you should be able to define a bookmark to always use Java when you create the bookmark as an admin (there is a radio button that allows for the applet to always be used and one for use as a fallback). Is this not what you are seeing?
Regarding the ability to always use the applet with the quick launch bar, I would recommend working with your SE for an enhancement to add this to the option list when enabling Java.
@mkelly_uwyo: It is not just for the quick launch bar; it is for the quick launch and admin-created bookmarks.
User created bookmarks, however, are available only for Windows users, yes.
"You are correct that user-created bookmarks are Windows-only (ActiveX control); however, you should be able to define a bookmark to always use Java when you create the bookmark as an admin (there is a radio button that allows for the applet to always be used and one for use as a fallback). Is this not what you are seeing?"
This is exactly what I'm seeing, and it's exactly the behaviour that I think is a bit of a mess, particularly when you're trying to deliver the same experience to users regardless of their client platform. It seems very odd to me that I can force admin bookmarks to use the applet (no use to me, since I actually need the users to create their own bookmarks) but I can't click a tickbox somewhere to force user bookmarks to behave the same way.
As it is, I have to write two sets of documentation, and say "If you're using Windows, do this, if you're using Mac OS/Linux, do something else". It doesn't create a good impression, especially when half the userbase know very well that Java can be used to deliver a consistent cross-platform experience. I will bundle all of this up into an enhancement request when I get the time.
[Edit: I'm the original poster - I've just got my accounts crossed up as I have one for IDP and one for IVE...]
One of the points is the Premier Applet feature is designed to work as a fallback mechanism for situations where windows client cannot work and its a fallback because it needs an additional license ($$$) which is per user and most admins will want to use the Windows client where possible and only fallback to the Premier Java Applet when there are no other options.
However you have a very valid point that some admins just want a consistent user expereince and are willing to pay the additional cost, so this should be an admin controlled option.