Zoom stores Hub configuration settings to connect with a Hub Server. These configuration values should be added to Zoom before installing the Hub Server. If these Hub configuration values in Zoom are updated after installing and starting the Hub Server, then restart the Hub after you have finished updating these values. Log in to the
Hub Configuration in Zoom Read More »
Several Zoom services depend on shared storage provided by a NAS or SAN in order to process files across multiple machines or Zoom services. The permissions (read/write/delete) on files or folders on these shared storage devices need to be setup to ensure requirements listed below are met for various deployment configurations for Zoom: Terminology Term
Permissions with shared storage (NAS/SAN) Read More »
Archiving is an optional feature that is available with an appropriate license. You can check your license information in Zoom’s Web Management Console. To check the license information, log on to your Web Management Console, for example, http://MyZoomServer:8443/ Open the License Management node under the System node in the Admin Menu sidebar. Click License Information
Checking Archive license Read More »
When the Archive Module is included as a part of the Zoom license, Zoom can be set up to archive assets to a single designated archive location using its internal Basic Archive Module. This folder location must exist on the Zoom MAM server in order for the configuration to work. Enable and set up the
Basic Archive Settings Read More »
As of Zoom 7.3, it is possible to automatically receive updates from the LDAP Server regarding the changes in existing user accounts as well as the addition of new users. In order to do this, you need to specify Auto Pull Frequency in the LDAP Server Settings inside the Web Management Console. Follow these steps:
Automatic Pull-Users from LDAP Server Read More »
Context Evolphin Managed Cloud-based Zoom Servers can technically be accessed from anywhere in the world. Without strict firewall settings, a user from any IP address can run the Zoom desktop apps or Web Client and access the cloud-based Zoom or Preview Servers. To protect against malicious users, by default, Evolphin locks down the Zoom server
Using Evolphin Managed VPN with Evolphin Managed Cloud based Zoom Servers Read More »
A new feature for Auto-Retirement has been introduced from Zoom 7.3 onwards, which allows Zoom admins to set up rules to determine which assets are automatically retired. This post outlines how the feature works and then shows how to configure it on your Zoom setup. Auto-retirement offers a mechanism by which assets can be identified
Setting up Auto-Retirement Policy Read More »
Rule without path restrictions What if I define a rule without restricting it to a certain Zoom path? If a rule has no path defined, then the rule implicitly applies to all the assets in the repository. While it may have been your intention to define an umbrella policy for all your assets, please make
Auto-Retirement FAQs Read More »
Zoom allows restrictions to be imposed on numbers of characters allowed in a string type metadata field at the time of ingest and during manual update. Follow these steps to apply this restriction: Log into the Web Management Console at http://[YourZoomServer]:8443 using your preferred web browser. Open Server Control Panel page from the left sidebar.
Maximum characters in a metadata field Read More »
Data Lifecycle Management in Zoom From 7.3 onwards, Zoom offers a more sophisticated data lifecycle management (DLM) experience. On the data ingestion side, the more tightly integrated VideoFX and VideoLX modules have become much easier to set up as well as pack more powerful new features like support for image sequences, etc. Post ingestion, the
Hierarchical Archive and the Job Hub Read More »
Zoom Hierarchical Archive Flow In Zoom 7.6.2, there are some changes in this module. Check this article for details. In the Asset Browser or Web Asset Browser, select one or more assets to be archived (Tier 0 to Tier 1) and select Archive from the Action menu. You could also right-click on the selected assets
Hierarchical Archive in action Read More »
Locale for Curator Server Follow these steps to set up Curator Server to use the new locale: Open wrapper.conf for editing from the conf folder inside your Zoom installation folder (Windows: [ZoomInstallDir]\conf and Linux: [ZoomInstallDir]/conf). Locate the line with the highest n for wrapper.java.additional.n in the file. Add 2 new lines for wrapper.java.additional increasing the value of
Locale setup for Curator Server Read More »
Locale for Preview Server Follow these steps to set up Preview Server to use the new locale: Open wrapper.conf for editing from the conf folder inside your Zoom installation folder (Windows: [ZoomInstallDir]\conf and Linux: [ZoomInstallDir]/conf). Locate the line with the highest n for wrapper.java.additional.n in the file. Add 2 new lines for wrapper.java.additional increasing the value of
Locale setup for Preview Server Read More »
From Zoom 7.3.1 onwards, new locales are supported in Zoom for use by all desktop and web-based Zoom Clients. To use these locales effectively with a Zoom Client, these should also be set up on all servers within Zoom, the Zoom MAM Server, Preview Servers, Curator Servers, and any HADR peers. Follow these steps on
Locale setup on servers Read More »
From Zoom 7.3 onwards, you can conveniently save or update one or more Zoom properties at a single place on the Zoom Server using the Web Management Console. These properties could be for use by the Zoom Server or one or more Zoom Clients. For a simple Zoom setup that does not use locations (as
Server Zoom Properties Read More »
Curator configuration in Zoom 7.3 is simpler and quicker, without having to edit any XML files or installing any services manually. All required services are installed with the Zoom Server installer and then the rest of Curator configuration is done using the Web Management Console only. Curator setup after Zoom upgrade to 7.3 You need
Curator Configuration (Zoom 7.3+) Read More »
VideoLX 3.0 is Evolphin’s lightweight proxy-based asset management module that lets Zoom users manage, store, and access high-resolution media files that are saved on high-speed bulk storage outside the Zoom repository. It is an upgrade to the previous VideoLX 2.0 with support for transcoding image and audio files, custom transcoding for different file types, location-based
Getting started with Zoom VideoLX 3.0 (Zoom 7.3+) Read More »
After Video LX 3.0 (Zoom 7.3+) has been set up as specified here, all check-ins to the Zoom repository will be screened for high-res assets. On a Zoom Client machine that is configured for a location set up for VideoLX, whenever a video asset is checked-in, it is compared against the ingest criteria as specified
VideoLX 3.0 in action Read More »
The Hub has a dashboard to track and monitor archive/restore jobs and it is accessed from Zoom’s Web Management Console. If you have installed Hub for AI, then the Hub Dashboard should be accessed as http://[HubServerIP]:8282/index.html. Check for more details. After your Hub is set up and all archiving parameters defined, you can view
Once all the setup for VideoFX 2.0 (Zoom 7.3+) is complete as described here, we are ready to see VideoFX 2.0 flow in action. A typical VideoFX 2.0 flow starts from the source file on the Client machine and ends on the low-res proxy checked-in to the Zoom MAM Server. Check here to see the
VideoFX 2.0 in action Read More »
