Azure Hybrid & Cloud Migration Blog

Compatibility Exchange 2010 SP2 RU 1 CAS-to-CAS Proxying issue with NON-Exchange 2010 SP 2 RU 1 Servers

Author: Zahir Hussain Shah | MVP Exchange Server, CISSP

All those who have applied Exchange 2010 SP 2 RU 1 in their Exchange environment, will see a problem for Exchange 2010 CAS to CAS proxy between Exchange 2010 SP2 RU1 to non-Exchange 2010 SP2 RU1 Servers, because Microsoft Exchange 2010 SP2 RU1 introduced a new method of user context cookie which is used in CAS-to-CAS proxying.

Problem:

All those customers, who are using CAS to CAS Redirection will not be affected with this change, but all you those who are doing CAS to CAS Proxy in between your Exchange Servers, where some of your Internet and NON-Internet facing CAS Servers are still not been updated for Exchange 2010 SP 2 RU1, will be suffered from this problem.

Resolution:
Update your Non-Exchange 2010 SP2 Servers with Exchange 2010 SP2 RU1 to fix this problem, or read more here

Cheers!

zahir_sig_rahat_pc_1.png

Azure Hybrid Blog

2 responses to “Compatibility Exchange 2010 SP2 RU 1 CAS-to-CAS Proxying issue with NON-Exchange 2010 SP 2 RU 1 Servers”

  1. Mohammed Osman Siddiqui

    As salaam alaikum Zahir, I am a Microsoft Certified Engineer, working in Kuwait, planing for an Upgrade of EX2003 to Ex2010, with two Server boxes with out HLB, Kindly suggest how can I go about it ?

  2. Zahir Hussain Shah

    Okay, so if you don’t wana use HLB for load-balancing your CAS, then you can use W-NLB.

    you can check my past posts, you will get the step by step guide for how to build a W-NLB cluster for your Exchange 2010 Servers.

    Moreover, if you wana know how to step by step transition / upgrade from Exchange 2003 / 2007 to Exchange 2010 Server, also you will find my previous post for the same.

    You can also check for Exchange Server Deployment Assistant (http://blogs.technet.com/b/exchange/archive/2012/03/21/exchange-server-deployment-assistant-update-for-exchange-2010-sp2-and-office-365-hybrid-deployments.aspx)

Leave a comment