-
Dynamics CRM 3.0 Outlook Rule Deployment Wizard Issue
Here is a strange little issue that you will run into when you run the Rule Deployment Wizard to place the CRM forwarding rule into each CRM user's mailbox.
At some point it will allow you to select the names of the people to deploy the CRM Rule to. When you click Next, it will do something magical and show you a list of people who have "passed" or something.
It is probably at this point where you see a list of users but the Next button is disabled.
This is where the issue lies. What the Rule Deployment Wizard has done is to show you a list of users it has approved to recieve the rule. To make it actually work, you have to select the users to which you would like to see the rule deployed.
Once you select the users, the Next button activates and you can continue on with the process.
Dynamics CRM
(No Ratings Yet)3,565 views
Loading ... -
Dynamics CRM 3.0 Outlook Client on Terminal Services
A couple of months ago I installed the CRM 3.0 Outlook client on a Windows 2003 Terminal Server using the using the TS Client Deployment Kit.
As part of the configuration, you need to modify the command script ( terminstall.cmd ) that actually does the work. Here is a segment of the customization area:
REM *** Set below values for your deployment ***
REM ********************************************************
REM *** SOURCE = Location where the PST file, mail merge templates and CrmForOutlookTsInstaller.exe are located ***
SET SOURCE="\crm1TSClient"
REM *** Path where Microsoft CRM is installed ***
SET CRMPATH="%ProgramFiles%Microsoft CRM\\"
REM *** CRM Server to use ***
SET WEBAPPURL="http://crm"
REM ********************************************************
I edited the required variables and values and ran the command file. Everything looked like it worked, but when I launched Outlook from a Terminal Server session, it didn't work. Actually, it was very irritated with something, but what, I could not quite figure out.
THEN, I look at the MSCRMClient registry hive and noticed there was a double-quote ( " ) within the values of two of the directory names that the CRM client used. That is a bad thing and it was causing the CRM client to fail.
After having wasted more time than I wanted to admit, I finally figured out what happened.
Do you see that pair of backslashes ( \\ ) at the end of the CRMPATH variable above? That is not a typo. The backslash character is used as an "escape" character that allows you to embed special characters in scripts, etc. The two backslashes will actually be converted by Windows into a single backslash.
But, since I didn't know that at the time, I removed it and made the remaining backslash an escape character for the double quote and it actually inserted that closing double-quote into the registry key.
Cleaning Up the Mess
If you have done the same thing that I did, here is how you fix it:
- Run terminstall.cmd again to uninstall the current installation.
- Manually delete any files it left in the installation directories you specified.
- Edit terminstall.cmd and restore the double-backslash you removed.
- Rerun the terminstall.cmd installation script.
Dynamics CRM (No Ratings Yet)3,755 views Loading ...
Polls
Loading ...