Create a Network Shortcut by Using a .LNK file or by Creating a Property
The first part describes how to create a .lnk file and to add that file to your Wise Project. (not best practices).
The second part describes how to create a property and set your WkDir to that property (best practices).
Why is the second part better than the first? The answer is simple: Maintaining.
Just imagine the work you'll have to do, if the network drive changes! Using the second part, you'll just need to change the value of the property.
Part 1. Create an add a .LNK file (Network Shortcut) to your Wise Project
Your VM, Virtual PC, or physical Wise Package Studio workstation, doesn't have any Network drives connected. (at least I hope not).
To create a .lnk file that points to a network drive, we need to create a Virtual Drive.
So, before you start all of this, you need to know the Network path for your shortcut (make note of the executable name).
Let's say the network path to the shortcut is Z:\Application\Package, and the executable is named setup.exe.
Step 1
Create a 'Virtual Drive'.
- Create a folder in the root of C: and name it test (You can pick any location that you want or name the folder anything you want, but this is just to fake a network drive).
- Create a new folder named Application inside the Test Folder.
- Create a new folder named Package inside the Application folder.
- Share the test folder.
- Now Map Z:\ Drive to that folder.
Now you have mapped Z:\drive to Application\Package.
Step 2
Create a setup.exe (or whatever your executable is called).
- Right click in the Package folder, select New and click on Text Document
- Rename that Text Document to setup.exe (make sure the extension .txt isn't there anymore).
It should look like below print screen.
Step 3
In this Step I'll create the Network Shortcut (.lnk file).
In Step 4 you'll have to add this .lnk file to your Wise project. For ease I created a folder Shortcut in the root of C:. (You don't have to create a folder just to create this shortcut, that is totally up to you, but I'll explain later why I do create a folder).
- Right click inside the folder Shortcut and select Create Shortcut
- Type or browse to the network executable, here it is:
Z:\Application\Package\setup.exe
- Give the Shortcut the appropriate name. I named it "Network Shortcut". ).
Step 4
In this step, I'll add the .lnk to the Wise Project, but first I will create a New Feature for this shortcut. This is not necessary, but I do it for documentation purposes and ease to find if ever needed.
- Start Wise Package Studio and open your project.
- Go to Setup Editor and select the Feature tab.
- Right click anywhere in the window. In that menu go to New and select Feature
- Name the Feature. I named it Network Shortcut (see below print screen).
- Click OK.
- Select Installation Expert.
- In the left column under Feature Details, select Files.
- In the right pane of the window, select the Feature you created in Step 3. Here it is 'Network Shortcut'.
- Now add the folder Shortcuts to the Wise project. (see print screen).
Here is why I created the folder Shortcut and added that folder to the Wise Project.
If your company has multiple 'Network Shortcuts' a folder that contains all these shortcuts is more organized and for troubleshooting purposes, there is only one folder to go to and through.
Step 5
In this Step, I'll create a shortcut pointing to the .LNK file.
- In your Wise Project select Shortcuts in the same column as where you selected 'Files' in Step 4.
- In the right window, select the correct feature 'Network_Shortcut', if not already selected.
- Click add, and create the Shortcut. Check the details and it should look similar as shown in the below print screen.
- Don't forget to select the correct Icon.
- Save your Wise Project and test the shortcut. Make sure you have that network connection though.
Part 2. Create a Property for a Network Shortcut.
In this part, I'll show you in just a few steps, how you can create a property and assign that property to the Shortcut. (so much easier and faster than Part 1).
I am using a Adobe product as an example.
Below print screen is to show what needs to get changed.
The Start in: path needs to change to the Network Path.
Right now it starts in "C:\Program Files\Adobe\" and the Network Shortcut is: "Z:\Application\Package\".
Step 1
In this Step, I'll create the Property, but first let's look at the existing shortcut.
- Open your Wise Project and select Installation Expert.
- In the left column select Shortcuts
- Look at the Shortcut Details that is currently there and notice the Working Directory.
It shows now, 'Program Files\Adobe'.
Let's take a look at the Shortcut as it is now in the Tables.
- Go to the Setup Editor
- Select the Tables Tab and scroll down to Shortcut.
- In the right pane of the window, scroll all the way to the right and you'll see the WkDir as shown in below print screen.
You'll see that the property assigned to the WkDir is now 'ADOBE'.
I'm going to create a new property and assign that to WkDir.
- Select the Product tab. Then select Properties in the left pane of the window.
- Right click anywhere and select New, then select Property
- You can give that property any name you like. I name it NETWORKSC (which stands for Network Shortcut). Give it a recognizable name.
- In the Value field: Type the whole path to your executable. Here it's Z:\Application\Package\ and click OK.
Step 2
Changing the WkDir.
- Go back to the Tables tab and scroll down to <Shortcut>
- Scroll all the way to right, in the right pane window and change the WkDir name to the property you just created. NETWORKSC.
Save your project and test.
Check the properties of the shortcut and you'll see that the Start in value has changed.
You see that Part 2 is much quicker and easier to do and better maintainable.

LNK files all the way!
We experimented with PROPERTIES for a while, but we kept having problems. In your example, the Z: drive has to be mapped to install your MSI. This is because using a property without the Z: drive mapped will not install long file names.
Also, using an LNK file, it is easy to update the one file using a transform and reinstall=all. If you try to update the PROPERTY with a transform, you would have to re-cache the transform on the local machine before calling the REINSTALL.
INI File Table
I've always enjoyed using the INI file table to create shortcuts
Looks interesting
Hi, This looks interesting to install shortcuts through ini file table. I woould like to know more about this. please share the same for benefit of all.
Piyush Nasa
Altiris Certified Professional (ACP)
INI File Table
I will dig around to see if i can find the detail, it was a while ago now but cool as I remember. I may even write an Article!
Would you like to reply?
Login or Register to post your comment.