Gets the current status of the Orchestration Service on the controller.
Get-OrchServiceStatus [-BearerToken <String>] [-TraceParent <String>] [-TraceState <String>] [-VirtualSiteId <String>] [-AdminAddress <String>] [<CommonParameters>]
Enables the status of the Orchestration Service on the controller to be determined. The database connection to the service does not need to be configured before using this command.
|Name||Description||Required?||Pipeline Input||Default Value|
|BearerToken||Specifies the bearer token assigned to the calling user||false||false|
|TraceParent||Specifies the trace parent assigned for internal diagnostic tracing use||false||false|
|TraceState||Specifies the trace state assigned for internal diagnostic tracing use||false||false|
|VirtualSiteId||Specifies the virtual site the PowerShell snap-in will connect to.||false||false|
|AdminAddress||Specifies the address of a XenDesktop controller the PowerShell snap-in will connect to. You can provide this as a host name or an IP address.||false||false||Localhost. Once a value is provided by any cmdlet, this value becomes the default.|
You cannot pipe input into this cmdlet.
The Get-OrchServiceStatus command returns an object containing the status of the Orchestration Service together with extra diagnostics information.
The Orchestration Service is running and is connected to a database containing a valid schema.
The Orchestration Service does not have a database connection configured.
The database rejected the logon attempt from the Orchestration Service. This may be because the service attempted to log on with invalid credentials or because a database has not been installed in the specified location.
The expected stored procedures are missing from the database. This may be because the Orchestration Service schema has not been added to the database.
The specified database could not be located with the configured connection string.
The Orchestration is connected to a database that is valid, but it does not have the full functionality required for optimal performance. Upgrading the database is advisable.
The Orchestration is connected to a database that is valid, but it does not have the full functionality required so the Orchestration cannot function. Upgrading the database is required.
The version of the Orchestration Service currently in use is incompatible with the version of the Orchestration Service schema on the database. Upgrade the Orchestration Service to a more recent version.
The version of the Orchestration Service schema on the database is incompatible with the version of the Orchestration Service currently in use. Upgrade the database schema to a more recent version.
A database schema upgrade is currently in progress.
Connectivity between the Orchestration Service and the database has been lost. This may be a transitory network error, but may indicate a loss of connectivity that requires administrator intervention.
Connectivity between the Orchestration and the database has been lost for an extended period of time, or has failed due to a configuration problem. The Orchestration service cannot operate while its connection to the database is unavailable.
(0) The service status cannot be determined.
If the command fails, the following errors can be returned.
An error occurred in the service while attempting a database operation.
The operation could not be completed because the database for the service is not configured.
An error occurred in the service while attempting a database operation - communication with the database failed for various reasons.
You do not have permission to execute this command.
There was a problem communicating with the Citrix Delegated Administration Service.
There was a problem communicating with the remote service.
An unexpected error occurred. For more details, see the Windows event logs on the controller or the XenDesktop logs.
Get the current status of the Orchestration Service.