Things that will not work properly using terminal services

[nattivillin]

We have been using CommitCRM via terminal services for about 2 years now. We gained, speed, reliability, and the ability to run the full client it over the vpn / rdc from anywhere.

Using the client anywhere was the primary goal.

Previously the entire staff didn't use the client due to the slowness via VPN. Now that everyone uses the client, we are amazed that many of the advanced features don't work properly.

The two that cause the most complaints;

1) sync outlook with CommitCRM
2) email items from CommitCRM

Both are related to email.

If you don't know, you cant just install office / outlook on a terminal server. You need either SPLA or open value / select type licensing. That adds to the cost considerably.

Without spending that extra cost for the microsoft licensing how are CommitCRM users taking advantage of all the things you need an installed email client to do?

[Support Team]

Re: Things that will not work properly using terminal services

RangerMSP is NOT an email client application and does not come to replace Outlook and therefore you have to have Outlook installed in order to send new emails out of RangerMSP.

[nattivillin]

Re: Things that will not work properly using terminal services

How many other things don't work properly while using as a terminal server.

I just noticed we cant use any web services either. Since the default browser on a server is IE with enhanced security, none of them work properly.

[nattivillin]

Re: Things that will not work properly using terminal services

How many other things don't work properly while using as a terminal server.

I just noticed we cant use any web services either. Since the default browser on a server is IE with enhanced security, none of them work properly.

[aaspeer]

Re: Things that will not work properly using terminal services

We have used terminal services for years (and its a solution we provide and install for many clients)

We have had no problems at all using terminal services and CommitCRM with outlook 2013. We use the Microsoft Action Pack which gives us all of the licensing that we need. Internet explorer also works fine, we disabled the enhanced security within the server.

[nattivillin]

Re: Things that will not work properly using terminal services

The Microsoft action pack software isnt supposed to be installed in a terminal server environment. (Unless they updated their EULA since I last checked)

It wouldn't even let us install it the last time we tried. How did you get it installed?

[nattivillin]

Re: Things that will not work properly using terminal services

The MAPS program doesn't include the volume license media or keys required to install in a terminal server.

The standard pro plus 2013 will not install (I just tried).

[aaspeer]

Re: Things that will not work properly using terminal services

We have had action pack for years, it includes 10 CALs for Remote Desktop Server and Office Pro Plus 2013 (Which we installed successfully) - Initially upon install, it gave me an error about it not being supported, yet it works just fine.

[raymond]

Re: Things that will not work properly using terminal services

MAPS does include Terminal Server CAL's however the Office licensing included in MAPS does NOT include running on an RDS/Terminal Server. From the Internal Use Rights Product Usage Guide:

For Action Pack subscribers, the software and keys issued to you are not compatible for operating Office 2013 in a Remote Desktop Services (RDS) environment. Using Office 2013 in a Remote Desktop Services (RDS) environment is not supported. If you require this functionality, the application needs to be purchased from the appropriate Volume Licensing program.

Partners do not receive all the Volume Licensing benefits associated with Office Professional Plus:
 Action Pack subscribers do not have access to Office Web Apps, Office Multi-Language Pack, and Remote Use Rights such as Remote Desktop Services (RDS). These benefits are available to competency partners.
 Both Action Pack subscribers and competency partners do not receive the following benefits: downgrade rights, Office Home & Student 2013 RT for commercial use, Roaming Use Rights, use of Office installed on a USB drive with Windows To Go, and Home Use Programs.

Simply put, if you are running Office from MAPS on a Terminal Server (not sure how you did that because the bits should not load), you are 100% violating the licensing agreement. Yes, it's stupid and MS has their head up their arses on this one but them's the rules...

We ended up ponying up for the Open licenses so we could run it on our RDS server... we are not happy about it but it's a must for us so simply became a cost of doing business expense.

Now, all that said, if Commit would "fix" the email connector and make it so that it directly communicated with Exchange, we wouldn't need to rely on Outlook to do all the sync work which might save everyone much trouble and some $'s along the way. Just another example of why we need direct Exchange support... (!)

Thanks!

//ray

[raymond]

Re: Things that will not work properly using terminal services

Oh, and we have not really noticed issues with running the CommitCRM client on RDS/TS. We did purchase and use the SQL Database module so that might make some differences.

Cheers!

//ray