ITWatchDogs Watchdog 15 Environment Monitor driver for Windows 7 - ITWatchDogs Watchdog 15 Environment Monitor drive

ITWatchDogs Watchdog 15 Environment Monitor 3.0.0

ITWatchDogs Watchdog 15 Environment Monitor driver from ITWatchDogs for OS Independent

ITWatchDogs Watchdog 15 Environment Monitor driver from ITWatchDogs for OS Independent

Publisher review for ITWatchDogs Watchdog 15 Environment Monitor 3.0.0:

Before install ITWatchDogs Watchdog 15 Environment Monitor 3.0.0you should set a system restore point, to make sure you can rollback to your original driver in case you accidentally install another driver or select the driver for another version of the operating system.

Also, do not forget to check with our site as often as possible for new version of ITWatchDogs Watchdog 15 Environment Monitor . We recommend to always use most recent version of a driver.

This firmware release is a major change to the firmware of the Watchdog 15. It includes a new GUI, new features, improved stability, and other improvements. Customers updating from the older v1.x.x firmware versions, please be aware of the following items:
- Once the unit has been updated to v3.0.0, it cannot be downgraded to the prior v1.x.x firmware.
- If your unit is an ITWatchdogs-branded device with a firmware version prior to v1.6.0, you will need to install the v1.6.0 firmware (below) before updating it to v3.0.0. (The easiest way to determine this is to log in to the unit's GUI; if it has a blue-and-white color scheme with the old ITWatchDogs "yellow dog" logo in the upper-left corner, you'll need to apply v1.6.0 before updating to v3.0.0.)
- Firmware updates over HTTPS will not be supported in v3.0.0. After updating the unit to v3.0.0, if you set the unit to allow "HTTPS Only" and disable HTTP access, you will not be able to apply any future firmware updates without reenabling HTTP access first.
- v3.0.0 is not compatible with Watchdog Console Aggregator! The 3.0.0 firmware does not implement the deprecated XML-based API which Console used, and Console is not able to use the newer JSON-based API. If you wish to continue using the Watchdog Console Aggregator software, do NOT update your Watchdog units to any firmware beyond v1.6.0!  bug fixes:- Fixed an issue where SNMP requests with long OIDs sometimes caused spontaneous reboots.
- SNMP getNext operations on invalid OIDs sometimes wrapped around to beginning of the MIB, causing an infinite loop in some SNMP managers. Fixed.
- Improved validation of various numeric and IP-address entry fields.
enhancements:- Removed support for deprecated SSLv3 protocol, for security reasons. Only TLS v1.2 is now supported.
- Removed support for 512-bit SSL/TLS certificates.
- Server certificates have been upgraded to 2048-bit.
- Added support for mail servers that use STARTTLS, such as Office365.
- Added support for the new A2D analog-to-digital converter, which will replace the soon-to-be-discontinued CCAT interface.
- Special characters '-', '!', and '~' are now permitted in SNMP community strings.
- New web interface, including a JSON-based web API.
- Added automatic Daylight-Saving Time (DST) adjustments.
- Added support for SNMPv3.
- Added support for IPv6.
- New, more flexible and configurable alarm system:
Alarm triggers now have individual delays for both trip and clear.
Delays and Repeats can be anywhere from 0–14400 seconds. (14400 seconds = 240 minutes, or 4 hours.)
User can define up to 8 "valid time" ranges, and set individual alarms to trip (or not trip) only within or outside of those times.
User can now define up to 32 alarm "actions", each with individually-settable delayed and repeating actions, and assign any of these actions to any alarm trigger.
(NOTE: Due to this change in the alarm-system behavior, be aware that any alarms which currently have "repeat every __ minutes" set in your current v1.x.x firmware will have their "repeat" settings reset to "0"! You will need to go back into the alarm settings after the update and manually re-enable repeats on the alarm actions after updating. Also note that all delay and repeat timers are now given in seconds, not minutes; if you previously had a 30-minute repeat, for example, be sure to reprogram it as "1800", not "30".)
Alarm triggers can be set to be either "Alarm" or "Warning" priority.
An alarm or warning can be made to "latch", requiring the user to manually log in to acknowledge and clear the event.

Operating system:
OS Independent