Automatic Software Update Using Group Policy
If the ODBC Driver for WordPress was initially deployed through Group Policy, it can be easily updated to a newer version. Follow the steps below to update both the ODBC Driver for WordPress and the license to newer versions on all remote computers in the domain.
-
Download the ODBC Driver for WordPress installation MSI file of a newer version and place it in the shared network folder.
-
Create a new MST file with a new license key using Orca.
If your license is still valid, there's no need to create a new MST file. Use the current MST file instead.

-
Follow the same workflow as outlined in Step 4 to Step 7 of the ODBC Driver for WordPress Remote Deployment and Activation section.
-
In the Properties dialog that appears after selecting the Advanced deployment method, go to the Upgrades tab and click Add.

Make sure to select the following check boxes while adding the package:
-
Current Group Policy Object
-
Package can upgrade over the existing package
-
Browse for the corresponding GPO object and click OK to apply the settings.

-
Now the Upgrades tab of the Properties dialog will list a new package with a newer version.

-
Go to the Modifications tab in the same properties dialog, click Add and browse to the MST file.
We have already created a new MST file with a new license key in Step 2.

-
In case of a positive outcome both the old and new versions of the driver package will be displayed in the Group Policy Management Editor.

Once the GPO configuration on the server is complete, the ODBC Driver for WordPress will automatically update to the latest version each time a client computer restarts.
Client-Side Actions
To update the ODBC Driver for WordPress to a newer version on remote client machines, all domain users must restart their computers after their first login.
If successful, both the driver and the license key will be automatically updated to the new version on remote computers. For detailed instructions on how to view the technical details of the ODBC Driver for WordPress after upgrading, refer to Client-Side Actions.
See Also