Attachment J2 - Baton Installation Manager Guide.pdf

BATON Installation Manager Guide Version 9.3

Installing BATON Enterprise on Windows Platform

Copyright2007-2025 Interra Systems, Inc. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form by any means without the written permission of Interra Systems, Inc., 1601 S. De Anza Boulevard, Suite 212, Cupertino, CA 95014. Phone: +1 408 579 2000. Fax: +1 408 579 2050.

Installation Guide for Installing BATON Enterprise on the Windows Platform.

Version: 9.3

BATON is a trademark registered with Interra Systems, Inc.

All other product names mentioned are trademarks of their respective owners

Open Source License Acknowledgment

BATON uses the following third-party software:

Python 3 Libraries pycurl-7.45.1 apscheduler 3.10.1 azure-core 1.7.0 azure-storage-blob 2.1.0 boto3 1.24 crossplane 0.5.8 channels 3.0.4 Django 4.0.3 django-clone 4.1.2 django-cors-headers 3.13.0 django-debug-toolbar 3.2.4 django-guardian 2.4.0 django-modern-rpc 1.0.0 django-role-permissions 3.1.1 djangorestframework 3.13.1 djangorestframework-simplejwt 5.1.0 django-silk 5.2.0 dnspython 2.2.1 drf-nested-routers 0.93.4 drf-spectacular 0.24.2 dropbox 11.36.2 ec2-metadata 2.10.0 elastic-transport 8.4.0 elasticsearch 7.17.8 elasticsearch-dsl 7.4.0 flask_sqlalchemy 3.0.3 gcs-oauth2-boto-plugin 3.0 google-cloud-storage 2.9.0 httplib2 0.20.4 Jinja2 3.1.2 jsonschema 4.12.1 ldap3 2.9.1 matplotlib 3.7.1 netifaces-plus 0.12.0 Pillow 9.5.0 platformdirs 2.5.2 psutil 5.9.5 psycopg2 2.9.6 pycryptodome 3.18.0 pyOpenSSL 23.0.0 pypiwin32 223 pysnmp 4.4.12 python3-ldap 0.9.8.4 python3-saml 1.15.0 PyYAML 6.0 redis 4.3.4

Licensed Software Acknowledgment BATON uses third-party software subject to the following licenses:

retry-decorator 1.1.1 suds-py3 1.4.5.0 Twisted 23.10.0 user-agents 2.2.0 uvicorn 0.32.0 waitress 2.1.2 websockets 13.1 winshell 0.6 wmi 1.5.1 xlwt 1.3.0 z3c.rml 4.2.1 faster-whisper v1.1.1

QT SDK 5.6.2 Grass Valley 6.52 Cineform 5.5.0 Dolby E Decoder 2.0.0 Dolby Vision Mastering Tools SIDK 5.1.0 Dolby AC-4 Professional Decoder 1.2.0 Dolby Digital (AC3) and Dolby Digital Plus (E-

AC3) 4.2

DTS 3.75.50

Dolby Professional Loudness Metering 1.0.0 DN x HD Avid 2.1.0 IPP Library 5.3.3 Logstash 7.16.3 MainConcept MVC 9.5 Beta MainConcept H.264 13.4 MainConcept MPEG4 13.4 MainConcept H.265 13.4 Dolby Atmos Storage SIDK Atmos 1.3 WMV Prores 7.7.2 Prores AVFoundation and QTKit MPEG-4 SStP (Sony) 1.1.5.50 Sony RAW SonyRawDev.dll 3.3.3.0 Guess Language Cinavia SDK 2 REDCODE (RED Camera) R3DSDK-2015MT.lib 6.3

Nielsen Decoder SDK 3.0.0

