Persisent and volatile on same OS image, but different device groups?

I would love to have the option to have both persisent and volatile devices on one single image, are there any downsides which make it less likely to get implemented in future versions?

Please contact your Dell Wyse Sales team to justify the business case and they will follow up with Product Management.

I would love to have this option.  The business case for this is that I have some clients that need to act as if they have a harddrive and be able to store user information but I also have classroom labs that need to be reset after every user or at least at the end of the day.  I want to save space on my servers so having a single image to stream but allowing it to be both persistent and volatile depending on the group would be ideal.

An OS Image

• can have only one Write Cache mode set at a time
• is assagned to a Device (Group), but not a User (Group)

There are two options that could probably help in this scenario:

• For the OS Image itself: copy the exiting OS Image, register with a new name and use this with a different write cache mode.
• For the User Profile: you can have User Profile Layering feature of WSM 8.6. It seperates the User portion from the OS, can be set to volatile and persistant cache mode which is seperate from the write cache of the OS Image.