Software Deployment

Keeping it simple, why not create a .LNK and copy it to the required Start Menu folder?

Thanks VbScab, I have created a new folder structure within the Application Data Folder ( ALLUSERSPROFILE)> START MENU> CORPORATE PROGRAMS and add the shortcut to it. This way if the user decide to change the shortcut path I will remove and add new shortcut within it.

Thank you, is always good to know that someone will help.

Hey

What about a shortcut to a network UNC path that is not accessible to a normal/ restricted user. i.e. I have an EXE on location \\setup.exe">\\<server_name>\<server_folder>\setup.exe and I want to create the same in AdminStudio. When I create a .lnk file it says the network location is not accessible as I am in normal user. Assume, this network location is available to the guy who is installing the application; but is there anyway by which I can package the application for this restricted network location. I tried the following methods:

1. Used another Shortcut, changed the extension to .TXT and edit it in notepad. I tried changing the values inside the TXT file, but on saving it gives the same old error of Network Not Accessible to the user. I know thats a stupid thing to happen, but I had no clue about it.

2. I tried downloading a few applications to create shortct but they were of no use.

3. I use Installshield, I created a Component and placed a dummy EXE inside. I created a shortcut to this dummy EXE. Thereby, editing the shortcut and marking the network location's PROPERTY. i.e. PROPRTY [location]=\\setup.exe">\\<server_name>\<server_folder>\setup.exe But, to my horror the same error appeared during installation of the MSI.

Could anyone tell me how this shortcut thingy works.

Thanks for patience in reading all this ;)


/ SATNIX

You need to follow the same principal that vscab mentioned before. Create a shortcut to the setup.exe on your machine and add this into your package 'as a file'. You can either add this directly into the start menu or place it elsewhere and create a shortcut in your package to point to the .lnk file.

What we usually do is to create a "file-launch-checker" to verify that the EXE-file is accessable from the network share and then launch the EXE-file, usually done by a vbscript that is is luanched as the shortcut.

Michaelnowell,

I tried doing that in the first place but I dont have direct access to the network EXE. If at all I dont have access then how can I create its shortcut. I just know that the EXE is present at the particular location.

AngelD,

It think "File launch checker" will only verify that the EXE is present and accessible. In my scenario, I know its present but I dont have access to the EXE.

Now, could anyone guide me how to proceed on that :(

Thanks for your replies

Satnix,

Step 1
Set up a property WkDir in the property table and set it to the directory of the EXE you want in your shortcut, \\XYZ\shared\application\

Step 2
In the shortcut table in the WkDir column for your shortcut enter WkDir (no square brackets no quotes).

Step 3
Create another property, EXEPath, with the full path of your network EXE, \\XYZ\shared\application\test.exe.

Step 4
In the Shortcut table in the same row you just entered the WkDir in, enter the [EXEPath] with the square brackets in the Target column.

Sorry but do you want to launch an exe (application) located on network share or run a setup from the network?

captain_planet

Thanks, captain_planet, i know this thred is now like 18 moths old, but... i've been stuck with this stupid Shortcut 'Start in' and warm google sent me to this thred...

i know its abit odd, but AppDeploy is posably the seond best website after google.