I couldn't find this page in my MSI help! I've downloaded the current
version ( Dec 99 ), perhaps you have a newer one.
"Robert M. Dickau"
installshield.com> schrieb im Newsbeitrag news:firstname.lastname@example.org...
> The MSI help page "How do I install a package with elevated privileges as
> non-admin?" has details.
It's in the July 2000 MSDN Library.
"Johannes John" <email@example.com> wrote in message
> Hallo Robert,
> I couldn't find this page in my MSI help! I've downloaded the current
> version ( Dec 99 ), perhaps you have a newer one.
> "Robert M. Dickau"
> installshield.com> schrieb im Newsbeitrag news:firstname.lastname@example.org...
> > The MSI help page "How do I install a package with elevated privileges
> > non-admin?" has details.
I am not quite clear on one issue involving installing with elevated privileges. The Windows Installer SDK states the following:
"To always install a package with elevated (system) privileges, set the AlwaysInstallElevated value to "1" under both of the following registry keys.
Is this something that I set as part of the install package or does an administrator have to set these on each machine before the install begins? If set for elevated privileges, does the user then keep this privilege until changed by an administrator or does it only apply for that install?
This is a pure Windows 2000 environment, but not running Active Directory.
We had those keys included in the standard disk image we use for new systems but you can have it done by a setup that is run by an admin or run via Active Directory (we also keep it there for case swhan a system is built from scratch and not using an image). The keys remain until an admin changes them.
Bear in mind that will allow MSI setups (we only use standard setups but it applies to basic as far as I know) to run despite users having no admin privileges.
We had to tighten the Group Policies for some users -- you know those who like to install stuff such as cute screen savers of unknown origin -- so they are not able to install from a removable drive but that can be done only by using Active Directory as far as I know.
From the work that I have done with elevated privileges, if the install is initially installed by an administrator, then whenever that install is launched again, it will run with admin privileges regardless of who the user is. (that is as long as the install was run in per-machine mode) I also found that the registry setting AlwaysInstallElevated is not required to be set.