3CX Assistant for Microsoft Terminal Services 8.11138

After high demand from 3CX administrators worldwide, we have finalized a version of the 3CX Assistant that is specifically designed for Windows Server OS with Terminal service roles enabled. Things to note in the 3CX Assistant TS installation (V8.11138):

  1. The Assistant installation will not prompt you to choose whether to install CRM or the 3CX Phone. These will be installed automatically but will not be enabled. The remote user must enable CRM and 3CX Phone Manually
  2. The 3CX TAPI Service will not be included because TAPI is not multi-profile aware. So the “Call Contact” via 3CX TAPI Service Provider context option in Outlook will not be available. Instead there will be the other context option – “Call Contact via 3CX” which will achieve the same functionality without TAPI.
  3. The user account used to install, uninstall or upgrade the 3CX Assistant must have full Administrator privileges. It is also important that before an installation, upgrade or un-installation, the administrator must make sure that there are no remote users logged in otherwise the server will need to be rebooted
  4. 3CX Assistants connected via 3CX Tunnel service protocol are not supported on a terminal services installation.
  5. Microsoft recommends that any applications that are planned to be used in a terminal services environment,  need to be installed AFTER the Windows server is promoted to a Terminal server.
  6. 3CX Assistant Updates will not be included and remote users will not be able to check for updates. Updating will be done by the Administrator and through a installation package.

Step 1: First time login for users – Simple connection via 3CX Assistant
The remote user needs to log in to the assistant for the first time to create the connection profile.

Step 2: Enable CRM Integration
After a successful first time connection, CRM can now be enabled. Click on the options tab and check the checkbox “Enable CRM Integration” and press the OK button.

Step 3: Registering the Outlook Plug-in
After the OK button is pressed, the CRM Wizard will automatically pop-up. This will register the plug-in addon in Outlook.

Go through the wizard configuration screens which will enable the user to configure CRM options and after the wizard is complete, the outlook plug-in will be enabled.

Step 4: Launch Outlook
Outlook can be launched on the user’s profile and you should receive a balloon tip notification that plug-ins are working correctly.

Step 5: Configuring Outlook Contact Folders
Go to the 3CX Assistant, click on File / CRM Settings and navigate to the CRM Plug-ins tab. Click on the Refresh button to query outlook for any contact folders.  Press OK to save the changes.

The 3CX Assistant is now configured to work with CRM on a Terminal Services Environment.

Liked this article?


Get notified of new articles
or share
You might also be interested in:
  1. Hi, we can’t get this damn “calling assistant” to function.
    All it says is “logging in” and nothing happends!! Everything else is working just fine in our 3CX phone system.

    February 27, 2010 at 9:10 pm
    • Hi, Is this on terminal server? Please open up a support ticket with our support department.

      March 1, 2010 at 1:34 pm
  2. Wally

    The 3CX terminal Assistant is great, except chat do not work. any idea?
    thank you
    Wally

    February 28, 2010 at 10:40 am
    • Its best to open a support ticket on this. Chat should work fine

      March 1, 2010 at 12:35 pm
  3. the best :) Works on anything – can also work on Vista and windows 7 with limited user account. flawless

    March 1, 2010 at 5:14 am
    • Good to hear that!

      March 1, 2010 at 12:35 pm
  4. Lee T.

    Are there special configurations required for 3CX Assistant on Terminal Server? We are planning on deploying this in the next implementation.

    March 4, 2010 at 12:40 pm
    • Yes, that is what this article is about. It requires a special install. See above :-)

      March 4, 2010 at 1:06 pm
  5. hv

    Works great on a single server :-),but in a server farm there are some ip dependencies in the outlook integration.

    March 10, 2010 at 2:52 am