ODMS Client Workgroup Installation Guide

• Run the Launcher.exe found on the Client CD
• Select Workgroup Installation.

• Click Next

• Accept the license agreement and click next

• Enter the license manager address and port number to match that of the License Manager.

• If the details are incorrect, it will fail to connect to the License Manager as shown below.

• By default, both modules will be installed. If you only want one module installed then click on the other module and select “This feature will not be available.”

• Leave the destination folder as default and click Next.

• Select WorkGroup for user profiles to be managed in repositories

• Choose the appropriate repository setting depending on how you have setup the repository on the server.

• If you are using the repository service please ensure this setting corresponds to the repository service on your server, otherwise it will fail to connect to the repository service as shown below.

• Click Install

• Click Finish

ODMS can be distributed to client users and PC’s using Group Policy.

Before beginning a deployment, please ensure the software MSI package and the customised MST package are in a shared folder which is accessible to all the Olympus users and computers to install the software. If you haven’t created an MST package please follow the MST creation guide.

A Group Policy Object should be created for Dictation Module and another for Transcription Module.

• Right click the new Group Policy Object and select “Edit…”.

• From “Computer Configuration” expand “Policies” > “Software Settings”.
• Right click “Software Installation” and choose “New” > “Package”.

• Browse to the repository location where the ODMS Client software package resides and choose “ODMSClient.msi”.

• Select “Advanced” and click “OK”.

• The properties window will now appear.

  

• Click on the “Modifications” tab and click “Add…”.
• Select the MST file created by the System Configuration Program and choose “Open”. In this example we will use “ODMSClientDM.mst”.

• The MST file location will now appear in the modifications list. Press “OK” to confirm the settings and assign the application.

• Next, specify the target for who will receive the deployed installation. Go to Security Filtering and click Add

• Then enter the target object; this can be a user, a PC or a group.

• Now the Group Policy Object is ready to be linked to your domain

Please ensure the software MSI package and the customised MST package are in a shared folder which is accessible to all the Olympus users and computers to install the software. If you haven’t created an MST package please follow the MST creation guide.

You will require the following details when creating a batch file:

• UNC path to “ODMSClient.msi”
• UNC path to “ODMS_DM.mst” and “ODMS_TM.mst”

The batch file should be saved in the same folder as ODMSClient.msi. It is recommended to create two batch files, one to install the Dictation Module and one to install the Transcription Module.

Each batch file should be named to reflect the module of software being installed, for example, DM.bat and TM.bat.

To create a batch file:

• Open a new notepad document
• Enter the following text: msiexec.exe /i “UNC path to ODMSClient.msi” TRANSFORMS=”UNC path to ODMS_DM.mst” /qb

• Choose “File” > “Save As” to save the document as a batch file.

• Choose a file name including the extension “.bat”.

• The batch file is ready to be used for installation, you can double click the newly created batch file to install the software. A command prompt window will appear after executing. Once the command prompt window disappears, the software should be installed and ready to use.

The batch file can also be deployed out to the users. In the example below, we will use Group Policy.

• Create a new GPO
• Go to Computer Configuration, expand Policies, expand Windows Settings, click on Scripts and choose Startup

• Click Add

• Browse to your batch file and click Open

• Click OK to add the batch file to the Startup script.

• Next, specify the target who will receive the deployed installation by going to Security Filtering and click Add

• Then enter the target object; this can be a user, a PC or a group.

• Now the Group Policy Object is ready to be linked to your domain