The DyKnow client is the application installed on a user’s PC. By itself, the DyKnow client can be used to create and open notebooks on local disks. When connected to a DyKnow server, the DyKnow client serves as the interface for using DyKnow Vision and/or DyKnow Monitor.
v5.4 [May 4, 2011]
- Added the ability for Users to log in via “User Principal Name” when the User Principal Name suffix is different than the windows domain name.
- Removed support for Blackboard integration as a mechanism to authenticate users.
- Enhanced the Monitor List display to more quickly and easily identify users not in session by segmenting the list into two user groups: connected users and those not yet connected.
- Enhanced the list to update the count of users connected and expected (ex. 2 of 28).
- Enhanced restart time of the DyKnow service if a workstation is modified via the Administration Console.
- Significantly improved the connection time when taking control of a workstation currently monitored in a different session.
- When using https over a proxy, URL Filtering could cause the service to fail.
- When using Google Chrome, if an https site was opened first, then URL Filtering applied; https sites were still accessible.
- Classes set as blocked by a Data Integration (DITO) import were still available in the class list to start a Monitor session.
- Modifications made to Application Blocking or URL Filtering plans set as the default plan were not accurately retained.
- Enhanced Vision polling to include the ability to optionally indicate the correct answer for polls created before class and saved in the notebook as well as spontaneous polls created in class. Polls saved to a *.csv file will include a new column which indicates whether the student answered the poll correctly. Note: This feature applies to DyKnow Vision polls only.
- Added the ability for Moderators to mark a notebook as shared with all class members. Once shared, everyone enrolled in the class: (The Moderator may remove the shared property at any time.)