IC3 Upgrading Information
English 日本語 (Japanese)

Introduction

This document discusses issues and information pertaining to upgrading existing IC3 networks to newer releases.

Order of Upgrade

When upgrading IC3 InfoChannel networks, we recommend the following order of upgrading components.
(Following a different order may not be supported and may lead to unexpected results.)

  1. First, upgrade Network Manager / Network Manager Enterprise.
  2. Next, upgrade each ICPlayer.
  3. Finally, upgrade each ICDesigner or Reporter.

In general by following this order, complete and correct functionality is maintained throughout the transition period. Any exceptions are noted here:

(New functionality in a release may require all components to be upgraded in order to take effect.)

ICPlayer Remote Software Update for Release 4 Networks and Newer

If your network (NetManager and Players) are already at Release 4 or newer, you can use the NetManager Install Software Update job maintenance task to send a player update over the network, without requiring operator intervention on each player.

ICPlayer Remote Software Update for SP2 Networks and Older

If your Players are at Service Pack 2 or older, they will not recognize NetManager's Install Software Update job maintenance task. However, the underlying technology still can be used to bring an older player up to date if you construct a single job containing these tasks:

  1. Install File maintenance task to send the icUpdate.exe utility to a specific location on the player.
  2. Install File maintenance task to send the icplayer_update.cab to a specific location.
  3. Run Command maintenance task to invoke
    path\icUpdate -I -L PathToLogFile -C path\icplayer_update.cab
    If the ICPlayer Network Engine is not running as local administrator, you must also specify user name, password, and optionally the domain, using these arguments:
     -A AccountName -P Password -D Domain
  4. A Retrieve Files maintenance task if you need to retrieve the icUpdate log file.
  5. A Reboot maintenance task, because the files are actually updated upon rebooting (to handle files in use).


Scala exclamation mark logo