Distinguished name of Configuration in AD is tampered?
- by Natan Abolafya
A user of our product came out with a problem which was caused by the DN of Configuration object in AD. We had a rather static lookup method to find Configuration object, thus it failed.
Let's say the domain name of AD is foo.bar.example.com. Therefore, the expected DN of configuration should be CN=Configuration,DC=foo,DC=bar,DC=example,DC=com, right?
But somehow, this user's DN of configuration has one value missing:
CN=Configuration,DC=bar,DC=example,DC=com.
Do you know how can we reproduce this issue (or is it commonly implemented?)?
