SMS 2003 and Software Distribution - PowerPoint PPT Presentation

1 / 23
About This Presentation
Title:

SMS 2003 and Software Distribution

Description:

Software to be upgraded currently installed and not at latest version ... scheduled task calls .cmd, which calls vbscript program that reads the NWIS file ... – PowerPoint PPT presentation

Number of Views:47
Avg rating:3.0/5.0
Slides: 24
Provided by: slko
Category:

less

Transcript and Presenter's Notes

Title: SMS 2003 and Software Distribution


1
SMS 2003 and Software Distribution
  • Stana Kopczuk
  • DMS Project Lead
  • Tony Valencia
  • SMS 2003 Administrator

2
What will be talked about
  • Identify machines that receive the software
    deployments
  • Dynamic Query collections
  • Desktop Management Software (DMS) Exemptions
  • Package, Program and Advertisement settings
  • Phased deployments for maximum percentage of
    machines successfully patched

3
Software Distribution
  • Machines that receive the deployment
  • No DMS exemptions
  • Software to be upgraded currently installed and
    not at latest version
  • Machines that do not receive the deployment
  • DMS exemptions by rule or registered in NWIS
  • Software not installed

4
Desktop Management SoftwareDefined
  • DMS includes the applications required to
    manage machines with the following core
    features
  • Patching
  • Software Distribution
  • Hardware and Software inventory
  • At SNL more than one application is required to
    patch and distribute software to each platform
  • Windows platform
  • Patching achieved with WSUS
  • software deployments achieved with SMS 2003

5
Desktop Management SoftwareExemption Types
  • Exemptions by rule
  • Non-Sandia owned equipment, no client is
    installed
  • Servers exempt from patching
  • LAN exemptions exclude network equipment
  • Explicit DMS Exemptions requested by machine
    System Administrator in NWIS and approved by
    upper management, CSR and DMS Administrator
  • DMS Client installed, no patching
  • DMS client not installed, no inventory or patching

6
DMS Exemptions integrated with SMS 2003
  • Registry key populated and exemption collections
    built nightly
  • File generated from NWIS of machine names and a
    code representing exemption type
  • Windows server scheduled task calls .cmd, which
    calls vbscript program that reads the NWIS file
  • Populate SMS server registry key that SMS 2003
    uses to determine which machines are exempt from
    client installations
  • Populate pre-defined collections used for
    exemptions from software distribution with
    machines that exist in SMS All Systems
    collection

7
Software Distribution Collections
  • What is the advantage of building exemption
    collections?
  • Collections created from All Systems, minus
    exempted machines become the target machines for
    deployments
  • Collections are updated by a set schedule
    dynamically based on criteria stored in the
    database
  • Dynamic queries replace the use of makecoll.bat
    utility
  • Makecoll.bat utility used to create collections
    based on list of machines from a flat file
  • Dynamic query collections based on software
    deployment criteria and updated on a schedule
  • Deployments are limited to the collections that
    exclude the exempted machines

8
Software Distribution Collections
  • Dynamic Queries are used to build collection of
    machines for software deployments meeting
    deployment criteria
  • Machines are included in the collection based on
    a dynamic query of software and/or hardware
    inventory information
  • Collection changes daily (dynamic) as
  • New machines connect to the network and are added
    to the collection if meet requirements
  • Software is successfully installed on a machine
    and it drops out when machine inventory reports a
    successful update and the collection is updated.

9
Software Distribution Collection
10
Software Distribution Collections
  • SMS used primarily for software distribution of
    third party software and Office upgrades or
    installations.
  • ICA Client
  • Adobe Reader
  • Microsoft Communicator

11
Software Distribution Deployment
  • Successful installation dependent on
  • Healthy client
  • Software and/or hardware inventory
  • Collection update on regular schedule
  • First phase of the deployment
  • Customer receives text box/notification about the
    deployment
  • Customer can cancel the installation
  • Second phase of deployment the application is
    sent in silent mode at night requiring no
    customer interaction

12
Software Distribution Package
13
Software Distribution Program
14
Software Distribution Program
15
Software Distribution ProgramPhase One
16
Software Distribution Advertisement
17
Software Distribution Begins
18
Software Distribution ProgramPhase One Text box
19
Software Distribution ProgramPhase Two
20
Software Distribution AdvertisementPhase Two
21
Software Distribution
  • Machine saturation reaches 60 on phase one
  • One to two nights of silent deployment quickly
    updates another 15-20 with minimal impact on the
    customer
  • Phase two continues another week to complete the
    deployment

22
Software Distribution Success Story
  • Update software on a large number of machines in
    a quick and timely manner
  • Few problems reported to the Help Desk
  • Customers call to verify it is OK to click OK
    button on the text box
  • Customers call when the software updates cause
    problems with their machines, but they are
    minimal due to thorough testing by the SNL CSU
    deployment team -- but that is another story

23
  • Questions?
  • Thank you!
Write a Comment
User Comments (0)
About PowerShow.com