Brother OmniJoin Installation guide

OmniJoin Hybrid Cloud

Installation and Planning

Guide

Version B

ENG

i

Legal Notice

Microsoft, Windows, Active Directory, ActiveX, Windows Server and Windows Vista are either registered

trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Intel and Intel Xeon are registered trademarks or trademarks of Intel Corporation in the United States and/or

other countries.

Any trade names and product names of companies appearing on Brother products, related documents and any

other materials are all trademarks or registered trademarks of those respective companies.

ii

W3C Software Notice and License

This work (and included software, documentation such as READMEs, or other related items) is being provided

by the copyright holders under the following license.

License

By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will

comply with the following terms and conditions.

Permission to copy, modify, and distribute this software and its documentation, with or without modification, for

any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies

of the software and documentation or portions thereof, including modifications:

The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.

Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, the W3C

Software Short Notice should be included (hypertext is preferred, text is permitted) within the body of any

redistributed or derivative code.

Notice of any changes or modifications to the files, including the date changes were made.

(We recommend you provide URIs to the location from which the code is derived.)

Disclaimers

THIS SOFTWARE AND DOCUMENTATION IS PROVIDED “AS IS,” AND COPYRIGHT HOLDERS MAKE NO

REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO,

WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE

USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS,

COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.

COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR

CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.

The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the

software without specific, written prior permission. Title to copyright in this software and any associated

documentation will at all times remain with copyright holders.

Notes

This version: http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231

This formulation of W3C’s notice and license became active on December 31 2002. This version removes the

copyright ownership notice such that this license can be used with materials other than those owned by the

W3C, reflects that ERCIM is now a host of the W3C, includes references to this specific dated version of the

license, and removes the ambiguous grant of “use”. Otherwise, this version is the same as the previous version

and is written so as to preserve the Free Software Foundation’s assessment of GPL compatibility and OSI’s

certification under the Open Source Definition.

iii

Table of Contents

1

Introduction 1

Target Users of This Guide ............................................................................................................................. 1

Related Documentation .................................................................................................................................. 1

Overview ......................................................................................................................................................... 1

2

Requirements 3

System Requirements ..................................................................................................................................... 3

Server Requirements ...................................................................................................................................... 3

Client Requirements ....................................................................................................................................... 7

Host Name Requirements............................................................................................................................... 8

Important Notes Regarding Host Names ................................................................................................ 9

3

Installation Planning 10

Network Readiness Assessment .................................................................................................................. 10

Installation Checklist ..................................................................................................................................... 11

Network Topology ......................................................................................................................................... 12

Network Planning – Determining the Best Server Locations ........................................................................ 16

Host Domain Name Services ........................................................................................................................ 16

Background ................................................................................................................................................... 17

Before Starting the Installation ...................................................................................................................... 18

Assumptions .......................................................................................................................................... 18

Example Settings ................................................................................................................................... 18

Settings to Determine in Advance ......................................................................................................... 19

DNS Settings ......................................................................................................................................... 19

Acquiring a Certificate............................................................................................................................ 20

External Use Configuration ........................................................................................................................... 27

Configure NAT to the APS and VCS ...................................................................................................... 27

Firewall NAT Mappings .......................................................................................................................... 28

IMPORTANT .......................................................................................................................................... 29

4

Installation 30

Setting Up the Configurator .......................................................................................................................... 30

Installing ........................................................................................................................................................ 31

Settings of VCS ............................................................................................................................................. 35

Verifying Basic Installation (IMPORTANT) .................................................................................................... 38

Troubleshooting ............................................................................................................................................ 39

Frequently Asked Questions (FAQs) ..................................................................................................... 39

Caveats ......................................................................................................................................................... 41

5

Deploying the Conferencing Client 42

Deploying OmniJoin Conferencing Client via Dynamic Load ....................................................................... 42

ClickOnce (Alternative Manual Installation) ........................................................................................... 42

