Hi guys!
Let's start by describing the situation:
App name: Firefox
Permitted Groups=APP VIRTUAL FIREFOX
ThinApp VOS: 4.7.3
Logon script: thinreg.exe \\foo\exe\firefox\firefox.exe
I registered the application for users with thinreg (streaming execution) with a logon script defined at the AD user object so everytime a user logs on, that logon script is executed (well, that is obvious). But then I removed a user from the only permitted group, APP VIRTUAL FIREFOX.
The user still have the icon but he doesn't have access anymore to the application anymove, he's receiving a box message saying permission denied.
So here a few questions for you guys:
- At the logon time, if the application was already registered with thinreg, how thinreg gonna react? Is going to try registering but stop because the application is already registered?
- In my case, the user got removed from the groups but the icon is still here. I thought thinreg what unregistering the application if the user wasn't authorized anymore. So when you want to unregister the application, what are you guys doing?
That thing of unregistring the application every time at the logon is a huge overhead in my opinion. I know thinreg loads itself into the memory then unload. I cannot ignore the overhead created by this process (especially for VDI environment) and I want to avoid deploying the thinapp SDK on the workstations.
I'd be glad to hear about the solution you guys implemented in your companies!
Thanks for your anwers!
palpe