Upgrading Different OmniServers No matter if you are upgrading from Version 1, Version 2.0, or simply from the OmniWedge or OmniServer Server Edition products, upgrading is easy and straightforward. For more information, just follow any of the links below for the version you wish to upgrade. Upgrading from V1.x to V2.7 Please note: Version 2.7 uses a new licensing scheme completely different from the older scheme. You must have your new license number available before beginning this procedure. Please contact us for information on how you can obtain your new license number. As Version 2.7 is, in fact, a complete and separate installation from Version 1.x, this is technically not an upgrade. However, if you follow the steps below, you can move your V1.x configuration files and protocols so that the migration from V1.x to V2.7 is seamless. Please note: ProgIDs and client application names for Version 2.7 have changed. Please see the documentation below for details on what you will need to change in your client application. To upgrade from Version 1.x to Version 2.7: IMPORTANT: Please make a backup of your V1.x installation directory. Although nothing in this procedure will destroy the V1.x installation, it's always best to have backups. Install your copy of V2.7. Do not launch the configuration program when prompted. Once the installation is complete, make sure that OmniServer is completely shut down. First, insure that the OmniServer Configuration program is not opened (it is opened by default from the Installation program). Next, check your Icon Tray. If you see and icon of a computer with a world behind, that is the OmniServer engine. Right-click on the icon and select "Exit". Go to your V1.x directory. Inside the V1.x directory you will find a file with the extension .CFG. Copy this file to your V2.7 installation directory. (C:\Documents and Settings\All Users\Application Data\Software Toolbox\OmniServer) Also in that directory you may find all your protocols. Each protocol will have the extension .DPD. Move those files over to the V2.7 installation directory. If you are running V1.x as a service, shut down that service. To start V2.7 as a service, please see our Using Services section. Start up V2.7. You will see your configuration and your protocols. Change your ProgIDs and client application names  in your client application as follows: OPC: Change DSSI.OmniOPCServer.1 to SWToolbox.OmniServer DDE: Change OMNISRV to OSRVDDE. Suitelink: Change OMNISRV to OSRVPOLL. Now just register Version 2.7 using the new license number you received with your V2.7 purchase. And that's all there is to it! Your next step will be to test the V2.7 installation with your configuration and protocols just to make sure that everything works.