Exchange 2010 / 2013 - Ambiguous URLs, Static MAPI Ports and a Loadbalancer

Hi Everyone, 

in a scenario like this: 

From this article

Where Exchange 2013 is already in place together with Exchange 2010, and shares the same namespaces, but the MAPI ports on Exchange 2010 are fixed to ... Port1 for MAPI, Port2 for addressbook..etc. 

Would it be possible to address the Ambiguous URL issue with a Rule on the Loadbalancer which sends the Outlook Clients back to Exchange 2010 if they are going to speak MAPI over the defined ports ?  In our tests this worked like a charm. 

thanks in advance, 

Rob




  • Edited by Robad 19 hours 39 minutes ago changed title
March 13th, 2015 7:42am

Well, if it works, I guess so.

Is that supported? Probably not, but if it works, then go for it knowing that if you run into any issues that require support, they may tell you to undo that.

Free Windows Admin Tool Kit Click here and download it now
March 13th, 2015 12:03pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics