steps by ms

Software Installation and Maintenance for the Windows 2000 operating system allows administrators to manage software for their organizations, including applications, service packs, and operating system upgrades. This overview guide explains how to use the Software Installation extension of the Group Policy Microsoft Management Console snap-in to specify policy settings for application deployment for groups of users and computers.On This PageIntroductionPrerequisites and Initial ConfigurationSoftware Installation Snap-in CONFIGURATIONSoftware Installation and Maintenance ScenariosAppendix An Excel 97 .Zap FileRelated LinksIntroductionThis document is part of a set of step-by-step guides that introduce the Change and Configuration Management 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 application deployment 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 both of these technologies.Publish vs. AssignAdministrators can use Software Installation and Maintenance to either publish or assign software: Publish. Administrators publish applications that users may find useful, allowing users to decide whether to install the application. You can only publish to users, not computers. Assign. Administrators assign applications that users require to perform their jobs. Assigned applications are available on users' desktops automatically.For a comparison of these capabilities, see Table 1 below. Administrators deploy applications in Group Policy objects (GPOs) that are associated with Active Directory containers such as sites, domains, and organizational units (OUs).Table 1 Publishing and Assigning SoftwarePublish to UsersAssign to UsersAssign to Computers

After the administrator deploys the software, it is available for installation:If an application is deployed in a GPO that is already applied to the user from a previous logon, it is available for installation in the current logon session (from the Add/Remove Programs Control Panel). If the application is deployed in a new GPO that is not already associated with the user, then it is available at the next logon.If an application is deployed in a GPO that is already applied to the user from a previous logon, it is available for installation in the current logon session (from the Add/Remove Programs Control Panel). If the application is deployed in a new GPO that is not already associated with the user, then it is available at the next logon.The next time the computer starts (reboot).

Typically, users install the software from:The Add/Remove Programs in Control Panel.Start menu shortcut.Desktop shortcut.Add/Remove Programs in Control Panel.The software is already installed.

If the software is not installed and the user opens a file associated with the software, will the application install?Yes.Yes.The software is already installed.

Can the users remove the software using the Add/Remove Programs in Control Panel?Yes. Users can re-install the application from the Add/Remove Programs in Control Panel.Yes. The software will be re-advertised immediately. This means that the shortcuts will be present in the users' desktops and they can re-install the application by clicking on a shortcut, for example.No. Only the local administrator can remove the software. A user can run a repair on the software.

Supported installation file types:Windows Installer packages (.msi files), and ZAP files.Windows Installer packages (.msi files)Windows Installer packages (.msi files)

