Creating allusers shortcuts to folders by scripting
Hi all, first post after lurking for a while .. and I have a question that might be simple for more experienced packagers but I've been struggeling for a while now ..
Quite simply, how do I make shortcuts in the all users profile to folders on C:\ or elsewhere?
To clarify my situation a little, I have repackaged several apps using WPS that have been deployed using AD .. while our users work in a lockdown environment. Some packages are repackaged old software (.. 98 and even 3.11 programs) which have data dirs and so on located on C:\ Now my task is to update some of my packages so that the Start menu entries of these apps also contain links to some of these data folders.
I've tried several ways of getting this to work but none of what I've tried so far has been successful - except one which I don't like - to run a short wisescript under execute deferred with the paths and links hardcoded. I couldn't get wisescript to read the Windows Installer properties I had created. Actually, I'm not even sure if I created them correctly. Which leads to a new question, how do I create or set a property so that it contains any of the paths in my Directory table?
If I could set a property like that correctly, how do I get that value passed to a wisescript running in deferred? As I understand it it must run under deferred because of our lockdown OS configuration.
I found this wise KB article but its only partly helpful.
Or is this really not the best way to do it? Should I rather capture my apps over again and create the folder-links I need before comparing snapshots? Or wouldn't that work?
Any help greatly appreciated.
Quite simply, how do I make shortcuts in the all users profile to folders on C:\ or elsewhere?
To clarify my situation a little, I have repackaged several apps using WPS that have been deployed using AD .. while our users work in a lockdown environment. Some packages are repackaged old software (.. 98 and even 3.11 programs) which have data dirs and so on located on C:\ Now my task is to update some of my packages so that the Start menu entries of these apps also contain links to some of these data folders.
I've tried several ways of getting this to work but none of what I've tried so far has been successful - except one which I don't like - to run a short wisescript under execute deferred with the paths and links hardcoded. I couldn't get wisescript to read the Windows Installer properties I had created. Actually, I'm not even sure if I created them correctly. Which leads to a new question, how do I create or set a property so that it contains any of the paths in my Directory table?
If I could set a property like that correctly, how do I get that value passed to a wisescript running in deferred? As I understand it it must run under deferred because of our lockdown OS configuration.
I found this wise KB article but its only partly helpful.
Or is this really not the best way to do it? Should I rather capture my apps over again and create the folder-links I need before comparing snapshots? Or wouldn't that work?
Any help greatly appreciated.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
jib
19 years ago
Posted by:
VikingLoki
19 years ago
They're in an odd place, so don't feel dumb.
When you are looking at the file structure tree in WPS, instead of finding profiles in "C:\Documents & Settings" yadda yadda yadda, they're under C:\Windows\Profiles\.
Why profiles are there instead of where they end up on a W2K/XP machine is a matter of debate, but that's where they are whenever you are looking at the directory tree in WPS. Don't worry, they end up in the right place.
When you are looking at the file structure tree in WPS, instead of finding profiles in "C:\Documents & Settings" yadda yadda yadda, they're under C:\Windows\Profiles\.
Why profiles are there instead of where they end up on a W2K/XP machine is a matter of debate, but that's where they are whenever you are looking at the directory tree in WPS. Don't worry, they end up in the right place.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.