This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(131.20000000000002, 16%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGH%3C/text%3E%3C/svg%3E)
Greetings all. I'm wrapping up a migration from on-prem Exchange 2010 to on-prem Exchange 2016. Specs are below: Exchange 2016 CU 18 Outlook 2016 Pro Plus 16.0.5134.100 32-bit Outlook 2019 Pro Plus 1808 10372.20060 64-bit We tried and failed to move public folders using the migration scripts. In terms of Outlook client functionality everything appeared fine up to that point. We then deleted the existing public folder deployment from 2010 and created a new empty structure on Exch 2016. The client then started importing everything in from PST which was also working fine. Weirdly, we observed that as soon as the new PFs came live on 2016 all of the Outlook 2019 clients started prompting for a password upon connection. The 2016 Outlook clients are fine. OWA is fine. When the Outlook 2019 user connects and is prompted all they have to do is click on the "Need Password: prompt at the bottom at which point the dialog goes away and they can work fine. Then at some point - 10m, 1 hr, 2hrs? - the prompt will reappear. We have tried everything from blowing away the profile, logging in on a new machine with a new profile, checking the RCP stats - everything looks normal and shows the Outlook 2019 users connected to the new single Exchange 2016 server. Any help would be greatly appreciated. Thanks.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
Hi,@Gregg Hamby
Agree with Andy, it may be caused by the new feature in Outlook 2016 version 16.0.6741.2017 or later versions, which tries to connect to O365.
And since Outlook 2016 16.0.5134.100 is a legacy version, it isn't affected.
To resolve the problem, you may follow these steps:
Could be the 2019 clients are actually trying to contact Office 365:
You can fix with a registry fix;
https://medium.com/jj365/outlook-issue-with-direct-connect-to-office365-352dd29de65
Thanks guys. This indeed turned out to be the issue. The customer thought they had tried this earlier but must have applied it incorrectly.
I have to vent a little - this customer has been running 2019 in their environment for a year. The problem only manifested itself upon installation of a 2016 Exchange server. While 2010 was the primary server they never observed this.
Kael - you're with MS? So is this the official answer? "Just go perform a reg hack to 1000 systems on your campus and we're all good?" This customer is on prem but is dealing with this issue because - apparently - MS will see you in the cloud or you can die trying to remain on prem.
I thank you both for your answers.
Hi,
While 2010 was the primary server they never observed this.
Since this issue is caused by the new feature of Outlook, and there are some cases in the similar situation with Exchange server 2010, I am not sure why it works fine before.
"Just go perform a reg hack to 1000 systems on your campus and we're all good?"
Sorry for the inconvenience.
While since it is caused by the feature of Outlook, there is no way to resolve the issue on the server side.
As a workaround,you may need to create a GPO to modify the registry on the user devices.