asp.net c# print barcode Deploying Software with Group Policy in Visual C#

Drawer Quick Response Code in Visual C# Deploying Software with Group Policy

12

Maximum, to provide all installation messages and screens for users during the installation of all packages in the GPO.

6. Click the Advanced tab. In the Advanced tab, shown in Figure 12-2, select any of the following, to be applied to all packages in the GPO:

Uninstall The Applications When They Fall Out Of The Scope Of Manage ment, to remove the application if it no longer applies to users or computers. Include OLE Information When Deploying Applications, to specify whether to deploy information about Component Object Model (COM) components with the package. Make 32-Bit X86 Windows Installer Applications Available To Win64 Machines, to specify whether 32-bit Windows Installer Applications (.msi files) can be assigned or published to 64-bit computers. Make 32-Bit X86 Down-Level (ZAP) Applications Available To Win64 Machines, to specify whether 32-bit application files (.zap files) can be assigned or published to 64-bit computers.

Off the Record In rare instances, when applications installed with Software Installation cannot be uninstalled by using Group Policy or Add/Remove Programs, you can use the MSICUU.exe (Windows Installer Cleanup Utility) or the MSIZAP .exe (Windows Installer Zapper) programs. These utilities are part of the Windows Support Tools, which you installed in 2. MSICUU is a graphical utility and MSIZAP is the command line version. MSICUU uses MSIZAP to remove applications. For detailed information about using these commands, refer to Windows Server 2003 Help.

12-19

7. Click the File Extensions tab. In the File Extensions tab, shown in Figure 12-3, select the file extension for which you want to specify an automatic software installation from the Select File Extension list.

8. In the Application Precedence list box, move the application with the highest pre cedence to the top of the list using the Up or Down buttons. The application at the top of the list is automatically installed if a document with the selected filename extension is invoked before the application has been installed. 9. Click the Categories tab. In the Categories tab, shown in Figure 12-4, click Add.

10. In the Enter New Category dialog box, type the name of the application category to be used for the domain in the Category box and click OK.

12-20

12

Note The application categories that you establish are per domain, not per GPO. You need to define them only once for the whole domain.

In this step, you specify the software applications you want to deploy by adding Windows Installer packages to the GPO. Then you specify how the package is deployed (either assigned or published).

Note The procedures in this step assume that you have chosen the Display The Deploy Software Dialog Box option (the default option that allows you to choose whether to assign or publish the application) in the software deployment properties for the GPO.

To modify or update the software application, any modifications must be associ ated with the Windows Installer package at deployment time rather than when the Windows Installer is actually using the package. Transform (.mst) and patch (.msp) files are applied to Windows Installer packages (which have the .msi extension) in an order specified by the administrator. This order must be determined before the appli cation is assigned or published. To add Windows Installer packages to the GPO and select package deployment method, complete the following steps: 1. Open the GPO console for the software deployment. In the Computer Configura tion or User Configuration node, open Software Settings. 2. Right-click the Software Installation node, click New, and then click Package. 3. In the Open dialog box, in the File Name list, type the UNC path (\\server name\sharename) to the SDP for the Windows Installer packages (.msi files), and then click Open.