Supported Installation File TypesSoftware 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 Windows Installer how to set up an application. It covers every conceivable situation: various platforms, different sets of previously installed products, earlier versions of a product, and numerous default installation locations. Some applications such as Office 2000 provide their own .msi files. These are referred to as natively-authored Windows Installer packages.You can create Windows Installer packages for your applications by using package-authoring tools provided by various vendors such as InstallShield Software Corporation and WISE Solutions, Inc. See the section on Windows Installer Applications for more information.You can also repackage an existing application for use with the Windows Installer. To create a package for the application, you use a repackaging tool such as the VERITAS WinInstall LE, described later in this document.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, the application properties, and the entry points that the application should install. A sample .zap file is included in the appendix - An Excel 97 .Zap File.Top of pagePrerequisites and Initial ConfigurationPrerequisitesThis Software Installation and Maintenance document is based on the two-part, "Step-by-Step Guide to a Common Infrastructure for Windows 2000 Server Deployment"http://www.microsoft.com/windows2000/techinfo/planning/server/serversteps.aspBefore beginning the steps in this guide, you need to build the common infrastructure, which specifies a particular hardware and software configuration. If you are not using the common infrastructure, you need to make the appropriate changes to this guide.Software Installation and Maintenance is dependent on Group Policy. It is highly recommended that you complete 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 policies particularly the loopback policies, as they may not allow people to install software from the Add/Remove Programs in the Control Panel.Additionally, you may want to use the "Step-by-Step Guide toRepackaging Software for the Windows Installer Using VERITAS WinINSTALL LE"and repackage some software before you continue with this guide.Windows Installer ApplicationsSoftware Installation and Maintenance leverages the new Windows Installer service that is a part of the Windows family of operating systems. (The Windows Installer is available in Windows 2000, Windows NT 4.0, Windows 98 and Windows 95.)For the best performance and the greatest reduction in TCO, you need to use applications that support the Windows Installer.No sample applications are supplied for these guides. You must acquire applications such as Microsoft Office 2000 that supply a natively authored Windows Installer package (an .msi file). Or you must use an authoring 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 and know 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. WISE Solutions, Inc. For information, see the WISE Solutions Web sitehttp://www.wisesolutions.com.If you want to use Software Installation and Maintenance with an existing application, you may want to consider repackaging the application to support the Windows Installer. The VERITAS WinInstall LE for repackaging of existing applications for use by the Windows Installer is available on the Windows 2000 Server CD. If you are unfamiliar with repackaging software, see the "Step-by-Step Guide to Repackaging Software for the Windows Installer Using VERITAS WinINSTALL LE," which explains how to use their repackager.For more information on this tool, please see the VERITAS Web sitehttp://www.veritas.com.Best Practice You may want to consider natively authoring a Windows Installer package rather than repackaging the application if you have all of the files for an application, if you know the changes that application makes 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 is performed. For best results, you should always start the repackaging of an application with a clean computer. For the purpose of repackaging, a clean computer is defined as a computer that has only the operating system and operating system service packs installed prior to running the VERITAS Discover program.Other companies will provide their applications with native Windows Installer support. Please contact your favorite application vendors for information on their Windows Installer support plans.Non-Windows Installer ApplicationsIt is possible to publish applications that do not install with the Windows Installer. They can only be published to users and they are installed using their existing Setup programs.Because these non-Windows Installer applications use their existing Setup programs, such applications cannot: Use elevated privileges for installation. Install on the first use of the software. Install a feature on the first use of the feature. Rollback an unsuccessful operation, such a install, modify, repair, or removal, or take advantage of other features of the Windows Installer. Detect a broken state and automatically repair it.Before an existing Setup program can be used with Software Installation and Maintenance, it must be described in a ZAP(.zap) file, which is a text file, similar to .ini files, which provides the following information: How to install the program -- which command line to use. The properties of the application -- name, version, language. The entry points that the application should automatically install -- for file extension, CLSID, and ProgID.Note that .zap files are stored in the same location on the network as the Setup program they reference. The appendix contains an example of a .zap file.Creating a Software Distribution Point for the Windows Installer ApplicationsTo manage software, you must create a software distribution point (SDP) that contains all the Windows Installer packages (.msi files), .zap files, and the actual software files.To create a software distribution point, you do the following: Create a network share along with the appropriate folders for software distribution. Copy the Windows Installer packages, application executable files, and .zap files to the appropriate shared folder. Set the appropriate permissions for the high-level network shared folder. Users must have the ability to read from the software distribution point. Set the following Discretionary Access Control (DACL) permissions:Everyone: ReadAdministrators: Full Control, Change, and Read.The following procedure shows you how to set up the distribution point.To create the software distribution point:1. Log on to theHQ-RES-DC-01server as an administrator.2. Double-click theMy Computericon.3. Double-click the hard-drive icon of the local disk where you want to create the software distribution point.4. On theFilemenu, selectNew, and then clickFolder.5. Under theNew Folderin the selected drive pane, typeManaged Applications.6. Right-click theManaged Applicationsfolder, and selectPropertiesfrom the context menu.7. In theManaged Applications Propertiespage, click theSharingtab, clickShare this folder, and then type Reskit Managed Applications in theCommenttext box.8. ClickPermissions. In thePermissions for Managed Applicationsdialog box, selectEveryone, and then underPermissions, clear theAllow permission for the Full ControlandChange check boxes. Ensure that Everyone has only Read access to the folder. Click Add.9. In theSelect Users, Computers or Groupsdialog box, underNameclickAdministrators, and then clickAdd. (Note theLook intext box should be pre-populated with reskit.com.) ClickOK.10. In thePermissions for Managed Applicationsdialog box, selectAdministrators, and then underPermissions, set theFull ControlandChangepermissions toAllow. Ensure thatAdministratorshaveFull Control,Change, andReadaccess to the folder. ClickOK.11. In the Managed Applications Properties dialog box, click OK.At this point, you should repeat the preceding steps to create any additional folders for the software you are managing. Note that each sub-folder does not need to be explicitly shared or have permissions set. Afterwards, you should copy the Windows Installer packages, .zap files, and the application files to the appropriate shared folders.You should note that for computer-assigned applications, the network share needs to be reachable by the local system account. This is not the default for Windows NT 4.0 and Novell servers.Best PracticeAdministrators should consider using either the distributed file system (Dfs) feature of Windows 2000 Server or Microsoft Systems Management Server to manage their software distribution points.Top of pageSoftware Installation Snap-in CONFIGURATIONThe Active Directory Users and Computers snap-in is part of the Administrative Tools program group. It already has a Group Policy and Software Installation snap-in. You may either follow these steps to configure your own tool, a saved snap-in, or use the Active Directory Users and Computers snap-in.Creating a Software Installation Snap-in ToolTo create the Software Installation snap-in:1. Log on to theHQ-RES-DC-01server as an administrator.2. ClickStart, clickRun, typemmc, and then clickOK.3. In the MMC console, clickAdd/Remove Snap-inon theConsolemenu.4. In theAdd/Remove Snap-indialog box, clickAdd.5. In theAdd Stand-alone Snap-indialog box, clickActive Directory Users and Computerson theAvailable Standalone Snap-inslist, and then clickAdd. ClickClose, then clickOK.6. In the console tree, double-clickActive Directory Users and Computersto expand the tree, double-click thereskit.comdomain, double-click theAccountsorganizational unit (OU).7. Click the+next to theHeadquartersOU.Saving the Software Installation Snap-in ToolAs you go through this guide, you may want to save changes to the MMC console.To save your changes:1. In the MMC console, clickSaveon the Console menu.2. In theSavedialog box, typeSIM Toolin theFile nametext box, and then clickSave.Your snap-in will look similar to Figure 1 below.

