Distributing Windows Installer Packages

By Author: fiona
Total Articles: 191
Comment this article

Because the Windows Installer service is part of the operating ccna boot camp system, it does not mat-ter how Windows Installer packages get to the client computer. If you are deploying software to many users in a large organization that is using Windows 2000 Server or later and Active Directory, and all of the workstations are using Windows 2000 Professional or later, you can deploy software with Group Policy. For large-scale deploy?ments or deployments with computers running preWinclows 2000 operating systems, you might also consider using the Microsoft Systems Management Server (SMS) along with Group Policy to handle software deployment.
Software deployment with Group Policy uses a pull model, which makes software available to users as it is needed. Applications are fully installed when a user chooses to use a user-assigned application for the first time or selects a file by choosing the filename extension of an application. For a satisfactory end-user experience, software deployment with Group Policy requires a high-speed local area network (LAN) connection between the client ...
... computer and the distribution server containing the SDP.
SMS supports a robust distribution model that you can use when deploying software with Group Policy. You can use SMS to analyze your network infrastructure for soft-ware distribution and then use Group Policy to target mcitp users and computers and to install the software. SMS is a particularly useful tool if you are deploying software to many users in a large organization. It includes desktop management and software distribution features that significantly automate the task of upgrading software on client computers.
SMS uses a. push model for software deployment, which you can use to coordinate and schedule software deployments, even arranging for off-hours distribution and installation, and to plan a single or multiple-phase rollout of software. It provides you with the ability to control and synchronize software deployments over multiple sites, helping to reduce compatibility issues that might otherwise occur.
The following are some of the areas where you might want to supplement software deployment with Group Policy by using SMS:
Non—Windows 2000-based clients SMS can distribute Windows Installerbased software to computers running Microsoft Windows 95 or later. Although
you cannot centrally manage the non-Windows 2000-basecl computers with Group Policy settings, SMS allows these computers to benefit from the capabilities built into the Windows Installer service, such as self-repairing applications.
Deploying software over slow links By default, software deployment with Group Policy does not operate over slow network or dial-up connections. SMS
provides options for deploying software to users who can connect free CompTIA practice tests only over slow network links, such as mobile users.