Preparing Microsoft Dynamics CRM for Outlook for a Group Policy deployment

[Applies to: Microsoft Dynamics CRM 4.0]

Follow this procedure to create the CRMClient.msi file that is required for a Microsoft Dynamics CRM for Outlook Group Policy deployment.

To create the CRMClient.msi file, follow these steps:

  1. Determine the distribution point and copy the MSI package in that location.
    • Run SetupClient.exe at the command prompt by using the /A and /targetdir parameters. The /A parameter specifies an administrative installation, and /targetdir specifies the target directory. After Setup is complete, you can share the location. For more information, see Use the Command Prompt to installMicrosoft Dynamics CRM.
    • Consider using Microsoft Distributed File System (DFS) and File Replication Service (FRS) to help improve the security and availability of your distribution points. For more information about DFS, FRS, and how to deploy Microsoft file server technologies, refer to your operating system documentation. We recommend that you understand those features before you configure your distribution point servers.
  2. Create the Group Policy object (GPO) and target the application to Microsoft Dynamics CRM Users. To do this, follow these steps:
    1. On a domain controller in the domain where Microsoft Dynamics CRM is installed, click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.

      You may have to download and install the Group Policy Management Console (GPMC) with SP1 snap-in. For more information, see Internet Security and Acceleration Server.

    2. In Active Directory Users and Computers, right-click the domain, and then click Properties.

    3. In the Properties box, click the Group Policy tab, and then click Open.

    4. In Group Policy Management, right-click the domain, click Create and Link a GPO Here, type a name for the Group Policy object, such as Microsoft Dynamics CRM Users, and the click OK.

      Creating a GPO at the domain level configures the GPO with domain-wide scope.

    5. Right-click the GPO that you created in the previous step, and then click Edit.

    6. In Group Policy Object Editor, expand User Configuration, and then expand Software Settings.

    7. Right-click Software Installation, point to New, and then click Package.

    8. Type the full path or locate the Microsoft Dynamics CRM for Outlook MSI package (CRMClient.msi) that was created by the administrative installation, and then click Open.

      Users must have Read access to this path.

    9. Click Publish to publish the Microsoft Dynamics CRM for Outlook application, and then click OK.

    10. By default, Microsoft Dynamics CRM for Outlook is available in Add or Remove Programs for all authenticated users the next time that they log on to the domain. To limit the scope to a specific OU, Group, or individual User, in Group Policy Management, click the GPO named Microsoft Dynamics CRM Users, and then add or remove the security objects that you want, such as a group, in the Security Filtering area of the publication on the Scope tab.

Publish versus assign

When you publish an application by using GPO deployment, it is made for users to install by using Add or Remove Programs in Windows Control Panel. Assigned applications are installed when a user logs on to the domain.


Microsoft Dynamics CRM for Outlook does not support application assignment through GPO installation. For more information about publishing versus assigning software, see the Group Policy deployment documentation for your operating system.

© 2011 Microsoft Corporation. All rights reserved.