Microsoft cannot guarantee that problems resulting from the incorrect use of the MSI file editor can be solved.I've read alot of older posts so far and they either assume I know VB faily well (which I don't) or they did not solve my problem.
Last but not the least, editing an MSI file can cause serious problems that may leave your system in an unstable state. You can download the latest Orca from the latest Windows SDK at Just for your reference, the version of the Orca which I am using is. Remember, the UAC is start from Windows Vista /2008 there no UAC option exists in the old version orca editor. msi file by Orca, click View->Summary Information…, and check the “UAC Compliant”. In Order to remove UAC requirement, you can open a. The Orca database editor is a table-editing tool available in the Windows Installer SDK and it can be used to edit your.
There is one other thought, if you can be sure the application never accesses protected locations, then you can rewrite the entire msi file yourself so that it never installs anything into protected locations, that would work under a limited user account.ĭue to limitations in the existing Windows Installer tools, you may need to edit the Windows Installer package (.msi) files directly. This is the best solution that you have available right now. This would actually prompt you for elevation even in limited user accounts but it would require you to provide the administrator account credentials too.
I'll bring it up again, but you rejected my earlier solution of creating a third executable which takes the msi file as a parameter and running it through shell execute using the runas verb. I know most of us want to find an easy way for anything, but there are some things which shouldn't be easy. Yes it can be annoying, but security isn't there to not be annoying or help out developers, it is there to protect users and and make administrators lives easier. In the admin roles which I have worked in, if anything needed to be installed then it would alwas be installed through the admin account after getting permission to install it. The point of limited user accounts is to stop them from doing things which they are not supposed to do, and modifying the global system state is one of them.
0 kommentar(er)
