CHAPTER 7: DEPLOYMENT

Transcription

1 Chapter 7: Deployment CHAPTER 7: DEPLOYMENT Objectives Introduction The objectives are: Understand Software Deployment with Group Policy Deploy Microsoft Dynamics NAV 2009 RoleTailored and Classic clients with Group Policy Deploying Software is essential to meet the changing application needs of organizations and provide these benefits:. 1. When deploying Microsoft Dynamics NAV 2009 clients with Windows Server Group Policy, users no longer need to look for the application on a network share, use a CD-ROM or install, fix and upgrade software themselves. 2. Deploying Microsoft Dynamics NAV 2009 with Group Policy reduces time spent administering users systems. 3. Applications can be redeployed, upgraded or removed in the same meaner in which they were deployed. 7-1

2 Installation and Configuration in Microsoft Dynamics NAV 2009 Deployment Process The Software Installation and Maintenance feature of IntelliMirror is the administrator's primary tool for managing software within an organisation. The Software Installation extension in the Group Policy Object Editor console is the key administrative tool for deploying software. The Administrator controls which software is available to users within Add Or Remove Programs. Software can be either assigned or published, and targeted to users or computers. A workable combination of these methods can be established to meet your software management goals. Software Installation Extension Using the Software Installation extension allows administrators to assign or publish an application to a user. Assigning the RoleTailored Client When you assign a Microsoft Dynamics NAV 2009 RoleTailored Client to a user, the application is advertised to the user on the Start menu the next time they log on to a workstation and local registry settings, including filename extensions, are updated. It does not matter on which physical computer the user logs on to because the application advertisement is mapped to their user credentials. When you assign the RoleTailored client to a computer, the application is advertised and the client will be installed the next time the computer is restarted. Publishing the RoleTailored Client When you publish the RoleTailored client to a user, the application does not appear installed on the user s computer, no shortcuts are visible, and no updates are made to local registry on the users computers. Instead, the published applications store their information in Active Directory. The application is available for the user to use Add Or Remove Programs in Control Panel or by clicking on a file associated with the application. Software Deployment Processes The steps in software deployment vary depending on whether the application is published or assigned and whether the application is automatically installed by activating a document associated with the application. 7-2

3 Chapter 7: Deployment Published Applications This is the installation process for published applications: 1. The user logs on to a client computer running Windows 2000 or later. 2. The user opens Add Or Remove Programs in Control Panel. 3. Add Or Remove Programs obtains the list of published software form Active Directory. 4. The user selects the Microsoft Dynamics NAV Add Or Remove Programs obtains the location of published software from Active Directory. 6. A request for software is sent to the Software Distribution Point 7. The Windows Installer service is started, and it installs, the requested Windows Installer package. 8. The user opens the newly installed application. Assigned Applications This is the sequence of the installation process for assigned applications: 1. The user logs on to a client computer running Windows 2000 or later. 2. The WinLogon process advertises applications on the users desktop or on the Start menu. 3. The user selects Microsoft Dynamics NAV 2009 from the desktop or the Start menu. 4. The Windows Installer service gets the Windows Installer package. 5. A request for the software is sent to the Software Distribution Point. 6. The Windows Installer service is started, it installs the requested Windows Installer package, and it opens the application. Deploy Microsoft Dynamics NAV 2009 After you ve familiarized yourself with the software deployment tools, the Windows Installer service, and the software deployment processes, you re ready to learn how to deploy software with Group Policy. This lesson walks you through the steps of deploying software with Group Policy. The tasks for deploying software with Group Policy are: 1. Plan and prepare the software deployment 2. Set up an SDP 3. Create a GPO and a GPO console for software deployment 4. Specify the software deployment properties for the GPO 7-3

4 Installation and Configuration in Microsoft Dynamics NAV Add Windows Installer packages to the GPO and select package deployment method. 6. Set Windows Installer package properties Planning and Preparing to Deploy Software 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 computer 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 This table describes strategies and considerations for deploying software. Some of these strategies might seem contradictory, but select the strategies that meet your business goals. Strategy Create OUs based on software management needs. Deploy software close to the root in the Active Directory tree. Deploy multiple applications with a single GPO. Publish or assign an application only once in the same GPO or in a series of GPOs that might apply to a single user or computer. Considerations 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 containers deep 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. 7-4

