search

MicrosoftDocs / windows-powershell-docs

This repo is used to contribute to Windows 10, Windows Server 2016, and MDOP PowerShell module documentation.
Creative Commons Attribution 4.0 International
446 stars 599 forks source link

-PhysicaldiskIds parameter #2006

Closed stephc-msft closed 3 years ago

stephc-msft commented 4 years ago

Server2019 has -PhysicalDisk and -PhysicalDiskGuid options

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

MaratMussabekov commented 4 years ago

Hello, @stefanie-msft , i've made some research, and found out following:

  1. as it was already mentioned, PhysicalDiskIds parameter was replaced by PhysicalDisk and PhysicalDiskGuid. PhysicalDisk accepts values of CimInstance#MSFT_PhysicalDisk class (it is a class of output of Get-PhysicalDisk cmdlet), and PhysicalDiskGuid accepts GUID strings. These parameters cannot be used with each other.
  2. Also, it has a new Reset parameter (without value)
  3. There is also CacheUsage parameter, that accepts following values: NonHybrid, Capacity, Cache, Auto

So, the syntax is following:

Set-ClusterStorageSpacesDirectDisk -PhysicalDiskGuid <string[]> [-CanBeClaimed <Boolean>] [-Reset] [-CacheUsage {NonHybrid | Capacity | Cache | Auto}] [-CimSession <CimSession[]>] [-ThrottleLimit <Int32>] [-AsJob] [-WhatIf] [-Confirm] [<CommonParameters>]
Set-ClusterStorageSpacesDirectDisk -PhysicalDisk <CimInstance#MSFT_PhysicalDisk[]> [-CanBeClaimed <Boolean>] [-Reset] [-CacheUsage {NonHybrid | Capacity | Cache | Auto}] [-CimSession <CimSession[]>] [-ThrottleLimit <Int32>] [-AsJob] [-WhatIf] [-Confirm] [<CommonParameters>]

Dear @e0i, would it be possible to contact the author of the article. It needs to be rewritten, as syntax, examples and parameters sections are incorrect? I cannot do it myself, as information about these parameters is not available in public sources.

Thank you

o0nj commented 4 years ago

Server 2019 content is not covered yet. Thank you.

MaratMussabekov commented 4 years ago

Hello @e0i, then we should just ignore it? Should I just close my PR? Thank you

MaratMussabekov commented 3 years ago

Hello @e0i, may be I should add a note that WS 2019 is not covered yet? can we ask article owner about it? Thank you