TIFF 4.0.6 winshell 0.6 ( https://pypi.python.org/ pypi/winshell ) elasticsearch 7.16.3 redis-windows 7.2.5 ARRIRAW SDK 6.2.2.0 Filebeat 7.16.3 Comprimato 2.6.4 AWS SDK 1.9 Avid DNxHR 2.2 DNG 1.5.0 Open EXR 3.1.1 whisper-base Hunspell 1.7.0 FLAC Audio1.3.3 libpng 1.6.37 libsamplerate 0.1.9 Netflix Photon 4.8.0 DTS 3.75.50

Client Side Software Acknowledgment

BATON uses client-side software subject to the following licenses:

axios 0.19.2 chart.js 2.9.3 core-js 3.6.5 d3 5.16.0 dagre-d3 0.6.4 json-server 0.16.1 vue 2.6.11 vue-chartjs 3.5.0 vue-infinite-loading 2.4.5 vue-multipane 0.9.5 vue-router 3.2.0 vuetify 2.2.11 vuetify-datetime-picker 2.1.1 vuex 3.4.0 Node.js 13.7.0 Dojo 1.10

For further questions and support:

Email: baton_support@interrasystems.com

Web: http://www.interrasystems.com

Toll Free No.: (1-877) BATON is (1-877-228-6647)

Postgresql 14.17 Dolby Vision® Confidential unpublished works.

Copyright© 2018-2021 Dolby Laboratories. All rights reserved

Dolby Atmos® Confidential unpublished works. Copyright© 2021 Dolby Laboratories.

All rights reserved mailto:baton_support@interrasystems.com http://www.interrasystems.com http://www.interrasystems.com http://www.baton.interrasystems.com http://www.interrasystems.com http://www.interrasystems.com

Table of Contents What is New

Release 9.3

New Features

Chapter 1: Introduction Overview of BATON

BATON Components

Types of BATON Setups

Single BATON Enterprise

BATON Enterprise Cluster

Chapter 2: Getting Started Pre-Requisites and System Requirements of BATON

Pre-Requisites

System Requirements

Choosing the Components to Install

BATON Enterprise Cluster

BATON HA

BATON Expansion

Planning and Preparing BATON Installation

Chapter 3: BIM Overview Purpose of BIM

Extracting and Launching BIM

The BIM Interface

Available Modes and Installation Types in BIM

System Requirements for BIM

Installation Guidelines

Initiating BIM and Reviewing Requirements

Chapter 4: Installing a Fresh BATON Setup Selecting Installation Type

Configuring Machine and Service Details for Local Installation

Configuring Machine and Service Details for Cluster-wide Installation

Reviewing Pre-Installation Checklist

Installing BATON in Different Configurations

Completing Installation

Chapter 5: Upgrading an Existing BATON Setup Upgrading BATON

Upgrading Local Installation of BATON

Upgrading Cluster-wide Installation of BATON Installed on Multiple Machines

Rollback Scenarios

Upgrading from BATON Standard to BATON Enterprise

Upgrading the License

Upgrading BATON Expansion Setup

Chapter 6: Configuring and Upgrading BATON HA Installing and Configuring BATON Enterprise with HA

Upgrading BATON Enterprise HA

Setting Up DB Failover Cluster

Overview of DB Failover Cluster

System Requirements

Network Infrastructure

Installing a DB Server Cluster

Configuring a DB Server Cluster

Configuring Microservices

Configuring Database Manager

Configuring VMs

Upgrading DB Failover Cluster

Upgrading DB Failover Cluster from BATON 9.x to 9.3

Upgrading DB Failover Cluster from BATON 8.x to 9.x

Setting Up VM VIP

Configuring Windows NLB Cluster

Chapter 7: Managing BATON Services BATON Service Manager (BSM) Overview

Configuring Services and Microservices Using BSM

Initiating BATON Services

Changing Port Numbers

Changing Target DB server on VM

Configuring BATON Monitor Services

Changing Proxy Details

Managing Microservices

Switching from HTTP to HTTPS

Renewing Certificate for HTTPs

Changing the Logon User

Changing Database

Chapter 8: Installing and Upgrading Data Migration Tool Installing DMT

Upgrading DMT

Accessing DMT WebHelp

Chapter 9: Accessing BATON Quick Start with BATON

Understanding the Interface

Configuring BATON Setup

Managing Licenses

Registering CS with VM

Registering Content Locations

Chapter 10: Uninstalling BATON

Chapter 11: Appendix Parsing Verification Report Using XSD Schema

XSD Files

Purpose of XSD Files

Configuring DNS and Reverse Lookup

Pre-requisites

Workaround

Registering a Proxy Server

Known Cases during Database Migration

Troubleshooting How to debug an installation issue?

.NET Framework Error During BIM Installation

Test Installer is Unable to Start Services After Changing the Log On User

BATON installed on a machine but unable to perfom basic operations

BATON UI not displaying correctly

BATON is not scheduling tasks onto some of the Checker Server

The license is uploaded, but BATON still shows an incorrect license on the license status page 147

License Upload didn't work

Where are BATON log files?

BATON application is not opening

BATON is reporting license error

The tasks scheduled are not executing, or the tasks are in queue for long

Connectivity Issue between Checker Servers or Content Locations

VM or CS service not responding

BATON does not detect the correct number of CPU cores

Active VM runs slow with API interface

How to Enable Remote Administration on Windows

How to Troubleshoot Errors Encountered while Enabling Remote Administration on Windows ...152

DCOM Access Denied (0x80070005)

BatonCache Service Fails to Start

How to Troubleshoot Errors while Fresh Installation or BATON Upgrade

BATON Upgrade Fails and Troubleshooting is Unsuccessful

BATON Stash Service Fails to Start During Fresh Installation

Technical Support

What is New

Release 9.3

New Features

BATON Installation Manager

Revamped UI:

The new user interface provides a redesigned installer experience for improving clarity, usability, and overall user engagement. The new installer features a modern dual-pane layout for faster access to settings and improved installation flow:

Left Pane- Streamlined Navigation Menu This pane provides a clear, step-by-step navigation menu, allowing you to easily track the installation journey and revisit previous steps if needed.

Right Pane- Real-Time Progress and Installation Details Context-aware pane that changes dynamically and provides progress indicators corre-sponding to each step based on the selected tab. This ensures you have immediate visi-bility into what’s happening at every installation stage.

Recommendation of System Requirements Minimum/Recommended Requirements

To ensure a smooth installation experience, the installer now displays the minimum/ recommended system requirements before the installation begins.

Manual Way to Verify Port Availability The installer prompts you to review ensure all the required ports are open and available before BATON installation.

Pre-Installation System Checks Automated pre-installation checklist

Before starting the BATON installation, the installer now automatically checks system readiness and network connectivity.

Improved Multiple Installation Modes The installer offers improved support for multiple installation modes, allowing greater flexibility based on your deployment needs:

Cluster-wide Installation: Ideal for distributed environments, this option enables the installation of BATON across multiple machines remotely.

Local Installation: Designed for simpler setups, this installs BATON directly on the local host machine.

See BIM Overview

Database Manager Related Updates

A new tool – Database Manager has been introduced to manage the database. With this, the following enhancements are done in BSM (BATON Service Manager) for managing Database Manager port and services:

BSM now displays Database Manager details, with the option to start/stop services and update port numbers.

See BSM Interface

A new service, Baton Database Manager v1 is added for managing the Database Manager tool. This service runs on the default port 8643.

See Configuring Services and Microservices

Configure Failover Database for accessing and running Database Manager services seamlessly.

See Configuring Database Manager

Support extended to update the logon user for Database Manager from BSM.

See Changing the Logon User

General Updates

Loopback support for registering Checker Servers with dynamic IP addresses is discontinued.

Consequently, the Loopback button has been removed from the BSM.

In the event of an upgrade, if loopback mode was enabled beforehand, it will remain functional but will generate a dashboard alert prompting the re-registration of the Checker Server.

Acronyms

Some of the acronyms used in this document are as follows:

Acronyms Description

BIM BATON Installation Manager

VM Verification Manager

CS Checker Server

DB Database Server

UAC User Account Control

HA High Availability

VIP Virtual IP

AMC Annual Maintenance Contract

MBR Master Boot Record

GPT GUID Partition Table

SPC-3 SCSI Primary Commands-3

FCCP Failover Cluster Configuration Program

DNS Domain Name System

LUNs Logical Unit Number

VDS Virtual Disk Service

MAC Media Access Control

Chapter 1: Introduction

BATON is an automated content verification solution for file-based media. Easily customizable for user-specified quality checks, BATON has been designed as an enterprise-class application that can be easily integrated with various infrastructure technologies in a file-based workflow.

BATON can be hosted on multiple machines, while its functions can easily be accessed through a standard web browser, thus making it a convenient multi-user system.

Read on to know about:

Overview of BATON

BATON Components

Types of BATON Setups

Overview of BATON BATON is an automated enterprise-class content verification solution for file-based media. Use BATON to create and implement customizable quality checks, which help you deliver high-quality media.

BATON Components BATON is an enterprise-class application. BATON’s core engine(s) are hosted on server computer(s) that communicate with multiple users using the organization’s LAN-based intranet.

The main components of BATON are:

Components Description

Note: For better synchronization of all BATON components, it is recommended to:

Set the same machine date and time on all systems where the VM, CS, DB, and BATON cli-ents are installed.

While installing BATON on AWS, deploying in hybrid mode, or upgrading, ensure that all the BATON components are on the same domain or network.

Verification Manager

(VM)

VM is the central component of BATON and runs as a service on a server. The VM coordinates various functions of BATON and acts as interface between the BATON clients, the DB Server, and the CS.

Checker Server (CS) CS is a service that runs on an independent server or on the same server where the VM is hosted. You can have one or more CS services running in a BATON Enterprise setup. The CS runs the media analysis and verification tasks.

BATON Client BATON Client is a web-based user interface that can be accessed by any standard browser. BATON Client provides a window to the various functions that can be executed using BATON. The BATON client is a part of the VM and requires no additional installation.

BATON Database (DB) Server

BATON DB Server stores verification reports and other information.

BATON Enterprise with a DB Server is suitable for fault tolerance at the database level.

Types of BATON Setups A BATON Enterprise setup enables easy scaling of content verification and QC to handle high volume, high density content, or meet high throughput requirements.

BATON Enterprise is designed to quickly scale verification and offers you various options based on verification load requirements and infrastructure setup. In addition, you can ensure a completely failsafe BATON Enterprise setup by adopting BATON High Availability (HA) and implementing BATON’s failsafe DB server.

This section gives you a preview of BATON Enterprise setups. These include:

Single BATON Enterprise

Single BATON Enterprise with BATON DB Server

Single BATON Enterprise with Failsafe BATON DB Sever

BATON Enterprise Cluster

BATON Enterprise Cluster with BATON DB Server

BATON Enterprise Cluster with Failsafe BATON DB Server

BATON HA

Single BATON Enterprise with HA

Single BATON Enterprise with HA and DB Server

Single BATON Enterprise with HA and Failsafe DB

BATON Enterprise Cluster with HA

BATON Enterprise Cluster with HA and DB Server

BATON Enterprise Cluster with HA and Failsafe DB

Single BATON Enterprise

A Single BATON Enterprise consists of a single VM. However, you can have more than one CS(s) installed on more than one computer, as per the needs of the facility. A CS can also be installed with the VM on the same computer. CS(s) can always be added to scale-up verification.

Here are the illustrations of a Single BATON Enterprise setups.

Single BATON Enterprise with BATON DB Server The following illustration depicts a Single BATON Enterprise in which a single VM is connected to a CS farm of six servers. VM is connected to a BATON DB that is installed on a separate server. Alternatively, the BATON DB can also be installed on the same server as the VM.

Note: For details of the installation process, refer Installing a Fresh BATON Setup.

Single BATON Enterprise with Failsafe BATON DB Sever The following illustration depicts a Single BATON Enterprise in which a single VM is connected to a CS farm of six severs. VM is connected to a failsafe BATON DB.

Note: For details of the installation process, refer Installing a Fresh BATON Setup. For DB Failover clustering, refer Setting Up DB Failover Cluster.

BATON Enterprise Cluster

A BATON Enterprise Cluster is a BATON farm that consists of more than one VM. These VMs are grouped as a cluster and work with several CS(s) to ensure content verification. The VM(s) communicate with the BATON DB server.

Recommended: It is recommended that a BATON VM cluster have a maximum of ten VM(s). It is also recommended that there be a maximum of seven CS(s) for each VM in the cluster.

You can use BATON’s DB failsafe technique to ensure that the BATON DB is fault- tolerant. In addition, you can create a VIP for the BATON cluster to ensure seamless access to BATON functions from the BATON clients.

Here are illustrations of recommended BATON Enterprise Cluster setups.

BATON Enterprise Cluster with BATON DB Server The following illustration depicts a BATON Enterprise Cluster that is connected to a BATON DB server.

The BATON DB can also be installed with the VM on the same computer.

Note: For details of the installation process, refer Installing a Fresh BATON Setup.

BATON Enterprise Cluster with Failsafe BATON DB Server The following illustration depicts a BATON Enterprise Cluster that is connected to a failsafe BATON DB server.

Note: For details of the installation process, refer Installing a Fresh BATON Setup. For DB Failover clustering, refer Overview of DB Failover Cluster.

BATON HA

BATON HA enables failsafe, 24/7 content verification in the BATON Enterprise setup.In a BATON Enterprise setup, verification of content can be affected if a BATON VM is unavailable. This, in turn, can result in operational inefficiency in a file-based workflow, leading to ineffective content monetization.

BATON HA ensures the persistent uptime of BATON verification.A BATON HA setup consists of one or more active VMs and a backup VM. The backup VM immediately takes over control of BATON operations when an active VM is unavailable. The active and backup VMs are connected to a common database;

therefore, reports, verification results, and Test Plans are concurrent at all times.

Here are samples of BATON Enterprise setups with BATON HA.

Single BATON Enterprise with HA

A Single BATON Enterprise setup consists of a single BATON VM that is connected to one or more CS. In this setup, if the VM is not available, content verification may stall until the VM is available again.BATON HA is implemented by adding a second BATON VM. One VM is configured as an active VM, and the other VM is configured as a backup VM. The VMs are connected to a BATON DB server. You can also ensure that the DB server is failsafe. In addition, you can setup a VIP to ensure seamless access to the BATON functions by the BATON clients.

The following sections depict the recommended Single BATON Enterprise Setups with HA.

Single BATON Enterprise with HA and DB Server

The following illustration depicts a single BATON Enterprise with HA that consists of an Active VM connected to multiple CSs. In addition, there is a Backup VM that immediately takes over BATON operations if the Active VM is unavailable. When the Active VM is available again, the Backup VM goes back to its standby state. Both the Active and the Backup VMs are connected to the same DB server.

Note: For details of the installation process, refer Installing and Configuring BATON Enterprise with HA.

Single BATON Enterprise with HA and Failsafe DB

You can also have a failsafe DB with Single BATON enterprise with HA, as illustrated below:

Note: For details of the installation process, refer Installing and Configuring BATON Enterprise with HA.

For DB Failover clustering, refer Overview of DB Failover Cluster.

BATON Enterprise Cluster with HA

A BATON Enterprise Cluster consists of two or more VMs, which are connected to several CSs. In this setup, if one VM is not available, content verification continues as other VMs automatically handle BATON operations. However, the efficiency of verification in a workflow may be affected. In a file-based workflow where several processes are critically linked, inefficient verification may lead to cascading inefficiency throughout the workflow.

In a BATON Enterprise Cluster, BATON HA is implemented by adding a backup VM and configuring all the other VMs in the cluster as active VMs. If any active VM is not available, the backup VM handles the operations of the unavailable VM.

The following sections depict the recommended BATON Enterprise cluster setups with HA.

BATON Enterprise Cluster with HA and DB Server

The following illustration depicts a BATON Enterprise Cluster with HA. In the BATON Enterprise Cluster, there are more than one active VM that is connected to several CSs. In addition, there is a backup VM, which becomes active when any of the active VMs are unavailable. When the active VM is available again, the backup VM goes back to its standby state.

Note: For details of the installation process, refer Installing and Configuring BATON Enterprise with HA.

BATON Enterprise Cluster with HA and Failsafe DB

You can also have a failsafe DB with BATON Enterprise cluster with HA.

For details of the installation process, refer Installing and Configuring BATON Enterprise with HA.

For DB Failover clustering, refer Overview of DB Failover Cluster.

Chapter 2: Getting Started

This chapter lets you know how to get started with installation of BATON.

Read on to know about:

Pre-Requisites and System Requirements of BATON

Choosing the Components to Install

Planning and Preparing BATON Installation

Pre-Requisites and System Requirements of BATON Before you begin the installation of BATON, make sure your system fulfills the following pre-requisites and system requirements.

Recommendation: We have provided minimum and recommended software and hardware requirements for BATON setup. However, to achieve maximum performance, it is recommended to use DB under SSD or high configuration mode and EC2 with optimized core-performance.

BATON supports network configurations that use either IPv4 exclusively or a combination of IPv4 and IPv6. However, configurations that use only IPv6 are currently not supported.

Pre-Requisites

The following pre-requisites need to be followed for BATON installation/upgrade:

Before installing BATON 9.x, ensure that IPv6 is disabled on all machines where the BATON components (VM, CS, DB) will be installed. This can be done by navigating to Control Panel>Network and Sharing Center>Properties of the NIC.

This step is mandatory.

If the machines where BATON 9.x will be installed are part of a domain, ensure that all machines have appropriate entries in the "Forward Lookup Zone" and "Reverse Lookup Zone" on the DNS.

This step is mandatory.

Ensure that you have admin rights to install BATON and its components through BIM.

Ensure that all the machines hosting BATON components are mutually accessible. BATON communicates with each host using its hostname or full computer name (FQDN). Test connectivity between hosts using the ping command from the command prompt.

For example, on BATON servers Baton1 and Baton2, the commands "ping Baton1" and "ping Baton1.mydomain.com" should work from both Baton1 and Baton2, and vice versa.

Ensure all machines of BATON components are in the same domain(if not in workgroup) and BIM should be launched from any one of the machines.

For this, verify the DNS server name using the nslookup command.

For example, for BATON servers, Baton1 and Baton2, the nslookup command on both the machines should give the same DNS server name, such as subdomain.domain.com and the full machine name for both the servers should be Baton1.mydomain.com and Baton2.mydomain.com respectively.

Please verify the full machine name from Control Panel\System and Security\System.

Machine configuration of all servers that are part of the BATON cluster should be known.

Identify the firewall rules (if any) on the ports used by BATON services and ensure no BATON ports are blocked. The default ports are: 8080, 8060, 9000, 9060, 9205, 9605, 6389, 8642, 8643, 8653, 8070, 8040 and 6666.

Ensure that enough disk space is available on servers where BATON components are to be installed (fresh or upgrade).

Local Installation: Requires 12 GB of storage.

Remote Installation: Requires 15 GB of storage.

Upgrade on DB Server requires additional:

10 GB for the Migration Tool installation.

Storage equivalent to 2 times the size of the databases, for backup and copying data into the Migration Tool folder.

Upgrade on Checker Server from 8.x or older version requires additional space which is equal to the size of projects folder present at <InstallationLocationof8.x or olderversionBATON >\baton- Sites\CheckerServer\projects. This space is required for copying data to version 9.x.

When upgrading from 9.x, place the existing 9.x installer in the same local folder as the new installer to enable rollback if the upgrade fails.

If a previous upgrade was done from version 7.x or 8.x to 9.x and is functioning properly and reliably, it is recommended to uninstall any remaining 7.x/8.x versions of BATON along with the already installed Data Migration Tool. This step should be performed before upgrading from 9.x to 9.1 or later.

For AWS setup, identify if any custom DNS is configured.

Ensure that the DNS Hostnames and DNS Resolution settings are enabled in VPC while installing BATON on AWS. In case the setting is disabled, BATON fails to fetch the IP address through the hostname.

If a service account other than LocalSystem is being used to run BATON services, validate the permissions and credentials. Limited permissions for other users may lead to difficulties managing BATON services, potentially impacting post-installation functionalities.

Before upgrading, note the current RAM usage by BATON services.

System Requirements

Ensure you meet the following requirements before you install BATON:

VM Requirements

CS Requirements

DB Requirements

VM and DB Requirements

CS and DB Requirements

VM and CS Requirements

VM, CS, and DB Requirements

Browser Application

Few Points To Be Noted:

For the best performance of BATON, it is recommended to turn off hyper-threading in the CS.

Since the VM, DB, and CS run the engines of BATON, the computers that host these services must have sufficient disk space and at least 6 physical cores.

Apart from specific NLB and failover cluster configurations, BATON standalone setup is supported on all non-server operating systems (except the discontinued operating systems, Windows XP and Windows 2003).

For better synchronization of all BATON components, it is recommended to:

Set the same machine date and time on all systems where the VM, CS, DB, and BATON clients are installed.

While installing BATON on AWS, deploying in hybrid mode, or upgrading, ensure that all the BATON components are on the same domain or network.

VM Requirements Operating Systems

Few Points To be Noted:

BATON will not install or upgrade if the system is running on Windows Server 2012 or an earlier version.

BATON Enterprise setup with NLB is supported on server editions only.

Processor

Minimum: 6-core machine with 4 cores for VM and 2 cores for OS.

RAM

Minimum: 16 GB and an additional 1 GB per core for greater than 6 cores.

Recommended: If the number of cores in a machine are increased, the RAM should be increased proportionately to get maximum performance benefit.

Disk Space

About 500 GB to store the reports and other data generated by BATON.

Cloud Hardware Recommendations for VM Instance type: t3.2xlarge

RAM: 32 GB

Cores: 8-core machine

BATON Setups

Operating System BATON Enterprise (Single/ Multi VM)

BATON Enterprise Cluster with NLB

Windows 10 Supported Not Supported

Windows 11 Supported Not Supported

Windows Server 2016 Supported Supported

Windows Server 2019 Supported Supported

Windows Server 2022 Supported Supported

CS Requirements Operating Systems

All operating systems are supported in case of CS. However, CS Windows option may be limited or constrained by BATON edition (as per table in VM section).

BATON will not install or upgrade if the system is running on Windows Server 2012 or an earlier version.

Processor

Minimum for 4K content: 12-core.

It is recommended that you run each task with at least 8 cores.

Minimum for Non-4K content: 6-core machine with 4 cores for CS and 2 cores for OS.

RAM

1 GB RAM per license CS core for SD analysis.

2 GB RAM per license CS core for HD analysis.

4 GB RAM per license CS core for 4K analysis.

Tip: If the numbers of cores in a machine are increased, the RAM should be increased proportionately to get maximum performance benefit.

Disk Space

About 500 GB to store the reports and other data generated by BATON.

CS Software Requirements

Install the latest version of QuickTime SDK for verification of quick time videos, such as ProRes (non-accelerated) and Photo jpeg files. For decoding Canopus HQ video, you need to install GV Codec.

Cloud Hardware Recommendations for CS

For 4K content:

Instance Type: c5.4xlarge

RAM: 32 GB

Cores: 16-core machine

For Non 4K content:

Instance Type: t3.2xlarge

RAM: 32 GB

Cores: 8-core machine

DB Requirements Operating Systems

Few Points to be Noted:

BATON will not install or upgrade if the system is running Windows Server 2012 or an earlier version.

For Failover support in DB, the database storage must be on SAN.

Processor

Recommended: Quad Core.

RAM

Recommended: 16 GB.

Disk Space

About 500 GB to store the reports and other data generated by BATON.

It is recommended to use SSD drive in database servers, as performance of SSD is 2-3 times faster than

HDD.

Cloud Hardware Recommendations for DB Instance Type: t3.xlarge

RAM: 16 GB

Tip: Cores: 4-core machine

BATON Setups

Operating System BATON Enterprise (Single/ Multi VM)

BATON Enterprise Cluster with Failover

Windows 10 Supported Not Supported

Windows 11 Supported Not Supported

Windows Server 2016 Supported Supported

VM and DB Server Requirements Operating Systems

Few Points To be Noted:

BATON will not install or upgrade if the system is running Windows Server 2012 or an earlier version.

BATON Enterprise setup with NLB is supported on server editions only.

For Failover support in DB, the database storage must be on SAN.

Processor

Minimum: 6-core machine with 4 cores for VM and DB, and 2 cores for OS.

RAM

Minimum: 16 GB.

Recommended: If the number of cores in a computer are increased, the RAM should be increased proportionately to get maximum performance benefit.

Disk Space

About 500 GB to store the reports and other data generated by BATON.

Cloud Hardware Recommendations for VM and DB Instance Type: t3.2xlarge

RAM: 32 GB

Cores: 8-core machine

BATON Setups

Operating System BATON Enterprise (Single/ Multi VM)

BATON Enterprise Cluster with NLB + Failover

Windows 10 Supported Not Supported

Windows 11 Supported Not Supported

Windows Server 2016 Supported Supported

CS and DB Requirements Operating Systems

Few Points to be Noted:

BATON will not install or upgrade if the system is running Windows Server 2012 or an earlier version.

For Failover support in DB, the database storage must be on SAN.

Processor

Recommended: 8-core machine with 4 cores for CS, 2 cores each for DB and OS.

RAM

Recommended: 16 GB.

Disk Space

About 500 GB to store the reports and other data generated by BATON.

It is recommended to use SSD drive in database servers, as performance of SSD is 2-3 times faster than

HDD.

To know more about the system requirements for 4K file analysis, click here.

CS Software Requirements

Install the latest version of QuickTime SDK for verification of quick time videos, such as ProRes (non-accelerated) and Photo jpeg files. For decoding Canopus HQ video, you need to install GV Codec.

Cloud Hardware Recommendations for CS and DB

For 4K Content:

Instance Type: c5.4xlarge

RAM: 32 GB

Cores: 16-core machine

For Non-4K Content:

Instance Type: t3.2xlarge

RAM: 32 GB

Cores: 8-core machine

BATON Setups

Operating System BATON Enterprise (Single/ Multi VM)

BATON Enterprise Cluster with Failover

Windows 10 Supported Not Supported

Windows 11 Supported Not Supported

Windows Server 2016 Supported Supported

VM and CS Requirements Operating Systems

Few Points To Be Noted:

BATON will not install or upgrade if the system is running on Windows Server 2012 or an earlier version.

BATON Enterprise setup with NLB is supported on server editions only.

Processor

Minimum: 8-core machine with 2 cores each for VM, CS and OS.

RAM

Minimum: 16 GB and an additional 1 GB per core for greater than 6 cores.

Recommended: If the number of cores in a machine are increased, the RAM should be increased proportionately to get maximum performance benefit.

Disk Space

About 500 GB to store the reports and other data generated by BATON.

Note: To know more about the system requirements for 4K file analysis, click here.

CS Software Requirements Install the latest version of QuickTime SDK for verification of quick time videos, such as ProRes (non-accelerated) and Photo jpeg files. For decoding Canopus HQ video, you need to install GV Codec.

Cloud Hardware Recommendations for VM and CS For 4K Content:

Instance Type: c5.4xlarge

RAM: 32 GB

Cores: 16-core machine

For Non-4K Content:

Instance Type: t3.2xlarge

RAM: 32 GB

Cores: 8-core machine

BATON Setups

Operating System BATON Enterprise (Single/ Multi VM)

BATON Enterprise Cluster with NLB

Windows 10 Supported Not Supported

Windows 11 Supported Not Supported

Windows Server 2016 Supported Supported

VM, CS, and DB Requirements If VM, CS and DB Server are installed on the same machine, then the following requirements need to be fulfilled:

Operating Systems All operating systems are supported in this case. However for CS, the option for Windows OS may be limited or constrained as per the BATON editions (as mentioned in the table under the VM Requirements section).

BATON will not install or upgrade if the system is running on Windows Server 2012 or an earlier version.

Processor

Minimum: 8-core machine.

RAM

Minimum: 16 GB and an additional 1 GB per core for greater than 12 cores.

If the number of cores in a computer are increased, the RAM should be increased proportionately to get the maximum performance benefit. For optimum performance under moderate/high load work-flows, 32 GB is recommended.

Disk Space

About 500 GB to store the reports and other data generated by BATON.

Note: To know more about the system requirements for 4K file analysis, click here.

Cloud Hardware Recommendations for VM, DB and CS For 4K Content:

Instance Type: c5.4xlarge

RAM: 32 GB

Cores: 16-core machine

For Non-4K Content:

Instance Type: t3.2xlarge

RAM: 32 GB

Cores: 8-core machine

Network BATON works on the media content that resides on the content servers on your organization’s LAN. To quickly access the media content using the FTP protocol, BATON needs a high-speed LAN environment.

Therefore, we recommend a Gigabyte Ethernet LAN to fully utilize the potential of BATON.

Browser Application BATON’s user interface can be easily accessed by a standard web browser.

We recommend the following browsers:

Microsoft Edge Version 137.0.3296.83(official build) (64-bit)

Mozilla Firefox 139.0.4 (64-bit)

Google Chrome Version 137.0.7151.57 (Official Build) (64-bit)

Currently, mobile browsers are not supported.

Choosing the Components to Install Before installing BATON Enterprise, you need to choose the components for the BATON installation.

Typically, you may need to choose the following:

Which computer would be the VM?

How many CSs would be required?

Would any CS be installed on the same computer as the VM?

BATON Enterprise Cluster

If you are planning to set up a BATON Enterprise Cluster, you also need to plan:

Number of VMs in the BATON cluster.

It is recommended to have a maximum of ten VMs in a cluster.

Number of CS required. It is recommended to have a maximum of seven CS for each VM.

For example, if you plan a cluster of four VMs, it is recommended to have a maximum of 28 CS.

VIP for seamless access to BATON VMs, if required.

For BATON DB, you may need to choose:

Whether the DB server will be installed with the VM or on a separate computer?

Should a failsafe BATON DB be setup?

For information on BATON Enterprise setups, refer to Types of BATON Setups.

BATON HA

For a BATON HA setup, you may need to identify:

The VM that will act as the Backup VM.

The VM(s) that will act as the Active VM(s).

For information on BATON Enterprise HA setups, refer Installing and Configuring BATON Enterprise with

HA.

BATON Expansion

You can also configure BATON by expanding it on cloud or in hybrid mode. For information on:

Expansion, refer BATON WebHelp.

AWS configurations, refer BATON Deployment on AWS.pdf.

Planning and Preparing BATON Installation Before you begin installation, remember the following points:

By default, the VM, CS, DB and DB Manager run on different ports as mentioned below:

VM runs on the port 8080 as a web service.

CS runs on the port 9000.

DB runs on the port 9205, 6389, 9605,and 8642.

DB manager runs on the port 8643

You can specify different port numbers for VM, DB Server, and CS. But make sure the specified ports are free. By default, the shortcut to access BATON programs and files is Start > Programs > BATON.

After the installation, if BATON does not open, access it using the following URL:

http: //<name of the computer where VM is installed>:8080 E.g. https: //localhost:8080 or http: //<IP address of the computer where VM is installed>:8080 E.g. https: //l23.43.45:8080

The default user name and password to access BATON is:

username: admin password: admin

Chapter 3: BIM Overview

To install BATON, BATON Installation Manager (BIM) is provided, that facilitates you to install and upgrade a BATON Enterprise Setup.

Read on to know more about:

Purpose of BIM

Extracting and Launching BIM

The BIM Interface

Available Modes and Installation Types in BIM

System Requirements for BIM

Installation Guidelines

Initiating BIM and Reviewing Requirements

Purpose of BIM The BATON Installation Manager (BIM) is a powerful tool designed to streamline the installation and upgrade process of BATON Enterprise Setup. It provides a seamless way to deploy and configure core components such as Verification Manager (VM), Database Server (DB), and Checker Server (CS), along with optional add-ons like LID and Nielsen.

BIM enhances flexibility by allowing customization of port numbers associated with BATON components and microservices. Using BIM, you can deploy BATON on one or multiple machines by installing BATON components on different machines.The advantages of BIM are:

Increases efficiency in managing large-scale BATON enterprise setups.

Installs BATON Enterprise on individual systems remotely, thereby saving the time and effort of administrators.

Installs multiple CSs and VMs at once on different machines.

The user-friendly BIM installer offers intuitive, step-by-step guidance to ensure a seamless setup experience.

Extracting and Launching BIM Using BIM, you can install or upgrade BATON Enterprise. For this, first you need to extract BIM.

To extract BIM:

1. Double-click the BATON Installation Manager exe provided by BATON team.

The Extract Baton Installation Manager page is displayed, as shown below:

2. In the Destination folder drop-down, browse for a path where you want to extract the BIM files.

Note: By default, BIM is extracted at C:\. You may change the location as per your requirement.

3. Click Install.

A progress bar appears indicating the installation status, as shown below:

After the extraction is complete, the BATON Installation Manager page is displayed. Refer to The BIM Interface

The BIM Interface BIM is an executable installer. This installer has all the necessary files and resources compiled into a package including the executable files, libraries, configuration files, and any other assets required for BATON to run.

The image below shows the BIM interface:

The BIM interface is divided into two panes:

Left Pane- Streamlined Navigation Menu This pane provides a clear, step-by-step navigation menu, allowing you to easily track the installa-tion journey and revisit previous steps, if needed.

Right Pane- Real-Time Progress and Installation Details This pane is context-aware that changes dynamically and provides progress indicators correspond-ing to each step based on the selected tab. This ensures you have immediate visibility into what’s happening at every installation stage.

Available Modes and Installation Types in

BIM

BIM simplifies BATON deployment in two modes: Fresh and Upgrade. Furthermore, BIM provides Cluster-wide or Local installation types for installing BATON.

Refer to the the table below:

Modes /Installation Type

To

Install BATON on one or multiple machines.

Install BATON on local machine.

Fresh Installation Install fresh BATON instance.

Upgrade Upgrade an existing BATON setup.

Cluster-wide

Local

System Requirements for BIM At least 4 GB of storage space is required to copy BIM, which contains all the necessary files for installing

BATON.

Installation Guidelines Before running BIM, remember the following points:

While configuring the BATON setup, remember the following User Account Control (UAC) conditions:

If the machines where you are installing BATON and the one launching BIM are in same domain, use the domain administrator account.

If the machine where you are installing BATON is a part of workgroup, use the built-in administrator account.

If you use any other user account with administrator rights, disable UAC.

By default, BIM installs/upgrades VM on port 8080, CS on port 9000, and the database on port 8642.

You can also customize the port numbers and the default locations where you want to install BATON.

Ensure that all these ports are available.

If you're using local mode installation, you can install only one database server. To set up a failover cluster, you'll need to install two database servers. Installing more than two servers is not supported.

Before using BIM to install or upgrade BATON components on remote servers, ensure those servers have administrative rights and privileges. You will be required to provide the administrator login credentials of the remote server to BIM.

Initiating BIM and Reviewing Requirements Using BIM, you can install or upgrade BATON Enterprise. For this, follow the steps mentioned below:

1. From the Welcome tab of BIM, click Next to move to License Agreement page, as shown below:

The License Agreement page appears, as shown below:

2. Select the I agree to the Terms and Conditions checkbox.

The Next button gets enabled.

3. Click Next.

The System Requirements page appears, as shown below:

The minimum/recommended system requirements, along with the required ports for BATON installa-tion, are displayed on this page. To know more, refer to System Requirements.

4. Ensure that your machine meets all the listed requirements, including operating system version, pro-cessor type, CPU, RAM, and available disk space. Also, confirm that the displayed ports are free and not in use.

Once you have verified, select the I confirm that the machine meets all the requirements men-tioned above checkbox to proceed.

5. Click Next.

BIM checks for a pre-existing BATON setup, as shown below:

If no existing setup is detected, BIM proceeds with Fresh Installation.

To know more refer to Installing a Fresh BATON Setup.

If any existing BATON setup is detected, BIM upgrades the same.

To know more refer to Upgrading an Existing BATON Setup.

Depending on whether an existing installation is detected, BIM proceeds accordingly and prompts you to select the installation type.

Chapter 4: Installing a Fresh BATON Setup

Machines without an existing BATON installation are eligible for a fresh installation. BIM automatically checks for existing BATON installations and deploys a new instance based on the selected options and configured settings.

For further steps, you can refer to the following:

Selecting Installation Type

Configuring Machine and Service Details:

Configuring Machine and Service Details for Local Installation

Configuring Machine and Service Details for Cluster-wide Installation

Reviewing Pre-Installation Checklist

Completing Installation

Selecting Installation Type Once BIM detects whether it's a fresh setup or an upgrade, the next step is to select the Installation Type, as shown below:

BIM offers two types of installation, that you can choose as per your requirement:

Local Installation: On selecting the Local Installation option, BIM installs BATON on the same host machine. To know more, refer to Configuring Machine and Service Details for Local Installation.

Cluster-wide Installation: On selecting the Cluster-wide Installation option, BIM installs BATON across multiple machines that work as a cluster. This option is commonly used for high availability and load balancing. To know more, refer to Configuring Machine and Service Details for Cluster-wide Installation.

Configuring Machine and Service Details for Local Installation

To configure machine and service details for local installation, follow the steps mentioned below:

1. Select the Local Installation option from the right pane of the InstallationType window, as shown below:

2. Click Continue.

The Machine and Service Details pop-up appears, as shown below. This pop-up provides configura-tion options to add details of the machine where BATON is to be installed and select services to be installed.

Since all the BATON components will be installed on the local machine, the IP/Host Name is auto-filled, but you can edit the name if required.

3. In the Baton Installation Folder field, provide the location where BATON and its services will be installed.

You can click to browse the location.

Note: Currently, unicode characters are not supported in folder file paths for the installation of BATON.

4. Under the Install Service(s) section, enable the Verification Manager, Checker Server, and Database Server checkbox, as required.

Additionally, you can provide the details of a remote DB if you have a pre-installed DB. To know more, click here

5. Under the Baton Service Log On section, in the Service Log On Credentials field, enter the login credentials of the user account using which BATON services will be run.

By default, services will run on LocalSystem account.

This field is optional.

6. Click Add.

The machine is added and displayed, as shown below. All the selected BATON components will be installed on the machine.

7. Click icon against each component to edit machine details.

In case of Verification Manager, you can edit Verification Manager server port and proxy details, as shown below:

The default port for Verification Manager is 8080.

Here, the specified proxy URL can be used to access the Verification Manager.

In case of Checker Server, you can edit Checker Server port number on which Checker Server will be installed.

The default port for Checker Server is 9000.

In case of Database Server, you can edit ports for installing Database Server, Baton Cache, Baton Logger, Database Manager, and Baton Stash.

Note: When providing port numbers, ensure each service uses a unique port when installed on the same machine. Duplicate ports will cause installation errors.

8. Click OK.

9. Under Include add-ons, enable the checkbox for add-on installers, Baton LID or Baton Nielsen as required.

10.Click Validate.

BIM validates all the details provided for the BATON components.

If all the provided details are correct and valid, the Add Machine page appears with the Next button enabled. The component tiles will display a green hue, indicating successful validation, as shown below:

If the details are incorrect or validation fails, an error message appears: "Validation failed. Please edit the components marked with errors and re-validate." The Add Machine page will highlight the components with issues using a red hue, as shown below:

Use the edit icon against the corresponding component to provide the correct details and validate.

Once validated, the Next button appears.

11.From the bottom right corner, click Next.

The Pre-installation Checks page appears.

To move forward with the installation, refer Reviewing Pre-Installation Checklist.

Configuring Machine and Service Details for Cluster-wide Installation

In case of Cluster-wide Installation, you can add multiple machines for each component.

To configure machine and service details for cluster-wide installation of BATON, follow the steps mentioned below:

1. After navigating to Installation Type page, select Cluster-wide Installation option from the right pane.

2. Click Continue.

The Add Machine page appears, as shown below:

3. Click Add Machine button.

The Machine and Services Details pop-up appears, as shown below:

4. In the IP/Host Name field, enter the IP address or host name of the machine where you want to install

BATON.

5. In the Machine Credentials field, enter the username (which may include the domain name) and the password of a user account with administrative privileges on the Windows machine where BATON will be installed.

6. In the BATON Installation Folder field, provide the location where BATON will be installed.

Note: Currently, unicode characters are not supported in folder file paths for the installation of BATON.

7. Under Install Service(s) enable the checkboxes for Database Server, Verification Manager, and Checker Server, as required You can install BATON components across multiple machines. To do this, select the checkboxes for the components you want to install on the machine for which you’ve entered the details above.

Additionally, you can provide the details of a remote DB if you have a pre-installed DB. To know more, click here.

8. Under the Baton Service Log On section, in the Service Log On Credentials field, enter the login credentials of the user account using which BATON services will be run.

By default, services will run on LocalSystem account.

This field is optional.

9. Click Add.

The machine is added, and the enabled components will be installed on it.

Important: Use the Add Machine button to add multiple machines. This allows you to allocate specific components to individual machines. You can set up a cluster by distributing components across machines in different combinations, as shown below:

To know more about how to install BATON with various combinations, see Installing BATON in Different Configurations.

You can click icon against each service to edit port number and other details. To know more, click here. Additionally, you can click to remove the added component.

Note: When providing port numbers, ensure each service uses a unique port when installed on the same machine. Duplicate ports will cause installation errors.

10.Click Validate.

BIM validates all the details for installating the BATON components.

Once validated,the Next button appears.

11.From the bottom right corner, click Next.

The Pre-Installation Checks page appears.

To move forward with the installation, refer Reviewing Pre-Installation Checklist.

Installing BATON with Remote DB

While installing BATON in…