Creating Routing Group Connectors

The first routing group connector between Exchange 2010 and Exchange 2003 is created and configured during installation of the first Hub Transport server role in an existing Exchange organization. While this connector works, it is better to create a bidirectional RGC so mail flows back and forth over the same route. So... delete the one Exchange 2010 creates and then create a new one with this command:

New-RoutingGroupConnector -Name "Interop RGC" -SourceTransportServers "HUB1.domain.com" -TargetTransportServers "EX2003.domain.com" -Cost 10 -Bidirectional $true -PublicFolderReferralsEnabled $true

Once the Interop RGC is created, you can add addtional servers as required. Since the RGC is bidirectional, the name is going to be the same for the RGC in 2003 and 2010, so when adding additonal servers to the RGC, you will need to do it for both routing groups. Use the following commands:

For the 2010 connector:

set-RoutingGroupConnector -Identity "Exchange Routing Group (DWBGZMFD01QNBJR)\Interop RGC" -SourceTransportServers "HUB1.domain.com","HUB2.domain.com" -TargetTransportServers "EX2003.domain.com"

For the 2003 connector:

set-RoutingGroupConnector -Identity "First Routing Group\Interop RGC" -SourceTransportServers "EX2003.domain.com" -TargetTransportServers "HUB1.domain.com","HUB2.domain.com"

Re-balance active database copies across the DAG

Here is a handy batch file that will redistribute the active databases across the DAG:

cd C:\Program Files\Microsoft\Exchange Server\V14\Scripts
powershell -noexit -command "& ".\RedistributeActiveDatabases.ps1 -DagName DAG1 -BalanceDbsByActivationPreference -ShowFinalDatabaseDistribution -Confirm:$false" "

Copy and paste the above into notepad and save it as a batch file. Make sure you change the path for your install location as well as change the name of the DAG to match what is in your environment.

Change OWA timeouts

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeOWA
Name: PublicTimeout
Type: DWORD
Value: {value in minutes} (This value is 15 minutes by default)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeOWA
Name: PrivateTimeout
Type: DWORD
Value: {value in minutes} (This value is 8 hours by default)

Details of Exchange Enterprise CAL

Provides detail and pictures of Exchange Enterprise CAL features

http://chrislehr.com/2009/12/exchange-2010-enterprise-client-access.htm

Exchange 2010 and OCS 2007 R2 Integration

http://www.networkworld.com/community/node/47348

Proper syntax on OWA server is Get-OwaVirtualDirectory -server SERVERNAME Set-OwaVirtualDirectory -InstantMessagingType 1

OCS Web Access ... create TLS certificate

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/MS_Live_Communications_Server/Q_24034409.html

Exchange 2010 Install Steps

• Setup Scripts available on Exchange CD


• ServerManagerCmd -i RSAT-ADDS Web-Server Web-ISAPI-Ext Web-Metabase Web-Lgcy-Mgmt-Console Web-Basic-Auth Web-Digest-Auth Web-Windows-Auth Web-Net-Ext Web-Dyn-Compression NET-HTTP-Activation RPC-over-HTTP-proxy –restart


• Installed 2007 Office System Converter: Microsoft Filter Pack http://www.microsoft.com/downloads/details.aspx?FamilyId=60C92A37-719C-4077-B5C6-CAC34F4227CC&displaylang=en


• Run ‘Set-Service NetTcpPortSharing -StartupType Automatic’ from PS console


• Run Install from CD


• Add product key for all servers


• Configure Send and Receive Connectors


• On CAS server, create web access certifcate and assign roles (make sure to add a legacy name for the Exchange 2003 OWA server, ie. legacy)


• Create DNS A record for legacy.domain.com


• To have co-existence between OWA users, run Set-OwaVirtualDirectory -Identity "SERVERNAME\owa (default Web site)" -Exchange2003Url https://legacy.domain.com/exchange


• Configure webmail to use username for logon


• Configure IIS on CAS to redirect to OWA directory

BES Supported on Exchange 2010

BlackBerry Enterprise Server (BES) is now fully supported on Microsoft Exchange Server 2010 and BlackBerry Technical Support Services are available. In order to enable full support, following updates are required: Roll-Up 1 (RU1) for Exchange Server 2010, MAPI v6.5.8147, and BlackBerry Enterprise Server 5.0.1 Maintenance Release 1 (MR1). All three updates are available free to customers of Exchange Server 2010 and BlackBerry Enterprise Server v.5.0 with SP1. BlackBerry Enterprise Server v5.0 SP1 and MR1 can be found here. This roll up also includes other minor updates including calendaring, OWA, and transport. You can read more about Exchange Server 2010 RU1 here, and download Exchange 2010 Update Rollup 1 here.