Skip to main content

System Upgrade

The tasks in this process prepare the system for customer use.

Unless otherwise noted, all steps in this process are required.

  1. Run Command 360 Installer on all Site/Command 360 Manager, Alpha FX, CineAgent 16 and CineAgent 4 appliances. See Command 360 Installer.

    Note

    • You need the device serial number before proceeding.
    • CineLink, CineLink KVM, and AD1 devices do not integrate via the Command 360 Install application. These devices are added via the Command 360 admin interface.
    • For CineAgents that will not have internet access, download and install the Microsoft Edge WebView2 | Microsoft Edge Developer - Evergreen Standalone Installer x86 Version. Without this, the CineAgent will not function properly in the Command 360 environment.
    • The Install process can be done on all devices simultaneously.
  2. For (3) and (4) GPU Alphas, disconnect video cables. You do not need to disconnect the KVM console.
  3. Run Command 360 Initialize from the Site/Command 360 Manager or Alpha FX that is managing the system's Command 360 instance. Standard is the recommended upgrade path. Advanced may require third-party coordination. See Initialization.

    Note

    You need the desired hostname before proceeding. After the system is initialized, the hostname cannot be changed without a factory reset.

  4. (Optional) Update Global Cache devices to latest firmware.
  5. (If applicable) For systems with a CineAgent VM license, reinstall Thinfinity v5. Thinfinity is not included in Haivision Files by default. See Reinstalling Thinfinity.
  6. (Optional) Change to desired or previous URL in Command 360 Utilities.

    Note

    This step can also be performed later, but it will require all Activities to be started for them to refresh their independent URLs.

  7. Configure Command 360 for use. See Admin Interface.

    Note

    If video performance is poor after initial configuration, restart Alpha FX services in the Admin interface.

  8. (Optional) Update TLS certificate with customer-provided certificate.

    Tip

    A previous TLS certificate can be used if the hostname is identical to previous implementations.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.