Jump to content
Posted 23 April 2012 - 11:18
Posted 23 April 2012 - 12:48
Posted 23 April 2012 - 13:09
A *default location* is generally the first place that an operating system (desktop or server) looks for things. It's no different in Hyper-V (or Windows Server 2K12) than in VirtualBox, VMware, Windows 8, or even Windows 7. This can be changed at VM-creation time (example - private VMs that you don't want shared at all); again, like any of the products I outlined above. That particular choice is because the default settings are for shared (public) VMs (hence that default location two levels down in the Public folder).
I'm curious as to the reasoning behind a default setting in Hyper-V server. When you initially configure the role, it lists the location of virtual hard disks. The default location it gives you is c:\Users\Public\Documents\Hyper-V\Virtual Hard Disks.
This seems like a slightly weird choice to me. Why did they make that the default location? Does it have to do with shared access to VMs? What benefits does putting them there provide?
Posted 28 April 2012 - 02:01
Posted 05 December 2012 - 22:31
Thanks for the replies and info. The Public user folder still seems an odd location for any OS to use as its default location to me, but I can accept it i suppose. I'll probably move the location to the root of C instead for now, until I see a benefit in the default.
As for the performance of Hyper-V vs others in running an XP vm. I think it's rock solid. I've installed and used Hyper-V as a role on 2 different servers with very different hardware, and they both perform(ed) very well when accessing them from the local machine and remote machines as well.
I've also used vmware and virtualbox, and am a lot more familiar with them. But Hyper-V seems very configurable and straightforward.
Posted 07 December 2012 - 05:37