NAZ1000

<div>
What I had thought but thank you for the confirmation.<br><br>
</div>


<div>
In the VM environment, always add disks and do not create partitions.
</div>


<div>
<div class="content wysiwyg-content fr-view">
Replacing a failed physical File Server with a new Host, Running a VM as the file server.<br><br>Is it better to create the VM , and add a data drive to this in HyperV, or add the data in the VM itself in subfolder /&nbsp; partition ?<br><br>If data drive is best then should it be of type shared ?<br><br>
</div>
</div>



Replacing a failed physical File Server with a new Host, Running a VM as the file server.
Is it better to create the VM , and add a data drive to this in HyperV, or add the data in the VM itself in subfolder /  partition ?
If data drive is best then should it be of type shared ?

Best Practice for HyperV Disk Creation

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

Virtualization

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.