There are other triggers in the MSI  that can cause install on demand from the 
MSI, advertised COM being one, and I think file extensions do it too,  but I 
don't know if that's an option for this particular issue.

Of course Active Setup can do it, yes, maybe that's a solution, getting Windows 
to run a command line often is ;)

Phil

From: Christopher Painter [mailto:chr...@iswix.com]
Sent: Friday, January 13, 2012 12:40 PM
To: Wilson, Phil; General discussion for Windows Installer XML toolset.; Dan 
Gough
Subject: RE: [WiX-users] Adding Internet Explorer Context Menu item for all 
users in a per machine install

Actually I just realized I've been saying it all.  I've been implying that the 
repair approach and the active setup approach are mutually exclusive.  In fact 
the active setup is just a way to trigger the repair through a command line 
when an advertised shortcut is unavailable.

I'm sorry if I was unclear or if I was clear and now I'm just confusing myself. 
:-)

________________________________
From: "Christopher Painter" <chr...@iswix.com>
Sent: Friday, January 13, 2012 2:33 PM
To: "Wilson, Phil" <phil.wil...@invensys.com>, "General discussion for Windows 
Installer XML toolset." <wix-users@lists.sourceforge.net>, "Dan Gough" 
<goug...@gmail.com>
Subject: RE: [WiX-users] Adding Internet Explorer Context Menu item for all 
users in a per machine install

l've used the Active Setup technique and replication occurred right away when 
the user logged on.

Make sure you are using a clean machine such as a snapshotted VM to ensure a 
good testing environment.  It could be that replication already occurred and 
isn't occuring again because the Version value isn't changing/increasing.

________________________________
From: "Wilson, Phil" <phil.wil...@invensys.com>
Sent: Friday, January 13, 2012 2:30 PM
To: "General discussion for Windows Installer XML toolset." 
<wix-users@lists.sourceforge.net>, "chr...@iswix.com" <chr...@iswix.com>, "Dan 
Gough" <goug...@gmail.com>
Subject: RE: [WiX-users] Adding Internet Explorer Context Menu item for all 
users in a per machine install

Log in won't cause replication of the keys. An earlier post mentioned that you 
need an advertised shortcut.

Phil W

-----Original Message-----
From: McCain, Jon [mailto:jon.mcc...@inin.com]
Sent: Friday, January 13, 2012 8:06 AM
To: chr...@iswix.com; General discussion for Windows Installer XML toolset.; 
Dan Gough
Cc: McCain, Jon
Subject: Re: [WiX-users] Adding Internet Explorer Context Menu item for all 
users in a per machine install

I have tried using the Active Setup keys but when the other user logs in the 
replication isn't occurring nor is the repair type install.

Here is what my setup looks like:

<!--Installed at HKLM so that Active Setup keys can be imployed-->
<RegistryValue Id="ctd_classinfo_185" Action="write" Type="string" Root="HKLM" 
Key="Software\Microsoft\Internet Explorer\MenuExt\Report Click-To-Dial Problem" 
Value="[#ctxmenu.htm]"/>
<RegistryValue Id="ctd_classinfo_186" Action="write" Type="string" Root="HKLM" 
Key="Software\Microsoft\Internet Explorer\MenuExt\Report Click-To-Dial 
Problem\Contexts" Value="1"/>
<RegistryValue Id="ctd_activesetup_regfix_1" Action="write" Type="string" 
Root="HKLM" Key="Software\Microsoft\Active Setup\Installed 
Components\[ProductCode]" Value="[ProductName]" />
<RegistryValue Id="ctd_activesetup_regfix_2" Action="write" Type="string" 
Root="HKLM" Key="Software\Microsoft\Active Setup\Installed 
Components\[ProductCode]\StubPath" Value="msiexec /fou [ProductCode] /qb"/>
<RegistryValue Id="ctd_activesetup_regfix_3" Action="write" Type="string" 
Root="HKLM" Key="Software\Microsoft\Active Setup\Installed 
Components\[ProductCode]\Version" Value="1,0,0"/>


HKCU items are in separate components so that they can have the KeyPath 
attribute set.

