<div>
If your domain has Exchange 2003 installed you need to run setup /PrepareLegacyExchangePerm<wbr />issions before you run setup /PrepareSchema...<br />
<br />
PLP should run automatically if previous versions of exchange is detected but i would try running setup /PLP:domain.com
</div>


If your domain has Exchange 2003 installed you need to run setup /PrepareLegacyExchangePermissions before you run setup /PrepareSchema...

PLP should run automatically if previous versions of exchange is detected but i would try running setup /PLP:domain.com

<div>
/preparelegacyexchangeperm<wbr />issions ran successfully. &nbsp;/prepareschema ran successfully. &nbsp; /prepareAD is the portion that I'm referring to which creates the Interop admin group and the security group OU. &nbsp;
</div>


/preparelegacyexchangepermissions ran successfully.  /prepareschema ran successfully.   /prepareAD is the portion that I'm referring to which creates the Interop admin group and the security group OU.  

<div>
<div class="content wysiwyg-content">
Our environment consists of a top-level root domain as a placeholder domain and our production domain underneath. &nbsp;We just ran setup /prepare schema and /prepareAD last night. &nbsp;I noticed that new Microsoft Exchange Security Groups OU and security groups were added to the top-level domain and not the domain in which Exchange is currently installed. &nbsp; Given that the domains are trusting each other, will this present any complications? &nbsp;I was expecting the new security group OU to be added to our production domain. &nbsp;Docs I've found indicate this new OU should be created in the forest root domain which would mean we are OK. &nbsp;The new Exchange 2007 administrative group was added successfully in the ESM. &nbsp;Please advise.
</div>
</div>


Our environment consists of a top-level root domain as a placeholder domain and our production domain underneath.  We just ran setup /prepare schema and /prepareAD last night.  I noticed that new Microsoft Exchange Security Groups OU and security groups were added to the top-level domain and not the domain in which Exchange is currently installed.   Given that the domains are trusting each other, will this present any complications?  I was expecting the new security group OU to be added to our production domain.  Docs I've found indicate this new OU should be created in the forest root domain which would mean we are OK.  The new Exchange 2007 administrative group was added successfully in the ESM.  Please advise.

Exchange 2007 ADprep with multiple domains

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.