Mundy

IT Knowledge Base

User Tools

Site Tools


issues_with_windows_search_index_and_user_profile_disks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
issues_with_windows_search_index_and_user_profile_disks [2017/10/17 11:59]
Dan Mundy created
issues_with_windows_search_index_and_user_profile_disks [2018/04/09 09:56] (current)
Line 7: Line 7:
  
 Other option is 3rd party solutions which replace Windows Search. Eg [[https://​docs.fslogix.com/​display/​20170529/​Roaming+the+Windows+Search+Database|Roaming the Windows Search Database - FSLogix Apps 2.8.6 - Documentation]] Other option is 3rd party solutions which replace Windows Search. Eg [[https://​docs.fslogix.com/​display/​20170529/​Roaming+the+Windows+Search+Database|Roaming the Windows Search Database - FSLogix Apps 2.8.6 - Documentation]]
 +
 +{{page>​ad&​noeditbutton&​nofooter}}
 +
 +----
 +
 +Another interesting thing suggests maybe it's all better in Outlook 2016? :
 +
 +<​blockquote>​
 +In pooled VDI and RDSH deployments,​ using search within Outlook has limitations. Search indexing depends on the machine ID, which is different for different VMs. It is possible that every time a user logs into a pooled VDI infrastructure,​ they are directed to a new VM. That would mean, if we enable local search, the indexer will run every time the machine ID changes (when the user is on a different VM). Depending on the size of the .OST file, the indexer could take a long time to complete and use up resources needed for other apps. Search would not only be slow but might not produce results. Using an Online Mode account profile would work around this, but overall performance would suffer due to the lack of a local cache.
 +Learn more about the difference between cached and online mode.
 +
 +Outlook 2016 has a solution to tackle this in cached mode by providing a new service search experience for mailboxes hosted on Exchange 2016 (or hosted in Office 365). This uses service search results against the local cache (OST). Outlook might fall back to using the local search indexer in some scenarios, but most searches would use this new service search feature. The recommendation for pooled VDI and RDSH deployments would be to use Outlook 2016 in cache mode with network connectivity to allow service search.
 +
 +<​cite>​[[https://​docs.microsoft.com/​en-us/​windows-server/​remote/​remote-desktop-services/​rds-office-vdi-rdsh|Office 2016 in RDSH and VDI deployments | Microsoft Docs]]</​cite>​
 +</​blockquote>​
issues_with_windows_search_index_and_user_profile_disks.txt ยท Last modified: 2018/04/09 09:56 (external edit)