Lansweeper 5.2 Beta (5.2.0.15)

[Hemoco]

Lansweeper beta has been updated to version 5.2.0.15

Beta testing is closed

5.2.0.15 changes:
- Fixed: Bug when deploying to report when using SQL server
- Fixed: Small fixes in deploy as logged on user.
- Fixed: Deleting Tasks after deployment failed when the taskservice was not running.
- Fixed: WOL is not deploying in certain cases.
- Fixed: Website cannot save asset because of special characters which were not encoded.
- Fixed: Unnecessary zeros are trimmed when saving an IP address.

5.2.0.14 changes:
- Added: Deploy packages as logged on user.
- Fixed: Assets cannot be deleted due to database constraint.
- Fixed: SNMP various performance bug fixes.
- Fixed: Handling quotes on model and manufacturer suggestions when editing an asset.
- Fixed: Handling special characters in Email alert group names.

5.2.0.12 changes:
- Added: Optional logging of all scans.
- Added: Fine tuning parameters for active scanning.
- Added: Asset type, domain and scanserver are now editable in mass edit mode.
- Changed: Packages now wait if there is already another package being deployed on the machine.
- Fixed: Incorrect vProAMT detection when page returns a 404 error.
- Fixed: Manual full rescan rescans disabled items.
- Fixed: Unable to delete packages linked to a schedule.
- Fixed: Date sorting problem with yyyy-mm-dd format.

5.2.0.11 changes:
- Changed: vProAMT ping response icon.
- Fixed: Removing deployment task schedules sometimes failed.
- Fixed: Launching deployments sometimes failed.
- Fixed: Userdomain\username incorrect scanning with lspush.
- Fixed: Linux software page crashes on invalid date fields.
- Fixed: Lasttried date is incorrect when scanning with lspush.
- Fixed: Latest lspush version is not written into database on new installs.

5.2.0.10 changes:
- Added: Scan dynamic groups and reports on a schedule.
- Added: vPro AMT detection.
- Added: Option in IP range scanning to only scan found windows machines that are not yet in the database.
- Changed: Report:Antivirus disabled does no longer show assets where a valid antivirus is installed.
- Changed: Better performance when deploying packages combined with scanning.
- Fixed: Immediately clear taskscheduler after run.
- Fixed: After scanning logging display problem.
- Fixed: Deploying on dynamic groups (deploy now button)
- Fixed: Deployment bug using environment variables in scripts.
- Fixed: Error while saving Apple Mac network cards.
- Fixed: Path length in tblEnvironment bug.
- Fixed: Deployment deadlock while scanning.
- Fixed: Error when deploying scripts with "@ " in the path name.
- Fixed: Issues in uninstaller (versions, wildcards)
- Fixed: Datetime parsing error on the package schedule page.
- Fixed: Dynamic groups widget are unsorted.
- Fixed: Report "Computer: Not seen in the last 30 days" shows incorrect data.
- Fixed: Lspush: Incorrect file version number scanned for some executables.
- Fixed: Lspush: An error is thrown if the adobe cache.db file is corrupt.

5.2.0.8 changes:
- Fixed: Bug where report parameters containing ',' would not deploy packages.
- Fixed: Bug where some reports with 'order by' queries would not deploy packages.
- Fixed: Unable to save deploy options when special html codes are used.

5.2.0.7 changes:
- Added: Linux & Mac software click through.
- Changed: Domain and OU are shown on asset page after partial scanning failure.
- Changed: The asset page shows when no anti virus is installed on the windows asset.
- Fixed: Global tabs made by other users cannot be deleted by administrators.
- Fixed: Computer names cannot be pasted into filter fields.
- Fixed: Date parse problem in some UI cultures.
- Fixed: Rounding error in switch connection speed.

5.2.0.6 changes:
- Added: Wildcard (%) in 'msi uninstaller' step
- Fixed: Added new Lspush version missing in 5.2.0.6
- Fixed: Logging bug.
- Fixed: Linked assets bug.
- Fixed: Domain scanning exclusion bug.
- Fixed: Some query results from widgets contain non-active assets.

