Software Distribution Overview

Prepared By:

Melvin Brewster

Chaofeng Yan

Sheng Shan Zhao

Khanh Vu

8/24/00 Group V 2

Objectives

• Give an overall picture of application/software distribution

• Explain the concept of Automated Deployment

• Introduce distribution software– Ghost, Drive Image Pro, IC3 and MSM Server

• Explain the concept of System Management

8/24/00 Group V 3

Modules

• Concept of Automated Deployment and Introduce Microsoft System Management Server

• MSM Server Cost and Terms• MSM Server Procedures for Software

Distribution• Deploying Windows 95 Upgrade with

MSM Server

Module 1:

Concept of Automated Deployment

Presented by: Khanh Vu

8/24/00 Group V 5

Objectives

• Explaining “Partition-image replication”

• Introduce distribution software:– Ghost– Drive Image– IC3– Microsoft System Management

8/24/00 Group V 6

Partition-image Replication

• Create a properly configured PC

• Create sector-by-sector file of active disk partitions

• Copy image file onto new PCs via LAN or removable drives

8/24/00 Group V 7

Distribution Software

• Symamtec - Norton Ghost

• PowerQuest - Drive Image Pro

• ImageCast - IC3

• Microsoft Systems Management Server

8/24/00 Group V 8

MicrosoftSystem Management Server

Overview

8/24/00 Group V 9

Managing Distributed PC The Historical Way

• Labor-intensive

• Time consuming

• Expensive in large organization

• Unreliable inventory information

• Disrupted end user activities

8/24/00 Group V 10

Managing Distributed PCs With MSM

• Increase efficiency

• Reduce expenses

8/24/00 Group V 11

MSM Increase Efficiency

• Management has specific configuration information

• Software distribution can be automated from a central location

• Help desk personnel can diagnose and solve problem remotely

8/24/00 Group V 12

MSM Reduces Expenses

• Cheaper and more accurate• Automated software distribution reduces

installation and configuration cost• Reduces helpdesk staff

– User’s configuration can easily obtain and update

– Access to remote troubleshooting tools– No need to visit workstation

8/24/00 Group V 13

End of Module

Module 2:

Cost and Terminology

Presented by: Sheng Shan Zhao

8/24/00 Group V 15

Objectives

• Emphasize the Cost efficiency of using Distribution Software

• Define Terms related to Microsoft System Management – Site Terms– Server Components

8/24/00 Group V 16

Cost If No Software Distribution

• Installation

• Technical Support

• Administrative tasks

8/24/00 Group V 17

Installation

• Task Best Case Worst Case

• Technician travel time 0.10 0.50• Backing up hard disk 0.10 0.75• Hard disk housekeeping 0.20 1.00• Installation of Windows 95 0.20 1.00• Testing of new configuration 0.10 0.50

8/24/00 Group V 18

Technical Support

• Task Best Case Worst Case

• Help desk calls 0.17 0.50• Tier-2 support calls 0.33 0.67• Peer-support calls 0.17 0.33• User disruption 1.00 2.00

8/24/00 Group V 19

Administrative Tasks

• Task Best Case Worst Case

• Filling out forms 0.00 0.50• Updating inventory system 0.00 1.00• Total time for all tasks 2.37 8.75• Hours saved per computer 6.38

• Source: Gartner Group

8/24/00 Group V 20

Site Terms

• Central Site

• Primary site

• Secondary site

• Domain

8/24/00 Group V 21

Central Site

• This is the highest site in the Systems Management Server architecture.

• Administers all sites and computers in the hierarchy.

• Has an unlimited number of sub sites. • The central site must be a primary site, and

have a SQL Server database. The central site must be running Windows NT Server.

8/24/00 Group V 22

Primary Site• A Systems Management Server site.

• Has its own database, which contains all of the hardware and software inventory information for the site and its sub sites.

• Local administration can be performed for the site server and all the sites below it in the hierarchy. A primary site must be running Windows NT Server.

8/24/00 Group V 23

Secondary Site

• Does not have a SQL Server database or Systems Management Server Administrator tool

• To be administered from any site above it in the hierarchy

• Does not have sub sites. Its site information is reported to the site above it. A secondary site must be running Windows NT Server

