Please let us know how useful you find this tip by rating it below. Do you have a useful Windows tip, timesaver or workaround to share? Submit it to our tip contest and you could win a prize!

Windows services are designed to run without user interaction. They can be started before any user logs in, obviating the need for a particular user to log in and run them, either manually or automatically. Many programs are designed to run as services or to exist in dual implementations as a service and a standalone application.

Some applications, however, just aren't available to run as a service. What do you do if you want one of those applications to run as one?

I've looked into a number of different programs that allow administrators to run NT programs as services, and there are more being written and updated as I write this. Right now, the best noncommercial program for running apps as services appears to be NT Wrapper.

NT Wrapper Lite, the freeware version, offers numerous features: It lets programs or scripts run as services, redirects stdout/stderr output to a file for troubleshooting (a handy feature for console apps) and prioritizes subprocesses. NT Wrapper Pro (the commercial version, which is sold on a license basis) offers even more advanced functions, such as binding the application to a specific CPU and remotely administering services.

Once installed, NT Wrapper Lite lets you add and configure the programs you want to run as services through a GUI interface -- which does not need to be running to use NT Wrapper). You can launch programs in the LocalSystem context (the default) or as another user if needed and create a custom launch environment (variables, etc.) for each application.

The advanced version of the program, NT Wrapper Pro, can be set to have dependencies on or for other services -- i.e., it can be set not to run unless another service is running and vice versa. Note that you may need to experiment to determine the correct combination of user contexts to get some services running correctly.

Editor's Note: If you would like to receive similar tips on how to manage Windows as well as other expert advice, be sure to subscribe to The Administrator Tip newsletter. Sign up now!

Serdar Yegulalp wrote for Windows Magazine from 1994 through 2001, covering a wide range of technology topics. He now uses his expertise in Windows NT, Windows 2000 and Windows XP as publisher of The Windows 2000 Power Users Newsletter and writes technology columns for TechTarget.

This was first published in March 2005

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.