Launcher (Alt. ActiveX

®

/ Add-on) .......................................................................................................... 43

Alternative... ActiveX

®

/ Add-on Installation ........................................................................................... 43

iv

Via Electronic Deployment (MSI) .................................................................................................................. 44

Methods of Deployment ......................................................................................................................... 44

Create a Distribution Point ..................................................................................................................... 44

Create a Group Policy Object ................................................................................................................ 44

Assign a MSI Package........................................................................................................................... 47

Publish a MSI Package ......................................................................................................................... 49

Redeploy a MSI Package ...................................................................................................................... 52

Remove a MSI Package ........................................................................................................................ 54

Other Methods .............................................................................................................................................. 56

6

Deploying the Live Contact List/OmniJoin IM

57

Via Electronic Deployment ............................................................................................................................ 57

7

Server Management 58

About Log Files ............................................................................................................................................. 58

What are the Hybrid Cloud Server Log Files? ....................................................................................... 58

WPC....................................................................................................................................................... 58

APS ........................................................................................................................................................ 59

VCS........................................................................................................................................................ 60

Keeping Backups .......................................................................................................................................... 61

Backup and Restore .............................................................................................................................. 61

Updating VCS ........................................................................................................................................ 62

8

Uninstalling 63

9

Special Topics 64

Special Considerations for Backup and Restore .......................................................................................... 64

Special Considerations for Single-Site, Hot Standby Facilities (Manual Cut Over, Not HA) ........................ 65

High Availability Systems and Redundancy .................................................................................................. 66

General Recommendations and Best Practices ........................................................................................... 66

General .................................................................................................................................................. 67

Best Practices ........................................................................................................................................ 67

IP Address Settings ....................................................................................................................................... 68

Setting 3 IP Addresses on One NIC ...................................................................................................... 68

Changing the number of room systems that can connect per conference (OmniJoin Interoperability Users

Only) .............................................................................................................................................................. 69

1

Introduction

1

1 Introduction

Target Users of This Guide

This guide has been written for readers with the basic knowledge of:



IT networking knowledge (i.e., capable of setting up ActiveDirectory

®

and DNS servers)



Certificates and public and private keys



OmniJoin license terms



OmniJoin products

Related Documentation

The complete OmniJoin Hybrid Cloud documentation set includes the PDF files listed below:

• Product brochure (varies by country)

• Systems Requirements Document

• Installation & Planning Guide (this document)

• Administrator’s Guide

These files are available via the OmniJoin public website and the administrator’s console download tab

(appears in the left navigation bar).

Overview

OmniJoin web and video conferencing provides a high-quality

online meeting experience including multipoint HD video,

synchronized wideband audio, and an extensive list of live

collaboration tools. These features support internal meetings,

training, sales, and a wide variety of specialty applications

including boardroom video conferencing, telemedicine,

distance learning, and more.

OmniJoin software and online services have been adopted in

financial services, healthcare, government, and many other security conscious environments. First and foremost,

OmniJoin was designed to meet IT manageability and security requirements.

OmniJoin uses a cloud-based architecture, and offers support for all three cloud deployment models: 1) public

online services; 2) hybrid deployments (this version); and, 3) private cloud. By offering support for all three cloud

deployment models, OmniJoin can easily provide immediate activation of free trials and near-zero-admin public

online services; plus hybrid and private deployment models for customers who require increasingly stringent

controls and high-performance network routing that can only be met with on-premise resources.

2

Introduction

1

OmniJoin Hybrid Cloud deployments

provide for customer on-premise installation

of virtual conference server (VCS), access

point server (APS), and web proxy cache

(WPC) content storage server software.

These network services can be installed on

one physical server, separate servers, or in

virtualized server environments as further

described below. The OmniJoin Hybrid

Cloud backend manages licensing, account

authentication, central process functions

and staging software updates.

In addition, the strategic placement of one

or more virtual conference servers (VCSs)

on the customer’s own network can provide

