Re: Multiple administrator

From: Karl Levinson [x y] mvp (jamescagney90210@excite.com)
Date: 11/29/02


From: "Karl Levinson [x y] mvp" <jamescagney90210@excite.com>
Date: Fri, 29 Nov 2002 09:54:06 -0500

I agree with the previous posts. Don't use a shared administrator account,
there's no accountability there. One typical method is to give each
administrator a second account [like jsmith and jsmith2] so that they log in
as a normal user [jsmith] most of the time and just use RUNAS to perform
administrator tasks using their second admininstrator-equivalent account
[e.g. jsmith2].

"Alder" <alder.must@mail.ee> wrote in message
news:as7r25$ta$1@news.eenet.ee...
> I think that there is more better to use own accounts. Because it's clear
> who can do what, and also for log detection . As it's known , that all
> administrators haven't same administrative rights, it's also possible to
> implement delegated administration.
> Also use policy to rename administrator account and use logon script to
use
> for account misuse detection.
>
>
> "Iikka Meriläinen" <Iikka.Merilainen@pato.vaala.fi> wrote in message
> news:u#eLqwxlCHA.1912@tkmsftngp04...
> > Hi!
> >
> > This is a difficult question to which no single correct answer exists.
> >
> > However, I personally use my own account which is a member of Domain
> Admins,
> > and preserve the _real_ Administrator account along with any copies of
it
> > for those situations my own profile screws up or something else strange
> > happens. This is also better when you don't want to share your admin
> > password to many people. In my organization there are about ten Domain
> > Admins members total of which only two (me and the director) know the
real
> > admin password. Thus you have a better control of who _has_
administrative
> > privileges, either via the administrator password or via their own
logins.
> >
> > If it's practical in your case, you can also use your normal accounts
> > without any administrative privileges and use the 'runas' functionality
> when
> > you need elevated privileges for some single process. I've tried it, but
> it
> > didn't work as smoothly as I expected.
> >
> > You could also have administrative privileges for your own accounts and
> then
> > use the real Administrator login as an emergency way out of problems.
For
> > example, make a nine-character password and make sure each of those
three
> > people know three different letters of the password. Then you can
> > cooperatively decide when the backup login is needed. This is for
> paranoids,
> > but many organizations have this policy.
> >
> > --
> > Best regards,
> >
> > Iikka Meriläinen
> > Vaala, Finland
> > ==================================================
> > Please reply to the newsgroup only so that others can learn from this
> issue.
> > This message is provided "as is", with absolutely no warranties.
> > ==================================================
> > "Philippe Aymer" <aymerphilippe@hotmail.com> wrote in message
> > news:47971ff0.0211281139.565d358f@posting.google.com...
> > > Hi,
> > >
> > > we are 3 server admins in a Win2000 network. What is better:
> > >
> > > - to log in as "administrator" each time we need to be admin,
> > > - to give our user account the "admin rights"
> > > - other ?
> > >
> > > Thanks!
> > >
> > > --
> > > Philippe Aymer
> >
> >
>
>



Relevant Pages

  • Re: XP Home --> Pro upgrade
    ... WinXP is designed to install and upgrade the existing operating system while simultaneously preserving your applications and data, and translating as many personalized settings as possible. ... The standard security practice is to rename the account, set a strong password on it, and use it only to create another account for regular use, reserving the Administrator account as a "back door" in case something corrupts your regular account. ... As for other accounts with administrative privileges, routinely using a computer with administrative privileges is not without some risk. ...
    (microsoft.public.windowsxp.general)
  • Re: Event 1202 Warnings after Renaming Administrator Acct on SBS2003
    ... policy to rename the account although it is not really necessary or useful. ... Did I check Group Policies for references to the Administrator ... Failed to perform redirection of folder Desktop. ...
    (microsoft.public.windows.server.general)
  • Event 1202 Warnings after Renaming Administrator Acct on SBS2003
    ... one referencing the original administrator account: ... specific policy setting that was flagged with a big, ... I used an incorrect procedure to rename the ...
    (microsoft.public.windows.server.general)
  • Re: Event 1202 Warnings after Renaming Administrator Acct on SBS2003
    ... Did you check the Group Policies for references to the Administrator ... Administrator account? ... what policy do you have? ... referencing the former administrator account. ...
    (microsoft.public.windows.server.general)
  • Event 1202 Warnings after Renaming Administrator Acct on SBS2003
    ... Did I check Group Policies for references to the Administrator account? ... enabling the Rename Administrator account policy in Group Policy. ... Failed to perform redirection of folder Desktop. ...
    (microsoft.public.windows.server.general)