I would not suggest this for any type of production environment. DWORD > Type 'DisableADALatopWAMOverride' and change the value to 1. DWORD > Type 'EnableADAL' and keep the value 0. I’ll stress that this solution is a quick and dirty approach suitable only in a temporary development scenario. ( Back up first ) 2) Created the following registry keys: HKCurrentUser \ SOFTWARE \ Microsoft \ Office \ 16.0 \ Common \ Identity. Tick the POP or IMAP option to use a custom email address and click Next. Choose the Manual setup or additional server types option and select Next. Office 365 has the tools you need to seamlessly create, collaborate, and share from all your devices. On the Welcome to Outlook 2016 window, click Next to proceed with the setup. I can debug my Outlook 2013 addin connected to an Exchange 2013 server in a different domain. Leverage the cloud when you Download Office 365. Now start Outlook and you should get the account setup wizardĪll going well I get a prompt regarding a security certificateĬlick view Certificate… and Install Certificate (then just keep accepting defaults)įinally you get back to the original dialog above and click YesĪll going well you now get a successful connection and can start Outlook connected to your Exchange 2013 server in another domain.Īll is now good to go. Now delete all profiles (through Control Panel>Mail>Profiles) then start Outlook.Įdit your hosts file (you need to have Admin rights to save changes) and add an entry for the autodiscover to work Here’s the steps to perform on the Outlook client machine: The only way I can get it to work is to go through the Exchange autodiscover process, and to make this happen I add an entry for into the hosts file on the development machine and point it to the IP address of the Exchange 2013 server. Outlook just keeps telling me it cannot establish connectivity to the Exchange server or the user account cannot be found (this is through both starting Outlook without a profile or Control Panel>Mail to create a new profile). Try as I might I just cannot manually setup a connection to the Exchange 2013 server. In my case I’ve already established TCP connectivity between and (i.e. Since I’m just doing some isolated dev I don’t want to be creating entries in our corporate DNS or AD. I need to be able to connect my Outlook 2013 client on my development machine (in ) to the Exchange 2013 server in a different environment (). I’ve setup an isolated domain with it’s own Active Directory server and Exchange server (let’s call it ). My development machine is in our corporate domain () and I’m doing development against Exchange 2013. Having gone through the pain twice now (you’d think I’d learn the first time) I’m going to punch out a quick blog post for future.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |