Windows services can be configured to start when the operating system is started and run in the background as long as Windows is running. Alternatively, they can be started manually or by an event. Windows NT operating systems include numerous services which run in context of three user accounts: System, Network Service and Local Service. These Windows components are often associated with Host Process for Windows Services. Because Windows services operate in the context of their own dedicated user accounts, they can operate when a user is not logged on.
change the startup type. Acceptable startup types include:
Automatic: The service starts at system logon.
Automatic (Delayed): The service starts a short while after the system has finished starting up. This option was introduced in Windows Vista in an attempt to reduce the boot-to-desktop time. However, not all services support delayed start.
Manual: The service starts only when explicitly summoned.
Disabled: The service is disabled. It will not run.
change the user account context in which the service operates
configure recovery actions that should be taken if a service fails
inspect service dependencies, discovering which services or device drivers depend on a given service or upon which services or device drivers a given service depends
export the list of services as a text file or as a CSV file
The command-line peer of the Services snap-in is sc.exe, the "Service Control" utility. This utility is included with Windows XP and later.
Sc.exe's scope of management is restricted to the local computer. However, starting with Windows Server 2003, not only can sc.exe do all that the Services snap-in does, but it can also install and uninstall services.
Windows PowerShell can intrinsically manage Windows services via the following cmdlets:
In addition to the trio of snap-in, sc.exe and PowerShell, Windows also includes components that can do a subset of what the trio can do. net.exe can start, stop, pause or resume a Windows service. In Windows Vista and later, Windows Task Manager can show a list of installed services and start or stop them. MSConfig can enable or disable (see startup type description above) Windows services.
A Windows service is created using development tools such as Microsoft Visual Studio or Embarcadero Delphi. In order to be a Windows service, a program needs to be written in such a way that it can handle start, stop, and pause messages from the Service Control Manager. Service Control Manager is a component of Windows which is responsible for starting and stopping services.
The Windows Resource Kit for Windows NT 3.51, Windows NT 4.0 and Windows 2000 provides tools to control the use and registration of services: srvany.exe acts as a service wrapper to handle the interface expected of a service (e.g. handle service_start and respond sometime later with service_started or service_failed) and allow any executable or script to be configured as a service. sc.exe (Service Control) allows new services to be installed, started, stopped and uninstalled.
^"New Elevation PowerToys for Windows Vista". TechNet Magazine. Microsoft. June 2008. Retrieved 21 June 2013. "The service CmdAsSystem is configured as interactive whose support is being deprecated. The service may not function properly. The problem is that this script tries to create and start an interactive service. Interactive services will not function correctly due to Session 0 Isolation in Windows Vista."
^ ab"Command-Line Reference: Sc". TechNet. Microsoft. Retrieved 8 January 2014. "Windows 7, Windows 8, Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Vista"