8/24/00 Group V 24

Domain

• A set of servers and client computers that have been grouped together.

• Primarily used to organize servers and clients into manageable groups.

• Provide logon validation, inventory collection, report generation, and package distribution.

8/24/00 Group V 25

Domain (Cont.)

• There is at least one domain at each site.

• Each site can have multiple domains to meet your management requirements. Valid domains are Windows NT, NetWare, LAN Manager, and LAN Server.

8/24/00 Group V 26

Server Components

• Site server

• Helper server

• SQL Server

• Distribution server

• Logon server

8/24/00 Group V 27

Site Server

• Each site has at least one site server.

• Running Windows NT Server.

• Contains Systems Management Server components needed to monitor and manage the site, its domains, and its computers.

• Serves as a collection point for instructions and inventory information.

8/24/00 Group V 28

Helper Server

• Helps ease the load on the site server.

• Makes moving some of the components from the site server to other servers possible.

• Used to offload some of the processing from the site server, they must be running Windows NT Server.

8/24/00 Group V 29

SQL Server• Each primary site must have a SQL Server.

• Microsoft SQL Server is used to store the site database.

• SQL Server can be installed on the site server or on a separate server.

• Different sites can share the same SQL Server. It is, however, more efficient for the SQL Server to be on the same LAN as the sites using its databases.

8/24/00 Group V 30

Distribution Server• Used as a distribution point when sending

applications for clients to install or run.

• Traffic on the network can be reduced by sending one copy of the software to each group of computers connected to the distribution server.

• A distribution server can be a Windows NT Server, a NetWare Server, a LAN Server, or a LAN Manager Server.

8/24/00 Group V 31

Logon Server

• Used to validate client computer logons.

• Functions as a transfer point between clients and site servers.

• Any supported network server can act as a logon server. For example, a NetWare Server can act as a logon server for its existing client computers.

8/24/00 Group V 32

Logon Server (Cont.)

• When a computer logs on, the network inventory information is placed onto the logon server, where it is collected by Systems Management Server, and stored in the database.

End of Module

8/24/00 Group V 34

Module 3:

Procedures ForSoftware Distribution

• Presented by: Melvin Brewster

8/24/00 Group V 35

Objectives

• Give an overview of Automated Distribution

• Explain the Distribution and Installation Procedures

8/24/00 Group V 36

Automatic Distribution

• Commercial Applications

• Internally Developed Applications

• Upgrades or Fixes

• Virus-checking software

8/24/00 Group V 37

Distribution and Installation Steps

• Query database to identify the workstations and servers on which you wish to install new software or share applications

• Prepare a package for distribution to client systems

8/24/00 Group V 38

Continue

• Create a job to install or share software

• Send the package to the site’s distribution servers at each site

• Install the software on, or allow sharing of the application to, the target computer

8/24/00 Group V 39

Querying the SQL Database

• Inventory information gathered by the Systems Management Server is stored in the SQL Server Database

• Query to identify computers that meet certain qualifications

• SMS has predefine queries, or you can define your own

• Query will provide a list of computers that matches your criteria

8/24/00 Group V 40

Packages

• Used to store information about software so it can be installed on clients, shared from servers, inventoried, or removed from a computer

• Before creating a package, all the files you want to use for the package must be placed in a shared source directory on a server or local drive

8/24/00 Group V 41

Packages

• Create the Package by identifying the files in the source directory and defining the Package properties

• Properties is the configuration and identification information used to either install the package on a client (workstation) or run from a network server (sharing)

8/24/00 Group V 42

Packages With Workstation Properties

• Used to install software on targeted clients• Create a job to send the Package to a distribution

server• When each targeted computer signs on to the

network, a program called the Package Command Manager(PCM) runs automatically and allows the user to install the new software by selecting it from the PCM window

8/24/00 Group V 43

Package Command Manager

• This product is installed and set up automatically when the computer is first inventoried by System Management Server

• At per set intervals, PCM checks to see if there are any software installation jobs for its’ computer

• It retrieves the software from the local distribution server and follows installation instructions

8/24/00 Group V 44

Package Command Manager

