Update: i have renamed this post to better represent the content.
All our users have 1 Writable Volume for OST and Search storage and a few Appstacks.
The Writable Volume is configured (snapvol.cfg) with the following entry:
#virtualize=\
Registry virtualization has been removed.
And the rest is the default snapvol.cfg + extra exclusions for virusscanner.
And using UEM/DEM we configured the OST to be placed on the writable volume.
This way we thought it would not virtualize the complete disk and only virtualize the paths we want, and it looked like this was working fine. Till now...
We now see stuff appearing inside the writable volume. Partly it's my fault not picking this up before. I wasn't looking at the right locations when testing this setup in our test environment and i thought everything was working as planned.
Our usecase is very simple. Writable Volume is used to store the OST and Search database and nothing else. The user profile part is managed using UEM/DEM.
Thats part 1 of the challenge we are facing; "How do we realize this usecase?" We thought we had this covered, but is seems we didn't.
Part 2 is that i need some more info on the relationship between Appstacks and Writable Volumes.
I did some testing with the following snapvol.cfg for my writable volume:
exclude_path=\ProgramData\
exclude_path=\Users\
exclude_path=\Windows\
exclude_path=\Program Files (x86)\
exclude_path=\Program Files\
When i use this snapvol.cfg for my writable vol and attach one or more appstacks as well, this isn't functioning like i was expecting.
I see that the folder structure from the appstack is visible in my file system, but the data is not accessible. That makes me think the processing of the appstack is influenced by the configuration of the writable volume. But both the appstacks and the writable volumes have there own snapvol.cfg. So that made me believe they are processed independently. My testing is indicating otherwise.
Can someone clearify this behaviour?
And maybe help me to correct our setup so it complies with our usecase; "Writable Volume is used to store the OST and Search database and nothing else"?