A Networked Machine Management System 16, 1999.

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

Transcript of A Networked Machine Management System 16, 1999.

Page 1: A Networked Machine Management System  16, 1999.

A Networked Machine Management A Networked Machine Management SystemSystem

http://www.roth.net/ July 16, 1999

Page 2: A Networked Machine Management System  16, 1999.

Needs AssessmentNeeds Assessment

Collect information in timely manner Automate Installation of software Perform routine maintenance Alert team of problems

Page 3: A Networked Machine Management System  16, 1999.

Needs AssessmentNeeds Assessment (cont.)(cont.)

Inexpensive Solution!Inexpensive Solution!

Page 4: A Networked Machine Management System  16, 1999.

Scr

ipts

Scr

ipts

The InfrastructureThe Infrastructure

Script is any executable task– Applications

winword.exe– Batch files

cleantmp.bat– Perl scripts

perl c:\tools\report.pl

Page 5: A Networked Machine Management System  16, 1999.

Scr

ipts

Scr

ipts

The InfrastructureThe Infrastructure

Script development– Perl• Very versatile• Extendible• Fast development Cycle

(cont.)(cont.)

Page 6: A Networked Machine Management System  16, 1999.

Scr

ipts

Scr

ipts

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.

The InfrastructureThe Infrastructure (cont.)(cont.)

Page 7: A Networked Machine Management System  16, 1999.

Rep

osit

ory

Rep

osit

ory

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.

The InfrastructureThe Infrastructure (cont.)(cont.)

Page 8: A Networked Machine Management System  16, 1999.

Sch

edul

erS

ched

uler

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.

The InfrastructureThe Infrastructure (cont.)(cont.)

Page 9: A Networked Machine Management System  16, 1999.

Sch

edul

erS

ched

uler

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.

SecuritySecurity

Page 10: A Networked Machine Management System  16, 1999.

Rep

osit

ory

Rep

osit

ory

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.

SecuritySecurity (cont.)(cont.)

Page 11: A Networked Machine Management System  16, 1999.

Variety of ScriptsVariety of Scripts

Configure ODBC drivers and Data Source Names

Collect system informationScan Event Log for anomalies

Page 12: A Networked Machine Management System  16, 1999.

ConclusionConclusion

Interactive web based status reportsLearning 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.

Page 13: A Networked Machine Management System  16, 1999.

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/