util:PermissionsEx uses its own custom table and its own set of custom actions. It was written to overcome some weaknesses in the LockPermissions table implementation in WI, but it also predates the SDL used in the LockPermissionsEx table. It does not make any use of either of those tables. It does, however, work on 2000/XP machines with WI 2.0.
It does have some weaknesses of its own, including the fact that you can't use it to turn off permissions nor to add deny permissions. I'm sure there are other implementations that may be more capable, or you may be able to get someone to code you one (possibly including me), or you can look at the current source code and either offer changes or a newer CA that better meets your needs. If a CA/Extension is to ship in WiX (assuming you contribute it back), it must work on all currently supported platforms that relate to the extension's technology (so, for directory permissions, that would be all Windows Platforms currently supported, which would mean for the next five years XP SP3/Server 2003 SP2, which by implication means WI 3.1). -----Original Message----- From: Elfe Xu [mailto:elf...@microsoft.com] Sent: Friday, July 02, 2010 6:56 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Unable to add permission for virtual account Thanks Blair! Yes, the util:PermissionEx works fine. And to my surprise, it works on my Vista machine with WI4.0 as well. (I've changed the account to "NT Authority\LocalService" for ServiceInstall, but the folder PermissionEx still use "NT Service\AtlGateway") I thought it might fail because http://msdn.microsoft.com/library/aa369774.aspx from here I see Windows Installer versions earlier than Windows Installer 5.0 ignore the MsiLockPermissionsEx Table. Windows Installer 5.0 can install an package that contains the LockPermissions Table. I guess the util:PermissionEx will put the permissions to MsiLockPermissionsEx table if it is WI5.0, but still put them to LockPermissions table if is earlier than WI5.0? Another question about permission: Seems the installer added more permissions than I required. In my code, I only add permissions for <util:PermissionEx GenericAll="yes" User="Administrator" /> <util:PermissionEx GenericAll="yes" User="CREATOR OWNER" /> <util:PermissionEx CreateChild="yes" User="Authenticated Users" /> <util:PermissionEx GenericAll="yes" User="NT Service\AtlGateway" /> But the result is: it also adds some special permissions for TrustInstaller, SYSTEM, Administrators and Users. These permissions are inhereted from c:\Program Files. If I use Permission, not the util:PermissionEx, these extra permissions won't be added. Is this the by design behavior of PermissionEx. What should I do to avoid this? Thanks, -Elfe -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unable-to-add- permission-for-virtual-account-tp5247894p5249951.html Sent from the wix-users mailing list archive at Nabble.com. ---------------------------------------------------------------------------- -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
