> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/get-rasproviderstatus.md).

# Get-RASProviderStatus

## SYNOPSIS

Retrieves the Provider status information.

## SYNTAX

```powershell
Get-RASProviderStatus [-Id] <uint> [-StatusLevel {Level1 | Level2 | Level3}] [<CommonParameters>]
```

```powershell
Get-RASProviderStatus [-InputObject] <Provider> [-StatusLevel {Level1 | Level2 | Level3}]
 [<CommonParameters>]
```

```powershell
Get-RASProviderStatus [[-Server] <string>] [[-SiteId] <uint>]
 [-StatusLevel {Level1 | Level2 | Level3}] [<CommonParameters>]
```

## DESCRIPTION

Retrieves the Provider status information and optionally desktop VM and application info.

## EXAMPLES

### Example 1

```powershell
Get-RASProviderStatus -Id 15
```

Retrieves the Provider status information for the Provider server with ID 15.

### Example 2

```powershell
Get-RASProviderStatus -Server MyProvider -StatusLevel Level2
```

Retrieves the Provider status and the desktop VM information for the server named "MyProvider".

### Example 3

```powershell
Get-RASProviderStatus -InputObject $Provider -StatusLevel Level3
```

Retrieves the Provider status, desktop VM, and application information for the server represented by the $Provider object.

### Example 4

```powershell
Get-RASProvider -Id 15 | Get-RASProviderStatus -StatusLevel Level1
```

Retrieves the Provider status information for the server represented by the object obtained from the pipeline output.

## PARAMETERS

### -Server

The name of the Provider server for which to retrieve the information.

This must be the actual server name used in the RAS farm.

```yaml
Type: string
Required: False
Position: 0
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -SiteId

Site ID from which to retrieve the specified Provider server information.

If the parameter is omitted, the site ID of the Licensing Server will be used.

```yaml
Type: uint
Required: False
Position: 1
Default value: 0
Accept pipeline input: False
Accept wildcard characters: False
```

### -Id

The ID of the Provider server. To obtain the ID, use the Get-RASProvider cmdlet.

```yaml
Type: uint
Required: True
Position: 0
Default value: 0
Accept pipeline input: False
Accept wildcard characters: False
```

### -InputObject

An object of type Provider representing a Provider server for which to retrieve the information.

To obtain the object, use the Get-RASProvider cmdlet.

Type reference: [Provider](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/types/provider.md)

```yaml
Type: Provider
Required: True
Position: 0
Default value: None
Accept pipeline input: true (ByValue)
Accept wildcard characters: False
```

### -StatusLevel

Specifies the level of detail that should be returned.

Acceptable values: Level1 (Provider status information only), Level2 (Provider status and Desktop VM info), Level3 (Provider status, Desktop VMs, Applications).

Possible values: Level1, Level2, Level3

Type reference: [StatusLevel](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/types/statuslevel.md)

```yaml
Type: StatusLevel
Required: False
Position: Named
Default value: Level1
Accept pipeline input: False
Accept wildcard characters: False
```

### CommonParameters

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

## INPUTS

### [Provider](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/types/provider.md)

## OUTPUTS

### [ProviderSysInfo](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/types/providersysinfo.md) [ProviderSysInfoHost](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/types/providersysinfohost.md) [ProviderSysInfoHostApp](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/types/providersysinfohostapp.md)

## RELATED LINKS

* [New-RASProvider](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/new-rasprovider.md)
* [Get-RASProvider](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/get-rasprovider.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/get-rasproviderstatus.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
