I'll just say that we have less search issues with 2019 than 2016 (and have no roaming search on the remaining few clients with 2012R2 servers, so they don't have search issues either). We have the settings from James' site in place as well. It works much better than the Citrix solution, but that could just be that 2019 works better than 2016. Even the 2019 servers though will work great, until they don't and we have to try and figure out why they break. If resetting the search index were a simple task, like adding a registry key or something, things would go much more smoothly. Usually it's the index gets corrupted and breaks the searchindexer on the server, which corrupts other users and it spirals out of control until we can get things cleared up. The Citrix index cleanup is a little easier as we can just delete the VHDX files with the users logged out. Trying to clean up the indexes for the Microsoft solution is more difficult as we have to get into the profile container (Citrix UPM) to clear the index location without deleting other things in the profile. The Citrix solution did not work well on 2019 servers so we went to the Microsoft way for 2019. It's just been a huge frustration that we can't just get it working consistently. It requires constant monitoring and after-hours clean up.