New-SCVirtualScsiAdapter

Creates a virtual SCSI adapter on a virtual machine, virtual machine template, or hardware profile used in VMM.

Description

The New-SCVirtualScsiAdapter cmdlet creates a virtual SCSI adapter on a virtual machine, virtual machine template, or hardware profile used in a System Center Virtual Machine Manager environment. After you create the virtual SCSI adapter, you can use the Set-SCVirtualScsiAdapter cmdlet to modify its settings.

Note: Using the ShareVirtualScsiAdapter parameter to share a virtual SCSI adapter on a virtual machine in order to enable guest clustering is supported only if the virtual machine is deployed on an ESX host. The SharedVirtualScsiAdapter parameter is not used for a virtual machine on a Hyper-V host because a virtual machine on a Hyper-V host uses iSCSI for shared storage.

A virtual machine on a Citrix XenServer host always has one virtual SCSI adapter. You cannot remove this adapter or add additional adapters.

For more information about New-SCVirtualScsiAdapter, type: "Get-Help New-SCVirtualScsiAdapter -online".

Parameters

AdapterID

Required? false
Accept Pipeline Input? true (ByValue)
Position? 0
Specifies the logical unit number, or LUN ID. Hyper-V and XenServer do not expose this value, and it cannot be changed. For a VMware ESX host, the default is 7 and cannot be changed. 

HardwareProfile

Required? true
Accept Pipeline Input? true (ByValue)
Position? named
Specifies a hardware profile object.

JobVariable

Required? false
Accept Pipeline Input? false
Position? named
Specifies that job progress is tracked and stored in the variable named by this parameter. 

PROTipID

Required? false
Accept Pipeline Input? false
Position? named
Specifies the ID of the PRO tip that triggered this action. This allows for auditing of PRO tips.

RunAsynchronously

Required? false
Accept Pipeline Input? false
Position? named
Indicates that the job runs asynchronously so that control returns to the command shell immediately. 

ScsiControllerType

Required? false
Accept Pipeline Input? false
Position? named
Specifies a SCSI controller type. Valid values are: DefaultType, NoType, LsiLogic, BusLogic, ParaVirtualSCSI, LsiLogicSAS.

ShareVirtualScsiAdapter

Required? false
Accept Pipeline Input? false
Position? named
Specifies that a virtual SCSI adapter will be shared so that it can be used in guest clustering.

 TYPE OF HOST		USES THIS PARAMETER
 ------------		--------------------
 Hyper-V host		No  (for guest clustering, use iSCSI storage)
 XenServer host  No  (Xen VMs always have exactly one SCSI adapter)
Note: When sharing a SCSI controller on a virtual machine on an ESX host, VMM defaults the SCSI sharing policy on VMware to "physical."

Synthetic

Required? false
Accept Pipeline Input? false
Position? named
Specifies that a device, such as a virtual network adapter, on a virtual machine deployed on a Hyper-V host is a high-performance synthetic device. Requires a virtualization-aware guest operating system on the virtual machine.

VMMServer

Required? false
Accept Pipeline Input? true (ByValue)
Position? named
Specifies a VMM server object.

AdapterID

Required? false
Accept Pipeline Input? true (ByValue)
Position? 0
Specifies the logical unit number, or LUN ID. Hyper-V and XenServer do not expose this value, and it cannot be changed. For a VMware ESX host, the default is 7 and cannot be changed. 

JobGroup

Required? true
Accept Pipeline Input? false
Position? named
Specifies an identifier for a series of commands that will run as a set just before the final command that includes the same job group identifier runs. 

JobVariable

Required? false
Accept Pipeline Input? false
Position? named
Specifies that job progress is tracked and stored in the variable named by this parameter. 

PROTipID

Required? false
Accept Pipeline Input? false
Position? named
Specifies the ID of the PRO tip that triggered this action. This allows for auditing of PRO tips.

RunAsynchronously

Required? false
Accept Pipeline Input? false
Position? named
Indicates that the job runs asynchronously so that control returns to the command shell immediately. 

ScsiControllerType

Required? false
Accept Pipeline Input? false
Position? named
Specifies a SCSI controller type. Valid values are: DefaultType, NoType, LsiLogic, BusLogic, ParaVirtualSCSI, LsiLogicSAS.

ShareVirtualScsiAdapter

Required? false
Accept Pipeline Input? false
Position? named
Specifies that a virtual SCSI adapter will be shared so that it can be used in guest clustering.

 TYPE OF HOST		USES THIS PARAMETER
 ------------		--------------------
 Hyper-V host		No  (for guest clustering, use iSCSI storage)
 XenServer host  No  (Xen VMs always have exactly one SCSI adapter)
Note: When sharing a SCSI controller on a virtual machine on an ESX host, VMM defaults the SCSI sharing policy on VMware to "physical."

Synthetic

Required? false
Accept Pipeline Input? false
Position? named
Specifies that a device, such as a virtual network adapter, on a virtual machine deployed on a Hyper-V host is a high-performance synthetic device. Requires a virtualization-aware guest operating system on the virtual machine.

VMMServer

Required? false
Accept Pipeline Input? true (ByValue)
Position? named
Specifies a VMM server object.

AdapterID

Required? false
Accept Pipeline Input? true (ByValue)
Position? 0
Specifies the logical unit number, or LUN ID. Hyper-V and XenServer do not expose this value, and it cannot be changed. For a VMware ESX host, the default is 7 and cannot be changed. 

