How To Start & Stop All Lync Services
This is a question that I saw on the Lync forum – how to stop & start all Lync services. The person who posted the question was after a PowerShell script or batch file to make the stop/start process easier. Unlike Exchange, Lync 2010 ships with cmdlets to start and stop all Lync services running…
This is a question that I saw on the Lync forum – how to stop & start all Lync services. The person who posted the question was after a PowerShell script or batch file to make the stop/start process easier.
Unlike Exchange, Lync 2010 ships with cmdlets to start and stop all Lync services running on a Lync server. You don’t need to run a script or batch file.
The cmdlet that needs to be run (from an elevated Lync Shell) to stop all Lync services is Stop-CsWindowsService.
All Lync services are stopped for sure.
Run net stop w3svc if you want the IIS services to be stopped as well.
In order to start the Lync services, the cmdlet is (yes, you guessed it right) Start-CsWindowsService.
Sure enough, all Lync services got started.
Again, run net start w3svc if you want IIS services to be started as well.
Taking the power of the cmdlet a bit further, you can stop/start Lync services on a remote server by using the –Computer parameter. If you want to stop/start only one service, specify the service using the –Name parameter. If you don’t know the exact name of the service, you can filter it by piping it to Where-Object. For example, if you want to stop the front end service & you are not sure of the actual service name, you can run
Get-CsWindowsService | Where-Object {$_.DisplayName –like “*front*”} | Stop-CsWindowsService.
Not sure as to why the cmdlet was not named Start/Stop-CsLyncService