GV STRATUS Control Panel configuration for K2 Central

Before configuring GV STRATUS Control Panel:

The entire system must be restarted in the following order so that the registry settings take effect:
- K2 systems
- All other servers
GV STRATUS servers and K2 Summit systems must be licensed.
K2 Summit system channels must be configured.

Configure Control Panel as you would a normal GV STRATUS system, except for the following steps.
In some fields you must manually enter text rather than selecting from a list.
Select Core | K2 Storage and verify that the K2 Central system displays in the K2 SAN Storage tab.
Select Core | Proxy Config | Proxy Settings and do the following:
1. Set the Location of Proxy Assets, CIFS Server, and HTTP Server.
2. Enable proxy Creation to set the proxy registry keys on the Summit clients.
3. Enable Proxy Encoders for auto-scavenging.
4. Save and Test Connections.
Select Core | MDI and configure a Summit MDI for SAN pointing to the K2 Central system.
The SAN name is arbitrary. Choose the name that you want to appear in the Navigator of GV STRATUS. Be sure to set the credentials to use the GVAdmin account on the fully qualified domain, such as GVDOMAIN.

Ensure the number of FTP streams is set to 10.
Shut down the entire system.
Power up in the following order:
- FSM/K2 Manager (Log in before powering up K2 Summit clients.)
- K2 Summit systems (Verify AppCenter is functioning on each client before powering up other servers.)
- All other servers.
Finish configuration of other devices (such as EDIUS, XRE/Render Engine, NCS/GV STRATUS Rundown, Archive servers etc.) as needed.
Some reboots may be required.