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.
Existing K2 Central server(s) and clients must be removed as SAN servers/clients and re-added as K2 Central server(s)/clients. Then the core server must be re-synced (by saving SiteConfig configuration) for GV STRATUS Control Panel to see these servers as K2 Central devices to be configured.
Any K2 config files must be deleted, and services restarted on the GV STRATUS core server, if originally K2 Central devices had been manually added to these files before configuring K2 Central systems in the GV STRATUS Control Panel.
If upgrading the K2 central system, the previously installed software must be uninstalled manually.

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 | K2 Central | Add.
The Add new K2 Central system dialog box appears.
Enter the name of the K2 Central system, select the K2 Central server and K2 clients for the system, and click Save.
To add multiple K2 Central systems, you can use the Add button repeatedly on the K2 Central tab.
Select Core | MDI and configure a Summit MDI for the K2 Central system.
Select K2 Central for the Type of K2 device.
The SAN name is arbitrary. Choose the name that you want to appear in the Navigator of GV STRATUS. Enter the UNC path to the K2 Central system.

Be sure to set the credentials to use the GVAdmin account on the fully qualified domain, such as GVDOMAIN. Then, click Save.
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.
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.