GRASS VALLEY AURORA BROWSE - S AND UPGRADE INSTRUCTIONS... Quick start guide

Copyright © Grass Valley, Inc. All rights reserved. Printed in the United States of America. Portions of software © 2000 – 2010, Microsoft Corporation.All rights reserved. This
document may not be copied in whole or in part, or otherwise reproduced except as specifically permitted under U.S. copyright law, without the prior written consent of Grass
Valley, Inc., P.O. Box 59900, Nevada City, California 95959-7900. This product may be covered by one or more U.S. and foreign patents.Product options and specifications
subject to change without notice. The information in this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a
commitment by Grass Valley, Inc. Grass Valley, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in this publication.Grass Valley, K2,
Aurora, Summit, Dyno, Solo, Infinity, Turbo, Profile, Profile XP, NetCentral, NewsBrowse, NewsEdit, NewsQ, NewsShare, NewsQ Pro, and Media Manager are either
registered trademarks or trademarks of Grass Valley, Inc. in the United States and/or other countries. Grass Valley, Inc. products are covered by U.S. and foreign patents,
issued and pending. Additional information regarding Grass Valley, Inc. trademarks and other proprietary rights may be found at www.grassvalley.com. Othertrademarks and
logos used in this document are either registered trademarks or trademarks of the manufacturers or vendors of the associated products, such as Microsoft® Windows®
operating system, Windows Media® player, Internet Explorer® internet browser, and SQL Server™. QuickTime and the QuickTime logo are trademarks or registered
trademarks of Apple Computer, Inc., used under license therefrom.
Aurora Browse Release Notes
Version 7.1
Release Notes & Upgrade Instructions
These release notes contain the most recent information and supersede previous
publications, as of October 18, 2010. Check the Grass Valley website at
www.grassvalley.com/docs for an updated version that contains additional important
information.
These release notes contain information for the following:
• Aurora Browse client
•MediaFrame server
•MDIserver
• K2 BaseCamp Express
• Aurora Proxy Encoder
•SmartBinsEncoder
071-8639-10

Contents
Grass Valley Product Support.....................................................................................................4
Release Summary......................................................................................................................6
What's new in version 7.1.0.....................................................................................................6
Version 7.1.0........................................................................................................................6
Changes and features in previous releases............................................................................6
Version 6.5.1.17...................................................................................................................7
Version 6.5.1........................................................................................................................8
Older versions......................................................................................................................8
Version compatibility...................................................................................................................9
System requirements..............................................................................................................9
Compatible MediaFrame server and K2 BaseCamp Express components...........................10
Aurora Browse components..................................................................................................10
Compatible Grass Valley products.........................................................................................11
Compatible third party products............................................................................................11
Upgrading Aurora Browse and MediaFrame systems...............................................................13
Upgrading Aurora Browse and MediaFrame devices with SiteConfig...................................13
About upgrading Aurora Browse and MediaFrame devices with SiteConfig......................13
Prepare for upgrade...........................................................................................................14
Prepare SiteConfig for software deployment.....................................................................14
Install prerequisite files on the control point PC.................................................................15
Upgrade K2 systems.........................................................................................................15
Distribute devices into deployment groups........................................................................15
Upgrade Aurora Edit, Ingest, and Playout systems...........................................................16
Upgrade NAS systems......................................................................................................16
Install High Priority Windows updates (recommended).....................................................17
Check all currently installed software.................................................................................17
Add software package to deployment group for Aurora Browse devices...........................18
Setting deployment options................................................................................................20
Upgrade software on Aurora Browse devices....................................................................22
Install Browse client PC application......................................................................................25
Logging in to the Aurora Browse client PC............................................................................25
Licensing Grass Valley products...............................................................................................27
About software licensing.......................................................................................................27
Requesting a license.............................................................................................................27
Adding a license....................................................................................................................29
Deleting licenses...................................................................................................................29
New topics................................................................................................................................30
Aurora and Windows 7..........................................................................................................30
Additional notes........................................................................................................................31
About the MediaFrame/BaseCamp SDK...............................................................................31
About the zoom knob............................................................................................................31
About using MediaFrame with non-English languages.........................................................32
Modifying the MediaFrame database for non-English searches........................................33
Asset and bin name limitations..........................................................................................34
Configuring the encoder for unicode languages................................................................35
Operation considerations..........................................................................................................36
2Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 18October 2010

