Re: Deploying Red Hat Workstations

From: Michael Mansour (micoots_at_yahoo.com)
Date: 03/17/04

  • Next message: Swamper: "Re: Unscribe question" 
    Date: Wed, 17 Mar 2004 13:21:51 +1100 (EST)
To: For users of Fedora Core releases <fedora-list@redhat.com>

    Hi,

     --- Christopher Ness <nesscg@mcmaster.ca> wrote: > On
    Tue, 2004-03-16 at 12:48, Chris Purcell wrote:
    > > 1) each workstation would execute a cron job daily
    > that would download a
    > > script from our central server each day
    > > 2) that script would be executed by another cron
    > job a few minutes later.
    > > This script will contain any changes that I need
    > to make. If there
    > > aren't any updates for the day, then the script
    > will be blank that day.
    >
    > You will likely want some feedback about what
    > succeeded and what
    > failed. Assuming every install is successful would
    > be a mistake.
    > Have each machine upload the results or email them
    > to someone.
    >
    > > Will this work? There has to be something better
    > than this out there.
    >
    > Sure it will work. But...
    >
    > Why not create a local "up2date" server on your LAN
    > that will only hold
    > the packages you want your machines to have. I'm
    > assuming you want them
    > all to be the same, correct. Then set up2date to
    > update automatically
    > from the 'up2date' local server. Very little
    > outgoing network traffic
    > and you control the packages/versions. Seems good
    > to me.
    >
    > I'm not sure how to set up an "up2date/yum/apt-get"
    > server but maybe
    > someone else has some experience.

    Webmin has the ability to "Cluster" machines. In this
    type of configuration I'd seriously take a look at
    Webmin to manage these machines and Cluster update
    anything I need to update. It also has the ability to
    run cluster crons, synchronise users and groups among
    all members of the cluster, update RPM's, deb's, etc
    packages across the cluster and so on.

    I use it on around 10 servers at the moment, and find
    it extremely useful. With the number of workstations
    you seem to want to manage, I reckon this would be a
    pre-requisite.

    Michael.

    Find local movie times and trailers on Yahoo! Movies.
    http://au.movies.yahoo.com 

    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Swamper: "Re: Unscribe question"

    Relevant Pages

    • Re: How to Create a TCP/IP PrinterPort on a MS Cluster 2k3 via Scr
      ... XP is not in the cluster so I'm not clear on the failure question. ... the user running the script should be admin on the remote print server. ... thus the creation of the port on the node. ...
      (microsoft.public.windows.server.clustering)
    • Re: How to Create a TCP/IP PrinterPort on a MS Cluster 2k3 via Scr
      ... XP is not in the cluster so I'm not clear on the failure question. ... the user running the script should be admin on the remote print server. ... thus the creation of the port on the node. ...
      (microsoft.public.windows.server.clustering)
    • Re: Network Load Balancing Problem
      ... Are you trying to test NLB from one of the NLB machines? ... MVP - Windows Server - Clustering ... With NLB manager in the Server1 i create new cluster ... the cluster response only with the second host, ...
      (microsoft.public.windows.server.clustering)
    • Re: VBS will not run on some machines, NO errors
      ... Establish sorted file list pictures of good vs: bad machines. ... Alternatively invoke "context menu" inf install. ... "When I go to a command prompt on this server and type Wscript.exe" ... When I state that we tried to run the script manually, ...
      (microsoft.public.scripting.wsh)
    • Measuring System Utilization Over Time
      ... Our current server roster has grown to the point ... This step will identify which machines are good candidates ... I figure that sar is the best way to capture usage statistics over time. ... By default sar only holds reports for 7 days so I modified the sa2 script ...
      (SunManagers)