WiseFixer is a professional and advanced system optimizer tool to help users easily and conveniently fix system errors,clean registry,optimize system to speed up PC. What's in the Release Notes The release notes cover the following topics: What's New; Earlier Releases of vCenter Server 5.5; Internationalization. If you can connect your gaming controller (I use an Xbox 360 controller) to your computer, you can simply use the joysticks to pilot. Your monitor shows off the first. The ridiculously expensive Texas Instruments graphing calculator is slowly but surely getting phased out. The times they are a-changin’ for the better, but I’m.![]() Fix Windows Errors and Optimize PCFix Windows Errors & Optimize Your System No Blue Screen, No Lock up, No Errors, Less Garbage Files → More Smooth System Running. WINNER OF OVER 1. Lansweeper changelog | what's new. Lansweeper server requirements: Windows 2. Windows XP or higher (Windows server recommended)Dotnet framework 4. SQL Compact (free) or SQL Express (free) or SQL server 2. Lansweeper client requirements: Windows 2. Windows home clients are only supported with Lspush scanning. Network device requirements: Snmp version 1/2 or 3 enabled. Linux/Mac client requirements: SSH server enabled. Latest updates and bug fixes: 6. Lspush 6. 0. 1. 00. SQL 1. 50 (0. 4 oct 2. Changed: #5. 64. 84. Removed RPC EPMAP check from tests performed by the Devicetester. Fixed: #5. 78. 74. When running the Ls. Push scanning agent on a Windows computer by double- clicking on the executable, the progress bar doesn't close after scanning has finished. Fixed: #5. 67. 48. Socket errors when running the Ls. Push scanning agent with a direct connection to the Lansweeper server. Fixed: #5. 64. 80. Scanning a network device using an SNMPv. MD5 or SHA1 authentication is used. Fixed: #5. 68. 72. If the Lansweeper scanning service and web console are on separate servers and the console is updated, the Lansweeper version number is incorrectly listed as 0 in the installer. Fixed: #5. 65. 96. When hosting the Lansweeper database in SQL Server and generating a backup using the Database. Maintenance tool, errors are generated. Fixed: #5. 72. 63. Grammatical error in an informational message in the Lansweeper installer when setting up an installation with multiple scanning servers. Fixed: #5. 75. 82. The Config. Editor tool incorrectly treats SQL Server instance name and username of the Lansweeper database as case sensitive, resulting in faulty warnings about inconsistent connection strings between scanning service and web console. Fixed: #5. 75. 78. When using Chrome and submitting text in the note editor of a help desk ticket, the editor expands in size when it shouldn't. Fixed: #5. 73. 01. Due to inconsistently formatted data returned by the HP website, warranty information of some HP assets cannot be scanned even though the HP website does return it. Fixed: #5. 64. 82. Scanning a network device using an SNMPv. OIDs. Fixed: #5. 70. When using the old default password for the lansweeperuser database user, automatic password randomization can in some cases lock out the user account. Fixed: #5. 72. 70. XML External Entity (XXE) issue in the import package functionality of the deployment module. Fixed: #5. 69. 45. If the Lansweeper database connection string is incorrect and the Database. Maintenance tool is run, the tool crashes instead of giving an error message. Version 6. 0. 1. 00. Lspush 6. 0. 1. 00. SQL 1. 48 (2. 2 Aug 2. Fixed: #5. 65. 96. When hosting the Lansweeper database in SQL Server and generating a backup using the Database. Maintenance tool, errors are generated. Fixed: #5. 69. 45. If the Lansweeper database connection string is incorrect and the Database. Maintenance tool is run, the tool crashes instead of giving an error message. Fixed: #5. 67. 48. Socket errors when executing Ls. Push with a direct server connection. Version 6. 0. 1. 00. Lspush 6. 0. 1. 00. SQL 1. 48 (0. 9 Aug 2. Fixed: #5. 66. 53. Due to changes in the HP website, warranty information of HP assets cannot be scanned. Version 6. 0. 1. 00. Lspush 6. 0. 1. 00. SQL 1. 48 (0. 2 Aug 2. Added: #5. 30. 79. A new Config. Editor. Program Files (x. Lansweeper\Tools on the Lansweeper server can be used to make changes to the database connection strings in Lansweeper configuration files, which are now obfuscated. Added: #5. 44. 07. Added 8. 4 new built- in reports to the Reports tab of the web console, 5. Added: #5. 44. 43. When submitting a proxy server for warranty scanning under Configuration\Server Options, a timeout in seconds is now configurable for establishing the connection from the proxy server to the manufacturers' websites. Changed: #5. 37. 58. Added generic, non- unique monitor serial number "CNC9. Serial. Translation database table so it is no longer scanned. Changed: #5. 34. 72. Added several generic, non- unique MAC addresses, models and serial numbers to an internal blacklist, to prevent these records from causing incorrect asset merges. Changed: #5. 53. 14. Added the version number of the Ls. Push scanning agent to popups you see when running Ls. Push with the /showresult parameter and getting a socket or other type of error. Changed: #5. 23. 64. Changed the Lansweeper version numbering from x. Changed: #5. 35. 07. Improved speed when performing multiple simultaneous scans with the Ls. Push scanning agent, by making the HTTPS listener of the Lansweeper Server service multi- threaded and able to handle 1. Changed: #5. 55. 81. Several improvements and bug fixes related to the Program Files (x. Lansweeper\Tools\Config. Editor. exe tool used to modify Lansweeper database connection strings. Changed: #5. 42. 48. Ticket indexing and search have been optimized and ticket filters with results from text searches no longer display a ticket count in the tab header when logging out and back in, to improve performance. Due to the ticket indexing changes, index files will be deleted and recreated upon updating to Lansweeper 6. Changed: #4. 66. 13. To improve security, database scripts can now only be run in the Program Files (x. Lansweeper\Tools\Database. Maintenance. exe tool on the Lansweeper server and the Configuration\Database Scripts menu in the web console has been renamed to Configuration\Database Tables. Changed: #5. 33. 61. To improve security, disabled HTTP TRACE requests to the Lansweeper web server by default. Changed: #5. 24. 12. To improve security, Lansweeper database connection strings stored in Program Files (x. Lansweeper\Service\Lansweeperservice. Program Files (x.Lansweeper\Website\web. . Changed: #5. 21. 45.To improve security, made the default permissions of the folders in Program Files (x. Lansweeper on Lansweeper servers more restrictive where possible. Changed: #4. 87. 24. To improve security, the Lansweeper database password is now automatically randomized when using a single scanning server. Changed: #5. 23. 80. To improve security, the Lansweeper Server service now uses HTTPS instead of HTTP to handle incoming requests by the Ls. Push scanning agent, which also means that only the most recent Ls. Push found in Program Files (x. Lansweeper\Client on the Lansweeper server will still work for agent based scanning. Due to the switch to HTTPS, the old Ls. Client tool for scanning Windows computers is no longer supported either, no longer works and should be replaced with Ls. Push in logon scripts and group policies. Changed: #5. 26. 25. Tools previously found in the Program Files (x. Lansweeper\Service folder on the Lansweeper server are now in a central Program Files (x. Lansweeper\Tools folder, where future tools will be added as well. Fixed: #5. 59. 77. Due to changes in the IBM/Lenovo website, warranty information of IBM/Lenovo assets cannot be scanned. Fixed: #5. 41. 58. Error when adding notes with attachments by using the Add. Note function of the ticket API and incomplete documentation for the Add. Note function. Fixed: #5. Errors in old dashboard widgets due to missing required parameters and in widgets displaying deleted reports. Fixed: #5. 53. 82. Extended warranty products of HP assets are not always scanned, resulting in an incorrect final warranty date for the asset. Fixed: #5. 40. 29. Invalid JSON output when using the Get. Assets function of the ticket APIFixed: #5. SSH scanning of a Mac computer can fail if the HTTPS output of the computer resembles that of a Windows machine. Fixed: #5. 52. 23. Syntax errors in reports submitted in the report builder are only detected upon saving the report and in databases hosted in SQL Server result in "Report cannot be found" errors. Fixed: #5. 55. 34. Unclear message about automatic Lansweeper database password randomization and incorrect database size and asset count in Program Files (x. Lansweeper\Service\Errorlog. Lansweeper server, as well as password randomization issues due to password policies being enforced on the lansweeperuser database user. Fixed: #5. 55. 66. Unclear or no validation errors on several web console pages in case of faulty user input. Fixed: #5. 55. 72. Using the Ls. Push scanning agent with a direct connection to the Lansweeper server sometimes generates socket errors. Fixed: #5. 10. 15. When using a Lansweeper license limited in number of assets and reaching the licensed asset limit, warnings to indicate that scanning will stop are not always given. Fixed: #5. 27. 94.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |