I went through this search and I pass in front of it several times until I watch your video. Definitive was the solution. A few weeks later I run into the Exchange 2016- Server and double click and guess what? in The GUI the last option was the Outlook Anywhere configuration😯😑
Just completed the journey. I now have internal and external urls all pointing at the Fqdn for my organisation Internally that fqdn has a dns entry pointing at the-internal ip for mailbox/cas server Public dns points at our public ip and i port forward 443 to our internal ip for the mailbox/cas server Hint-: Left control and right click on outlook system tray icon and select connection status to identify the published urls your outlook is connecting to and checking ssl certs for. Read the whole url! Mine was /mapi prefixed with the internal domain name, so i then knew to change the relevant service in aj’s Transcript output Works like a charm now thanks for the video Message if you wish. What a mess ms made
I have been at this for over a week now, when I saw this I felt really hopeful on fixing it. However, for me it made absolutrely no difference. Unbelievable. I am clost uninstalling the entire server and using something else!
I tried your suggestion and completed AJ Tek's other recommendations (minus the backup procedure). Still getting error. I scrolled down to the bottom of page to "OK, I Got All of That. What About Troubleshooting?" and I added the 8 Registry tweaks and my certificate issues resolved!! I've been chasing this for over a year. I can check off the box now.
Tnx for the info.but in my case idid auto discover option for fetching internal exchange outlook access on azure ad joined PC's and start fetching email's as well.But the problem is, still this pop is coming.
Something from this video or the guide by AJ Tek fixed this for me but it did not start to work until I deleted my outlook mail profile in control panel and created a new one to start over. Hope this helps someone.
I went through this search and I pass in front of it several times until I watch your video. Definitive was the solution. A few weeks later I run into the Exchange 2016- Server and double click and guess what? in The GUI the last option was the Outlook Anywhere configuration😯😑
Just completed the journey.
I now have internal and external urls all pointing at the Fqdn for my organisation
Internally that fqdn has a dns entry pointing at the-internal ip for mailbox/cas server
Public dns points at our public ip and i port forward 443 to our internal ip for the mailbox/cas server
Hint-: Left control and right click on outlook system tray icon and select connection status to identify the published urls your outlook is connecting to and checking ssl certs for. Read the whole url! Mine was /mapi prefixed with the internal domain name, so i then knew to change the relevant service in aj’s Transcript output
Works like a charm now thanks for the video
Message if you wish. What a mess ms made
I have been at this for over a week now, when I saw this I felt really hopeful on fixing it. However, for me it made absolutrely no difference. Unbelievable. I am clost uninstalling the entire server and using something else!
same as that. great video, exactly my condition but still presenting internal domain! to externals
This worked for me.. Exact same situation I missed it because the default command I found didn't list Internal and External Url. Thanks so much
good info. do we need to restart the IIS server after the change?
this got me on the right track, I needed this and to make the autodiscoverurl null since we are in a hybrid config. thanks
Can you elaborate a bit more on this?
I tried your suggestion and completed AJ Tek's other recommendations (minus the backup procedure). Still getting error. I scrolled down to the bottom of page to "OK, I Got All of That. What About Troubleshooting?" and I added the 8 Registry tweaks and my certificate issues resolved!! I've been chasing this for over a year. I can check off the box now.
what are the 8 registry tweaks you added
Tnx for the info.but in my case idid auto discover option for fetching internal exchange outlook access on azure ad joined PC's and start fetching email's as well.But the problem is, still this pop is coming.
Is it safe to assume that you run the commands from Powershell?
DUUUUUDE! i was on this for like 3days YOU ARE A CHAMP, THANK YOU let me go have a beer. DONE XD
If my outlook 2016 is connecting to exchange server 2010, can I try this solution?
If you can,Please help me by recommending and option for the below issue to.
I owe you a beer for this. Thanks!
Something from this video or the guide by AJ Tek fixed this for me but it did not start to work until I deleted my outlook mail profile in control panel and created a new one to start over. Hope this helps someone.
Thank you so much