Active Topics          Search          Help
            Register          Login
eControl ~ Installation, Management and Support (Forum Locked Forum Locked)
 Omni Web Forum : eControl for Microsoft and Novell Systems : eControl ~ Installation, Management and Support
Subject Topic: How to Upgrade eControl 2.5 Post ReplyPost New Topic
Author
Message
Gordon Welling
Admin Group
Admin Group

Manager Technnical Support Services

Joined: 11-December-2003
Location: Canada
Posts: 637
Posted: 06-May-2010 at 9:49am

IMPORTANT NOTICE

Quote:
The information in this article is no longer being updated.  For the most current information ragarding upgrading eControl 2.5 to 3.x, please refer to our knowledgebase article Upgrade eControl 2.5 to eControl 3.5.

Important Upgrade Notice

eControl 2.5 can only be upgraded to eControl 3.0. Once installed, eControl must be upgraded to the latest release 3.1 or higher. Recommended upgrade path from eControl 2.5 to eControl 3.0 is to install eControl 3.0 on a clean Windows 2003 server (do not upgrade the existing Windows 2000 server hosting eControl 2.5).

Procedure to Upgrade eControl 2.5 to eControl 3.x

The following must happen prior to the installation:
  1. Customer contacts Omni to schedule an eControl Upgrade.
  2. Omni Technical Support will conduct a site survey and advise the customer of all preparatory work that must be accomplished, and schedule the upgrade. technical will email the customer a list of the work that needs to be accomplished.
  3. Customer will complete the work identified by Omni Technical Support and advise that they are ready.

For the upgrade installation Omni Technical Support will remote into the customer's environment and working with the customer the Omni representative WILL accomplish the following steps:
  1. Install eControl 3.0 but do not run any of the connection wizards.
  2. On the eControl 3 server, create a \Config folder in C:\Program Files\Omni\Riva.
  3. The Omni Technical Support staff will download the customer's "econtrol.cfg" file from the eControl 2.5 server, covert it to an "econtrol.xml" file and upload and save a copy of it to eControl 3 \Riva\Config folder created in step 2. (NOTE - ensure that a copy of the econtrol.xml and econtrol.cfg files as retained in case the upgrade has to be repeated).
  4. Confirm that the \Riva\Config directory has the same permissions assigned as the \Riva\Configuration directory.
  5. Confirm that all systems that eControl 2.5 connected to are running and can be authenticated to. This is critical as the upgrade will fail to create the econtrol.config file properly during the upgrade if any connection is not working.
  6. Remove the default .config files from the \Riva\Configuration folder.
  7. Restart IIS.
  8. Navigate to eControl Web Site using web browser but do not login. At this point configuration file should be upgraded. Make a backup copy of the \Riva\Configuration folder before proceeding to the next step. Starting Riva may overwrite the econtrol.config file with the default installation version of the file.
  9. Start "eControl Connections" on the eControl 3 server. Go to "Setup" page and confirm that connections exist to systems being managed by eControl 2.5.
  10. In the case of GroupWise connections, create the trusted key and assign it to all Domains and POs in the GroupWise system. Also configure the "Options" settings appropriately on each domain and save them, then assign those settings to the correct corresponding POs.
  11. In case of Active Directory and Exchange connections, remove them and re-add them using Active Directory Connection Wizard.
  12. Perform an IISRESET /STOP. In Windows Task Manager confirm that all instances of the Omni.Connection processes are ended.
  13. Copy the "econtrol.config" file from the backup \Riva\Configuration folder to the \Riva\Configuration folder. This will preserve the configurations, task collections, create profiles, etc from the eControl 2.5 server.
  14. Perform an IISRESET /START.
  15. Confirm that eControl policies exist in the "Policies" page in Riva.
  16. Open a web browser and go to http://localhost. Login as the eControl service account and go into the "Administration" panel. Confirm that task collections, manage forms, task collection assignments, create forms, create profiles and assignments. self service settings and assignments exist as they did in the eControl 2.5 Admin Tool. Click "Apply Settings" to resave the settings to the eControl configuration files. Close the web browser.
  17. Close the Riva application.
  18. Make another backup copy of the \Riva\Configuration folder.
  19. Run the eControl 3.0 setup.exe and remove eControl.
  20. Run the latest eControl 3.x setup.exe to upgrade eControl to the latest release.
  21. Start "eControl Connections". Perform steps to confirm target connections for all eDirectory, GroupWise and Active Directory connections. Perform GroupWise trusted key tests. Perform WMI tests for Active Directory connections.
  22. Run applicable Wizards to add any new systems as required by the customer.
  23. Confirm that eControl policies exist.
  24. Restart IIS. Open a web browser and go to http://localhost. eControl will run in DEMO mode. Login as the eControl service account and confirm that all task collections, manage forms, task collection assignments, create forms, create profiles and assignments. self service settings and assignments exist as they did in the eControl 3.0 Administration Panel.
  25. Start "eControl Connections".
  26. Follow the steps to run the Riva license wizard and request an eControl license.
  27. The Omni Technical Support staff performing the upgrade will upload and activate the eControl license file.
  28. Close and restart the "eControl Connections" application.
  29. Verify that the licenses are activated by right-clicking each eControl policy in the "Policies" page in Riva and examine the "License Details".
  30. In Windows Task Scheduler, end any Omni.Connection processes.
  31. Restart IIS.
  32. Open a web browser and go to http://localhost. Login into eControl 3 and test the environment and make necessary modifications.



Edited by Gordon Welling on 01-September-2010 at 4:09pm
Back to Top
 

Sorry, you can NOT post a reply.
This forum has been locked by a forum administrator.

  Post ReplyPost New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum



This page was generated in 0.0781 seconds.