Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Disable advertised shortcuts?

252 views
Skip to first unread message

William Jones

unread,
Jan 19, 2007, 9:54:33 AM1/19/07
to
Is there any way to force Windows Installer to always generate regular
(non-advertised) shortcuts? I know you can set the DISABLEADVTSHORTCUTS
property on individual MSI packages, but I'm looking for something like a group
policy setting that would apply globally. I need to disable advertised
shortcuts when the MSI isn't readily available (e.g. when it's bundled inside a
setup.exe bootstrapper).

Christopher Painter

unread,
Jan 19, 2007, 2:05:36 PM1/19/07
to

The DisableMSI policy is the closest that I can think of to doing what
you want. ( Well, I suppose MsiZap if you don't want to ever uninstall
the app .. perhaps you reimage the machine instead. )

Instead, consider running the setup.exe and ripping the msi out of the
temp directory that a boostrapper typically creates. Then you can use
a tool like SMS 2003 ( SMS Advanced Client - MSI Source Agent ) to
manage associating the package on a distribution point to the source
location of the install, or write your own custom utility for doing so
( MSISourceList API's )

Phil Wilson

unread,
Jan 19, 2007, 6:12:45 PM1/19/07
to
You're assuming that shortcuts are the only thing that can automatically
trigger a repair, but they are not. They are other places where an automatic
repair can be triggered.
--
Phil Wilson
[Microsoft MVP Windows Installer]
"William Jones" <no...@none.com> wrote in message
news:6im1r294p21qabb0q...@4ax.com...

William Jones

unread,
Jan 20, 2007, 8:24:29 PM1/20/07
to
I know there are Windows Installer API's that can also trigger repairs.
However, all the applications that are giving me grief are triggering repair
only at launch, based on the advertised shortcut. If I delete the advertised
shortcut and manually create my own standard shortcut, everything works. I'd
like to eliminate this manual process.

I'm sure advertised shortcuts (and automatic repair) are valuable in many
environments, but they add no value and create trouble for me. It's
unfortunate that they can't be globally disabled.

Linda Liu [MSFT]

unread,
Jan 22, 2007, 7:11:59 AM1/22/07
to
Hi William,

Thank you for posting here.

It seems that this issue is more related to GPO, and is not a .NET
Framework Development related one. I suggest that you may post this issue
in:

microsoft.public.windows.group_policy

You may have someone who has more experience on GPO to help you.

Good luck!

Sincerely,
Linda Liu
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

Christopher Painter

unread,
Jan 22, 2007, 9:02:04 PM1/22/07
to
Maybe someone should let Linda in on the fact that GPO can't deploy
MSI's that are compressed within a bootstrapper.

Phil Wilson

unread,
Jan 23, 2007, 2:28:06 PM1/23/07
to
It's not just APIs, it's actions that the user takes. COM activation, using
file extensions other actions can cause a repair. You're fighting an
in-built design feature of Windows Installer instead of working with it and
having the MSI file available for repair somewhere. If you're seeing a
repair then either the installation is broken or users are removing/altering
files (or you are somewhere with a custom action after files are installed).

--
Phil Wilson
[Microsoft MVP Windows Installer]

"William Jones" <no...@none.com> wrote in message

news:7if5r2h87jn68rab8...@4ax.com...

0 new messages