Managing Applications by Using Windows Installer Packages
Objective:Manage applications by using Windows Installer packages.Windows Installer Windows Installer service runs on each computer, and depends on the Remote Procedure Call (RPC) service. The Windows Installer service, by default, does not start up automatically when you boot up Windows XP. Instead, it starts up whenever an .msi package is run. The service works in conjunction with the Msiexec.exe executable file, which interprets the information in the .msi file.NoteUse Msiexec.exe to repair .msi packages If you have trouble with an .msi package, you can run the Msiexec.exe file from the command line to repair the package. You can also use Msiexec.exe to control the installation process through its optional command-line switches, whether you run it from the command-line or use it in a script.Active Directory environments offer Group Policy control over Windows Installer deployments. An Active Directory administrator can deploy applications as follows:- Publish a package to users Enables users who receive this GPO to install the application through the Add/Remove Programs applet in Control Panel, or the installation is offered when the user attempts to open a file whose extension is associated with the application.
- Assign a package to users For users who receive this GPO, it automatically provides the application in the Start menu of any computer that the user logs on to. The application installs upon the activation of the icon in the Start menu or when the user attempts to open a file whose extension is associated with the application.
- Assign a package to computers For computers that receive this GPO, the application is installed automatically upon startup.
NoteNever assign a Windows Installer application to both a user and a computer If you do so, and the two GPOs use different transforms, the operating system installs and uninstalls the application every time it is accessed.Exam AlertKnow where you can publish a Windows Installer package You can assign a Windows Installer package to both computers and users. However, you can publish a Windows Installer package only to users.When you right-click any .msi file, you are presented with the following options specific to Windows Installer files:- InstallThe default
- RepairTo use when you have had a problem with installation
- UninstallTo remove the application (especially when the application installs incorrectly)
From the command line, you can use the Msiexec.exe file along with the .msi package name to install, uninstall, or repair the package, as well as to advertise or create an installation package. (Advertising a program does not install it on a computerit makes the application available for the user to install.) Step by Step 10.6 provides the method for installing an .msi file.
Step by Step" 10.6 Using Msiexec.exe
| 1. | Click Start, Run, type cmd in the Open text box, and press Enter. | | 2. | At the command prompt, type msiexec /I filename.msi. (If you have a copy of Microsoft Office 2003 multilingual, the filename is Muiwiz.msi.) | | 3. | The application begins installing and prompts for input. | | 4. | To remove the application, type msiexec /X filename.msi. | | 5. | The repair parameters can assist when troubleshooting a Windows Installer problem. To repair the application, type msiexec /F [parameter] filename.msi, where you replace [parameter] with a letter representing how to complete the repair. These parameters are listed in Table 10.3. | | 6. | To advertise an application, type msiexec /J [parameter] filename.msi. There are two parameters for advertising: m advertises to all users on the computer, whereas u advertises only to the current user. | | 7. | Administrative installation packages are required for deploying applications from network shares. |
Table 10.3. Parameters for Using msiexec /F to Repair an Application | Parameter | Function | Troubleshooting Usage |
|---|
| a | Reinstalls all the files for the application | Use when the application does not completely install. | | c | Reinstalls any missing file or one whose checksum is invalid | Use when you receive File missing error messages. | | d | Reinstalls any missing file or an invalid version of a file | Use after installing a different application that overwrites shared files and you receive errors or experience problems. | | e | Reinstalls any missing file, or an equal or older version of a file | Use when you have rolled back another application's installation and then you receive error messages. | | m | Rewrites the Registry entries of the applications that are attached to the computer (HKEY_LOCAL_MACHINE) | Use when the application displays the same error for all users who use the computer. | | o | Reinstalls any missing file or an older version of a file | Use when you have rolled back another application's installation and then you receive error messages. | | p | Reinstalls any missing file | Use when the application does not finish copying files. | | s | Re-creates application shortcuts | Use when you use a Start menu or desktop icon and the application does not open, but you can run the application from the command line or Run dialog box. | | u | Rewrites the Registry entries of the applications that are attached to the user (HKEY_USERS or HKEY_CURRENT_USER) | Use when the application works for one user but does not work for another, even though they are using the same computer. | | v | Caches a package locally (overwriting any existing cached package) and then runs the application from the source | Use when you install from a network location that is connected by a slow or unpredictable network link, or when the application has failed during the file copy process. |
|
NoteUsing Add/Remove Programs to start Windows Installer The Control Panel Add/Remove Programs applet automatically invokes Windows Installer to install, uninstall, or repair any application that uses the Windows Installer method.
Understanding MSI Features and Support
Before Windows transform file, which has the extension of .mst. The transform file answers the questions that the installation process asks, such as the path for the application, the component selection, and other configuration options.Exam AlertBeware of the ZAP ZAP files are used by Group Policy to install applications that are not native Windows Installer files. A ZAP file is created with a text editor and has a .zap extension. The file essentially provides basic installation instructions that Group Policy can use when assigning or publishing the application package.
Using Group Policy to Deploy MSI Packages
Group Policy is an administrator's best friend for implementing desktop settings. GPOs work with Windows 2000 and Windows XP clients and can deploy Windows Installer packages to these computers. To use Group Policy to deploy a Windows Installer package, follow the procedure in Step by Step 10.7. If you follow along with this exercise, you should already have an administrative installation of a software application created, as well as a transform file to script the installation. This exercise also requires a Windows 2000 or Windows 2003 Active Directory domain and a client computer.Exam AlertUnderstand the basics of Group Policy When you take the exam, you will probably run into questions that assume you know how Group Policy performs on a Windows 2003 Active Directory network. Take the time to brush up on the basics of Group Policy.
Step by Step: 10.7 Deploying Windows Installer Applications with Group Policy
| 1. | Log on to a domain controller as a domain administrator. | | 2. | Open the Active Directory Users and Computers console. If you do not have this console available in Administrative Tools, click Start, Run, type mmc in the Open text box, and press Enter. Select the File menu and click Add/Remove Snap-in. Click the Add button, select Active Directory Users and Computers from the list, and Click Finish. Click the Close button and then click OK to return to the console. | | 3. | Navigate to the OU to which you will be applying the group policy. | | 4. | Right-click the OU and select Properties. | | 5. | Click the Group Policy tab. | | 6. | Click New. | | 7. | Type a name for the GPO, and then right-click the policy and select Edit. | | 8. | The Group Policy Object Editor snap-in opens. | | 9. | To assign the software package to a computer, navigate to the Software Settings node below Computer Configuration. To assign or publish the software package to users, navigate to the Software Settings node below User Configuration. | | 10. | Right-click the Software Installation GPO, select New, and then click Package. | | 11. | Browse to the network share that contains the installation files for the application you are deploying. The .msi file should be in this folder. Click Open. | | 12. | The Deploy Software dialog box opens. Click the Assigned option and then click OK. | | 13. | Save the GPO and close all dialog boxes. | | 14. | To test the GPO, start the client computer. If you assigned the software to the computer, it should be installed automatically and you can validate this after logging on. If not, log on as a user in the OU, try to open a file associated with the application, and see whether the application installation begins. If you selected Published instead of Assigned, you should see the installation option for the application in the Add/Remove Programs Control Panel applet. |
|
|
لطفا منتظر باشید ...
