Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

Migrating to Exchange Server 2007 : Migrating from Exchange 2000 Server or Exchange Server 2003 to Exchange Server 2007 (part 7)

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
11/11/2014 3:43:53 AM

Cleaning Up the Exchange 2000 Server and Exchange Server 2003 Environments

After a new Exchange 2007 server is added to the network to functionally replace an old Exchange 2000 or 2003 server, there comes a time when the old server should be removed.

For front-end servers, however, they can be removed as soon as a new Exchange 2007 Client Access server is added to the network because the new Exchange 2007 Client Access servers will host both Exchange 2000 or 2003 back-end servers as well as Exchange 2007 Mailbox servers.

The removal process is more than just powering off the system and disconnecting it from the network. It is very important that the old Exchange servers are properly removed from the Exchange organization; otherwise, Exchange does not know that a server has been removed, and the server remains in the Exchange organization configuration tables. As an example, if you have a bridgehead server that used to route mail messages between sites and you just unplugged the server without properly removing it, Exchange servers in the organization will not know that the server has been removed, and will continue to try to route messages to the server. This could cause messages to pile up in a queue and unless the Exchange servers can recalculate a new message route for messages, the lack of removing a specific server can prevent messages from ever routing within the organization until the server is properly removed. So, remove servers properly.

The proper process of removing an old Exchange 2000 or 2003 server is a three-step process:

1.
Remove all routing connectors to the server.

2.
Uninstall Exchange from the server.

3.
Remove routing groups.

Removing Routing Group Connectors to Servers

The removal process of an Exchange 2000 or 2003 server starts with the removal of routing group connectors from the server being removed. It is important to confirm that the routing group connector that is being removed is not serving a key communication route for a site or for the organization. As an example, if the routing group connector is the only link for a server to another site in the organization, the removal of the routing group connector will have messages cease being sent or received to the remote site. Alternatively, if the routing group connector is the link between Exchange 2000 or 2003 and Exchange 2007 and if there are no other routing group connectors between Exchange 2000 or 2003 and Exchange 2007, the removal of the routing group connector will effectively drop any communications between the old and new Exchange environment.

If you are certain that the routing group connector serves no purpose, remove the routing group connector so that you can remove the Exchange server from the organization.

Tip

If you aren’t sure whether a routing group connector serves an important function in the network, and cannot figure out through looking at architectural or mail flow diagrams of the organization whether the RGC is of value, just stop the Routing Group Connector (RGC) service. On the Exchange 2000 or 2003 server, click on Start, Programs, Administrative Tools, Service. Right-click on the Microsoft Exchange Routing Engine, and choose Stop. Wait a few hours or days to see if anybody complains that their messages aren’t being transmitted properly. If after a few days no one has complained, you can probably assume the RGC is not serving any valuable function.


To remove a routing group connector, do the following:

1.
On the Exchange 2000 or 2003 server on which you plan to remove the routing group connector, launch the Exchange 2000 or 2003 System Manager program.

2.
Expand the Administrative Groups container.

3.
Choose and expand the administrative group where the server that you are on resides.

4.
Choose and expand the Routing Groups container.

5.
Choose and expand the routing group that holds the routing group connector you want to remove.

6.
Choose and expand the Connectors container.

7.
Right-click on the routing group you want to remove, and choose Delete. Confirm Yes that you want to remove the routing group connector.

This process removes the routing group connector and you can now proceed with removing the server itself from Exchange.

Uninstalling Exchange from Old Exchange 2000 Server or Exchange Server 2003 Servers

Rather than simply removing or disconnecting an old Exchange server from the network, it is important to uninstall Exchange from the old server system. The uninstall process doesn’t just remove the Exchange software off the hard drive of the system; it performs a very important task of properly removing that Exchange server from the Exchange directory.

After all mailboxes, public folder replicas, and connectors have been moved off an old Exchange 2000 or 2003 server, the server can be retired and removed from service. The easiest and most straightforward approach to this is to uninstall the Exchange 2000 or 2003 component via the Add/Remove Programs applet in Windows. To perform this operation, do the following:

1.
On the Exchange server, select Start, Control Panel.

2.
Double-click Add/Remove Programs.

3.
Select Microsoft Exchange (2000 or 2003) and click Change/Remove.

4.
Click Next at the welcome screen.

5.
Under Action, select Remove from the drop-down box, and click Next to continue.

6.
At the summary screen, click Next to continue. The Exchange server will then be uninstalled.

7.
Repeat the process for any additional Exchange 2000 or 2003 servers.

As Exchange 2000 or 2003 servers are removed from Exchange 2000 or 2003 routing groups, upon the removal of the last Exchange 2000 or 2003 system from a routing group, the routing group itself can be removed.

Removing an Exchange 2000 Server or Exchange Server 2003 Routing Group

In Exchange 2000 or 2003, routing groups are containers that hold groups of Exchange servers that frequently communicate with each other, typically servers within a site, or servers within a region. Because the concept of a routing group does not exist in Exchange 2007, as Exchange 2000 or 2003 servers are removed from the network, when the last Exchange server in a routing group has been removed, the routing group itself can be deleted, thus cleaning up the Exchange environment of remnants of Exchange 2000 or 2003.

To remove a routing group, do the following:

1.
Remove routing group connectors to servers that are being removed per the instructions .

2.
Remove old Exchange 2000 or 2003 servers as they are no longer needed.

3.
When all of the servers in a routing group have been removed, go into the Exchange 2000 or 2003 System Manager utility by selecting Start, All Programs, Microsoft Exchange, Exchange System Manager.

4.
Expand the Administrative Groups container.

5.
Choose and expand the administrative group where the routing group that you want to remove resides.

6.
Choose and expand the Routing Groups container.

7.
Choose and expand the routing group that you want to remove and confirm that no member servers exist in the routing group anymore by choosing the Members container to see if any servers exist.

8.
If no servers are in the Members container, right-click on the routing group that you want to remove, and select Delete. Confirm Yes that you want to remove the routing group.

Upon removal of the last Exchange 2000 or 2003 routing group, the environment should be completely void of any Exchange 2000 or 2003 servers. There is no Native Exchange 2007 mode. The removal of the last Exchange 2000 or 2003 routing group clears legacy mail routing that is no longer needed in Exchange 2007.

Other -----------------
- Migrating to Exchange Server 2007 : Deploying a Prototype Lab for the Exchange Server 2007 Migration Process
- Migrating to Exchange Server 2007 : Moving to Native Mode in Exchange
- Migrating to Exchange Server 2007 : Understanding What’s New and What’s Different with Exchange Server 2007
- Migrating to Exchange Server 2007 : Understanding How to Migrate to Exchange Server 2007
- Sharepoint 2013 : Working with the CSOM (part 6) - Working with the JavaScript client object model - Creating, reading, updating, and deleting in the JavaScript client object model
- Sharepoint 2013 : Working with the CSOM (part 5) - Working with the JavaScript client object model - Handling errors
- Sharepoint 2013 : Working with the CSOM (part 4) - Working with the JavaScript client object model - Returning collections
- Sharepoint 2013 : Working with the CSOM (part 3) - Working with the managed client object model - Creating, reading, updating, and deleting
- Sharepoint 2013 : Working with the CSOM (part 2) - Working with the managed client object model - Handling errors
- Sharepoint 2013 : Working with the CSOM (part 1) - Understanding client object model fundamentals
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server