Exchange 2016 Post Installation Question
After we configure the first Exchange 2016 server to take over the CAS reposibilities and Internet facing with Active-Sync and Webmail. Does the users' mailbox have to be on Exchange 2016 to take advantage of the Exchange 2016 Active-Sync?
Ogandos
From which one of the exchange versions are you migrating from? Definitively the new features included in Exch 2013 and Exch 2016 are associated to the service provide when you are hosting your mailbox in one of these two newer versions, because in that way your access can be done through the 2016 CAS. If you have mailboxes in Exchange 2010 the 2016 CAS servers redirect or proxy the connection with an Exch 2010, where you will have limited functionality.
No. You won't get any of the 2016 specific features or advancements when a mailbox is on a 2013 server.
I think it's also important to point out that if you're using Exchange 2016 just for client access, your Exchange architecture is incorrect. There is no longer any role separation starting with Exchange 2016, and if your environment is designed in a way that has Exchange 2016 directly connected to the Internet (if the server itself is assigned a public IP address)...stop it. Don't do that. It's a seriously bad idea. CAS is not a "Front End" server of the type that Exchange 2003 had, which was designed to be directly connected to the Internet (Front End in 2003 was not usually a domain member, so it was safe to put in a DMZ). The CAS role must be on a domain member, and having a domain member with a Public IP assigned to its NIC is a terrible security practice and a great way to get severely hacked. If you want to protect the Exchange environment's Internet facing servers (which should have private IPs), use a Web Application Proxy server or Load balancer to act as an intermediary between the internet and the server itself. It's usually okay to allow port 443 to go through the firewall to an Exchange server using NAT, but having it straight on the Internet is not recommended.
If your 2016 server is straight on the Internet, pull it into the LAN and use NAT to get port 443 to the Internet to it. Set up a Web Application Proxy server that is connected to the Internet if you want (That role does not require domain membership) and have it proxy connections to the 2016 server. From there, migrate your mailboxes from 2013 to 2016.
I think it's also important to point out that if you're using Exchange 2016 just for client access, your Exchange architecture is incorrect. There is no longer any role separation starting with Exchange 2016, and if your environment is designed in a way that has Exchange 2016 directly connected to the Internet (if the server itself is assigned a public IP address)...stop it. Don't do that. It's a seriously bad idea. CAS is not a "Front End" server of the type that Exchange 2003 had, which was designed to be directly connected to the Internet (Front End in 2003 was not usually a domain member, so it was safe to put in a DMZ). The CAS role must be on a domain member, and having a domain member with a Public IP assigned to its NIC is a terrible security practice and a great way to get severely hacked. If you want to protect the Exchange environment's Internet facing servers (which should have private IPs), use a Web Application Proxy server or Load balancer to act as an intermediary between the internet and the server itself. It's usually okay to allow port 443 to go through the firewall to an Exchange server using NAT, but having it straight on the Internet is not recommended.
If your 2016 server is straight on the Internet, pull it into the LAN and use NAT to get port 443 to the Internet to it. Set up a Web Application Proxy server that is connected to the Internet if you want (That role does not require domain membership) and have it proxy connections to the 2016 server. From there, migrate your mailboxes from 2013 to 2016.
Hello Adam, isn't it that you mean about the new ActiveSync features that are in Office365? Is it already included in Exchange 2016 OnPremises? (Maybe these features are at the moment just in the updated Exchange servers that Microsoft uses for Office365).
ASKER
We are in a Exchange 2010 SP3 Organization and we will be Co-Existing with Exchange 2016. I just wanted to know if a users' mailbox has to be migrated to Exchange 2016 to take advantage of the Active-Sync Features in Exchange 2016?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.