Support · Appliance

MediaCaster Appliance — VMware Deployment Guide

Deploying the MediaCaster virtual appliance on VMware — what differs from the CastEdge guide, VM sizing, and first login.

For customer it

Specific to your organisation. Your copy in the onboarding bundle names your organisation and your deployment contact. See your onboarding bundle, or contact us.

Image version: 2026.11.11

Current release: mediacaster-appliance-2026.11.11.ova — SHA-256 shown on the download portal next to the file.


1. What this covers

MediaCaster is a virtual appliance that turns your video sources (multicast channels from your headend, slideshows and web pages) into multicast channels for your IPTV set-top boxes.

You deploy it the same way as the CastEdge appliance. Follow the CastEdge VMware Deployment Guide for importing the OVA and attaching the configuration, with the differences listed here:

  • Sizing: MediaCaster needs a larger VM (section 2).
  • Network: no secure tunnel and no Stage 2. The appliance needs only outbound HTTPS 443 (section 3).
  • First login: MediaCaster has its own web console, with an administrator password that is shown once (section 5).
  • File names: your bundle's configuration files are <customer>-mediacaster-userdata.yaml and <customer>-mediacaster-seed.iso. Wherever the CastEdge guide says <customer>-userdata.yaml or <customer>-seed.iso, use these.

2. What you need (requirements)

Everything in section 2 of the CastEdge guide applies, except for:

ItemRequirement
CPUA 64-bit Intel or AMD processor from 2009 or newer (one that supports SSE4.2: Intel Nehalem or newer, AMD Bulldozer or newer). The appliance does not need AVX2. Encoding and decoding video is CPU-heavy, so core count and speed decide how many channels it carries; see VM sizing. In Proxmox/KVM, set the CPU type to host or x86-64-v2-AES or later, not kvm64 or qemu64.
VM sizingMinimum 4 vCPU / 8 GB RAM. Give it more CPU and memory if the host allows. Your headend channels are a mix of AVC (H.264) and HEVC (H.265). Decoding HEVC is CPU-heavy, and every multicast input holds its own buffer in memory.
DiskTwice the content you plan to upload, plus 30 GB; for example 250 GB for up to 100 GB of video, slides and web pages. The OVA's disk is 40 GB; enlarge it in Edit Settings before first power-on, and the appliance grows into it on first boot. Every software update first copies your uploaded content as a safety snapshot, so the disk needs room for it twice. Thin provisioning is fine: the datastore only holds what is written.
The OVAImports at 4 vCPU / 8 GB already. Keep that, or raise it, before first power-on. Only the QCOW2 image (for Proxmox/KVM) starts at a lower 2 vCPU / 4 GB; raise it to at least 4 vCPU / 8 GB before first power-on.
NetworkNetwork adapter 1: the segment that carries your headend multicast and reaches your set-top boxes, your operators' browsers and the internet (outbound 443). It must pass IGMP, so the appliance can join headend channels. Network adapter 2 is for audio-over-IP, which a video-only deployment doesn't use. Remove it in Edit Settings before first power-on. A static address is applied to the appliance's network adapter, and with two adapters present it can't tell which one you mean.

3. Network prerequisites

DirectionProtocol / PortDestinationPurpose
OutboundTCP 443*.mediacast.appHTTPS to the Mediacast control plane
OutboundTCP 443*.s3.us-east-1.amazonaws.comSoftware updates (see the S3 note in the CastEdge guide)
OutboundUDP/TCP 53, 123Your DNS / NTP serversName resolution, time sync
InboundUDP (multicast)From your headendSource channels the appliance subscribes to
OutboundUDP (multicast)To your set-top boxesThe channels MediaCaster produces (MPEG-TS)
InboundTCP 8443 (HTTPS), 8080From your operators' workstations onlyMediaCaster web console; 8080 redirects to 8443

There is no UDP 51820 secure-tunnel rule: MediaCaster has no Stage 2. The CastEdge guide's web-gateway / TLS-inspection note applies unchanged. So does its "Mediacast support access" section: the appliance has the same key-only mcops support account, and no password login for it.

4. Deploy — step by step

Follow section 4 of the CastEdge guide (4A for vCenter, 4B for a standalone ESXi host). There are two extra checks before you power on:

  1. CPU, memory and disk: Edit Settings shows at least 4 vCPU and 8 GB, and the disk sized as in section 2.
  2. Network adapter 2: removed.

On vCenter (4A step 2), the OVA already includes the Cloud-init userdata property under vApp Options → Properties, so you don't need to add it. Edit it and paste the entire contents of <customer>-mediacaster-userdata.yaml.

On a standalone ESXi host (4B), the deploy wizard's Additional settings page shows four Cloud-init fields. They are single-line, so a pasted file loses its line breaks: either leave them empty, or paste the base64-encoded file and enter base64 in the matching encoding field. On this path always attach the seed ISO as well (4B step 3). It is what the appliance reads on a standalone host.

Static address. If the appliance needs a fixed address rather than DHCP, tell Mediacast the address, prefix, gateway and DNS servers before the kit is built. The address travels in the seed ISO (and, on vCenter, in the Cloud-init network config property).

The rule that matters most is the same: attach the configuration before first power-on.

5. First login

The web console is at https://<appliance IP>:8443. Sign in as user admin.

The appliance creates the admin password itself on first start. It prints it once, to the system journal, under the heading FIRST-RUN ADMIN ACCOUNT CREATED, and never shows it again. Reading the journal needs the support account, so Mediacast reads it with your administrator during the turn-up session.

The password goes straight into your organisation's password manager. Don't put it in email, chat, a ticket or a screenshot. Then:

  1. Sign in with it to confirm it works.
  2. Recommended: change it under Settings to a password your password manager generates, and update the entry. The original stays in the appliance's journal until the journal rotates it out. Changing it means that copy no longer works.

If the password is lost, the only reset clears the appliance's database, which also deletes its streams and playlists. Contact Mediacast before you try this.

6. How you'll know it worked

  • Mediacast confirms the appliance's first check-in, usually within minutes of power-on.
  • First login works (section 5).
  • A test channel plays: a headend channel, passed through MediaCaster, plays on a set-top box (or in VLC) on your network.

If Mediacast hasn't confirmed within about 10 minutes, see section 5 of the CastEdge guide.

7. Support

Specific to your organisation. Your deployment support contact is named in your onboarding bundle. See your onboarding bundle, or contact us.

After the appliance is confirmed running, delete local copies of the configuration files (.yaml and .iso) from any workstation that touched them.