PDA

View Full Version : Elevated Privileges



NewsArchive
11-04-1999, 01:00 AM
This is absolutely correct.

--
David Thornley
Lead Developer Support Engineer
InstallShield Software Corporation
http://www.installshield.com



Luciana Soligo wrote in message <38218126.30DD0300@cost.se>...
>As far as I understand, to run an installation with elevated privileges,
>
>the administrator should define/ allow users and applications to do so.
>Then there 's nothing I can do from the installation point of view to
>run with these
>privileges.
>I mean, if the machine wasn't set for that, I'll be running as the
>normal user.
>
>Is my statement correct??
>
>
>Luciana Soligo
>Entegrity Solutions
>
>

NewsArchive
01-12-2000, 01:00 AM
When you stated that Windows 2000 has an option to run setup as the admin,
are you refering to Windows Installer? I was not aware of this feature if
not. How does it work? Is there an option to enable this feature?

"Stefan Krueger" <@> wrote in message
news:387b62d3.0@news.installshield.com...
> Not with IS6 as far as I know. (you may be able to write code that logs
off
> the current user and automatically logs on as Administrator to run setup
in
> Admin mode, but that would be tedious)
> Windows 2000 will automatically give you the option to run setup as
> Administrator (without having to log off the current user). That's a new
> feature of Win2k that doesn't exist on NT4.
>
> --
> Stefan Krueger
> Independent Setup Consultant
>
> // InstallSite - Resources for Setup Developers
> // http://www.installsite.org
>
> My reply-to address is invalid to avoid spam.
> Paid support and consulting services are available:
> Write to info@installsite.org for details (auto-responder).
>
>
> ugfu.tmlra.sika_2 <tmlra.sika_2@bluewin.ch> schrieb in im Newsbeitrag:
> 387B348E.80A6625D@bluewin.ch...
> > Is it possible to launch an installation with elevated privileges
> > (Administrator rights) without InstallShield for Windows Installer ?
> >
>
>

NewsArchive
01-12-2000, 01:00 AM
I tried this myself. If the user running the install program is not an
administrator equivalent, the OS pops up a dialog asking how to run the
install. I am not sure how the OS knows it is an install program. My guess
is it looks for a *setup* or *install* file name. The dialog allows the user
to enter the username and password to use for running the install program,
or run it as the currently logged in user.

Does anyone know which HKEY_CURRENT_USER is being used during the install if
the user supplies an admin user and password? Will it be the current
non-admin user, or the administrator equivalent user?

NewsArchive
01-12-2000, 01:00 AM
> is it looks for a *setup* or *install* file name. The dialog allows the
user

That's correct.

> Does anyone know which HKEY_CURRENT_USER is being used during the install
if
> the user supplies an admin user and password? Will it be the current
> non-admin user, or the administrator equivalent user?

Not sure, but I assume Administrator.

--
Stefan Krueger
Independent Setup Consultant

// InstallSite - Resources for Setup Developers
// http://www.installsite.org

My reply-to address is invalid to avoid spam.
Paid support and consulting services are available:
Write to info@installsite.org for details (auto-responder).

NewsArchive
07-19-2000, 12:00 AM
The MSI help page "How do I install a package with elevated privileges as a
non-admin?" has details.

NewsArchive
07-21-2000, 12:00 AM
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.

Johannes


"Robert M. Dickau"
<i_wish_i_had_time_to_answer_individual_questions_through_email_but_i_don't@
installshield.com> schrieb im Newsbeitrag news:3976275b.0@208.30.171.38...
> The MSI help page "How do I install a package with elevated privileges as
a
> non-admin?" has details.
>
>

NewsArchive
07-30-2000, 12:00 AM
Hi, Johannes,

It's in the July 2000 MSDN Library.

--- Robert

"Johannes John" <jn@rib.de> wrote in message
news:39780866.0@208.30.171.38...
> 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.
>
> Johannes
>
>
> "Robert M. Dickau"
>
<i_wish_i_had_time_to_answer_individual_questions_through_email_but_i_don't@
> installshield.com> schrieb im Newsbeitrag news:3976275b.0@208.30.171.38...
> > The MSI help page "How do I install a package with elevated privileges
as
> a
> > non-admin?" has details.

Eric Hudson
02-19-2002, 11:24 AM
Hi,

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.

HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer"

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.

Thanks.

Eric

LewisQ
02-19-2002, 12:14 PM
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.

huntant
02-19-2002, 03:44 PM
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.



Anthony