Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.
- Create BookmarkCreate Bookmark
- Create Note or TagCreate Note or Tag
- DownloadDownload
- PrintPrint
Chapter 19. Exchange Server 2010 Message... > Using Default Message Routing
Using Default Message Routing
The first thing to understand about remote mailflow to another Active Directory site is that routing groups are no longer used. To support coexistence between Exchange 2010 routing and Exchange 2003, all Exchange 2010 servers are automatically added to a single routing group when they are installed. The Exchange 2010 routing group is recognized in Exchange System Manager in Exchange 2003 as Exchange Routing Group (DWBGZMFD01QNBJR) within Exchange Administrative Group (FYDIBOHF23SPDLT), but it is not recognized in Exchange Management Console (EMC) or Exchange Management Shell (EMS). Both the routing group and the administrative group are hidden in the Exchange 2010 tools. Do not move Exchange 2010 servers out of Exchange Routing Group (DWBGZMFD01QNBJR). Do not move Exchange 2003 servers into it (except when you’re decommissioning the last 2003 routing group). Also, don’t rename either the hidden routing group or the hidden administrative group with any utilities that may be able to do so.
Tip
Increasing each letter/number in the routing group’s name by one spells “EXCHANGE12ROCKS,” in case you were wondering what the deal was with all the letters. This might have made sense in Exchange Server 2007, even if you didn’t care for it. However, the name is still the same in Exchange Server 2010 (Exchange 14.)