VMTemplate

Required? true
Accept Pipeline Input? true (ByValue)
Position? named
Specifies a VMM template object used to create virtual machines.

JobVariable

Required? false
Accept Pipeline Input? false
Position? named
Specifies that job progress is tracked and stored in the variable named by this parameter. 

PROTipID

Required? false
Accept Pipeline Input? false
Position? named
Specifies the ID of the PRO tip that triggered this action. This allows for auditing of PRO tips.

RunAsynchronously

Required? false
Accept Pipeline Input? false
Position? named
Indicates that the job runs asynchronously so that control returns to the command shell immediately. 

ScsiControllerType

Required? false
Accept Pipeline Input? false
Position? named
Specifies a SCSI controller type. Valid values are: DefaultType, NoType, LsiLogic, BusLogic, ParaVirtualSCSI, LsiLogicSAS.

ShareVirtualScsiAdapter

Required? false
Accept Pipeline Input? false
Position? named
Specifies that a virtual SCSI adapter will be shared so that it can be used in guest clustering.

 TYPE OF HOST		USES THIS PARAMETER
 ------------		--------------------
 Hyper-V host		No  (for guest clustering, use iSCSI storage)
 XenServer host  No  (Xen VMs always have exactly one SCSI adapter)
Note: When sharing a SCSI controller on a virtual machine on an ESX host, VMM defaults the SCSI sharing policy on VMware to "physical."

Synthetic

Required? false
Accept Pipeline Input? false
Position? named
Specifies that a device, such as a virtual network adapter, on a virtual machine deployed on a Hyper-V host is a high-performance synthetic device. Requires a virtualization-aware guest operating system on the virtual machine.

VMMServer

Required? false
Accept Pipeline Input? true (ByValue)
Position? named
Specifies a VMM server object.

AdapterID

Required? false
Accept Pipeline Input? true (ByValue)
Position? 0
Specifies the logical unit number, or LUN ID. Hyper-V and XenServer do not expose this value, and it cannot be changed. For a VMware ESX host, the default is 7 and cannot be changed. 

VM

Required? true
Accept Pipeline Input? true (ByValue)
Position? named
Specifies a virtual machine object.

JobVariable

Required? false
Accept Pipeline Input? false
Position? named
Specifies that job progress is tracked and stored in the variable named by this parameter. 

PROTipID

Required? false
Accept Pipeline Input? false
Position? named
Specifies the ID of the PRO tip that triggered this action. This allows for auditing of PRO tips.

RunAsynchronously

Required? false
Accept Pipeline Input? false
Position? named
Indicates that the job runs asynchronously so that control returns to the command shell immediately. 

ScsiControllerType

Required? false
Accept Pipeline Input? false
Position? named
Specifies a SCSI controller type. Valid values are: DefaultType, NoType, LsiLogic, BusLogic, ParaVirtualSCSI, LsiLogicSAS.

ShareVirtualScsiAdapter

Required? false
Accept Pipeline Input? false
Position? named
Specifies that a virtual SCSI adapter will be shared so that it can be used in guest clustering.

 TYPE OF HOST		USES THIS PARAMETER
 ------------		--------------------
 Hyper-V host		No  (for guest clustering, use iSCSI storage)
 XenServer host  No  (Xen VMs always have exactly one SCSI adapter)
Note: When sharing a SCSI controller on a virtual machine on an ESX host, VMM defaults the SCSI sharing policy on VMware to "physical."

Synthetic

Required? false
Accept Pipeline Input? false
Position? named
Specifies that a device, such as a virtual network adapter, on a virtual machine deployed on a Hyper-V host is a high-performance synthetic device. Requires a virtualization-aware guest operating system on the virtual machine.

VMMServer

Required? false
Accept Pipeline Input? true (ByValue)
Position? named
Specifies a VMM server object.
Requires a VMM virtual machine object, virtual machine template object, or hardware profile object, which can be retrieved by using the Get-SCVirtualMachine, Get-SCVMTemplate, or Get-SCHardwareProfile cmdlets, respectively.

Examples

1: Create a virtual SCSI adapter on a virtual machine.
PS C:\> $VM = Get-SCVirtualMachine -Name "VM01"
PS C:\> New-SCVirtualScsiAdapter -VM $VM
The first command gets the virtual machine object named VM01 and stores the object in the $VM variable.

The second command creates a virtual SCSI adapter on VM01.
2: Create a virtual SCSI adapter on a virtual machine template.
PS C:\> $VMTemplate = Get-SCVMTemplate | where { $_.Name -eq "VMTemplate01" }
PS C:\> New-SCVirtualScsiAdapter -VMTemplate $VMTemplate
The first command gets the virtual machine template object named VMTemplate01 from the VMM library and stores the object in the $VMTemplate variable.

The second command creates a virtual SCSI adapter on VMTemplate01.
3: Create a virtual SCSI adapter on a hardware profile.
PS C:\> $HWProfile = Get-SCHardwareProfile | where { $_.Name -eq "NewHWProfile01" }
PS C:\> New-SCVirtualScsiAdapter -HardwareProfile $HWProfile
The first command gets the hardware profile object named NewHWProfile01 from the VMM library and stores the object in the $HWProfile variable.

The second command creates a virtual SCSI adapter on NewHWProfile01.

See Also