Parameters

Many Lync Server 2010 components run as standard Windows services; for example, the Lync Server Conferencing Attendant application is actually a service named RTCCAA. The Get-CsWindowsService cmdlet enables you to retrieve detailed information about these Lync Server services and only these services. That’s because the cmdlet has been designed to ignore any service that is not part of Lync Server.

The fact that Get-CsWindowsService automatically filters out non-Lync Server services is one advantage the cmdlet offers over the generic Get-Service cmdlet that ships as part of Windows PowerShell. In addition to that, there is another reason to use Get-CsWindowsService if you need to retrieve information for a Lync Server service: Get-CsWindowsService returns useful data that Get-Service does not return. For example, when returning information about the Lync Server Conferencing Attendant service, Get-CsWindowsService reports back the number of concurrent calls being handled by the service (the service activity level). Get-Service does not.

By default Get-CsWindowsService runs against the local computer. However, by including the ComputerName parameter you can return information about the Lync Server services running on a remote computer.

Who can run this cmdlet: By default, members of the following groups are authorized to run the Get-CsWindowsService cmdlet locally: RTCUniversalServerAdmins. In addition, you must also be a member of the Performance Monitor Users group on the destination computer in order to run this cmdlet. 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 "Get-CsWindowsService"}

None. Get-CsWindowsService does not accept pipelined input.

Get-CsWindowsService returns instances of the Microsoft.Rtc.Management.Deployment.Core.NTService object.

-------------------------- Example 1 ------------------------

The command shown in Example 1 returns information about all the Lync Server services installed on the local computer. This is done by calling Get-CsWindowsService without any parameters.

-------------------------- Example 2 ------------------------

Example 2 also returns information about the Lync Server services on the local computer; in this case, however, the data is displayed in list format. (Among other things, this enables you to view all the property values for each service. In the default, tabular view, only a subset of property values is displayed.) To carry out this task, Get-CsWindowsService is first called, then the resulting information is piped to the Format-List cmdlet.

-------------------------- Example 3 ------------------------

Example 3 returns information for a single Lync Server service: the service with the name RTCSrv.

-------------------------- Example 4 ------------------------

In Example 4, detailed information is displayed for all the service roles handled by the RTCSrv service. To perform this task, Get-CsWindowsService is first used to return information about the RTCSrv service. This information is then piped to the Select-Object cmdlet, which uses the ExpandProperty parameter to display all the roles handled by the RTCSrv service. Note that this command will return an error message if a service does not have a role name.

-------------------------- Example 5 ------------------------

The command shown in Example 5 returns information about the Lync Server services installed on the remote computer atl-cs-001.litwareinc.com. This is done by including the ComputerName parameter followed by the FQDN of the remote computer.

-------------------------- Example 6 ------------------------

The preceding command returns information about all the Lync Server services installed on the local computer. In addition, the Report parameter is included in order to save error information to a file named C:\Logs\Services.html. If Get-CsWindowsService encounters any problems in retrieving service data, information about that problem will be recorded in Services.html.

-------------------------- Example 7 ------------------------

In Example 7, information is returned only for the Lync Server services on the local computer that are currently running. To accomplish this, the command first calls Get-CsWindowsService to return a collection of all the Lync Server services, running or not running. This collection is then piped to the Where-Object cmdlet, which picks out only those services where the Status property is equal to Running.

-------------------------- Example 8 ------------------------

Example 8 shows how you can retrieve information for a particular service even if you do not know the actual name of that service (in this case, RTCASMCU). To perform this task, Get-CsWindowsService is first called without any parameters; that returns a collection of all the Lync Server services on the local computer. This collection is then piped to the Where-Object cmdlet, which selects the one service where the DisplayName property includes (-like) the string value "Application Sharing". The end result: information is displayed for the Lync Server Application Sharing Conferencing service.

-------------------------- Example 9 ------------------------

Example 9 returns information about any services that host the Application Server role. To do this, the command first calls Get-CsWindowsService to return a collection of all the Lync Server services on the local computer. This collection is then piped to the Where-Object cmdlet, which selects those services where the RoleName property includes (-contains) ApplicationServer.

Other Resources

Start-CsWindowsService
Stop-CsWindowsService