Hi, We have a small domain (facilities) with users on our Exchange server in a different domain. All mail functions seem fine but I learned that setup /preparedomain had never been run on the facilities domain. Are there any problems or implications with running it on the facilities domain now?

Forgot to mention versions: Domain = 2003 Functional Level, Exchange = Exchange 2007 SP2

Hi Should you install Exchange into that domain? No you can run it, if you are going to install into the domain otherwise there's no needJonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

Hi, Actually, the installer have done all the AD/Domain preparation automatically when you install Exchange server. So you do not need to run /preparedomain manually.

This domain will not have an Exchange server installed into the domain. It was setup after our original Exchange install and hosts some Exchange users.

Actually, I do need to run setup /preparedomain http://technet.microsoft.com/en-us/library/bb125224.aspx You must run this command in every domain in which you will install Exchange 2010. You must also run this command in every domain that will contain mail-enabled users, even if the domain doesn't have Exchange 2010 installed. I just want to make sure I won't cause any issues for existing mail-enabled users in the domain.

Hi, >>"You must run this command in every domain in which you will install Exchange 2010". This is right. If the setup /preparedomain is not performed, you are unable to install exchange server into your domain. I think your exchange server was installed by using the UI interface (Setup.exe). The setup.exe automaticly performed these tasks for you. The articles on TechNet shows how to perform these tasks manually.

You weren't reading the details of the scenario - the child domain was installed AFTER exchange was installed and according to this thread I do need to run setup /preparedomain http://technet.microsoft.com/en-us/library/bb125224.aspx