Operating Considerations: Aurora Browse Client..................................................................36
Operating Considerations: MediaFrame Server and MDIs....................................................36
Operating considerations: K2 BaseCamp Express...............................................................37
Operating Considerations: Aurora and K2 systems...............................................................37
Operating Considerations: 3rd party archive considerations.................................................37
Known Issues............................................................................................................................39
18October 2010 Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 3

GrassValley Product Support
To get technical assistance, check on the status of a question, or to report a new issue,
contact Grass Valley Product Support via e-mail, the Web, or by phone or fax.
WebTechnical Support
To access support information on the Web, visit the product support Web page on the
Grass Valley Web site.You can download software or find solutions to problems.
World Wide Web: http://www.grassvalley.com/support/
Technical Support E-mail Address: [e-mail]
Telephone Support
Use the following information to contact Product Support by phone.
International Support Centers
Our international support centers are available 24 hours a day, 7 days a week.
In countryToll freeSupport Center
[phone]+800 80 80 20 20France
[phone]+1 800 547 8949United States
Authorized Local Support Representative
A local support representative may be available in your country. To locate a support
center during normal local business hours, refer to the following list. This list is
regularly updated on the website for Grass Valley Product Support
(http://www.grassvalley.com/support/contact/phone/)
After–hours local phone support is also available for warranty and contract customers.
TelephoneCountryRegion
[phone]ChinaAsia
[phone]Hong Kong, Taiwan, Korea,
Macau
[phone]Japan
[phone]Southeast Asia - Malaysia
4Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 18October 2010
Grass Valley Product Support

TelephoneCountryRegion
[phone]Southeast Asia - Singapore
[phone]India
1 300 721 495AustraliaPacific
0800 846 676New Zealand
[phone]For callers outsideAustralia
or New Zealand
[phone]AllCentral America,
South America
[phone];
[phone]
North America, Mexico,
Caribbean
North America
[phone]UK, Ireland, IsraelEurope
[phone]Benelux –Netherlands
[phone]Benelux –Belgium
[phone];
[phone]
France
[phone]Germany, Austria,
Eastern Europe
[phone]Belarus, Russia,
Tadzhikistan, Ukraine,
Uzbekistan
[phone]Northern Europe
[phone]Southern Europe –Italy
[phone]Southern Europe –Spain
[phone]Middle EastMiddle East, Near East,
Africa [phone];
[phone]
Near East and Africa
18October 2010 Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 5
Grass Valley Product Support

Release Summary
What's new in version 7.1.0
This version of software includes several improvements, in addition to correcting
some problems that were present in earlier releases.
Version 7.1.0
•Windows 7 support —The Aurora Browse client supports the Windows 7
operating system for 32-bit and 64-bit versions.
•Installing or updating SNFS and Generic iSCSI —SNFS and Generic iSCSI
cab files no longer bundled together. Check the Version Compatibility section to
determine the version compatible with your system.
Changes and features in previous releases
The following sections describe changes and features in past releases.
Version 7.0.0
•New look —The look and feel of the Aurora Browse client has been changed to
match the rest of the Grass Valley product lines.
•New terminology —The MediaFrame server will now be referred to as K2
BaseCamp. (The scaled-down version of theAurora Browse/MediaFrame system
is still referred to as K2 BaseCamp Express.)
•AVC-Intra —Proxy encoders support both AVC-Intra 50 and AVC-Intra 100.
For a list of supported partial file restore (PFR) formats, refer to Operating
Considerations: 3rd party archive considerations on page 37 .
•K2Summit MDI —A new K2 Summit MDI allows for detection of multiple-tiered
bin structure.
•Extended naming capabilities —Longer names are now allowed for bins and
assets. For more information, refer to Asset and bin name limitations on page 34.
•Dockable Transfer Manager —The Transfer Manager, which can be launched
via the Window menu, can be docked as a preferred view within Aurora Browse.
This works just like the other dockable windows, such as the search window and
asset results list. In addition, the Transfer Manager can be configured into a saved
view for quick recall.
•SimplifiedTransferManagerinterface—MultipletabsoftheTransferManager
interface have been merged into a single view.
6Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 18October 2010
Release Summary

•Extended transfer history —Transfer Manager history now can extend up to one
year.
•Concurrent transfers —For News, K2, K2 Summit, and Generic FTP MDIs, you
can now specify a maximum number of concurrent transfers. The maximum number
of transfers depends on the configuration of your system. For more information,
see your Grass Valley representative.
•Increased transfer capabilities for nearlines and other archives —You can
now manage transfers between multiple nearline systems, or between a nearline
system and a Flashnet or Diva archive, from a single PC.
•Enhanced keyword notepad —Double-clicking keywords now launches an
enhanced keyword “notepad”, which allows for a much more flexible dialog for
editing keywords within Browse, Edit, etc. When the keyword is double-clicked,
a pop-up dialog appears that shows the keyword thumbnail along with naming
information, which can be extended to much more than a typical name character
size.
•Extended NetCentral audit trail —MediaFrame support of NetCentral has been
extended to incorporate an audit capability; NetCentral can now track the lifetime
of an asset.
•Updated SDK —The SDK is fully supported. Refer to About the
MediaFrame/BaseCamp SDK on page 31 .
•New zoom capability —You now have the ability to zoom in on long files, similar
to Aurora Edit. Refer to About the zoom knob on page 31.
Version 6.5.2
•SiteConfig support —Network configuration and software deployment across
allAurora products is supported by SiteConfig, GrassValley's system management
tool.
•Administrator password –The default administrator account onAurora devices
has credentials as follows:
•Username: administrator
•Password: adminGV!
SiteConfig expects these credentials by default.
•Databaseconfigurationchange —The database needs to be configured in simple
mode.You no longer need to run transaction log backups. If the database has
previously been set to the full recovery model, you must update it to the simple
model before upgrading to version 6.5.2. For more information, see the Aurora
Browse Installation & Configuration Guide.
Version 6.5.1.17
•K2Summit compatible –TheAurora suite of software, includingAurora Browse,
is compatible with the K2 Summit software.
18October 2010 Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 7
Release Summary

Version 6.5.1
•The MediaFrame Config tool —the MediaFrame server can now be configured
with an application that facilitates the various MediaFrame setup.
•Aurora Browse client installed locally on client PCs —The Aurora Browse
application is no longer a web-based application. In previous versions, it was
installed on the MediaFrame server and served to individual client PCs via HTTP.
In Aurora Browse 6.5.1, it is a Windows executable, like the Aurora Edit LD
application, and is installed locally on each client PC.
•Support for archives —Aurora Browse is now compatible with version 6 of the
SGL FlashNet archive product and version 6 of the DIVA archive product, as well
as the Avalon archive, version 3.2
•Roundrobinarchivingof assets —Aurora Browse supports a round robin method
for distributing transfers requests from a K2, News, M-Series or Profile MDI server
to multiple transfer servers.
•Condor NAS —Aurora Browse is now compatible with the Condor NAS used
with K2 Storage Systems.
•Collections —a virtual folder workspace allows you to create public or private
folders so that you and others can contribute references to the assets. Some of the
uses for Collections include selecting clips for projects, selecting clips to be archived
or restored, and requests for the media manager, all without actually moving or
duplicating assets.
•TransferTool now integrated —In the Aurora Browse Client, you can drag and
drop files and monitor transfer progress between devices.
•Pinnable Windows —the MediaFrame panels are now pinnable and relocatable
so you can customize and resize MediaFrame tools within the application
•Extended Custom Metadata types —Custom Metadata now supports fields that
are variable- and unlimited-sized text fields, date, pick list, and numbers
•Enhanced Search —use filters for flexible and efficient searches.You can now
search device metadata and save commonly used searches for private or global
use.
•Expanded results window, with dynamically positioned columns —you can
customize a view using the column picker to show technical, general, or custom
metadata when viewing search results.
•DynamicKeywordandKeyframemarking—FeedClipfeaturesarenowincluded
as standard functions. This includesAutoMark for single button capture of events
with preset duration. These automatic calculation features enable easy capture of
sports highlights, sound bites, or shots of interest for development of stories from
live footage or material in shared storage.
Older versions
For information about older software versions not listed in these release notes, refer
to the release notes for those versions.
8Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 18October 2010
Release Summary

Version compatibility
Versions qualified for compatibility with this release of software are summarized in
the following sections.
System requirements
This section describes the recommended hardware requirements for this release.
Recommended specMediaFrame Server component
Dell PowerEdge R610Model
Two Intel Xeon E5520, 2.26 GHzProcessor(s)
4 GBMemory
146 GB 15K RPM SASSystem Drive
Gigabit EthernetNetwork
Windows Server 2003 R2 32 SP2OS
Recommended specK2 BaseCamp Express component
Dell PowerEdge R710Model
Two Intel Xeon E5520, 2.26 GHzProcessor(s)
4 GBMemory
Four 250 GB 7.2K SATASystem Drive
Gigabit EthernetNetwork
Windows Server 2003 R2 32 SP2OS
Recommended specMDI Server component
Dell PowerEdge R610Model
Intel Xeon E5520, 2.26 GHzProcessor(s)
4 GBMemory
146 GB 15K RPM SASSystem Drive
Gigabit EthernetNetwork
Windows Server 2003 R2 32 SP2OS
Recommended specAurora Proxy Encoder component
Dell PowerEdge R610Model
Two Intel Xeon E5520, 2.26 GHzProcessor(s)
18October 2010 Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 9

4 GBMemory
146 GB 15K RPM SASSystem Drive
Gigabit EthernetNetwork
Windows Server 2003 R2 32 SP2OS
Compatible MediaFrame server and K2 BaseCamp Express
components
The following components are prerequisites that reside on the MediaFrame server and
K2 BaseCamp Express. Compatible versions are pre-installed on new servers shipped
from the factory.
CommentsVersionProduct
2005 SP3SQL
Under Web Service Extensions,
make sure ASP.NET is allowed.
Version 6Internet Information Services
(IIS)
3.0Web Services Enhancements
Aurora Browse components
The following components make up the Aurora Browse system and are compatible
with this release of software as listed in the following table.
CommentsVersionComponent
Bundled in the
MediaFrameServerinstall
7.1.0.8Aurora Browse client
Supported on Windows
XP SP3 and Windows 7
7.1.0.18MediaFrame server
Formerly referred to as
Advanced Encoder
7.1.0.15Aurora Proxy Encoder
Not supportedNAS on SerialATA network
platform
Not supportedNAS on Linux Fastora
platform
10 Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 18October 2010
Version compatibility

Compatible GrassValley products
Grass Valley products are compatible with this release of software as follows:
CommentsVersionProduct
With compatible version of
SQL
7.1.0.273Aurora Edit
With compatible version of
SQL
7.1.0.68Aurora Ingest
With compatible version of
SQL
7.1.0.39Aurora Playout
7.1.0.273Aurora Suite installer
GVG_MLib installer and
Generic iSCSI installer with
compatible version of SNFS.
3.3.2.1401 or 7.2.7.1397K2
7.1.0.273K2-Aurora FTP
—1.4.0.451 or higherSiteConfig application
—1.1.188SiteConfig DiscoveryAgent
Compatible with K2 version
3.3.2.1401 and K2 Summit
version 7.2.7.1397
3.5.2.1b15620StorNext File System
(SNFS)
The prerequisite files must
be installed on the
SiteConfig control point PC.
1.0.0Grass Valley prerequisite
files
7.1.0.11Aurora Browse Switcher
7.1.0.7Aurora Browse database
upgrade utility
Compatible third party products
Products by manufacturers other than Grass Valley are compatible with this release
of software as follows:
CommentsVersionProduct
To create a recovery image
for a MediaFrame server or
8162
Acronis Imaging
Proxy Encoder, use a
recovery CD, part number
063-8246-04.
18October 2010 Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 11
Version compatibility

CommentsVersionProduct
Prerequisite for all Aurora
machines.
NOTE: Install after IIS.
3.5 SP1 / 2.0 SP2
Microsoft .Net Framework
6.3.1.4.1 (Server side)
Front Porch Digital
DivArchive software 6.1.22 (Client side)
After installing FlashNet
MDI you need to make sure
6.2.09 (Server side)
6.1.44 (Client side)
SGL FlashNet software
that the fnapi.dll in the
C:\Program Files\ Grass
Valley\ ManagedDevices\
FlashNET directory is the
same version as the FlashNet
Client software that is in
C:\flashnet6\bin. If not copy
the file in C:\flashnet6\bin to
C:\Program Files\ Grass
Valley\ ManagedDevices\
FlashNET.
Avalon software is now
"End of Service." The last
supported version was 3.2.
See comments.Avalon software
12 Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 18October 2010
Version compatibility

Upgrading Aurora Browse and
MediaFrame systems
This section contains the tasks necessary for the upgrade to this release of software.
Upgrading Aurora Browse and MediaFrame devices with SiteConfig
This section contains the tasks for using SiteConfig to upgrade to this release of
software. Work through the tasks sequentially to complete the upgrade.
NOTE: These upgrade instructions assume that current software is at version 6.5
or higher. If you have a lower version of software, contact GrassValley Support
before upgrading.
CAUTION: If you upgrade and then decide you do not want to stay with this
version of software, you must use the recovery disk image process to downgrade
to your previous version.
About upgrading Aurora Browse and MediaFrame devices with SiteConfig
With the upgrade instructions in this document, you use SiteConfig from a network
connected control point PC and remotely upgrade software simultaneously on your
Aurora product devices. This is the recommended process for software upgrades.
NOTE: Do not use the upgrade instructions in this document if upgrading with
SiteConfig for the first time.
If SiteConfig was not used for your previous software upgrade, do not use the upgrade
instructions in these release notes. Instead, use the SiteConfig Migration Instructions.
Before you upgrade software using SiteConfig, each of your Aurora product devices
must be migrated to become a SiteConfig managed device. This includes installing
SiteConfig support on the device, manually uninstalling any and allAurora components,
and qualifying the device for communication with SiteConfig. These instructions are
in the SiteConfig Migration Instructions.Also refer to the SiteConfig User Manual or
SiteConfig Help Topics.
The upgrade instructions in this document apply to the following devices:
•MediaFrame server
•MDI server
•Aurora Proxy Encoder
•K2 Basecamp Express
To upgrade software using SiteConfig, you must first have SiteConfig set up for system
management and software deployment in your facility. These upgrade instructions
assume that you have already done that for your K2 SAN. Then you add your Aurora
18October 2010 Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 13

product devices to the SiteConfig system description that you are using for your K2
SAN.
NOTE: Do not attempt to upgrade software incrementally across the devices of a
K2SAN while media accessis underway.Onlinesoftwareupgradingisnot supported.
The following installation tasks provide information specifically for the upgrade to
this version of software. Read the information in these sections carefully before
attempting any upgrade to software.
Prepare for upgrade
Before upgrading, do the following:
•Procure the software installation files for this release via the appropriate distibution
method, such as download, CD-ROM, network drive, or external drive.
•Start up the devices you are upgrading, if they are not already started.
•Stop all media access on the devices you are upgrading.
•Shut down all applications on the devices you are upgrading.
Prepare SiteConfig for software deployment
Do the following to prepare SiteConfig for the software upgrade.
1. Make the following files accessible to the SiteConfig control point PC:
•MediaFrameServer software installation (*.cab) file
•AuroraProxyEncoder software installation (*.cab) file
•GenericISCI software installation (*.cab) file
(GenericiSCSI_x86<versionnumber>.cab for the 32-bit and
GenericiSCSI_x64<versionnumber>.cab for the 64-bit.)
•SNFS software installation *.cab file.
(SNFS_nonK2_x86<versionnumber>.cab for the 32-bit and
SNFS_nonK2_x64<versionnumber>.cab for the 64-bit.
•GVGMLib software installation (*.cab) file
•PCmonitoring software installation (*.cab) file
•Aurora Suite - software installation (*.cab) file
2. If a newer version of SiteConfig is available for upgrade and you have not yet
upgraded SiteConfig, do the following:
a) From Windows Add/Remove programs, uninstall the current version of
SiteConfig from the control point PC.
b) Install the new version of SiteConfig on the control point PC.
14 Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 18October 2010
Upgrading Aurora Browse and MediaFrame systems

