Exchange 2016 Edge role issue with Windows Server 2016
Me and my team were on the Enterprise Deployment of Exchange server. We were deploying Exchange 2016 CU8, as CU7 had some issues and fixes were provided on CU8. We had deployed Exchange on Windows server 2016 (1607) for all the Farm environment. Configuration for the Mailboxes roles were good and had a complete DAG environment. But unfortunately, we faced Exchange 2016 Edge role issue with Windows Server 2016. On doing further research I found the blog which has not recommended to install Exchange Edge role on Server 2016.
After the installation of Exchange 2016 Edge on the Windows Server 2016. we got the anonymous issue of getting Exchange Transport Service stopped. Even after everything was good. I was frequently getting my transport service stopped. Which later on found that this was the issue of collision between the content filters shipped by Exchange and Windows which have conflicting configuration information in the Windows registry. Exchange Transport Service will crash on startup if the content filter agent is enabled on the Exchange Server. The Edge role enables the filter by default and does not have a supported method to permanently remove the content filter agent
So finally, if you are running the Edge role on Windows Server 2016:
Delay deploying KB4013429 to your Edge role or uninstall the update if required to restore service
Deploy the Edge role on Windows Server 2012 or Windows Servers 2012R2 (Preferred)
Support services is available for customers who may need further assistance.
That is not true ony for Edge , we are running EXchange 2016 mailbox role on server 2016 cummalative update march 2018 and since we upraded to cu 8 .net 4.7.1 this service started stoping for Microsoft transport delivery service , so in test environment we built same config and upgraded to cu9 till the problem was solved.