I also assumed this was a test of persistent vdi.
# microsoft-avd
j
I also assumed this was a test of persistent vdi.
j
well.. eventually it'd be fslogix, etc.. but for right now, I don't have that set up. thats all on prem at the moment. My goal would be to ensure that users can run zoom/teams/google meetings within the AVD session, etc. Right now they have zoom installed on their local pc, but do 99% of their work within the RDS server, where zoom isnt allowed to run.
j
Ah ok use we fslogix on Azure files for shared hosts but not persistent as no real benefit in persistent that I see. Users mainly store files in dfs shares or gits anyway. We do have users in shared pools using office and teams without complaints (well major issue complaints). Teams needs to be using slimcore version, especially if across an ocean.
j
I might move my profile vhdx file up to azure files just to test out fslogix, as thats the end-game, and just to see how it all works. but yeah I'd have to set up a vpn back on prem to access local files, map drives, etc. See how slow things would be
im scared of the cost of doing all this.. lol.. too many unknowns
j
Well we are seeing it be very cost effective so far well under budget and users like it much more than previous on prem horizon vdi. There are of course some issues coming up mostly login confusion due to our odd setup security wanted. We only cut over all users about 6 weeks ago. But some growing pains on load balancing and host availability in shared pools. Just not as elegant as ICA there. Also previously all users were a vdi so a little learning curve for admins moving to shared pools
j
how many users?
and what exactly are you using, if I may ask.. you're using d4as v5 with how many users per host?
j
Right now im at 212 users. We have 20 share host pools, 3 persistent.
Have mabe 30 -50 offshore users overnight
j
thats about the same size.. we're probably around 250 or so. 20 share host pools.. does that mean 1 host pool with 20 vm's?
im learning the lingo 🙂
j
Host pools is like a delivery group
So no it is 143 host spead between those. We have some with only 2 hosts. They are chopped up for tagging things for cost tracking.
Some shared are d8s some d4s some use depth first some use breadth first load balance. Just depends on the team, etc.
j
143 hosts?!?! wowwww
thats like a host per user almost 🙂
j
Well we do an odd double hop vdi for privileged users. Some some pool doubling due to that security setup. We are not a fan but some alternative solutions we just didn't have time to work out within deadline.
j
im not questioning your setup 🙂 just trying to figure out how/why and how it'd relate to me
currently, we have 7 on prem RD session host VMs, they each have 10vcpu / 128GB ram, and have about 30 users each on them. Too many.
I have to wrap my brain around many more hosts with less users per host..
j
Users have to login with regular to shared vdi, then launch from that internal ip'd session with privileged creds to a persistent or shared vdi depending on team. It is kind like the old store front double hop. Very secure but we want to solution a more efficient setup eventually. Still under budget and we'll under horizon lisense renew/cluster refresh. And users do say performance is way better. So is odd but good.
Yeah we see on shared app w d8 v5 and max of 14 users a server. Then avd wants another host.
We do have some e8bs v5 pools getting 20 users per host if looking to higher density.
j
i dont think it really costs much more to run a bunch of hosts, right?
vs fewer, larger hosts
j
Yeah it varies from sku in each region so need to look for your region.
j
geez.. MS denied my request for d8 quota 😞
j
That is odd
j
apparently west us 2 is the issue
👍 1
folks are recommending just using W365 instead of AVD.. but man that seems like it'd be so expensive without utilizing multi session hosts, etc
j
Yeah no control in W365 and no muti session
W365 is a desktop you manage from 365 and don't see in Azure. Itis only persistent and completely managed by MSFT. So if your organization wants different patch schedule, custom agents, etc. You cannot do that. Also far more limited in sku size and unless something changed no gpu support.
It's ok for basic use in smaller environments, bigger enterprise with developers not as much
j
they do have GPU options now. I feel ilke w365 could be good for our small prorgramming folks or people who arent regular users. Currently we have PCs on prem that they access.. first they VPN in from their home computers (we dont manage those) and then they RDP into their physical desktop at the office. W365 might be a good thing to replace those with
i tested with setting up a site to site vpn with azure <> meraki and it worked great.. w365 spun up, hybrid joined to on prem AD, mapped drives, etc.. but know thats frowned upon nowadays