Separate disk for OperateITData and OperateITTemp folders in a virtual environment
1. Does this recommendation also apply to virtual environments?
2. Does anybody had performance issues with OperateITData and OperateITTemp folders on the same disk with the operating system?
3. Is it possible to move these folder to another disk in a running system?
I agree with previous answer, the benefit of separating the OperateITxxxx folders from C:\ is less in a virtual environment where you likely have other factors affecting the actual separation.
Still, a separate data disk have less risk of running full or becoming negatively influenced from what takes place on C:\
Moving can be done from SCC which will take care of suspending dependent services during transfer. Please note that cleanup of the old location is a manual effort (not automated due to the risks of a failed transfer). Manual move is also possible; the path is stored in Windows Registry and in the Service Definition aspect. Topic touched in past AKS threads and documented in my System Health Check manual (occasionally attached on AKS threads). NOTE: never move OperateITTemp\FsdCache when VB6 is used, then omit/skip copying that subfolder to force the FSD Client to download and register the VB6 .ocx files at the new location.
I recommend always applying PNSM's Basic Computer Monitoring to keep a watch on the C:\ and the additional (optional) disk partition where you have moved the OperateITxxxx folders.
Most important of them all, never use disk snapshots in production environment, or only for very short durations (eg during a System Installer "deploy" action or installation of new SW as a quick way out if the installation should derail royally; still a full cold disk image is always a better option).