Test-CsComputer verifies the status of the Microsoft Communications Server services running on the local computer. The cmdlet also verifies that the appropriate Communications 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.
Syntax
Test-CsComputer [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Report <String>] [-WhatIf [<SwitchParameter>]] |
Parameters
Parameter | Required | Type | Description |
---|---|---|---|
Report |
Optional |
Enables you to specify a file path for the log file created when the cmdlet runs. For example: -Report "C:\Logs\Computer.xml". If this file already exists, it will be overwritten when you run the cmdlet. |
|
Verbose |
Optional |
Switch Parameter |
Reports detailed activity to the screen as the cmdlet runs. |
Force |
Optional |
Switch Parameter |
Suppresses the display of any non-fatal error message that might arise when running the command. |
WhatIf |
Optional |
Switch Parameter |
Describes what would happen if you executed the command without actually executing the command. |
Confirm |
Optional |
Switch Parameter |
Prompts you for confirmation before executing the command. |
Detailed Description
Test-CsComputer is an example of a Communications Server "synthetic transaction." Synthetic transactions are used in Microsoft Communications 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 automatically run by an application such as Microsoft System Center Operations Manager.
Test-CsComputer, which can be run only on the local computer. verifies the status of all the Microsoft Communications 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 Microsoft Communications Server have been added to the corresponding local groups. For example, Test-CsComputer will verify that the Active Directory group RTCUniversalUserAdmins has been added to the local Administrators group.
Return Types
Test-CsComputer returns an instance of the Microsoft.Rtc.SyntheticTransactions.TaskOutput object.
Examples
-------------------------- Example 1 ------------------------
Copy Code | |
---|---|
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 onscreen.
-------------------------- Example 2 ------------------------
Copy Code | |
---|---|
Test-CsComputer -Verbose -Report C:\Computer.xml |
The preceding command 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:\Computer.xml. This log is generated by including the -Report parameter followed by the full path to the log file where the information should be recorded.