Due to a bug in the event handler, DomainScan will always update the 'First event time' for an event to the current time.
As a sideeffect, this bug will disable the possibility to use triggers that must activate X minutes after the first event occured.

Due to a bug in the Domain creation algorithm, domain names with more than 2 parts (for instance test.example.com) will be created incorrectly. Therefore the same domain name will be created in the database by DomainScan over and over again, and eventually saturate DomainScan.

Under certain conditions, DomainScan may shut down during the scanning preprocess. In this preprocess DomainScan determines what devices to scan, and this may lead to an unexplained shutdown

Due to a situation in the preparation algorithm, DomainScan will not add devices from device lists, unless a prior preparation has found devices that are to be scanned

Due to an error, DomainScan will send out Notification email, even if there isn't any notifications

Due to an internal bug in DomainScan, devices marked as webservers will not use either the WMI or SNMP interface, and thus not collect any information

In case one upgrades from a DomainScan prior to v2.8, one may experience that event information dissappear from the DomainScan Client and that event information is not written to the event log. This happens due to an issue in the filtering process.
Note: Events are correctly handled by DomainScan Service.

Due to a bug in the Kiosk mode handler, the Graph panel will not be shown, if DomainScan Client is running in Kiosk mode, and Notes are disabled.

If a worker thread crashes unexpectedly during a device scan, DomainScan may enter a situation where it waits forever for the worker thread to stop correctly, which it doesn't. Eventually, the watchdog engine will terminate the current scan.

Due to an error in a condition check, DomainScan may choose to skip data collection via the SNMP interface. The situation occur, when the WMI interface is disabled on the device

Due to a bug, DomainScan may record a CPU load value above 100 percent.

Due to a bug, one may experience that one cannot alter service status within DomainScan. The bug will only appear after DomainScan has been running for a while.

DomainScan may crash during application shutdown. The problem is minor, and does corrupt any data. The excact cause is yet to be determined.

Due to an error in the DomainScan Service Engine, emails created by responses will not be sent, unless a notification reciever has been set.

When the client application has been opened for some time, one may experience one or more of the messages and even Windows may be slow. The cause is yet to be identified.

Due to a bug in the Operating system detection module, DomainScan may fail to resolve the correct edition of Windows Vista / Windows 7.

The SMTP connector in DomainScan does not authenticate itself to the mail server, even if a login is provided. Therefore, DomainScan will be denied access to any mail server that require secure login.

When one sets DomainScan to mail notifications to a notification receiver, then only some notifications will be sent.

Due to a bug, DomainScan fails to issue 'event cleared' notifications, when an event has been cleared and the monitor is set to issue an event when the event has been cleared.

If a device type is changed at one point in time (say from being a computer to being a server), then the change will be shown incorrectly in the device-tracking window due to a bug in the presentation code, which means that the current device type will be shown even for historical data (which means that the device type will always be shown as server for the given example).

Due to an error in the content updating mechanism, the content of the device, use, monitor and information views will be cleared but not updated with new content when a filter has been applied.

If one tries to test a security credential login, one may receive a 0x40 error. Afterwards DomainScan Pro may become unresponsive.

Due to an error in the path management, remote installations of DomainScan Client do not commit setup changes to the remote database server. Instead DomainScan Client will try to commit data to the local device, which will silently fail.

If a monitor triggers an event on a device, and the device is turned off while the event is triggered, then the event counter on the device will not be reset if the event is no longer triggered (which will happen, if the monitor is not set to trigger the event on offline devices)

Due to an error in the device and user dialog, the task deadline will always be set to a wrong date.

GDB revision 3.6 contains a data alignment error that affects some statistical counters. These counters include ‘Scans performed’, ‘Devices scanned’, ‘Audit records’, ‘Tracking records’ and a few internally used counters.

In the device, user or domain dialog, DomainScan shows the various monitors and responses that are assigned to the user or domain, including potentially responses that can be triggered.
If one clicks on these possible responses to view the responses setup, an error occur instead.

Due to a timing issue, one may experience that DomainScan stalls while trying to refresh its content from the database.
Typically, it can be seen in the lower left corner in the main window (where the database icon can be seen), where the text will continue to show 'connecting'.

If one saves information in Settings and rapidly closes the Settings window, DomainScan may fail with a 0x68 'read' failure.

Due to a bug in the Client, system notifications does not appear in the Outlook panel.

Due to a bug in the Setup Wizard, the Setup Wizard will fail to repair/reinstall DomainScan if the Service is installed. The problem only occurs if the repair/reinstall option is chosen.

