As far as I know, there is no DC locator flag for this. I think you can
found out by reading rootDSE, but I can't remember exactly what to look
for
and don't have a handy RODC to check. Essentially, my answer is not very
useful as I'm really not sure. :)
I asked someone for clarification but didn't get a response (hence the
delay), but I'll ask again.
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
"JRB" <john@[EMAIL PROTECTED]
> wrote in message
news:3b81b97b-ee2d-4397-be34-9f426b962297@[EMAIL PROTECTED]
Jul 1, 11:23 am, "Joe Kaplan"
<joseph.e.kap...@[EMAIL PROTECTED]
> wrote:
> Probably the two biggest things to be careful about are watching out for
> RODCs if they are deploying any and your app writes to the directory
> (RODCs
> won't accept writes) and being careful about how you calculate password
> expiration if they are using fine-grained password policies.
Joe
What is the recommended method to identify an RODC? Is there a new bit
defined in the sv102_type field of NetServerGetInfo, or is there a
property of the AD server object which indicates its RO?
TIA, John
|
