This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 23%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
Hello!
I am working on a scenario for restoring infrastructure from backups in case of failures.
I restored my Exchange 2013 servers and domain controllers from backup images to an isolated test network and check their viability.
The connection to the mailbox via the Web and to the ECP via the Web is working successfully.
Sending and receiving mail via the Outlook Web App between users works
But when connecting from Microsoft Outlook 2013 on Windows 10, I get an error like in the attached pictures:
"The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action"
I can't figure out where to start solving the problem.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
Hi @Pavel
Please run a Test E-mail Autoconfiguration via Outlook (you may need to configure another mailbox for example outlook.com or create a profile without a mailbox).
And check the results under the Log tag. (Don't forget to hide your personal information in the screenshot)
Hello!
Hi,
Thanks for the update!
Did it work fine on Windows 10+Outlook 2013 before the restore?
And have you enabled TLS 1.2 on the Exchange servers?
Hi!
Did it work fine on Windows 10+Outlook 2013 before the restore?
Yes, in the original network everything worked and is working now without problems.
The difference between the restored network and the original one is that in the restored network I changed the addresses of domain controllers and some Exchange servers,
because in the original network, the servers are divided into two subnets, and in the restored network, I combined them into one subnet.
But I corrected everything correctly in DNS, all names are resolved correctly and mail works through WebApp.
And have you enabled TLS 1.2 on the Exchange servers?
I didn't set the TLS1.2 settings on purpose. The restored network has the same settings as the original one.
But now a thought came to me!
I did not restore all the databases, since they are large. I restored only bases with user mailboxes.
And bases where there are system mailboxes (Arbitration and others) did not recover.
Could this be the cause of the error?
Hi,
Thanks for the information.
While to me I suppose it may not be the cause in this case, although it may cause other problems.
I noticed a strange point here is that Autodiscover is supposed to succeed in the first step(SCP).
If you access this url https://EX01.domain.com/autodiscover/autodiscover/xml via a browser, would you be prompted for credentials?
If yes, after input of the credentials, would it return error 600?
Please also post the result of Test E-mail Autoconfiguration under the Results tag.
(Also don't forget to hide your personal information)
Hi @Pavel
I am writing here to confirm with you how thing going now?
Did the issue get resolved?
Hello!
I noticed a strange point here is that Autodiscover is supposed to succeed in the first step(SCP).
The first step Autodiscover error - is to try to connect through the EX01 server.
This is the very first EXchange 2007 server in our organization.
There are currently no mailboxes on this server.
The rest of the servers are Exchange 2013 versions.
I planned to remove EX01 from our infrastructure, but did not find information on how to do it correctly so as not to
our mail infrastructure was disrupted.
I have now corrected the AutoDiscoverServiceInternalUri parameter to EX01 and now Atodiscover runs in one step.
Attached are screenshots of new Outlook Test E-mail AutoConfiguration.
Perhaps I found the cause of my problem, but I do not know how to fix it.
Access to the Offline Address Book does not work.
Test-OutlookWebServices -Identity testuser01 -MailboxCredential (Get-Credential) | fl
link https://server/OAB/65...79/oab.xml not work (page not found):
but file oab.xml is present on folder *C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB\65b..79*
Hi,
To me this issue may also be unrelated.
Have you recovered the database with the system mailboxes?
Back to the original Outlook connection issue, I suppose we may need to use some tool like fiddler to check the connecting process.
Hello!
Yes, all system boxes have been successfully restored.
I found information on the Internet that OAB corruption may be one of the reasons for the first Outlook connection error when creating a user profile in Windows.
Also recommend to recreate OAB.
But I can't understand why my OAB is not available, because all the system boxes are in place and the oab.xml file itself is in place.
Maybe when restoring the server from the backup image, the web application settings got lost?
I would like to restore OAB availability so that Test-OutlookWebServices will work successfully.
Sorry I didn't mention it in my former replies:
How did you restore the server? Did you use windows server backup?
I would also recommend creating a new OAB and see if it would resolve this OAB issue.
You may use the cmdlets in these links:
Create an offline address book in Exchange 2013
Change the default offline address book in Exchange 2013
New-OfflineAddressBook -Name "newOAB" -AddressLists "\Default Global Address List" -VirtualDirectories $Null -GlobalWebDistributionEnabled $True
Set-OfflineAddressBook -Identity "newOAB" -IsDefault $true
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 85%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Hello Team i want to add this point when i researched. On exch 2013 give users the permissions on discovery management. I think htis is the most logical step so that the users when you set up their profile in outlook, will discover their address and other information. i also gave view only orgnisation management as in 2nd image below but i dont think this is relevant. I did both steps just to check if the eror is disappeared..so the error was not there and the profile was setup.