Prepare Active Directory for Exchange 2007 (Part 2)

In part one, we went over the first four steps to take to prepare the Active Directory schema to receive Exchange 2007.

>> Prepare Active Directory for Exchange 2007 (Part 1)

First we need to prepare the legacy permissions for Exchange in case the legacy versions of Exchange exist, such as Exchange 2000 or Exchange 2003. Also in part one we just run the setup / PrepareLegacyExchangePermissions command to display a The number of errors should be fixed before the preparation process is completed. These problems are displayed in the command window but there are a number of other methods to check what happened when running these prepared commands.

In this section we will focus on checking whether the process of preparing an Exchange heritage license is successful.

Install Log files

For every preparatory process that we will perform in this article, the Log files (logs) will be created and we can check after this process completes to see if an error occurs. The file to check is ExchangeSetup.log, created in the C: ExchangeSetupLogs folder as shown in Figure 1.



If you open the ExchangeSetup.log file in Notepad, you will see the same errors and warnings in the text file that we have seen in the command window (in part one). These errors are highlighted in Figure 2.



You should note that some errors have hidden other errors that may appear in the legacy Exchange system. For example, when adding a current account to the Enterprise Admins group and moving the legacy Exchange system to a natural node, then run the setup command again.
/ PrepareLegacyExchangePermissions will cause a new error as shown in Figure 3. It means that one or more Exchange 2003 servers in the legacy system have not installed Exchange 2003 SP2 version. Therefore you need to make sure that you have fully archived the legacy Exchange system and fixed any errors that may hinder the process of preparing legacy Exchange licenses before running this command. If you do not do so, you need to run this command repeatedly to detect any missing errors.



Finally, you will be able to run the setup / PrepareLegacyExchangePermissions command successfully as shown in Figure 4. However, you should be aware of the warning that the .NET Framework 2.0 SP1 still exists and this warning is not true. obstructing the process.

---

Check out groups Permissions

1. Run LDP.EXE .
2. At the LDP window, click on the Connection button and then click Connect .
3. In the Connect window, enter the name of the original Domain Controller and click OK as shown in Figure 6.

1. When returning to the main LDP window, click Connection and then click on Bind .

1. In the Bind window, enter the user name, password, and domain of a licensed user account, such as the administrator account of the root domain as shown in Figure 7.

---

1. In the results window of Security Descriptor , leave the Dn field blank and click OK .

1. Click Connection to select New to delete the right panel.
2. In the left panel, expand the object domain and then double-click the System object. Just inside the System object you will see the AdminSDHolder object.
3. Click Connection to select New to delete the right panel.
4. Right-click on the AdminSDHolder object, select Advanced and then select the Security Identifier .
5. At the Security Identifier window, leave the Dn field blank and click OK .
6. You will then see a lot of ACE information displayed in the right panel. You can check the entire list to find out which items to install ReadProperty and WriteProperty for the Exchange Enterprise Servers group as shown in Figure 12.

So far we have completed testing legacy Exchange licensing settings.

Conclude