OS and Device
- Windows 7, Windows 8, Windows 8.1, Windows 10
- 32- and 64-bit supported
- English/US or English/Australian Localization
- Minimum 512 MB RAM 32-bit or 2 GB RAM 64-bit
- Minimum resolution 1024×600 and 96 DPI (100%) or 120 DPI (125%)
- Client virtualization platforms supported: VMware View, VMware Fusion
Note: We currently support IE 9+, Chrome, Firefox, and Edge browsers on student devices when using Filter URLs feature. Teachers are encouraged to use Application Blocking to allow one of these browsers.
- Use this wizard-based prerequisite guide
- Client prerequisites are the same as with 5.6 or 5.7 except if doing an upgrade
- Prerequisites must be installed manually since 5.8 is only MSI (no EXE)
OS for Local Server (if not using our ASP)
- Microsoft Windows Server 2008, 2008 R2, 2012 R2
- 64-bit supported
- English/US or English/Australian Localization
- Microsoft .NET Framework 3.5 SP1
- Internet Information Server
- Server virtualization platforms supported: VMware, Citrix, Hyper-V
- Port 443 must be open for outbound traffic in order to autoupdate clients
Database for Local Server (if not using our ASP)
- Microsoft SQL Server 2008, 2008 R2, 2012, 2014
- 64-bit supported
- Workgroup, Standard, or Enterprise Edition (Processor license recommended)
- English/US or English/Australia Localization
Windows Application Server Recommendations
The DyKnow Application Component is currently supported by most editions of Windows Server, but Standard, Enterprise or Datacenter Editions are recommended. If installation needs grow, and more RAM is required, server administrators may find it necessary to use a 64-bit edition of Server OS.
NOTE: The DyKnow Application Server does not support the use of self-signed SSL certificates.
Application Server Installation Logistics
DyKnow Application Server: DyKnow installs to the Default Web Site on IIS; therefore, exclusive installation of the DyKnow Application Server on IIS is recommended due to unknown configuration changes other Web applications may cause to IIS. DyKnow does not support or guarantee the DyKnow Application Server will work in IIS with multiple Web applications.
DyKnow Database Server: The DyKnow Database Component must be installed to a “default” instance of, and not a “named” instance of SQL Server. Furthermore, “Mixed Mode Authentication” and SQL Server Agent service need to be enabled and running.
SQL Database Server Recommendations
DyKnow recommends using Standard or Enterprise Editions of SQL because they utilize the maximum amount of RAM supported by the Host Operating System (32GB for Windows Server x64 Standard and 2TB for x64 Enterprise). SQL Server Workgroup edition should only be considered if the customer already owns a license and has a small deployment. DyKnow recommends 64-bit SQL Server for large deployments (for more information, see the “Large Deployment Recommendations” section).
Microsoft licensing allows customers to use a single processor license on a quad core processor; therefore, DyKnow recommends using a dual or quad core processor on SQL Server. DyKnow also runs on a multiple processor license.
Server Virtualization Support
- VMware ESX 2.5.5 or later
- Microsoft Windows Server 2008 R2 Hyper-V or later
- Citrix XenServer 5.5 with Windows Server 2008 or later
Where available, the resources allocated to a DyKnow Application and Database server tiers must be reserved. Not reserving these resources for the DyKnow Server may cause sub-optimal performance. Microsoft provides Windows Operating System and SQL Server support for these virtualization environments through the SVVP Program. DyKnow independently validates its software solution against a subset of these vendors. Configurations not meeting the above requirements are not recommended or supported.
Running the DyKnow Application or Database server tiers on the same machine as your virtualization environment can lead to unpredictable and sub-optimal performance. You should allow the virtualization environment to manage all the virtual machines and run the Application and Database servers on these virtual machines. Mixing native and virtual machines on the same hardware is not supported.
Data Storage and Disk Space
The DyKnow Server stores all of its information in the SQL Server Database using a SORM (Store Once Read Many) mechanism. The SORM drastically reduces the amount of duplicate data stored, in turn reducing needed disk space while allowing for easy backup and data restoration. The DyKnow administrator can further control data storage needs by regulating how long information is saved in the database. Institutions using only DyKnow Monitor should allow up to 20GB of storage space on the database, while institutions using the DyKnow Bundle or only DyKnow Vision should use the calculation below to determine data storage needs:
- 20G (Base) + 8GB per teacher
NOTE: It is important to note that data storage needs vary for each institution.
Audio Broadcasting Server Specifications
A DyKnow Audio Broadcasting Server is required in order to leverage DyKnow Vision's one-way streaming audio feature. This server* should meet the following minimum specifications:
Pentium 4, 3.2GHz (Dual Xeon or higher recommended)
2 GB of RAM
Gigabit Ethernet Card
Windows 2003 Server Standard SP1 (32bit)
Flash Media Server 3 Interactive**
DyKnow Media Server Application
Once the DyKnow Audio Broadcasting Server has been set up, the customer needs to obtain an updated license key that includes the Media functionality plus configuration instructions from their CSM. The customer will also need to specify how many connections their Flash Media Server 3 supports.
Network Particulars and Performance
DyKnow’s client-server design creates many networking and product performance benefits, including: increased network efficiency, mass connectivity (hundreds of computers) in local and distance networking environments and efficient operation over wired or wireless networks and the internet from broadband cable/DSL connections. These benefits are possible because DyKnow does not use any peer-to-peer or multicast technology; all data communications within DyKnow are sent exclusively using standard Web protocol. Users need not worry about connectivity interruptions in wireless environments because DyKnow uses special “lost signal transmit” (LSR) technology to address such issues.
Additionally, while DyKnow’s core functionality classifies the product as a low network bandwidth application, schools planning to use the full breadth of the DyKnow product should consider having higher bandwidth (see NOTE for more details). Furthermore, many school districts require Web filters or packet shapers. While the software performs more efficiently without introducing these devices, DyKnow will operate smoothly if server bound traffic can bypass them “untouched”.
NOTE: Higher bandwidth is recommended if the customer plans to use DyKnow’s “View Screen”, “File Transfer” and “Screen Broadcaster” features.
The average bandwidth used by 500 concurrent DyKnow Clients is about 4Mbps; however, DyKnow recommends a minimum of 10Mbps up/down bandwidth because usage varies over time. Additionally, customers utilizing a remote server for DyKnow (i.e. a centrally located server, a campus datacenter server or DyKnow ASP hosting) should take external bandwidth into consideration. Additional bandwidth might be necessary in order to effectively use Monitor features such as File Transfer, Screen Broadcaster, View Screen and Remote Control.
Single (Combined) Server Scaling
- 2 GB RAM / Single Core Processor = 150 concurrent users
- 4 GB RAM / Dual Core Processor = 500 concurrent users (64-bit recommended)
- HDD = 20GB (base) + 8GB per teacher
NOTE: These values represent a sample server estimate. Factors such as network and server IO performance may alter these values. Contact DyKnow for custom spec recommendations.
Large Deployment Recommendations
Infrastructure: For better scalability on large deployments, DyKnow recommends a 64-bit infrastructure, which will allow more RAM per machine while improving backup and failover capabilities. DyKnow also recommends separating the DyKnow Database and Application to create two distinct processes: The DyKnow Database Server and the DyKnow Application Server. Doing so allows the administrator to easily add additional application servers and scale the DyKnow Server as needs increase (Communication process: DyKnow Client > Application Server > Database Server). The server can then use any low-tech method to load balance (i.e. Round Robin DNS).
Bandwidth: For larger deployments, administrators should linearly scale minimum bandwidth usage, while having additional bandwidth available for activities such as transferring images or audio files or using Monitor features like Screen Broadcaster, View Screen, Remote Control and File Transfer.
NOTE: When performing high-tech load balancing, the DyKnow Application Server has two stateful components and one stateless component. In this case, the server administrator may use the ASP.NET state service to help perform load balancing. For more information on this please contact DyKnow technical support at email@example.com
There are two basic server architectures currently available; 32-bit (x86) and 64-bit (x64). It is important to note that various installed software should have the same architecture when setting up the DyKnow Server in a combined server configuration. For example, if your institution runs 32-bit Windows Server , it must also run 32-bit SQL Server and the 32-bit DyKnow Server. The same holds true if running a 64-bit Windows Server.
Each server must follow the above stated format even if the DyKnow Application Server and the DyKnow Database Server run on multiple (separate) servers. However, the architectures do not have to be the same between the separate physical servers. For example, one could have a 32-bit (x86) DyKnow Application Server connecting to a 64-bit (x64) DyKnow Database Server.
Download the PDF to see a chart which shows the various combinations of server architecture(s) we support.