Best Practices Question
Error when capturing an image of a VM with k2000
I am using a K2000 3.6 and Hyper-V Manager
When i try to capture an image (WIM) I get an error that there is not enough disk space to perform the action. I dont give my vm's much more space than they need, so I assume that the temp files can not be written to the disk as a result of this.
My intent is to add a second hard drive in the vm settings to allow for this as i believe windows will automatically check for space other than the current partition(s) it is capturing.
The second hard drive would point to a "Temp" directory I could use for all of my vm's when capturing to the k2000
Is this what is best practice? I have read and watched best practices for golden images etc, but nothing goes into any setup for this part of imaging that i have seen, only to use vm's.
I want to minimize the space that my vm's are using and only use the temp directory when i capture my updated vm to kace.
Any help or thoughts are greatly appreciated.
Answer Chosen by the Author
So, I was able to create a second HDD / VHD with enough disk space to allow for the temp files that is used when capturing an image in case (WIM). By doing this, is can add and remove as needed. Again, I only work with one image at a time, so the "Temp Drive" and be used for multiple VM's only when I am ready to capture and image.
This keeps my disks space at a minimum which meets my requirements. Best practice? Maybe lol, works for me.
Answered 06/25/2015 by: