Set-SCCloud

Changes the properties of a private cloud in VMM.

Description

The Set-SCCloud cmdlet changes the properties of a private cloud in System Center Virtual Machine Manager (VMM).

For more information about private clouds, type: "Get-Help New-SCCloud -detailed".

For mroe information about Set-SCCloud, type: "Get-Help Set-SCCloud -online".

Parameters

Cloud

Required? false
Accept Pipeline Input? true (ByValue)
Position? 0 
Specifies a private cloud object.

AddCapabilityProfile

Required? false
Accept Pipeline Input? false
Position? named 
Adds one or more capability profile objects to a private cloud.

AddCloudResource

Required? false
Accept Pipeline Input? false
Position? named 
Adds one or more resources to a private cloud. Resources that you can add to a private cloud include: Load Balancer, Logical Network, Static IP Address Pool, Storage Pool, and VIP Template.

AddReadOnlyLibraryShare

Required? false
Accept Pipeline Input? false
Position? named 
Adds one or more specified read-only library shares to a private cloud.

AddVMHostGroup

Required? false
Accept Pipeline Input? false
Position? named 
Adds one or more host groups to an existing host group array or private cloud.

Description

Required? false
Accept Pipeline Input? false
Position? named 
States a description for the specified object.

JobGroup

Required? false
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.

Name

Required? false
Accept Pipeline Input? false
Position? named 
Specifies the name of a VMM object.

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.

ReadWriteLibraryPath

Required? false
Accept Pipeline Input? false
Position? named 
Specifies a writable library path to which virtual machines can be stored.

RemoveCapabilityProfile

Required? false
Accept Pipeline Input? false
Position? named 
Removes one or more specified capability profile objects.

RemoveCloudResource

Required? false
Accept Pipeline Input? false
Position? named 
Removes a specified resource from a private cloud.

RemoveReadOnlyLibraryShare

Required? false
Accept Pipeline Input? false
Position? named 
Removes a specified read-only library share.

RemoveVMHostGroup

Required? false
Accept Pipeline Input? false
Position? named 
Removes one or more host groups from a host group array or private cloud.

RunAsynchronously

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

VMMServer

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

Examples

1: Update the properties of a private cloud using a job group. 
PS C:\> $Guid = [System.Guid]::NewGuid()
PS C:\> $Cloud = Get-SCCloud -Name "Cloud01"
PS C:\> $CapabilityProfile = Get-SCCapabilityProfile -Profilename "HyperV"
PS C:\> Set-SCCloudCapacity -JobGroup $Guid -StorageLimited $True -StorageGB 500 -VirtualMachinesLimited $True -VirtualMachines 50 -VirtualCPUCountLimited $True -VirtualCPUCount 100
PS C:\> Set-SCCloud -Cloud $Cloud -AddCapabilityProfile $CapabilityProfile -JobGroup $Guid -Description "Updated description for Cloud01"

The first command creates a new GUID and stores it in the $Guid variable. Subsequent commands that include this GUID are collected into a single job group.

The second command gets the private cloud object named Cloud01 and stores the object in the $Cloud variable.

The thrid command gets the Hyper-V capability profile object and stores the object in the $CapabilityProfile variable.

The fourth command sets the following limits on the cloud capacity dimensions: 500 GB storage, 50 virtual machines, and 100 CPUs. Using the JobGroup parameter specifies tha this command will not run until just before the final command that includes the JobGroup with the same GUID.

The last command adds the capability profile stored in $CapabilityProfile to Cloud01, updates the description for Cloud01, and sets the cloud capacity properties on Cloud01 using the settings specified in the fourth command. This command uses the JobGroup parameter to run Set-SCCloudCapacity just before Set-SCCloud runs so that the settings will be assocated with the specified private cloud.

See Also