Stop-Cs Windows Service

Stop-CsWindowsService enables you to stop a Skype for Business Server service. This cmdlet was introduced in Lync Server 2010.

Syntax

Description

Many Skype for Business Server components run as standard Windows services; for example, the Conferencing Attendant application is actually a service named RTCCAA. If you need to stop a Skype for Business Server service, you can do so by using the Stop-CsWindowsService cmdlet.

Keep in mind that the Stop-CsWindowsService cmdlet can only stop Skype for Business Server services; an error will occur if you attempt to stop a non-Skype for Business Server service (such as the print spooler) using this cmdlet.

Functionally, the Stop-CsWindowsService cmdlet is very similar to the generic Windows PowerShell Stop-Service cmdlet; if you wanted to, you could use the Stop-Service cmdlet to stop a Skype for Business Server service. However, the Stop-CsWindowsService cmdlet includes a ComputerName parameter that makes it easy to stop a service on a remote computer: you simply include the ComputerName parameter followed by the fully qualified domain name (FQDN) of the remote computer. The Stop-Service cmdlet does not have a comparable parameter. In addition, the Stop-CsWindowsService cmdlet has a Report parameter that enables you to keep a log of any errors that might occur when calling that cmdlet.

The Stop-CsWindowsService cmdlet does exactly what the name implies: it stops any service you ask it to stop. This includes services that have dependent services (services that can only run if the service you are attempting to stop is running). By default, if you try to stop a service that has dependent services, the Stop-CsWindowsService cmdlet will not only stop the service in question, but will stop all those dependent services as well. Because that could result in unexpected consequences, you can include the Graceful parameter when calling the Stop-CsWindowsService cmdlet. When you include the Graceful parameter, the Stop-CsWindowsService cmdlet will prevent the service from accepting any new requests. All existing service requests will remain as is; however, new requests will be rejected. As existing requests finish, those requests will not be replaced. Eventually, all the existing requests will be filled and the service will then shut down.

Examples

————————— Example 1 ————————

The command shown in Example 1 stops the Response Group application service on the local computer. The Response Group application service is identified by including the Name parameter and the name of that service: RTCRGS.

————————— Example 2 ————————

Example 2 also stops the Response Group application service; in this example, however, that service is located on the remote computer atl-cs-001.litwareinc.com. To stop a service on a remote computer, include the ComputerName parameter followed by the FQDN of the remote computer.

————————— Example 3 ————————

Example 3 demonstrates how you can stop a service even if you do not know the service name (in this example, RTCCPS). To do this, the command first calls the Get-CsWindowsService cmdlet without any parameters in order to return a collection of all the Skype for Business Server services on the local computer. This complete collection is then piped to the Where-Object cmdlet, which selects only those services where the DisplayName property includes the string value «Call Park». The filtered collection is then piped to the Stop-CsWindowsService cmdlet, which stops the Call Park application service.

Parameters

Name of the remote computer running the service to be stopped; if this parameter is not included, then the Stop-CsWindowsService cmdlet will stop the specified service on the local computer. The remote computer should be referenced using its FQDN; for example, atl-mcs-001.litwareinc.com.

Type:	String
Position:	Named
Default value:	None
Accept pipeline input:	False
Accept wildcard characters:	False
Applies to:	Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019

Prompts you for confirmation before executing the command.

Type:	SwitchParameter
Aliases:	cf
Position:	Named
Default value:	None
Accept pipeline input:	False
Accept wildcard characters:	False
Applies to:	Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019

Suppresses the display of any non-fatal error message that might occur when running the command.

Type:	SwitchParameter
Position:	Named
Default value:	None
Accept pipeline input:	False
Accept wildcard characters:	False
Applies to:	Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019

Instead of immediately shutting down a service, waits until all existing service requests have been filled. (However, all new service requests will be rejected.) The service will not completely shut down until all the existing requests have been filled.

Type:	SwitchParameter
Position:	Named
Default value:	None
Accept pipeline input:	False
Accept wildcard characters:	False
Applies to:	Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019

Enables you to stop a service using an object reference rather than a service name. For example, if you use the Get-CsWindowsService cmdlet to return information about a service and if you store the returned object in a variable named $x, you can then stop the service using this command:

$x = Get-CsWindowsService -Name «RTCCPS»

Stop-CsWindowsService -InputObject $x.Name

Type:	NTService
Position:	Named
Default value:	None
Accept pipeline input:	True
Accept wildcard characters:	False
Applies to:	Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019

When specified, stops all the Skype for Business Server services except for the centralized logging agent service.

