I've been testing North Star with much interest. However, managing who's is getting what application is a bit more difficult then with e.g. Softgrid. I came up with the folllowing solution:
I use PermittedGroups in the Package.ini to control what AD group has access to the app. This works fine.
I then run "thinreg.exe <package path\<package.exe>" in a logon script to register the application on each users desktop if he/she is also in the appropriate group.
If I remove a user from the AD group, Thinreg.exe unregisters the app as it should.
So far so good. However, soon after, I added another two users to the AD group for testing, but the icon didn't turn up on thier desktop....? I ran the thinreg.exe command manually without success. No error message appeared. Thinreg.exe also returned a 0 to the VBscript logon script. The app didn't register whatsoever for those users.
I then tried thinreg.exe /u to unregister the app first, even though it didn't register before. After that I ran the script again without /u. The app suddenly registered and the Icon appeared. This problem has happended intermittently on a few test systems since. As mentioned before, the only way I can register the app for the user is by running thinstall.exe /u first. This makes the logon script/thinreg.exe option quite unreliable.
Could this be a bug? Has anyone noticed similar issues with Thinreg.exe? Are there other options to control install/uninstall of virtual apps? I wish North Star had a Management Front End for this.
Cheers.