1 / 13

A Networked Machine Management System

A Networked Machine Management System. http://www.roth.net/. July 16, 1999. Needs Assessment. Collect information in timely manner Automate Installation of software Perform routine maintenance Alert team of problems. Needs Assessment. (cont.). Inexpensive Solution!. The Infrastructure.

berny
Download Presentation

A Networked Machine Management System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Networked Machine Management System http://www.roth.net/ July 16, 1999

  2. Needs Assessment • Collect information in timely manner • Automate Installation of software • Perform routine maintenance • Alert team of problems

  3. Needs Assessment (cont.) Inexpensive Solution!

  4. The Infrastructure • Script is any executable task • Applicationswinword.exe • Batch filescleantmp.bat • Perl scriptsperl c:\tools\report.pl Scripts

  5. The Infrastructure (cont.) • Script development • Perl • Very versatile • Extendible • Fast development Cycle Scripts

  6. The Infrastructure (cont.) • Script Execution Tracking • Each script maintains a log on each machine indicating if it has already been run. • Prevents multiple execution of scripts which only run once. • No need to remove already run scripts from repository. • Allows new machines to run scripts which. Scripts

  7. The Infrastructure (cont.) • Script Repository • Shared directory centrally located on a server. • The repository directory tree was part of a replication tree across other domain controllers. • When the engine starts it locates a domain controller and uses it as the repository. Repository

  8. The Infrastructure (cont.) • Scheduler Service • Scheduler service configured to run the engine at predetermined time. • Each machine set to run engine at a unique time to prevent network traffic storms. Scheduler

  9. Security • Scheduler Service • Configured to logon as a domain account (SchedulerAccount). • Domain account was a member of the Domain Admins group. • Added the Domain Admins group into each machines local Administrators group. Scheduler

  10. Security (cont.) • Repository Permissions • Shared directory was hidden by appending a $ to the share name. • Share permissions only allowed Administrators FULL and SchedulerAccount READ access. • Directory tree secured with the same permissions as on the shared directory. Repository

  11. Variety of Scripts • Configure ODBC drivers and Data Source Names • Collect system information • Scan Event Log for anomalies

  12. Conclusion • Interactive web based status reports • Learning Perl benefited not only this project but others as well. • Substantial cost savings. • First use for software deployment took only 4 hours with no human supervision. Compare this to 100 hour man hours at overtime pay.

  13. Online version of presentation available at: http://www.Roth.Net/Conference/LisaNT/1999/ Perl is available from: http://www.Perl.com/ http://www.ActiveState.com/

More Related