Type:	SwitchParameter
Position:	Named
Default value:	None
Accept pipeline input:	False
Accept wildcard characters:	False
Applies to:	Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019

When present, shuts down all services except the Web Server service on the specified computer.

Type:	SwitchParameter
Position:	Named
Default value:	None
Accept pipeline input:	False
Accept wildcard characters:	False
Applies to:	Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019

Name of the Skype for Business Server service you want to stop. Note that you must use the service name (for example, RTCCAA) and not the service display name. You can only pass a single service name to the Name parameter, and you cannot use wildcards in the service name. You can use the Get-CsWindowsService cmdlet to retrieve service names.

Keep in mind that the Stop-CsWindowsService cmdlet can only stop Skype for Business Server services; you cannot use this cmdlet to stop other Windows services. For those services, you might be able to use the Windows PowerShell Stop-Service cmdlet.

Type:	String
Position:	2
Default value:	None
Accept pipeline input:	False
Accept wildcard characters:	False
Applies to:	Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019

When present, causes the command to run and then immediately return control to the Windows PowerShell prompt. If not present, control will not be returned until the command has completed and a status report has been written to the screen.

Type:	SwitchParameter
Position:	Named
Default value:	None
Accept pipeline input:	False
Accept wildcard characters:	False
Applies to:	Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019

Path to an HTML file where error information can be written. If this parameter is included, any errors that occur during the running of this cmdlet will be logged to the specified file (for example, C:\Logs\Service_report.html).

Type:	String
Position:	Named
Default value:	None
Accept pipeline input:	False
Accept wildcard characters:	False
Applies to:	Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019

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

Настройка установки клиента Windows в Skype для бизнеса Server Customize Windows client installation in Skype for Business Server

Сводка: Обзор методов установки и средств для Skype для бизнеса. Summary: Overview of installation methods and tools for Skype for Business.

Сведения об установке Skype для бизнеса, которая поставляется вместе с Microsoft 365 и Office 365, см. в сведениях о развертывании клиента Skype для бизнеса в Microsoft 365 или Office 365. For installation information about Skype for Business that comes with Microsoft 365 and Office 365, see Deploy the Skype for Business client in Microsoft 365 or Office 365.

Администраторы предприятия могут настраивать установку версий Skype для бизнеса с корпоративной лицензией на основе установщика Windows (MSI), используя методы, рассмотренные в этом разделе. Enterprise administrators can customize the Windows Installer-based (.msi) installation of volume licensed versions of Skype for Business by using the methods discussed in this section. Так как ни одно средство не предоставляет все параметры настройки, скорее всего, вы будете использовать сочетание этих методов в развертывании Skype для бизнеса. Because no single tool provides all customization options, you’ll likely use a combination of these methods in your Skype for Business deployment. Можно использовать средства, описанные в следующих разделах: You might use the tools described in the following sections:

Используйте средство настройки Office (OCT) в Skype для бизнеса Server для настройки параметров установки и компонентов Skype для бизнеса и других программ Office. Use the Office Customization Tool (OCT) in Skype for Business Server to customize setup options and features for Skype for Business and other Office programs.

Используйте Config.xml для выполнения задач установки в Skype для бизнеса Server, чтобы указать путь к точке сетевой установки и выполнить установку в тихом режиме. Use Config.xml to perform installation tasks in Skype for Business Server to specify the path of the network installation point and perform silent installation.

Используйте параметры командной строки программы установки в Skype для бизнеса Server, чтобы указать Config.xml для использования во время установки. Use Setup command-line options in Skype for Business Server to specify the Config.xml file to use during installation.

Настройте политики загрузки клиентов в Skype для бизнеса Server с помощью оснастки редактора объектов групповой политики MMC. Configure client bootstrapping policies in Skype for Business Server by using the Group Policy Object Editor MMC snap-in.

Скорее всего, при развертывании набора продуктов Office вы захотите настроить другие параметры. There will probably be other options you’ll want to configure as you deploy the Office suite of products. В темах этого раздела приводится обзор этих средств настройки и рассматриваются вопросы, связанные со Skype для бизнеса. The topics in this section give an overview of these customization tools and discuss considerations specific to Skype for Business. Здесь предоставляются ссылки на подробную справку Office по каждому средству. Included are links to detailed Office help for each tool.

Manage services for Skype for Business Server

This article describes how to manage services running in a Skype for Business Server topology.

View a list of computers running Skype for Business Server

You can use Skype for Business Server Control Panel to view a list of all the computers that are running Skype for Business Server in your topology and see the service status of each. You can sort the list by computer, pool, or site.

To view a list of computers running Skype for Business Server

