Boss Everyware \ Docs \ Monitoring multiple computers \ Deploying the loggers

Using the deployment package

To install the Logger on a number of computers easily and silently, use the Logger deployment package.

Logger deployment package is a single program file, which incorporates a setup utility, the logger executable files and configuration settings. Once launched, by hand or from a script, it installs and configures the Logger without showing any messages to the user.

How to use:

1 Create your deployment package

First, open Logger Configurator and set up the options as you want them to be used as configuration for installed Logger. Then click  . Set the path and file name for your package, then click 'Save'. The Logger deployment package is created.

2 Deploy Logger with the package

Copy the created package to a network share and run it on every computer you want to monitor:

• to install the logger permanently for all users of the computer, run the package in the context of an administrator's account. The package starts monitoring immediately. If the package is launched via Run As, the monitoring begins at the next logon.
• to monitor only a specific user, run the package within the user's session with the /u switch:
  
  f:\bossew\bedepl.exe /u
  
  This way the logger is extracted into a temporary folder and starts monitoring immediately. To monitor each session, use the option "Run with Windows", or schedule the package to run every time the user logs in (recommended for Terminal Services).
  
  This mode is also activated when the deployment package is running in the context of a user who does not have administrative credentials, even if there was no /u switch specified.
  
  This mode is recommended for use on Windows Vista with UAC turned on.

Important: Monitored users must have modify permissions to the log file folder.

To get more information about how Logger has been installed, set the package to create a setup log. Specify a setup log file as a command-line parameter when running the package, e.g.

f:\bossew\bedepl.exe f:\bossew\logs\pcsetlog.txt

where bedepl.exe is the name of the Logger deployment package, and pcsetlog.txt is the setup log. Setup log is not overwritten by subsequent installations, so you can use the one single setup log for all your Logger installations on different computers.

To run the deployment package remotely, you may consider using psexec.exe. How?
Psexec.exe is a well-known free remote execution tool made by Sysinternals, recently acquired by Microsoft.

See also:
How to control the logger?
Uninstalling a deployed logger
Getting Started - Case 2. Pete monitors usage of all the computers in the office