This message was deleted.
# microsoft-fslogix
s
This message was deleted.
d
Outlook will not show up as indexed location, that’s by design. Did you install Office after enabling the search service? If not you will have to reinstall or repair Office.
k
Forgot to mention, that I am running the latest updates for both Windows and Office 365 and I have found this article in the MS support forum: https://social.technet.microsoft.com/Forums/lync/en-US/e87a25c5-71b8-412a-ba82-b7fa07a7363b/windows-search-changes-in-server-2019-rds?forum=winserverTS A few workarounds are mentioned in the article, but they don't seem to work with FSLogix.
Yes, I am following the procedures outline by FSLogix a few years ago 1 - Enable Windows Search Service 2 - Reboot 3- Install Office 365 4- Reboot 5 - Install FSLogix agent + "hardcode" the RoamSearch registry 6 - Reboot
I am pretty sure Outlook show up in Indexing Options in Windows Server 2016
j
I've had it working in 2019 with a customer recently - check your fslogix search logs and see what it has to say. I always check index within outlook search options as a good indicator
k
Hmm...nice to hear that it is actually working
I am going to go through my config once more
Hmm...it does look like it's working, but it is definitely not behaving as when it's installed/configured on 2016. I don't see any mail count up or count down in the Indexing Status box, but it looks like FSLogix is building the index though
j
maybe reset the outlook profile and make sure 100% its dead - maybe its nicely indexed already đŸ™‚
k
I am testing with a clean profile everytime