I have ABOBE, VISO and MS Project all created as a thinapp and they work fine. We are using AD groups to restrict who can run these. The issue we are having is when the thinapp is presented to a pool of desktops and the use is not in the proper AD group. Instead of using VISO viewer the OS see the full install of VISO and attempts to use that and is subsiuqently denied. From a end-user standpoint we can't tell everyone to right-click and use this application everytime.
Is there a way around this or are we stuck?
Craig
Craig,
Have you tried registering the ThinApp?
Minus the steps during the standard package build no, we put the specific AD group that has access and that’s about as far as we go. We were hoping for a solution to apply to the entire environment vs per user.
Sounds like you would be better of register on a per user basis rather than using the View Manager ThinApp entitlement. This way the end-user's group membership will decide what gets registered. Thinreg.exe supports AD group membership.
More info on registering ThinApp packages using thinreg.exe:
http://pubs.vmware.com/thinapp4/help/wwhelp/wwhimpl/js/html/wwhelp.htm?href=thinreg_utility.html