If one disables all discovery options in DomainScan, DomainScan Engine will go into an everlasting loop and never complete. The Control Service will however detect the problem and terminate DomainScan Engine. This scenario will repeat itself indefinitely.
A second, but unconfirmed, cause of the 3E0 stop failure may that the Browser Service in Windows isn’t running. In this case a similar situation may occur.

By design, DomainScan tries to ping devices with an empty packet. However not all devices will respond to an empty ping-packet, and subsequently DomainScan will not detect that the device are online.

The device list editor look for device lists in the ‘other’ directory, where the correct location is the ‘database’ directory. Therefore, the editor will not detect device lists if the two folders are different.

Due to a formatting error, the slope value will be shown as NULL, if the regression line has a negative slope.

DomainScan Service fails to write the sleep period to the registry, which is needed in order for DomainScan Control Service to know the preferred rest period between scans.
When the registry key is not present, DomainScan Control Service will use a default 3 minutes sleep period.

Due to a bug in the Engine, the backup routine fails to copy both the service and the event log. All other files are copied correctly to the backup folder.

If one specifies separate directories for the database, log and script, then DomainScan will fail to relocate files correctly. Log files will be moved to the database folder, and the Devices and Users directory will not be moved at all.

It may appear that IP ranges fails to exclude excluded addresses. However this is not the case. The monitor is working correctly, and it is only due to an error in the page rendering that it appears this way.

The first time-column in the Event file may contain 2 errors.
The time that is written to the file is always the previous scan time.
Also, the time column may be prefixed with a second timestamp, which is not the intended behavior.

Under certain circumstance, DomainScan may fail to save backup settings, if one alters backup settings. This happen due to a missing registry key which DomainScan fails to create.

The version name of 64 bit editions of Windows Vista is displayed incorrectly due to a data interpretation bug.

When a user monitor fires an event, it fails to set the monitor-failure signal on the user, so that it could appear that the user is okay

Due to an error in DomainScan, one or both of the built-in domains may appear as a Directory enabled domain, even though this is not correct.

When one tries to alter the device type from within the Device dialog, it is not automatically saved.
However DomainScan does change the device type temporarily, but one must press ‘Save’ before the device change will be committed.

This bug only affects offline devices, where the event count is not reset before the new scan cycle. In effect, this causes the event count increments from the previous count for each scan.

When using the network search tools, the result for each device may be inserted multiple times. This only occurs when multiple devices are searched at the same time.

In x64 editions of Windows, registry settings for 32 bit programs are placed in the ‘wow6432node’ subfolder, which DomainScan is not aware of. Therefore, DomainScan will show an error message (-1), and open the database in read-only mode.

Under certain conditions, DomainScan will miss updating the counter that tells the number of events that occurred on the device.
If the situation also occurs in the following scan cycle, then DomainScan will register that a different number of events occurred (which may be a result of this bug), which will then cause a tracking record to be written after each scan for all devices that are affected by this bug.

If a device is offline, then a monitor will create an event, even if the monitor is not set to do so

Due to an error in the scanning engine, the network scan time is written to the statistics log before the value is updated.

If all values in a graph lead to a mean value of 0, this will lead to a division by zero error due to the fact that the condition is not caught before the division.

Due to a change in the DLL-naming convention in Visual Studio 2005 in comparison with Visual Studio 2003, DomainScan could no longer connect correctly to certain functions within a DLL, thus causing the LDAP interface to stop working. The bug does also affect service installation, because DomainScan can no longer set Run As privileges.

When a device is reassigned from one domain/workgroup into another and then again to a third a few minutes later, then the Windows Browser service may detect that the device is belonging to 2 or more workgroups/domains at the same time. In DomainScan this will lead to a link-loop, which would cause the device to be scanned indefinitely.

When a device is reassigned from one domain/workgroup into another and then again to a third a few minutes later, then the Windows Browser service may detect that the device is belonging to 2 or more workgroups/domains at the same time. In DomainScan this will lead to a link-loop, which would cause the device to be scanned indefinitely.

When a device is reassigned from one domain/workgroup into another and then again to a third a few minutes later, then the Windows Browser service may detect that the device is belonging to 2 or more workgroups/domains at the same time. In DomainScan this will lead to a link-loop, which would cause the device to be scanned indefinitely.

DomainScan cannot mount a database that is only available via a share name. However the database can be mounted by either connecting directly using the default shares, or by mounting the share name as a network drive.

