Run Program on Windows Startup

Application As Service

Run any application as Windows Service.

Application as Service will let your application:

Zoom

Application as Service core is a command line driven application. The graphical user interface (Application as Service GUI) is a front-end to console application which helps you grasp the overwhelming number of options and simplifies the whole process of installing and launching your application as service. However, if you find it more useful and convenient for your tasks to use command line, Application as Service will help you generate command line options to automate the process in future. Alternatively, you can install and start services using XML configuration file which guarantees simple integration and extensibility of Application as Service great features into your own application (OEM license only).

Finally, this software provides all possible functionality needed to run application as services you may think of, simplifying system administration chores and software development.

Use Application as Service software to:

• Launch application as a Windows service(32-bit and 64-bit applications are fully supported on Windows 2000/XP/2003/Vista)
• Launch application or program at system boot, i.e. before user logon (useful for keyloggers, surveillance utilities, etc.), or even run it in absence of any user session at all
• Run executable - 16 bit (Dos, Windows, OS/2), 32 bit, batch files, scripts (VBScript, JScript) - as a service
• Run program locally or on any remote computer
• Launch application on a specific date or at a specific time (useful for backup utilities, reminders, etc.)
• Run programs with specific user rights and process priority
• Have application automatically restarted in case of crash (useful for client/server utilities, database applications, etc.)
• Launch application only after specific Windows services are started (e.g., on which it is dependent), or start other applications before or after its launching
• Use standard input/output automatic redirection to files
• Record execution errors to the Event Log
• Run multiple processes in the same service context

Overview

• Run any application (32/64-bit and console ones, scripts like VBScript or JScript) as Windows Service
• Create and manage native system services in few clicks
• Easily connect to remote PC over local network or Internet and manage all remote services like your own
• Run application before users login into their accounts
• Run your application interactively (visible to users) or silently
• Minimize downtime by auto-restarting application once it is crashed
• Schedule your service to run at the exact time and periodically on the defined day of the week/month/year
• Advanced service dependencies mechanism allows you to run applications at the certain order
• Achieve higher fault tolerance with your software reporting private errors to the event log and automatically restarting on errors
• Define Load Order Group which your application belongs to
• Restrict/grant your application with execution rights by specifying user account name under which it is run
• Specify the process priority for your application (Normal/High/Real Time)
• Define CPU binding for multi-processor PCs
• Conveniently supply additional options and system environment variables for console and Windows application
• Run additional programs prior to the service startup, program start, stop or just after the service shutdown
• Take all benefits of multi-processor, multi-thread and 64-bit platforms
• On-the-fly service start-up type customization
• Gracefully close console and Windows applications
• Close various popup windows that your application might display
• Redirect STDIN, STDOUT and STDERROR streams to or from the file for console application
• Specify desktop on which you would like your application to run as service
• Works under Virtual Machines (VMWare and so on)
• Use XML configuration file to install the service
• Sample services of Calculator and Notepad can be optionally installed
• Run a GUI application under a different security context (even under NT 4.0). User passwords are entered by the administrator and users are not prompted