3
3
Installation Planning
*
Software is being updated without any notice, so please keep in mind that some of the description may differ
from the actual software.
Network Readiness Assessment
The following paragraphs are a simplified readiness assessment sufficient for an OmniJoin Private 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 the Systems
Requirements document for more details regarding operating systems, browsers, mobile devices an
d
r
evision 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
env
ironment. In addition to the hardware and operating system revision levels stated in the Systems
Requirements Document, 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 configurations, your organization must
have, or be willing to install .Net 4.0 and 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 t
he
c
onferencing users and the server resources shown in the diagrams above will not see the performanc
e
i
mprovements normally provided by on-premise server installation. Such networks are NOT ready for privat
e
cloud deployments.
Access and control over firewalls, routers, and proxies. The installation of all server resources and the
es
tablishment 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
am
enable the private cloud environment. Customers without access to and control over firewalls, proxies
and
r
outers are not ready for private cloud deployment.
Ability to get static IP addresses. Private 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. Private 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
i
ntended (see diagram), than at least two domain names (see Host Domain Name Services in Installatio
n
s
ection of 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 private cloud installation.