All Users Shortcut

[RM]

Hi,

I'm still kind of new to this software, but I anyway feel like blushing when asking such a dumb question:

I'm capturing with PackageAware a setup of Nvu 1.0: this program places a shortcut in the directory "All users". So far, so good. Then, I build my setup into an MSI file (leaving alone the default $Variables$) and I set a shortcut (in the visual tab mode) linking my NVU.exe and placing it in $STARTMENUALL$\\ProgramsWhat happens after I deploy that MSI is: In the "all user\\start menu\\Program" directory there is just an empty directory (nvu witch I set in "project properties": shortcut folder) and no shortcut file. In the admin user folder, witch is the user i used to install manually the msi, (say admin\\startmenu\\prog), the shortcut file is present (in the right "nvu" folder).

So, the question is: what do I have to do to place a shortcut in "All user" just as it is in the "original" installation ? Right now it looks like that shortcut is placed in a signle user folder despite I use a $*ALL$ variable, witch is supposed to handle all users :s

Thanks for your patience.

[MichaelNesmith]

You shouldn't do it this way.

You should always let the end-user decide if (s)he wants to create shortcuts for only him/herself, or for everybody. This is part of the Windows Installer standards and requirements. The link location in the Create Shortcut command should always be $SHORTCUTFOLDER$.

However, you can violate these standards, should you want to. In that case, set the link location field of the Create Shortcut command to $SHORTCUTFILESALL$\\$STARTMENU$.

[RM]

Hi,

I tried with $SHORTCUTFILESALL$\\$STARTMENUALL$: now the installer doesn't do anything anymore: nothing installed in prog files\\nvu, no shortcut, nothing, just as if the .msi was never launched.

Same trying with $SHORTCUTFILESALL$\\$STARTMENUME$.

As a desperate move, I tried with $SHORTCUTFILESALL$\\$STARTMENU$: this time the installer works, but it's the same result as the initial problem: in "all users\\startmenu\\programs", the folders exists but is not filled with the shortcut.... And in the local user\\startmenu\\programs, everything is fine.

It looks like I can try anything, InstallAware just doesn't want to set shortcauts in "all users". Might this be an InstallAware "feature" to prevent users from doing non-MSI-standard stuff just like i'm trying to ?

The thing is: it has to be a silent install, so I can't ask the user anything. Besides everyone on the machine has to get a shortcut.... That's why I intented to create a all users shortcut no matter what.

[MichaelNesmith]

Nothing is hard-coded in InstallAware, so you will be able to do what you want. However, I cannot tell how you may have edited/changed your MSIcode script from here, so you will have to take a look at it. Type ALT+C in the IDE and step through your setup code, line by line, in the IDE. That will show you what's going wrong.

[RM]

Well...is the "get for all users if applicable" option from the "get folder location" command applicable for Win XP ? .....that may be the problem.....

The variable are all as I expect except maybe that one...But what's strange is that it appears this variable is ok because it create a folder at the rigth place, when i use this variable.....BUT it can't create a shortcut at the place I reference with that variable......

[RM]

I did some test and created lot of shortcuts following multiple cases:

There are 2 possibilities: 1 InstallAware forbid to create shortcuts in "all users" (possibilitie to exclue due to Micheal's previous post)

2. (I don't see any other solutions): the "get for all users (if applicable)" option is not working.... Win XP is NT based right ? so it should normally be applicable.....

Do you see any other reasons this options is not applicable / Is there any other hack I can use to dynamically point to the "all users" folder ? (As the $SHORTCUTFILESALL$ is supposed to be empty when the "get for all users (if applicable)" option is not applicable).

Thanks.

[MichaelNesmith]

I'm still thinking something is wrong with your script.

If you just create a new default project, and then install it for all users (just click next in the wizard dialogs), you will have a shortcut created in the All Users section of the Start Menu. And yes, also on Windows XP!

Try that out!

[RM]

"If you just create a new default project, and then install it for all users"

Hmm I'm not sure on how to install it for all users......by just setting the ALLUSERS variable to TRUE ? I guess i'm missing something there.

Now to give you some more details about the problem: I tried it on other machines, installed by other peoples, XP and 2000, still the same result.

What is really strange is that the "local user\\startmenu\\mysoft is created successfully with a shortcut, but at the same time, there is a creation of a folder "all user\\startmenu\\mysoft" without a shortcut (why are there 2 folders created ? I only set 1 shortcut, which was not part of the capture), and when I uninstall the program via the ARP, both folders are successfully deleted...

[MichaelNesmith]

Just run the default project and hit Next on every dialog.

[RM]

Hi,

I tried it:
I created a new defaut projet, and built it as a single .exe, then I executed it in my VMWare and clicked "next button". It's working perfectly: the shortcut is created in "all users".

And then, I tried another thing: I converted that .exe into an MSI using the group policy wizard (I didn't modify the project at all) with /s param (as I always do). I installed the MSI on my VM and the problem reappears: no shortcut in "all users".

What should I do to have to same result as the .exe with the MSI ?

Thanks.

[RM]

Hmm well Ok, I've found the problem: As long as you don't deploy the MSI via Active Directory or something similiar, it doesn't work. I tried deploying it via an Active Directory-like software and it working ok: the shortcut is in the all "users" folder. Earlier, I was deploying it manually to see if everything looked Ok.

I still have a lot to learn about group policies....Why does it work via active directory and not via manual install ?

Thanks for the big help, I would still be searching blindly without it.

[MichaelNesmith]

Ah, if you were testing with Group Policy MSIs, the golden rule is that they are intended for Group Policy deployment only.

Why? Because the Active Directory Group Policy Object Editor makes it mandatory to specify certain options at deployment time - such as the mode of installation (All users/Just me), whether setup will be installed immediately or be offered to the end-user as an optional install, and so on.

Therefore, you should not use Group Policy MSIs outside of a real Group Policy Deployment situation.

By the way, using the Group Policy Wizard is similar to running an MSI file with the "/a" administrative installation option - both prepare an MSI for group policy deployment.