Figure 1: Software Installation Snap-InCreating a Group Policy ObjectIf you have already completed the Group Policy step-by-step guide, then you may have already created the necessary Group Policy objects (GPOs).To create a Group Policy Object (GPO):1. In the Software Installation snap-in tool you just saved (SIM Tool console), in the console tree, double-clickActive Directory Users and Computers, double-clickreskit.com, and then double-clickAccounts.2. Right-clickHeadquarters, and selectPropertiesfrom the context menu.3. In theHeadquarters Propertiesdialog box, click theGroup Policytab, and then clickNew.4. TypeHQ Policy.This creates a new Group Policy object called HQ Policy.At this point, you could add another GPOgiving each one that you create a meaningful nameor you could choose to edit a GPO, which starts the Group Policy and Software Installation snap-ins. If you have more than one GPO associated with an Active Directory folder, verify the order; a GPO that is higher in the list is processed first.5. ClickClose.Best PracticeConsider using security descriptors (DACLs) on the GPO to increase the granularity of software management for your organization.To close the Software Installation snap-in:1. In the SIM Tool console, clickSaveon theConsolemenu.2. ClickExiton theConsolemenu.To edit a Group Policy Object (GPO):1. Log on to the HQ-RES-DC-01 server as an administrator.2. ClickStart, point toPrograms, clickAdministrative Tools, and then clickSIM Tool.3. In theSIM Toolconsole, double-clickActive Directory Users and Computers, double-clickreskit.com, and then double-clickAccounts.4. Right-clickHeadquarters, and selectPropertiesfrom the context menu. In theHeadquarters Propertiesdialog box, click theGroup Policytab. Right-clickHQ Policyin theGroup Policy Object Linkslist box, and clickEdit.This opens the Group Policy snap-in.5. In the Group Policy snap-in, underComputer Configurationnode, double-clickSoftware Settings.6. In the console tree, under theUser Configurationnode, double-clickSoftware Settings.You have opened the Software Installation snap-in for theHQ PolicyGPO. Your snap-in should look like Figure 2 below.

Figure 2: Group Policy Snap-InYou can use the Software Settings node in the console tree underHQ PolicyandComputer Configurationto assign an application tocomputersthat are managed by this GPO. You use the Software Settings node under theUser Configurationnode to assign or publish an application touserswho are managed by this GPO.Configuring the Software Installation Defaults for a Group Policy ObjectYou can configure default settings for Software Installation on a per-Group Policy Object (GPO) basis.To specify software installation defaults for the selected Group Policy object, you use theSoftware Installation Propertiesdialog box, shown below in Figure 3. This section explains some of the available options.

