PowerShell Restart-Service Cmdlet
Windows PowerShell Restart-Service
The most efficient way for PowerShell to cure a hung service is with the verb restart. Restart-Service xyz is just simpler and more efficient than stop-Service xyz, followed by start-Service xyz. If you are new to PowerShell Restart-Service, then I suggest that you begin with my Get-Service page.
Topics for PowerShell Restart-Service
The service which benefits most from Restart-Service is, "Spooler". The reason being the printer gives more trouble than any other piece of hardware, and often restarting the Spooler cures the problem. The inferior, but ruthless method of curing such printer jams is to reboot the computer. When the the computer is also a fileserver, this technique is undesirable.
All you really need is this simple command:
# PowerShell Restart-Service example
Note 1: You can change "Spooler" to the name of another service. To list services see PowerShell's Get-Service
Comprehensive Restart-Service Script
# PowerShell cmdlet to restart the Spooler service
Note 2: My biggest fear is that in a production script I will misspell the name of the service. Thus, check for success by observing this system message:
WARNING: Waiting for service 'Print Spooler (Spooler)' to finish starting...
Note 3: There will be variations depending on which operating system you are using.
SolarWinds' Network Performance Monitor will help you discover what's happening on your network. This utility will also guide you through troubleshooting; the dashboard will indicate whether the root cause is a broken link, faulty equipment or resource overload.
Perhaps the NPM's best feature is the way it suggests solutions to network problems. Its second best feature is the ability to monitor the health of individual VMware virtual machines. If you are interested in troubleshooting, and creating network maps, then I recommend that you try Solarwinds NPM now.
What's in a Name? What do these groups of services have in common?
More importantly, why won't the PowerShell's service family interact with Group B?
The Answer: Some services have a 'Display Name' which differs from their 'Service Name', for example Telnet and Tlnsvr. How did I find this out? When I tried to start 'Telnet', or 'Print Spooler', nothing happened. Yet if I had a manual walk-through in the Service GUI, no problem. Then I ran Get-Service * and observed the two columns, Name and also Display Name. What threw me into confusion was Group A, where both names are the same.
Just to emphasise, if you wish to use the name 'Print Spooler', you need to specify the property -DisplayName.
# PowerShell Restart-Service example using displayName
Note 4: You could research the names and displayNames with Get-Service.
In Windows Server 2003 days I choose the Alerter service for testing, partly because it's relatively harmless service, and partly because its name is near the top of the list! However, since it's been removed from Windows 7 and Server 2008 does I have choosen PLA (Performance Logs and Alerts) to test PowerShell's service cmdlets.
Let us check the service's status, and also let us 'warm up' with Get-Service before we employ other members of the service family.
# PowerShell cmdlet to check a service's status
Note 5: I have decided to introduce the variable $srvName to hold the value of the service. Hopefully this will emphasise the name of the service, and prompt you to change it as necessary for your project.
Note 6: Observe how I mix the ''literal phrases'' with the $variables and properties to produce a meaningful output.
Encouraging computers to sleep when they're not in use is a great idea - until you are away from your desk and need a file on that remote sleeping machine!
WOL also has business uses for example, rousing machines so that they can have update patches applied. My real reason for recommending you download this free tool is because it's so much fun sending those 'Magic Packets'. Give WOL a try - it's free.
The Main Event - Starting PLA
Windows 7 and Server 2008 do not have an Alerter service, this is why I now use PLA (Performance Logs and Alerts) to test PowerShell's start-Service.
# PowerShell cmdlet to start a named service
Note 7: Observe how the speech marks are slightly different in this script
compared with the previous:
Note 8: I prepared the above script to help you appreciate the factors needed to control a Windows Service. It also reflects my thinking process of how I learn about a command. On the other hand, for a production script you could take a much more ruthless approach and simplify the script thus:
set-Service PLA -startuptype manual
The main reason to monitor your network is to check that your all your servers are available. If there is a network problem you want an interface to show the scope of the problem at a glance.
Even when all servers and routers are available, sooner or later you will be curious to know who, or what, is hogging your precious network's bandwidth. A GUI showing the top 10 users makes interesting reading.
Another reason to monitor network traffic is to learn more about your server's response times and the use of resources. To take the pain out of capturing frames and analysing the raw data, Guy recommends that you download a copy of the SolarWinds free Real-time NetFlow Analyzer.
In real life, you may want a script which ensures that services such as: Telnet, Messenger and Routing and Remote Access are Stopped. Just for testing, you may need a script which reverses start-Service, just to be sure that it really is working as designed. Either way, here is a script which stops the service defined by $srvName.
# PowerShell cmdlet to stop the Plug & Play service
Note 9: Observe how this script is the mirror image of the Start-Service script. It even disables the service once it has stopped. If you remember, when Example 1 wanted to start a service, it must first make sure the -startuptype is set to manual.
The '-Service' Family (Each member has a different verb)
Get-Service: Useful for listing
This Engineer's Toolset v10 provides a comprehensive console of 50 utilities for troubleshooting computer problems. Guy says it helps me monitor what's occurring on the network, and each tool teaches me more about how the underlying system operates.
There are so many good gadgets; it's like having free rein of a sweetshop. Thankfully the utilities are displayed logically: monitoring, network discovery, diagnostic, and Cisco tools. Try the SolarWinds Engineer's Toolset now!
Remoting with PowerShell Service
One aspect of remoting in PowerShell v 2.0 is simply to append -computerName xyz to the command that you ran on the local machine. For further research try:
Surprise! Get-Service is amongst the cmdlets that support remoting, but stop, start and restart-Service are not on the list. More bad news, stop, start and restart-Service really don't work on network machines. Thus you have to employ different techniques such as Get-WmiObject and InvokeMethod. Alternatively, you could enter-PSSession and then run restart-Service as if you were on the local machine. However, to get that working you have to first install and setup WinRM
If your mission is to master the start-Service command, commence with Get-Service. Once you have mastered the rhythm of the Get-Service verb-Noun pair, move on to the Start, Stop, and restart-Service family of PowerShell commands. For scripting purposes, make sure that you use the true Service Name, and avoid the Service's Display Name. A final piece of advice, open the Service GUI so that you can double-check that what your script is doing is what you intended.
If you like this page then please share it with your friends
See more PowerShell examples of process and service
Please email me if you have a better example script. Also please report any factual mistakes, grammatical errors or broken links, I will be happy to correct the fault.