Install prerequisite files on the control point PC
Some software components, such as those for Aurora products, share common
prerequisite software.You must install a prerequisite software package on the control
point PC to make the prerequisite software available for software deployment to
devices.
1. Check release notes for the required version of prerequisite files, if any.
2. On the SiteConfig control point PC, open Windows Add/Remove programs and
look for GrassValley Prerequisite Files, then proceed as follows:
•If the required version of prerequisite files is installed, do not proceed with this
task.
•If prerequisite files are not installed or are not at the required version, proceed
with this task.
3. Procure the required prerequisite software installation file. The file name is
Prerequisite Files.msi.
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.
18October 2010 Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 15
Upgrading Aurora Browse and MediaFrame systems

•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
•MDI server
•Aurora Proxy Encoder
•K2 Basecamp Express
•If you have a K2 Nearline SAN (NAS), in a deployment group named for the SAN
system, place the following devices:
•The Nearline SAN's K2 Media Servers.
Upgrade Aurora Edit, Ingest, and Playout systems
Prerequisites for this task are as follows:
•K2 systems are upgraded to the compatible version of K2 system software.
•AllAurora Browse and MediaFrame devices are offline (all media access stopped)
or shut down.
Upgrade yourAurora Edit, Ingest, and Playout systems to the compatible versions
of software. Refer to each Aurora product's release notes for procedures.
Upgrade NAS systems
Prerequisites for this task are as follows:
•K2 systems are upgraded to the compatible version of K2 system software.
•Aurora Edit, Ingest, and Playout systems are upgraded to the compatible versions
of software.
16 Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 18October 2010
Upgrading Aurora Browse and MediaFrame systems

