New-MSDSMSupportedHW
Syntax
New-MSDSMSupportedHW
[-VendorId] <String>
[-ProductId] <String>
[-CimSession <CimSession[]>]
[-ThrottleLimit <Int32>]
[-AsJob]
[<CommonParameters>]
New-MSDSMSupportedHW
[-AllApplicable]
[-CimSession <CimSession[]>]
[-ThrottleLimit <Int32>]
[-AsJob]
[<CommonParameters>]
Description
The New-MSDSMSupportedHW cmdlet creates a new hardware identifier (ID) with a specific vendor ID and product ID combination in the Microsoft Device Specific Module (MSDSM) supported hardware list.
Unlike MPCLAIM.exe, when you specify the vendor ID and product ID, do not pad the fields with spaces.
The Update-MPIOClaimedHW cmdlet must be run to have the Multipath I/O (MPIO) claiming process take effect.
Examples
Example 1: Add a hardware ID
PS C:\> New-MSDSMSupportedHW -ProductID "VendorX" -VendorID "ProductY"
This example adds a hardware identifier with vendor ID of VendorX and product ID of ProductY combination in the MSDSM supported hardware list.
Example 2: Add all applicable hardware IDs
PS C:\> New-MSDSMSupportedHW -AllApplicable
This example finds all applicable devices and then adds corresponding hardware identifiers to the MSDSM supported hardware list. Applicable devices are those that are connected to the system by using Fibre Channel, iSCSI, or SAS.
Required Parameters
Specifies that all applicable devices that are connected to system by using Fibre Channel, iSCSI, or SAS, are added to the MSDSM supported hardware list.
Type: | SwitchParameter |
Aliases: | All |
Position: | Named |
Default value: | None |
Accept pipeline input: | True (ByPropertyName) |
Accept wildcard characters: | False |
Specifies the product ID.
Type: | String |
Position: | 1 |
Default value: | None |
Accept pipeline input: | True (ByPropertyName) |
Accept wildcard characters: | False |
Specifies the vendor ID.
Type: | String |
Position: | 0 |
Default value: | None |
Accept pipeline input: | True (ByPropertyName) |
Accept wildcard characters: | False |
Optional Parameters
Runs the cmdlet as a background job.
Use this parameter to run commands that take a long time to complete.
The cmdlet immediately returns an object that represents the job and then displays the command prompt.
You can continue to work in the session while the job completes.
To manage the job, use the
*-Job
cmdlets.
To get the job results, use the
Receive-Job
cmdlet.
For more information about Windows PowerShell® background jobs, see
about_Jobs
.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.
Type: | CimSession[] |
Aliases: | Session |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Specifies the maximum number of concurrent operations that can be established to run the cmdlet.
If this parameter is omitted or a value of
0
is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer.
The throttle limit applies only to the current cmdlet, not to the session or to the computer.
Type: | Int32 |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Inputs
None
Outputs
None