Will this work with non persistent VDIs?
“It Depends”, that could mean a lot of different things. In practice it’s been complicated for several customers, you may have to do some experimentation and it’s still prone to some duplication if any of the moving pieces don’t work together.
This article depends on the client having the same identity when it is restored - which is more than hostname/IP address, it needs to have the same SID and SCHANNEL encryption identities. In practice Citrix PVS meets this, but I’m not sure about other solutions.
What has worked for some with Citrix PVS, is to install BESClient to persistent storage, change the BESClient service startup to manual, and setup a Shutdown script to stop the BESClient service, save off the registry keys and keystorage folder listed in that article.
Then a startup script that waits several minutes for the Citrix PVS service to restore the machine identity, then restore the BESClient registry keys and __Keystorage folder listed in that article, and start the BESClient service.
If you’re using another VDI service I’d like to hear how the experience goes for you and the details on your configuration.