Upgrade the MediaFrame Proxy NAS (K2 Nearline SAN) to the compatible version
of K2 software. Use SiteConfig and deploy software, using steps similar to those
for other systems.
a) Check software on the Nearline SAN's K2 Media Servers.
b) Add software *.cab file to the deployment group that contains the K2 Media
Servers.
c) Upgrade software on K2 Media Servers via a SiteConfig deployment session.
Install High PriorityWindows updates (recommended)
•Windows “High Priority”updates are recommended, but not required. While you
have devices in an offline state to upgrade software, you should check to see if
there are any new updates that you need to install. Use standard Windows
procedures.
CAUTION: Only “High Priority Updates”should be installed. Do not
install otherWindows or driver updates unless specifically directed by
product documentation or by GrassValley Support.
Check all currently installed software
Prerequisites for this task are as follow:
•The device is assigned in the SiteConfig system description and network
connectivity is present.
•SiteConfig is able to log in to the device using the username/password credentials
assigned to the device.
•The SiteConfig control point PC does not have a network drive mapped to an
administrative share (such as C$) on a device on which you are checking software.
•If the SiteConfig Network Configuration Kit and/or DiscoveryAgent at version
lower than 1.1.0.185 is currently installed, it must be manually uninstalled and
updated. For more information refer to SiteConfig Migration Instructions.
•If Aurora product software at a version lower than 6.5.2 is currently installed, it
must be manually uninstalled. For more information refer to SiteConfig Migration
Instructions.
Do the following steps on the devices that you are upgrading.
1. In the Software Deployment | Deployment Groups tree view, right-click the top-most
node for the group or any individual device and select Check Software.
NOTE: If you have access problems, verify that the adminstrator account on
the device has credentials as currently configured in SiteConfig. By default
credentialson the device shouldbe administrator/adminGV! forAuroradevices
and Administrator/adminK2 for K2 devices.
18October 2010 Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 17
Upgrading Aurora Browse and MediaFrame systems

