> 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/invoke-rasrdshostprocesscmd.md).

# Invoke-RASRDSHostProcessCmd

## SYNOPSIS

Sends an RDS Process command.

## SYNTAX

```powershell
Invoke-RASRDSHostProcessCmd [-InputObject] <ServerAppInfo> -Command {Kill} [<CommonParameters>]
```

```powershell
Invoke-RASRDSHostProcessCmd [-RDSId] <uint> -Command {Kill} -Id <uint> [<CommonParameters>]
```

```powershell
Invoke-RASRDSHostProcessCmd [-RDSServer] <string> [[-SiteId] <uint>] -Command {Kill} -Id <uint>
 [<CommonParameters>]
```

## DESCRIPTION

Sends an RDS session process command.

It will only fail with an error if the name or ID of the target RD Session Host server is invalid or command does not reach the destination.

If the process ID is invalid, the command will not fail.

Kill: sends an RDS kill process command.

## EXAMPLES

### Example 1

```powershell
Invoke-RASRDSHostProcessCmd "server.company.dom" -Id 2536 -Command Kill
```

Invoke the RDS kill process command in the Licensing Server site (default) for the process with ID '2536'.

To obtain the Process ID, use the Get-RASRDSHostStatus cmdlet with StatusLevel as Level3.

### Example 2

```powershell
Invoke-RASRDSHostProcessCmd -RDSId 10 -Id 2536 -Command Kill
```

Invoke the RDS kill process command for the process with ID '2536' of the RDS Server with ID '10'.

To obtain the ID, use the Get-RASRDSHost cmdlet.

To obtain the process ID, use the Get-RASRDSHostStatus cmdlet with StatusLevel as Level3.

### Example 3

```powershell
$RDPSessionApp | Invoke-RASRDSHostProcessCmd -Command Kill
```

Invoke the RDS kill process command for the process, which is identified by an object obtained from the pipeline output.

To obtain the $RDPSessionApp object, use the Get-RASRDSHostStatus cmdlet with StatusLevel as Level3.

## PARAMETERS

### -RDSServer

The name of a RD Session Host server.

The name can be either FQDN or IP address, but you have to enter the actual name this server has in the RAS farm.

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

### -SiteId

Site ID.

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

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

### -RDSId

The ID of a RD Session Host server.

To obtain the ID, use the Get-RASRDSHost cmdlet.

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

### -Id

Process ID.

To obtain the RDS Process ID, use the Get-RASRDSHostStatus command with StatusLevel as Level3.

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

### -InputObject

The RDS Server Application info object.

To obtain an ServerAppInfo object representing a RD Session application info, use the Get-RASRDSHostStatus command with StatusLevel as Level 3."

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

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

### -Command

Process command.

Accepted values: Kill.

Possible values: Kill

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

```yaml
Type: RDSProcessCmd
Required: True
Position: Named
Default value: 0
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

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

## OUTPUTS

### None

## RELATED LINKS

* [Get-RASRDSHost](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/get-rasrdshost.md)
* [Get-RASRDSHostStatus](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/get-rasrdshoststatus.md)
* [Invoke-RASRDSHostCmd](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/invoke-rasrdshostcmd.md)
* [Invoke-RASRDSHostSessionCmd](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/invoke-rasrdshostsessioncmd.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/invoke-rasrdshostprocesscmd.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.
