Home > Articles

  • Print
  • + Share This
This chapter is from the book

This chapter is from the book

Connection Agreement Testing

Now that you have a live Exchange 2003 server, you can test the Connection Agreements created by the ADC. Here's a list of experiments you should perform to familiarize yourself with the ADC operation. For the sake of getting the most experience possible from the experiments, check the Application Log on the ADC server during each experiment to see the events that occur as objects replicate back and forth between legacy Exchange and Active Directory.

  • Create a new mailbox-enabled user and verify that the ADC creates a mailbox in legacy Exchange with an owner whose name matches the new user. You might want to use the LDAP Browser (LDP) to see how the ADC-Global-Names attribute gets fleshed out as the attributes replicate back and forth between Active Directory and the legacy Exchange directory service.

  • Create a new mail-enabled group and verify that the ADC creates a distribution list in legacy Exchange.

  • Add members to a mail-enabled group in Active Directory and then see if they appear in the legacy distribution list.

  • Connect to a legacy mailbox with Outlook to make sure you have access permission via SIDHistory (if applicable) and to make sure you can add members to distribution lists and send mail to the members. Verify that the members appear in the group in Active Directory.

  • Create a new mail-enabled contact and verify that the ADC creates a custom recipient in legacy Exchange. Check the legacy attributes to verify that the e-mail address you gave the contact appears in the custom recipient.

  • Create a new mailbox in legacy Exchange using Admin and give the mailbox an owner from Active Directory who does not already have a mailbox. Verify that the ADC populates the user account with e-mail attributes so that the account now shows as a mailbox-enabled user.

  • Delete a mailbox in legacy Exchange and verify that the ADC removes the e-mail attributes from the corresponding user in Active Directory. Do this for a user with a mailbox on the legacy Exchange server and for a user with a mailbox on the Exchange 2003 server. Note that the Exchange 2003 mailbox does not actually get deleted when you delete the mailbox in legacy Exchange. Instead, run the Mailbox Cleanup Wizard to see that the mailbox gets a big red X and that you can link it to the same or another user. See Chapter 5, "Managing Recipients and Distribution Lists," for details.

  • Delete a distribution list and a contact in legacy Exchange and verify that the ADC strips e-mail attributes from the corresponding objects in Active Directory. Note that the Active Directory objects themselves remain and that the membership of a group remains intact.

  • Place a Universal Distribution Group on a public folder permission list and verify that it gets promoted to a Universal Security Group in a few minutes. The Exchange Information Store service performs this upgrade, so you might want to check the Event Log for MsExchangeIS events.

  • Create a new public folder using Outlook or ESM, and verify that the ADC creates a corresponding Public Folder object in the Microsoft Exchange System Objects container in the domain.

  • Delete a public folder and verify that the ADC removes the Public Folder object from the domain.

  • Replicate public folder content by including the new Exchange server in the replication list for each public folder using the steps outlined in Chapter 10, "Managing Public Folders." You'll eventually decommission the legacy server so you want to move all public folders and system folders to Exchange 2003 servers.

  • Verify that Schedule + Free Busy replicates to the new server by opening a new user and creating an appointment and then opening another user and verifying that the appointment appears in the availability columns.

The final set of ADC tests involve the Configuration Connection Agreement created when you installed the first Exchange 2003 server in the site.

  • Legacy Exchange. Launch Admin at a legacy Exchange server in the same site as the new Exchange 2003 server and verify that the new server appears in the Configuration container.

  • Active Directory. Launch ESM and drill down to the Administrative Group representing the legacy site and verify that you have black-and-white icons representing the legacy Exchange servers.

If you don't see this information, force the CA to replicate by right-clicking the CA object and selecting Replicate Now from the flyout menu. Check the Event Log to make sure there aren't any errors. If you experience any issues, you can use the Diagnostics Logging tab in the properties window for a server in ESM to assist in troubleshooting (or to overwhelm you with information).

  • + Share This
  • 🔖 Save To Your Account