This message was deleted.

We have a customer who precreates profiles on their 4 citrix servers for all 400 employees, whats wierd about that?

Pre-creates them with settings saved somewhere?

Precreates them by logging the users on and setting up a local profile on each server and configuring things for them (like Outlook to cache).I was trying to convince them it was rather bonkers

lol, what?

It sure is.

Tell them that all of us think that's insane.

Its only for new employees

And when they hit a different server of the four??

Well the have a precreated profile on there too

But without any of the customizations they may have made on Server A.......OK, whatever floats their boat

what

Persistent multi-session looking good now?

Nah, that sounds dumb, too...

Fair 😛

Aren’t AVD session hosts using Windows 10/11 Multi-session essentially persistent by default? By persistent I mean restarting the session host doesn’t revert it back to a known state.

Ha ha, exactly what AVD is 😂 my next project I'm recommending that they pre create profiles on every box, an then we have a "Clever" trigger with auto scaling and a runbook to do that whole process every time a machine boots up. Whilst I explain all that I'll have the cat filter stuck on so I can be taken totally seriously.

@Nathan Sperry abso-friggin-lutely. One my biggest bug bears is the term non persistent in AVD… sessions might be non persistent, but the hosts are 100% persistent - RDS in the cloud baby

In the AVD world, most use persistent VMs which I agree is not ideal especially for multi sessions. Not every one that setup AVD have a VDI background therefore they are not even familiar with non persistent vms.

By persistent I mean with the profile and user changes persisted locally

It’s the norm for a lot of traditional smaller RDS native environments. It’s only in the established VDI world with Citrix and a like, do people question it. In some environments you don’t need profile “roaming” if you’re using a single LOB published app. However I don’t know what context MS we’re using persistent in, but the marketing message can be strange at times

Yeah I always make sure to have a slide in my presos that makes the distinction between "dedicated and pooled" (for machines) and "persistent and non-persistent" (for profiles). Not sure what MS's intent was

To be honest, persistent desktops just require maintenance but that depends on your provisioning method and how you handle rebuilding them. If you rebuild regularly its all good. On a side note, FSLogix seems to have been a little hit-and-miss lately, I've been seeing some serious weirdness with the later releases. General rules of thumb, no errors in the logs and configured as expected its a bug. Logging issues with MS support is a joke.

Logging issues with MS support is a joke. FTFY