> 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/add-raswindevicegroupinboundport.md).

# Add-RASWinDeviceGroupInboundPort

## SYNOPSIS

Adds the Windows device group Inbound ports.

## SYNTAX

```powershell
Add-RASWinDeviceGroupInboundPort [-Id] <uint> -Port <uint>
 -Profile {Domain | Private | Public | All} -Protocol {TCP | UDP} [<CommonParameters>]
```

```powershell
Add-RASWinDeviceGroupInboundPort [[-InputObject] <WinDeviceGroup>] -Port <uint>
 -Profile {Domain | Private | Public | All} -Protocol {TCP | UDP} [<CommonParameters>]
```

```powershell
Add-RASWinDeviceGroupInboundPort [-Name] <string> -Port <uint>
 -Profile {Domain | Private | Public | All} -Protocol {TCP | UDP} [-SiteId <uint>]
 [<CommonParameters>]
```

## DESCRIPTION

Adds the Windows device group Inbound ports.

## EXAMPLES

### Example 1

```powershell
Add-RASWinDeviceGroupInboundPort -Name "WinDeviceGroup" -Port 50005 -Protocol TCP -Profile All
```

Adds an Inbound port to the list of Inbound ports of the Windows device group with name WinDeviceGroup.

### Example 2

```powershell
Add-RASWinDeviceGroupInboundPort -Id 1 -Port 50005 -Protocol TCP -Profile All
```

Adds an Inbound port to the list of Inbound ports of the Windows device group with Id 1.

## PARAMETERS

### -Port

The Port to add to the windows device group.

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

### -Protocol

The Protocol to add to the windows device group.

Possible values: TCP, UDP

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

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

### -Profile

The Profile to add to the windows device group.

Possible values: Domain, Private, Public, All

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

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

### -Name

The name of the windows device group from which to add the Inbound Port.

This must be the actual windows device group name used in the RAS farm.

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

### -SiteId

The ID of the Site from which from which to add the Inbound Port.

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

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

### -Id

The ID of a windows device group from which to add the Inbound Port.

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

### -InputObject

The Windows Device Group to modify.

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

```yaml
Type: WinDeviceGroup
Required: False
Position: 0
Default value: None
Accept pipeline input: true (ByValue)
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

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

## OUTPUTS

### None

## RELATED LINKS

* [New-RASWinDeviceGroup](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/new-raswindevicegroup.md)
* [Get-RASWinDeviceGroup](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/get-raswindevicegroup.md)
* [Set-RASWinDeviceGroup](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/set-raswindevicegroup.md)
* [Remove-RASWinDeviceGroup](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/remove-raswindevicegroup.md)
* [Get-RASWinDeviceGroupInboundPort](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/get-raswindevicegroupinboundport.md)
* [Remove-RASWinDeviceGroupInboundPort](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/remove-raswindevicegroupinboundport.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/add-raswindevicegroupinboundport.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.
