#21894 |
Fixed an issue where a node with an unclassified node type would not be deleted when the IP/MAC usage timeout expires. |
5.0.31 |
#24192 |
Fixed an issue where tags would be displayed as many times as the number of authenticated nodes. |
4.0.138 5.0.35 |
#24449 |
Fixed an issue that caused the button to become unresponsive in the Uninstall a Program plugin. |
5.0.42 (LTS) 6.0.0 |
#24502 |
Fixed the problem that the value of the option that has not been changed is corrected when the policy is modified. |
5.0.44 |
#24523 |
Fixed an issue where certain columns were missing when exporting users. |
4.0.7 |
#24554 |
Fixed the problem that the paging output option was restored when the condition was deleted on the node group detail screen. |
5.0.12 |
#24560 |
Fixed an issue where files in the C:program Files (x86) path could not be executed. |
5.0.0 6.0.0 |
#24568 |
Fixed an issue where allowed APs were blocked by WLAN control. |
|
#24576 |
Fixed an issue where the 'Login IP Restriction Subnet Support' off option in the adv settings was not reflected when setting the device batch in system management. |
4.0.13 |
#24592 |
Fixed an issue where related data did not appear on the page moved to the button created when system log collection was completed. |
5.0.40 |
#24620 |
Fixed an issue where the node list was not displayed when viewing the filter and status menus. |
5.0.42 (LTS) 6.0.0 |
#24626 |
Fixed an error log output when clicking the close list button on the node detail screen. |
5.0.38 |
#24628 |
Fixed an issue where the integrity check function did not work properly in macOS Agent. |
5.0.27 6.0.0 |
#24630 |
Fixed the problem that the tooltip of the control policy column of the node registered in the center was displayed incorrectly. |
5.0.27 |
#24637 |
Fixed an issue where an error would occur when changing the infrastructure System from Site to Cloud to On-Premises. |
6.0.0 |
#24645 |
Fixed an issue where editing of the management view was not reflected in the status & filter tag screen. |
5.0.9 |
#24646 |
Fixed and issue where the macOS Agent's Desc.ico file does not satisfy the integrity test. |
5.0.28 6.0.0 |
#24649 |
Fixed a blocking malfunction in Windows Firewall control plug-in when multiple rights objects were registered in the control policy. |
5.0.28 6.0.0 |
#24652 |
Fixed an issue where the dashboards agent installation status widget's contents of the execution date column was not displayed. |
6.0.0 |
#24665 |
Fixed the problem that free space on the local disk does not work when performing a backup through an external storage device. |
4.0.19 |
#24680 |
Fixed an issue where the policy server would not detect agent installation node as in the down state. |
5.0.36 |
#24685 |
Fixed an issue where blocked IPs set to be used were assigned when using the Allow Blocked IPs option. |
4.0.12 |
#24701 |
Fixed an issue where the external authentication linkage function does not work when the BASE64 encryption method is used. |
5.0.0 6.0.0 |
#24707 |
Fixed an issue where the node list was not displayed when moving. |
5.0.33 |
#24718 |
Fixed an issue where the ZTNA version Dashboard Widget Palette Add Preview images feature was showing a blank preview. |
|
#24729 |
Fixed an issue where an error occurred when approval/rejection of one or more items were done individually. |
4.0.113 5.0.10 |
#24733 |
Fixed an issue where the action policy was not executed when there were many script contents to be executed. |
4.0.16 5.0.0 6.0.0 |
#24742 |
Fixed an issue where the inequality sign (>) was outputting as > in the processing message of the system management. |
5.0.42 (LTS) 5.0.45 6.0.2 |
#24767 |
Fixed an issue where the domain information of the node was not being updated by NETBIOS scan. |
4.0.M3 |
#24785 |
Fixed an issue that caused a Google auth code issuance error in G Suite sync settings after changing Google API client ID. |
6.0.4 |
#24797 |
Fixed a collection error due to incorrect data format when registering a switch through SNMP information collection. |
4.1.4 |
#24802 |
Fixed the problem that the real-time monitoring forced control option for V3 vaccine did not work. |
5.0.0 6.0.0 |
#24817 |
Fixed an issue where the list of sub-department users by department of all users is not displayed. |
5.0.45 6.0.4 |
#24885 |
Fixed an issue where when uploading an image from a custom button the table of contents pages does not moved to another page. |
5.0.12 |
#24895 |
Fixed an issue where agent plug-ins on Windows 7 systems would abnormally terminate when collecting vaccine information. |
5.0.0 6.0.0 |
#24897 |
Fixed a database error in macOS related settings where an audit log would occur. |
5.0.45 6.0.2 |
#24905 |
Fixed the problem where the node is changed to the UP state when the agent is in the Down state. |
5.0.47 (R) 6.0.4 |
#24936 |
Fixed an issue where there are items that were output in button format instead of drop-down type components. |
5.0.31 |
#24949 |
Fixed an issue where deleting the device in System > System Management, nothing was printed in the Tomcat log and Center log. |
6.0.0 |
#24971 |
Fixed an issue where the block target list was causing the sensor daemon to hang. |
4.0.117 |
#24999 |
Fixed an issue where if there are more then 32 virtual sensors, they could not be displayed in the list. |
5.0.32 |
#25003 |
Fixed an issue where the failure to transmit the DHCP information of the node collected from the sensor would cause the center to restart. |
4.0.114 5.0.11 |
#25037 |
Fixed an issue where searching from the node group menu would bring up the error system message. |
5.0.38 |
#25050 |
Fixed an issue where call-trace causes a memory allocation failure in the ENFORCER kernel module. |
5.0.40 |
#25060 |
Fixed an issue where removing agent information by long -term down, the agent platform information was not updated even after reinstallation and logon. |
4.0.61 5.0.0 |
#25067 |
Fixed an issue where the debug log was duplicated in multiple directories. |
5.0.42 (LTS) |
#25068 |
Fixed an issue where plug-in was closing when using macOS Appearance and Personalization actions. |
5.0.15 6.0.0 |
#25085 |
Fixed an issue where creating a node was incorrectly matching the registration date/updown status node group conditions. |
4.0.0 |