routing, bandwidth, and video conferencing

performance benefits not achievable using

the public cloud.

There are several components needed to

complete an OmniJoin Hybrid Cloud

installation, including on-premise servers

and the OmniJoin backend, which is the

managed by the OmniJoin team in our

secure datacenter. Here is an overview of

the major server components:



The OmniJoin backend (managed by Brother)

As an OmniJoin administrator, you will need an OmniJoin administrative account and login credentials.



The Access Point Server (APS) – the server component for the Live Contact List/OmniJoin IM and

presence application for Windows

®

(optional). It allows users to:

• Manage and enter meetings without using their web browser

• View other users’ status in their Live Contact List/OmniJoin IM (similar to an address list)

• Send meeting invites



The Virtual Conferencing Server (VCS) – required

The VCS is the central point where active meetings are hosted. Users who join meetings connect

directly to a VCS.



The Web Proxy Cache (WPC) Server – required

The WPC handles all content caching and storage, including web portal pages. The WPC server is

bound to the Web Portal Host Name.

The three OmniJoin server components (APS, VCS and WPC) are available in the same setup program.

The server administrator decides which component to install when the installation starts.

The administrator can decide to install three components on the same physical server or split the OmniJoin

servers onto separate Windows

®

servers.

This is one of many possible configurations. In this example

the APS, VCS, and WPC are installed on three separate

servers at one location behind a firewall. Both “internal” and

“external” conference participants are supported.

3

2

2 Requirements

System Requirements

The paragraphs and tables below refer to physical installations. Customers with virtualized data centers should

interpret the requirements below as meaning immediate availability of such physical resources. It should be

noted that conference link resolution (to physical VCS server) and portal page response times are directly

related to DNS, IIS, and SQL response times; and a good, high-quality VoIP and video conferencing experience

is dependent on bandwidth to and from the VCS, and VCS processor and memory availability. For these

reasons, some customers may opt for a virtualized environment for all servers except VCSs.

NOTE

Customers with virtualized environments must possess advanced technical capabilities to bind separate

static IP addresses, server certificates, host/domain names (DNS entries), network connections, and IO

ports to separate, individual virtual machines.

Server Requirements

OmniJoin Hybrid Cloud systems requirements for server resources

 Windows Server

®

operating system requirements

 Windows Server

®

2012 or later, 64-bit

 Server must NOT be a Windows Domain Controller

NOTE

See also port binding requirements below.

 .Net Framework 4.0 & later

 Microsoft Office 2013 is required on the VCS for sharing MS Office documents, 32 bit

NOTE

For VCS only, this is for Word, Excel, and PowerPoint document conversion and sharing.

 See chart below for minimum hardware requirements (APS, VCS, WPC)

4

Requirements

2

SERVER H/W

APS

VCS

WPC

APS, VCS, WPC all on

one physical server

The table below refers to physical servers. Customers with virtualized data centers should interpret the

requirements below as meaning immediate availability of such physical resources.

SMALLMinimum

hardware

requirements.

Intended for trial

evaluation and up to

50 users.

Intel

®

Xeon

®

quad-core

processor at

2.0+ GHz, 4

GB RAM

available to

this service,

8 GB of

available

hard disk

space

Intel

®

Xeon

®

quad-core

processor at

2.0+ GHz, 4 GB

RAM available to

this service, 8

GB of available

hard disk space

Intel

®

Xeon

®

quad-

core processor at 2.0+

GHz, 4 GB RAM

available to this

service, 8 GB of

available hard disk

space AND at least

500 GB of available

storage capacity for

content (can be direct-

attached storage,

DAS, or Microsoft

UNC network path to

NAS or SAN)

Intel

®

Xeon

®

quad-core

processor at 2.0+

GHz, 4 GB RAM

available for OmniJoin

APS, VCS, and WPC

services, 8 GB of

available hard disk

space AND at least

500 GB of available

storage capacity for

content, can be direct-

attached storage

