techno106
asked on
Terminal Server issue with outlook connecting to exchange online
I have setup up a server 2012 R2 for terminal services for 3 users, i have installed all licenses required.
We have installed Office 2016 Standard Volume Licensed Edition
The issue i am having is connecting outlook to exchange online and it hangs and doesnt connect up to the server.
I can log on from the server to the webmail with no issues.
We have installed Office 2016 Standard Volume Licensed Edition
The issue i am having is connecting outlook to exchange online and it hangs and doesnt connect up to the server.
I can log on from the server to the webmail with no issues.
Vasil Michev (MVP)
You are not giving us much to work with... Does it hand when configuring the profile or when launching Outlook (after the profile is already configured)? Are you using Online or Cached mode? Have you confirmed that all relevant URLs and IPs are allowed in your env?
ASKER
Yes sorry, when i am opening outlook and setting up the account and click next to set the profile up it just sits there and fails to connect to exchange. It sits saying connecting to exchange but never does.
The profile just wont configure.
I have also tried to set this up manually with the settings required and it does the exact same thing.
The profile just wont configure.
I have also tried to set this up manually with the settings required and it does the exact same thing.
Try querying the Autodiscover service from the local machine by holding the CTRL key and right-clicking on Outlook's icon in the tray. Enter the username and password, clear the two GuessSmart checkboxes and run the test, then monitor the status on the Log tab. If it fails, post the sanitized results here.
The hang is in relation to your deployment setup.
By default, Outlook 2016 will use cached exchange mode. However, as your deployment is on RDS, there might be not enough disk space or I/O’s are not sufficient. Besides, your user should have a large exchange mailbox in exchange online, the cache will start to grow in size when you setup the Outlook profile.
When the cache or the I/O reaches its limit of your RDS, Outlook will just hang up.
In order to fix the above, you can use Office Customization Tool or in Group Policy to change the default mode to online mode. The drawback is slow performance.
Or you can seup a network share within RDS to store the ost file and install Windows search on the server which provide the network share and point the ost file to that network share. You can still use cached exchange mode.
https://technet.microsoft.com/en-us/library/jj683103.aspx
By default, Outlook 2016 will use cached exchange mode. However, as your deployment is on RDS, there might be not enough disk space or I/O’s are not sufficient. Besides, your user should have a large exchange mailbox in exchange online, the cache will start to grow in size when you setup the Outlook profile.
When the cache or the I/O reaches its limit of your RDS, Outlook will just hang up.
In order to fix the above, you can use Office Customization Tool or in Group Policy to change the default mode to online mode. The drawback is slow performance.
Or you can seup a network share within RDS to store the ost file and install Windows search on the server which provide the network share and point the ost file to that network share. You can still use cached exchange mode.
https://technet.microsoft.com/en-us/library/jj683103.aspx
ASKER
Please see error for autodiscover
autodiscover-issue.PNG
autodiscover-issue.PNG
It's normal for AutoDiscover to fail on some methods, the important pats it that it needs to success on the HTTP redirect one (the CNAME). You havent included that in your screenshot.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The tool works to get your outlook profile up and running.