EXAMPLE 1

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.

	Copy Code
Test-CsComputer -Verbose

EXAMPLE 2

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.

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

The Test-CsComputer cmdlet is an example of a Lync Server "synthetic transaction." Synthetic transactions are used in Lync 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 Lync 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 Lync 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.

None. The Test-CsComputer cmdlet does not accept pipelined input.

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