I am wondering In an environment where Exchange 2007 has been running for years, but where I see some permission related errors Would it harm to do a domainprep and forestprep again, is it safe to do so ?. I never tried to re-aply them many years after a deployment. As a side note healtcheck doesnt show the various permission problems we've had.

Hi I don't think that running a domain prep would cause any issues but it also may not resolve the issues that you are seeing. Most of the permission problems with Exchange that I have seen come from blocked inheritance either at the OU or AD object level. I would check this before taking any other steps. Cheers, Steve

You can run domainprep ( it's known as /preparead in exchange 2007) This is what it will do, it won't break anything. 1: If the Microsoft Exchange container does not exist, this command creates it. 2: If no Exchange organization container exists, than organization container will be created with the name that you specify. 3: Verifies that the schema has been updated and that the organization is up to date by checking the objectVersion property in Active Directory. The objectVersion property is in the CN=<yourorganization>,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=<domain> container. What is the issue you have related to the permissions? Can you post the event id 2080.Gulab Prasad, MCITP: Exchange Server 2010 | MCITP: Exchange Server 2007 MCITP: Lync Server 2010 | MCITP: Windows Server 2008 My Blog | Z-Hire Employee Provisioning App

As a side note healtcheck doesnt show the various permission problems we've had. Hi PGT2008, Please also run Exbpa with a Permission Check. Yes, it is safe to re-run /PrepareAD in existing infrastructure. It verifies that, everything is fine if it finds something corrupted then it will fix it. Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com Frank Wang TechNet Community Support

Although exbpa wont reveal wrong permissions in our case i mark your answer as solution (as normally that would be a wise thing to do) We tried that earlier, eventually got some permissions fixed with Microsoft PSS.