This message was deleted.

Which OS?

Windows 2019 with Office 365. All latest patches installed.

Do u use citrix optimization? This kills the windows search service 😵

Yes BISF and Citrix Optimizer 2.6.0.118

the default VDA optimization is the same as the PVSTragetOSOptimizer and this disable the the Search Service

Okay, so will this require a new Master Image build, or just upgrade to 7.1912 and reseal?

check if you use the VDA optimization switch in the comandline to install the VDA

$UnattendedArgs = '/quiet /components vda /controllers "'+$ListofDDCs+'" /mastermcsimage /install_mcsio_driver /optimize /enable_remote_assistance /enable_hdx_ports /enable_hdx_udp_ports /enable_real_time_transport /disableexperiencemetrics /includeadditional "Citrix User Profile Manager WMI Plugin" /exclude "Personal vDisk","Citrix Telemetry Service" /virtualmachine /noreboot /logpath "C:\Windows\Temp"'

@Eric did you installed Office then WS Search Service?

the default settings of the optimizer for VDA and PVS

Yes Its included in both VDA Optimizer and Target Device Optimizer

Office is installed after WSearch is installed & started

Okay..

Latest O365

Never 😉 seems that maybe the WSearch service was not set to Automatic, henche to started prior to Office

Now its working after u set to Automatic to WSSearch Service

Fixed to Automated for now - https://github.com/haavarstein/Applications/blob/master/Microsoft/Windows%20Search/Install.ps1

is it’s working now without the optimize switch ?

Rebuilding as we speak, WLYK

so the WSearch service needs to be set to delay?

NO, @James Kindon just put his awesome t/s post on his site : https://jkindon.com/2020/01/06/fslogix-containers-search-index-considerations-and-troubleshooting/

Ahh I seen this, this morning. But didnt read it yet. NICE! Good find

I’m curious about FSLogix Search Roaming with Server 2019, because MS Support lately told us that Server 2019 RDSH comes with its own user based search index which is stored in a folder under AppData\Roaming\Microsoft\Search. See related msdn forum thread here: https://social.msdn.microsoft.com/Forums/en-US/a9b5000d-e2a8-442b-9cbf-48e05136f732/support-for-server-2019-and-office-2019-search-roaming?forum=FSLogix @Eric Are you sure FSLogix search roaming is working correctly? Hooking, second logon...

No sure, that whats why I’m pulling my hairs ;-)

@Eric I’ve been nailed a few times with search and auto start - any dodgy optimiser that even touches the search service on build should be shot - on master image builds you want it to set to auto and never touched, then bake search roaming key into image, then install office, then reboot and make sure all is running before sealing - the optimise switch in the VDA should be made defunct IMHO

Thx James, your re-post today came handy. Just added FSLogix GPO to Stage OU and removed /Optimize & also have script to Install Search Feature and set Service to Auto before reboot (will remove feature since I had that mixed up with WS12). Now building new image on WS16 just to test. It might seem its still not prime time on WS19 ref the MSDN forum post above.

I have had search going OK on 2019 with outlook 2016 - but the whole search component across 2016 and 2019 is pretty sensitive

This is O365, lets see how it goes. Rule out config first, then its easy to swap OS in the build.

what does /optimize actually do? I use it all over the place. 😕

He’s fast :-)

That he is. I need to get me some BISF. I'm writing up some stuff to get you in here for. MDT/BISF/Choco stuff. Just need to articulate it enough.

as an insurance policy i always put a GPO in that enables the windows search and sets to auto for any OU's containing any VDA's and master images - that way i dont care who does what, search always gets set back the way it should

smart

protects against silly things like Citrix using logic from yesteryear when "optimising" an image

Really smart

so really, you could just do both, it's not going to hurt anything, and just enable Search with GPO and you're good to go.

yep - i think i put in a feature request for BIS-F to quadruple handle the check

One this that bit me a couple of times, I think James said this as well https://social.msdn.microsoft.com/Forums/windows/en-US/2b4b271a-c29c-44c5-b5a7-b28f5a809be6/outlook-search-troubleshooting-guide -- If search was enabled (through Windows features) after Office was installed the .dlls will not be in place. Run Add/Remove programs repair on the MS Office entry to fixthis issue: https://support.office.com/en-us/article/Fix-search-issues-by-rebuildling-your-Instant-Search-catalog-213a2728-0ef4-427a-9bb2-aed329a59b17 •If an MS Office Repair doesn't fix the issue... Or if LoggingEnabled=2 and RoamSearch=2 and there is not a SearchPlugin log directory or thereare no logs being generated in that directory, then one or more of the FSLogix .dlls is not registering. •To resolve, please do a Full uninstall/reboot/reinstall of FSLogix. You may also need to clean the registry of all FSLogix settings betweenuninstalling and reinstalling FSLogix.

GPO at Staging OU will prevent Office issues if not started, so just do it!

So no go on 2019?

Not at the moment, UX first and BTW we’re in the UAT stage. But will continue to play with WS19 in Dev.

Way to hammer it out man.

does ms / fsl know of this issue with 2019 and its in the pipeline to be fixed?

Nick - I do not believe anyone on this thread has opened a support case yet. I tried to, and cannot. Want to give it a go?

@Tim Riegler I opened a case. See MSDN forum thread

👍