Upgrading Command 360
This section describes the tasks and subprocesses for upgrading an existing Command 360 or CineNet system to Command 360 version 4.4.
Note
Please note that not all steps will apply to every Command 360 instance. If you are unsure which upgrade steps are necessary for your specific environment, contact Haivision for assistance.
Preparation
These steps should be completed before going to the customer site.
Understand the upgrade process, estimated downtime, and features or workflows that do not correspond to Command 360. For a list of appliances and devices that cannot be upgraded to 4.4, see Not Supported in 4.4.
Note
The process will differ if the system has a Manager appliance, or the upgrade is from CineNet to Command 360.
If necessary, make any network firewall modifications. See the Command 360 Port Documentation for more information.
Obtain software license keys and hard drives:
Windows 10 LTSC 2021 license for CineNet to Command 360 upgrades.
If upgrading a Command 360 appliance, the existing Windows 10 LTSC license can be reused. A new Windows 10 LTSC license is necessary for any CineNet to Command 360 upgrade.
Macrium LTSC license. The MAC address from each appliance is needed to obtain a Macrium license. You need one license for each Site/Command 360 Manager, Alpha FX video processor, and CineAgent appliance.
Command 360 Pro/Elite license. Most Command 360 systems already have a compliant license. Best practice in this case is to relicense. Command 360 Standard and Device Control Lite licenses will not function properly.
Appliance hard drives. The ISO process will not function if the device has less than 500 GB. CineMassive and some older Haivision CineAgent 4 appliances require a hard drive upgrade.
Obtain two USB drives with at least 25 GB of storage.
Create BIOS drive (~15 Mb file).
Create Windows/Command 360 ISO drive (~22 GB file).
Important
You cannot use the same drive for both BIOS and ISO processes.
Do not clone USB drives. Create a new ISO with Rufus.
Baseline
The tasks in this section prepare the system to be upgraded. Once completed, the hardware will be in a state comparable to a newly-provisioned system from Haivision.
(Optional) Document existing user workflow and system data. This includes: Accounts/Access Groups, Canvases, Displays, Audio Settings, CineAgent Asset info, Input Asset info, device controls, Rooms, Activities, Layouts, Behaviors, etc.
Note
Most CineNet behaviors do not need to be recreated; Command 360 replicates that functionality in other ways.
A new URL will be created based on the system manager hostname entered during Initialization. Additionally, an initial TLS certificate will be created. See Certificate Management for changing this cert after the system is initialized.
(Optional) Create a Macrium restore for every appliance. See Creating a Macrium Backup.
Note
Site Manager/Command 360 Manager, Alpha FX, and CineAgent 16 can use the existing Backup SSD via Macrium.
For a CineAgent 4 running CineNet, create a backup using the existing drive.
This step can be done on all devices simultaneously.
(If applicable) For systems with a CineAgent VM license, deactivate Thinfinity and document the license for future use. Failing to deactivate the license will essentially forfeit the license and make it unusable when reinstalling Thinfinity. See Deactivating the Thinfinity License.
(If applicable) Complete Manager, Alpha FX, and CineAgent hardware appliance modifications.
Note
This step is required for all CineAgent 4 appliances running CineNet, as well as CineAgent 4 appliances running Command 360 if the drive is less than 500 GB.
Most Site/Command 360 Managers and Alpha FX appliances do not require a hard drive modification.
Any Site Manager with a RAID card will need the card removed in order to complete the next step.
Complete BIOS upgrade process for Site Manager/Command 360 Manager, Alpha FX, and, if necessary, CineAgent 4 Gen2. See BIOS Updates.
Note
No BIOS update is needed for CineAgent 16.
Load ISO from USB to install Windows 10 LTSC, Macrium LTSC Installer, and Haivision Files.
Note
The USB containing the ISO can be removed after the first reboot and moved to other devices.
Press F11 to enter the boot order menu on CineAgent 4.
Important
If upgrading from CineNet, update the capture card firmware with the Haivision IPX driver. See Updating IPX Capture Card Drivers.
Run Macrium LTSC Installer. See Installing Macrium Reflect LTSC.
(If applicable) Update CineLink device firmware with the CineLink Utility provided in Haivision files.
Note
The ideal time to update CineLinks is during the ISO loading process. The update can be done from any Windows device with the CineLink Utility.
Some CineMassive CineLinks may not be recognized without updating the "Branding."
If the CineLink will be used with an AD1, or managed by Command 360, the unit must be factory reset prior.
You must import the provided TLS certificate into the Trusted Root folder of the device running the CineLink Utility for it to function.
If CineLink firmware is updated post-Initialize process, you may see up to a 10 minute delay in C360 recognizing the device(s). Please wait 10 minutes before attempting to add CineLinks.
Check for and apply any Windows updates.
(Optional) Create a Macrium restore for every appliance. See Creating a Macrium Backup.
Note
Although not required, creating Macrium backups can save time in situations where you may need to reattempt installing Command 360. Without Macrium backups, restarting the ISO process is required.
Upgrade
The tasks in this process prepare the system for customer use.
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 appliance 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 user 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.
For (3) and (4) GPU Alphas, disconnect video cables. You do not need to disconnect the KVM console.
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.
(Optional) Update Global Cache devices to latest firmware.
(If applicable) For systems with a CineAgent VM license, reinstall Thinfinity v5. Thinfinity is not included in Haivision Files by default. See Reinstalling Thinfinity.
(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.
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.
(Optional) Update TLS certificate with customer-provided certificate.
Tip
A previous TLS certificate can be used if the hostname is identical to previous implementations.