STARR Professional contains support for deployment and use on Local Area Networks (LAN).

A. Create individual log files (and reports)

You can create individual log files for each user and/or each PC by simply adding the <PC> and/or <USER> tags in the STARR log file name. Other available tags are <DATE>, <TIME>. STARR will automatically parse and replace the tags with the current PC name, user name, date or time.  

Example: 

You name the log file "log_<USER>.sys". Your users ( = user login name) are "PeterBrown", "AnnSmith" and "Administrator".

Starr creates the following log files:

1. log_PeterBrown.sys

2. log_AnnSmith.sys

3. log_Administrator.sys

Note: On Win 9x/ME systems it is possible that a user does not log in. In this case, and for everything that happens before a login, the <USER> tag is replaced with "Nobody" so the recorded information can be examined separately.

B. Setup options for LAN networks

For log file storage and reporting there are two recommended options:

1. Store the STARR log file on a Administrator PC. 

With this option no data is stored in the Client PCs. On the  Administrator PC you can use the STARR Commander to create reports. For this option to work well the Client PC should have a permanent LAN connection. To rename the log file go to STARR Commander >> SETTINGS TAB >> Click ADVANCED SETTINGS. If it is not (e. g. laptops !) we recommend option 2:

2. Save the ready to use reports on the Administrator PC. With this option the STARR log itself is kept on the PC (unless you use option 1 as well). STARR sends the ready-to-use reports over the LAN to the Administrator PC. To rename the report file names go to STARR Commander >> EMAIL / LAN TAB >> Click LAN SETTINGS.

Note: 
If you use option 2 you do not need to install the program on the Administrator  PC (Server) but only on the workstations that you wish to monitor. If you have a peer-to-peer network without a server STARR will work equally well. The only requirement is a single shared folder that all machines have read/write access to. To create a shared folder that other workstations cannot see, append a "$" character to the folder's share name (i.e. "STARR$"). This folder should be on the server but it can be on any machine on the network. The network transport protocol is unimportant.  STARR clears old records on the CLIENT PC automatically and needs no maintenance.

By using a shared folder the STARR reports (and the STARR log file)  is always available to the Administrator - even if the source machine has been shut down.

C. STARR Deployment

Deploying STARR in a network is done by cloning the settings of a SOURCE machine. Since STARR is written as a very compact software only a few files are needed. The installation is transparent and can be easily automated. The source machine can be any PC on the networking running STARR, including this PC.

Remote Deployment for Networks is available to all users with a multi-user or site-license.

Typically there are 3 ways to deploy STARR:

Option 1: Network install

Copy all logging engine files to the appropriate folders on the CLIENT PC. To automate the first startup, copy "starr.lnk" to the start-up folder of the machine:

Directly after the first start the logging engine completes the setup. This includes removing the start-up link and replacing by a more secure startup mechanism. Also, the "starr.ini" file is automatically deleted.

Option 2: Use Login Script

This is the best option for large networks and where file sharing is not practical. Your login scripts needs to copy all logging engine files to the target machine and start the logging engine. After it is started, the logging engine invisibly completes the setup and deletes the "starr.ini" file automatically.

Option 3: Manuall installation using a "Clone" disk or network path. 

This is the most simple option and can be used where option 1 and 2 are not practical: Simply copy all logging engine files in the appropriate folder on the target machine and start the logging engine once. After it is started, the logging engine invisibly completes the setup and deletes the "starr.ini" file automatically.

Note 1: The table the complete list of all necessary  files can be found here .

Note 2: When you need to update the settings, create a new "starr.ini" file and copy to the client PCs. The logging engine automatically picks it up, reads the settings and deletes it at the next start up.

D. How to store the settings ("starr.ini" file)

To create the starr.ini file (needed for option 1 - 3) and the "starr.lnk" (needed for option 1) start STARR Commander. Then go to EMAIL / LAN >> LAN SETTINGS and click "STORE SETTINGS": The ready-to-use files are created.

Note: For easy testing, not only the logging engine (wsys.exe) can read the "starr.ini" file but also the STARR Commander.

E. Notes to Network Administrators

1. Make sure that the network (or local) directory exists and has full access rights (read and write) for all users! If a directory does not exists, STARR will ask you to create it when you press the "TEST" button on the LAN options page. 

2. There is no limit to the size or type of network that STARR is installed on, and there are no requirements for any particular transport protocols. STARR is currently running on small peer-to-peer office networks and multi-server networks with 100+ machines, with mixed operating systems including Windows 95/98/Me/NT/2000 and Novell.

3. All you need is one shared folder on the Network. STARR will work on any machine that can write to that folder. Create an invisible shared folder by adding a "$" sign to the share name so that the end users cannot see it in Network Neighborhood. 

4. The number of Client PC installations ("logging engine") allowed on your network is embedded in your license key. Installation of the STARR Commander are unlimited

5, If the connection to the network folder is lost at any point, STARR will  save all information locally and resends it once the network connection is established again.  This is especially important for a laptop that may be disconnected for long periods.

6. To make sure you have the correct path, we recommend that you use the "Browse" button on the LAN options page. There must be a slash "\" at the end of the directory path. If you forget it, STARR will add it for you :-)

7. STARR Commander has a command line option "-convert" for an easy (automated) conversion of STARR log files into reports:

8. You can use the remote deployment also to disable a STARR installation: Disable "Autostart" in the STARR Commander and create a new "starr.ini" file. Once this file is placed in the same directory as the logging engine (wsys.exe) the logging engine will read this file at the next start and stop itself from running at the following PC start.

9. Share Name Hint: You can setup an "invisible share" by proceeding you share name with a dollar sign ($). An invisible share is not shown in the list of shares on your computer, but can still be accessed by the share name (example: \\my-computer\shared$ where "my-computer" is the name of your computer on the network an "shared$" is the name of your hidden share).