Start installation

Installation packages

The software is supplied as a zip file containing several Microsoft® Installer (.msi) packages.
Please unpack the ZIP file before you run the .msi files!

The various packages are containing a lowercase abbreviation for the language and a lowercase abbreviation for the region of the software in the file name. E.g. "en" stands for the language English and "US" stands for the region United States.
Example: UCServer_en-US.msi is the English server installation package for the region USA.
Below the abbreviation is given neutrally with xx-XX.

File name Description
UCServer_xx-XX.msi Installation package for the estos UCServer.
Administrator rights are required for installation on the server.
ProCall_xx-XX.msi Installation package for the estos ProCall workstation.
Includes a standard TAPI driver.
Multiline TAPI Driver_xx-XX.msi (see directory "Addons") Installation package for the multi-line remote TAPI-driver.
For the use of a multi-line TAPI driver on a Terminal Server.
UCServer Tools for Active (see directory "Addons") Active Directory® schema extension tool. Instructions on using the schema extension are to be found in this zip file.
More information can be found on the page Active Directory® integration.
EWS Calendar Replicator_xx-XX.msi (see directory "Addons") Installation package for the Exchange Calendar replicator service.
For the server sided replication of appointment data. To be used since Exchange 2007 SP1.
SIP Proxy_xx-XX.msi (see directory "Addons") Installation package for the estos UCServer SIP Proxy.
Enables for multi-site scenarios the interconnection of multiple UCServers via SIP federation.
XMPP Proxy_xx-XX.msi (see directory "Addons") Installation package for the estos UCServer XMPP Proxy.
Enables for multi-site scenarios the interconnection of multiple UCServers via XMPP federation.
STUN_TURN_Server_xx-XX.msi (see directory "Addons") Installation package for the estos UCServer STUN/TURN server.
Enables Audio/VideoChat connections using the public internet for media communication. These type of connections are using STUN/TURN servers to pass the Internet router (for NAT traversal). (see directory "Addons") Contains all administrative templates for server operating systems.
-ADM: applicable for all Microsoft® Windows® server operating systems.
-ADX: optimised for Windows® 2008 Server (and later) and Windows® Vista-Workstations (and later).
UCServer_AnalyticsServer_xx-XX.exe (see directory "Analytics") Installation program for the estos UCServer Analytics server
The estos UCServer Analytics server enables reporting of communication statistics.
Help files (PDF) Documentation in PDF format for the modules listed above.
After the installation of the software please use the integrated online help.
readme.txt Installation guide

Performing the installation

  1. By clicking on the UCServer_xx-XX.msi the server installation starts.
  2. The version number is displayed on the welcome page. If an older installation already exists, this number is removed. You can select the application of existing settings later during the estos UCServer setup.
  3. Read and confirm the licensing agreement.
  4. After a short period, you receive the message "The estos UCServer was successfully installed". Click on Complete.
  5. If you haven't removed the tick on Start now estos UCServer server setup, the estos UCServer setup automatically starts at he point where you can carry out the most important basic settings. The estos UCServer setup can also be found on the Windows® start menu where you can check settings or change them. Help with the estos UCServer setup dialogs can be found under Setup.

The server may not be installed directly from the zip file supplied as otherwise the Windows® installer cannot find ProCall_xx-XX.msi which is required for installing or updating the workstations.

Notes for the installation with Microsoft® Installer on a terminal server

The following points should be borne in mind when running a .msi file on a Terminal Server:

  • Administrators and non-administrators can run Windows® Installer Installations from the command line.
  • A terminal server remote session allows only administrators to perform installations.
  • Administrators can only perform Windows® Installer installations from a remote session if the EnableAdminTSRemote system policy is activated. This policy is only available from Windows® Installer version 1.1 upwards and Windows® 2000 and later Windows® versions.
  • The Windows® Installer is started as a system service and therefore cannot access connected network drives. If you execute .msi from a network resource, use UNC paths (\\Server\Verzeichnis\produkt.msi).
  • If you get an Error 2755: Server returned unexpected error 3 attempting to install package message the cause is usually that you have run the setup from a network drive and have not used UNC paths (the installer service cannot find the .msi).

Version 7.8