2.3 Automating Software Distribution

 < Day Day Up > 



With a growing population of PC and workstation users deployed across widely dispersed geographical locations—each potentially using different combinations of operating systems, applications, databases, and network protocols—software has become more complex and difficult to install and maintain. The ability to perform these tasks over a network from a central administration point can leverage investments in software, enforce vendor license agreements, qualify the organization for discounts on network licenses, and greatly reduce network support costs.

The complexity of managing the distribution and implementation of software at the desktop requires that IT managers make use of automated file distribution tools. By assisting a network administrator with tasks like packaging applications, checking for dependencies, and offering links to event and fault management platforms, these tools reduce installation time, lower costs, and speed problem resolution.

One of these tools is a programmable file distribution agent. It 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, these types of changes can be applied to each workstation or group automatically.

The agent can be set up to collect file distribution status information. The network administrator can view this information at the console to determine if files were distributed successfully. The console allows 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 on to the network at one or more workstations, the file distribution agent determines where to distribute files based on the primary user (owner) of the workstation. The owner is established the first time that a hardware or software inventory is taken of the workstation. Before automated file distributions are run, the hardware inventory agent is usually run to check for resource availability, including memory and hard disk space. Distributions are made only if the required resources are available to run the software.

Via scripts, the network administrator can define distribution criteria, including the group or station to receive files and the day or days on which the 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. The templates are displayed as a preset list of common file tasks. Using the templates, the network administrator can outline a file distribution script, and then use the outline to actually generate the script.

To help network administrators prepare for a major software distribution, some products offer routines called “wizards” that walk administrators through the steps required to assemble a “package.” A package is a complete set of scripts, files, and recipients necessary to successfully complete a distribution and install the software. To reduce network traffic associated with software distributions, some products automatically compress packages before they are sent to another server or workstation. At the destination, the package is automatically decompressed when accessed. When a file distribution job is about to run, target users receive a message indicating that files are about to be sent and requesting that they choose to either continue or cancel the job, or postpone it for a more convenient time.

Periodically, a scan is performed on all disk drives to maintain an accurate inventory of software, enforce vendor license agreements, and check for unauthorized copies of software. By tracking software usage, a company can reduce its software acquisition costs, since accurate usage information can be used to determine which applications are run most before deciding on upgrades and how many copies to buy. The network administrator can choose to be notified of the times when users are denied access to particular applications because all available copies are in use. This may identify the need to purchase additional copies of the software or pay an additional license charge to the vendor so more users can access the application simultaneously.



 < Day Day Up > 



LANs to WANs(c) The Complete Management Guide
LANs to WANs: The Complete Management Guide
ISBN: 1580535720
EAN: 2147483647
Year: 2003
Pages: 184

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net