AVD Truly Non-Persistent
We have an environment where there are machines available for public use (a public library). Users should be able to create documents and the like on the machine, and save them to locally attached storage, or e-mail/cloud storage, etc.
When a user logs out, the machine should completely reset; all changes made, documents created, history, and the like should be erased and the machine should automatically reset to the base image.
Everything in the MS documentation I can find that mentions non-persistent machines just means pooled machines, which doesn’t do this. If I want to set up an AVD pool that does this, how would I accomplish that?
We have an environment where there are machines available for public use (a public library). Users should be able to create documents and the like on the machine, and save them to locally attached storage, or e-mail/cloud storage, etc. When a user logs out, the machine should completely reset; all changes made, documents created, history, and the like should be erased and the machine should automatically reset to the base image. Everything in the MS documentation I can find that mentions non-persistent machines just means pooled machines, which doesn’t do this. If I want to set up an AVD pool that does this, how would I accomplish that? Read More