Before You Upgrade to 1.0.1.63
Posted: Tue Feb 02, 2016 1:27 pm
If you are upgrading Cleaner for LabTech from a earlier version to 1.0.1.63 there is some maintenance you need to do afterwards to fully upgrade the system.
We discovered a bug in our encoding and decoding processes where different platforms would cause inconsistent output from our decoders. This was due to the encoder type we used and the cross platform issues with that algorithm. We have switched to a more universal one and have seen the bug disappear.
To complete the update you will need to open the failed installs manager by selecting the hammer/gear in the licensing section of the global manager.
New select the Path Decode Test button to start the test and to make the corrections that may be needed.
The test will try to decode each agents path and if it fails to decode correctly it will test the system for a real path and correct the path data for that system. if the system decodes correctly it will skip it or if the system fails and is offline and can not be verified it will also be skipped.
This means any offline systems that fail will need to have this test run against them again when available for verification.
This repair will not prevent the normal automated cleanings from taking place on the systems but will correct several other minor issues when manually managing systems.
Post any issues here that you may have with this process and we will work with you to get them resolved.
We discovered a bug in our encoding and decoding processes where different platforms would cause inconsistent output from our decoders. This was due to the encoder type we used and the cross platform issues with that algorithm. We have switched to a more universal one and have seen the bug disappear.
To complete the update you will need to open the failed installs manager by selecting the hammer/gear in the licensing section of the global manager.
New select the Path Decode Test button to start the test and to make the corrections that may be needed.
The test will try to decode each agents path and if it fails to decode correctly it will test the system for a real path and correct the path data for that system. if the system decodes correctly it will skip it or if the system fails and is offline and can not be verified it will also be skipped.
This means any offline systems that fail will need to have this test run against them again when available for verification.
This repair will not prevent the normal automated cleanings from taking place on the systems but will correct several other minor issues when manually managing systems.
Post any issues here that you may have with this process and we will work with you to get them resolved.