I am 99% done testing an Instant Clone VDI pool that does not use any writable volume, DEM only, and has 100% user persistence. The new Default App & FTA captures were the final missing piece, until....
We no longer have UI Visual performance settings staying persistent. When we used a writable volume, we set it once for a new user and it stayed for each new logon. (Control Panel > System > Advanced Settings > Performance) Now, even though we have a DEM profile to add the proper settings via RegKey, the registry changes happen after the desktop visual settings are applied at logon. I have tried a scheduled task on the root image to change the regkeys at logon, but again, the change happens too late in the desktop creation to matter. A user cannot change the settings manually without admin rights and they won't have those.
Does anyone know method of defining those settings for all users? My dev team is trying to build a .exe that executes a change to the settings, but outside of that, there doesn't seem to be anyway to set it that does not require a restart of the PC. Once it restarts, we are back to square one.
A user cannot change the settings manually without admin rights and they won't have those.
DEM can only apply settings in locations that the user has permissions to, so how exactly have you configured that "DEM profile to add the proper settings via RegKey"?
And, just to make sure, are these the settings you want to persist:
You can set the performance settings using OSOT by editing the template you are using. Run OSOT during image creation and this setting are present in your base image!
Upon a lot of additional testing, the OSOT only allows some of those settings to be base-lined.
We were able to create a .exe that changes those settings and actually changes them on a live desktop. We placed that .exe on the Golden Image in a hidden Scripts folder (this is the 4th script we have had to create) and then call it after the user profile is complete. The .exe. does not need admin rights to run.
Beyond that, we had to abandon the test because several mission critical applications will not stay persistent without a writable volume. Importing the reg keys an AppData later in the boot process doesn't work for them.
Closer, but still not ready to ditch writables for us.