Re: Login as local admin

thanks kj. SP1 just installed ok. Next the transition pack.......

"kj" wrote:

The requirments for the Windows part of SP1 should be met by an account in
schema admins, enterprise admins and the other groups mentioned, but the
"built-in" Administrator is also the Exchange "Full Administrator", possible
special permissions with SQL, ISA, Sharepoint, and Group Policy (I'm not
100% positive on these).

If at all possible, use the built-in adminstrator for best results
installing SBS SP1.

--
/kj
"Andy Wolsten" <AndyWolsten@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:38407EB2-18FD-4F11-B443-D22BDF1E89DD@xxxxxxxxxxxxxxxx
thanks guys.

So if i basically ensure that my domain administrator account is a member
of
the schema admins, and enterprise admins, and login using these
credentials,
the service pack error i have been experiencing should be removed.

Appologies for the confusions between local and built in. From my
experiences IT (un)professionals are well know to use lots of terminology
interchangabley (whether right or wrong).

"kj" wrote:

The referenced article is correct. Note "built-in" and "local" are NOT
the
same. The article does not reference "local" administrator (as far as I
could search).

If you choose to use an account other than the built-in administrator
account, then it must also be a member of the additional groups specified
in
the article. Membership in Domain Admins alone is not sufficient.

There are other differences as well. I would recommend using the built-in
administrator (as does the article) account for this objective.

Hopefully, once and for all, "local" accounts are SAM based accounts on
workstations, member servers, workgroup machines, and the special account
on
domain controllers accessable only durring active directory restore mode
operations.

--
/kj
"Andy Wolsten" <AndyWolsten@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2E42EFAA-867F-4716-BEBD-9B3B0DBB198E@xxxxxxxxxxxxxxxx
Hi chaps, this is a very interesting discussion.

As i am trying to install SBS SP1, an error is displayed indicating
that
the
current user must be a member of the Schema Admins and Enterprise
Admins
groups, despite me being logged in as domain administrator account,
hence
my
concern and questions about enabling the local administrator login. The
install then fails but indicates success. Result - unable to transition
pack

http://www.smallbizserver.net/Default.aspx?tabid=266&ArticleType=ArticleView&ArticleID=68&PageID=70

This document recomends the use of the built in administrator account.
Any advice would be greatly appreciated.

"kj" wrote:

"Joe" <joe@xxxxxxxxxxxxxx> wrote in message
news:e5bvcf$715$1$8302bc10@xxxxxxxxxxxxxxxxxxx
kj wrote:
"Joe" <joe@xxxxxxxxxxxxxx> wrote in message
news:e59ol1$oa2$1$8300dec7@xxxxxxxxxxxxxxxxxxx
kj wrote:
The "local administrator" of a SBS (or other AD domain
controller)
server is *only* used durring active directory restore mode.

If you can log in normally using the domain administrator, then
describe in some detail what errors or results you are having
installing which service pack(s).

The smallbizserver SP1 install instructions emphasize the use of
the
built-in administrator account. Domain admin isn't enough for that
job.

Could you provide some reference for that statement?

The SBS Domain Administrator ("Administrator") has *complete*
permisions
to the Operating System.


The SBS SP1 installation instructions provided by Susan, Mariette et
al
on the smallbizserver website, or at least this was the case last
year
when I last did it. I don't have a copy to hand, and I don't think
it
is generally accessible now.

But I think we're at cross-purposes here. I am using the term
'domain
admin' as Microsoft does to mean accounts created after
installation,
and I do not mean the SBS built-in administrator, the one set up
during
installation. That is the one SP1 needs. So I'm told, and I didn't
really have the time to try it both ways, but a few posts like the
original one here suggest that it is true.

OK, The "Built-in" Administrator is;

1) different than the "local administrator" ( SAM based Administrator
used
ONLY (almost) for Active Directory Services Restore Mode).

2) Has capabilities above what other members of the "Domain Admins"
get
by
default. Just look at some of the other groups that the "built-in"
Administrator is a member of for a glimpse.

/kj









.

Relevant Pages

  • SP2 - Access Denied error when installing software
    ... we'll repair Windows and then install SP2. ... > Okay here's what I've found in the registry looking at the permissions in the ... So I added my account and "Users " groups. ... > By the way I did all this from safe mode under the "Administrator" account. ...
    (microsoft.public.games)
  • Re: XP Professional Adminstraor Account...?
    ... Logged onto domain from workstation as Administrator. ... users and gave the user administrative rights. ... Logged out and logged back in under the users account in which I ... Attempt to install program and the install will fail while copying ...
    (microsoft.public.windowsxp.security_admin)
  • Re: XP Professional Adminstraor Account...?
    ... Logged onto domain from workstation as Administrator. ... users and gave the user administrative rights. ... Logged out and logged back in under the users account in which I just ... Attempt to install program and the install will fail while copying ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Login as local admin
    ... So if i basically ensure that my domain administrator account is a member of ... the schema admins, and enterprise admins, and login using these credentials, ... The article does not reference "local" administrator (as far as I ... If you choose to use an account other than the built-in administrator ...
    (microsoft.public.windows.server.sbs)
  • Re: No idea what the Administrator password is and now it is askin
    ... Have a PC which had a load of virus's on it. ... If you have forgotten your password, if you have another user account ... normally hidden Administrator account. ... do for sure but the simplest solution might be to try a Repair Install ...
    (microsoft.public.windowsxp.general)