Transfer Exchange 2003 to Exchange 2007 (P.4)

In this section we will install additional Exchange 2007 servers, and configure these servers.

Transfer Exchange 2003 to Exchange 2007 (P.4)

Network administration - Exchange system has been gradually formed through the first three parts of this article. So far, we have incorporated the Hub Transport Server and Client Access Server as well as the Clustered Continuous Replication environment consisting of two nodes, which are components that coexist with existing Exchange 2003 servers. However, at this point we still need to install additional Exchange 2007 servers.

>> Transfer Exchange 2003 to Exchange 2007 (Part 1)
>> Transfer Exchange 2003 to Exchange 2007 (Part 2)
>> Transfer Exchange 2003 to Exchange 2007 (Part 3)

Install Edge Server

The last server to deploy is the Edge Transport server used to replace an existing server using MailSweeper software. The MailSweeper server is configured to send and receive Internet Mail through the MessageLabs service, so this configuration still has to be kept in order for configuration management to be easier, because then you won't have to change things like copies. Mail Exchange recording is stored in the system. Dedicated server like Edge Transport server is prepared with the same type of application deployed on other functional servers such as .NET Framework, Powershell, etc. In addition, this server's DNS Suffix is changed from option By default it has a Fully Qualified Domain Name (FQDN).

To change DNS Suffix, open the computer properties window and select the Computer Name tab. Here, click on the Change button, then you will see the Computer Name Changes window pop up, click the More . button to open the DNS Suffix and NetBIOS Computer Name window. In this window you can enter the main DNS Suffix as shown in Figure 1.

Figure 1: Enter the main DNS Suffix.

You need to make sure that the Edge Transport and Hub Transport servers can handle all different names through normal server files or DNS. Also, in part one, the Edge Transport server is already a member of the internal Active Directory domain, so we removed it from this domain and moved it back to a workgroup configuration.

An important component added to the Edge Transport server is Active Directory Application Mode (ADAM). ADAM needs to be used because the Edge Transport server is running on Windows Server 2003; If the Eddge Transport server operates on Windows Server 2008 you will have to install Active Directory Lightweight Directory Services to replace ADAM on Windows installation options.

Once the related DNS changes have been made and ADAM has been installed, we will proceed to install the Edge Transport server. After you have completed the installation of the Edge Transport server and the related Update Rollup has been applied, enter the Product Key for this server. Although there is now an Edge Transport server, this server is not configured to perform any functions yet. Therefore, we need to register this Edge Transport server into the Active Directory that currently contains Hub Transport function servers.

Edge Subscription Process

Edge Subscription Process is an important feature of Edge Transport server functionality. It allows registering one or more Edge Transport servers to the Active Directory site containing Hub Transport servers, resulting in a one-way mirroring of configuration information as well as information received from Active Directory. in ADAM database running on Edge Transport servers. The main benefit from this process is that you can optionally create the necessary configuration changes on the Hub Transport server and copy to Edge Transport servers. In addition, mail sent from Outlook will be aggregated on the Edge Transport server.

Below is the process needed to register the Edge Transport server, EDGE1 , to the Active Directory site containing both Hub Transport servers.

First open Exchange Management Shell on EDGE1 and run the following command:

New-EdgeSubscription -FileName 'c: EdgeSubscription.xml'

This command will create the signed information in a file called EdgeSubscription.xml outside the C: drive on EDGE1 . Note that the information shown in Figure 2 indicates that you must complete the registration within 1440 minutes before the startup account expires.

Transfer Exchange 2003 to Exchange 2007 (P.4) Picture 2

Figure 2: Information displayed when running the New-EdgeSubscription command

Next we have to copy the contents of this XML file from EDGE1 to one of the Hub Transport servers.

The Edge server registration process can then be completed using either the Exchange Management Console or Exchange Management Shell on the Hub Transport server. If you choose the Exchange Management Console then you will have to go to the Organization Configuration , select Hub Transport and then select New Edge Subscription on the context menu.
In the New Edge Subscription wizard, you need to install the Active Directory site correctly for the Active Directory site , then click the Browse button to import the previously copied EdgeSubscription.xml file. Also select the Automatically create a Send connector check box for this Edge Subscription (automatically create a Send Connector for this Edge registration process) as shown in Figure 3. Note, in this example the name of the Active Directory page is HeadOffice .

Transfer Exchange 2003 to Exchange 2007 (P.4) Picture 3

Figure 3: New-EdgeSubscription Wizard.

Once this wizard has started, you will see a warning that requesting a name convention between the Edge Transport and Hub Transport servers so that Hub Transport servers can connect to the Edge Transport server via port 50636 . That's why it is necessary to ensure a naming convention is applied, and make sure that the firewall system is correctly configured.

