Summary of upgrade from version 3.5 to version 4.5

Several upgrade tasks are new or require special consideration with this upgrade. Apply upgrade tasks as appropriate for your system design, as follows:

All systems:
- GV STRATUS software installation automatically creates and installs a security certificate on the GV STRATUS Core server. No manual steps are required.
- Schedule Monitor, Security Manager: After the upgrade, existing users and groups do not have these roles assigned, so you must assign the roles if appropriate. If you create new users and groups, some roles are assigned by default, so you must remove those roles if appropriate.
- Require the upgrade of SNFS (StoreNext File System) version 4.7.2 if you are upgrading to K2 9.5 system. For more details, refer to the "Upgrading K2 systems" section of the K2 Topic Library.
Systems with Proxy Encoders:
- Proxy generation functionality is included in the GV STRATUS Render Engine. Proxy Encoders must be converted to Render Engines. The required steps for the conversion of Proxy Encoder servers to Render Engine servers are integrated in the main upgrade process and in the section Install Render Engine server software and upgrade EDIUS client software.
- Require the removal of GV STRATUS Proxy Encoder role in order to use the proxy encoder functionality in GV STRATUS Render Engine. You must remove the GV STRATUS Proxy Encoder role on every existing Proxy Encoder in your operation.
Note: In case one Proxy Encoder role is still configured in a GV STRATUS system, the GV Render Engine will not perform any proxy encoding jobs. Instead all proxy encoding jobs will be executed by the existing Proxy Encoder.
Systems with GV Render Engine server:
- Require the removal of K2 FTP Server role. You must remove the K2 FTP Server role on every GV STRATUS Render Engine in your operation.
Systems with Remote Site configured:
- Verify and configure Remote Site settings. GV STRATUS security requires re-entering existing information and configuring new settings.
Systems with MEWS Server:
- Set up the MEWS Server in SiteConfig and deploy the MEWS Service software.
Systems with GV STRATUS Rundown:
- To enable automatic transfer of assets into a playout server, configure the Summit MDI in GV STRATUS Control Panel for the K2 system that is a playout server.
Systems with DIVA archive:
- Require the configuration of all K2 Summit SAN FTP server as an individual entry in the Configuration Utility on the DIVA server. For more details, refer to Configuring DIVA.
- Require the same number of maximum concurrent archive and restore operations entered in the Configuration Utility on the DIVA server for all FTP servers belonging to the same K2 Summit SAN.
- Require the configuration of the correct number for supported archive and restore operations in the Diva MDI in GV STRATUS Control Panel to match the configuration on the DIVA server. For more details, refer to DIVA Archive MDI settings.
Systems with SGL Flashnet archive:
- Require the configuration of all K2 Summit SAN FTP server as an individual entry in the Configuration Utility on the SGL FlashNet server. For more details, refer to Configuring FlashNet.
Systems with routers using SMS7000 protocol:
- Verify that router source and destination IDs do not include invalid characters. For more details, refer to Characters not allowed in router source and destination IDs.
Systems with Ingest database:
- Disable the Auto Close feature on Ingest database to prevent inaccessibility problems. For more details, refer to Disabling the Auto Close feature in Ingest Database.