4. On the SiteConfig control point PC, run the installation file. The installation program
copies prerequisite files to
C:\Program Files\Grass Valley\Prerequisite
Files
.
Upgrade K2 systems
Prerequisites for this task are as follows:
•
If upgrading a K2 SAN, all SAN clients must be offline (all media access stopped)
or shut down. Depending on your system design, this could include devices such
as K2 clients, K2 appliances, Aurora Proxy (Advanced) Encoders, MDI server,
Aurora Edit clients, Aurora Ingest clients, Aurora Playout clients, and generic
clients.
Upgrade your K2 systems to the compatible version of K2 system software. This
includes K2 SAN systems and stand-alone K2 Media Client and K2 Summit
Production Client systems. Refer to K2 Release Notes for procedures.
Distribute devices into deployment groups
You can gather devices of different types into a SiteConfig deployment group. This
allows you to deploy software to all the devices in the deployment group at the same
time, as part of the same deployment session. Based on the roles you have assigned
to the devices, SiteConfig deploys the proper software to each device. This increases
the efficiency of your software deployment with SiteConfig.
If you have not already done so, configure your deployment groups. The recommended
deployment group distribution is as follows. Depending on your system design, your
system might not have all the device types listed.
•
In a deployment group named "Aurora_Edit_Ingest_Playout", place the following
devices:
•
Aurora Edit workstation of any storage options: Shared storage, NAS storage,
and stand-alone.
•
Aurora Edit LD computer
•
DSM
•
Conform Server
•
SmartBin Server
•
FTP Server
•
Aurora Ingest Platform
•
IEP
•
Aurora Playout Platform
•
In a deployment group named "Aurora_Browse_MediaFrame", place the following
devices:
•
MediaFrame server
18 October 2010
Aurora Playout Version 7.1.0 Release Notes and Upgrade Instructions
13
Upgrading Aurora Playout systems
