Re: adminCount schema attribute
- From: "Jorge de Almeida Pinto [MVP - DS]" <SubstituteThisWithMyFullNameSeparatedByDots@xxxxxxxxx>
- Date: Mon, 19 Nov 2007 20:20:51 +0100
way a user is protected is to add them to a protected group?So did I understand your article correctly that the
No! That is NOT correct!
The term "protection" means that the group and its members are protected from changes when delegation has been configured on some OU that contains the group and/or its members. Although this is true the members of course inherit the permissions assigned to the protected groups.
It is better NOT to use the default groups like backup operator, server operator, etc. The exception to this are the administrators and the domain admins groups.
Create your own groups and add members and assign permissions to those custom created groups
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* How to ask a question --> http://support.microsoft.com/?id=555375
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"JayDee" <dopamine@xxxxxxxx> wrote in message news:500a2d2f-9444-4171-84d1-ebe4fc295324@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Nov 18, 2:33 pm, "Jorge de Almeida Pinto [MVP - DS]"
<SubstituteThisWithMyFullNameSeparatedByD...@xxxxxxxxx> wrote:
see:http://blogs.dirteam.com/blogs/jorge/archive/2006/05/16/981.aspxhttp://blogs.dirteam.com/blogs/jorge/archive/2005/11/16/86.aspx
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)-->http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)-->http://blogs.dirteam.com/blogs/jorge/rss.aspx
--------------------------------------------------------------------------- ---------------
* How to ask a question -->http://support.microsoft.com/?id=555375
--------------------------------------------------------------------------- ---------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
--------------------------------------------------------------------------- ---------------
#################################################
#################################################
--------------------------------------------------------------------------- ---------------"JayDee" <dopam...@xxxxxxxx> wrote in message
news:ea33eb8c-31f2-486f-be2f-3d1c4e5f3389@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>I was under the impression this attribute was incremented when a user
> account had administrative privileges to keep users with loser rights
> from being able to edit those accounts. So I guess my first question
> is - is that correct?
> Here are some things I noticed:
> If adminCount is set to 1, admins with "change password" rights cannot
> change passwords on these accounts. Setting the attribute to <NOT SET>
> seems to remedy this problem.
> It seems that accounts randomly have this attribute set to "1" - even
> though they've never been an admin.
> Once I reset the attribute to <NOT SET>, I have not found a way to
> make it increment again.
> Can someone please explain this strange attribute to me? It seems to
> evade my understanding...
> Thanks!
> - JmD
Hey thanks for those links Jorge. I now understand that the adminCount
attribute isn't used by the internal AdminSDHolder process, it's just
something else that changes as a result of adding someone to a
protected group. So did I understand your article correctly that the
way a user is protected is to add them to a protected group? And the
thing that makes them unable to be edited or changed once removed is
that inheritence is turned off - and that turning it back on must be a
manual process.
But I'm pretty sure that on some occasions resetting the adminCount to
<NOT SET> has been enough to allow "lower" admins to edit the account.
Also, I noticed that when adding a user to Domain Admins, I don't
always see the adminCount attribute change... any ideas regarding
those two things?
Thanks for the info!
- JD
.
- Follow-Ups:
- Re: adminCount schema attribute
- From: JayDee
- Re: adminCount schema attribute
- References:
- adminCount schema attribute
- From: JayDee
- Re: adminCount schema attribute
- From: Jorge de Almeida Pinto [MVP - DS]
- Re: adminCount schema attribute
- From: JayDee
- adminCount schema attribute
- Prev by Date: Re: windows2000server with DNS to upgrade to windows2003 Serevr
- Next by Date: RE: Promoting a second DC
- Previous by thread: Re: adminCount schema attribute
- Next by thread: Re: adminCount schema attribute
- Index(es):
Relevant Pages
|