You will note that the ExchangeGUID does not show up in the ADDS cmdlet: Get-Mailbox Administrator | Select Name, *GUID* You will note that the information specified in the Exchange server name is the ExchangeGUID of the mailbox. We can talk more about that with MAPI/HTTP. The intent was to minimise the occurrences of “Your administrator has made a change that requires you to restart Outlook”. This was a deliberate design change in Exchange 2013 to provide a single consistent identity that Outlook could store. Is this something to be worried about? The answer is no. Note that the Exchange server field does not state the name of any of the Exchange servers. We issued the LDAP query to AD, did the Autodiscover SCP query, and start to process the Autodiscover response.Ĭlicking OK, shows the below dialogue box.Ĭouple of things to mention about the content of the above window. For details on Autodiscover please see this post.Īll normal so far. As expected we hit up AD to get the SMTP address and then query AD for the Autodiscover SCP endpoints. Trying to create a new Outlook 2013 profile with pre Outlook 2013 SP1 and then Outlook 2013 SP1 both resulted in the same issue.įiring up Outlook initiated the Auto Account setup. Let’s look at what was going on and then remediate manually and how to automate the fix. Why would it want a default gateway when all machines are on a single subnet, the network is a private Hyper-V switch and all machines resolve names perfectly…… Since this entire lab exists on a single flat subnet ( 10.0.0.0/8 ) I foolishly, ignored the default gateway bit of the error message and focussed on client connectivity. Your Network Adapter does not have a default gateway”. The connection to Microsoft Exchange is unavailable. When creating a new profile the error received was “ The action cannot be completed. The symptom was that Outlook would not connect using an existing profile, and was unable to create a net new profile. Legacy IIS permissions when coexisting with Exchange 2013 are covered here for example. Well it turns out that they were, and this was just a client side issue. A witch hunt then ensued to ensure that all of my Outlook Anywhere, Autodiscover and authentication settings were correct. Outlook 2013 refused to connect to Exchange 2013. When doing some recent customer work for Exchange 2013, I ran into an annoying issue in one of my labs.
0 kommentar(er)
