Native Outlook Experience Hi everyone I use Native Outlook Experience with Windows 2025 and CVAD 2507. I put the EnablePerUserCatalog and I observe errors in application event logs for Outlook and Search Index. I don't know if those error impacts users. Does anyone use native Outlook experience ? Do you observe the same ?

Search sucks. With that out of the way, I am using Native Outlook on Windows Server 2025 and CVAD 2507 CU1 with the Microsoft EnablePerUserCatalog Enabled and the Citrix Enable search index roaming for Outlook - Disabled. It works most of the time, but not all of the time. The Search Index will get corrupted occasionally and we get errors in the logs. I have a script that clears and resets the user search index folders for the logged in users and I rebuild the local index at the same time twice. I don't know why, but I have found that doing the double rebuild helps get the users to rebuild. I haven't found a reliable method to automate that process though, if someone has one I would be interested in learning it.

Why not enable search index roaming ? That means the search index is rebuilt every time ?

Microsoft Roams the search index better than Citrix roams the search index in my experience. If you enable the Citrix roaming, you should disable the Microsoft EnablePerUserCatalog. They are competing settings in which manages the roaming index. They roamed indexes both live in <username>\AppData\Roaming...but Citrix goes to Citrix\... and Microsoft (EnablePerUserCatalog) goes to (you guessed it) Microsoft\...

And how do you handle ost cache ? With Enable search roaming enabled, ost and search are in an VHDX container.

I used to put them outside the profile container on a network share, but Microsoft has been not honoring the setting for new profiles recently, so now when Outlook profiles get rebuilt, they get placed in the VHDX.