![Connecting outlook 2016 to exchange 2013](https://kumkoniak.com/53.jpg)
![connecting outlook 2016 to exchange 2013 connecting outlook 2016 to exchange 2013](https://www.ionos.com/help/fileadmin/images/Email/Microsoft_Exchange_2013/2374/EN/2374_EN_setup_Exchange_2013_Outlook_2016_2019_02.png)
Also, our buddy John Doe would have a AD UPN (this was automatically populated on user setup) An example would be “John Doe”, with the username of “JohnD”, and the e-mail address of “ ”. Now if you’re like me, another thing I always configured, was user accounts that didn’t match e-mail addresses.
![connecting outlook 2016 to exchange 2013 connecting outlook 2016 to exchange 2013](https://i.ytimg.com/vi/pYVax8tMiwo/maxresdefault.jpg)
guys, except for a few configuration considerations when setting up Outlook clients, DNS, etc… This has never really posed any problems for us I.T. This used to be considered best practice, and most of us even configured. I wanted to open a discussion on a big issue I had a couple years ago in one of my first migrations from SBS 2008, to Windows Server 2012 R2 with the Essentials Experience role installed, with Exchange Server 2013.Īs most of you know, SBS comes packaged to push “.local” domains on initial domain configuration. However, some of these old environments are starting to catch up with us. The connection to MicrosoftĮxchange is unavailable.There’s quite a few of us that started off deploying Small Business Server (SBS2008, SBS2011) environments back in the day, loving the handy all-in-one package taking care of everything from Active Directory and Exchange, to disaster recovery and business continuity. Problem is when add new account in Outlook 2016, it hit an error when Logging on to the mail server with error message "The action cannot be completed.
![connecting outlook 2016 to exchange 2013 connecting outlook 2016 to exchange 2013](https://wiki.zimbra.com/images/9/98/Zimbra-eas-wiki-004.png)
Able to resolve the hostname for the AD, Exchange 2016, Win10, .Īlready added CNAME and MX for
![connecting outlook 2016 to exchange 2013 connecting outlook 2016 to exchange 2013](https://i.stack.imgur.com/V0ItD.png)
opening the web shows a website with ErrorCode 600 and Invalid Request which is correct. Testing is done in private network without internet connection.Ĭheck autodiscover seems to be working. Setup as follows:Įxchange Server 2016 - installed on Windows 2012 R2Īlready configured internal & external url to points to single url: I'm testing Exchange 2016 but can't get Outlook 2016 to connect to it.
![Connecting outlook 2016 to exchange 2013](https://kumkoniak.com/53.jpg)