Laszlo Denes
asked on
GPO configure profile based on Active Directory Primary SMTP address not working on W10 GPO for Office Outlook 2013
As always firstly thanks to anyone/everyone for their time and kind insights. We are running 2 2016 DC (FFL/DFL is 2012R2 right now) W7 with a GPO set for users to automatically configure their Outlook 2013 for our 2013 Exchange. It works seamlessly for W7 users in the W7 OU/GPO container. However, I applied the same settings for W10b1903 users OU/GPO but it does not do this automatically.
GPO setting: Administrative Templates (Users) > Microsoft Outlook 2013> Account Settings > Exchange > Automatically configure profile based on Active Directory Primary SMTP address.
ENABLED!
Same settings on both and the user sits directly in the OU that the GPO gets applied to. I can see other GPO items working, just not this one. Is there some new trick? I have the latest W10b1903/server 2016 ADMX templates in the central store and the last available (2017) templates for Office 2013. It should work with GPO from what I have read. Any insights greatly appreciated.
GPO setting: Administrative Templates (Users) > Microsoft Outlook 2013> Account Settings > Exchange > Automatically configure profile based on Active Directory Primary SMTP address.
ENABLED!
Same settings on both and the user sits directly in the OU that the GPO gets applied to. I can see other GPO items working, just not this one. Is there some new trick? I have the latest W10b1903/server 2016 ADMX templates in the central store and the last available (2017) templates for Office 2013. It should work with GPO from what I have read. Any insights greatly appreciated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Would rather not do registry, because GPO worked for W7 users with same setting so I am hoping same for W10.
Only difference is admx template for Outlook 2013 on W7 was from 2015 and is from 2017 for W10, but I have not heard or read any issues with the 2017 version.