To handle different program dependencies on start up we are using VBscripts to launch the programs.
If a program need HKCU settings these are added using a launch.vbs before starting the program.

The company I work for has configured all computers not to run VBS files, so as a workaround they have made their own extension and related this to VBscript files, and to run them they have to run wscript.exe with the file as argument.
All users are local adminstrators on their computer.

For the organizations core applications I want to set permissions on the shortcuts.
I want to set the permissions to for local administrator and Domain Users to Read\Browse\Execute and Full for Domain Admins.

I have tried to sett this on the Components for the shortcuts inside my MSI, but with the result that the permissions was also added to C:\ ? This made the installation fail since they no longer could copy files to [ProgramFilesFolder].

I have also looked at the possibility to use MMC and create a security template inf file, but this only set permissions on the actual file running ([SystemFolder]\wscript.exe) and not the .lnk.

I have thougt of making a vbscript and run it as a custom action.

An other thing about shortcuts running wscript.exe with arguments is that this is a preexisting file, and I cannot set it Advertised, how can I do this?

Anyone have any idea what would be the best approach for these issues?

Thanks in advance.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Windows Installer will automatically self-repair missing HKCU stuff on the user's 1st run, so I don't see the point of launching apps with a VB script.

Ennywayz, Google SetACL for setting permissions. Plop it into a custom action.
Answered 07/08/2005 by: VikingLoki
Second Degree Brown Belt

Please log in to comment