This message was deleted.

Possibly. Could still be persistent machine with just profile deletion though. Also only covers the profile, not resetting the machine.

Non persistent isn't really anything to do with profiles. It just means the machine loses any changes made to it when it restarts. For example, with Citrix MCS single user non persistent machines, they restart whenever the user logs off back to the clean imaged state.

Microsoft play this card when using non-persistent terminology in AVD which has no native non-persistent capability in a traditional sense.... Traditionally we associate "non persistent" with machine level changes. At the end of a session the machine is wiped, and reset. Microsoft don't have this in RDS in the Cloud AVD and tend to refer to the ability to attach and remove a user profile as achieving non-persistence - the host is always persistent unless 3rd party tooling or automation is in the mix to destroy/recreate the instance

@James Kindon so when dealing with AVD and RDS and attaching and removing the profile do you treat the enviro as non persistent and follow non persistent recommendations or do you ignore them as it’s truely not non persistent ?

It depends in what context/items you are looking at specifically? By their very nature, a persistent machine is a persistent machine - so if you were looking at Antivirus configurations for a dumb example, you wouldn't typically follow non-persistent guidance there, but lots of "non-persistent" guidance can be applied to persistent hosts - just depends on the context of the ask 🙂

There is non-persistence as in "provisioning non-persistence" (machine reverts to clean state on reboot) and non-persistence as in profile non-persistence (profile is cleared at logoff but saved somewhere and restored at logon to a new "clean" machine)