Quick answers to your questions about the server component of DyKnow.

Client Specifications

Microsoft Windows XP or Microsoft Windows Vista
English/US Localization or Australian Localization only
Minimum 512 MB RAM
Microsoft .NET Framework 3.5 SP1
Note: DyKnow software is supported on a Mac running Windows via Boot Camp

DyKnow 5.2 Server Specifications

Operating System
Microsoft Windows Server 2003, 2008
32-bit and 64-bit (x64) supported

Database Storage
Microsoft SQL Server 2005, 2008
Workgroup, Standard, or Enterprise Edition Supported
32-bit and 64-bit (x64) supported – Processor License recommended
SQL 2005 Detailed Specifications
SQL 2008 Detailed Specifications

Miscellaneous
English/US, English/Australia Localization only
Microsoft .Net Framework 3.5 SP1 (free download)
Internet Information Server Installed (included in Windows OS)

Windows Application Server Recommendations

The DyKnow Application Component is currently supported by most editions of Windows Server 2008; however, Standard, Enterprise or Datacenter Editions are recommended. If installation needs grow, and more RAM is necessary, server administrators may find it necessary to use a 64-bit edition of Windows.

NOTE: The DyKnow Application Server does not support the use of self-signed SSL certificates.

Application/Database 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 SQL Server 2005 or SQL Server 2008 Standard or Enterprise because both editions 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. DyKnow recommends a 64-bit version of 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 (for more information on licensing, see the "Microsoft CAL vs. Processor licensing" section).

VMware Support

For those interested in using VMware, the DyKnow Database and Application Servers are supported on VMware ESX Server 2.5.5 (or later versions). System resources allocated solely to the Virtual Server must be equal to the above stated specifications because sharing DyKnow Server resources may cause sub-optimal performance. Configurations not meeting the above requirements are not recommended or 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 2GB of storage space on the database, while institutions using the DyKnow Software Suite or only DyKnow Vision should use the calculation below to determine data storage needs:

2G (Base) + 1G per 5 classes with approximately 25 students per semester

Additionally, customers planning to use DyKnow Vision's Audio Recorder feature should plan for 12MB of storage for each additional hour of recorded audio.

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's one-way Audio Broadcaster feature. For an additional fee, DyKnow can host the customer's DyKnow Audio Broadcasting Server (contact your sales representative or Customer Relationship Manager-CRM for more details). If the customer intends to host their own DyKnow Audio Broadcasting Server, they will need to procure a separate* server that meets the following specifications:

Hardware
Pentium 4, 3.2GHz (Dual Xeon or higher recommended)
2 GB of RAM
Gigabit Ethernet Card

Software
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 will need to obtain an updated license key that includes the Media functionality plus configuration instructions from their CRM. The customer will also need to specify how many connections their Flash Media Server 3 supports when contacting the CRM.

*For optimal performance, the customer should use a separate audio server from the main DyKnow application and database servers.

**Request the educational discount when purchasing your Flash Media Server 3 Interactive software.

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.

WAN Requirements

The average bandwidth used by 500 concurrent DyKnow Clients is 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 features such as "File Transfer", "Screen Broadcaster", "View Screen" and "Remote Control". (For more information call 1.888.8.DYKNOW or E-mail sales@dyknow.com)

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 = 2GB Base + 1GB for every 5 classes with 25 students

Customers who plan to use Vision 5.1's Audio Recorder should have 12MB of storage available on the Database Server for each hour of recorded audio. Audio data can be purged each semester to manage database size.

NOTE: These values represent a sample server estimate. Factors such as network and server IO performance may alter these values.

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 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 1.888.8.DYKNOW or support@dyknow.com

Architecture Requirements

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.

The following chart helps show the various combinations of server architecture(s) that DyKnow supports.

Microsoft CAL vs. Processor licensing

Microsoft Windows Server and Microsoft SQL Server each have three different licensing models. Two of the models require CALs (Client Access Licenses) and the third requires a Processor License. A Microsoft Windows Server license with five user CALs is sufficient for typical server installations running only the DyKnow Server.

The current Microsoft SQL Server licensing specification licenses a processor license per "socket", so a single processor license can be utilized on a "Quad Core" processor. For more information please visit this Microsoft Website: http://www.microsoft.com/sql/howtobuy/licensing.mspx, specifically Section 3a of the Server Processor End-User License Agreement (EULA).

Visit the DyKnow store to purchase SQL or email sales@dyknow.com for more information.