Anand Mohan Eluri: Work with disks with out drive letters

When we set up a cluster of virtualization is commonly used CSV to have more than one VM per LUN (disk).

However there are situations where we prefer to dedicate one or more disk LUN to a VM on grounds of privacy, control, performance, a software requirements, etc..
On these occasions if we give each disk a drive letter you will find that when the cluster comes to have many such cases, we will run out of drive letters.
For quite some time and of course Windows clusters let us work with disk drives that have no letter.
When a unit has no lyrics, accessed by a unique identifier we call GUID.
There is a misconception that to work without drive letters is necessary to set the volume with the formatting style GPT partition instead of MBR, say that this is false and that except for Itanium-based machines must leave the formatting style GPT partition for those volumes that will have more than 2TB.

For a letter volume has not only have to remove it or not allocated during creation.

For me the volume label is very important in a cluster is a key tool to have traceability records from all the tools, soil advise if it is a SAN disk turn your same tag you've used in the SAN, if it also is a label that gives us added information for the better, such as SAN in the next, the type of records, etc.
Well, you have created the disk, now as accedéis?, From the disk manager will see that you can not open the drive, if you go to explorer the drive does not come out.
Powershell y ejecutar el siguiente comando: To open the drive the first thing you need is to know the GUID for this show Powershell and run the following command:
“gwmi win32_volume|where-object {$_.filesystem -match "ntfs"} |fl Label, name”

Excecute the command:
"Gwmi win32_volume | where-object {$ _.filesystem-match" ntfs "} | fl Label name"