Hi,
when you run O&O Defrag setup in unattended mode with my command-line statement above, and you tell the msi not to create a desktopshortcut (DESKTOPSHORTCUT=0), this does not work. Desktopshortcut is always created.
Who can help?

Commandline:
"O&O Defrag Professional Edition.msi" LICCODE="xxxx-xxxx-xxxx-xxxx" LICUSER="MY-USER" LICCOMPANY="MY-COMPANY" DESKTOPSHORTCUT=0 SCREENSAVER=1 SHELLEXTENSION=1 SETDEFDEFRAG=1 REBOOT=REALLYSUPPRESS ALLUSERS=2 /passive

Manfred
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
While unchecking the "Create shortcut on desktop" checkbox the DESKTOPSHORTCUT property is removed.
[1952] MSI (c) (A0:70) [21:38:15:500]: PROPERTY CHANGE: Deleting DESKTOPSHORTCUT property. Its current value is '1'.

The component holding the shortcut has a condition of "DESKTOPSHORTCUT" so if you specify 0 as the value the condition will still resolve to true.

Shortcut table
Shortcut Directory_ Name Component_ Target Arguments Description Hotkey Icon_ IconIndex ShowCmd WkDir
oodcnt_ds.53480420_ED54_41F1_B802_5A3B83DAF067 DesktopFolder O&ODEF~1|O&O Defrag CmpContainerDesktopShortcut.53480420_ED54_41F1_B802_5A3B83DAF067 [INSTALLDIR.53480420_ED54_41F1_B802_5A3B83DAF067]oodcnt.exe Launches O&O Defrag oodcnt_ds.53480420_ED54_41F1_B802_5A3B83DAF067.exe 0 1

Component table
Component ComponentId Directory_ Attributes Condition KeyPath
CmpContainerDesktopShortcut.53480420_ED54_41F1_B802_5A3B83DAF067 {53480425-CA19-476C-822F-8DA0CD87DA80} INSTALLDIR.53480420_ED54_41F1_B802_5A3B83DAF067 4 DESKTOPSHORTCUT Registry5.53480420_ED54_41F1_B802_5A3B83DAF067

Either use a transform and remove the DESKTOPSHORTCUT property or specify DESKTOPSHORTCUT="" on the command line.
Answered 05/21/2008 by: AngelD
Red Belt

Please log in to comment
0
Hi AngelD,

great job!
Thank you for your explanations,but how did you find this?

Manfred
Answered 05/22/2008 by: msenn
Orange Belt

Please log in to comment
0
Manfred, please don't forget to edit your 'Package KB' entry to reflect this new information.
Answered 05/22/2008 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: msenn
Thank you for your explanations,but how did you find this?

I used DebugView to find out what happend behind the scene while un-checking the option.

Ian,

I've already added this thread to the KB in the "Discussion Threads" section for the application.
Answered 05/22/2008 by: AngelD
Red Belt

Please log in to comment
0
ORIGINAL: AngelD
I've already added this thread to the KB in the "Discussion Threads" section for the application.
Indeed you have but the article hasn't been updated with this latest detail.
Answered 05/22/2008 by: VBScab
Red Belt

Please log in to comment
0
The information is now pending and waiting for Bob to approve.

Thanks Ian for pointing it out.
Answered 05/22/2008 by: AngelD
Red Belt

Please log in to comment
0
ORIGINAL: AngelD
I used DebugView to find out what happend behind the scene while un-checking the option.
Is it DebugView for Windows v4.74 from Microsoft/Sysinternals?
Answered 05/23/2008 by: msenn
Orange Belt

Please log in to comment
0
Yes.

Have a look at my "Monitor MSI installation actions in real time" comment at http://juice.altiris.com/article/1358/troubleshooting-wise-packages-with-windows-installer-log-files
Answered 05/24/2008 by: AngelD
Red Belt

Please log in to comment
0
Thanks AngelD, this is very helpfull to me![:)]
Answered 05/24/2008 by: msenn
Orange Belt

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