This message was deleted.

Yes, you need to configure the RoamSearch to 2, and not 1

Thanks Kasper, Is the RoamSearch set to 2 the same things as the group policy settings that says Allow concurrent user sessions? Regardless of the answer if i make this change will it have any negative impacts on current users?

Yep, there is another setting you need to select. Type of user search.

Leee, but im not having multiple OST access. Users always reconnect to the same desktop. This was something i just noticed in the log that made me review my settings. So, it sounds like question 2 is a yes, question 5 is VHDX is fine with 365 containers. Any idea about questions 3 and 4?

The GPO value is: Computer Configuration\Administrative Templates\FSLogix Enable Search Roaming But this value has to be set during/after the FSLogix Apps Agent setup, or Search Roaming might not work

You can change the reg keys without impact as right now search roaming is not working.

Kasper\Lee, Thank you I missed that. Is there a way to fix it this oversite since I already have about 100 or so profiles deployed.

You may have had it enabled already, if so... change the reg key and try a login. Should be fine.

Ah, thank you, So it sounds like I make the reg\gpo change and then can reinstall the fslogix app and will be good. What about Office. I have read a few times that you have to repair office if it was installed prior to some of these changes.

Yeah, that's an interesting one and it amazes me why this isn't mentioned in the documentation Back when FSLogix was just FSLogix they had a whitepaper describing how to get search roaming to work properly. There is a specific order you have to install/enable: 1. Enable the Windows Search Service 2. Reboot 3. Install Office 4. Reboot 5. Install FSLogix 6. Reboot All reboots might not be necessary, but I have spent a lot of hours troubleshooting search index roaming, and I know this works

great, i gues rx reset-user-search-db -user domain\user wouldnt hurt also, that resets the search index.

You should use that if you see search index corruption, if you have that trust me you will see it in the event viewer 🙂

But I guess the thing that trips me up is, why is this setting needed for me anyway I ideally never had or never will have users connected to multiple sesssions using the same FXlogix container. I assume the error was because I set the store search database in office 365 container and didnt Enable the Search Roaming feature.

Yes, the error message it not related to multi-session usage

i might have to read a little. Is the word roaming not like roaming profile? I assumed it was a multi session setting.

Well, no 🙂 Search index roming, is the user's windows search index being saves within either the profile container or the office container.

Wonderful wording 🙂 . So is it true then I didnt need to set either of them and leave them at the defaults and all would have been fine?

Yes, if you don't need search index roaming or multi-session usage, then yes, leave the default values

But, if i did need multi session, then I would need the allow concurent users sessions to be enabled. And I can do that when the user use to be set for single user session

Yes, you can do that

last question, I Maybee promise that. What is the use case for turning on index roaming. Why wouldnt the index just get saved to one of the containers

Yes, it does actually, because FSLogix can take the user specific part out and save it in the container and then inject it again when it's needed on another machine

Wait, it still saves the entire index on the host? Does it ever resize it when it pulls out the user specific part? Shoot I thought fslogix would help with the large file sizes that the index takes up on the local C drives of the servers.

I don't know exactly how FSLogix does it, but they have found a way to extract the user specific data of the machine based search index, save it in the container and then inject to the machine based index again

Ok, so its dynamic. They pull it out of the C drive file thus reducing its size on C, place it in the container where it sits there until a users logs into another and then injects it. If so that is amazing

Yes

wow, its like we are now at the file level virtualiztion or containerization

Yeah, this is probably one of the technical reasons why MS acquired FSLogix 🙂

Ok, really really last question. When i redo this, should i reset/delete the current index file that is on local server to make this clean

That shouldn't be necessary, it's cleared out when the server is rebooted

Alright, that was fun. Is there a way to confrim that search is roaming into the container?

The logs will show u that, as well as the search db in the profile i believe.