Meanwhile we experimented with a vanilla Windows 10 golden-image, meaning no Symantec Endpoint Protection, just Windows defender. I attached the VDA session start-up times for the Symantec-start-up and the Win10-Vanilla-/Defender-startup.Įdit: Not nearly as bad as 4 minutes as mentioned in the former discussion, but the VDA-Launch-Duration isn't the only amount of time the user experiences as well.Īfter further investigation with the Citrix Support I received a link towards antivirus exclusions best-practices for Citrix environments, sadly it doesn't mention UPL and its services at all. we can't create an isolated Symantec-Layer. I know this goes side-by-side with the App-Layering via ELM, but e.g. This means we have the Symantec antivirus installed in our golden image and than creat a Pool of desktops via MCS, with the UPL-Policies configured. The main difference between the existing discussion and our issues is that we aren't using App-Layering via ELM, but the User Personalization Layer Feature inside the VDA and Studio of CVAD 1912 LTSR.
This shouldn't probably link to the discussion again, but another source? Still I'm prretty certain we run a supported version of SEP.Įdit: You probably meant to link to this: - Yes, we are using a supported version.
Not sure how else to troubleshoot this (I don't have access to SEP in a lab for testing), but I'm willing to continue to poke at this with the hopes of getting to a resolution for you (or at least a understanding of the 'why').Ĭan you confirm (as per ) that you are running a supported version of SEP (and are following the guidance of the deployment of SEP to the layer could you provide details on how you are deploying SEP to the layer)? In Director, is the session startup portion of the session details page showing any difference in start up times from the with/without SEP present testing? If so, could you provide a screenshot of each to show the differences?
Regarding the experiencing similar issues or best practices, the following discussion thread seems to point to the same issue you are face (no resolution though, but there are additional things they tried to resolve the issue):Ĭan you confirm (as per ) that you are running a supported version of SEP (and are following the guidance of the deployment of SEP to the layer could you provide details on how you are deploying SEP to the layer)? I didn't see anything in the first discussion URL posted above regarding their version, but it's always a good thing to verify when troubleshooting.
0 kommentar(er)
