IFS Enterprise Explorer deployment

This guide describes how to install Enterprise Explorer for end users in a Standard Production Environment. This can either be done in a ClickOnce or in a managed fashion.

This page is intended for System Administrators / Technicians, who manage deployment of client software into production environments.

The process of installing the client tier consists of the following parts:

1. Check if there any special network architecture or security consideration that require changes in application settings. More information about those settings can be found here.
2. Enterprise Explorer is a web deployed application. After running the standard installation the installation technician needs to sign the application. This is a security measure to assure that end users can trust the application.
3. End users then type the system url in a web browser and simply clicks on the provided Http link to start the application. Depending on the network security policies Windows may prompt the user to accept to Run the application.
4. That's it. The application now loads and starts automatically from the web. If you have chosen to publish the application as an Installed application a Windows Start menu entry is also created.

Three scenarios is provided in this document:

• ClickOnce Deployment
  ClickOnce is an application deployment technology that makes deploying a rich user interface application as easy as deploying a web application. With “ClickOnce” running the application is as simple as clicking a link on a web page. For administrators, deploying or updating an application is simply a matter of updating files on the deploy server; no need to individually touch every client. This is the recommended deployment model for IFS Enterprise Explorer.
   

  (To read more about ClickOnce functionality see the ClickOnce FAQ.)

• Managed Deployment
  is aimed for companies with a managed deployment of software. If you are system technician who manage Citrix, Windows Terminal Server, software on network file systems, or an automated software installation for workstations, this scenario could be an option for you.
• Hybrid Deployment
  Hybrid Deployment is designed for those who cannot use ClickOnce deployment because they are using some kind of Terminal Server solution, but still want the full functionality, including possibility to have links into the application.