In Windows NT operating systems, a Windows service is a computer program that operates in the background. It is similar in concept to a Unix daemon. A Windows service must conform to the interface rules and protocols of the Service Control Manager, the component responsible for managing Windows services.
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 the 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.
Kalipso applications aren’t designed to be installed as user-defined services since they don’t have by design, several characteristics and behaviors specific to a Windows Service. As a workaround, in case that an application needs to be installed as a Windows Service, the user can try at its own risk, one of two ways:
- Use a service wrapper in order to be able to run the application as a service that provides a GUI (Graphical User Interface) to select the executable.
- Create a User-Defined Service using Command Line, Registry Editor, and some tools available in the Windows NT Resource Kit to install the Kalipso Application and use it as a service.