Recently a British customer TRM has asked them to TRM
"I have to restrict our users the execution of two instances of a particular application. How can I do this? "
There was a bit of team puzzle of how to do it ...
- load evaluator?
- some kind of policy?
- can limit users to one instance of the application could be adjusted to limit a user to 2 cases?
Thus, the obvious candidate is the published application setting to limit a user a single instance of the application; here's a screenshot of this option taking XenApp 6.5:
Would not it be great if there was a UI option to set a limit flexible per user for published application? Unfortunately, there seem to be such an option, even "under the covers".
The desire of the customer to limit the application to the user by two bodies was due to the application of resource consumption, to be held in check for the benefit of the wider user community. However, this was balanced against the flexibility of the user community needed to run multiple instances of the application. To simplify administration of the client did not want to get up a separate silo of XenApp servers just for this application
Based on these requirements we had several suggestions for the customer :.
1. Custom Script
Write a script that checks for the executable in question, and if two instances are already running to the requesting user, prevent him from other instances of launch. Publish script for users rather than the native application.
2. Publish twice
Post the executable of the application twice, and use the "allow only one instance of application for each user".
I am interested to know if anyone else has had this business or technical requirement and the way they handled this. are there any third-party products that could do it? what do you think?
0 Komentar