Operating Environment - Microsoft CRM v1.x

Note that MS CRM v1.x support is deprecated in OmniRush v9.0 and up.

 

Click here for Microsoft Dynamics CRM v3.

 

The Connector for Microsoft CRM (MS CRM) requires that the MS CRM system be installed, configured, and operational before installing OmniRush.

 

There are a number of options on how OmniRush can be configured, so here are the details.

 

Environment Item

Discussion

Where to install OmniRush

OmniRush can be installed onto any Windows2000 PC (Pro, Server, etc.) that resides in the same Active Directory domain as MSCRM.  In nearly all cases, OmniRush should not be installed on the MSCRM server.  See the software coexistence matrix for information on what can coexist with OmniRush.

OmniRush Server Side Support Only

The OmniRush Viewer, Toolbar and Universal Client do not integrate with MSCRM at this time.  MSCRM support is from the OmniRush Server, which provides all job types from the built-in MSCRM Fax UI, from the OmniRush UI plugin, and from MSCRM Workflow.

Fax Receiving with OmniRush & MSCRM

OmniRush can be used for receiving faxes with MSCRM when OmniRush is set to forward all faxes as email.  This can be set up with or without DID hardware.

 

In this scenario, the OmniRush viewer is probably not used, rather all inbound faxes are handled using the email system (e.g. Outlook).

OmniRush UI

Installing the OmniRush UI will require administrative access to the MS CRM Server(s).  See the detailed installation instructions.

Required Credentials

You will need two kits of credentials to set up OmniRush:

 

MSCRM credentials:  This should be an Active Directory user who is configured as an MSCRM Administrator.  A dedicated userid is not required for this purpose, however some installations may have audit requirements that demand a dedicated userid (and ergo, MSCRM license) for OmniRush.

 

Note, MSCRM user licenses are not included with OmniRush.  Contact your MSCRM reseller for appropriate MSCRM licensing.

 

SQL Server credentials.  This should be either an Active Directory or SQL Server userid that has dbo role in the MSCRM database.

 

Note: After OmniRush is configured, changing the passwords on either of these accounts will cause OmniRush to shut down.  Make sure to either plan to update OmniRush when passwords change, or disable periodic password expiration on the accounts used by OmniRush.