Set-SCApplicationHostTemplate

Configures the properties of an application host template that has been added to a service template.

Description

The Set-SCApplicationHostTemplate cmdlet configures the properties of an application host template that has been added to a service template. 

For more information about Set-SCApplicationHostTemplate, type: "Get-Help Set-SCApplicationHostTemplate -online".

Parameters

ApplicationHostTemplate

Required? true
Accept Pipeline Input? true (ByValue)
Position? 0
Specifies an application host template object.

ApplicationProfile

Required? false
Accept Pipeline Input? false
Position? named
Specifies an application profile object.

ComputerName

Required? false
Accept Pipeline Input? false
Position? named
Specifies the name of a computer that VMM can uniquely identify on your network. Valid formats are: FQDN, IPv4 or IPv6 address, or NetBIOS name.

NOTE: See the examples for a specific cmdlet to determine how that cmdlet specifies the computer name.

DeploymentOrder

Required? false
Accept Pipeline Input? false
Position? named
Specifies the order in which a computer tier or application host is deployed.

Description

Required? false
Accept Pipeline Input? false
Position? named
States a description for the specified 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. 

Name

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

Owner

Required? false
Accept Pipeline Input? false
Position? named
Specifies the owner of a VMM object in the form of a valid domain user account.

Example format: -Owner "Contoso\ReneeLo"
Example format: -Owner "ReneeLo@Contoso"

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. 

ServicingOrder

Required? false
Accept Pipeline Input? false
Position? named
Specifies the order in which a computer tier or application host is serviced.

Tag

Required? false
Accept Pipeline Input? false
Position? named
Specifies a word or phrase to associate with an object so that you can search for all objects with the specified set of tags. You can search for a subset of tags, or you can search for the full set of tags.

Examples

1: Change the description of the application host template.
PS C:\> $ServiceTemplate = Get-SCServiceTemplate -Name "ServiceTemplate01"
PS C:\> $AppHostTemplate = Get-SCApplicationHostTemplate -ServiceTemplate $ServiceTemplate
PS C:\> Set-SCApplicationHostTemplate -ApplicationHostTemplate $AppHostTemplate -Description "This is the updated description"
The first command gets the service template object named ServiceTemplate01 and stores the object in the $ServiceTemplate variable.

The second command gets the application host template object for the service template in $ServcieTemplate and stores the object in the $AppHostTemplate variable.

The last command changes the description property of the application host template in $AppHostTemplate.
2: Change the name of an application host template.
PS C:\> $ServiceTemplate = Get-SCServiceTemplate -Name "ServiceTemplate01"
PS C:\> $AppHostTemplate = Get-SCApplicationHostTemplate -ServiceTemplate $ServiceTemplate
PS C:\> Set-SCApplicationHostTemplate -ApplicationHostTemplate $AppHostTemplate -Name "This is the updated name"
The first command gets the service template object named ServiceTemplate01 and stores the object in the $ServiceTemplate variable.

The second command gets the application host template object for the service template stored in $ServiceTemplate and stores the object in the $AppHostTemplate variable.

The last command changes the name property of the application host template stored in $AppHostTemplate. Because the application host template is cloned into the service template, renaming the application host template does not affect other service templates in the system.

See Also