(DAS), or Microsoft

UNC network path to

NAS or SAN

MEDIUM

Minimum server for

up to 200 concurrent

conferencing users

(and 4,000 LCL

users).

Intel

®

Xeon

®

quad-core

processor at

2.0+ GHz,

16 GB RAM

available to

this service,

8 GB of

available

hard disk

space

Dual Intel

®

Xeon

®

quad-core

processor at

2.0+ GHz or

better, 16 GB

RAM available to

this service, 8

GB of available

hard disk space

Dual Intel

®

Xeon

®

quad-core processor

at 2.0+ GHz, 8 GB

RAM available to this

service, 16 GB system

hard disk space AND

at least 2 TB of

available storage

capacity for content

(can be direct-

attached storage,

DAS, or Microsoft

UNC network path to

NAS or SAN)

Dual Intel

®

Xeon

®

quad-core processor at

2.0+ GHz or better, 16

GB RAM available for

OmniJoin APS, VCS

and WPC services, 8

GB system hard disk

space AND at least 2

TB of available storage

capacity for content,

can be direct-attached

storage (DAS) or

Microsoft UNC network

path to NAS or SAN

SMALL with

INTEROPERABILITY

Minimum hardware

requirements for

server running VCS

and room systems

interoperability

software.

n/a

Dual Intel

®

Xeon

®

quad-core

processor at

2.0+ GHz or

better, 16 GB

RAM available to

this service, 8

GB of available

hard disk space

n/a

INTEROPERABILITY

Medium and Large

n/a

CONTACT US

It is not possible

to publish

guidelines. See

detailed note

below.

n/a

5

Requirements

2

NOTE

This chart is intended to communicate MINIMUMS and provide general guidelines. Your specific scenario

and server sizing requirements may vary depending on number of simultaneous conferences, video

participants, video resolution (e.g., HD video, floating videos), desktop sharing, media file sharing, and

other features used. Backend load is generally light; VCS load should be monitored carefully. Please

contact OmniJoin technical support services for more specific recommendations.

 Ports

Required Ports Recommended Ports

WPC 80, 443

APS 80, 443

VCS 80, 443 22, 23, 1270

Note: assigned ports must be bound to the OmniJoin service and

cannot be shared

 1 standard internal Ethernet network interface card (NIC) required, 2 redundant Ethernet NICs

recommended

NOTE

USB to Ethernet, Wi-Fi, and connection types other than standard internal Ethernet NICs are NOT

supported at the server

6

Requirements

2

 Adequate symmetric bandwidth at each server, 100 Mbps and above recommended

 Host / Domain Name Services (DNS) resolution

 Administrative access to internal domain controller is required

 Administrative access to customer’s public DNS may be required

 OmniJoin Private Cloud requires DNS host records for the WPC, APS and VCS servers in the

customer DNS system. In certain situations, these DNS records will reside on an internal DNS

server to resolve host/domain names for internal users and on an external DNS server for

resolving host/domain names for external users.

 For a more complete discussion of DNS requirements including the public or private host/domain

name for each server, please refer to the Host Name Requirements in this guide

 Static IP address for all server resources

 Each service (APS, VCS, WPC) requires a static IP address

 IP addresses can be mapped or “forwarded”, but must be static

 Network topology (see diagram above)

 Internet access to OmniJoin Hybrid Cloud backend

 Network access for internal conference participants to all server resources (APS, VCS, WPC);

see also Network Topology in this guide

 Network access for external conference participants, if any, to all server resources (APS, VCS,

WPC); see also Network Topology in this guide

 TLS security certificates

 Security certificates issued by a recognized Certificate Authority are required for each server

hosting an OmniJoin service

 Customers may use OmniJoin self-signed, automatically generated certificates. This is

recommended for quick bench tests only, otherwise network users may receive browser

security warnings after clicking Hybrid Cloud conference URLs. Please note:

• Self-signed certificates do NOT work for Apple OS X and iOS clients