The Check Software dialog box appears. SiteConfig searches for software on
the selected device or devices and gathers information. Progress is reported.
2. When the check is complete for the selected device or devices, close the Check
Software dialog box.
An updated list of all currently installed software is displayed in the Software
Deployment | Devices | Installed Software list view. If software is a SiteConfig managed
software package, information is displayed in the Managed Package and Deployment
Group columns.
Related Links
About installing SiteConfig
Add software package to deployment group for Aurora Browse devices
Prerequisites for this task are as follows:
•You can access the software package file from the SiteConfig control point PC.
•The devices to which you are deploying software are in a deployment group.
To review which Browse/MediaFrame software roles to install on which machine, see the
Aurora Browse Installation and Configuration Manual.
Use the following procedure to add one or more software package installation files to
the deployment group that contains the devices in the following list. Depending on
your system design, you might not have all of the device-types listed:
•MediaFrame server
•MDI server
•Aurora Proxy Encoder
•K2 Basecamp Express
•AuroraSuite
For this release of software, identify and add software package installation files as
follows:
File nameSoftware
MediaFrameServer_7.1.0.xxxx.cabMediaFrame Server
AuroraProxyEncoder_7.1.0.xxxx.cabAurora Proxy Encoder
AuroraSuite_7.1.0.xxx.cabAurora Suite
PCMonitoring_x.x.x.xx.cabGrassValley Windows Monitoring SNMP
agent
Depending on the K2 software version of your K2 SAN, also add software package
installation files as follows:
NOTE: Add files for either 3.x OR 7.x. Do not add files for both 3.x AND 7.x.
•If your devices access storage on a K2 software version 3.x K2 SAN, add software
package installation files as follows:
18 Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 18October 2010
Upgrading Aurora Browse and MediaFrame systems

