Your network consists of a single Active Directory forest. You have an Exchange Server 2003 organization. You need to create a plan to transition the organization to Exchange Server 2010. The plan…

Question

Options

• ATwo Send connectors a sharing policy address lists that use OPATH
• BTwo Send connectors public folder replication new address lists
• CA two-way routing group connector a sharing policy new address lists
• DA two-way routing group connector public folder replication address lists that use OPATH

• A
  6% (2)
• B
  11% (4)
• C
  3% (1)
• D
  80% (28)

Explanation

Two-way routing group connector: When you install Exchange 2010 in an existing Exchange 2003 organization, Setup performs the following coexistence-specific tasks: Creates the Active Directory universal security group ExchangeLegacyInterop. This group is granted the permissions that allow the Exchange 2003 servers to send e-mail messages to the Exchange 2010 servers. Creates a two-way routing group connector between Exchange 2010 and a selected Exchange 2003 bridgehead server. Exchange 2010 and Exchange 2003 use different routing topologies. You must configure a routing group connector to enable mail flow between the Exchange The two servers that we were connecting were server1 (exchange 2003) and server2 (exchange 2010). We use the following command to complete this: New-RoutingGroupConnector -Name "VSERVER13toDGM56G41"- SourceTransportServers "server2. fserver4.com"-TargetTransportServers "server1.fserver4.com"-Cost 100 -Bidirectional $true- PublicFolderReferralsEnabled $truethis created you will need bidirectional messaging. A bidirectional connector is actually just two connectors so create a routing group connector in the direction you need. In Microsoft Exchange Server 2003 and earlier versions LDAP filtering syntax is used to create custom address lists, global address lists (GALs), e-mail address policies, and distribution groups. In Exchange Server 2010 and Exchange Server 2007, the OPATH filtering syntax replaces the LDAP filtering syntax. Using the OPATH filtering syntax allows you to create filters directly in Exchange Management Shell commands by using the - RecipientFilter parameter. For administrators that have supported Exchange since Exchange 5.5 or 2003 days, you know that if you have a large organization with multiple domains, you likely have several Address Lists and Email Address Policies that need to be upgraded to Exchange 2007\2010 format. The problem is when you migrate to Exchange 2007 or 2010, the syntax or Opath format is no longer supported in the old version. Essentially the Opath format is a LDAP filter, where the syntax between the different types of Exchange versions is drastically different. This causes old address list queries to not produce any user while searching. (Typically from the Outlook address book or

No community discussion yet for this question.