You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Details of the scenario you tried and the problem that is occurring:
We are currently using the xStorage 3.4.0.0 module with the xDiskAccessPath resource within Chef to mount disks to a folder path. This works fine however on reboot the mounted disks are also assigned drive letters. Looking at native PowerShell there is an option like Set-Partition -NoDefaultDriveLetter $true and I was wondering if there is an option to ensure no drive letters are assigned when using DSC.
The DSC configuration that is using the resource (as detailed as possible):
Hi @IcedGoblin - thanks for raising this. This does sound like a switch we could add.
My question for the community: Should this switch default to "True"? E.g. should a drive letter be prevented from being assigned to the disk when using the DiskAccessPath (note: xDiskAccessPath has been renamed to DiskAccessPath in StorageDsc).
I vote for using the default $true, do not assign drive letters. I would think that if you want to use mount points, one reason is that there will potentially not be enough drive letters for the disks, meaning there will not be enough drive letters for all mount points.
Details of the scenario you tried and the problem that is occurring:
We are currently using the xStorage 3.4.0.0 module with the xDiskAccessPath resource within Chef to mount disks to a folder path. This works fine however on reboot the mounted disks are also assigned drive letters. Looking at native PowerShell there is an option like
Set-Partition -NoDefaultDriveLetter $true
and I was wondering if there is an option to ensure no drive letters are assigned when using DSC.The DSC configuration that is using the resource (as detailed as possible):
Version of the Operating System and PowerShell the DSC Target Node is running:
Windows Server 2012 R2
PowerShell 5.1
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
The text was updated successfully, but these errors were encountered: