SupermanTB
asked on
Outlook (2016) not showing up in Indexing Options for Win 2008 R2 Terminal Server
I've got a brand new Windows Server 2008 R2 terminal server with Office 2016 installed. My users are having issues using the Windows Search functionality in Outlook. Ironically when searching the Inbox, the search results return very quickly. However, when searching say contacts, the search takes an extremely large amount of time.
When I look at the Indexing Options in Outlook, Microsoft Outlook is not present. The number of items index is also very small, only around ~2,000 for a users with a 10GB mailbox (Office365 Exchange).
The Windows Search service has been installed on this server.
Any ideas on how to troubleshoot?
Thanks very much
When I look at the Indexing Options in Outlook, Microsoft Outlook is not present. The number of items index is also very small, only around ~2,000 for a users with a 10GB mailbox (Office365 Exchange).
The Windows Search service has been installed on this server.
Any ideas on how to troubleshoot?
Thanks very much
Adam Brown
Install the Desktop Experience Feature on the server to see if it shows up after doing so. If not, you probably can't index outlook on windows server (Indexing isn't fully meant for Windows Server).
It takes several hours before the indexing can be finished.
Do you find the Indexing Options in Control Panel?
Do you find the Indexing Options in Control Panel?
ASKER
I've already installed the Desktop Experience. That did not help. I have other 2008 R2 terminal servers that have Outlook indexed, so I don't think it's that the server OS can't index.
I do see the Indexing Options in Control Panel. The server was installed several days ago. It has had time to index. Also, the number of indexed items is not increasing
I do see the Indexing Options in Control Panel. The server was installed several days ago. It has had time to index. Also, the number of indexed items is not increasing
Which version of Outlook 2016?
Volume licence or Click to run installer?
32 bit or 64 bit?
Volume licence or Click to run installer?
32 bit or 64 bit?
ASKER
Outlook 2016 32-bit, volume license
RDS > Office 365 > Outlook 2016 can only be run in online mode if you want to do instant search but the performance is poor.
Can you describe how you setup your RDS?
My wild guess that you are using cached mode with OST file.
The info below might give you some insights.
"I've been through the mill with effin O365 and RDS.
Simply put the only mode supported by Microsoft for O365 Exchange online on RD servers is On-line Mode (non-cached). This makes Outlook slow and laggy and a source of constant frustration to users.
I had attempted to implement cached mode by using a dedicated File server to host redirected OSTs for cached mode, it works, is quick, but there are big issues, and of course is not supported by Microsoft.
Apart from the Massive space requirements for the OSTs in cached mode, searching becomes a big big problem. In a normal Exchange environment, and on 0365 online mode, all searching is performed against the Exchange Server, it is quick and it works well.
In cached mode, the terminal/remote desktop server itself must index every OST and use this to run searches against. It takes days to populate with many users, cripples the System, and gets completely messed up if using a RDS farm (or session collection I think they call them now). In the end the completed search index database can take up around 50% of the size of the OSTs.
My happy medium (so far) is using a 1 or 3 month cached mode (absolutely not supported for O365 at all by Microsoft, even on normal desktops) Which allows for a smaller footprint and indexing performance hit, improving the laggyness of Outlook, while still giving access to larger searches on the O365 servers if need be.
In short O365 Exchange online on RD servers is a disaster for end-users and Admins alike. We are seriously considering migrating back to On-site exchange."
Source: http://forums.overclockers.co.uk/showthread.php?p=28782737
Can you describe how you setup your RDS?
My wild guess that you are using cached mode with OST file.
The info below might give you some insights.
"I've been through the mill with effin O365 and RDS.
Simply put the only mode supported by Microsoft for O365 Exchange online on RD servers is On-line Mode (non-cached). This makes Outlook slow and laggy and a source of constant frustration to users.
I had attempted to implement cached mode by using a dedicated File server to host redirected OSTs for cached mode, it works, is quick, but there are big issues, and of course is not supported by Microsoft.
Apart from the Massive space requirements for the OSTs in cached mode, searching becomes a big big problem. In a normal Exchange environment, and on 0365 online mode, all searching is performed against the Exchange Server, it is quick and it works well.
In cached mode, the terminal/remote desktop server itself must index every OST and use this to run searches against. It takes days to populate with many users, cripples the System, and gets completely messed up if using a RDS farm (or session collection I think they call them now). In the end the completed search index database can take up around 50% of the size of the OSTs.
My happy medium (so far) is using a 1 or 3 month cached mode (absolutely not supported for O365 at all by Microsoft, even on normal desktops) Which allows for a smaller footprint and indexing performance hit, improving the laggyness of Outlook, while still giving access to larger searches on the O365 servers if need be.
In short O365 Exchange online on RD servers is a disaster for end-users and Admins alike. We are seriously considering migrating back to On-site exchange."
Source: http://forums.overclockers.co.uk/showthread.php?p=28782737
ASKER
Very interesting. Thanks so much for the detailed response. I definitely have the profiles setup in cached mode.
The old RDS server we migrated from was also Server 2008 R2, but used Office 2010 volume license. Still using Office365 for the email. It is in cached mode and doesn't have a problem with the indexing at all.
I saw your response was taken from that forum you referenced. It sounds like this person has experience with the issue, but there don't seem to be any other users on that forum confirming what the poster said. It's hard for me to put too much stock in that without a little more confirmation or perhaps some documentation from Microsoft.
I did notice this forum, which perfectly describes my issue. It seems to work fine in Outlook Safe Mode. I've already installed the Windows Search service though. I'm currently in the process of uninstalling/reinstalling the Windows Search service along with repairing Office
http://serverfault.com/questions/726397/windows-search-in-outlook-2013-on-remote-desktop-service-windows-server-2012r2
The old RDS server we migrated from was also Server 2008 R2, but used Office 2010 volume license. Still using Office365 for the email. It is in cached mode and doesn't have a problem with the indexing at all.
I saw your response was taken from that forum you referenced. It sounds like this person has experience with the issue, but there don't seem to be any other users on that forum confirming what the poster said. It's hard for me to put too much stock in that without a little more confirmation or perhaps some documentation from Microsoft.
I did notice this forum, which perfectly describes my issue. It seems to work fine in Outlook Safe Mode. I've already installed the Windows Search service though. I'm currently in the process of uninstalling/reinstalling the Windows Search service along with repairing Office
http://serverfault.com/questions/726397/windows-search-in-outlook-2013-on-remote-desktop-service-windows-server-2012r2
ASKER
Any further comments on this issue? I just can't seem to get the indexing to work for Outlook. The users' Outlook is showing up in the indexed locations, but the number of indexed files is still very small. Several of these users have pretty large mailboxes. Searching, specifically for contacts isn't working correctly.
This is an unsupported configuration of using cached mode in MS Outlook in RDS for a very large mailbox as it will end up with multiple large OST files in RDS farm from multiple RDS sessions. Indexing will never finish as reindex will start when user logins to a RDS session.
Why safe mode will work?
In safe mode, only one OST file will be locked for use and indexing can be finished.
Why safe mode will work?
In safe mode, only one OST file will be locked for use and indexing can be finished.
https://social.technet.microsoft.com/Forums/office/en-US/e8ce3243-5c46-4851-ac2e-19e2b3bdbad8/outlook-indexing-and-rds?forum=winserverTS
The above question in MS Technet confirmed my findings.
The above question in MS Technet confirmed my findings.
ASKER
While I appreciate the comments, I don't see how this is an unsupported configuration. If you can provide a Microsoft KB article saying as much, then I'll definitely agree with you. That MS Technet article doesn't get you there as far as it being a Microsoft official unsupported configuration
I cannot locate a Microsoft KB article.
My wild guess us that MS will not be interested to provide a solution.
Somehow, Citrix, the provider of RDS solution do have a deployment guide which says:
"In a non-persistent environment (pooled VDI or XenApp), searches will be slow until the index is rebuilt for each user session. In a non-persistent environment, the cache file must be rebuilt, unless the cache file is redirected to a persistent store.
Source: https://www.citrix.com/content/dam/citrix/en_us/documents/products-solutions/deployment-guide-office-365-for-xenapp-and-xendesktop.pdf
My wild guess us that MS will not be interested to provide a solution.
Somehow, Citrix, the provider of RDS solution do have a deployment guide which says:
"In a non-persistent environment (pooled VDI or XenApp), searches will be slow until the index is rebuilt for each user session. In a non-persistent environment, the cache file must be rebuilt, unless the cache file is redirected to a persistent store.
Source: https://www.citrix.com/content/dam/citrix/en_us/documents/products-solutions/deployment-guide-office-365-for-xenapp-and-xendesktop.pdf
ASKER
Thanks for the reply Jackie. If you do find that Microsoft KB, please shoot it over. I would love to have that for my records as I'm sure this issue will arise again.
It is definitely an unsupported configuration. Details are as follows:-
The supported configuration is to use Online mode for "Virtualized or Remote Desktop Services (RDS) (Terminal Services) environments that run Outlook 2013 and on which disk size or disk input/output (I/O) limitations prevent running Cached Exchange Mode at the scale you want."
Source: https://technet.microsoft.com/en-us/library/jj683103.aspx
Outlook 2010 or later versions hosted remotely by using Windows Server 2008 R2 or later Remote Desktop Session Host (RDSH) or Virtual Desktop Infrastructure (VDI) configuration
Outlook 2010 or later versions functionality is supported when networked .pst or .ost files are used under the following conditions:
A high bandwidth/low latency network connection is used.
There is single client access per file (one Outlook client per .pst or .ost).
Either Windows Server 2008 R2 or later Remote Desktop Session Host (RDSH), or Windows Server 2008 R2 or later Virtual Desktop Infrastructure (VDI) is used to run Outlook remotely.
If a specific Outlook feature stops working or the .pst or .ost file becomes corrupt and you can reproduce the issue in the above environment, contact Microsoft Support.
Note Customers are responsible for both defining and maintaining adequate network and disk I/O. Microsoft will not assist in troubleshooting slow performance due to networked .pst or .ost files. Microsoft will only assist if the performance issue is reproduced while the .pst or .ost file is located on either a hard disk that is physically attached to the computer that is running Outlook, or on a virtual hard disk (VHD) that is attached to the virtual machine that is running Outlook.
Source: https://support.microsoft.com/en-us/kb/297019
If you do not store the ost file in a permanent store, it will rebuild every time you logout and login the RDS to run MS Outlook. So, the search result is just like what you have experienced.
The workaround is to:-
* create a mapped drive to store the .ost
* set cached mode to cache only one month of email.
This has resulted in fairly good performance (even at first email login.) Most of the emails customers want immediate access to falls in that one month window. The options still exists to search the server for emails going back further.
Source: https://forum.appsense-exchange.com/forums/showthread.php?1285-Office-365-Outlook-OST-file-in-non-persistant-VDI-land&s=e166b18f410719675fa6f124bb8f22af
The supported configuration is to use Online mode for "Virtualized or Remote Desktop Services (RDS) (Terminal Services) environments that run Outlook 2013 and on which disk size or disk input/output (I/O) limitations prevent running Cached Exchange Mode at the scale you want."
Source: https://technet.microsoft.com/en-us/library/jj683103.aspx
Outlook 2010 or later versions hosted remotely by using Windows Server 2008 R2 or later Remote Desktop Session Host (RDSH) or Virtual Desktop Infrastructure (VDI) configuration
Outlook 2010 or later versions functionality is supported when networked .pst or .ost files are used under the following conditions:
A high bandwidth/low latency network connection is used.
There is single client access per file (one Outlook client per .pst or .ost).
Either Windows Server 2008 R2 or later Remote Desktop Session Host (RDSH), or Windows Server 2008 R2 or later Virtual Desktop Infrastructure (VDI) is used to run Outlook remotely.
If a specific Outlook feature stops working or the .pst or .ost file becomes corrupt and you can reproduce the issue in the above environment, contact Microsoft Support.
Note Customers are responsible for both defining and maintaining adequate network and disk I/O. Microsoft will not assist in troubleshooting slow performance due to networked .pst or .ost files. Microsoft will only assist if the performance issue is reproduced while the .pst or .ost file is located on either a hard disk that is physically attached to the computer that is running Outlook, or on a virtual hard disk (VHD) that is attached to the virtual machine that is running Outlook.
Source: https://support.microsoft.com/en-us/kb/297019
If you do not store the ost file in a permanent store, it will rebuild every time you logout and login the RDS to run MS Outlook. So, the search result is just like what you have experienced.
The workaround is to:-
* create a mapped drive to store the .ost
* set cached mode to cache only one month of email.
This has resulted in fairly good performance (even at first email login.) Most of the emails customers want immediate access to falls in that one month window. The options still exists to search the server for emails going back further.
Source: https://forum.appsense-exchange.com/forums/showthread.php?1285-Office-365-Outlook-OST-file-in-non-persistant-VDI-land&s=e166b18f410719675fa6f124bb8f22af
ASKER
From the first KB article...direct copy/paste
Outlook 2013 supports running in Cached Exchange Mode in a Remote Desktop Services (Terminal Services) environment that has multiple users.
Additionally, this is for Outlook 2016.
Outlook 2013 supports running in Cached Exchange Mode in a Remote Desktop Services (Terminal Services) environment that has multiple users.
Additionally, this is for Outlook 2016.
Yes. It is supported but there is a limit for the .ost file. Your ost files for users exceed the processing power and disk I/O of your RDS.
Besides, can you try to sync only one year of data for your ost file?
https://social.technet.microsoft.com/Forums/office/en-US/aaf517f8-62c2-4d73-b4f2-f4102cfab58c/server-2012-r2-user-profile-disks-and-outlook-search-not-working?forum=winserverTS
Besides, can you try to sync only one year of data for your ost file?
https://social.technet.microsoft.com/Forums/office/en-US/aaf517f8-62c2-4d73-b4f2-f4102cfab58c/server-2012-r2-user-profile-disks-and-outlook-search-not-working?forum=winserverTS
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm going to award you points based on effort here. I appreciate all the helpful tips you've given. We were unable to figure this problem out and had to move the users off the terminal server and onto their locals. I'm not really sure what the problem actually was. I have quite a few terminal servers out there with very similarly sized OST files. Granted, they don't have Office2016, but they all work fine.
No problems of any kind running Outlook in cached mode with decent-sized OST files on an RDS server.
Thanks very much for all your help.
No problems of any kind running Outlook in cached mode with decent-sized OST files on an RDS server.
Thanks very much for all your help.