https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# citrix-vad
s
This message was deleted.
a
we're mcs persistent w/out using profile management (for the most part) so may not be the same kind of comparison but a first time logon for us usually is about 30 seconds and each after is between 15-20 seconds (sometimes a little more , sometimes a bit less). are you stopping the clock when you can fully interact w/ the start menu i assume?
i'm sure you have this already but on a dual screen setup we found one of the biggest culprits for longer login times was the Acrylic Background blur deal Windows 10 brought in (i think in the 1809 build?). disabling that helped quite a bit
n
I should mention, this is non-persistent PVS on 1912 LTSR CU3.
And yeah, @Guy Leech tweeted about that long ago, which prompted me to make the change.
👍 1
a
cool yup i remembered you were non persistent and pvs so not apples to apples here
n
I run Citrix Optimizer, rip out all UWP apps, use WEM as much as possible, have efficient GPOs, etc. I think I'm doing everything that I can think of to help with this. New hardware, which I'm getting this summer, should help, and I've heard rumors that 2203 is faster (@dready I think mentioned this?).
⤴️ 1
o
No user GPO, all in WEM, logon time = 20 seconds.
n
I swear I've tested no user GPO, and it didn't really cut down the login time. I can certainly revisit that, though.
o
Please do. The waiting time we can see is the "FSLogix Apps Service" which is normal, last 4 seconds or so. Then Explorer kicks in, takes 15 seconds to make the desktop operational.
n
I've looked at our FSL logs, and didn't see that much of a delay. Also ran Guy's COntrolUp logon analyzer script which didn't really reveal anything glaring.
I know FSL is a little slower for the logon than CPM, but I just cannot go back to CPM as it stands.
o
Yeah, no surprise.
You mean CPM with Profile Streaming then
n
20 seconds from clicking on the published desktop to seeing your desktop on a brand new profile?
o
no, no brand new profile
n
Okay, so connecting to an existing profile
o
yes, brand now profile you have the Active Setup etc
n
That's still 7-10 seconds faster than my setup.
Defender is actually responsible for adding roughly 10 seconds to my logon.
o
We have McAfee, so I can't say about that
n
My guess is that you'd get your logon down to 15 seconds without McAfee, lol
We just ditched McAfee in our enterprise. All Defender now.
o
lol, maybe
we are heading this way too, yes
n
Enjoy. It's... fun.
If you run into issues with your VDA, post up here. I went through a lot of bullshit to get things working nicely with Defender.
👍 1
o
but from the click on Desktop icon, in StoreFront or CWA, we get to 20 seconds before the desktop being operational
it seems like Windows would go to synchronous GPO/GPP processing sometimes
I just removed all of that, so it never happens
n
I think 20 seconds would be perfect. Can't see anyone complaining about that. Not sure I can get there, though. Certainly not on my existing E5-2697A hardware.
I don't have any GPP stuff anymore - all of that is now in WEM. Moved Folder Redirection to WEM, too, which cut nearly 20 seconds off the logon.
o
For sure, folder redirection was quite something for us too, I've removed that as well
n
I just moved it from GPO to WEM. Single best move I made.
o
Indeed. But we have instructed our helpdesk team to prepare the "new" user profiles
so our benchmark never include a brand new profile
n
Prepare new profiles?
o
For a new employee, they prepare it
login once, etc
n
Wow, that's a new one for me.
SOunds like a great idea, though.
o
Well, even for a profile reset
sort of "quality of service"
not such a high price to pay, our users keep their profile for months if not years before they need a reset
n
I'm going to throw that into the hat as an option, let leadership shoot it down. I like that idea.
I have only had to kill one FSL profile since going live.
and they were a crazy user who bastardized everything
o
Well, especially with WEM, because WEM is a post-logon thing so with a brand new profile you must have a lot of things not in place
for your very first logon
n
WEM should run while you're already in your desktop session, though
o
yes it does, but I think that your very first logon, on a brand new profile, might not be the best
n
I'm an App Layering user, too, so I can't move some of those registry keys to the default profile.
o
I was an App Layering user too. Trying to convert them in my new place. 🙂
n
Honestly, I can live with an extra 10 seconds or so for the initial profile creation. It's the next logon and others that I think are the target here.
o
Well, using different techniques, like extreme UPM optimization, we would achieve a 30 seconds logon even at the time
but with FSLogix, M365 and the "go big on profile" things have changed a little bit
n
MS doesn't do us any favors. Each build of W10 gets slower. Go-EUC has documented this consistently.
o
yeah, that's why I've decided to go on full WEM, nothing on MS
n
We're going to new Cisco blades with Intel 8362s, so I really hope that alone will alleviate most of this issue.
Our current hardware is just dated, and also affected by those Intel bugs from back in the day.
o
Meltdown? Not still sure if it's the name of the fix or the issue.
n
That's it, Meltdown and SPectre
o
Profile streaming was great because you just download the NTUSER.DAT and deal with the rest later
n
We used Profile Streaming when we were on UPM. It was great, for the most part.
OneDrive alone is reason enough that we can't use it anymore.
o
yeah the only issue was with just mapping drive and printers
n
I use WEM for drive mapping, too/ 😄
o
which is the main things I've noticed to take time in logon, and yes as you say it's all in WEM now for us too, and no issues
n
Printers... we're lucky there. Citrix Universal Print Driver only, and we map any printer the user has mapped on their client.
o
No print servers where you are?
n
Tons of them, but we just bring in what's already mapped on the endpoint.
o
ah
n
Nobody manually maps printers once they're inside the session.
o
so are you suing the print routing policy?
n
I think we're looking at a secure printing product, which may make it even easier. LRS is one of them.
o
what we have is a Follow Me print queue
but still need to map a network printer for that, and it was taking time with GPO, none with WEM
n
That's basically what we're looking for. Single print queue to rule them all.
o
yeah, better for users, as they just login to the printer anywhere and it will fetch the spooler for them and print
n
I don't even want to guess how many printers we have. We're healthcare, and they think you need a printer every 12 feet.
o
hehe
n
can probably find a printer in the bathroom
o
I was working for a company printing 52 millions of pages per year
health provider as well
n
wtf
o
they would send 5 GB of print data per hour on the network, like a DVD
and we found that the Citrix UPD was the best compression ever
I still have the benchmark data, between UPD, Postscrip and PCL6 (which zip print jobs)
and types of document being printed etc, I had to monitor dozens or print servers
We tried Citrix SDWAN or WAN Scaler at the time, and nothing would beat Citrix UPD in the end
best compression
n
Our printing environment is a mess. Some on clusters, some on standalone... not my problem, thankfully.
o
but that's important for Citrix, depending on your strategy, especially if you map the endpoint printer
but if you are using the universal print driver, I know for sure it's the best compression. But you could use the print routing strategy depending on your network, which could be better
n
I am, yes. Wouldn't have it any other way.
o
but for that actually you need the driver to be on your boxes
print spooling is in two pass, high and low spooling
n
And that right there is a major issue. We have so many different drivers that it would be a disaster.
o
yeah, I understand that, UPD then is your best choice
and eventually UPS as a workaround if you have the network
n
Alright, I'm tired of today, so I'm logging off finally. Thanks for the input, I appreciate it. I'm going to mess around with the user GPOs to see if it has any real effect on logon times. If so, maybe I'll take the opportunity to import the policies into WEM entirely.
o
Sure, let me know. Have a great evening.
d
20 secs for subsequent logons should be doable for W10 single session, fslogix, WEM as long as your hardware isn't the bottleneck
r
Nick you are doing AppLayering right?
I skimmed through this message. IF you said that I didn't see it. I do everything you do. Clean GPOs, Monothecal only, Computer GPO, and very few user GPO. All GPP in WEM. Nutanix AHV with nvme and USC with Unity. 18 seconds XA, and VDI is averge 20is high and low. Sometimes it goes higher that 20is and it something in the enviroment that acts up.
n
I imagine that Nutanix would provide a boost, compared to our Cisco UCS blades on Pure flash storage.
r
yea nutanix kicks butt
n
I do wonder how much it would help our logon times by moving to Nutanix. I don't think it's on the table at all, but if I'm being asked “what can we do”, there's no sense in holding back.
r
Do they allow you to admin the hypervisor side? Nick from reading everything you seems to have a fine tuned Environment man. Now obviously newer hardware and Nvme would help. But would it get you down from 40 to 20? That's hard to say. I never used Citrix applayering. I thought you did? I only used PVS with Nutanix AVH super micro servers. Some use MCS and may get better performance but leveraging the DSF software defined storage they have.. maybe. The environment I'm at right now is over 60 seconds. It kills me man, and I'm setting up WEM now to start that in parallel with Fslogix. A lot to do to get them down to 20-30. But I did the pre login with xenapp and it helped. About 5-7 seconds. Are you guys talking about the blurry background setting that's This? HKLM\SOFTWARE\Policies\Microsoft\Windows\System DisableAcrylicBackgroundOnLogon DWORD Value: 1 (Enabled)
You could always take one machine and remove all GPO and polices and test a login. Then slowly add things back to see if your reporting matches .
Wow @Osiris Amanpour you do all user GPO in WEM!!! That's is really cool. I k ow WEM can do HKLM side now. But never tried it. GPO is mature and the ADMX files it offers makes thing easier. However it's all reg settings anyways. I often wonder if all user GPO move over to WEM , how much time would it really save? GPP is a given and done that for a while now.
n
Sorry, yes, I'm an App Layering guy. And yes, that sounds like the setting - Show clear logon background if setting it via GPO. I have access to XenServer, but not UCS or Pure… at least, I don't think I do. Technically not my area of responsibility, so I leave it alone.
r
Gotcha. Would applayering add to it? I don't know crap about citrix applayering. Other than it doesn't like me lol.
n
The only increase we saw with App Layering was when Elastic layering was enabled, which I do not use.
r
I have seen your optimizer configuration you sent me before. It's super clean and you trim a lot of fat. Where In the controlUp guy leech's scripts shows the highest time? Just curious
n
https://www.controlup.com/script-library-posts/analyze-logon-duration/ @Trentent recently modified it to include more information, which makes it even more useful.
d
We have around 10-20sec in our platform(atleast what Citrix Cloud "Director") is reporting. 100% Azure, Most stuff moved to WEM, FSlogix profiles on Azure File Premium and Folder Redirect. Windows 2019
o
@Ray Davis 60 seconds is a lot. It's a risk of users to come with pitch forks and ask for Citrix to be brought down. Especially with the NvMe era and their personal laptops booting in just 1.9 seconds. Yes I'm doing all in WEM, it's a great help for logon times. Huge help actually. For HKLM, I'm trying it but it's not working very well, I prefer to rely on true GPO for that, makes more sense to me, and so far is more reliable. But I am still testing it on WEM.
n
Waiting for replication to complete, but my first test of an existing profile took 42 seconds to get to the desktop. Atrocious.
(current config)
Unlinking all user GPOs cut 4 seconds off the logon.
o
so is that a 26 seconds logon time?
n
38 to see the desktop
This is in QA, which isn't an apples/apples comparison to Prod, so Prod would be a little faster.
o
Not too bad. You can check the different run keys, run the Citrix Optimizer, BIS-F, defrag the disk if on PVS, probably another couple of precious seconds to gain.
Remove all network stacks on the PVS network adapter doing the streaming, except IPv4. I was able to gain some precious seconds just with that also.
n
The one thing I'm worried about is managing GPO settings within WEM. I guess I'd just have to resort to adding the registry values into the console instead of using GPMC's GUI.
o
you can import your GPOs now, this is what I am doing. What you can do is manage the GPO in the GPMC UI, like WEM - GPO 1, WEM - GPO 2 etc, just as an example. Export them (backup in the context menu), zip them, and import then in WEM. If you want to make a change, do it in the GPMC UI, export again, import and check "overwrite existing GPO", and done.
💪 1
n
Yeah, I just did that.
I mean, when I want to test something. It's a little more cumbersome to add to GPO, backup, import, test.
I'd almost just add it to WEM, test, then add to the GPO should I want to import later on.
o
yeah it's the price to pay I suppose
n
I don't make a ton of changes, so I'm probably just overreacting
o
the WEM console is not great for GPO editing. The columns won't adjust properly etc.
n
So I've noticed, lol
o
lol
n
Using WEM for the GPO basically gives me the same logon times as when I disabled User config in the GPOs themselves, which is good. Ultimately, I think my next step is to wait for my new hardware to be stood up, because that's going to be a huge factor.
I'd also like to use it as a baseline for any other changes I make.
I also wonder if I'll be able to unlink my IE GPO next month, since we're going to be enabling the setting that removes IE entirely. I don't see why those old IE settings would be relevant anymore.
Unless they're used for sites that load in IE mode, which would suck.
I also wonder if moving to Citrix Cloud (Azure most likely) is the better play for the long term. I have no idea what logon times are like there.
r
@Osiris Amanpour yea man, 60 seconds is bad. That is the new place I started. I will get them down to optimal performance in time.
@Nick Panaccio I think and I could be wrong but I think it may be hardware. I know you do good tuning. Anyway you could post the output from the Logon Analyzer?
a
speaking of IE, i know its apparently finally going away this summer and IE mode will continue to work (we use that as well) but for IE mode to function the IE 11 feature has to be enabled we found. i wonder if IE will still be there under the hood but the main program will be hidden now
n
I'd have to run it again. There was one or two AppX processes that took a little while to run, but everything else looked real good. This hardware is just bad. Not at all snappy, apps take too long to load, etc.
I bet it will be, becuase of IE Mode.
r
Yep I am thinking that is correct as well.
a
wish we could flat out ditch it though but still a handful of homegrown apps/sites we need to keep it for
r
The king of tuning is @James Rankin. I followed all his stuff and its damn GOOD.
👍 1
a
same here
n
We're removing IE next month and using IE Mode for the handful of sites that need it.
a
by removing do you mean disabling the IE11 feature?
n
Yeah, setting it via GPO.
j
Sub 10 seconds is possible, but do you really need it? I think I covered all of the factors around "good logon times" in my first article on the subject. "Aim for ten, accept twenty, don't go over thirty"
👍 2
a
i may be wrong but i could have sworn when i tested that a ways back (just manually disabling that feature in the control panel) made the IE mode feature stop working
n
Disable Internet Explorer 11 as a standalone browser
Nope, works fine for me
a
interesting! best we can do here is wait until MS forces our hand on it (which our group is happy about ) but we can use security as our reasoning this time
n
@James Rankin: IMO, no, we don't, but the clown who made the comment likes pushing dumb ideas.
a
@James Rankin thats the rule we go by here now for times too......i found that really anything between 10-20 still "feels" decently fast or at the very least made people stop complaining
n
My personal goal would be 20 seconds.
r
ahahah, Nick tells it like it is.
n
I still can't wrap my head around a 10 second logon to non-persistent Citrix.
a
i still dont fully know who to believe for actual times between Directory, ControlUP and WEM reports (WEM i know is notoriously high though )
r
I had 10 in my lab. But it was just FSLogix and WEM. Very basic
j
Best I've ever done is about 6 on a trader platform
So high-spec stuff everywhere
r
6 seconds, WOW
a
damn
r
yea big DAMN
n
Ignoring hardware, I also wonder how vanilla you have to get to achieve that.
My FSLogix stuff is on crazy fast Isilon flash storage, so I have no concerns there.
j
You need async processing for that though - so forget FSLogix unless you're using an old version. Not very vanilla to be fair, this was a complex solution
a
for those of you using WEM and fslogix, do you find Teams takes forever to launch at login? some of our basic dev vm's it loads much quicker so i know i need to narrow things down to whats different but i figure if thats slow to load i'm sure other login items are stuck waiting in line too
n
We don't set Teams to auto launch, but Teams loads slow no matter what, IME
r
I give up on teams, It just junk and I don't start it at log in at all.
n
It's a pile of shit
r
YEP
j
Yeah Teams blows goats
r
We have vGPU and it still sucks with Teams
a
100% with you guys there......sort of a pick your battles thing here w/ that one.
r
I love zoom, even though they had security issues in the past.
n
I want to at least use this whole debate to get a POC of Citrix Cloud, which we've been trying to do for years.
a
good to know! i just had noticed some vm's launch it much quicker than our main image so i'm sure theres some improvements i can make. hurts when we have some laptops now and people see how fast it loads on that
b
@Ray Davis you just ruined my day. Got my GPUs in transit now. Guess I can send them back 😂
j
I so WISH Teams had an option to make the "turn off incoming video" setting stick once selected. That's the main reason I get slowdowns in VDI, people's huge grinning melons appearing all over the session
😂 1
r
hahaha sorry @Bill Pennie. I just don't see any value with vGPU with Teams. Could be that I did it wrong lol.
j
vGPU only useful if you're not offloading IME
👍 1
But at least that means you can use "full" Teams
r
But again, I walked into a pile shit and I have to fix everything so, don't let my vGPU comment steer you.
n
Full Teams... I finally got my first ticket about a feature not being available in optimized Teams last week, ha
b
Yeah that was the idea. We need feature parity with the non machine wide installer.
a
haha thankfully everyone here has been used to the bastardized optimized version for a couple years here now so calls have stopped on that front
sorry didnt mean to hijack this thread with Teams rants 🙂
g
Is the turn off incoming video influenced by any reg values, cmd line argumnets, etc? I've got a prototype of something that can intercept the launch of teams.exe processes and modify the environment before it's allowed to run or change its parameters
r
I thought they were suppsed to redo teams. I remember reading somewhere about removing the eletron and replacing it with WEbview2
b
This thread is great. Thanks for starting it @Nick Panaccio
👍 1
💯 1
a
they did (we had a test version of it) but only worked for personal accounts i believe and was never planned to be for enterprise
n
No worries at all, this stuff works for me
a
i think it was more or less teams web with a shiny new coat but quicker
r
I wish I could sit down with the MS developers and ask them questions
n
Never planned for enterprise? That would be a huge blow...
ask them questions punch them in the throat
😂 1
a
ask questions, slap them in the face, whatever works lol
r
LMAO
a
hahah
i found a question on a MS page someone asking about teams 2.0 and the answer was that it has no current announcement but will be for the future
or its just their push for people to go to Windows 11 where its built in i guess?
r
Here is two keys that I been testing and they seem to load the the desktop fast. It stops the appx package from hogging the login. They still run, but it doesnt wait for them. REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer" /v AppReadinessPreShellTimeoutMs /t REG_DWORD /d "0" /f REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v DelayedDesktopSwitchTimeout /t REG_DWORD /d "0x1e" /f
I don't recommend running it prod as it just me testing. Nick I am wondering if it would help any in your testing?
a
interesting! so if we use App-V this would maybe help i wonder.......thats one thing that we dont have on our dev machines that tend to login quicker
r
I never used App-V, so I am not certain man.
a
no problem! that was going to be part of my testing (disabling those types of features 1 at a time to see what helps/doesnt but this will be good to test with too so thanks!
r
Yea man, no problem.
d
I played around with the reg keys @Ray Davis mentioned when dealing with a black screen phase before the desktop loads. This was with VDA 2112. You have to be careful because it can break the start menu search. A Timeout of 5 ms was the sweet spot in my environment and allowed to load the desktop without start menu issues. I never put it into production, because a clean install of VDA 2203 solved the black screen issue for me and logon times went back to sub 20 seconds. Just to make it clear, this is on non-persistent W10. From what I‘ve seen desktops on multi session OS usually load faster, about 10 seconds logon time. I guess it's because of prelaunched processes and missing APPX crap. So compare apples to apples, single session vs multi session OS makes quite a difference, unless you go with LTSC which comes close to server OS but probably nobody should use anymore for VDI these days.
n
You used the value of 5 for both of those?
I played around with the second setting a while back, but had weird results. We're going to 2203 this year, but I'm not sure if the others want to hold off until CU1 given how many issues we keep hearing about from others.
d
AppReadinessPreShellTimeoutMs set to 5
n
Do those need to be baked into the image, or can they be applied via GPO?
d
I baked them into the image.
n
I guess I could try trying them via GPO first so that I don't have to crack open the image and spend an hour waiting for Defender to seal it.
j
LTSC Windows 10 is a thing of beauty. Just did a deployment using it. Felt so clean
n
This is a dumb question, but Citrix has no actual cloud platform similar to Azure where you can build your own VMs, etc., right? I always thought they were just the management plane, and you used Azure, AWS, etc. for your actual VMs.
s
you talking something like this, where it's Citrix's azure subscription? https://docs.citrix.com/en-us/tech-zone/design/reference-architectures/citrix-managed-desktops.html
n
I guess that's the difference - Citrix's Azure subscription vs. your own. We're an E5 customer, and I assume it would make more sense to just handle the VM side ourselves.
s
yeah, i'd imagine so from a flexibility standpoint. Not sure if there is any type of network to network peering that is an option, for cases where you need to do Sentinel/SIEM or Special management agents or stuff like that.
vnet peering is an option to your existing azure environment, thats nice.
d
Citrix Cloud didnt add any seconds on our login
With Citrix Cloud we only use the management side, So pretty much the Controller and SQL and License server, the rest we manage in our own Azure Subscription. We run our own storefront servers and ADC
n
I mean compared to on-prem hardware/VMs
Trying to keep up with hardware is arguably the biggest obstacle
d
yeah, we gave up on own hardware 4-5years ago
n
Hmm, changing the reg values above to 5 each gave me a black screen for 2 seconds, but I could see the desktop in 20 seconds.
Apps were still loading in the background and all, but stilll...
s
it's all about the 'perception' not the reality 🤣
n
Yeah, I can see this leading to "but I can't do anything yet", lol
However, perception is the same on physical clients...
Changing the second value to 10, I'm at the desktop in 25 seconds with no black screen. Gonna walk that back to 7 and see if I can get to like 21-22 seconds of showing the desktop
r
Interesting.... so 5 gave you 2 seconds. 10 gave you instant .
I am going to try 10 now as well.
n
Yeah, which is why I think 7 may be the magic number for my environment.
r
yea, I am trying 7 now myself.
5 in my old environment was perfect. 5 in this environment I am in now, is black screen for 3-4 seconds. 7 is perfect. Shell loaded nice and no delay
n
Splitting hairs here, but I'm getting closer. 7 still had a black screen.
d
you might get 10sec on test user, and when you put it in prod, you will see anything from 8sec to 60sec
r
@Daniel Viklund that is true. I have seen that as well.
d
I think its impossible to have 10-15sec on every user account, you will always have a couple of bad apples.
n
So, using 8 as the desktop timeout seems fine for existing profiles, but for new profile creations, that leaves an 8 second period of just a black screen. I'm wondering if I should care about the new profile creation black screen.
s
i wouldn't care...imo
n
I'm going to see if setting it to 10 gets them both to behave the same. If not, I think I'm of the same opinion. First logon? Take a hike
s
yeah, and universally expected to be a little longer than subsequent logons
n
haha, tell that to my leadership...
b
That more ammo for the the Helpdesk to pre-load first logins 😉
n
Oh yeah, you can bet that I'm bringing that up. I think that's brilliant.
d
I‘d still try to completely remove your VDA with Citrix Cleanup Tool and afterwards re-install the VDA. Maybe be this brings down your logon times without all the tinkering.
n
App Layering... new VDA install every single time.
r
@dready Did you notice 2203 VDA seems to allow logins faster?
s
you try logging in without AV present at all too? Just to get an idea if maybe your missing any exclusions? Also, using Citrix optimizer?
n
Citrix Optimizer, yes. Running Defender, which I know for a fact was responsible for 5-10 seconds being added to our logon compared to Trend. Nothing I can do there, though.
r
Who needs AV lol?
n
I would have preferred a hypervisor based AV as opposed to running a client in the VM, but that wasn't an option.
r
I was actually just thinking that. I was wondering how it would perform at the hypervisor level.
n
And yes, all exclusions are applied.
👍 1
d
@Ray Davis I did not compare to 2112 directly, all I can say is removing 2112 and re-installing 2203 solved the black screen for me, while just upgrading to 2112 did not.
n
I'll be going from 1912 to 2203, though I am tempering my hopes about a faster logon experience from that alone.
Can't be disappointed if you expect the worst, haha
Which should really be Microsoft's slogan, now that I think about it.
r
@dready Thanks for the details. @Nick Panaccio The only things I would say is start from scratch. I know it sounds like a lot of work, and it is. Base Image, No GPO, Tuned and try it. Then start adding things one by one until you can see what it does.
n
I've thought about doing that, as I've upgraded W10 from 1709 to the now 20H2.
b
We used to use McAfee Move hypervisor based AV. We noticed a hit to the overall user experience. Everything that was offloaded to the scan server added extra ms in the user interaction. Was horrible.
n
I have never had a good experience with McAfee anything, so that doesn't surprise me.
💯 2
I would have tried Trend's solution, but they don't support XenServer.
d
BitDefender FTW
r
@Nick Panaccio new image for 20H2 right?
n
Nah, I always upgrade the OS in my OS layer
r
interesting, I wonder how many folks do in place upgrades?
n
Comes with the territory with App Layering, since all layers are linked to that one OS layer.
r
gotcha
a
us being persistent its different of course but we always do in place upgrades as well
n
@Ray Davis: Are you also using the FirstLogonTimeout registry value mentioned here? https://docs.microsoft.com/en-us/troubleshoot/azure/virtual-desktop/windows-virtual-desktop-blank-screen. I can't really find references to it on any Citrix forum.
r
No, I never seen that one lol. Need to read about that more.
n
I couldn't really find anything on it outside of that one link. Another mystery key from MS.
r
Says Azure Virtual Desktop, but these keys still work on prem
n
Yeah, I found plenty of references to the other keys on Citrix's forum and elsewhere.
a
I'm gonna have to go and see if we're using that one now. it sounds vaguely familiar
28 Views
Open in Slack
PreviousNext
Powered by