• The user can be given the option of selecting the package now or later

• Can set a deadline by which the user must accept the package

• Also, can set to install when the computer is unattended

8/24/00 Group V 45

Packages With Sharing Properties

• Used to install and then share, software on one or more network file servers

• Job sends the package to the distribution server at a site

• Shares the necessary network directories

• Makes the package available to users with specified access permissions

8/24/00 Group V 46

Packages With Sharing Properties

• Packages can have one or more properties

• Example: a package with both Workstation and Inventory properties defined would,– Would allow installation off new software to a

target client– Include the new software in the site’s inventory

8/24/00 Group V 47

Packages Definition Files

• Systems Management Server includes PDFs• They specify, setup programs, installation

options, and execution command lines for certain applications

• Software developers may create PDFs for their applications

• Imported PDF will automatically define all the variables for for an specific application

8/24/00 Group V 48

Creating Jobs

• Jobs let System Management Server know where to send a Package

• It includes the distribution server to use, type of job (Run command on workstation, Share application server, and Remove shared Package from server

8/24/00 Group V 49

Distributing the Software

• Systems Management Server takes over the distribution process after the you have defined the package properties and job details

• It compresses the package

8/24/00 Group V 50

Distributing the Software

• Manages error detection and corruption over WAN

• When the packages arrives at the site, it is placed on the specified distribution server

• SMS uncompress the package and uses the package properties and job type to determine what to do with it next

End of Module

Module 4:

Deploying Windows 95 with

System Management Server

Presented by: Chaofeng Yan

8/24/00 Group V 53

Objective

• Demonstrate a practical example of Microsoft System Management Server’s implementation.

8/24/00 Group V 54

Upgrade Process

• Determine which computers are appropriate for upgrading

• Send upgrade package to identifying the target computers

8/24/00 Group V 55

Determine Computers’ Appropriateness

• Query the SQL Server database to locate all computers that match the upgrade specifications.

• The Predefine query included in Systems management Server examines the CPU, the operating system, the available hard disk space, the installed RAM, and so on.

8/24/00 Group V 56

Determine Computers’ Appropriateness

• A typical query for an upgrade of desktop computers might specify:

– A 386 DX processor or better

– MS-DOS version 5.0 or later, Windows, or Windows for Workgroups

– 35 MB or more of hard disk space

8/24/00 Group V 57

Determine Computers’ Appropriateness

• Hard disk space required:

• Existing Operating System Compact Typical Full

• New(no system installed) 30 MB 40 MB 50 MB

• Windows 3.1 15 MB 35 MB 40 MB

• Windows for workgroups3.11 15MB 30 MB 35 MB

8/24/00 Group V 58

Determine Computers’ Appropriateness

• A typical query for an upgrade of desktop computers might specify: (Continue)

• 4 MB or more of Installed RAM

• Windows 95 is not already installed

8/24/00 Group V 59

Deploying Windows 95 Upgrade

• Create and share a package source directory for the Windows 95 files.

• This directory can be on any server that can be shared with the network.

8/24/00 Group V 60

Deploying Windows95 Upgrade

• Copy the appropriate files from the Windows 95 compact disc to the new package source directory.

• From the systems management server 1.0a compact disc, copy the following files to the package source directory:

– WIN95.INF file from SMS\LOGON.SRV\MSTEST.

– DOS2W95.EXE file form SMS\LOGON.SRV\MSTEST (If you are setting up clients that run MS-DOS).

8/24/00 Group V 61

Deploying Windows 95 Upgrade

• Review the INF file for your configuration, and make appropriate changes (such as changing the time zone).

• Create a package containing the Windows95 source directory.

8/24/00 Group V 62

Deploying Windows 95 Upgrade

• Create a job to distribute the package to the clients.

• Send the job to the target computer.

End of Presentation

End Of Module

8/24/00 Group V 64

References

• http://www.microsoft.com/siteserver/site/ProductInfo/SystemReq.htm

• http://msdn.microsoft.com/library/winresource/dnwin95/S688B.HTM

• http://www.zdnet.com/products/stories/review/0,4161,2343040-2,00.html

• http://www.compaq.com/tco/bestpractices/bp_autosoftware.html