Shortcut points to nowhere?
Hi there,
I have an app that installs a few db drivers, ini files, etc, but it does not install the bin files for the app. They are located on a network share somewhere. This app is deployed with SMS.
Problem is this, the package creates 5-7 shortcuts to files on the network. All the users have access to this location. When SMS deploys it, it fails because SMS does not have access to the location. How can I instruct the package to ignore this shortcut creation error and create them on the users HD regardless of the access restriction?
If this could work, the app would be fine because like I said, the users have access.
Thanks,
theLane
I have an app that installs a few db drivers, ini files, etc, but it does not install the bin files for the app. They are located on a network share somewhere. This app is deployed with SMS.
Problem is this, the package creates 5-7 shortcuts to files on the network. All the users have access to this location. When SMS deploys it, it fails because SMS does not have access to the location. How can I instruct the package to ignore this shortcut creation error and create them on the users HD regardless of the access restriction?
If this could work, the app would be fine because like I said, the users have access.
Thanks,
theLane
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
laszlo
17 years ago
Hi,
is that a msi installation?
if yes, are the shortcuts advertiseded?
if no, take them out of the shortcutsection and put them into the file section (like windows\profiles\all users\desktop\app.lnk).
regards
martin
is that a msi installation?
if yes, are the shortcuts advertiseded?
if no, take them out of the shortcutsection and put them into the file section (like windows\profiles\all users\desktop\app.lnk).
regards
martin
Posted by:
aogilmor
17 years ago
a better idea (if I may be so immodest) is to populate properties with the shortcut paths you want to use, i.e. z:\apppath\app.exe, then put that property into the target field in the shortcut table.
This way you don't have .lnk files that you can't see the contents of, and avoids "hard coding" paths into the lnk files.
This way you don't have .lnk files that you can't see the contents of, and avoids "hard coding" paths into the lnk files.
Posted by:
edocshare
17 years ago
If I am following you correctly, that is the way it is currently setup. The path to the network location is stored within a variable and the variable is being used as the target in the Shortcut table.
I haven't tested laszlo's idea yet. have to wait for the SMS admin now <sigh>
thanks
edoc
I haven't tested laszlo's idea yet. have to wait for the SMS admin now <sigh>
thanks
edoc
Posted by:
edocshare
17 years ago
ORIGINAL: laszlo
is that a msi installation?
if yes, are the shortcuts advertiseded?
if no, take them out of the shortcut section and put them into the file section (like windows\profiles\all users\desktop\app.lnk).
Thank you. This solution worked great!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.