once upon a time, I was in a citrix admin training, and I remember there was a topic on mcs and how changes on disk are kept or not.
I remember the workshop was if we reboot the vm hosted on vmware through the start menu, changes were kept, all changes are stored until we shutdown or reboot the vm through the studio console
I've seen behaviour is different with vm hosted on azure provisonned with mcs
what settings should I set if I want to keep this behaviour ?
because I've tested different setting (new vm created from scatch after updating the Machine catalog, mcsio is enabled), I've tested non persistant write cache enable, but it has no disk assigned, even if there is a cache disk ? temp disk and cache disk are different ?
Question
_XD_
Hi everyone
once upon a time, I was in a citrix admin training, and I remember there was a topic on mcs and how changes on disk are kept or not.
I remember the workshop was if we reboot the vm hosted on vmware through the start menu, changes were kept, all changes are stored until we shutdown or reboot the vm through the studio console
I've seen behaviour is different with vm hosted on azure provisonned with mcs
what settings should I set if I want to keep this behaviour ?
because I've tested different setting (new vm created from scatch after updating the Machine catalog, mcsio is enabled), I've tested non persistant write cache enable, but it has no disk assigned, even if there is a cache disk ? temp disk and cache disk are different ?
thanks for your explanations
Xavier
0 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now