Decision Guide:
Web Deployment vs Conventional Deployment

What are My Deployment Options?

There are two different deployment options for the Desktop Client:

  1. EMS Desktop Web Deployment

  2. Conventional Deployment

EMS Desktop Web Deployment

Note:

EMS Desktop Web Deployment (V44+ and V44.1) is an alternative method for installing EMS Desktop Client locally on individual user machines. This solution is not a replacement for the EMS Web Client (discontinued after V43), but rather, it is an alternative to using Microsoft® methods of deployment, such as SCCM. Administrators can use it to host EMS Desktop Client on a web server, with the ability to push the URL to any EMS Administrators so they can download EMS Desktop Client without needing Administrative Privileges on their local machine.

The web deploy application is installed on your web server. The EMS Desktop Application is included within this installation. Once installed, end users point their web browsers to the EMS Web Deployment Application, which points them with a link to download the EMS Desktop Client. (See also: Types of EMS Users). Once a user downloads and runs that link, the EMS Desktop Client is installed in the user's profile on that workstation. Once installed, the EMS Desktop Client will check the server for an updated version of the client each time the client is launched. If a new version is available, then it will automatically download and install the update.

​Conventional Deployment

Conventional Deployment works like previous releases of EMS. The downloadable installer is in the form of a MSI file. Once the software is installed on the Admin Users workstation, it connects directly to the database. optionally it can be configured to connect to the Desktop Client API included in the Web Deployment option.

Note:

The Web Deployment method also adds an application layer (in the form of a web service), to the architecture of the application. Instead of the Desktop Client connecting directly to the Database server as it has in the past. All connections are routed through the Desktop Client API (Included with Web Deploy). this can add additional benefit for Security Considerations, or multi-region deployments.

Features of Each Deployment Method

The table below outlines the features available between the two deployment methods.

Feature Desktop Web Deployment Conventional Deployment
Admin Rights required on the workstation No Yes
Number of installations per workstation 1 Per User Once for all users of the workstation
Installation location Users Profile Location can be specified during installation
Requires a web server Yes No
Can adopt customer specific, deployment procedures No Yes (Requires IT Assistance)
Able to deploy without user intervention No Yes (Requires IT Assistance)
Updates are handled... From the Web Service on the server Must be re-pushed to individual workstations.
IT has control of when updates are pushed Yes Yes
Network Connection to the database Desktop Client API Direct TCP connection or Desktop Client API
Note:

To enable SSL, you first make changes to the EMS Desktop Client .msi file. See Also: Enabling SSL.