Verify that devices are configured properly

After all software, hardware and OS upgrades are complete, do the following to verify systems and tools are ready for configuration:

Reboot your GV STRATUS system in the correct order.
On the Core server, open SQL and go to Databases | ISDB | Properties | Options. Verify that AutoClose is set to False.
Grass Valley recommends the GV STRATUS Control Panel is only configured on the Core server. In the GV STRATUS Control Panel, do the following:
- Re-save the Proxy settings if the K2 Summit 10 upgrade procedure was followed.
- In each Summit MDI, do the following:
  - Verify the UNC path to the V: drive exists. (This is required for GV Render Engines to work.)
  - Verify all K2 SANs, K2 Centrals, and Third Party Storage systems have a primary and secondary devices entered (usually set as the first and second K2 Summit clients).
  - Re-save the Summit MDI. (This is required for GV I/Os to work, if any have been added.)
- In Engines settings, do the following:
  - Verify that all engines are running.
  - Select and reconfigure the Xcode Control Engine, if you have the Telestream Vantage transcoder in your operation.
  - Select and configure the new External Media engine, if you have the Verizon-CMS system in your operation.
- If your system has a K2 SAN, click Core | K2 Storage | K2 SAN Storage and verify that the information for the K2 SAN is the same information that is in K2Config. If the information is the same, it means that the Control Panel application is correctly reading the information from the K2Config application.
- If your system has a GV I/O Ingest Appliance, configure the GV I/O channel formats in General | Channels | I/O Appliances to the desired formats configured in the General | Format | Formats settings, if you added one or more GV I/O Ingest Appliances to your K2 SAN or SMB storage system.
From each machine in the GV STRATUS system, verify that you can ping all the devices that the GV STRATUS server needs to communicate with over the control network.
For the machines that need to communicate with a Proxy server, verify you can log in to that Proxy server using the credentials that the system will be using.
Verify that GV Render Engines are configured correctly. Mapped V: drives for non-iSCSI connection to K2 Summits are no longer needed. You may need to delete the Servers in the XREAdminConsole | Plug-in | Importer/Exporter | K2 (SAN) | Server window and re-select the “Configure automatically” check-box, then verify these Server settings:
- FSMs will get the server names.
- K2Centrals, SMB Storage SANs, and K2 Summit Standalone(s) will get the SummitMDI names.
The GV STRATUS database is automatically indexed to support enhanced search features. During this time, Search features and Rules are not fully functional. In GV STRATUS Control Panel, click Core | Search Index Config to view indexing progress.
Begin by configuring STRATUS Core Services settings and move on to other settings.

After automatic re-index completes, reboot system in the correct order and verify that the GV STRATUS-EDIUS system is working.

Note: If prompted for a Java update, upgrade to the latest version of Java software to ensure you have the latest security updates.