Additional Deployment Information

Here are some things to keep in mind:

• Private CA Environments: In private certificate authority (CA) environments, every TLS certificate a browser might accept must be validated. While the Haivision Helper certificate for *.apps-local.haivision.com is issued by a recognized root authority, it must be explicitly added as a trusted certificate to all browsers in such environments. Otherwise, users may be repeatedly prompted with "untrusted certificate" warnings, or Haivision Helper may simply fail to work.

• Firewalls: Haivision Helper and the application it launches (multicast agent, low-latency agent, or InStream) need to be able to communicate with the respective server. Your firewall should be configured to allow UDP traffic. This is because UDP video streams (unicast or multicast) represent incoming connections that must be allowed inbound to the client device. In the Windows firewall (and any other desktop firewall), incoming UDP packets are blocked by default. You should therefore setup the appropriate firewall rules, preferably with a GPO.
  • HMP: For the multicast agent, a firewall exception is required for live event multicast which uses a UDP port in the 41000–41199 range. (This port range is user-configurable. See the Multicast Port entry in Location Settings.)
  • Furnace: For Furnace IPTV, as long as all the streams are configured to use port 4900, it is sufficient to allow ports 4900 and 4901 from the source IP network. A firewall exception is required for live event multicast, which uses UDP port 32000. (This port is not user-configurable.)
• Anti-virus: Haivision Helper and the application it launches must be whitelisted by antivirus applications which may intercept their functions. If you are using Microsoft UAC, you may need to create an exception.

• Installer Options: The Haivision Helper .msi can be deployed using standard Microsoft installer options (see Microsoft Windows Installer Documentation). For example, you can use -quiet to have the installation take place in the background. You can also apply transforms to the properties of the Haivision Helper .msi file, which you can view by using an editor such as Microsoft Orca.

  

  Note

  Haivision does not recommend or support making changes to the .msi file itself.

• Installation Directory: The default Haivision Helper .msi installs to %LOCALAPPDATA%, and not to %PROGRAMFILES%. Therefore, deployment via GPO must be per user, not per machine. It may also be deployed with a script.