Tuesday, February 8, 2011

It's all about the MRS

Why reinvent the wheel... or rewrite it.  Great article about the Microsoft Replication Service and changing the worker threads for moving mailboxes.


Tuesday, December 21, 2010

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"

Wednesday, December 15, 2010

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.

Thursday, April 1, 2010

Change OWA timeouts

Name: PublicTimeout
Value: {value in minutes} (This value is 15 minutes by default)

Name: PrivateTimeout
Value: {value in minutes} (This value is 8 hours by default)

Thursday, February 11, 2010

Friday, December 18, 2009

Exchange 2010 and OCS 2007 R2 Integration


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

OCS Web Access ... create TLS certificate