Figure 3: The Software Installation Properties pageSetting Options for New Packages and Installation User InterfaceTo control what happens when you add a new package to the selected GPO, you use theGeneraltab in theSoftware Installation Propertiesdialog box, and set options in theNew packagesframe. The default behavior is that theDeploy Softwaredialog box appears each time, and the administrator can select one of the choices from that dialog box.If you are going to deploy several packages to a GPO as published without transforms, you can selectPublishin theNew Packagesframe, and every package that is deployed is automatically published. If you are going to add a package with a transform (customization or .mst file), you must selectAdvanced published or assigned.Note:You cannot add or change transforms (.mst files) after the software is deployed.This setting is most useful when an administrator is adding several applications at one time. For example, if an administrator is adding five applications to this GPO and they are all to be published with no transforms, then the administrator could set this to Publish.Similarly, the options in theInstallation user interface optionsframe allow the administrator to set how much of the user interface (UI) the Windows Installer presents to a user during installation. The Basic UI (the default option) only presents progress bars and messages; no user choices are presented other thanCancel.TheMaximumUI option shows the UI that the author of the Windows Installer package defined.Setting Options for CategoriesWhen an organization has a large amount of software to manage, administrators can create categories for software. These categories can then be used to filter the software in theAdd/Remove ProgramsinControl Panel. For example, you could create a category calledProductivity Applicationsand include software such as word processing and database management applications.Although there is aCategoriestab on theSoftware installation Propertiesdialog box, categories are established on a per-domain basis. This means the domain administrator can create and edit the categories from any of theSoftware installation Propertiespages for any GPO in the domain. Administrators can then use these categories with software they are managing within any GPO in the domain. There are no default or supplied categories.Best PracticeBecause Categories are established per domain rather than per GPO, an organization should standardize the Categories and create them in a centralized manner.To configure the default settings:1. In the Group Policy snap-in console tree, right-clickSoftware installationunderUser Configuration, and then clickProperties. This opens theSoftware Installation Propertiesdialog box. You use this dialog box to set defaults for software installation in the current GPO. You can set the default package location to the network location of the software distribution point you created earlier. Then you do not have to browse for each package that you add.2. In theSoftware installation Propertiesdialog box, clickBrowse.You need to browse for the software distribution point you created in the previous section relative to the network share location, rather than the local drive on the server. This ensures that you are managing software from the network share location that users can access. Users cannot access the package from the local drive of the server.3. In theBrowse for Folderdialog box, click the plus sign (+) next toMy Network Places, double-clickEntire Network, double-clickMicrosoft Windows Network, and then double-clickreskit.com.4. Double-clickHQ-RES-DC-01, clickManaged Applications, and then clickOK.Note:The exact navigation above may differ on your network. Be sure that you are pointing to the software distribution point relative to the network rather than relative to the local drive on the server.5. In theSoftware Installation Propertiesdialog box, click theGeneraltab, select theDisplay the Deploy Software dialog box(default) in theNew Packagesfield, and selectBasic(default) in theInstallation user interface optionsfield.6. In theSoftware installation Propertiesdialog box, click theCategoriestab. ClickAdd.7. In theEnter new categorydialog box, typeProductivity Applicationsin theCategorytext box, and then clickOK. In theCategoriestab, clickAdd.8. In theEnter new categorydialog box, typeSystem Applicationsin theCategorytext box, and then clickOK. ClickOK.Later, if you want to change these defaults or add additional categories for the organization, you can return to theSoftware installation Propertiesdialog box. As mentioned previously, categories are per-domain, not per GPO.At this point you can either close the Software Installation snap-in or proceed with the scenarios described next.Top of pageSoftware Installation and Maintenance ScenariosScenarios Covered in this DocumentThis guide covers a few basic scenarios for Software Installation and Maintenance, including: Assigning repackaged Microsoft Word 97 (to users). Publishing Microsoft Excel 97 (using a .zap file). Removing Excel 97. Upgrading Word 97 to Microsoft Office 2000 (using an Office 2000 transform). Assigning Windows 2000 to a computer (a new build).As the packages for these applications are not included, you may have to modify the step-by-step guide. You may use applications that either natively support the Windows Installer or that you have repackaged for the Windows Installer.Please note that this guide does not describe all of the possible Software Installation and Maintenance scenarios. You should use this guide to gain an understanding of Software Installation and Maintenance. Then think about how your organization might use software installation and the other IntelliMirror features to reduce TCO.Note:If you completed the Group Policy step-by-step guide, it may be necessary to undo some of the Group Policy to complete this guide. For example, the Loopback policy disables the ability to access the Add/Remove Programs in the Control Panel.Assigning Repackaged WordWhether publishing or assigning software, the basic steps are fundamentally the same. This guide presents a scenario forassigninga repackaged version of Microsoft Word 97 for users.This procedure assumes that you have already created a Word97 folder in the software distribution point created earlier, and that you are using a repackaged version of Microsoft Word 97.Note:To assign to users, start in the Group Policy snap-in User Configuration node. To assign to computers, start in the Computer Configuration node.To assign repackaged Word or other software:1. Log on to theHQ-RES-DC-01server as an administrator.2. ClickStart, point toPrograms, clickAdministrative Tools, and then clickSIM Tool.3. In theSIM Toolconsole, double-clickActive Directory Users and Computers, double-clickreskit.com, and then double-clickAccounts.4. Right-clickHeadquarters, and selectPropertiesfrom the context menu. In theHeadquarters Propertiesdialog box, click theGroup Policytab. Right-clickHQ Policyin theGroup Policy Object Linkslist box, and clickEditto open the Group Policy snap-in.5. In the Group Policy snap-in, underUser Configuration, double-clickSoftware Settings, right-clickSoftware installation, and then selectNewfrom the context menu. ClickPackage.6. In theOpendialog box, click theWord97folder.7. You need to substitute the folder for the software you are going to deploy, from the software distribution point you created earlier.8. ClickOpen. ClickWord, and clickOpen. In theDeploy Softwaredialog, clickAssigned, and then clickOK.Note:If you are going to deploy a Windows Installer package with a transform, you have to selectConfigure package propertiesin theDeploy Softwaredialog so that you can associate the transform with the package. Make any other changes to the properties at this point, before you pressOKto either assign or publish the software.The application is added to the Software Installation snap-in as assigned. After the application is assigned, you can right-click the application entry in the details pane to view the assigned applications property pages.The application is assigned to all the users managed by the Headquarters GPO.Verifying the Effect of Assigning WordTo verify the effect of assigning Word 97 to the Headquarters GPO, you can log on to Windows 2000 Professional as a user who is managed by the Headquarters OU. (If you are using the common infrastructure, you could log on to the client [email protected],for example.)When you log on to Windows 2000 Professional, you should see a Microsoft Word icon on theStartmenu.If you select Word, the Windows Installer installs Word for you. While the installation is proceeding, you should see a progress indicator from the Windows Installer. When the installation is complete, Word starts and you can edit a document.If the software installation becomes damaged, then the next time the user selects Word from the Start menu, if all the key files as defined in the Windows Installer package for Word are present, Word starts. If a key file is missing or damaged, the Windows Installer repairs Word and then starts it.Publishing Legacy ExcelTo publish Excel 97 without repackaging it for the Windows Installer, you must first create a .zap file for Excel. Use the .zap file example in the appendix as a model. You also need to create a folder for Excel97 in the software distribution point you created earlier.Open the Software Installation snap-in saved previously, and edit the Headquarters GPO. (See the steps in the preceding section.) When you are ready to publish Excel 97, the snap-in should look like it did when you assigned Word 97 in the previous section.To publish Excel:1. In the SIM Tool console, double-clickActive Directory Users and Computers, double-clickreskit.com, and then double-clickAccounts.2. Right-clickHeadquarters, and clickProperties.3. In theHeadquarters Propertiesdialog box, click theGroup Policytab, click theHQ PolicyGPO, and then clickEditto open the Group Policy snap-in.In the Group Policy snap-in console tree, underUser Configuration, double-clickSoftware Settings, right-clickSoftware installation, and then selectNewfrom the context menu. ClickPackage.4. In theOpendialog box, click theExcel97folder, and clickOpen.In theFiles of typecombo box, click the down arrow, and then clickZAW Down-level applications package (*.zap). ClickExcel97, and clickOpen.5. In the Deploy Software dialog box, thePublishoption is already selected, clickOK.Excel 97 is published to the users managed by the Headquarters GPO.Because a ZAP file publishes the existing Setup, the Setup will not run with elevated privileges. Therefore, you will need to supply administrative privileges during the Setup. This can be done by using theInstall Program as Other Userdialog box. Accessing this dialog is controlled by policy. A policy calledRequest credentials for network installationsis available in the Group Policy snap-in, underUser Configuration\Administrative Templates\Windows Components\Windows Explorer. If enabled, this policy displays theInstall Program As Other Userdialog box even when a program is being installed from files on a network computer across a local area network. For more information, see theExplaintab on this policy property page.To set the Request Credentials for network installations policy:1. In the SIM Tool console, navigate to theHeadquartersOU, and then right-clickHeadquartersand clickProperties.2. In theHeadquarters Propertiesdialog box, double-click theHQ PolicyGPO to open the Group Policy snap-in.3. In the Group Policy snap-in, underUser Configuration, click the+next toAdministrative Templates.4. In theRequest credentials for network installationsdialog box, clickEnabled, and clickOK. Close the Group Policy snap-inIn theHeadquarters Propertiesdialog box, clickOK.5. In the SIM Tool console, clickSaveon theConsolemenu. ClickExiton theConsolemenu.Verifying the Effects of Publishing Excel 97To verify the effect of publishing Excel 97 to the Headquarters GPO, first log on to Windows 2000 Professional as a user who is managed by the Headquarters OU. (If you are using the common infrastructure, you could log on [email protected],for example.)To confirm the effects of publishing Excel 97:1. ClickStart, point toSettings, clickControl Panel, and then double-clickAdd/Remove Programs.2. In theAdd/Remove Programsdialog box shown in Figure 4 below, clickAdd New Programs.Note:Word 97, which was assigned, is listed in theAdd/Remove Programsdialog box. This is so that users can add or remove the assigned program if they need to. Even if a user removes the assigned application, it is available for installation again the next time the user logs on.

