Administrator and Adminisrators

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have heard that some drivers can only be installed by local adminisrator
account not an account belonging to administrators group.
Is this true?
I would like to know the difference between adminisrator and administrators
in the
case of installing something.

Thanks in advance.
 
Iwashi said:
I have heard that some drivers can only be installed by local
adminisrator account not an account belonging to administrators group.
Is this true?
Click to expand...

No, it isn't true. In Windows XP all computer administrators have equal
powers.

Malke
 
Iwashi said:
I have heard that some drivers can only be installed by local adminisrator
account not an account belonging to administrators group.
Is this true?
Click to expand...


If the developer foolishly or perversely actually hard-coded an account
name into the installation routine, yes.
I would like to know the difference between adminisrator and administrators
in the
case of installing something.
Click to expand...

There should be none, unless, as I said, some poorly trained developer
hard-coded the installation routine to a specific user account.


--

Bruce Chambers

Help us help you:



They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -Benjamin Franklin

Many people would rather die than think; in fact, most do. -Bertrand Russell
 
Malke said:
No, it isn't true. In Windows XP all computer administrators have equal
powers.

Malke
Click to expand...


In theory, you're correct. But I've found this not to always be the
case, in practice. I've encountered a very small sampling of
installation routines that had actually been written so that they would
work *only* when run from the built-in Administrator account, and then
only if the account hadn't been renamed, as is a common security practice.

I could not install these applications using a domain administrative
account, nor using the renamed built-in administrator account. I
actually had to disconnect the machine from the domain (as a security
precaution) and rename the built-in administrator account to
"Administrator" before the installation routine would work. Stupidest
thing I've ever encountered; but some developers simply have no concept
of multiple user accounts and/or proper security.

Of course, this condition is a limitation of those specific, poorly
written applications, not the operating system. When installation
routines are properly written, there is no functional difference between
the built-in Administrator account and any other accounts that are
members of the local Administrators group.


--

Bruce Chambers

Help us help you:



They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -Benjamin Franklin

Many people would rather die than think; in fact, most do. -Bertrand Russell
 
Ivo said:
I have found at least two apps which can be installed only by LOCAL
user being in Local Administrators group not by domain user being
in the same group of Local Administrators.

So question is what is the difference between these two accounts
and where it has been defined? I know that theoretically these
accounts should be equal in rights. I have studied also domain
policies but did not found a place where these differences are
defined.

And in this case the name of account is not the case, the only
difference is that one account is local user the second is domain
user.

The apps that are not working are famous Daemon tools (CD emulator)
and Alcohol 120% (also CD emulator).
Click to expand...

Your testing is incorrect or there is something else going on.
I have installed these on MANY machines as a Domain Admin account on a
system.

What that means is that my account was a domain administrator putting it in
the local administrators group of the machine.

In other words...

Start button --> RUN --> cmd --> OK

net localgroup administrators

and "Domain Admins" is listed there as a member of the local
'Administrators' group.

And I had no issue installing either of the applications you have referred
to in this posting.
 
Ivo said:
Hello!

I have found at least two apps which can be installed only by LOCAL user
being in Local Administrators group not by domain user being in the same
group of Local Administrators.

So question is what is the difference between these two accounts and where
it has been defined? I know that theoretically these accounts should be equal
in rights.
Click to expand...


The accounts are equal, both in theory, and in practice.
Unfortunately, however, not all application installation routines are
properly written.


--

Bruce Chambers

Help us help you:



They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -Benjamin Franklin

Many people would rather die than think; in fact, most do. -Bertrand Russell
 
Shenan said:
Your testing is incorrect or there is something else going on.
Click to expand...


Not necessarily.

I have installed these on MANY machines as a Domain Admin account on a
system.

What that means is that my account was a domain administrator putting it in
the local administrators group of the machine.

In other words...

Start button --> RUN --> cmd --> OK

net localgroup administrators

and "Domain Admins" is listed there as a member of the local
'Administrators' group.

And I had no issue installing either of the applications you have referred
to in this posting.
Click to expand...


In theory, you're correct. But I've found this not to always be
the case, in practice. I've encountered a very small sampling of
installation routines that had actually been written so that they would
work *only* when run from the built-in Administrator account, and then
only if the account hadn't been renamed, as is a common security practice.

I could not install these applications using a domain
administrative account, nor using the renamed built-in administrator
account. I actually had to disconnect the machine from the domain (as a
security precaution) and rename the built-in administrator account to
"Administrator" before the installation routine would work. Stupidest
thing I've ever encountered; but some developers simply have no concept
of multiple user accounts and/or proper security.

Of course, this condition is a limitation of those specific, poorly
written applications, not the operating system. When installation
routines are properly written, there is no functional difference between
the built-in Administrator account and any other accounts that are
members of the local Administrators group.



--

Bruce Chambers

Help us help you:



They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -Benjamin Franklin

Many people would rather die than think; in fact, most do. -Bertrand Russell
 
Back
Top