Lecture 9 - PowerPoint PPT Presentation

1 / 20
About This Presentation
Title:

Lecture 9

Description:

Linux - Red Hat 9 Customization Guide, Section V (Package Management). You should pay particular attention to Ch. ... zap Zero Administration Package ... – PowerPoint PPT presentation

Number of Views:61
Avg rating:3.0/5.0
Slides: 21
Provided by: ets97
Category:
Tags: lecture | zap

less

Transcript and Presenter's Notes

Title: Lecture 9


1
Lecture 9 10 Software Management
  • Reading
  • Windows - W2KER section 6.3, ch. 7 (also
    http//www.serverwatch.com/tutorials/print.php/149
    7871 and http//www.serverwatch.com/tutorials/prin
    t.php/1497901)
  • Linux - Red Hat 9 Customization Guide, Section V
    (Package Management). You should pay particular
    attention to Ch. 32 (also the authoritative
    reference for RPM and LAH Ch. 23)
  • Common Ground
  • Windows Specifics
  • Linux Specifics
  • Updating and managing software

2
Common Ground
  • What's Common?
  • Everyone needs software
  • What does software installation require?
  • Files added or updated
  • Directory services updates (e.g., changes to
    /etc/services, new DNS aliases)
  • Becoming accessible to users (e.g., showing up in
    a Start Menu, or in a user's PATH)
  • Localization (i.e., what is different from the
    system as shipped by the vendor vs. what you need
    locally).
  • Install it yourself
  • Give list of packages and pay third party to
    install it

3
Common Ground (cont.)
  • Inventory (i.e., what do you have?)
  • Managing changes
  • Versioning your build
  • Rogue users and departments
  • Testing
  • Make changes reversible (n.b. undoable and
    reversible arent the exact same concepts).
  • "reversible" means that you can do some
    well-defined set of steps to both do an operation
    forwards, as well as backwards
  • "undoable" means you can get back to the original
    state, but may require a much more cumbersome
    process
  • Revision control policy and process
  • Software location policies (client vs. server,
    which directories/drives are for user software,
    etc)

4
Common Ground (cont.)
  • Interactive installation vs. automatic
    installation
  • Timing of installation and updates (vendor driven
    vs. SA driven vs. user driven)
  • Fat clients vs. thin clients (with fat servers)
  • Question one old rationale for thin clients was
    the high cost of disks. Now that disks are
    cheaper, some argue that fat client is better.
    What other factors need to be considered in
    making a decision between fat and thin client?

5
Windows Specifics
  • Registry and system folder combine to encourage
    fat client
  • Microsoft encourages fat client installation
  • DLL Hell (different applications needing
    different versions of core DLLs)
  • Current methods for installation rely on GPO
    (Group Policy Object)

6
Windows Specifics (cont.)
  • Three ways of Installing Software using AD
  • Publishing applications (make available for end
    users to install)
  • Assigning applications to computers (installs
    onto system)
  • Assigning applications to users (installs desktop
    and/or Start Menu shortcuts, but the first use
    actually does the install)

7
Windows Specifics (cont.)
  • .msi Windows Installer Database
  • .msp Windows Installer Patch
  • .mst Windows Installer Transform
  • .zap Zero Administration Package
  • WinINSTALL LE (and similar products) can be used
    for packaging software that does not provide a
    native installer

8
Windows Specifics (cont.)
  • Other ways of installing software
  • Copy files locally and update desktop and/or
    Start Menu
  • Copy files onto server, and update desktop and/or
    Start Menu
  • Run vendor-supplied installation package (often
    just like Assigning to computers, but may not be
    if the package doesn't update the list of
    installed software).

9
Windows Install Exercise
  • When would we want to Publish software?
  • When would we want to Assign to a User?
  • When would we want to Assign to a Computer?
  • Are there other ways of installing software
    beyond what was covered in the lecture?
  • Lets take a look at how this is done in a Group
    Policy!

10
Digressions on HW5
  • Linux - UID
  • Minimum?
  • Maximum?
  • Create user (test1) and set password
    (notsosimple)
  • Will Useradd p notsosimple test1 work?
  • Lets SSH to Einstein and try
  • Create user with command
  • Log in as user

11
Digressions on HW5 (cont.)
  • Linux GID must it be in /etc/group?
  • What happens if we do the following?
  • Create a User
  • This creates a UID and GID
  • Delete the users Group from /etc/group

12
Digressions on HW5 (cont.)
  • Windows - Groups
  • Nesting Groups ???
  • Local groups
  • Domain based groups
  • Domain local groups
  • Universal groups
  • Global groups
  • Grant permissions to user or group
  • Base groups on security needs

13
Digressions on HW5 (cont.)
  • Password restrictions
  • Can Windows enforce a complex password?
  • Can Windows enforce password length?
  • How Windows domain authentication works
  • Locate server
  • Authentication protocol
  • Other tasks

14
Linux Specifics
  • Unix world often thin client and fat server
  • Some vendors have packaging solutions
  • Traditionally
  • Download source (assume it's src.tgz)
  • gunzip -c src.tgz tar xvf -
  • cd src
  • read README
  • read INSTALL
  • edit Makefile
  • edit source code
  • make
  • make install

15
Linux Specifics (cont.)
  • More recently, it's
  • Download source (assume it's src.tgz)
  • gunzip -c src.tgz tar xvf -
  • ./configure
  • make
  • make install
  • Upgrade? Symbolic links to provide canonical
    names.
  • Uninstall? Who would ever do that?

16
Linux Specifics (cont.)
  • RedHat uses rpm
  • rpm ivh package (install, verbose, w/hashes)
  • rpm qa (query for all installed package(s))
  • rpm ql package (list all files in a package)
  • rpm -qi package (provide package info)
  • rpm -Uvh package (upgrade, verb/hashes)
  • rpm -e package (erase)
  • Lack of ability to build programs from source may
    hinder your growth as an SA. Also, some
    experience with C (or C) can be important, as
    there may be times when you are asked to debug
    code issues (in the form of buggy software from
    vendors, on both Windows and Unix).

17
Linux Install Exercise
  • Lets play with RPM
  • Install from source?

18
Updating and Managing Software
  • Windows
  • Widowsupdate / autoupdate
  • Officeupdate
  • SUS/WUS
  • SMS
  • Lets look at Windows Update WUS

19
Updating and Managing (cont.)
  • RedHat
  • RedHat Network / up2date
  • RHN Proxy
  • Lets look at RHN

20
Up Next
  • Before next class
  • Homework 6 Web and FTP (Due 11/10)
  • Readings -
  • W2KER 3.4 (also LAH Ch. 18, ESA pp328-329, man
    xinetd, man xinetd.conf, man nsswitch.conf, Linux
    Network Administrator's Guide, second edition,
    Ch. 13 (available on Safari) or the NIS HOWTO for
    Linux)
  • Next class
  • Service Management
Write a Comment
User Comments (0)
About PowerShow.com