1. The NoImpersonate bit only affects deferred custom actions. This
implies you're launching applications from a deferred CA. Immediate CAs
typically after InstallFinalize are best suited for this (like displaying a web
page or something).
2. Signing is really only necessary for the MSI, and that provides the
publisher in the dialog. You can't get rid of the dialog, though, for an MSI
install. You can only prevent this from popping up for patches if you follow
instructions in http://msdn2.microsoft.com/en-us/library/aa372388.aspx.
3. Public properties passed from client (how you invoke your installation
transaction) to the server must be listed in the SecureCustomProperties
property or they will be ignored. See
http://msdn2.microsoft.com/en-us/library/aa371571.aspx for more information.
Heath Stewart
Technical Lead
Deployment Technology Group, Microsoft
http://blogs.msdn.com/heaths
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hao Liu
Sent: Thursday, July 19, 2007 3:54 PM
To: wix-users@lists.sourceforge.net; [EMAIL PROTECTED]
Subject: [WiX-devs] Problems about running a msi against Vista
I run a msi by using msiexec 4.0 on Vista with UAC ON. And the msi have two
custom actions (a setup dll and a remover dll). Even if my account is
Administrator, it failed to install on Vista though it worked on XP. After I
set the two CA with Impersonate="no" as Bob Arnson suggested, they get
elevated, and installation and uninstalling went through well. However, there
are the following issues:
1. When I spawn another process after installation in my setup.dll, the
process actually run as system account context rather than current user context.
2. I signed my custom actions (a setup dll and a remove dll) and the msi as
well. But when I run the msi, I still get the UAC prompt like:
A program needs your permission to continue
Product Name
Company name
Install
Version
Is there any way to prevent the prompt opened?
3. One more issue when I uninstall. I could not pass successfully a public
parameter value pair on Vista. But it works on XP. The log is:
MSI (s) (60:84) [17:46:47:028]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (60:84) [17:46:47:028]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (60:84) [17:46:47:028]: Using cached product context: machine assigned
for product: FF01F0D58705B3A4EBBC07DB4FF537FC
MSI (s) (60:84) [17:46:47:028]: Product {5D0F10FF-5078-4A3B-BECB-70BDF45F73CF}
is admin assigned: LocalSystem owns the publish key.
MSI (s) (60:84) [17:46:47:028]: Product {5D0F10FF-5078-4A3B-BECB-70BDF45F73CF}
is managed.
MSI (s) (60:84) [17:46:47:028]: Running product
'{5D0F10FF-5078-4A3B-BECB-70BDF45F73CF}' with elevated privileges: Product is
assigned.
MSI (s) (60:84) [17:46:47:028]: Machine policy value 'EnableUserControl' is 0
MSI (s) (60:84) [17:46:47:028]: PROPERTY CHANGE: Adding RestrictedUserControl
property. Its value is '1'.
MSI (s) (60:84) [17:46:47:028]: Ignoring disallowed property REMOVEPARAMS
Thanks a lot,
Hao
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
