How to Configure ActiveSync Virtual Directories in coexistence between exchange 2007 and 2013, when you have different external and internal namespaces




In coexistence environment (exchange 2007-2013), we could set Exchange 2013 ActiveSync External URL to mail.yourexternaldomain.com and set Internal URL to mail.yourinternaldomain.com. And set Exchange 2007 Internal URL to mail.yourinternaldomain.com and set External URL to Null. 

We could run the following commands.

Set-ActiveSyncVirtualDirectory -Identity "<CAS2013>\Microsoft-Server-ActiveSync (Default Web Site)" -ExternalUrl "https:// mail.yourexternaldomain.com /Microsoft-Server-ActiveSync"  –InternalURL “https:// mail.yourinternaldomain.com /Microsoft-Server ActiveSync”

Set-ActiveSyncVirtualDirectory -Identity "<CAS2007>\Microsoft-Server-ActiveSync (Default Web Site)" -ExternalUrl $Null  –InternalURL “https://mail.yourinternaldomain.com /Microsoft-Server-ActiveSync”

Comments

  1. AnonymousMay 23, 2017 at 12:12 AM

    that's really helpful.... could you please explain more on how does exchange 2013 proxy activesync request to exchange 2007?

    ReplyDelete
    Replies
    1. Faisal SharifMay 23, 2017 at 2:41 AM

      Exchange 2013 automatically proxy requests from user whose mailbox exist on exchange 2007.
      https://social.technet.microsoft.com/Forums/en-US/5c291f4c-c9d0-4f94-90bc-fc3f4e85ad74/exchange-2013-and-2007-coexistence-and-activesync?forum=exchangesvrmobility

      Delete
    2. Faisal SharifMay 23, 2017 at 2:43 AM

      https://blogs.technet.microsoft.com/exchange/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment/

      Delete

Post a Comment

Popular posts from this blog

Image
Faulting application name: hostcontrollerservice.exe, version: 16.0.775.0, time stamp: 0x5211bea8 Application Error Faulting application name: hostcontrollerservice.exe, version: 16.0.775.0, time stamp: 0x5211bea8 Faulting module name: KERNELBASE.dll, version: 6.2.9200.17637, time stamp: 0x56980227 Exception code: 0xe0434352 Fault offset: 0x000000000004b418 Faulting process id: 0x4878 Faulting application start time: 0x01d2a139409a0421 Faulting application path: D:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\hostcontrollerservice.exe Faulting module path: C:\Windows\system32\KERNELBASE.dll Report Id: 80ceb831-0d2c-11e7-950e-005056be650e Faulting package full name: Faulting package-relative application ID: Solution: Stop the Microsoft Exchange Search service and Microsoft Exchange Search Host Controller (this one probably already is). Edit the file installconfig located in C: \ Program Files \ Microsoft \ Exchange Server \ V15 \ Bin \ Search \ Ceres \ Ins...
Read more

Troubleshooting IMAP Connectivity: Unable to authenticate to IMAP server. IMAP command failed: Login failed.

Image
The first step is to check if the  Courier  IMAP server is accepting connections. Open a terminal window and type: telnet hostname 143 Replace  hostname  with the  IMAP  server's  DNS  name. This expected results would look like this: $ telnet imap.example.com 143 If you get the error "no login failed" then you need to check the following; 1. Make sure IMAP Service is running. 2.  You should make sure that you are using the correct password and that the mail username is in the format: 3. Make sure there is correct name in your exchange server certificate. Please check your certificate settings: Get-ExchangeCertificate | fl I noticed that the InternalConnectionSettings is pointed to Test2.contoso.com but the X509CertificateName is using Remote.domain.com. If there is a certificate with Test2.contoso.com, please change the X509CertificateName to it to have a try: Set-IMAPSettings -Identity Test2\1  -X509CertificateName Test2.contoso.com T...
Read more