Our installer uses RegLoadKey/RegUnloadKey in a CustomAction to perform
multi-user installation (i.e. write to mutliple user's HKCU trees), and,
more importantly, multi-user uninstallation. Installation can effectively be
delayed to first run, but uninstallation needs to happen immediately for all
users. This paradigm works fine on all OS'es before Vista.
In Vista, the least-privilege obsession has unnecessarily crippled the
Windows Installer engine by removing these privileges. My primary question
is this: Has anyone figured out how to get SeBackupName/SeRestoreName
privileges in an MSI CustomAction on Vista?
See discussion...
http://www.macrovision.com/company/news/newsletter/tips/is_vista.shtml
http://blog.deploymentengineering.com/2006/10/vista-deferred-ca-consideration.html
http://blogs.msdn.com/vistacompatteam/archive/2006/10/19/impact-of-least-privilege-in-system-services.aspx
Does anyone else have concerns about continuing to develop on a platform
that can change so dramatically, effectively pulling the rug out from under
our feet? When we made the decision to use WiX/MSI it was with the intent of
being more sysadmin-friendly and leveraging some of what Windows
Installer/MSI can already do for us. Now I wonder if we should move to an
internally cooked-up system for install/uninstall, if the Windows Installer
won't be able to do "real-world" multi-user installs/uninstalls.
Please send suggestions!
Thanks,
-Brian Patton
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