• Self-signed certificates are increasingly rejected by browser vendors

 Customers may use wildcard certificates, for example *.somedomain.com

 Customers may use separate certificates for internally accessible cloud resources versus

externally accessible resources. For example internal.somedomain.com and

external.somedomain.com

 Customers may use Subject Alternative Name (SAN) certificates

 See Network Topology for scenarios where these options may apply

 Directory services

 Optional, for directory integration (ADS) and/or single sign-on (SSO) implementation

 Customer must have access to directory service administration sufficient to add and edit a

directory service group for OmniJoin

 Clock settings

 SSO implementation (SAML 2.0) requires accurate date, time, and time zone clock settings

(at WPC server)

7

Requirements

2

Client Requirements

OmniJoin desktop and laptop client requirements

NOTE

The client systems requirements listed below are identical to OmniJoin public online services.

 Windows

 Windows 7

®

and later

 Minimum hardware required: Core 2 Quad, Intel i3, i5 or i7 equivalent; 4 GB RAM; 100 MB free

disk space

 Web browsers

• Internet Explorer

®

11.0 or later

• Mozilla Firefox (note Firefox is self-updating)

• Google Chrome™ (note Chrome is self-updating)

 Microsoft

®

DirectX

®

11 or later (for audio/video peripherals and media processing)

 Audio and video peripherals

• Most Windows

®

selectable audio and video devices, including USB 2.0+ and PCI

adapter card inputs

 OS X

 OS X 10.10 or later

 Minimum hardware required: Core 2 Duo equivalent or later; 4 GB RAM; 200 MB free disk space

 Web browsers

• Safari

• Mozilla Firefox (note Firefox is self-updating)

• Google Chrome™ (note Chrome is self-updating)

 Audio and video peripherals

• Most Apple built-in audio/video devices

 Minimum client bandwidth availability (for desktops and laptops only, see above for mobile)

 For hosts or presenters: High-speed broadband Internet access (minimum 1 Mbps upstream /

4 Mbps downstream)

 High-speed broadband Internet access (minimum 512 Kbps upstream / 4 Mbps downstream)

Network access to hybrid cloud resources – all client components must have DNS resolution (described above)

and routing access to all OmniJoin Hybrid Cloud resources installed on the customer’s network (APS, VCS,

and WPC servers). Customer IT contacts must have network infrastructure access sufficient to implement

IP address, NAT-port forwarding (NAT-PMP), and possibly proxy settings as required for users to access

servers behind the firewall.

8

Requirements

2

Host Name Requirements

OmniJoin Hybrid Cloud requires one internal zone and the following public and private host names as listed

below:



WPC / Web Portal Host Name – OmniJoin Hybrid Cloud requires a Web Portal Host Name that

resolves to the WPC server. Examples of valid host/domain names are WPC.XYZcorp.com,

Meetings.XYZcorp.com, and OmniJoin.XYZcorp.com. Of course the latter two are much easier for

network users to remember. This is an important planning and install-time decision because the

host/domain name is used for your web portal including login page, all portal pages, and most

importantly conference links (URLs). The Web Portal Host Name must resolve to the WPC server IP

address. The Web Portal Host Name must match the SSL certificate bound to that address. The Web

Portal Host Name may be registered as a public or private host/domain name – if private, logins, portal

page access, and conference link resolution will fail for all uses outside the customer’s private network.



VCS Host Names – If external online meeting participants are required, then this is a public host name(s)

otherwise it is private – The VCS host name must resolve to the VCS server IP address. The VCS Host

Name must match the SSL certificate bound to that address. The VCS Host Name is required for join

conference links to function.



APS Host Names – If external Live Contact List / OmniJoin IM users are required, then these are public

host names, otherwise private. The APS host name, which is used by the OmniJoin Live Contact List /

OmniJoin IM, must:

• Resolve to the APS server IP address.

• Match the SSL certificate bound to that address.

9

Requirements

