OK, the package is fine except this one point.

I place a shortcut on the allusers desktop, and the *.msi doesn't put it there, only for the original user.

I've checked the exclusions list and allusers isn't one of them although default user is.

Anyone had this problem before?

Thanks
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Are you installing per-user or per-machine? Create a verbose log of the install and check the value of the ALLUSERS property.
Answered 10/13/2009 by: VBScab
Red Belt

Please log in to comment
0
Not sure. I run discover, and perform a 'before snapshot', install the app and put the shortcut on the allusers desktop. The application doesn't have the 'only for this user'/'everyone' options though.

It creates the *.msi then when I run it on a clean build, it puts the program in no problems just not the allusers shortcut.

How would I go about creating a verbose.log file?

Thanks
Answered 10/13/2009 by: cormack
Yellow Belt

Please log in to comment
0
did you set allusers=1
Answered 10/13/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
ORIGINAL: cygan

did you set allusers=1


No. I'm quite new to WinInstall - where would I set this option using discover?

Thanks
Answered 10/13/2009 by: cormack
Yellow Belt

Please log in to comment
0
open your msi with orca look in the property table

add if not there

ALLUSERS 1
Answered 10/13/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
Thanks will give that a go now.

One other thing - wininstall puts it's folders in a file before building the *.msi it appears. It does have an allusers folder, but it hasn't got subfolders of desktop or start menu. It does have one called application data

Will report back anyway, cheers for now.

EDIT: That appears to have done the trick - Thanks!!!!
Answered 10/13/2009 by: cormack
Yellow Belt

Please log in to comment
0
How would I go about creating a verbose.log file?For completeness...

You use the '/L' argument:msiexec /i <name of MSI> <other command line options> /L*V %TEMP%\whatever.log

Logs can be pretty impenetrable for newcomers but there is a free tool you can download (WiLogUtl, IIRC) which tries to perform some analysis for you.
Answered 10/13/2009 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity