Is there a way as an admin I can add a user terminal services bookmark for them without logging on as them?
Only way I can see doing it is creating a unique role for every user with their assigned Terminal services bookmark.
Any advise please?
Solved! Go to Solution.
I am afraid, we are choiceless. That is the only way to permit user's create thier own bookmarks. If that's not what they need OR if your users needs everything to be done by the administrator, then I guess the administrator needs to create new bookmarks for each servers on the SA which definetly is not going to be that easy.
However - educating them and convincing the users is the best way to get around this.
Hope the above answers your question.
Please mark this post as 'accepted solution' if this answers your question that way it might help others as well, a kudo would be a bonus thanks
Jitender K, I just want to let you know that I have an ER open with Juniper to allow user defined Terminal Services bookmarks to work with Java RDP clients like Hoblink. The number is 29755. I've been asking other customers to have their company names added to the ER to get some movement going.
Hi,
You can enable the option which will allow the users themselves to add a terminal services bookmark and use it when required.
- Go to Role > Terminal Services > Options
- Under "Options" you will see Users can define their own Terminal Services sessions)
Now, everytime a user logs into this, he / she can add any bookmark to any machine which he / she wants remote access and use it.
NOTE:
Please ensure that you have proper ACL's for those terminal services session created by the users on the SA. This can only be done by the admin.
For example:
If you have few users who can remote access into any computers between 10.1.1.1 - 10.1.1.50, then please have an ACL to allow remote access to this range of IP's. This way, admin really doesn't have to create 50 terminal services bookmark. Any user can connect to the SA and add thier own session bookmarks to the above 50 IP's and then remove it whenever required.
Please mark this post as 'accepted solution' if this answers your question that way it might help others as well, a kudo would be a bonus thanks
Yeah Ive enabled that method for ICT but our users like to be spoon fed and would prefer the bookmark to already exist. What way do you recommend I manage this?
cheers
Graham
I am afraid, we are choiceless. That is the only way to permit user's create thier own bookmarks. If that's not what they need OR if your users needs everything to be done by the administrator, then I guess the administrator needs to create new bookmarks for each servers on the SA which definetly is not going to be that easy.
However - educating them and convincing the users is the best way to get around this.
Hope the above answers your question.
Please mark this post as 'accepted solution' if this answers your question that way it might help others as well, a kudo would be a bonus thanks
I am afraid, we are choiceless. That is the only way to permit user's create thier own bookmarks. If that's not what they need OR if your users needs everything to be done by the administrator, then I guess the administrator needs to create new bookmarks for each servers on the SA which definetly is not going to be that easy.
However - educating them and convincing the users is the best way to get around this.
Hope the above answers your question.
Please mark this post as 'accepted solution' if this answers your question that way it might help others as well, a kudo would be a bonus thanks
AJA has the right of it in that there is no easy option if users choose to not make their own bookmarks.
some things to look at, that may or may not be applicable in your envirnment:
pulling user attribute, if applied on the server, and setting the bookmark as <userAttr.attributeName>
use rdp launcher, only, and not have any bookmarks
I use the approach suggested by zanyterp.
In our authorization LDAP, we have a multi-valued attribute which contains the names or addresses of RDP destinations allowed for the user. We have a back-end system which allows them to edit this attribute.
The user then is presented with as many RDP bookmarks as they have defined. However, the configuration shows only one bookmark, to <userAttr.rat> (rat is the name of the attribute - don't ask).
Ken