3CX Assistant V9 for Terminal Services

3CX is pleased to announce service 3CX Assistant client installer for Terminal Services. This installer allows you to install the 3CX Assistant on a Windows Server operating system which has been promoted to a Terminal Server.

Important Notes to take into consideration before installing

  • Version number of the 3CXAssistant for Terminal services is the following: 9.15035
  • This Version has been tested on Windows 2008 R2 with Terminal Services Role installed
  • This installation package is to be used only in terminal services scenarios.
  • TAPI will not work in the TS installation because TAPI is not multi user aware.
  • Outlook and any other applications that need to be installed, must be done AFTER the machine is promoted to a terminal server.
  • The 3CX Assistant should be installed AFTER the Windows Server is already a Terminal server.
  • This guide assumes that if you any previous installations of the 3CX Assistant for terminal services are Uninstalled before the Version 9 installation is initiated. Install-Overs are not supported and can cause problems.
  • If you remove/Uninstall the 3CX Assistant Terminal services installation, make sure that All active terminal sessions are logged off. This ensures that instances of Outlook, Assistant or 3CXPhone are not currently running on the TS.

Installation procedure:

  1. Log in to the terminal server using the Domain Administrator Account. (The outlook add-on will only work for the Domain\Administrator account and will NOT work for the Local\Administrator Account)
  2. Download the 3CX Assistant for TS installation package from here
  3. Select whether you want CRM (Right click on CRM and select “Will be installed on Local Hard Drive”) and optional 3CXPhone in the Custom Setup screen.
  4. After the installation is complete, you can double click the 3CX Assistant Icon located on your desktop. You can now tell your users to start a TS session and start their Assistants from their Desktops.

How to identify that the Outlook plug-in has been registered correctly:

  1. Open Outlook
  2. Click on File/Options
  3. in the Outlook Options screen click on Add-Ins
  4. If you see the 3CX Assistant Microsoft Outlook Add-in in the Active applications Add-ins, then the add-in registration was successful. If the 3CX Assistant add-in is under the Inactive Appluication Add-ins, then the add-in registration failed

What to do is the plug-in does not register correctly. Perform the following steps:

  1. Exit the 3CX Assistant
  2. Exit Outlook
  3. Navigate to the CRM folder example: C:\Program Files\3CX Assistant\CRM and locate the following executable “3CXCRMWizard.exe”. Double click this exe. A script will run that will re-register/modify the outlook add-on on your current user profile.
  4. Log off your TS session and log in again.
  5. Start The 3CX Assistant and proceed to start Outlook. The add-in should be correctly registered now.

Liked this article?

Get notified of new articles
or share
You might also be interested in:
  1. Pingback: 3CX VoIP Blog » 3CX Assistant V9 for Terminal Services

  2. Chris


    This has been a long time coming but I’m glad the day is finally here! The sun is shining, the birds are singing and our terminal users can once again enjoy the convenience of the 3CX assistant.

    For v10, please develop and release this concurrently with the primary product so I don’t have to strip it from our users when we upgrade.

    Good job!

    November 19, 2010 at 9:10 pm
  3. Pingback: 3CX VoIP Blog » 3CX Assistant V9 for Terminal Services

  4. Igor Snezhko

    “Outlook and any other applications that need to be installed, must be done BEFORE the machine is promoted to a terminal server.”
    Should be “AFTER the server become a Terminal Server”. Or I missing something..

    November 20, 2010 at 7:56 am
  5. NoBody

    CRM Integration with Outlook 2010 still does not work.
    (Windows 2008 R2, Office 2010 x86)
    What’s wrong?

    November 20, 2010 at 5:03 pm
  6. All the components you are trying with were tested and works.
    Is the add-in being registered in outlook? What user account are you trying with? Did you try to double click on the exe manually as described in the blog?

    November 20, 2010 at 5:07 pm
  7. NoBody

    Add-in is registered, but disabled.
    Domain administrator.
    Yes we have double clicked 3CXCRMWizard.exe.
    P.S. Windows Server 2008 R2 x64 Remote Desktop Services enabled.

    November 20, 2010 at 5:16 pm
  8. Can you try and log in as a user now? See if the addin works for that user?
    This is a typical problem of the LOCAL Administrator account. This is what happens under the local admin.
    Check whether the local admin works.
    Did you have a previous installation of the assistant with TS before on this server?
    Send me these answers in email nb@3cx.com and I will check this out.

    November 20, 2010 at 5:24 pm
  9. @Igor – Yes should be after – typo. Any application that is intended for TS Use should be installed AFTER the Machine is promoted to a terminal server.

    @Chris – For V10, this will not be a problem anymore. We are revamping the 3CX Assistant client.. so much that a TS installation will not be required any longer.

    Thank you all for your comments. If you have any problems let us know.

    November 20, 2010 at 11:24 pm
  10. Chris

    @nb -> Best answer yet on the v10 expectation. I really am pleased with the response 3CX developers give to the community voice.

    Keep up the good work!

    December 8, 2010 at 5:45 am