ICE

Please login or register.

Login with username, password and session length
Advanced search  

News:

ICETCP.PRO and ICETCP.PLUS are compatible with Windows 11!

Author Topic: ICE TCP-PRO SCO Compatibility  (Read 827 times)

derickson

  • Newbie
  • *
  • Posts: 1
  • Place Personal Text Here
ICE TCP-PRO SCO Compatibility
« on: May 10, 2004, 06:09:47 pm »

I need to move my server from a windows 95 PC to a Windows 2000 Profesional PC.  The curent version of TCP-PRO that we are running is 5.0 our Unix Box is SCO 4.2.
Since we need to upgrade to 5.1.21 for it to work properly on Windows 2000, will this new version work with SCO Unix 4.2?

What is the best upgrade path to migrate our Server and Clients to the new release. (our clients are already W2K with no know issues)
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
ICE TCP-PRO SCO Compatibility
« Reply #1 on: May 11, 2004, 12:11:35 pm »

The emulation is unchanged in the current versions so they will work fine with your SCO server.

The proper way to update your clients is to install the update onto the machine hosting the PRO license server and do a full install.

First, backup your License folder (under TCP5_USER) and copy down your current licenses and company name by running licenseadmin on the PRO license server machine.

Download and install the update on the PRO license server. If you use that machine for a client, do the client install as well.

Run licenseadmin and check to make sure your licenses and users are still there. If they are then skip to the next paragraph. If not, reenter the licenses and company name if they don't show up in licenseadmin and copy the backuped License folder over the top of the one in TCP5_USER. Rerun licenseadmin, you should be able to see the licenses and users.

Now you are all set to install the new version of PRO on your new machine by simply doing the usual network install. (Browse to the TCP5_USER share on the machine serving as the PRO license server and run the setup.exe program).

Ideally, at some point you should update the other client machines. A network install just like on a new machine should update the existing client and leave the settings intact (you should only need to get a sequence number, not a profile).
Logged
 

Page created in 0.013 seconds with 21 queries.