Random Issues with WVD

%3CLINGO-SUB%20id%3D%22lingo-sub-1166947%22%20slang%3D%22en-US%22%3ERandom%20Issues%20with%20WVD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1166947%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20a%20few%20issue%20going%20on%20with%20our%20WVD%20deployment.%20The%20biggest%20two%20issues%20we%20are%20facing%20right%20now%20are%20as%20followed.%20Also%20these%20two%20issues%20just%20started%20about%20a%20week%20ago%20on%20a%20deployment%20that%20was%20put%20into%20production%20on%20Nov%2015th%202019.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFile%20Explorer%20-%20Very%20slow%2C%20takes%2045%20seconds%20to%20a%20minute%20to%20open.%26nbsp%3B%3C%2FP%3E%3CP%3ERemote%20Printing%20-%20We%20redirect%20local%20printers.%20Worked%20fine%20until%20about%20a%20week%20ago.%20No%20updates%20or%20modifications%20to%20software%20has%20occurred.%20Printing%20sometimes%20takes%20up%20to%2030%20minutes%20to%20spool%20to%20the%20local%20printer.%20This%20occurs%20with%20several%20users%20in%20several%20locations.%20Not%20specific%20to%20a%20user%2C%20location%2C%20or%20model%20printer.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOutlook%20search%20does%20not%20work.%20Running%20latest%20FSlogix%20version.%20We%20have%20gotten%20two%20different%20answers%20in%20regards%20to%20FSLogix%20ROAM%20Search.%20One%20is%20ROAM%20Search%20should%20be%20set%20to%202.%20One%20says%20with%20Windows%2010%20MS%20and%20Windows%20Server%202019%20the%20search%20feature%20is%20built%20in%20and%20no%20options%20for%20ROAM%20Search%20should%20be%20set.%20We%20have%20attempted%20both%20and%20neither%20work.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewindows%2010%201903%2C%20but%20also%20occurs%20on%20Windows%2010%201909.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20experience%20any%20of%20these%20issues%20and%20have%20a%20resolution%20or%20workaround.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1675262%22%20slang%3D%22en-US%22%3ERe%3A%20Random%20Issues%20with%20WVD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1675262%22%20slang%3D%22en-US%22%3EDid%20you%20ever%20get%20to%20the%20bottom%20of%20your%20issue.%20We%20are%20experiencing%20similar%20Windows%20Explorer%20issue%2C%20were%20you%20using%20OneDrive%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1692028%22%20slang%3D%22en-US%22%3ERe%3A%20Random%20Issues%20with%20WVD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1692028%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F553539%22%20target%3D%22_blank%22%3E%40RYCUL80%3C%2FA%3E%26nbsp%3Bwe%20are%20having%20the%20same%20issues%20with%20Explorer.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20whole%20client%20is%20pretty%20buggy%20I%20find.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGood%20luck%2C%20will%20be%20interested%20to%20hear%20if%20anyone%20can%20solve%20this%2C%20although%20don't%20expect%20anyone%20from%20MS%20to%20reply.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

We have a few issue going on with our WVD deployment. The biggest two issues we are facing right now are as followed. Also these two issues just started about a week ago on a deployment that was put into production on Nov 15th 2019. 

 

File Explorer - Very slow, takes 45 seconds to a minute to open. 

Remote Printing - We redirect local printers. Worked fine until about a week ago. No updates or modifications to software has occurred. Printing sometimes takes up to 30 minutes to spool to the local printer. This occurs with several users in several locations. Not specific to a user, location, or model printer. 

 

Outlook search does not work. Running latest FSlogix version. We have gotten two different answers in regards to FSLogix ROAM Search. One is ROAM Search should be set to 2. One says with Windows 10 MS and Windows Server 2019 the search feature is built in and no options for ROAM Search should be set. We have attempted both and neither work. 

 

windows 10 1903, but also occurs on Windows 10 1909. 

 

Anyone experience any of these issues and have a resolution or workaround. 

2 Replies
Did you ever get to the bottom of your issue. We are experiencing similar Windows Explorer issue, were you using OneDrive?

@RYCUL80 we are having the same issues with Explorer.

 

The whole client is pretty buggy I find.

 

Good luck, will be interested to hear if anyone can solve this, although don't expect anyone from MS to reply.