Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Download
Standard view
Full view
of .
Look up keyword
Like this
1Activity
0 of .
Results for:
No results containing your search query
P. 1
Step by Step Wininstall Info

Step by Step Wininstall Info

Ratings: (0)|Views: 15|Likes:
Published by projectsquirt

More info:

Published by: projectsquirt on Sep 01, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

09/01/2010

pdf

text

original

 
Step-by-Step Guide to Software Installation and Maintenance
Software Installation and Maintenance for the Windows® 2000 operating system allows administrators tomanage software for their organizations, including applications, service packs, and operating systemupgrades. This overview guide explains how to use the Software Installation extension of the Group PolicyMicrosoft Management Console snap-in to specify policy settings for application deployment for groups of users and computers.
On This Page 
Introduction Prerequisites and Initial Configuration Software Installation Snap-in CONFIGURATION Software Installation and Maintenance Scenarios Appendix – An Excel 97 .Zap File Related Links 
Introduction 
This document is part of a set of step-by-step guides that introduce the Change and ConfigurationManagement features of the Windows® 2000 operating system. This guide presents an overview of Software Installation and Maintenance. It also explains how to use the Software Installation extension of the Group Policy Microsoft Management Console snap-in to specify policy settings for applicationdeployment for groups of users and computers.Software Installation and Maintenance is dependent upon both the Active Directory and Group Policy.Administrators who are responsible for Software Installation and Maintenance should be familiar with bothof these technologies.
Publish vs. Assign 
Administrators can use Software Installation and Maintenance to either publish or assign software: 
Publish. Administrators publish applications that users may find useful, allowing users to decidewhether to install the application. You can only publish to users, not computers. 
Assign. Administrators assign applications that users require to perform their jobs. Assignedapplications are available on users' desktops automatically. For a comparison of these capabilities, see Table 1 below. Administrators deploy applications in GroupPolicy objects (GPOs) that are associated with Active Directory containers such as sites, domains, andorganizational units (OUs).
Table 1 Publishing and Assigning Software
 ©2008 Microsoft Corporation. All rights reserved.
Publish to Users Assign to UsersAssign toComputers
After theadministratordeploys thesoftware, it isavailable forinstallation:
 If an application isdeployed in a GPO that isalready applied to theuser from a previouslogon, it is available forinstallation in the currentlogon session (from theAdd/Remove ProgramsIf an application isdeployed in a GPO that isalready applied to theuser from a previouslogon, it is available forinstallation in the currentlogon session (from theAdd/Remove ProgramsThe next timethe computerstarts (reboot).
 
Page 1 of 18Step-by-Step Guide to Software Installation and Maintenance8/12/2008http://technet.microsoft.com/en-us/library/bb742421(printer).aspx
 
Supported Installation File Types
 Software Installation and Maintenance supports Windows Installer packages (.msi files), repackaged files,and .zap files.A Windows Installer package (.msi file) contains all the information necessary to describe to the WindowsInstaller how to set up an application. It covers every conceivable situation: various platforms, differentsets of previously installed products, earlier versions of a product, and numerous default installationlocations. Some applications such as Office 2000 provide their own .msi files. These are referred to asnatively-authored Windows Installer packages.You can create Windows Installer packages for your applications by using package-authoring tools providedby various vendors such as InstallShield Software Corporation and WISE Solutions, Inc. See the section onWindows Installer Applications for more information.You can also repackage an existing application for use with the Windows Installer. To create a package forthe application, you use a repackaging tool such as the VERITAS WinInstall LE, described later in thisdocument.Non-Windows Installer-based applications must use a .zap file to describe their existing setup program.A .zap file is a text file (similar to .ini files) that provides information about how to install a program, theapplication properties, and the entry points that the application should install. A sample .zap file is includedin the appendix - An Excel 97 .Zap File.Top of page 
Control Panel). If theapplication is deployed ina new GPO that is notalready associated withthe user, then it isavailable at the nextlogon.Control Panel). If theapplication is deployed ina new GPO that is notalready associated withthe user, then it isavailable at the nextlogon.
Typically, usersinstall thesoftware from:
 The Add/RemovePrograms in ControlPanel.Start menu shortcut.Desktop shortcut.Add/Remove Programs inControl Panel.The software isalreadyinstalled.
