Previous | Table of Contents | Next |
A file distribution agent is a tool that is used to automate the process of distributing files to particular groups or workstations. A file distribution job can be defined as software installations and upgrades, start-up file updates, or file deletions. Using a file distribution agent allows these types of changes to be automatically applied to each workstation or to a specified group of workstations.
The agent can be set up to collect information on file distribution status, which the systems administrator can view at the console to determine if files were distributed successfully. The console provides view formats and types that allow the administrator to review status data, such as which workstations are set up for file distributions, the stations to which files have been distributed, and the number of stations waiting for distributions.
Because users can be authorized to log in at one or more workstations, the file distribution agent determines where to distribute files based on the primary user (i.e., owner) of the workstation. The owner is established the first time an inventory is taken of the workstation. Before automated file distributions are run, the hardware inventory agent is usually run and distributions made only when the owner is actually working at the station.
Using scripts, the systems administrator defines distribution criteria, including the group or station to receive files and the day or days on which files are to be distributed. Scripts usually identify the files for distribution and the hardware requirements needed to run the file distribution job successfully. Many vendors provide templates to ease script creation that are displayed as a preset list of common file tasks. Using the templates, the systems administrator outlines a file distribution script and then uses the outline to actually generate the script.
The ability to monitor network activity allows the systems administrator to ensure the effectiveness and efficiency of network services. An event manager agent is used to track network activity (i.e., events), log network activity, and automatically alert the individual responsible for responding to certain network occurrences. Any network occurrence can be considered an event, from running the virus scan program, to logging in to the network, to performing a network backup.
The systems administrator specifies the network activity to be tracked, such as the times when users log in and out of the network or when programs are run. Network activities that may require immediate attention are also specified. A notification feature can be set to alert the systems administrator, or the person responsible, of the times when these events occur. Different notification methods can be set as appropriate for each network event.
Event notifications can be processed based on priority level. For example, if three network events occur simultaneously, notification of the event with highest priority is sent first. Priority levels range from a low of one to a high of nine. When the systems administrator specifies the network activity to monitor, a priority level for each event is assigned based on how critical the activity is and whether someone has to be notified when the event occurs.
The following methods of event notification are typically available:
The systems administrator chooses one or more contacts to receive notification of each event level. For example, a technician can be specified to receive a pager message when high-priority events occur, and a help desk operator can be specified to receive an E-mail message when routine application-related events occur. An acknowledgment of receipt for event data can be sent to the console to help ensure a proper response to events.
A scheduling agent is an application used to organize and run jobs. A typical job can be running a command for network backup or sending a broadcast message to users before the backup begins. Instead of having to keep a written log of jobs and remembering to run them, the systems administrator uses a scheduling agent to specify that the jobs run automatically at a certain time. For example, the systems administrator could schedule the system backup process for 2 A.M. a time when the system is not likely to be heavily used. At the specified time, the scheduling agent automatically starts jobs unattended. The job specifications can be saved and updated whenever necessary, and jobs can be changed or deleted at any time.
The scheduling agent can also provide job completion information, such as whether the job ran successfully, when it ran, and the next time it is scheduled to run. Following are examples of jobs a scheduling agent streamlines:
A scheduling agent can implement jobs that run once or at these regular intervals: hourly, daily, weekdays, weekly, monthly. Instead of being run individually, jobs can be grouped to accomplish multiple tasks. An entry can be posted in the event log after jobs are completed that tells the systems administrator when the job started and ended. For example, with regard to scheduling the network virus scan process, the scheduling agent can automatically add a record to the log of network events provided by the event agent.
Previous | Table of Contents | Next |