


Moving the RDS server to a different OU so the RDS GPO's don't apply doesn't help.Testing auto discovery on a reg-exported profile connected Outlook comes back clean.If you export the current user /software/microsoft/office/16/outlook/profile reg key from a working computer then Outlook loads and connects no problem.Info is discovered, auto discovery works, exchange won't authenticate. On prem exchange 2016, latest and greatest. After the updates this month the any new or existing profiles in Outlook won't connect when on an RDS server.
