First I gotta say.. Writables are the DEVIL . Man have they created so many issues for us .,
It sounds like the problems increase the more one jumps from pool to pool..
If i create a vPGU pool.. i generally dont create a whole new ID to test the pool w/.
I log into it and my writable follows.. and then corrupts most everything.. so nothing works eventually :smileysilly:. At least that's my hypothesis .
Deleting the Writable generally fixes the issue.
Im engaging the option now where my writable will only attach to certain computer names / pools.. thus it should only attach if im on a certain pool .
Granted would be nice to have it attach to my vGPU pool as well.. for better testing perhaps .
I was curious if one could have a different Writable per Pool.. for the same person . The ToolTip sorta implies the possibility .
Is it just as simple as Creating a new App stack for a user that already has one.. and changing the "Limit Attachment" to a Unique / different pool ?
That is how I test new appstacks and instant-clone updates. I have 2 profile-only writable's assigned to my user account, one using mount prefix for the TEST pool vm's, and the other mount prefix for the production pool vm's.
As stated by whibr the only way to do that is to add a Machine name prefix to the writable. Theoretically you could create a much writables for a user as you would like to as long as the prefix is different all the times, otherwise it won't create it because it says the file already exists.
You could also disable the writable while testing, might be an option?
And yes, writables are both heaven and hell, it takes quite a lot of work to maintain them, I really depends on your use case to be honest. I think you should not give a writable to anyone (although that's what were doing ). For developers it is very very nice. Or for classes in which students must be able to install software for a specific class..
Thanks Everyone. Appreciate the assistance .
I think were moving to what you stated Ray ... Not giving a user a Writable by default .. just as needed .
We have all but deleted them all for I.T. .. us jumping to different pools has caused more than enough issues .
Granted this doesnt offer a great test environment..
thanks for the help everyone .