It seems like something it trying to connect out to the Internet through our proxy servers because when I check Outlook.exe with ProcessExplorer I can see an open connection to the proxy but I cannot seem to get it to stop doing that even with the "ExcludeExplicitO365Endpoint"
Source ServiceEndpoint Scenario Result LatencyĢ Autodiscover: Outlook Provider Success 57Ģ Exchange Web Services Success 78Ģ Availability Service Success 140Ģ Offline Address Book Success 45 If I run Test-OutlookWebServices everything checks out good. By default, this attribute specifies the Active Directory site to which the Client Access server belongs. The keywords attribute specifies the Active Directory sites to which this SCP record is associated. I have a case open with Microsoft Support but haven't made any progress yet. It is this url which internal Outlook client uses to connect to the mailbox and other Exchange features published using autodiscover. HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover The attempt to log on to Microsoft Exchange has failed. Instead I get: Cannot start Microsoft Outlook. We have not migrated anyone or modified any of our previouslyĪutoDiscovery does work because I can delete my mail profile and it will automatically populate all the values for my mailbox but it will not allow me to continue and open Outlook to display my e-mail. I never though just installing new Exchange servers could potentially break a working Exchange 2010 environment. I have tested OWA access from each server and that works without issue. I have tried to disable a lot of the AutoDiscover options as listed here but nothing makes any difference. Not everyone seems to be having this problem. The connect is to our proxy server not any of the Exchange servers. In the Resource Monitor when you choose OUTLOOK.EXE and look under the "Network" connections. Outlook chooses to immediately try to access the internet through our proxy server. We get a login prompt that does not accept any credentials to get past. Several of our users including myself now cannot open Outlook 2016. If someone knows why this is better, please leave a comment and enlighten me.I'm having a very frustrating problem after we installed some new Exchange 2016 servers to migrate from Exchange 2010. Not every Domain is run like it would be in an enclosed lab. And before anyone says “Why don’t you just use Autodiscover”, there are times in the real world when you can’t use it.
2013 requires Administrator Support for each user that needs a manual setup since users can’t run the Exchange Cmdlet needed to get the GUID.
I honestly don’t see how this is an improvement over Exchange 2010 where all users could be given a simple set of instructions and could setup their own mailbox if autodiscover didn’t work for them. That should get the client connected to the Exchange 2013 mailbox. Click OK to apply the changes and NEXT to Finish the setup. In the Proxy Settings Window, enter the mailserver CAS host’s FQDN in the Proxy server field.ĩ. Select the Connection Tab, check the “Connect to Microsoft Exchange using HTTP” and click the “Exchange Proxy Settings” Button (See image for reference)Ĩ. In the Username Field enter the user email address (i.e. In the Exchange Server Field enter the using the GUID returned from the Get-Mailbox Cmdlet and the mailbox domain (i.e. From the E-Mail service window, select Microsoft Exchange and Click Next.ĥ. In the Account Setup section, Check the option to “Manually configure server settings” and click Next.Ĥ. Note that the labels vary slightly from outlook 2007 to 2010 to 2013, but the steps are essentially the same.Ģ.
You can get to this windows through Outlook from TOOLS -> ACCOUNT SETTINGS or from the CONTROL PANEL -> MAIL -> EMAIL ACCOUNTS. We need to create a new account either by running Outlook for the 1st time or in the “Account Settings” window. You should get something like the following: Name : Clark KentĮxchangeGuid : 39f83854-18b3-4bb2-baf1-9cc03c721c6b Use the Exchange Powershell get-mailbox cmdlet to get the information. So the 1st thing we need is the GUID for the account mailbox. That basically means that end users now need a specific value in the server field that is provided by an Exchange administrator. In Exchange 2013, the Exchange server name now uses the format of where GUID is the Mailbox guid and is unique to each user. In Exchange 2010 and earlier, one could just manually configure the Exchange account with a server name of the Exchange server i.e. However, the employee was using a laptop that was not a domain member and could not use autodiscover to automate Outlook setup. I had the need to setup an employee’s laptop with access to an Exchange 2013 mailbox. I have had this issue come up a few times.