Planning and Preparing a Software Deployment
Before you can begin deploying software with Group Policy, you must plan the deployment. When planning for software deployment, you should
Review your organization’s software requirements on the basis of your overall organizational structure within Active Directory and your available GPOs
Determine how you want to deploy your applications
Create a pilot to test how you want to assign or publish software to users or computers
Prepare your software using a format that allows you to manage it based on what your organization requires, and test all of the Windows Installer packages or
repackaged software
Table 12-2 describes strategies and considerations for deploying software. Some of these strategies might seem contradictory, but select the strategies that meet your business goals.
Allows you to target applications to the appropriate set of users. Group Policy security settings are not required to target the appropriate set of users.
Makes it easy to provide all users in an organization with access to an application. This reduces administration because you can deploy a single GPO rather than having to re-create that object in multiple con-tainers deep Network+ certification in the Active Directory tree.
Reduces administration overhead by allowing you to create and manage a single GPO rather than multiple GPOs. The logon process is faster because a single GPO deploying 10 applications processes faster than 10 GPOs, each deploying one application. This is appropriate in organizations where users share the same core set of applications.
Makes it easier to determine which instance of the application applies to the user or computer.
Software licenses are required for software written by independent software vendors and distributed using SDPs. It is your responsibility to match the number of users who can access software to the number of licenses you have on hand. It is also your responsibility to verify that you are working
free exam question papers within the guidelines provided by each independent software vendor with the software.
Gather the Windows Installer packages (.msi files) for the software. Perform any necessary modifications to the packages and gather the transform (.mst) or patch (.msp) files.
Processing your request, Please wait....