5.2.0.5 changes:
- Added: New deployment option: "Deploy after successful scan"
- Added: New deployment option: "Retry deployment if machine is offline for x hours"
- Added: Deployment can now run using localsystem or using the scanning credential.
- Fixed: Bug in msi uninstaller command.
- Fixed: Lspush uses file.version instead of file.productversion which is sometimes different.
- Fixed: Lspush reports an incorrect filesize on large files.
- Fixed: Various small improvements and error fixes.

5.2.0.4 changes:
- Added: Using parameters /silent /silentupgrade /accepteula it is now possible to silently upgrade remote scanning servers.
- Added: Compare function for software versions => smaller | equalorgreater
- Changed: Lansweeper installer does no longer download additional tools.
- Fixed: Configure Remote Desktop & Firewall Does not work.
- Fixed: Thumbnail.aspx is returning a broken image for Asset Images.
- Fixed: Deployment does not work when connecting from XP to a newer OS.
- Fixed: Removed the option to add dynamic asset groups on the edit asset page.
- Fixed: Multiple conditions are not written correctly in the registry.
- Fixed: Replace CRLF by space character for custom commands.

5.2 new features:
- Fully customizable mass software deployment, scripting, uninstalls, ...
- Anti- virus definition scanning (disabled/out of date)
- Support to scan the latest Adobe serial numbers (requires C$ share access)
- Support to scan the latest Autodesk serial numbers.
- Dynamic asset groups.
- Possibility to exclude domains from scanning.
- Possibility to exclude asset types from scanning.
- User based software and msi packages are now visible on the software page.
- Custom reports have new additional optional columns: foregroundcolor, backgroundcolor, hyperlink
- Button to clear the scanning queue for a scanning server.
- Comments and attached documents have a visual indicator.
- Global tabs: an administrator can edit dashboard tabs and mark them as global to make them visible for all users.
- Option in IP range scanning to scan devices that only reply to a ping request.
- Lansweeper Standard 750 is rebranded as Lansweeper Professional and can now scan 1000 assets and Vmware/Hyper- V/SQL server databases.

We are looking for feedback and suggestions!

Please send any emails concerning the 5.2 beta to helpdesk@lansweeper.com, as this will allow us to test the Lansweeper help desk we’re working on.
(The help desk is not included in the 5.2 beta. We’re only doing internal help desk testing for now.)

Disclaimer
Beta releases are likely to contain bugs. To avoid loss of data or functionality, we recommend that you either install Lansweeper 5.2 on a test server or back up your production environment prior to upgrading. Upgrade instructions can be found in our online documentation. Note that you’ll be able to upgrade from the 5.2 beta to the final release version (when it becomes available).

To take a backup of your database:
- Create a copy of Program Files (x86)\Lansweeper\SQLData\lansweeperdb.sdf, if you are using SQL Compact as your database server.
- Right- click on the lansweeperdb database in SQL Server Management Studio and select Tasks\Back Up, if you are using SQL Server as your database server. If SQL Server Management Studio isn’t installed on your Lansweeper server, we recommend downloading it online. (You will need to perform a search for the Management Studio that’s compatible with your particular edition and version of SQL Server.)

Bug reports
If you believe you’ve found a bug or are experiencing another technical issue, please upgrade to the latest beta release first and see if the issue persists. Upgrade instructions can be found in our online documentation. If the issue does persist, contact helpdesk@lansweeper.com and provide us with:
- Screenshots of the problem, if possible.
- A detailed description of the problem: which steps are you taking, what do you expect to happen and what is actually happening?
- Any logs present in Program Files (x86)\Lansweeper\Install on your Lansweeper server.
- Program Files (x86)\Lansweeper\Service\Errorlog.txt.
- Program Files (x86)\Lansweeper\Website\App_Data\errorlog.txt, if this file exists.
- Your browser name and version number.