Due to the fact that most new processors feature multiple cores, DomainScan can get confused and show an incorrectly number.

Due to an issue in the GH Software Online module, DomainScan may clear all URLs to the GH Software website, and when one tries to open a website, DomainScan will refuse to do so, because it does not point to ghsoftware.dk.

Due to an issue in the GH Software Online module, DomainScan may fail to retrieve the port name definition file. Following this, one may experience that the port name list may be empty.

The automatic database refresh cycle may fail to synchronize with the database

Due to an uninitialized variable in the calculation routine, the regression line may be computed incorrectly.

Due to a presentation bug, the time for ‘Last seen’ is shown as --- for domains that has never been online.

When selecting Wake-On-LAN (WOL) on offline devices, DomainScan fails to gather the MAC address, and shows that the address could not be resolved.

If an event has triggered a response, then the event is supposed to display a yellow dot instead of the red dot. This may not happen

It may not be possible to open the log file from within DomainScan.

WMI monitors that are set up as select [Name], [Monitor] from [wmi_namespace] may most likely parse the returned data wrongly, and display that data ‘did not return data as expected’, even though the data were returned as expected.

Due to an error while parsing WMI data, the size of attached network drives may be included in the total disk size.

This will happen, when one or more devices in an IP range are included in the scan.

The port editor in Preferences may be locked for editing.

Domain assigned monitors is included in the user monitor count, even if the domain assigned monitor isn’t a user-monitor. The reverse problem is also present.

A remote database mount may fail with error code 30. The error is due to a problem reading the remote registry, that lead to the path information being erased. In order to be able to mount the remote database, disable “Commit pending changes”

In Domain Report – due to a calculation error, the summary numbers is the overview table may not reflect the current state correctly.

The monitor page may display a 0x00000004 read error, while trying to display an event. This situation occurs when a WMI monitor fails, and a 'The query did not return data as expected' event is created.

This bug is limited to devices that are included via device file lists, and is due to a comparison error.

After running a new query in the WMI browser, DomainScan may show an Index out of range error. This occurs if the query is being executed, while an item in the result list is selected.

The process collecting functionality is not enabled in DomainScan Service, which will therefore ignore the process flag.

When the database connection is refreshed, DomainScan does not refresh the timeline content properly, leading to devices being inserted one more time for each refresh cycle.

The text shown is not correct

Whenever a custom description is assigned to a device or a user, then the description will be replaced with a “?” after the first database refresh.

A response may not be executed if:
  - The response is as a domain-assigned response.
  - It is the first time the event is detected

DomainScan does not execute monitors on a device the first time it is detected as online (regardless of whether it’s a new device or a device that has been offline).

DomainScan does not reset the event counter for offline devices, which leads to an ever increasing number of reported events if events are created on offline devices. However, the events are executed correctly.

This happens if a custom port is assigned to a port monitor, which is unknown to the port scanner list, which will therefore not include this unknown port.

A bug exists so that the same port can be loaded more than once when DomainScan synchronizes the TCP port list with the port definition file from GH Software

MAC address, DEP (data execution prevention) or PAE (physical address extension) may not be detected correctly. Furthermore Windows NT may be reported as Windows 95 due to an OS interpretation error.

Monitors and responses cannot be deleted.

The ‘More information’ menu in the main window does not work when the selected item is a domain/workgroup

Due to a bug in ‘Preferences’, DomainScan may turn audit off when domain settings are saved. The bug will only affect new devices, where hardware audit will not be collected.

DomainScan Client and DomainScan Service may not agree on the amount of devices that are to be checked by an IP range monitor, which may cause DomainScan Service to create more events that needed.

DomainScan Client may lose connection to a database if there are pending changes.

Device types cannot be changed.

The uptime is increased instantly for newly discovered users/devices. I.e. a new user or device is shown with an uptime >0 even if the user/device has just been discovered.

In the hardware timeline, the audit always reports the current user and not the user from when the audit was collected.

Remote databases may not load.

The 'Clear recent list' option does not work.

DomainScan may report 0 processors on Hyper-Threading enabled systems, due to an error upon audit-collecting.

Precommit will fail if trial-period is active

Changing the monitor/response setup could cause DomainScan to crash

The icon for IP Range monitors are not correct

Secondary commit file is not deleted after a recovery

An issue in the audit collecting routine may caused the wrong OS version to be saved. Furthermore DomainScan Client may fail to show a change in the operating system.

When sending an email response, Domain will show the sender as 'DomainScan Service Service'