Prerequisites and Initial Configuration
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.
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/ ] .
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