DKajfes
asked on
Exchange ActiveSync Multiple Exchange Servers on One domain
Hi All,
I have a small issue that i have run into during an upgrade.
Client has SBS 2003 with Exchange 2003. I have installed a new Windows Server 2012 with Exchange 2010.
I have moved 2 test users mailboxes to the new server. All good, and it all works via outlook in the office.
The 2 exchange servers are communicating with each other and passing mail correctly.
I can't however get exchange active sync to work for both servers at the same time.
If i forward port 443 to the new server, then exchange activesync to mobile works for the moved mailboxes but not the old non moved mailboxes. If i leave port 443 pointing to the old server then the users on that server can use active sync.
Is there a way to allow users on either server to have phone access to their respective mailbox.
ie. Can you run activesync on 2 servers and have the old server re-direct traffic to the new server for the moved mailboxes?
As a side note. Outlook web access also doesn't work remotely for users on the new server unless i redirect traffic which of course breaks connectivity to the old server.
Internally OWA works as i can point to either server from within the network.
Any advise would be appreciated.
Thanks
I have a small issue that i have run into during an upgrade.
Client has SBS 2003 with Exchange 2003. I have installed a new Windows Server 2012 with Exchange 2010.
I have moved 2 test users mailboxes to the new server. All good, and it all works via outlook in the office.
The 2 exchange servers are communicating with each other and passing mail correctly.
I can't however get exchange active sync to work for both servers at the same time.
If i forward port 443 to the new server, then exchange activesync to mobile works for the moved mailboxes but not the old non moved mailboxes. If i leave port 443 pointing to the old server then the users on that server can use active sync.
Is there a way to allow users on either server to have phone access to their respective mailbox.
ie. Can you run activesync on 2 servers and have the old server re-direct traffic to the new server for the moved mailboxes?
As a side note. Outlook web access also doesn't work remotely for users on the new server unless i redirect traffic which of course breaks connectivity to the old server.
Internally OWA works as i can point to either server from within the network.
Any advise would be appreciated.
Thanks
Here's a simpler article on how to configure Exchange for your requirements: http://exchangeserverpro.com/exchange-2003-2010-coexistence/
In short, unless you are running ISA2007 or similar, you will need multiple public IPs to differentiate between the two servers for OWA/ActiveSync connections.
In short, unless you are running ISA2007 or similar, you will need multiple public IPs to differentiate between the two servers for OWA/ActiveSync connections.
ASKER
Thanks for the links, however I really only need activesync to work. OWA is not an issue as they have not been shown how to use it yet.
At this stage the public IP points to Exchange 2003 server, not the new 2010.
Should I redirect traffic to 2010 then link back to 2003?
Can I somehow make activesync work with 2010 via 2003?
Thanks
At this stage the public IP points to Exchange 2003 server, not the new 2010.
Should I redirect traffic to 2010 then link back to 2003?
Can I somehow make activesync work with 2010 via 2003?
Thanks
Unfortunately you can't unless your running ISA 2006 or another similar reverse proxy engine.
If you don't have a reverse proxy, you'll need two public IPs (one to point to Exchange 2003 and the other to Exchange 2010).
If you don't have a reverse proxy, you'll need two public IPs (one to point to Exchange 2003 and the other to Exchange 2010).
ActiveSync should proxy to the Exchange 2003 server. It is only OWA that requires separate IP addresses.
This is outlined in the Proxy and Redirection article on TechNet.
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
What can happen, particularly with SBS 2003 servers, is that the configuration of the server isn't correct, usually around authentication settings and the proxy fails.
Running the Exchange 2003 BPA (Download from Microsoft), the Exchange 2010 BPA (in the toolbox) and also the external testing tool at http://exrca.com/ can often pinpoint where the configuration is wrong.
Simon.
This is outlined in the Proxy and Redirection article on TechNet.
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
What can happen, particularly with SBS 2003 servers, is that the configuration of the server isn't correct, usually around authentication settings and the proxy fails.
Running the Exchange 2003 BPA (Download from Microsoft), the Exchange 2010 BPA (in the toolbox) and also the external testing tool at http://exrca.com/ can often pinpoint where the configuration is wrong.
Simon.
ASKER
Thanks Simon, I read the article you linked above, and modified the authentication settings. Still no Joy. BPA doesn't reveal anything wrong.
So I modified authentication settings as per the article, I opened port 443 for active sync to the new server.
I have a SSL certificate for our mail domain, and assigned the services to it.
Users on the new server can now login via mobile devices - its really slow however. But works. takes over 60 seconds to sync, while old server does it in 2 or 3 seconds.
Users on the old server now get an invalid certificate error. and I can't connect.
If I set the port redirection back to the old 2003 server, users on the old server can't login due to certificate error until I go back to the new server and un assign services to the SSL cert.
I can't understand what is going on with the SSL.
The old server was setup years ago with eg "mail.domain1.com.au" its not their primary address anymore - they use "mail.domain2.com.au" now.
The new server was setup with "mail.domain2.com.au" as the primary domain when I setup exchange 2010. I did get a certificate which included both domain1 and domain2 on it.
Exchange 2010 server is on the same local domain as exchange 2003 and the DC. Internally on the network all users are able to use outlook irrespective of which server their mailbox is on.
Could the ssl have something to do with it?
Thanks.
So I modified authentication settings as per the article, I opened port 443 for active sync to the new server.
I have a SSL certificate for our mail domain, and assigned the services to it.
Users on the new server can now login via mobile devices - its really slow however. But works. takes over 60 seconds to sync, while old server does it in 2 or 3 seconds.
Users on the old server now get an invalid certificate error. and I can't connect.
If I set the port redirection back to the old 2003 server, users on the old server can't login due to certificate error until I go back to the new server and un assign services to the SSL cert.
I can't understand what is going on with the SSL.
The old server was setup years ago with eg "mail.domain1.com.au" its not their primary address anymore - they use "mail.domain2.com.au" now.
The new server was setup with "mail.domain2.com.au" as the primary domain when I setup exchange 2010. I did get a certificate which included both domain1 and domain2 on it.
Exchange 2010 server is on the same local domain as exchange 2003 and the DC. Internally on the network all users are able to use outlook irrespective of which server their mailbox is on.
Could the ssl have something to do with it?
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Simon, Was not able to get a solution to this so i have decided to accelerate the migration. Thanks.
Please refer below articles to configure coexists:
http://technet.microsoft.com/en-us/library/dd638130(v=exchg.141).aspx
http://technet.microsoft.com/en-us/library/ee332348(v=exchg.141).aspx