<!--Must be installed in HKCU for installing user to immediately use. All other 
users will have the plugin silently repaired using Active Setup-->
<Component Id="ctd_ieplugin_hkcu_menuext" 
Guid="DB65E89E-C207-43BC-B4E9-E75D20A870AF" SharedDllRefCount="yes">
<RegistryValue Id="ctd_classinfo_183" Action="write" Type="string" Root="HKCU" 
KeyPath="yes" Key="Software\Microsoft\Internet Explorer\MenuExt\Report 
Click-To-Dial Problem" Value="[#ctxmenu.htm]"/>
<!--These two entries keep the install from re-running or repairing itself when 
the installing user logs back in.-->
<RegistryValue Id="ctd_activesetup_HKCU_COPY_1" Action="write" Type="string" 
Root="HKCU" Key="Software\Microsoft\Active Setup\Installed 
Components\[ProductCode]" Value="[ProductName]" />
<RegistryValue Id="ctd_activesetup_HKCU_COPY_2" Action="write" Type="string" 
Root="HKCU" Key="Software\Microsoft\Active Setup\Installed 
Components\[ProductCode]\Version" Value="1,0,0"/>
</Component>
<Component Id="ctd_ieplugin_hkcu_menuext_context" 
Guid="327241A1-ECFF-454D-A8EC-34E0BF616904" SharedDllRefCount="yes">
<RegistryValue Id="ctd_classinfo_184" Action="write" Type="string" Root="HKCU" 
KeyPath="yes" Key="Software\Microsoft\Internet Explorer\MenuExt\Report 
Click-To-Dial Problem\Contexts" Value="1"/>
</Component>

The OS I am running this on is Windows 7 64 Bit. The installing user is also in 
the local admin group but the others users are not.

Jon

-----Original Message-----
From: Christopher Painter [mailto:chr...@iswix.com]
Sent: Thursday, January 12, 2012 7:12 PM
To: Dan Gough; General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Adding Internet Explorer Context Menu item for all 
users in a per machine install

Then there's the case of Office AddIns that allowed either HKCU or HKLM in 
2003, took away in 2007 ( and put it back with a hotfix and enabling registry 
value ) and really put it back in 2010 leaving one hell of a mess for us 
installer guys to deal with.


So, yes, YMMV... in the event it really needs to be HKCU like the poster 
asserted then my response below will help.

----------------------------------------

From: "Dan Gough" <goug...@gmail.com>

Sent: Thursday, January 12, 2012 5:21 PM

To: chr...@iswix.com, "General discussion for Windows Installer XML toolset." 
<wix-users@lists.sourceforge.net>

Subject: Re: [WiX-users] Adding Internet Explorer Context Menu item for all 
users in a per machine install


Or try applying the key to HKLM rather than HKCU in the first place. Many
Windows settings can apply to either key to give you the flexibility of
having each setting system-wide or per-user.

On Thu, Jan 12, 2012 at 9:34 PM, Christopher Painter <chr...@iswix.com>
wrote:

The Registry element has a Root attribute that you can set to HKCU. If

your program has an advertised shortcut you can use this to trigger

resilency to complete the installation for each user who uses your app.

It's an ugly story though like the old Office install that popped up every

time you went to a new conference room and logged in.


http://wix.sourceforge.net/manual-wix3/wix_xsd_registry.htm


Here's an alternative approach that avoids all that:


http://blogs.flexerasoftware.com/installtalk/2011/11/using-active-setup-to-r


epair-user-settings.html


----------------------------------------


From: "McCain, Jon" <jon.mcc...@inin.com>


Sent: Thursday, January 12, 2012 3:28 PM


To: "General discussion for Windows Installer XML toolset.

(wix-users@lists.sourceforge.net)" <wix-users@lists.sourceforge.net>


Subject: [WiX-users] Adding Internet Explorer Context Menu item for all

users in a per machine install


I have been working on a new install where a context menu is added to the

Right-Click Menu within Internet Explorer.


Everything I have read regarding this requires the key be added to

HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer. This does work but

the issue I have is that our installs are run as per-machine installs and

this causes other users that login to not have this menu.


Links to MSDN articles explaining context menu additions for Internet

Explorer: http://msdn.microsoft.com/en-us/library/aa753589%28VS.85%29.aspx


The wxs code is quite simple for this addition:


<RegistryValue Id="ctd_classinfo_183" Action="write" Type="string"

Root="HKCU" Key="Software\Microsoft\Internet Explorer\MenuExt\keyName"

Value="[#FileID]"/>


<RegistryValue Id="ctd_classinfo_184" Action="write" Type="string"

Root="HKCU" Key="Software\Microsoft\Internet Explorer\MenuExt\ keyName

\Contexts" Value="1"/>


Has anyone run into this or another issue where a per-machine install is

performed but features or other items need to exist for all users in the

above fashion?


Thanks,


Jon


----------------------------------------------------------------------------


--


RSA(R) Conference 2012


Mar 27 - Feb 2


Save $400 by Jan. 27


Register now!


http://p.sf.net/sfu/rsa-sfdev2dev2


_______________________________________________


WiX-users mailing list


WiX-users@lists.sourceforge.net


https://lists.sourceforge.net/lists/listinfo/wix-users


----------------------------------------------------------------------------
--

RSA(R) Conference 2012

Mar 27 - Feb 2

Save $400 by Jan. 27

Register now!

http://p.sf.net/sfu/rsa-sfdev2dev2

_______________________________________________

WiX-users mailing list

WiX-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 
7AW (Registered number 166023). For a list of European legal entities within 
the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx.

You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail 
recept...@invensys.com. This e-mail and any attachments thereto may be subject 
to the terms of any agreements between Invensys (and/or its subsidiaries and 
affiliates) and the recipient (and/or its subsidiaries and affiliates).





*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 
7AW (Registered number 166023). For a list of European legal entities within 
the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx.

You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail 
recept...@invensys.com. This e-mail and any attachments thereto may be subject 
to the terms of any agreements between Invensys (and/or its subsidiaries and 
affiliates) and the recipient (and/or its subsidiaries and affiliates).

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to