Hi,
We have about one user a week where their indexing is failing. We are running VMware View 6.0 and esxi 5.5 update 2 along with Unidesk to push out our apps. Our client is Microsoft outlook 2010 - exchange server is 2007.
If I click in the search window the search ribbon is greyed out - along with the filter button. Going to control panel - indexing options - outlook is usually not listed and indexing appears to not be running.
To fix it we have been running the MS fix it for search issues and also deleting the config\TxR\*.* hidden files and bouncing the workstation.
Our View workstations are Windows 7 pro with 4 gb of ram. ( i have the problem currently on my wkst and im at 8 gb ).
One thing i know we are doing that is not best practice is we are keeping the OST on a network share. We have a paid support ticket in w/ Microsoft.. they stated to move the OST 's local and upgrade our Exchange server.
Any one actually 'solve' this indexing issue ?.. or is it something I need to live with ?. We have about one user a week that has this issue would be great to fix.
Any ideas ? This issue is easy to quick fix for a user temporarily.. just would like to find a 'global' fix if possible.
I know there are third part indexers.. however they seemed rather spendy.
thanks for your consideration.
- JB
We have about one user a week where their indexing is failing. We are running VMware View 6.0 and esxi 5.5 update 2 along with Unidesk to push out our apps. Our client is Microsoft outlook 2010 - exchange server is 2007.
If I click in the search window the search ribbon is greyed out - along with the filter button. Going to control panel - indexing options - outlook is usually not listed and indexing appears to not be running.
To fix it we have been running the MS fix it for search issues and also deleting the config\TxR\*.* hidden files and bouncing the workstation.
Our View workstations are Windows 7 pro with 4 gb of ram. ( i have the problem currently on my wkst and im at 8 gb ).
One thing i know we are doing that is not best practice is we are keeping the OST on a network share. We have a paid support ticket in w/ Microsoft.. they stated to move the OST 's local and upgrade our Exchange server.
Any one actually 'solve' this indexing issue ?.. or is it something I need to live with ?. We have about one user a week that has this issue would be great to fix.
Any ideas ? This issue is easy to quick fix for a user temporarily.. just would like to find a 'global' fix if possible.
I know there are third part indexers.. however they seemed rather spendy.
thanks for your consideration.
- JB