New Boundary Support Forum
Home      Members   Calendar   Who's On
Welcome Guest ( Login | Register )
      



Automatically deleting obsolete shortcutsExpand / Collapse
Author
Message
Posted 8/4/2006 6:40:29 AM
Junior Member

Junior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior Member

Group: Forum Members
Last Login: 7/25/2007 6:29:22 AM
Posts: 16, Visits: 19
Is there a quick way to have an application's shortcut deleted from the user's StartMenu when he is not a member of a certain group anymore?

We deploy our packages based on group membership and put NTFS permissions on the program folders. When the user is removed from a group, he cannot access the program folder anymore but the shortcut stays where it is. It would be nice if the shortcut would disappear automatically. We do not want to uninstall the entire package because some are rather large and computers are used by numerous users, all having certain software needs, so we want to avoid large packages being uninstalled and re-installed all the time. 

For now, the quickest solution I found is to create another package that uses the Deleted Items folder which contains the shortcut to delete and to create another group rule ("security group" "groupname" = false), but having a few hundred applications this really is a time consuming solution.

Regards,

Raymond 

Post #1351
Posted 8/4/2006 12:12:23 PM


Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Moderators
Last Login: 8/8/2008 12:14:02 PM
Posts: 657, Visits: 793
Your solution is probably the best available.  Some work is going to need to be done in order for shortcuts to be removed, and matching Packages that do so with Configuration Groups is a good solution.

One thing that you may want to look at is the new MEMBER_OF operator, available in version 7.0.3 and later:
http://www.nbtnet.newboundary.com/download/support/kb.htm

It might make making the Configuration Groups a little bit easier.  An example rule in your case might look like:

NOT DomainUserName MEMBER_OF "Domain\AppGroup"



New Boundary Technologies Support
support@newboundary.com

Post #1352
Posted 8/8/2006 12:49:44 AM
Junior Member

Junior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior Member

Group: Forum Members
Last Login: 7/25/2007 6:29:22 AM
Posts: 16, Visits: 19
We have solved the problem another way. We just made a big KixTart-script that contains the following:

IF NOT INGROUP("Group1")
 IF EXIST ("%USERPROFILE%\Menu Start\App1.lnk")
  DEL "%USERPROFILE%\Menu Start\App1.lnk"
 ENDIF
ENDIF

IF NOT INGROUP("Group2")
 IF EXIST ("%USERPROFILE%\Menu Start\App2.lnk")
  DEL "%USERPROFILE%\Menu Start\App2.lnk"
 ENDIF
ENDIF
and so on...

This is run as a Prism-script, using the RUNH-tool, making the execution of the script completely invisible to the user. The task is then set to run at every logon, in the context of the current user. This is much quicker to deploy and less of a hassle to update compared to making an extra package for every application.

Regards,

Raymond


 

Post #1353
« Prev Topic | Next Topic »


Reading This TopicExpand / Collapse
Active Users: 0 (0 guests, 0 members, 0 anonymous members)
No members currently viewing this topic.
Forum Moderators: New Boundary Support

PermissionsExpand / Collapse

All times are GMT -6:00, Time now is 5:28pm

Powered By InstantForum.NET v4.1.3 © 2008
Execution: 0.391. 11 queries. Compression Enabled.