Software Deployment

Here's what I do usually for Shortcuts packaging to have an advertised shortcut,

1. I'd request for the EXE and URL file. At least they should provide the EXE or ICO file for ARP icon and shortcut icon. You can create a URL yourself provided you have the FQDN target (eg. ""testserver.testdomain.com\myapp.exe"
2. Create a component, set the install dir to the app (for example Reference Manager)
3. Add the URL file to this component.
3. Create an advertised pointing to this URL in the same component.
4. Done other changes and compile your MSI. (you may want to include icon in ARP entry)
5. As long as you have access to the server that the exe resides, you will not have any issues.

Sometime, you dont have access to the server so of course you have issues like icons missing etc,you can test test by directly accessing the server and see if you can see/execute the EXE.

Hope this helps.

The above seems needlessly complicated.

Icons are read at install-time. If you are deploying using the local System account, that account has no network access and thus no access to the icon.

- Use an icon editor to extract the icon you want to an .ICO file
- Edit the relevant entry in the Shortcut table to point at the .ICO file.
- Compile

well it depends. if the MSI contains only a shortcut to a network drive, with no files, then this is what I do, at least to have an advertised shortcut. im not sure if there's any other better approach. and its easier to ask the client\requester to provide you with the exe because most of the times, we dont have access to their server. the exe itself contains the icon hence save the hassle to extract, etc

Just my 2 cents.

That doesn't make sense. If the s/c points to a UNC and is installed by the System account, how will it get the icon? It has to be extracted and included with the package.

What i referred to was the method i use to have an advertised shortcut package. But I agree with you that if we dont have access to the UNC then we wont get the icon and to get the icon even without access to the server, we would need the icon included in the package. Most of the times i ignore this because the package will be installed to a group of users with access to the server.

Thank you for all help, but I still have some questions.
I’m still trying to get the icon to show even if the user don’t have access to the share.

So I extracted the icon from the exe file, and added it to the msi package under C:\program files\program1\icon1.ico and pointed the shortcut icon to the same file. But still the icon doesn’t show.

Do I have to add the icon in a different way?
//johan

What package tool are u using? WPS or IS?

If IS, just rights click the shortcut and click on Change Icon, point to the icon file and save/compile. WPS? hmm i cant recall.

If you edited the Shortcut table by hand, did you remember to add the icon to the MSI's Binary table?

I’m using Wise Packge Studio and the Windows Installer Editor.

This is how I have done it:
· I have opened my package.
· I have clicked the Shortcuts link on the left panel.
· I have clicked the “Add” button.
· I have marked the Command line radio button and entered \\server\share1\file.exe + a shortcut name.
· I have marked a shortcut destination directory
· I have clicked the new icon button, browsed my local drive for the icon.
· I have tried to install the icon file in the same path as on my local drive.

But still when I install my package I don’t get any icons for the shortcut.
I haven’t edited the shortcut table by hand.
//johan