This guide covers the deployment of WINK virtual appliances in your environment. Each OVA file is pre-configured with your organization's license and MAC address - your responsibility is setting up the virtual machine and network connectivity.
Support Scope
WINK provides support for the WINK software and appliance functionality. Virtual machine deployment, hypervisor configuration, and infrastructure setup are the customer's responsibility. We do not provide support for VMware, Hyper-V, Proxmox, or other virtualization platforms - please contact your hypervisor vendor or IT team for platform-specific assistance.
Overview
Deploying a WINK virtual appliance is straightforward:
- Download your OVA file from the Client Portal
- Import the OVA into your hypervisor
- Allocate appropriate resources (CPU, memory, storage)
- Configure networking via the
wink-ttyconsole - Access web administration on port 444
For the step-by-step process, see the Getting Started Guide.
Pre-Licensed Appliances
Every OVA is Unique
Your OVA file is built specifically for your organization with:
- Pre-installed license (no activation required)
- Pre-assigned MAC address (registered with WINK licensing servers)
- Pre-configured for your deployment
The MAC address and license are hardcoded and cannot be changed. If you need additional appliances or replacement images, contact WINK support.
Resource Allocation
CPU Requirements
Video transcoding is CPU-intensive. Allocate resources based on your stream count:
| Resource | Recommendation |
|---|---|
| CPU Cores | 1 physical core per stream (for transcoding appliances) |
| Hyperthreading | Disable for resolutions above 720x480. Hyperthreading can cause frame timing issues at higher resolutions. |
| CPU Overcommit | Not recommended. Dedicated cores provide consistent transcoding performance. |
| Shared CPUs | Not recommended. Video transcoding requires predictable CPU availability. |
For detailed sizing calculations, see the Hardware Requirements Guide.
Memory Requirements
| Setting | Recommendation |
|---|---|
| Memory Allocation | Fully reserved - do not use dynamic memory |
| Memory Ballooning | Disable. Memory ballooning can cause stream interruptions. |
| Minimum RAM | See Hardware Requirements for per-product specifications |
Memory Ballooning
VMware, Hyper-V, and other hypervisors may enable memory ballooning by default. This feature reclaims unused memory from VMs and can cause video stream interruptions. Disable ballooning and reserve full memory allocation for WINK appliances.
Storage Requirements
| Storage Type | Notes |
|---|---|
| Local Storage (SSD) | Best performance for stream startup and service restarts |
| SAN / NAS | Acceptable. May add latency to stream startup and service restarts, but does not affect transcoding performance once streams are running. |
| Disk Size | Minimum 100GB for base installation. Additional space needed if recording locally. |
SAN/NAS Note
Running the system on networked storage is fine for most deployments. You may notice slightly longer startup times when services initialize or streams restart, but once streams are running, transcoding performance is unaffected by storage type.
Hypervisor Compatibility
WINK OVA files are compatible with standard virtualization platforms:
- VMware vSphere / ESXi 6.7+
- Microsoft Hyper-V
- Proxmox VE
- KVM / QEMU
- Oracle VirtualBox (testing only)
- Cloud platforms (AWS, Azure, GCP) with OVA import capability
Import the OVA using your platform's standard import process. Consult your hypervisor documentation for OVA import procedures.
MAC Address Preservation
Critical
The MAC address embedded in the OVA is tied to your WINK license. During import, ensure your hypervisor preserves the original MAC address. If the MAC address is changed, the appliance will not function.
Most hypervisors preserve MAC addresses during OVA import by default. If you need to manually configure the MAC address, refer to your appliance documentation in the Client Portal for the assigned address.
Network Configuration
After importing and powering on the VM:
- Open the VM console to access the
wink-ttyinterface - Configure static IP address, subnet mask, gateway, and DNS
- Save settings - the appliance will apply the network configuration
- Access web administration at
https://[IP]:444
The wink-tty console is for initial network setup only. All other configuration is done through the web interface.
Firewall Requirements
Before deploying, ensure your firewall is configured for WINK traffic. Key ports include:
| Port | Protocol | Purpose |
|---|---|---|
| 444 | TCP (HTTPS) | Web administration (required internally) |
| 443 | TCP (HTTPS) | HLS streaming / API access |
| 554 | TCP/UDP | RTSP streaming |
| 8554 | TCP | Alternative RTSP port |
For complete port requirements and network architecture options, see the Firewall & Network Configuration Guide.
Post-Deployment
Once your appliance is running and accessible via the web interface:
- WINK Forge: Configure camera inputs and transcoding - see WINK Forge Manual
- WINK Media Router: Configure stream distribution - see WINK Media Router Manual
Related Documentation
Getting Started Guide
Hardware Requirements
Firewall & Network Configuration
WINK Forge Manual
WINK Media Router Manual