1. From a user account that is assigned to any of the predefined administrative roles for Skype for Business Server, log on to any computer in your internal deployment. For details about the predefined administrative roles available in Skype for Business Server, see Planning for Role-Based Access Control.
2. Open a browser window, and then enter the Admin URL to open the Skype for Business Server Control Panel.
3. In the left navigation bar, click Topology and then click Status.
4. On the Status page, do any of the following as needed:
   • Sort the list by clicking the Computer, Pool, or Site column heading, and then clicking the up arrow or the down arrow.
   • Click Refresh to view the most up-to-date list.
   • Search for a specific computer by typing the computer name in the search field.

View the status of services running on a Skype for Business server

You can use Skype for Business Server Control Panel to view all the services that are running on a specific computer in your Skype for Business Server topology and see the status of each service.

To view the status of services running on a computer

1. From a user account that is assigned to the CsUserAdministrator role or the CsAdministrator role, log on to any computer in your internal deployment.
2. Open a browser window, and then enter the Admin URL to open the Skype for Business Server Control Panel.
3. In the left navigation bar, click Topology.
4. On the Status page, sort or search the list, as required, to find the computer you’re interested in, and then click the computer name.
5. Do any of the following:
   • To see the latest status of services running on the computer, click Get service status.
   • To see a list of specific services running on the computer and the status of each service, click Properties, and then click Close to return to the list.

Viewing service status with Windows Powershell cmdlets

You can also view service status by using Windows PowerShell and the Get-CsWindowsService cmdlet. You can run this cmdlet from the Skype for Business Server Management Shell or from a remote session of Windows PowerShell. For details about using remote Windows PowerShell to connect to Skype for Business Server, see the blog article «Quick Start: Managing Microsoft Lync Server 2010 Using Remote PowerShell». The process is the same in Skype for Business Server.

To view service status

To view service status on a computer, type a command similar to the following in the Skype for Business Server Management Shell and then press Enter:

This command returns information similar to the following:

RoleName	Status
	Running
	Running
	Running
	Running
	Running
	Running
	Running

View details about a service

You can use Skype for Business Server Control Panel to view details about each service that is running on a specific computer in your topology. You can view the status of each service and details such as the associated databases, ports, and dependent services.

To view details for a service

1. From a user account that is assigned to any of the predefined administrative roles for Skype for Business Server, log on to any computer in your internal deployment. For details about the predefined administrative roles available in Skype for Business Server, see Planning for Role-Based Access Control.
2. Open a browser window, and then enter the Admin URL to open the Skype for Business Server Control Panel.
3. In the left navigation bar, click Topology and then click Status.
4. In the Status page, sort or search through the list and then click the computer that you want to view.
5. Click Properties.
6. In the View Computer Detail window, sort the list of services, if necessary, and click the service you want to view.
7. Do any of the following as needed:
   • To see the latest status of that specific service, click Get service status.
   • To see the details for that specific service, click Properties and then click Close.
   • To return to the list of all computers in your topology, click Close.

Start or stop Skype for Business Server services

You can use Skype for Business Server Control Panel to start or stop all the Skype for Business Server services running on a specific computer or to start or stop a specific service.

To start or stop all Skype for Business services on a computer

From a user account that is a member of the RTCUniversalServerAdmins group (or has equivalent user rights), or assigned to the CsServerAdministrator or CsAdministrator role, log on to any computer that is in the network in which you deployed Skype for Business Server. You can determine whether you have been assigned the CsServerAdministrator or the CsAdministrator RBAC role by running a command similar to the following:

Open a browser window, and then enter the Admin URL to open the Skype for Business Server Control Panel.

In the left navigation bar, click Topology and then click Status.

On the Status page, sort or search through the list as needed to find the computer that is running the services you want to start or stop, and then click it.

Click Action.

Click Start All services or Stop All services.

To start or stop a specific service

1. From a user account that is assigned to the CsUserAdministrator role or the CsAdministrator role, log on to any computer in your internal deployment.
2. Open a browser window, and then enter the Admin URL to open the Skype for Business Server Control Panel.
3. In the left navigation bar, click Topology and then click Status.
4. On the Status page, sort or search through the list as needed to find the computer that is running the service you want to start or stop, and then click it.
5. Click Properties.
6. Sort the list of services, if necessary, and click the service you want to start or stop.
7. Click Action.
8. Click Start service or Stop service.
9. Click Close.

Prevent sessions for services

You can use Skype for Business Server Control Panel to prevent new sessions for all the Skype for Business Server services running on a specific computer or to prevent new sessions for a specific Skype for Business Server service.