Software Distribution

1
Software Distribution
Information Compiled From Presentation Notes

• Big Ten Engineering Computing Support
  Networking Conference
• 14 November 2002
• Steven Zydek University of Illinois
• Paul Oliphant University of Wisconsin

2
Distribution Approaches

• Illinois
• Uses NFS
• Ok for HPOX Solaris
• Experimented With AFS
• Developed a PERL script for a bare bones
  solution that will not go out of style
• Primary Issue Management
• A synchronizing program helps synchronize
  distribution ease management problems

• Wisconsin
• Uses AFS
• Works about 90 of the time
• The 10 of the time that it crashes, it really
  causes problems
• Moving away from SMS Winstall using Windows
  Applications Luncher for Novell
• Tightly integrated applications cause a problem

3
Applications License Services

• Wisconsin
• Has approximately 20 applications licenses that
  are centrally shared
• Employs a front end License Server that is behind
  a Firewall
• The Firewall is open to all College IP addresses
• Users outside the College MUST log into and the
  system to gain access through the Firewall.
• Individuals must use a secure login procedure
• The login includes a step-by-step user
  authentication process
• Licenses are issued for four hours can be
  renewed
• The license server maintains licenses issued and
  other information
• Maintains a listing of all available software and
  usage statistics

4
Iowas Approach

• Working hard to get all software server based
• Server based installs are much easier
• Servers have are connected to the backbone via
  GigE
• Have experimented with multiple tactics
• Servers distributed on different subnets
• Servers with multiple NIC connectivity to the
  backbone
• Most of the time servers are available the
  network is the least of their problems
• Using Install Shield to do MSIs
• Install Shield is expensive there are only 3
  available licenses
• Uses a dual software distribution approach
  Remote install process Winstall
• After the OS is installed, NIS Active Directory
  are used
• Push out applications rather than permitting user
  installs is a direction being reviewed
• Reboot all windows boxes at 0500 on Sunday morning

5
Michigans Approach

• Michigan sets up computers so that anyone in
  engineering can get access to any application on
  any system
• There is an interest in having the ability to let
  people choose the installed applications base
• This option is available with the MSIs
  information available at Real Men Dont Click

6
Penn States Approach

• Users are generally free to install any
  applications that best meets their needs
• University-wide licensed application are
  available on a College Information Server for
  access by College faculty and staff
• Access is gained through user ID and Password
  authentication
• A few high dollar value design applications are
  purchase at the College level
• License keys are maintained on both Unix and
  Windows license servers
• Keys are signed out on a first-come, first-served
  basis with no time limit for use
• Department specific licensed applications are
  managed and maintained at that level
• With the exception of Virus definition updates,
  no updates are pushed out from the College level