Software Push

[Jeremy Oberg]

This is slightly different than the original purpose of Windows based
clients, but a great place to look for how to maintain an infrastructure
(made by sysadmins after the last LISA conference.)

This provides a framework for your entire infrastructure. After reading
the whole site, I realized many points for Linux/Unix on the desktop
(for something that windows can not do.) It also explains why not to
push updates, but to let the client pull them.  It highlights:     
    * Remote management
    * Secure communications
    * Distributed Monitoring
    * Unattended network-based installation
    * Automatic host administration (no need to manually track or apply
changes to managed hosts)
    * Unified desktop and server management
    * Single System Image
    * Single Signon
    * Continuous, long-term live host management (no re-installation
needed to apply upgrades)
    * Ordered, validated changes to any given host
    * Prototype and class-based host definitions
    * A coherent framework for managing all of the above

http://www.infrastructures.org/

-Jeremy

----- Original Message -----
From: Hanasaki JiJi <hanasaki at hanaden.com>
Subject: Re: Software Push

> On a slightly parallel note...
> 
> Take a peek at the below URL for on-demand deployment to clients.
> 
> http://java.sun.com/j2se/1.4/docs/guide/jws/
> 
> Steven Elling wrote:
> > On Thursday 05 December 2002 14:18, Jonathan Hutchins wrote:
> > 
> >>Ok, one point that someone brought up in support of Novell is 
> that they
> >>already own Novell-based software management tools that can 
> automatically>>update workstation applications.  Windows uses SMS 
> to achieve this,
> >>although in my company they more often use an embedded Version
> >>Check/Update routine within an application that may require updates.
> >>
> >>What does a Linux Server environment offer that can push software 
> updates>>to (Windows NT/2000) machines?
> > 
> > 
> > When I worked in Sprint's ITFS as a Desktop Support Prof.  we had 
> > distribution servers --- running some form of UNIX --- we 
> connected to via 
> > telnet and scheduled software pushes to Windows systems 
> individually or as 
> > a group.  The software pushes could be individual programs or a 
> group of 
> > programs.  We could even pop in a DOS floppy and rebuild a system.
> > 
> > I can't remember the name of it but it worked really well.  It 
> could of 
> > worked better if Sprint's implementation wasn't so sh*tty.
> > 
> -- 
> = Management is doing things right; leadership is doing the     =
> =       right things.    - Peter Drucker                        =
> =_______________________________________________________________=
> =     http://www.sun.com/service/sunps/jdc/javacenter.pdf       =
> =  www.sun.com | www.javasoft.com | http://wwws.sun.com/sunone  =
> 
> 
> 
> majordomo at kclug.orgEnter without the quotes in body of message 
>