Finally, we'll force the synchronization process to take place immediately using the Start-EdgeSynchronization command and check if the process is successful. See the example in Figure 4.

Transfer Exchange 2003 to Exchange 2007 (P.4) Picture 4

Figure 4: Edge synchronization process successfully completed.

Internet Mail

Keep in mind that the Edge synchronization process will automatically create the Send Connector that should be used to send Internet Mail out of the system. However, this Send Connector has a blank address space *, which means it will be able to handle mail sent to all Internet domains, and it can also be configured with a default value of 100, yes. This means that any existing SMTP Connector configured in Exchange 2003 may have a smaller value and must still be used as a Connector to send Internet Mail. In other words, Internet Mail will still be sent in the current direction rather than through the new direction configured in the Edge Transport server. You can see the empty address space and configure the value in Figure 5, where the basic properties of Send Connector are displayed on the Exchange Management Shell.

Transfer Exchange 2003 to Exchange 2007 (P.4) Picture 5

Figure 5: Send Connector default address space and value.

Then we need to check if this Edge Transport server can send and receive Internet Mail. Before doing this, you need to make sure that the MessageLabs system recognizes this new server. To test email connectivity, increase the value of the Exchange 2003 SMTP Connector and lower the value of the Exchange 2007 Send Connector to make this Send Connector a priority. Also, need to change Protocol logging level to Verbose on this send Connector (Figure 6). Keep in mind that these configuration types are implemented on the Hub Transport server and copied to the Edge Transport server through the Edge registration process.

Transfer Exchange 2003 to Exchange 2007 (P.4) Picture 6

Figure 6: Changing the Protocol logging level for Send Connector.

In doing so we will be able to check the information in the Send Connector protocol logs on both the Edge Transport and Hub Transport servers to confirm that these servers handle mail better than the legacy servers of Exchange 2003. By default, these log files are stored in two subdirectories in the Program FilesMicrosoftExchange ServerTransportRolesLogsProtocolLog folder as shown in Figure 7.

Transfer Exchange 2003 to Exchange 2007 (P.4) Picture 7

Figure 7: SMTP protocol log.

Conclude

In Part 4, we have completed the installation of an existing Exchange 2007 system in parallel with Exchange 2003. You can keep your Internet Mail connection intact until you have moved all users to Exchange 2007. We will begin to configure the Exchange 2007 system before moving the mailboxes.

Transfer Exchange 2003 to Exchange 2007 (P.7)
in the previous section, we have configured some of the necessary components in the exchange 2007 environment, such as the ccr and transport dumpster configuration parameters.
Transfer Exchange 2003 to Exchange 2007 (Part 2)
in this article, we will continue the process to build the exchange 2007 system starting with the installation of the hub transport and client access server.
Transfer Exchange 2003 to Exchange 2007 (P.5)
in the previous four sections, we have built a new exchange environment that is coexisting with the original exchange 2003 environment.
Transfer from Linux Mail Server to Exchange Server 2007 (Part 1)
in exchange server 2003, we can use the exchange migration wizard to switch from an imap4 running environment to active directory and exchange server 2003. in this article, however, i don't want to talk about exchange server 2003 but instead. gi
Transfer Exchange 2003 to Exchange 2007 (Part 3)
in the previous two sections, we installed the first exchange 2007 servers, combining hub transport and client access servers in an exchange 2003 environment.
Transfer mailboxes in Exchange 2007 through the Exchange Management Console
there are many tasks that every exchange administrator must perform daily and moving mailboxes is one of those tasks. the most obvious example of mailbox migration is when a user is moved from one exchange server to another
Transfer Exchange 2003 to Exchange 2007 (P.6)
in this section, we have configured the settings related to the hub transport function server. in this section we continue to configure the exchange 2007 environment.
Transfer Exchange 2003 to Exchange 2007 (Part 1)
in this series, we will learn how to migrate data from exchange server 2003 system to exchange server 2007 system.
Transfer MDaemon to Exchange 2007/2003 (Part 2)
in the previous section, we learned how to export and import accounts and passwords from mdaemon to active directory of exchange server systems when needed.
Transfer mailboxes in Exchange 2007 through Exchange Management Console (Part 2)
in part 1 of this article, we introduced the move mailbox utility that is included in the exchange management console as well as other event logs recorded when the mailboxes were moved in exchange 2007. although the move mailbox utility provides one. the interface is simple to perform mailbox migration between databases and servers but it still lacks some
Transfer MDaemon to Exchange 2007/2003 (P.7)
in the last part of this series we will perform some administrative tasks that a mdaemon system administrator should know in an exchange server 2007 environment.
Remote Exchange 2003 administration
you already know about exchange 2005, exchange 2007, but the most basic concepts are provided in hand? in the following article, we will discuss how to remotely access the exchange management console anywhere, at any time.