ODBC Driver for Dynamics 365

Remote Deployment and Activation - ODBC Driver for Dynamics 365

Installing and Activating Software Remotely

Group Policy automated-program installation is specifically designed for deploying Windows Installer packages (MSI files). Therefore, when deploying the ODBC Driver for Dynamics 365 using Group Policy, be sure to use the corresponding MSI file for the ODBC Driver for Dynamics 365.

Prerequisites: Locating the MSI Installation File

Prior to making configuration settings in the Group Policy, you'll need to create a distribution folder:

  1. Create a shared network folder on the publishing server.
  2. Set the appropriate sharing permissions on this folder to allow read access to the driver installation package for all domain users.
  3. Download the ODBC Driver for Dynamics 365 MSI file, and place it in the network folder.

The MSI file for the ODBC Driver for Salesforce is taken as an example to illustrate the Group Policy installation process. Use the same steps described in this section when installing the ODBC Driver for Dynamics 365.

Further in this section, you'll find more detailed information on how to deploy and activate the ODBC Driver for Dynamics 365 on remote client computers using Group Policy.

Server-Side Actions

  1. Open the Group Policy Management desktop application.
  2. In the Group Policy Management window, navigate to the desired forest node, then expand the appropriate option under the Domains node. For this example, we'll select devart-test.test. Right-click the Domains node, and from the context menu, select Create a GPO in this domain, and Link it here.

    Creating and Linking a GPO

  3. You can now create a New Group Policy Object. In the New GPO dialog enter a name for the new object and click OK. The new GPO will then appear within the Group Policy Management container.
    For example, let's create a GPO named after the ODBC driver name.

    Entering a new GPO name

    Keep in mind that each ODBC Driver for Dynamics 365 Windows installation package corresponds to one Group Policy Object (GPO), which is important for managing future software upgrades. To install multiple drivers using Group Policy, you need to create a separate GPO for each driver you want to deploy.

  4. Right-click the new object and select Edit from the context menu.

    Editing a GPO

  5. In the left pane of the Group Policy Management Editor, navigate to Computer Configuration --> Policies --> Software Settings --> Software installation. Your current deployment package will appear in the right pane. Right-click Software installation, then select New --> Package.

    Creating a New Package

  6. In the Group Policy Management Editor dialog that opens, select the desired MSI installation file and click Open.

    Browsing to the MSI installation file

  7. In the Deploy Software dialog, select Advanced to specify the software deployment method. The Advanced deployment method allows you to make necessary modifications to the MSI file, such as creating the MST file in Orca.

    Selecting Advanced Software Deployment Method

  8. In the Properties dialog of the installation package that opens, go to the Modifications tab and select Add. Browse for the corresponding MST file, select it, and click Open to apply the settings.

    Adding MST file in Properties dialog

  9. If configured correctly, the Group Policy Management Editor window should look as follows:

    Assigned MSI file in Group Policy Management Editor

Client-Side Actions

For the ODBC Driver for Dynamics 365 to be successfully installed on remote client machines, all domain users must restart their computers after logging in for the first time.

In case of successful deployment, the ODBC driver will be installed on the client's computer. To verify, open the ODBC Data Source Administrator on the client's machine and add the deployed ODBC driver.

ODBC Driver installed on remote client's computer

All information on the deployed driver is accessible upon clicking the About tab.

ODBC Driver OEM license on remote client's computer

Similarly, the valid license key will be automatically activated after the successful installation of the ODBC Driver for Dynamics 365.

ODBC Driver OEM license on remote client's computer

See Also

© 2015-2024 Devart. All Rights Reserved. Request Support ODBC Forum Provide Feedback