Figure 4: Add/Remove Excel 973. SelectMicrosoft Excel 97from theAdd programs from your networklist, and clickAdd.You should see theInstall Program As Other Userdialog box shown in Figure 5 below because you are installing a non-Windows Installer based application.

Figure 5: Install Program as Other User4. In theInstall Program As Other Userdialog box, clickRun the program as the following user, typeAdministratorin theUser Nametext box, and type the domain name (reskit) in theDomainbox. If you have an Administrator password set for this computer, you must enter this as well.5. ClickOK.Excel now installs using the original Setup program. You should follow the instructions in the original Setup UI to complete the installation. After you have installed Excel, you can close the application.6. CloseAdd/Remove Programs, and then closeControl Panel.7. Log off Windows 2000 Professional.To remove Excel 97:1. In the SIM Tool console, double-clickActive Directory Users and Computers, double-clickreskit.com, and then double-clickAccounts.2. Right-clickHeadquarters, and clickProperties.3. In theHeadquarters Propertiesdialog box, click theGroup Policytab, click theHQ PolicyGPO, and then clickEditto open the Group Policy snap-in.4. In the details pane, right-clickMicrosoft Excel 97, and selectAll Tasksfrom the context menu.5. ClickRemove.6. In theRemove Packagedialog box, clickYes.Note:Because Excel 97 was installed using a .zap file, you do not have the option to force the removal as you would with a Windows Installer file.Microsoft Excel 97 no longer appears in the details pane.7. Log on to the Windows 2000 Professional as the Local Administrator (remember, Excel was installed as Administrator in the preceding scenario).8. ClickStart, point toSettings, clickControl Panel, and then double-clickAdd/Remove Programs.9. In theAdd/Remove Programsdialog box, click theMicrosoft Excel 97entry in theChange or Remove Programsframe, and then clickChange/Remove.10. The Excel 97 Setup program starts. In theMicrosoft Excel 97 Setupdialog box, clickRemove All.11. When Setup prompts you about removing Microsoft Excel 97, clickYes. ClickOK.12. CloseAdd/Remove Programs, and then closeControl Panel. Log off Windows 2000 Professional.Upgrade Microsoft Word 97 to Office 2000 With a TransformOffice 2000 comes with a Windows Installer package natively authored. Before performing this upgrade, use the Office 2000 Customization Wizard to create a transform. You must substitute the name of your transform in this scenario.This procedure assumes that you have placed the necessary files (.msi, .mst, and so on) in a folder called Office in the software distribution point.To upgrade Word 97 to Office 20001. In the SIM Tool console, double-clickActive Directory Users and Computers, double-clickreskit.com, and then double-clickAccounts.2. Right-clickHeadquarters, and clickProperties.3. In theHeadquarters Propertiesdialog box, click theGroup Policytab, click theHQ PolicyGPO, and then clickEditto open the Group Policy snap-in.4. In the Group Policy snap-in, underUser Configuration, double-clickSoftware Settings, right-clickSoftware installation, clickNew, and then clickPackage.5. In theOpendialog box, click theOfficefolder, and clickOpen. Select theOffice 2000Windows Installer package (data1.msi), and clickOpen.6. In theDeploy Softwaredialog box, clickAdvanced published or assigned, and clickOK.7. In theMicrosoft Office 2000 Propertiesdialog box, click theModificationstab, and clickAdd.8. In theOpendialog box, clickOffice, and then clickOpen. Select theOffice 2000 transform(.mst), and clickOpen.Note:It is important that you donotclick OK until you have set all the options for the modifications.9. In theMicrosoft Office 2000 Propertiesdialog box, click theUpgradestab, and clickAdd.10. In theAdd Upgrade Packagedialog box,Microsoft Word 97should be highlighted in thePackage to Upgradelist box. If not, click it to select it. ClickUninstall the existing package, then install the upgrade package, and then clickOK.11. In theMicrosoft Office 2000 Propertiesdialog box, click theRequired Upgrade for existing packagescheckbox. Donotclick OK yet.12. In theMicrosoft Office 2000 Propertiesdialog box, click theDeploymenttab, clickAssignedin theDeployment typefield, and accept the default option (Basic) in theInstallation user interface optionsfield.Review all the tabs to make sure you have edited all the properties and you are ready to assign the upgrade. ClickOK.Office 2000 with the transform is added to the Software Installation snap-in. The snap-in should now show Office 2000 as assigned, and it should show an upgrade relationship between Word 97 and Office 2000.At this point, if you log on to Windows 2000 as a user in the HQ Policy GPO, you should see Word 97 being removed, the start of the upgrade. When you select any of the Office icons from theStartmenu, you install Office 2000 to complete the upgrade.Assigning Windows 2000 to a Computer Upgrading Windows 2000You can upgrade Windows 2000 to the release version.Note:The operating system build being upgraded must be older than the build you are upgrading to.If you completed the Group Policy guide before this, you may have turned off applying Group Policy to computers. If this is the case, you need to change this before this Software Installation policy can be applied on the computers.In this scenario, you assign the upgrade of Windows 2000 to computers managed by a policy created for the Desktops OU under Resources. You could just as easily publish it for users.The RES-WKS-01 computer should be in the Desktops OU. If it is not, you need to move it to one of the OUs under the Resources OU. You can move the computer by highlighting it in the details pane of the Active Directory Users and Computers Snap-in and then selectingMovefrom the context menu.Note:To deploy the Winnt32.msi package, you need to modify the Unattend.txt file to include the Windows 2000 CD key information. Otherwise, the Setup program would ask for this information in a non-interactive desktop and wait indefinitely.1. Open the SIM Tool console you created earlier.2. Double-clickActive Directory Users and Computers, double-clickreskit.com, and then double-clickResources.3. Right-clickDesktops, and clickProperties.4. Click theGroup Policytab, clickNew, and typeDesktop OS Upgrades. PressEnter. ClickEdit.5. In the Group Policy snap-in, underComputer Configuration, double-clickSoftware Settings.6. Right-clickSoftware installation, clickNew, and then clickPackage.7. Browse to the network to the software distribution point that has the Windows 2000 files.Note:You may want to place the Windows 2000 CD in the CD drive of the server, and share the CD-ROM drive as the software distribution point for these files. This saves having to copy all the files to the software distribution point, although if the CD-ROM drive is not fast, the install may take longer.8. Click thei386folder, clickOpen, clickWINNT32(.msi file), and then clickOpen.9. In theDeploy Softwaredialog box, theAssignedoption on theDeploy Softwaredialog box is already selected. ClickOK.10. Close the Group Policy snap-in, then in theDesktop Propertiesdialog box, clickClosein theGroup Policypage.11. In the SIM Tool console, clickSaveon theConsolemenu, and then clickExiton theConsolemenu.At this point you should restart the RES-WKS-01 computer. When you do, the normal shutdown and startup messages are displayed.Eventually, in the Windows 2000 Professional startup dialogs you should see the following messages:Applying Software Installation settingsFollowed by:Windows Installer installing managed software Windows 2000 ProfessionalThe computer restarts and continues the upgrade.Important NotesThe example company, organization, products, people, and events depicted in these guides are fictitious. No association with any real company, organization, product, person, or event is intended or should be inferred.This common infrastructure is designed for use on a private network. The fictitious company name and DNS name used in the common infrastructure are not registered for use on the Internet. Please do not use this name on a public network or Internet.The Microsoft Active Directory structure for this common infrastructure is designed to show how Microsoft Windows 2000 Change and Configuration Management works and functions with the Active Directory. It was not designed as a model for configuring an Active Directory for any organizationfor such information see the Active Directory documentation.Top of pageAppendix An Excel 97 .Zap FileBelow is an example .zap file for Microsoft Excel 97.Use notepad to create the following text file and save it as excel.zap in the network folder that contains the Excel 97 setup program. The comments (any line that starts with ';') explain what each entry in the file is for.The underscore ( _ ) is a continuation symbol, these lines should appear together on one line.While the following example shows all of the possible entries in a ZAP file, note that many of these entries are optional. The smallest possible ZAP file to publish Excel 97 using the existing setup would be:[Application]FriendlyName = "Microsoft Excel 97"SetupCommand = \\servername\sharename\Excel 97\setup.exe; ZAP file for Microsoft Excel 97[Application]; Only FriendlyName and SetupCommand are required, ; everything else is optional; FriendlyName is the name of the application that ; will appear in the software installation snap-in ; and the Add/Remove Programs Control Panel.; REQUIREDFriendlyName = "Microsoft Excel 97"; SetupCommand is the command line that we use to ; Run the application setup. If it is a relative ; path, it is assumed to be relative to the ; location of the ZAP file.; Long file name paths need to be quoted. For example:; SetupCommand = "long folder\setup.exe" /unattend; or; SetupCommand = "\\server\share\long _; folder\setup.exe" /unattend; REQUIREDSetupCommand = setup.exe; Version of the application that will appear ; in the software installation snap-in and the ; Add/Remove Programs Control Panel. ; OPTIONALDisplayVersion = 8.0; Manufacturer of the application that will appear ; in the Software Installation Snap-in and the ; Add/Remove Programs Control Panel. ; OPTIONAL Publisher = Microsoft; URL for application information that will appear ; in the Software Installation Snap-in and the ; Add/Remove Programs Control Panel.;; OPTIONAL URL = http://www.microsoft.com/office; Language for the application, in this case US ; English. ; OPTIONAL LCID = 1033; Architecture, in this case, Intel.; OPTIONALArchitecture = intel; the [ext] [CLSIDs] and [progIDs] sections are ; all optional[ext] ; File extensions for which this application ; will "auto-install". They are not required if you ; do not want the application to auto-install. This ; entire section is OPTIONAL.; Note: You can put a dot in front of the file ; extension. Text after the first = is optional and ; ignored, but the first = is required (or the whole ; line will be ignored).XLS=XLA=XLB=XLC=XLM=XLV=XLW=[CLSIDs]; CLSIDs that this application will "auto-install" ; for. This entire section is OPTIONAL. ; Format is CLSID with LocalServer32, ; InprocServer32, and/or InprocHandler32 (in a ; comma separated list) after the =.{00024500-0000-0000-C000-000000000046}=LocalServer32{00020821-0000-0000-C000-000000000046}=LocalServer32{00020811-0000-0000-C000-000000000046}=LocalServer32{00020810-0000-0000-C000-000000000046}=LocalServer32{00020820-0000-0000-C000-000000000046}=LocalServer32{00020820-0000-0000-C000-000000000046}=LocalServer32[progIDs]; progIDs that this application will "auto-install" ; for. This entire section is OPTIONAL.; format is a CLSID, with the corresponding progid; listed after the = sign{00024500-0000-0000-C000- _000000000046}=Excel.Application{00024500-0000-0000-C000- _000000000046}=Excel.Application.8{00020821-0000-0000-C000-000000000046}=Excel.Chart{00020811-0000-0000-C000-000000000046}=Excel.Chart.5{00020821-0000-0000-C000-000000000046}=Excel.Chart.8{00020810-0000-0000-C000-000000000046}=Excel.Sheet.5{00020820-0000-0000-C000-000000000046}=Excel.Sheet.8{00020820-0000-0000-C000-000000000046}=Excel.Sheet{00020820-0000-0000-C000-000000000046}=Excel.Template{00020820-0000-0000-C000-000000000046}=Excel.WorkspaceTop of pageRelated LinksOnly for educational purpose not for commercial use