File nameSoftware compatible with 3.x K2 SAN
GenericISCI_x86_3.3.x.cabGeneric iSCSI client for 32-bit systems
GenericISCI_x64_3.3.x.cabGeneric iSCSI client for 64-bit systems
GVG_MLib_3.3.2.1393.cabGVG MLib software
SNFS_nonK2_x86_x.x.x.xxx.cab (Use
version compatible with your K2 software)
SNFS for 32-bit systems
SNFS_nonK2_x64_x.x.x.xxx.cab (Use
version compatible with your K2 software)
SNFS for 64-bit systems
•If your devices access storage on a K2 software version 7.x K2 SAN, add software
package installation files as follows:
File nameSoftware compatible with 7.x K2 SAN
GenericISCI_x86_7.2.x.cabGeneric iSCSI client for 32 bit systems
GenericISCI_x64_7.2.x.cabGeneric iSCSI client for 64 bit systems
GVG_MLib_7.2.x.cabGVG MLib
SNFS_nonK2_x86_x.x.x.xxx.cab (Use
version compatible with your K2 software)
SNFS for 32 bit systems
SNFS_nonK2_x64_x.x.x.xxx.cab (Use
version compatible with your K2 software)
SNFS for 64 bit systems
You can add files for both 32 bit and 64 bit systems because when SiteConfig deploys
software it automatically deploys the 32 bit or 64 bit software appropriate for the target
device.You must install SNFS as a separate cab file. SNFS is not bundled with the
Generic iSCSI cab file.
1. In the Software Deployment | Deployment Groups tree view, select a deployment
group.
2. Click the Add button.
The Add Package(s) dialog box opens.
3. Do one of the following to select the software package:
•Select from the list of packages then click OK.
•Click Browse, browse to and select the package, then click Open.
4. If one or more EULAs are displayed, accept them to proceed. If you do not accept
a EULA, the associated software is not assigned to the deployment group.
SiteConfig adds the package to the deployment group.
The package appears in the Managed Packages list for the selected deployment group.
SiteConfig creates new software deployment tasks for the package and displays them
in the Tasks list view.
18October 2010 Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 19
Upgrading Aurora Browse and MediaFrame systems

Setting deployment options
Pre-requisites for this procedure are as follows:
•A software package has been assigned to the deployment group and applicable
deployment tasks are now displayed in the Tasks area.
1. In the Software Deployment | Deployment Groups tree view, select a deployment
group.
2. In the Tasks list view, view tasks and determine if you must set deployment options.
Tasks that need to have deployment options set display in the Details column a
message stating "Deployment options required."
If you select a task that needs to have its deployment options set, the Start
Deployment button is disabled and the message is displayed next to the button.
3. Proceed with next steps to set deployment options for the following:
•GVG_MLib
•MediaFrame Server
•Proxy Encoder
•Aurora Suite
4. Do one of the following to set deployment options:
•Double-click the task.
•Select the task and click the Options button.
A wizard opens.
5. Work through wizards and set deployment options as follows:
Deployment options
Software
Enter the name(s) of the K2 Media Server(s) with role of file system
server (FSMs)
GVG_MLib
MediaFrame
Server and
20 Aurora Browse Version 7.1.0 Release Notes and Upgrade Instructions 18October 2010
Upgrading Aurora Browse and MediaFrame systems