Edit

Share via


Test-CsComputer

The Test-CsComputer cmdlet verifies the status of the Skype for Business Server services running on the local computer. The cmdlet also verifies that the appropriate Skype for Business Server Active Directory groups have been added to the corresponding local groups on the computer, and that the necessary computer firewall ports have been opened. This cmdlet was introduced in Lync Server 2010.

Syntax

Default (Default)

Test-CsComputer
    [-Report <String>]
    [-Verbose]
    [<CommonParameters>]

Description

The Test-CsComputer cmdlet is an example of a Skype for Business Server "synthetic transaction." Synthetic transactions are used in Skype for Business Server to verify that users are able to successfully complete common tasks such as logging on to the system, exchanging instant messages, or making calls to a phone located on the public switched telephone network (PSTN). These tests can be conducted manually by an administrator, or they can be run automatically by an application such as Microsoft System Center Operations Manager (formerly Microsoft Operations Manager).

The Test-CsComputer cmdlet, which can be run only on the local computer, verifies the status of all the Skype for Business Server services on that computer. The cmdlet also checks to see if the appropriate firewall ports have been opened on the computer, and determines whether or not the Active Directory groups created when you installed Skype for Business Server have been added to the corresponding local groups. For example, the Test-CsComputer cmdlet will verify that the Active Directory group RTCUniversalUserAdmins has been added to the local Administrators group.

Examples

Example 1

Test-CsComputer -Verbose

The command shown in Example 1 verifies the service activation status for the local computer. The Verbose parameter is included in the command to ensure that the success (or failure) of the operation is fully reported on the screen.

Example 2

Test-CsComputer -Verbose -Report C:\Logs\Computer.html

Example 2 also verifies the service activation status of the local computer. In addition, this command writes detailed information about the activation status to the file C:\Logs\Computer.html. This log is generated by including the Report parameter followed by the full path to the log file where the information should be recorded.

Parameters

-Report

Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019

Enables you to specify a file path for the log file created when the cmdlet runs. For example: -Report "C:\Logs\Computer.html". If this file already exists, it will be overwritten when you run the cmdlet.

Parameter properties

Type:String
Default value:None
Supports wildcards:False
DontShow:False

Parameter sets

(All)
Position:Named
Mandatory:False
Value from pipeline:False
Value from pipeline by property name:False
Value from remaining arguments:False

CommonParameters

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -ProgressAction, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.

Inputs

None

The Test-CsComputer cmdlet does not accept pipelined input.

Outputs

Microsoft.Rtc.SyntheticTransactions.TaskOutput

The Test-CsComputer cmdlet returns an instance of the Microsoft.Rtc.SyntheticTransactions.TaskOutput object.