This message was deleted.
# citrix-vad
s
This message was deleted.
t
I’m just finishing off a fairly large 1909 VDI image at the moment. It’s the first VDI I have done as we have been an RDSH shop up to now. I’ve been using the guides from yourself and Mr Rankin and I’m pretty happy with how it’s performing. I did get caught out by the WEM process names and path changes in our last update which meant the AV exclusions were no longer correct. I do get a black screen on logon between the GPO processing ending and the WEM agent starting. It seems to last about 9 seconds, so I would be interested in knowing if you see the same.
j
Black screens we are working through at the moment but pretty sure we know the root cause - are you using FSLogix Profiles by chance? 1909 has been my least favorite VDI deployments - the compute requirements are much larger than previous even if you optimize the crap out of it
c
We use 1909; SEP sucks, we moved to defender. Not make sure the sep scans are set at night and ur exclusions.Also with fslogix I noticed my uwp apps go missing. I have an open ticket. Gonna downgrade to 7117. Can you set it he DG to register on a delay? Is it the vdi slow when it's been on for a few minutes? Bit I have not seen general slowness with 1909
j
there is a known issue with AppX and FSLogix in 1909 which is resolved in 2004 - that also impacts black screens from what we have seen - we have registration delays in place etc, looking at anything we can do in that warm up period to reduce the impact when the logon occurs - work in progress 🙂
c
@James Kindon is that for all fslogix versions?
j
I think so @Nick Panaccio pointed me at a twitter post - seemed to be 1909 related rather than FSLogix
c
The fslogix supper rep said if I enable the store it’s a workaround
j
my issue is the registration of appx packages happening at every logon and spanking the CPU
c
Yuck, I guess that’s a fix but does slow it down. I am not ready to go to 2004
j
I am - cant wait to get the 2004 image out there to get rid of this fluff for this customer
n
Is there a VDI/clone AV sealing procedure for Symantec?
l
Symantec sicks massively mate, i have it in a current project on server 2019. Constant issues. Make sure its in the right container in SEP or it'll run like a dog. The machines have to be moved into the correct container manually or using a routinely scripted approach. You can check your current exclusions in the registry btw.... this was the heavy hitter for me. To test quickly, change the service state key in the registry if your image and roll an uodate, this will disable sep and see if your issues go away.
t
I am using FSLogix for the profiles, so any links to the black screen problem would be useful. The only AppX package I use is calculator, everything else is turned off. For warming up the image i'm doing an auto login with the Citrix Desktop service controlled by the script from Jeremy Saunders, a scheduled task to update the WEM cache and BIS-F. If your using BIS-F I found the personalisation startup script was doing a Win32_Product class WMI query that was causing all the installed MSI applications to reconfigure. The bigger your image the bigger the impact and it may be exasperating your problems with Symantec as well. I raised a bug report (#270) and Matthias has a fix in the place for the next release. You can download the updated script from the bug page.
👍 1
j
thanks lads - had some exclusions updated which helps, also have a change in to get the "scan on definition update disabled", i need to look at the service state key 😛
@TimonW interesting - thanks for sharing this - we are using the delayed desktop service with an insurance policy script i wrote here https://github.com/JamesKindon/Citrix/blob/master/CheckBrokerService.ps1 <- just protects against BIS-F failing to start the service...we are doing some warm up stuff and autologon will come in via sysinternals shortly - bloody App-V streaming is also kick the crap out of the image
j
Auto-logon and advance power-up
t
Looking into the FSLogix black screen on 1909 it looks likes it Windows Search. The FSlogix search roaming settings were miss-configured so I have set them up as per your blog post, reset the search index for my test users which has helped reduce the black screen time considerably.
l
Perhaps MS need to step down their release cadence a little, there really is so much to test now when pushing out a new image. Enter products like LoginPI (LoginVSI Entperise now) and ControlUp for the proactive monitoring.