Install or Upgrade EMS for Outlook on User Computers

To start the installation/upgrade process, uninstall previous versions of the EMS for Outlook add-in. 

EMS for Microsoft Outlook Web Deployment Option

As of the Update 19.1 software release (December 2017), a web deployment option is now available for EMS for Microsoft Outlook. This is the recommended method for installing EMS for Outlook locally on individual user machines. Administrators can use the web deployment to host EMS for Outlook on a web server, with the ability to push the URL to any EMS Administrators so they can download EMS for Outlook without needing Administrative Privileges on their local machine.

For either 32- or 64-bit installation, you will also need an EMS Platform Services Virtual Directory Name (typical default is EMSPlatform). Make a note of the new site you created. This URL will need to be entered during the installation process (e.g., http://[ServerName]/EMSPlatform/ [replace ServerName with the name of your web server]).

Benefits of Web Deployment

The web deploy application is installed on your web server. The EMS for Outlook Add-in 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 for Outlook Add-in. Once a user downloads and runs that link, the EMS for Outlook is installed in the user's profile on that workstation. Once installed, the EMS for Outlook Add-in 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.

Web Deploy Service Installation on Server

  1. Verify that the Requirements and Prerequisites are met.
  2. Download the EMS.Outlook.WebDeploy.msi file onto the user’s desktop.
  3. Close Outlook.
  4. Run EMS.Outlook.WebDeploy.msi.
  5. The first screen welcomes you to the EMS Outlook Web Deploy Setup Wizard.

  6. To begin the installation process, click Next.

    The Destination Folder screen opens.

  7. Specify the Installation Folder.

  8. Click Next.

    The EMS Platform Services screen opens.

  9. Enter the address your organization uses (e.g., http://[ServerName]/EMSPlatform).

  10. Click Next.

    The Ready to install EMS for Outlook Web Deploy screen opens.

  11. To complete the installation, click Install.
  12. Click Close.

Manual Installation (32-BIT or 64-bit)

A 64-bit installation requires an elevated permission level.

  1. Verify that the Requirements and Prerequisites have been met.
  2. Download the EMSForOutlook.msi file onto the user’s desktop.
  3. Close Outlook.
  4. Run EMSForOutlook.msi.
  5. The first screen welcomes you to the EMS Outlook Add-in Setup Wizard.

  6. To begin the installation process, click Next.

    The Destination Folder screen opens.

  7. Specify the Installation Folder.

  8. Click Next.

    The EMS Platform Services screen opens.

  9. Enter the address your organization uses (e.g., http://[ServerName]/EMSPlatform).

  10. Click Next.

    The Ready to install EMS for Outlook screen opens.

  11. To complete the installation, click Install.
  12. Click Close

  13. Start Outlook.

    The EMS button should display on the user’s Outlook toolbar on the Calendar as online.

If the EMS for Outlook displays as Offline, see EMS for Outlook Add-In Is Offline.

Testing EMS for Outlook

EMS Software recommends that customers test new versions of EMS for Outlook before deploying to production. Ideally, customers would have PROD and TEST Exchange environments to pair with the PROD and TEST EMS environments, and separate machines for each environment (e.g., have a machine dedicated to being connected to the test environment).

When creating a reservation in EMS for Outlook, the application stores a unique “PAM ID” on the reservation in EMS and stores the EMS Reservation ID on the Exchange object (meeting/appointment) to establish the link between the two systems.

If the customer has both PROD and TEST linked to the same Exchange environment, here is the risk:

  1. User creates reservation 1234 while connected to TEST EMS.
  2. User switches connection (by changing Platform URL) to PROD EMS.
  3. User cancels reservation 1234 from Outlook, that was originally created in TEST EMS.
  4. Since the connection was changed to PROD, instead of canceling 1234 in TEST, 1234 is canceled in PROD. 1234 in TEST and PROD are almost guaranteed to be two completely different reservations for different users. So the user has now canceled an unrelated reservation in PROD by accident.

Having separate TEST and PROD Exchange environments is the best way to avoid the problem; however, this is often impractical and costly, if not impossible. The alternative option is to be careful and deliberate when following the guidelines below:

  1. Users can use a single machine.
  2. Install TEST EMS for Outlook version, connect with TEST Platform URL.
  3. Make reservations according to test cases and include TEST in the subject line of all meetings created here to help distinguish them.
  4. If they are tracking with UAT test cases they can document the date/time/reservation ID used for each test case to help track these.
  5. Before going back to PROD EMS for Outlook, all TEST reservations must be canceled while still connected to TEST EMS.
  6. Once all TEST reservations are canceled, the normal process of uninstalling the TEST EMS for Outlook and reinstalling with PROD can go forward (ensure the Platform URLs are correct).

 

(missing or bad snippet)