Faronics Insight - Manual (Page 10)

Faronics Insight User Guide
10
|
Installing Faronics Insight
Planning the Installation
Before installing Faronics Insight, review the following requirements and ensure your network
and computers are running smoothly. Doing so will prevent problems during installation.
In most cases, the Insight software running on a computer is referred to as the Teacher or Student
(uppercase), as opposed to the users-the actual teachers and students (lowercase) or their general
devices.
Consider these issues before beginning installation:
Determine Insight architecture for your enviroment
There is a new, optional method to install Faronics Insight called the Insight Connection Server.
The Insight Connection Server is based on a client-server architecture, where the traditional
Insight install is based on a peer-to-peer architecture. The Insight Connection Server will reduce
the need for configuration changes to routers and wireless access points to support wired/wireless
environments and VLANs.
The existing peer-to-peer architecture will still exist and in many instances may still be the
preferred method to install Insight.
Faronics will also support a hybrid environment of both peer-to-peer and client-server
architectures.
Before installing, you will need to think about which architecture will be best for your
organization. Here are some things to think about when making your decision.
Peer-to-Peer
Pros
• Simple, quick install to teachers and students, no server is required
• Uses less network traffic
• No configuration changes if your labs are all the same subnet
• Perfect for single classroom or small schools
• Scalable for large districts as long as you can make networking changes to allow Multicast or
• Directed Broadcast
• Redundancy is built into the architecture, there is no single point of failure (server)
Cons
• Traffic does not cross subnets without router, wireless access point modification
• If your wired and wireless networks are not connected, you must make configuration changes
to allow broadcast/multicast packets to traverse both networks