2

Important Notes Regarding Host Names

Note there is only one “Web Portal Host Name” per deployment. VCS and APS host names are associated with

each individual server. All the host names above must be unique, including host names for individual VCS and

APS servers.

DNS / IP Address / Server Mapping Summary

APS

VCS

WPC

Live Contact List / OmniJoin IM

Route

—

Route, DNS

Conferencing clients

—

Route, DNS

Web browsers (portal access)

—

Route, DNS

Storage applet

—

Route, DNS

Host/Domain Name

Type

IP Address

Open Ports

Summary Description

Web Portal Host Name

(e.g., Conferencing.Xyz.com)

PUBLIC

Static

80, 443

Maps to the primary WPC

Server.

VCS Host Names

(e.g., VCS.Xyz.com)

*Public or

private

(see

details

above)

Static

80, 443 required,

22, 23, 1270,

37000

recommended

Maps to one or more VCSs

proxy settings as required,

the host/domain name must

resolve publicly if external

conference participants are

planned.

APS Host Names

(e.g., APS.Xyz.com)

*Public or

private

(see

details

above)

Static

80, 443

Maps to one or more APSs

proxy settings as required

, the

host/domain name must

resolve publicly if external

Live Contact List / OmniJoin

IM users are planned.

Note: assigned ports must be bound to the OmniJoin service and cannot be shared.

Planning Guide for Your Installation:

Host/Domain Name

Type *

IP Address

Planning Notes

Web Portal Host Name:

VCS Host Name:

APS Host Name:

* Public or private. Note all these resources must be accessible by ALL users including your network users and

their online meeting attendees. Most customers register all these resources as publicly resolvable host/domain

names.

10

3

3 Installation Planning

*Software is being updated without any notice; some descriptions may differ from those included in the actual

software.

Network Readiness Assessment

The following paragraphs are a simplified readiness assessment sufficient for an OmniJoin Hybrid Cloud

installation at a single location. It is recommended that customers considering a multi-site installation contact

OmniJoin technical support services for a more in-depth readiness assessment, capacity planning, and

determining best server locations.



Client operating environment. OmniJoin client agents require Windows

®

. Please refer to System

Requirements for more details regarding operating systems, browsers, mobile devices and revision

levels.



Familiarity with client-side network access, proxy settings, browser security settings, application loaders,

user access rights, and so on.



Server operating environment. OmniJoin server components require a Windows Server

®

operating

environment. In addition to the hardware and operating system revision levels stated in System

Requirements, successful installation requires administrator-level access for software installation.



Administrator rights for software installation.



Experience acquiring and installing customer SSL security certificates.



Ability to set and bind static IP addresses and ports to specific services.



Microsoft

®

.Net readiness. The on-premise components as shown in the architectural overview at the

beginning of this Planning Guide are .Net-based server software resources. For hybrid configurations,

your organization must have, or be willing to install, .Net 4.0 or later.



Bandwidth. Providing web and video conferencing services on one’s own network requires adequate

bandwidth. In particular, it is recommended the VCS have at least 100 Mbps bandwidth.



Network reliability. In addition to bandwidth, uninterrupted connections are generally required for

successful video conferencing. In general, higher network reliability and fewer interrupted connections

means better network readiness. Customers familiar with QoS controls can often further improve and

refine their conferencing performance. Customers with Wi-Fi to desktops, saturated Internet access,

devices and services that intentionally interrupt connections on a timed basis, and otherwise impeded

network routes between the conferencing users and the server resources shown in the diagrams above

will not see the performance improvements normally provided by on-premise server installation. Such

networks are NOT ready for hybrid cloud deployments.



Access and control over firewalls, routers, and proxies. The installation of all server resources and

the establishment of the network routes as shown in the architecture diagram above requires customer

contacts that are familiar with ports, NAT port mapping (NAT-PMP), firewall settings, proxy settings, and

general network routing topics. The faster and easier various settings can be reviewed, approved, and

