around 10% of all Safeboot clients got problems updating Safeboot from version 5.2.3 to 5.2.8.
1. Problem: Deactivated Safeboot machines got activated automatically (see attachment 1Problem_Deactivated.txt). How could we prevent this the next time?
2. Problem: We found out that a lot machined do not synchronize with the server. One solution would be to use the emergency boot function of Safetech. But that costs a lot of time. (see attachment 2Synchronization.txt) Could we fix the problem remotely?
3. Problem: With the new installation set we got a problem installing Safeboot on new machines with SMS. Nearly every second strike fails. How could I make a troubleshooting in this case?
I would appreciate every help.
AngeloNachricht geändert durch aferrante on 02.10.11 13:48:09 CDT
for problem 1, the machine must exist in the DB, but have the policy set to "disable" - you must have changed that to "enable" at some point, because the machine went from doing nothing (because it was told to be disabled), to activating (meaning the machine was set to something else).
Does the user have compression in the root of C? That will cause the error you are seeing.
For 2, your pre-boot was corrupted prior to upgrade - the new version has additional code to fix it (if possible).
for 3 - you need to supply some evidence of the problem.