> 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/new-rasconnectionbroker.md).

# New-RASConnectionBroker

## SYNOPSIS

Adds a RAS Connection Broker server to a site.

## SYNTAX

```powershell
New-RASConnectionBroker [-Server] <string> [[-SiteId] <uint>] [-NoFireWallRules <SwitchParameter>]
 [-NoInstall <SwitchParameter>] [-NoRestart <SwitchParameter>] [-Takeover <SwitchParameter>]
 [<CommonParameters>]
```

```powershell
New-RASConnectionBroker [-Server] <string> [[-SiteId] <uint>] -Password <SecureString>
 -Username <string> [-NoFireWallRules <SwitchParameter>] [-NoRestart <SwitchParameter>]
 [-Takeover <SwitchParameter>] [<CommonParameters>]
```

## DESCRIPTION

Adds a RAS Connection Broker server to a site.

The agent software will be installed on the server by default. You can optionally skip the agent installation by including the -NoInstall parameter.

## EXAMPLES

### Example 1

```powershell
New-RASConnectionBroker "server.company.dom"
```

Adds the specified server to the Licensing Server site as a RAS Connection Broker.

The agent software will be installed on the server automatically.

To add a RAS Connection Broker to a specific site, add the -SiteId parameter.

## PARAMETERS

### -Server

FQDN or IP address of the server to add to a site as a RAS Connection Broker.

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

### -SiteId

Site ID to which to add the RAS Connection Broker server.

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
```

### -Username

An administrator account for push installing the agent on the server.

If this parameter is omitted, your RAS admin username and password will be used.

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

### -Password

The password of the account specified in the Username parameter.

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

### -NoInstall

Specifies not to install the agent software on the server.

If you omit this parameter, the agent will be push installed on the server using your RAS admin credentials.

To specify different credentials, include the Username and Password parameters.

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

### -NoRestart

Specifies not to restart the server after the RAS Connection Broker is installed.

If this parameter is omitted, the server will be restarted if required.

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

### -NoFireWallRules

Specifies not to add firewall rules to allow the RAS Connection Broker to communicate.

If this parameter is omitted, the firewall rules will not be added.

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

### -Takeover

Specifies to takeover the RAS Connection Broker that is installed on the server, if installed.

If this parameter is omitted and the RAS Connection Broker is installed, this service will not be taken over.

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

### None

## OUTPUTS

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

## RELATED LINKS

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