Process Lasso

[ main index ]

In the Enterprise

Process Lasso works wonders on servers. It can prevent a single process from monopolizing the server's CPU resources. We offer a special Server Edition of Process Lasso, with a 30-day free trial available. See this page for more information.

Process Lasso can be used on Terminal Servers, web servers, file servers, or more complex network client/server environments. In fact, it can be used in just about any scenario you can envision. The fact that the core engine is seperate from the GUI makes it easy to install without it being visible to the end user.  You can even run the core engine as a system service and perform silent installs, feature many network admins will appreciate.

Methods of Deployment

The big question is whether you want to use a centralized network configuration and log store, a per-machine store, or a per-user store.

Option 1: Centralized configuration and log

In this mode, all workstation are configured to use the same configuration file and log folder. These can be on network shares, or can be pushed out to workstations through alternate methods.

Option 2: Per-workstation configuration file and log

In this mode, you'd install Process Lasso on each workstation and use a common configuration and log path that every user of the workstation would access.

Option 3: Per-user configuration file and log

In this mode, you'd install Process Lasso on each workstation and let each user have their own configuration and log. This is the default behavior of Process Lasso. If you don't need or want to make changes to the configuration or modify the log files, this is a good way to run Process Lasso.

Option 4: Some combination of the above, or an alternate method

In the end, you can utilize Process Lasso just about however you want. You could have workstations launch it from a network share, for instance, without ever having to install Process Lasso on those workstations. The prerequisites to running Process Lasso are very few. A single COM control (ProcessControl.dll) should be registered, and older systems (XP before SP2) will require Microsoft's GDIPLUS.DLL to be installed before the Process Lasso GUI can run. However, the core engine does not require the GDIPLUS library to be present.

Service Mode

You can install Process Lasso's core engine, processgovernor, as a service. This option is presented to you during the install process of Process Lasso Pro. It is also available during silent installs using the command line switches.

Running the core engine as a service has its advantages as disadvantages. There are a few minor caveats to running the core engine as a service, so be aware of them.

Silent Installation

Process Lasso (as of v3.53) now supports completely silent installation. For more information, see the command line switches documentation.

More help?

If you have any questions about getting Process Lasso up and running in your enterprise, please email us at support@bitsum.com. Customized solutions are also available.