If the software isnot installed andthe user opens afile associatedwith thesoftware, will theapplicationinstall?
 Yes. Yes. The software isalreadyinstalled.
Can the usersremove thesoftware usingthe Add/RemovePrograms inControl Panel?
 Yes. Users can re-installthe application from theAdd/Remove Programs inControl Panel.Yes. The software will bere-advertisedimmediately. This meansthat the shortcuts will bepresent in the users'desktops and they can re-install the application byclicking on a shortcut, forexample.No. Only thelocaladministratorcan remove thesoftware. A usercan run a repairon the software.
Supportedinstallation filetypes:
 Windows Installerpackages (.msi files), andZAP files.Windows Installerpackages (.msi files)WindowsInstallerpackages (.msifiles)
Page 2 of 18Step-by-Step Guide to Software Installation and Maintenance8/12/2008http://technet.microsoft.com/en-us/library/bb742421(printer).aspx
 
Prerequisites and Initial Configuration
Prerequisites 
This Software Installation and Maintenance document is based on the two-part, "Step-by-Step Guide to aCommon Infrastructure for Windows 2000 Server Deployment"http://www.microsoft.com/windows2000/techinfo/planning/server/serversteps.asp [ http://www.microsoft.com/windows2000/techinfo/planning/server/serversteps.asp ]Before beginning the steps in this guide, you need to build the common infrastructure, which specifies aparticular hardware and software configuration. If you are not using the common infrastructure, you needto make the appropriate changes to this guide.Software Installation and Maintenance is dependent on Group Policy. It is highly recommended that youcomplete the Group Policy step-by-step guide before the Software Installation and Maintenance guide.
Note:
If you completed the Group Policy guide, it may be necessary to disable some of the policiesparticularly the loopback policies, as they may not allow people to install software from the Add/RemovePrograms in the Control Panel.Additionally, you may want to use the "
Step-by-Step Guide toRepackaging Software for the WindowsInstaller Using VERITAS WinINSTALL LE 
"and repackage some software before you continue with this guide.
Windows Installer Applications 
Software Installation and Maintenance leverages the new Windows Installer service that is a part of theWindows family of operating systems. (The Windows Installer is available in Windows 2000, Windows NT4.0, Windows 98 and Windows 95.)For the best performance and the greatest reduction in TCO, you needto use applications that support the Windows Installer.No sample applications are supplied for these guides. You must acquire applications such as Microsoft Office2000 that supply a natively authored Windows Installer package (an .msi file). Or you must use anauthoring or repackaging tool to create Windows Installer packages for your software.You can author a Windows Installer package using a package-authoring tool if you have all of the files andknow the architecture of the application. Package authoring tools are available from the following vendors:
InstallShield Software Corporation. Information is available at the InstallShield Web sitehttp://www.installshield.com[ http://www.installshield.com/ ] . 
WISE Solutions, Inc. For information, see the WISE Solutions Web sitehttp://www.wisesolutions.com [ http://www.wisesolutions.com/ ] . If you want to use Software Installation and Maintenance with an existing application, you may want toconsider repackaging the application to support the Windows Installer. The VERITAS WinInstall LE forrepackaging of existing applications for use by the Windows Installer is available on the Windows 2000Server CD. If you are unfamiliar with repackaging software, see the "
Step-by-Step Guide to RepackagingSoftware for the Windows Installer Using VERITAS WinINSTALL LE 
," which explains how to use theirrepackager.For more information on this tool, please see the VERITAS Web sitehttp://www.veritas.com [ http://www.veritas.com/ ] .
Best Practice
 
You may want to consider natively authoring a Windows Installer package rather than repackaging theapplication if you have all of the files for an application, if you know the changes that applicationmakes to the registry for installation, and if there are not too many files. 
Success with repackaging is affected by the state of the computer where the repackaging isperformed. For best results, you should always start the repackaging of an application with a clean
 
Page 3 of 18Step-by-Step Guide to Software Installation and Maintenance8/12/2008http://technet.microsoft.com/en-us/library/bb742421(printer).aspx

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->