Additional Features complimentary to Citrix...

Below is a list of frequently asked questions and their answers

	What does it do?
	Hangman is software that monitors process CPU usage and performs actions should certain criteria be exceeded. Typically this will involve warning the user of the problem and then terminating the offending process. The product is fully configurable with the ability to exclude specific users and processes, set per-user and per-process thresholds and to configure an unlimited number of criteria & associated actions.
	Why would I need it?
	How many times have you had users complaining that the server is running slow, only to find that one of them has a process running that is chewing up all the CPU? Hangman reduces the impact of run-away processes on multi-user servers by automatically performing actions such as killing the process. Because it runs 24x7 it takes care of your users even when you can't.
	What Operating Systems are supported?
	Hangman is specifically written for Windows NT 4.0 Server Terminal Server Edition and Windows 2000 Server. The product will work with or without Citrix MetaFrame installed.
	What do I get?
	The software consists of a single executable, which gets installed as an NT service. It also comes with a configuration utility and help file.
	How does it work?
	Hangman automatically starts when the server is booted and runs 24x7, monitoring process CPU usage. Should any process exceed the defined criteria the configured actions will automatically be performed.
	How do I configure it?
	Configuration is performed through a Control Panel applet - full details are included with the product.
	Does it use much resource on the server?
	No, normally the service uses much less than 1% CPU. Even on a busy server with 50 users and 500+ processes running, the service still only takes 1% CPU on average.
	Do I have to list all processes or users to monitor?
	No, there are default settings that can be overridden for specific users or processes.
	How does it work in a multi-server environment?
	Each server maintains it's own configuration although you may specify a server from which the configuration will be replicated during service startup, thus allowing enterprise-wide configuration. Note that because the configuration is replicated to the local server, even if the master server is not available, it will simply start with the cached configuration information.
	Do I install it on every computer?
	Hangman has been written explicitly for the multi-user NT operating systems listed earlier. As such, you only install it on those servers you wish to control.
	Does it provide an audit trail?
	Yes, all actions are logged to the event log, which can either be the servers local event log or that of a specified server.
	Does it work across multiple NT domains?
	Yes because the criteria is defined by username and ignores domain information.