dSupportSuite v126.96.36.199 Release
Today dSupportSuite v188.8.131.52 was released to address a few issues, and also contains updates to the configuration interface to group some items more intuitively and make it easier to work with.
The online config manual is also being updated to reflect the interface changes, as well as added links to specific points in the video (although with the old interface) that describes thoroughly all of the same features and functionality!
- Scheduled maintenance failed to start (only on some systems) although maintenance always worked properly when run from the user interface.
- CCleaner custom app required an update to the default app configuration as well as the dSupportSuite binary itself, to address a new download method. This would have failed in previous configurations.
- Although this should not have been a problem for the maintenance task as a whole, some people have reported when CCleaner ran that maintenance would stall indefinitely or even stop altogether and restart itself a second time. We were not able to reproduce either issue, however at least in the case of the restart, the reporting user now says it is no longer an issue.
- One user states the update may not have fixed his CCleaner download although I have not received a confirmation on the version (dSupportSuite was updated once earlier today to v184.108.40.206 in order to address the first issue above, not this one.) The user is now hosting the file himself which is working of course.
My thoughts on app downloads in general are that any user with app download issues can always self-host the download file on their own web server, which brings other benefits: Control in updating.
It may be that you would like to test some 3rd party software’s update before allowing it to run automatically on your customer machines! Let’s face it, the latest isn’t always the greatest.
Also what about the potential for disaster? For example it was a year or two ago when I believe it was CCleaner itself that was inadvertently released with malicious tampering to the installation files, causing users systems to get infected. While it wasn’t long before the issue was resolved, you wouldn’t want your customers’ systems automatically downloading this as part of maintenance for example.
If you were self-hosting the file download, chances are you would know about any problems before you updated it on your web host, therefore your customer’s systems wouldn’t be affected.
Food for thought…