Link to home
Create AccountLog in
Avatar of seag33k
seag33k

asked on

Help - MS Exchange Best Practice Analizaer - Inheritance Block

I just ran the MS Exchange Best Practices Analyzer and one of the errors I am getting refers to an Inheritance Block.  I've followed the link to enable the security tab and followed the path to the given object but am not clear on where and how to re-enable inheritance on the object in question.  Here is the opbject path:

(CN=ExchangeServer,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=mydomain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=local).

When I locate the object in Exchange System Manager, it points to the server.  When open its properties and select the security tab I get a list of users.  Is there a particular user to edit and allow inheritance? or am I missing a key step?

Thanks!
Avatar of abhaigh
abhaigh
Flag of United Kingdom of Great Britain and Northern Ireland image

ADSIEdit connected to the Configuration naming contex will allow you to set the permissions on that object
Avatar of seag33k
seag33k

ASKER

For some reason I cannot find the first CN (CN=Configuration) thus the rest of the path for the object in question.  Do I need to enable any views for ADSIEdit?
after you run ADSIEdit - you need to right click on it and choose 'connect to' - that will present you with a dialogue sheet where you can choose which naming context you wish to attach to - it defaults to Domain
Avatar of seag33k

ASKER

Thanks! I found the object (CN=ExchangeServer).  When I select the security tab I am again given a list of Groups and Users.  Is there a particular user I am suppose to give inherit permissions to?

Thanks!
ASKER CERTIFIED SOLUTION
Avatar of abhaigh
abhaigh
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of seag33k

ASKER

I added Allow inheritable permissions to the Exchange Domain Servers as you suggested and re-ran the analyzer and the error is now gone :)

Thanks for the help!

Eric