• Home
  • About us
  • Contact

Welcome to www.DoitFixit.com

www.doitfixit.com

  • Microsoft
  • Fortinet
  • Symantec
  • Office 365
  • Azure
  • Others

Co-Existence for Exchange 2003 and Exchange 2010 – Part III

December 14, 2012 By Damitha Anuradha Leave a Comment

Part I – Co-existence for Exchange Server 2003 and Exchange Server 2010

Part II – Co-existence for Exchange Server 2003 and Exchange Server 2010

Assigning certificate to Exchange 2003

You can use below command to get current assigned certificate for Exchange 2010.

Get-ExchangeCertificate

Then use below command line in Exchange management shell to export the certificate for Exchange 2003. You will be asking for User Name and Password, also User Name is not important.
Paste your certificate thumbprint in -Thumbprint argument.

$file = Export-ExchangeCertificate -Thumbprint 76695655A4F64BF7204863415C6DBCC0F97D1055 -BinaryEncoded:$true -Password (Get-Credential).password

Save the certificate

Set-Content -Path “C:\Exchange2010Certificate.pfx” -Value $file.FileData -Encoding Byte

Go to Exchange 2003 server and Import the above certificate (PFX) in to personal node.

Now open IIS Manager and go to Default Web Site properties.

Go to Directory Security tab and click Server Certificate in Secure Communications.

Assign an existing certificate/Replace existing certificate

Again open the Exchange System Manager and go to Exchange Virtual Server Properties.

Select Enable Forms Based Authentication in Settings tab.

Restart IIS Service.

Exchange 2003 Web access will be accessible.

Now we have to change the communication mode for Exchange 2003 to use SSL.

Now log in to Exchange 2003 mailbox through Exchange 2010 Outlook Web App.

See the redirection path bottom of the browser.

You will be redirected to Exchange 2003 user mailbox.

Now we have to configure mail flow to route mail between Exchange 2003 and 2010. Use below command to create new routing group connector.

New-RoutingGroupConnector -Name “Exchange 2003 – Exchange 2010” -SourceTransportServers “ex2003.doitfixit.com” -TargetTransportServers “ex2010A.doitfixit.com” -Cost 1 -Bidirectional $true -PublicFolderReferralsEnabled $true

Check the created connectors in Exchange System Manager.

You can delete all Routing Group Connectors by executing this command:

Get-RoutingGroupConnector | Remove-RoutingGroupConnector -confirm:$false

Also you can create Routing group connectors using below commands as well.

Routing Group Connector (Exchange Server 2010 to Exchange Server 2003)

New-RoutingGroupConnector -Name “2010-2003” -SourceTransportServers “ex2010A.doitfixit.com” -TargetTransportServers “ex2003.doitfixit.com” -Cost 1 -Bidirectional $false -PublicFolderReferralsEnabled $true

Routing Group Connector (Exchange Server 2003 to Exchange Server 2010)

New-RoutingGroupConnector -Name “2003-2010” -SourceTransportServers “ex2003.doitfixit.com” -TargetTransportServers “ex2010A.doitfixit.com” -Cost 1 -Bidirectional $false -PublicFolderReferralsEnabled $true

Lets test the mail flow.

For External web access, you should create legacy host record on your external DNS and should point to Exchange 2003 Server with a different static IP. Also you can achieve this by using ISA/TMG server with a single IP.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

LATEST ARTICLES

  • Slow Network Speed with Hyper-V Virtual Machines on Windows Server Server 2019
  • Block MS Exchange Server OWA access from Internet
  • Error 1168 – The specified product key could not be validated.
  • Unable to Enable Desktop Icons after Joining to the Domain
  • Veritas BackupExec – A backup set was created which contains no data 0xe00084b7

Copyright © 2020 · www.doitfixit.com · Log in