Operating Environment - MSCRM 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/XP/Win2003 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.
Supported OmniRush Modules	The OmniRush Toolbar does not integrate with MSCRM at this time. The OmniRush Viewer and Universal Client do work with MSCRM v3.
Fax Receiving with OmniRush & MSCRM	This can be done either the the OmniRush Viewer (standard OmniRush operation) or using all the OmniRush DID features.
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.

If the OmniRush Viewer will be used to link faxes to contacts, and the CSID auto-lookup feature is desired, a customization must be made to MSCRM:

1. Go to the Settings\Customization\Customize Entities\

2. Open “Account” entity

3. Go to the “Attributes”

4. Add new attribute “OmniRushCSIDLookup” of type nvarchar, length 100

5. Repeate steps 2..4 for the “Contact” entity

6. Publish all changes

User Logins

The default security mechanism for MSCRM is “integrated security”. When a CRM users creates jobs in CRM, OmniRush automatically imports that user into OmniRush in the Users area (in order to know the 'From' information for the job).

Note: If the “Domain Logon Name” field is empty OmniRush will use the “Full Name” field, which may have spaces. The problem here is that certain advanced features of OmniRush need the user name (such as the OWN: override). Spaces in a user name would break these features. Our current understanding that this situation should never arise, however.

Here is the information that OmniRush references when auto-importing users from CRM into OmniRush: