- CRM 4.0 Terminal Services support
- Posted by Todd K on December 19th, 2007
I have read through the CRM 4.0 planning guide and the "what's new in CRM
4.0" partner guide, and see very little mention of Terminal Services support
for the client Outlook 2003/2007 CRM Plugin. One example in the Planning
Guide page 4-63 shows a "Terminal Server, Microsoft Dynamics CRM for Outlook"
in "Domain B - Forest Y". There also appears to be a discrepancy between
these two guides in support for Windows 2000 SP4 - the what's new page 2-11
specifically says it is supported, and the planning guide page 3-29
specifically says it is not.
Is there, or will there be, support for Outlook 2003 and the CRM 4.0 plug-in
under Terminal Services 2000, 2003, and/or 2008? We run a pure TS
environment, so lack of support would prevent us from rolling out 4.0,
reverting to CRM 3.0.
Thanks for your help.
- Posted by Matt Parks on December 19th, 2007
As far as I know, term svcs is still supported with the desktop client for
4.0. The install should actually be a little easier this time around as
well. 4.0 will no longer support the 2000 level products though.
--
Matt Parks
MVP - Dynamics CRM
"Todd K" <Todd K@discussions.microsoft.com> wrote in message
news:98CE4119-B613-40DF-A105-A79AFE913044@microsoft.com...
I have read through the CRM 4.0 planning guide and the "what's new in CRM
4.0" partner guide, and see very little mention of Terminal Services support
for the client Outlook 2003/2007 CRM Plugin. One example in the Planning
Guide page 4-63 shows a "Terminal Server, Microsoft Dynamics CRM for
Outlook"
in "Domain B - Forest Y". There also appears to be a discrepancy between
these two guides in support for Windows 2000 SP4 - the what's new page 2-11
specifically says it is supported, and the planning guide page 3-29
specifically says it is not.
Is there, or will there be, support for Outlook 2003 and the CRM 4.0 plug-in
under Terminal Services 2000, 2003, and/or 2008? We run a pure TS
environment, so lack of support would prevent us from rolling out 4.0,
reverting to CRM 3.0.
Thanks for your help.
- Posted by Todd K on December 19th, 2007
Great, thanks for the quick reply.
Todd
"Matt Parks" wrote:
- Posted by enterprise2k5 on January 23rd, 2008
We have installed the outlook client on a TS on W2K3 platform, and are
getting errors stating that we need to have an exchange 2007 environment. It
is failing to install under the prerequisite check, due to this error. It
clearly states that this will work on Exchange 2003 environment, so this
would be no valid reason to fail.
Sean
"Todd K" wrote:
- Posted by Pell7 on April 11th, 2008
Hi Todd,
We are also having the same problems with TS and the 4.0 client. Haven't
had much luck finding any info on this. Have you had any success yourself?
"enterprise2k5" wrote:
- Posted by enterprise2k5 on April 16th, 2008
So, after major misunderstandings with MS reps that told us to remove
exchange from that server...and us telling them that exchange wasn't on that
server....I had one engineer who stated that he thought it had something to
do with doing a registry edit, and removing any exchange entries from the
registry hive.
During initialization, the Exchange OLE DB provider (ExOLEDB) scans the
HKEY_CLASSES_ROOT hive to identify registered file types.
We haven't made any progress as of yet, but that is the best lead we have.
"Pell7" wrote:
- Posted by Pell7 on April 16th, 2008
That's funny! I had the same conversation with them.
Thanks for the update, I appreciate it. I will be sure to post any findings
here.
"enterprise2k5" wrote:
- Posted by Ken on May 7th, 2008
See:
http://www.microsoft.com/communities...9-10e2027e6dab
Hope that helps.
"Pell7" wrote:
- Posted by Ken on May 7th, 2008
That was dumb, I meant to link here:
https://mbs.microsoft.com/knowledgeb...NZWQSNQVXTXXNP
"Pell7" wrote: