Topic Last Modified: 2013-02-21

Adds a computer that hosts trusted applications to an existing pool. This cmdlet was introduced in Lync Server 2010.

Syntax

New-CsTrustedApplicationComputer -Identity <XdsGlobalRelativeIdentity> -Pool <String> [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-WhatIf [<SwitchParameter>]]

Examples

EXAMPLE 1

This example adds a new computer with the FQDN Trust1.litwareinc.com to the pool TrustPool.litwareinc.com. We use the Identity parameter to specify the FQDN of the new computer, and the Pool parameter to specify the FQDN of the pool. The pool must exist and must be a trusted application pool. (Note: To create a trusted application pool, call the New-CsTrustedApplicationPool cmdlet.)

Copy Code
New-CsTrustedApplicationComputer -Identity Trust1.litwareinc.com -Pool TrustPool.litwareinc.com

Detailed Description

We recommend that the computers that are running trusted applications within a Lync Server deployment be added to a separate pool that is only for trusted applications. However, you can add trusted application computers to an existing pool that is also used for other purposes. By default, when you create a pool, a computer with the same fully qualified domain name (FQDN) as the pool is also created. Use this cmdlet to create a new computer and add it to a pool.

The trusted application pool must already exist in order for this cmdlet to succeed. In addition, you can’t add an additional trusted application computer to a pool that contains service roles other than the ExternalServer role. For example, if the pool also supports Registrar or CentralMgmt roles, the pool can contain only one trusted application computer. In addition, if you did not specify a computer FQDN for the default computer when you created the pool (by calling the New-CsTrustedApplicationPool) cmdlet, the computer will have the same FQDN as the pool and you cannot add another computer.

Who can run this cmdlet: By default, members of the following groups are authorized to run the New-CsTrustedApplicationComputer cmdlet locally: RTCUniversalServerAdmins. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell prompt:

Get-CsAdminRole | Where-Object {$_.Cmdlets –match "New-CsTrustedApplicationComputer"}

Parameters

Parameter Required Type Description

Identity

Required

Microsoft.Rtc.Management.Xds.XdsGlobalRelativeIdentity

The FQDN of the computer that hosts the trusted application.

Pool

Required

System.String

The FQDN of the pool hosting the trusted application computer. You can find available pools by running the Get-CsTrustedApplicationPool cmdlet.

Confirm

Optional

System.Management.Automation.SwitchParameter

Prompts you for confirmation before executing the command.

Force

Optional

System.Management.Automation.SwitchParameter

Suppresses any confirmation prompts that would otherwise be displayed before making changes.

WhatIf

Optional

System.Management.Automation.SwitchParameter

Describes what would happen if you executed the command without actually executing the command.

Input Types

None.

Return Types

Creates an object of type Microsoft.Rtc.Management.Xds.DisplayComputer.

See Also