Wilson, Phil wrote:
That's the whole point
really. The general issue is that many custom actions are arguably
incorrect because to access secure parts of the system they run with
the installing user's privilege, who was therefore required to be
privileged. The "right" thing is to run deferred with noimpersonation,
requiring them in the scripted part of the execute sequence. To get
them running with privilege in the UI sequence I believe the
recommended solution is to launch the MSI with a manifested exe that
will demand privilege with a UAC dialog so the MSI is launched with
privilege.
Correct. The UI sequence doesn't support elevation directly because you
(generally) don't need elevated privs before you get into modifying the
system.
--
sig://boB
http://bobs.org
|
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
