What is EMS "Easy Deployment"?
This additional application layer on the conventional EMS deployment method simplifies the deployment process for administrative users so they can deploy EMS Desktop Client software installations directly to their users' workstations. For an overview, see our webinar. It does this by running all database queries through a Web Service, which allows the database server to be isolated from the end user network. By using this tool, your users do not need to first navigate to the EMS web deploy website and download the application to their local profile.
What Are My Deployment Options?
EMS Deployment is a process you can use to programmatically deploy software to your end user workstations, either via the web or using conventional methods. See the Web Deployment VS Conventional Deployment Decision guide to understand how we can handle that process for you. We recommend implementing a deployment method in order to minimize additional legwork to roll out the EMS Desktop Client to your organization.
How a Deployment Changes Standard Configurations
Configuration after completion of this topic
Prerequisites for Easy Deployment
- EMS Desktop Client installed on end users' machines
- EMS Web Deploy Service installed on a web server so end users are able to access it
- A method to remotely push a registry value into end users' registries
Modify the EMS Web Deploy Service
By default, once you install the Web Deploy Service, users will be able to download and run the desktop client directly from that service. To prevent that, you should delete or rename the install.html file within that service. This will prevent clients from being able to download the client and ensure that you can maintain the desktop installations via your application delivery policy. This will also keep the application running outside the users' network.
Modify the Desktop Client
To connect the Conventional Desktop Client to to the web service instead of directly to the database, you will need to add a String Value named "AppFacadeUrl" to the users' registry:
HKEY_CURRENT_USER\SOFTWARE\Dean Evans and Associates\Version 44
The Value of this String will be the URL to the Web Service (example: "http://yourwebserver.domain.local/em...ktopwebdeploy/"). Once that key is in place, any server and database keys are ignored. To revert back to a direct database connection, simply delete the Registry Key "AppFacadeUrl"
Once the Conventional Desktop client points to the Web service for Connection to the database, it will not auto-update. When it comes time to deploy a new build of the software, you will need to install the updated Web Deploy Version to update the web server side, then push the updated local client from the updated MSI file, and deploy it using your standard installation methods. See Conventional EMS Desktop Client Deployment for further information.