Setup /preparedomain exchange 2013

The same is also true when upgrading from Exchange to Exchange , if there are no Exchange servers in the organisation. As mentioned above, it is not the act of installing the files onto the disk of the new Exchange server that blocks the installation of Exchange. Nor is it the act of extending the schema to support Exchange The individual steps to manually prepare the AD infrastructure for Exchange are listed in the Prepare Active Directory and Domains documentation for Exchange , Exchange and also Exchange Since Exchange has a hard requirement that Exchange and also has been removed from the organisation prior to starting its setup, this is no longer required.

You say this would never happen? Let me give you the following scenario. Assume you get a shiny new administrator workstation that has the latest version of Windows installed. In order to install the Exchange management tools you need to install the management tools from the latest build of Exchange. Morale of the story? You should not need schema admin permissions for your day to day role, even for a highly trusted administrator. Grant and revoke schema admin membership as needed.

Less is more! Running Exchange setup checks the current status of Active Directory and the Exchange organisation. Besides warning that some infrastructure bits are missing, it does warn that if you continue with this course of action, you will be unable to introduce older versions of Exchange if they are not currently present.

Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? In this article. Restart Windows to proceed with the dependencies for Exchange Server Now check for all available updates, install and restart between updating.

When all updates have been installed, download and install the following in order:. With elevated privileges, run setup. Important: If you encounter an ' An error occurred during forest discovery ' error, this means that certain MS Exchange Services have failed to start.