5 Chapter 7: Deployment 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 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. Setting Up an SPD After you have planned and prepared for software management, the next step is to copy the software to one or more SDPs, network locations from which users are able to get the software that they need. To set up an SDP, complete the following steps: 1. Create the folders for the software on the file server that will be the SDP and make the folders network shares; for example: \\servername\sharename(file://\\servername\sharename). 2. Replicate the software to the SDP by placing or copying the software, packages, modifications, all necessary files, and components to a separate folder on the SDP. 3. Set the appropriate permissions on the folders. Administrators must be able to change the files (Full Control), and users must only view (Read) the files from the SDP folders and shares. Use Group Policy to manage the software within the appropriate GPO. Using DFS to Manage SDPs The Microsoft Distributed File System (DFS) provides users with convenient access to shared folders that are distributed throughout a network. With DFS, you can make files distributed across multiple servers appear to users as if they reside in one place on the network. For a software deployment with Group Policy, you can set up DFS to automatically direct users to the nearest SDP. Creating a GPO and a GPO Console In this step, you create a GPO and a GPO console for the software deployment. In this step, you define the default settings for all Windows Installer packages in the GPO in the Software Installation Properties dialog box. The Software Installation Properties dialog box consists of the following tabs General, Advanced, File Extensions, and Categories. 7-5

6 Installation and Configuration in Microsoft Dynamics NAV 2009 In the General and Advanced tabs, you specify how you want all Windows Installer packages in the GPO to be deployed and managed. In the File Extensions tab, you specify which application users install when they select a file with an unknown extension. You can also configure a priority for installing applications when multiple applications are associated with an unknown file extension. For example, if you use a GPO to deploy both Microsoft Office XP Professional and Microsoft Office FrontPage version 2002, both of these applications can edit Spreadsheet Load Library files with the.sll extension. To configure the file extension priority so that users who are managed by this GPO always install FrontPage, set FrontPage as the application with the highest priority for the.sll extension. When a user managed by this GPO who has installed neither Microsoft Office Word version 2002 nor FrontPage 2002 receives an.sll file (by or other means) and double-clicks the.sll file, Software Installation installs FrontPage 2000 and opens the.sll file for editing. Without Software Installation, the user would see the Open With dialog box and be asked to select the best alternative from the software already present on his or her computer. File extension associations are managed on a per-gpo basis. Changing the priority order in a GPO affects only those users who have that GPO applied to them. In the Categories tab, you can designate categories for organizing assigned and published applications to make it easier for users to locate the appropriate application from within Add Or Remove Programs in Control Panel. Specify Software Deployment Properties To specify software deployment properties for the GPO, complete the following steps: Open the GPO console for the software deployment. 1. In the User Configuration or the Computer Configuration node, right-click the Software Installation node, and then click Properties. 7-6

7 Chapter 7: Deployment 2. In the General tab of the Software Installation Properties dialog box type the Uniform Naming Convention (UNC) path (\\servername\sharename(file://\\servername\sharename)) to the SDP for the Windows Installer packages (.msi files) in the GPO in the Default Package Location box. FIGURE 7.1 SOFTWARE PROPERTIES DIALOG BOX 3. In the New Packages section, select one of the following: Display The o Deploy Software Dialog Box, to specify that when you add new packages to the GPO, the Deploy Software dialog box will display, allowing you to choose whether to assign, publish, or configure package properties. This is the default setting. o Publish, to specify that when you add new packages to the GPO, they will be published by default with standard package properties. Packages can be published only to users, not computers. If this is an installation under the Computer Configuration node of the Group Policy Object Editor console, the Publish choice is unavailable. o Assign, to specify that when you add new packages to the GPO, they will be assigned by default with standard package properties. Packages can be assigned to users and computers. o Advanced, to specify that when you add new packages to the GPO, the Properties dialog box for the package will display, allowing you to configure all properties for the package. 7-7

8 Installation and Configuration in Microsoft Dynamics NAV In the Installation User Interface Options section, select one of the following: o Basic, to provide only a basic display for users during the installation of all packages in the GPO. o Maximum, to provide all installation messages and screens for users during the installation of all packages in the GPO. 5. Click the Advanced tab. In the Advanced tab of the Software Installation Properties window, select any of these, to be applied to all packages in the GPO: o Uninstall The Applications When They Fall Out Of The Scope Of Management, to remove the application if it no longer applies to users or computers. o Include OLE Information When Deploying Applications, to specify whether to deploy information about Component Object Model (COM) components with the package. o Make 32-Bit X86 Windows Installer Applications Available To Win64Machines, to specify whether 32-bit Windows Installer Applications (.msifiles) can be assigned or published to 64-bit computers. o Make 32-Bit X86 Down-Level (ZAP) Applications Available To Win64Machines, to specify whether 32-bit application files (.zap files) can bea ssigned or published to 64-bit computers. FIGURE 7.2 ADVANCED TAB 7-8

9 Chapter 7: Deployment Click the File Extensions tab. In the File Extensions tab, shown in File Extensions tab, select the file extension for which you want to specify an automatic software installation from the Select File Extension list. FIGURE 7.3 FILE EXTENSIONS TAB 1. In the Application Precedence list box, move the application with the highest precedence 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. 2. Click the Categories tab. In the Categories tab, shown in Categories Tab of the Software Installation Properties dialog box, click Add. FIGURE 7.4 CATEGORIES TAB 3. 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. 4. Click OK. 7-9

10 Installation and Configuration in Microsoft Dynamics NAV 2009 Adding Windows Installer Packages to the GPO 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). To modify or update the software application, any modifications must be associated 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 application is assigned or published. 1. To add Windows Installer packages to the GPO and select package deployment method, complete the following steps: 2. Open the GPO console for the software deployment. In the Computer Configuration or User Configuration node, open Software Settings. 3. Right-click the Software Installation node, click New, and then click Package. In the Open dialog box, in the File Name list, type the UNC path (\\servername\sharename(file://\\servername\sharename)) to the SDP for the Windows Installer packages (.msi files), and then click Open. 4. In the Deploy Software dialog box, click one of the following: o Published, to publish the Windows Installer package to users without applying modifications to the package. o Assigned, to assign the Windows Installer package to users or computers without applying modifications to the package. o Advanced, to set properties for the Windows Installer package, including published or assigned options and modifications. FIGURE 7.5 DEPLOY SOFTWARE Click OK. If you selected Published or Assigned, the Windows Installer package has been successfully added to the GPO and appears in the details pane. If you selected Advanced, the Properties dialog box for the Windows Installer package opens, where you can set properties for the Windows Installer package, such as deployment options and modifications. 7-10

11 Setting Windows Installer Package Properties Chapter 7: Deployment In this step, you can fine-tune the deployment of each application by setting Windows Installer package properties in the Properties dialog box for the package. The Properties dialog box for the Windows Installer package contains the following tabs: General, Deployment, Upgrades, Categories, Modifications, and Security. In the General tab, you can change the default name of the package and designate a support URL. Users can select a support URL from the Add Or Remove Programs window to be directed to a support Web page. A support URL can contain helpful information such as frequently asked questions (FAQs) and can assist in reducing calls to a help desk or support team. In the Deployment tab, you can designate the deployment type, deployment options, and installation user interface options. In the Upgrades tab, you can deploy a package that upgrades an existing package. The Upgrades tab does not appear for packages created from application files (.zap files). Using the Upgrades tab is discussed in Lesson 3. In the Categories tab, you can select the categories under which the application is listed for users in Add Or Remove Programs in Control Panel, making it easier for users to find the application. Categories you set generally pertain to published applications only, as assigned applications do not appear in Add Or Remove Programs. In the Modifications tab, you can indicate the modifications (transforms or patches) you want to apply to the package and specify the order in which the modifications apply to the package. In the Security tab, you can indicate permissions for the software installation. Permissions set for software installation pertain only to the package installation. To set Windows Installer package properties, complete the following steps: 1. Open the GPO console for the software deployment. In the Computer Configuration or User Configuration node, open Software Settings. 2. Click the Software Installation node. 3. In the details pane, right-click the package for which you want to set properties, and then click Properties. 7-11

12 Installation and Configuration in Microsoft Dynamics NAV In the General tab of the Properties dialog box for the package, you can type a new name for the package in the Name box, if desired. You can also type a URL that provides user support in the URL box. FIGURE 7.6 GENERAL TAB 5. Click the Deployment tab. In the Deployment tab of the Properties dialog box for the package, select one of the following in the Deployment Type area: o Published, to allow users in the selected site, domain, or OU to install the application using either Add Or Remove Programs in Control Panel or application installation by file activation. If this is an application under the Computer Configuration node of the Group Policy Object Editor console, the Published option is unavailable, because packages can only be assigned to computers, not published. o Assigned, to allow users in the selected site, domain, or OU to receive this application the next time they log on (for assignment to users) or when the computer restarts (for assignment to computers). FIGURE 7.7 DEPLOYMENT TAB 7-12

13 Chapter 7: Deployment 6. In the Deployment Options area, select one of the following: o Auto-Install This Application By File Extension Activation, to use the application precedence for the filename extension as determined in the File Extensions tab of the Software Installation Properties dialog box. If this is an application under the Computer Configuration node of the Group Policy Object Editor console, the check box appears dimmed and selected, because by default the application is installed automatically. o Uninstall This Application When It Falls Out Of The Scope Of Management, to remove the application when users log on or computers start up in the event of relocation to a site, domain, or OU for which the application is not deployed. o Do Not Display This Package In The Add/Remove Programs Control Panel, to specify that this package should not be displayed in Add Or Remove Programs in Control Panel. o Install This Application At Logon, to specify that this package should be fully installed rather than just advertised by a shortcut. This option is available only for assigned applications. Avoid this option if the computer or user to which the application is assigned has a slow connection because the startup and logon procedures require a large amount of time when the application is first assigned. 7. In the Installation User Interface Options area, select one of the following: o Basic, to provide only a basic display to users during the install process. o Maximum, to provide all installation messages and screens to users during the package installation. 8. Click Advanced to display the Advanced Deployment Options dialog box. In the Advanced Deployment Options area, select any of the following check boxes: o Ignore Language When Deploying This Package, to specify whether to deploy the package even if it is in a different language. o Make This 32-Bit X86 Application Available To Win64 Machines, to specify whether the 32-bit program is assigned or published to 64-bit computers. 7-13

14 Installation and Configuration in Microsoft Dynamics NAV 2009 o Include OLE Class And Product Information, to specify whether to deploy information about COM components with the package. FIGURE 7.8 ADVANCED DEPLOYMENT OPTIONS DIALOG BOX 9. Click OK. 10. Click the Categories tab. In the Categories tab of the Properties dialog box for the package, shown in Figure 7-9, click the category under which you want to display this application to users from the Available Categories list, and then click Select. FIGURE 7.9 CATEGORIES TAB 7-14

15 Chapter 7: Deployment 11. Click the Modifications tab. In the Modifications tab, Do any of the following: o To add modifications, click Add. In the Open dialog box, browse to find the transform file (.mst) or patch file (.msp), and then click Open. You can add multiple modifications. o To remove modifications, click the modification you want to remove, and then click Remove. Repeat until each unwanted modification has been removed. o To set the order of modifications, select a modification and then click Move Up or Move Down. Modifications are applied according to the order specified in the list. FIGURE 7.10 MODIFICATIONS TAB Do not click OK in the Modifications tab until you have finished configuring the modifications. When you click OK, the package is assigned or published immediately. If the modifications are not properly configured, you will have to uninstall the package or upgrade the package with a correctly configured version. 7-15

16 Installation and Configuration in Microsoft Dynamics NAV Click the Security tab. In the Security tab of the Properties dialog box for the package, click the security group on which to set permissions. Administrators who manage the application installation should have the Full Control permission set to Allow. Users who use the software assigned or published by the application should have the Read permission set to Allow. FIGURE 7.11 SECURITY TAB 13. Click OK. Microsoft Dynamics NAV 2009 Settings To configure the RoleTailored client and the NAV Server in Microsoft Dynamics NAV 2009 Setup: 1. Double-click RoleTailored client in the Specify parameters pane. 2. Provide values for the settings. For example: Setting Server Name Server Port SQL Server Values Since the RoleTailored client and the NAV Server are both to be installed on the local computer, use localhost as the value for this setting. Value is not relevant. The default (7046) is fine. Identifies the network server computer where SQL Server is installed. In our example, this computer is named jetsam. 7-16

17 Chapter 7: Deployment Setting SQL Database Web Service Port Values Identifies the SQL database to use. In our example, the database name is operations4. The default value (85) is fine. 3. Click Apply to save the settings and return to the Specify parameters pane. To create a Setup configuration file: 1. In the Specify parameters pane, click Save the configuration. 2. In the Save As window, provide appropriate path and filename information. Click Save to exit the Save As window and return to the Specify parameters pane. That's it. At this point you can go ahead and click Install to begin installing Microsoft Dynamics NAV Or you can click in the upper-right corner of the Setup screen to exit setup without installing any software for now. Summary The tasks for deploying software with Group Policy are the following: plan and prepare the software deployment, set up an SDP, create a GPO and a GPO console for software deployment, specify the software deployment properties for the GPO, add Windows Installer packages to the GPO and select package deployment method, and set Windows Installer package properties. For a software deployment with Group Policy, you can set up DFS to automatically direct users to the nearest SDP. You can define software deployment properties that affect all Windows installer packages in a GPO. You can also define software deployment properties that affect individual Windows Installer packages in a GPO. Microsoft Dynamics NAV 2009 deployment settings were discussed 7-17

18 Installation and Configuration in Microsoft Dynamics NAV 2009 Quick Interaction: Lessons Learned Take a moment and write down three key points you have learned from this chapter: