All Users shortcut uses wrong argument
Updated: 23 May 2010 | 3 comments
Hi,
I have a shortcut set to be created on the Desktop, it is set to launch an installed application which then uses a file defined in the Argument. From an earlier posting I have been able to set it so that when a new users logs onto the PC and uses the shortcut for the first time it will install the relevant file in the users profile and update the registry. But the shortcut will then try and run the file installed for the first user, as they haven't got permission for that users profile it fails.
The common runtime is installed in Program files and the separate user file is installed into the users Local Appdata folder.
Any suggestions gratefully received.
Tim
discussion Filed Under:
Comments
You'll need to make sure any
You'll need to make sure any userprofile files gets repaired.
Are you installing per- user or machine?
Is the Shortcut installed under the user's desktop or under AllUsers?
Did you set a HKCU registry entry as the keypath for the component holding the file located under LocalAppDataFolder?
Once our application has been
Once our application has been run then it writes back to the file in the User profile so I don't want to force a repair each time the user uses it otherwise they will lose those changes.
I was trying to set it so the common files are installed per machine and then the other file per user.
The shortcut us installed under AllUsers desktop.
I have set the HKCU entry as the keypath for the component, this was how I made certain the files got installed originally the first time the user used the shortcut.
It will need a repair each
It will need a repair each time due to the way you've designed it.
You could always create an executable wrapper, ex.
shortcut launches a vbscript, the vbscript makes sure the file exist in the users profile (the first self-repair should fix this) and then executes the command of choice.
Would you like to reply?
Login or Register to post your comment.