Start-WebSitesOperation

Starts a DWAS operation.

Syntax

Start-WebSitesOperation
     [-OperatorName] <String>
     [-OperationName] <String>
     [-Parameters] <Hashtable>
     [-WaitForCompletion]
     [[-Timeout] <TimeSpan>]
     [-RemoteSettings <RemoteSettings>]
     [-SuppressRequestIdLine]
     [<CommonParameters>]

Description

The Start-WebSitesOperation cmdlet starts a Dynamic Windows Activation Service (DWAS) operation. DWAS is designed to carry out such tasks as:

  • Provisioning and activating sites.
  • Starting and monitoring worker processes.
  • Shutting down and deprovisioning sites.
  • Overseeing sandbox and security measures.

Examples

Example 1: Start an upgrade on all front-end servers

PS C:\> Start-WebSitesOperation -OperatorName "WFF" -OperationName "Upgrade" -Parameters @{"WebFarmName"="FrontEndServers"}

This command starts an upgrade operation on front-end servers.

Example 2: Start an upgrade on a specific worker server

PS C:\> Start-Operation -OperatorName "WFF" -OperationName "Upgrade" -Parameters @{"WebFarmName"="WorkerServers";ServerName="SERVER01"}

This command starts an upgrade operation on the server named Server01.

Required Parameters

-OperationName

Specifies the name of the operation being started. For example:

-OperationName "Upgrade"

The most commonly-used operations are Upgrade and Repair.

Type:String
Position:1
Default value:None
Accept pipeline input:True (ByPropertyName)
Accept wildcard characters:False
-OperatorName

Specifies the name of the operator under which the role runs. For example:

-OperatorName "WFF"

Type:String
Position:0
Default value:None
Accept pipeline input:True (ByPropertyName)
Accept wildcard characters:False
-Parameters

Specifies a hash table containing parameters for the operation. These parameters typically consist of a server farm name and/or a server name For example, this syntax uses a single parameter (WebFarmName) that specifies a web farm:

-Parameters @{"WebFarmName"="FrontEndServers"}

To use multiple parameters, separate the parameters by using a semicolon. For example, this syntax uses two parameters (WebFarmName and ServerName):

-Parameters @{"WebFarmName"="WorkerServers";ServerName="SERVER01"}

Type:Hashtable
Position:2
Default value:None
Accept pipeline input:True (ByPropertyName)
Accept wildcard characters:False

Optional Parameters

-RemoteSettings

{{Fill RemoteSettings Description}}

Type:RemoteSettings
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
-SuppressRequestIdLine

{{Fill SuppressRequestIdLine Description}}

Type:SwitchParameter
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
-Timeout

Specifies the maximum time (in seconds) to wait for the operation to finish.

Type:TimeSpan
Position:4
Default value:None
Accept pipeline input:True (ByPropertyName)
Accept wildcard characters:False
-WaitForCompletion

Indicates that the cmdlet waits for the operation to finish before it returns control to the Windows PowerShell console or the calling script. If not specified, control returns immediately, and the command runs in the background.

Type:SwitchParameter
Position:3
Default value:None
Accept pipeline input:True (ByPropertyName)
Accept wildcard characters:False