Exchange ActiveSync issue on Windows Server 2016 with iOS11

From Hostek.com Wiki
Revision as of 15:31, 14 September 2017 by Chrisd (Talk | contribs) (Created page with "=Exchange ActiveSync issue on Windows Server 2016 with iOS11= Exchange ActiveSync (EAS) users will not be able to REPLY to, or FORWARD, messages with attachments from the def...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Exchange ActiveSync issue on Windows Server 2016 with iOS11

Exchange ActiveSync (EAS) users will not be able to REPLY to, or FORWARD, messages with attachments from the default Mail app on iOS 11. This is NOT a SmarterMail issue but an iOS 11 and Windows Server 2016 compatibility issue that affects ALL versions of SmarterMail as well as other mail servers and services, including Microsoft Exchange Server customers using Windows Server 2016.

The cause of the issue is related to the implementation of HTTP/2 in either Windows Server 2016 or in iOS 11. HTTP/2 is a major revision of the HTTP network protocol used for communication across the internet. Windows Server 2016 and Windows 10 both implement, and default to, HTTP/2 versus the more legacy HTTP/1.1. With iOS 11, Apple is now using HTTP/2 because Windows Server 2016 supports it.

If your mail server is running and older version of Windows Server, you will not see this problem as iOS 11 will continue to use HTTP/1.1.

Workaround

As a workaround, system administrators can modify the Windows Server 2016 registry to “act as” previous versions of Windows Server, essentially telling iOS 11 to use the HTTP/1.1 protocol.

The following keys would need to be modified AND the server rebooted:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters

EnableHTTP2Tls REG_DWORD 0 — the default is 1

EnableHttp2Cleartext REG_DWORD 0 — again, the default is 1

Retrieved from "https://wiki.hostek.com/index.php?title=Exchange_ActiveSync_issue_on_Windows_Server_2016_with_iOS11&oldid=3728"