Re: adminDSholder being over zealous!
From: Rabbit (rabbit@the.hutch)
Date: 01/05/03
- Next message: Onrej Sevecek: "Re: closing a specific port"
- Previous message: GSTACS R2: "Assign only one IP address to a certain USER"
- In reply to: Joe Richards [MVP]: "Re: adminDSholder being over zealous!"
- Next in thread: Joe Richards [MVP]: "Re: adminDSholder being over zealous!"
- Reply: Joe Richards [MVP]: "Re: adminDSholder being over zealous!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Rabbit" <rabbit@the.hutch> Date: Sun, 5 Jan 2003 08:47:45 -0000
Thanks for that - that was my thought and I will verify it again. However,
the test accounts are new accounts with no AdminCount
set (checked with RepAdmin). They get secured by adminSDHolder (I'll spell
it right this time!) on the first run after the account is created and added
to one of the problem groups. The only group that they are a member of (or
ever have been a member of) is Domain Users.
"Joe Richards [MVP]" <humorexpress@hotmail.com> wrote in message
news:emWwYhCtCHA.1628@TK2MSFTNGP10...
> Try clearing the AdminCount property of the account in question that you
> don't want adminSDHolder overwriting.
>
> --
> Joe Richards
> www.joeware.net
> ---
>
> "Rabbit" <rabbit@the.hutch> wrote in message
> news:thBR9.1211$Gn6.18605@newsfep4-gui.server.ntli.net...
> > Have just come across a problem with the adminDSholder process which is
> > causing me some grief!
> >
> > On our production domain, if I create a new user (or copy an existing
one)
> > and add it to either the Server Operators or Print Operators builtin
> domain
> > group, the account becomes secured by adminDSholder (I have verified
this
> to
> > be case by modifying the permission set on adminDSholder and seeing it
> then
> > propogate to the test accounts), along with other higher-level admin
> > accounts.
> >
> > According to the (sparse) documentation I can find on this,
adminDSholder
> > only secures Administrators, Domain Administrators, Enterprise
> > Administrators and Schema Admins. I've tested this on a freshly-built
> test
> > domain and the securing of Server Operators and Print Operators doesn't
> > occur.
> >
> > This is a big headache for us as we run a custom process to secure
> 'medium'
> > level admin accounts with our own ACLs - this is now being overwritten
by
> > adminDSholder every hour.
> >
> > Any ideas on why this is occuring and how we can fix it...?
> >
> >
>
>
- Next message: Onrej Sevecek: "Re: closing a specific port"
- Previous message: GSTACS R2: "Assign only one IP address to a certain USER"
- In reply to: Joe Richards [MVP]: "Re: adminDSholder being over zealous!"
- Next in thread: Joe Richards [MVP]: "Re: adminDSholder being over zealous!"
- Reply: Joe Richards [MVP]: "Re: adminDSholder being over zealous!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|