set, the more amenable the hybrid cloud environment. Customers without access to and control over

firewalls, proxies and routers are not ready for hybrid cloud deployment.



Ability to get static IP addresses. Hybrid cloud deployments require static IP addresses for all server

resources. Certain host/domain names require publicly routable IP addresses (see below).



Expertise with DNS resolution and direct access to one’s own Domain Controller. Hybrid cloud

deployments require an understanding of private and public host/domain name resolution and

administrator access to one’s own domain controller. In particular, an understanding of fully qualified

name resolution as required for internal users and, optionally, external users, is essential. It should be

noted that if external conference participants are intended (see diagram), than at least two domain

names (see Host Domain Name Services in this guide) must resolve via the public Internet. Customers

without full-time staff familiar with DNS topics, IP addresses, and network routing should not attempt

hybrid cloud installation.

11

3

Installation Planning

Installation Checklist

In addition to the staff contacts, network expertise, and physical network readiness is good, the following

specific items are also required. It is recommended that the preparation phase of hybrid cloud deployment

include rounding up all the items below:



Completed deployment plan



Capacity plan (for over 50 concurrent users) including server sizing (small, medium or large)



Network topology diagram illustrating server placement



Completed table with host name, IP address and ports (see Installation)



Physical or virtualized server resources ready



Administrator access on all required servers for server software installation, SSL certificate installation,

and IP address and port bindings



Custody of desired customer SSL certificate (can use self-signed certificates for bench testing)

NOTE

If you need to purchase a specific certificate, the installation may be time-consuming for some customers.



Administrator access to firewalls for NAT port mapping rules (NAT-PMP)



Administrator access to internal and external DNS server to register private host names and,

if separately managed, access to customer’s method for registering public host/domain names



[Optional, for directory integration and SSO implementation] Administrator access to internal directory

service (ADS)

12

3

Installation Planning

Network Topology

In this section we explore various hybrid cloud deployment configurations and how they map to various

customer network topologies. The simplified diagrams on the following pages are intended to conceptually

illustrate server placement, routing, Internet access, and host/domain name resolution requirements for each

scenario.

Note the generalizations that apply to all hybrid cloud scenarios below:



Server-to-OmniJoin backend communications. In all cases, the server resources must have Internet

access and routing sufficient to connect to the OmniJoin Hybrid Cloud backend (for license and

account validation, software update staging, invite-email services, and so on).



Online meeting participant-to-server routing and domain name resolution. The Web Portal Host Name

must resolve to to the appropriate IP address for all intended participants including your network users

and their attendees. Of course, once DNS returns the correct IP address, it must be routable for all

desired internal and external (if any) online meeting participants.



In addition to routing and DNS resolution requirements for internal and external participants, server-to-

server communications require successful routing and DNS resolution services between each other

(in particular, using the OmniJoin.Dedicated host name). Note that this requirement becomes more

important when planning advanced, multi-site and HA configurations.

Typical Installation – Single Site, Single Server

13

3

Installation Planning

Typical Installation – Single Site, Multiple Servers (Adds Capacity)

This is also a very typical installation. This setup can handle more users and heavier conference loads than a

single physical server. Details shown previously are omitted here for simplicity.

14

3

Installation Planning

Advanced Scenarios – Single Data Center, More Servers

This is also a very typical installation. This setup can handle more users and heavier conference loads than a

single physical server.

15

3

Installation Planning

Advanced Scenarios – Single Data Center, But Located at a 3rd-Party Hosting Facility

This configuration may also be useful for large customer organizations that already have a major hosted data

center location. The benefit of this configuration is the use of a contract hosted data center that may have more

sophisticated physical and environmental controls than the customer’s own locations.

Depending on application, there may be bandwidth and performance benefits too, especially for interrupted

operations or lots of external participants.

Page is loading ...

Brother OmniJoin Installation guide

Brother OmniJoin Installation guide

Related papers

Other documents