SpaceGuard SRM - Tools4Ever.com

Release Notes11. When importing quotas from SpaceGuard 4.2 the client could crash when parsing entrieswith multiple Email addresses. (1067, 10-13 2003)12. When revoking access on Windows 2000/2003/XP the security entries where not orderedcorrectly. (1067, 10-13 2003)13. Several cosmetic fixes (1067, 10-13, 2003)14. Fixed a crash when stopping the SpaceGuard SRM service on Windows 2003 (1067, 10-13, 2003)15. On Windows 2003 the reset revoke access could fail because of incorrect rightsassignments. (1067 10-13, 2003)16. A compatibility issue regarding RFC 821 when using the SMTP alarm action has beenfixed. (1067 10-13, 2003)Version 5.2 (1053), August 29, 20031. Engine optimization: the SpaceGuard SRM engine no longer needs to resolve user SID'swhen revoking access or resetting access rights. This results in increased engine speedand decreases the number instances of 1338 and 1332 error messages in theSpaceGuard log where the operating system was not able to resolve a user SID. (1051,07-31 2003)2. When editing the size of Auto-Add policies, the add percentage and add absolute valuewere not properly recalculated. (1051, 07-31 2003)3. In some cases the SpaceGuard SRM service could crash when automatically removingquotas for directories that had been deleted. (1053, 08-29 2003)4. Several issues with revoke access: Revoke access could enter a 'broken state'; Whenencountering a (minor) error the revoke or reset revoke would stop. (1053, 08-29 2003)5. When installing the service to a directory without spaces the pathname would becomeinvalid. (1053, 08-29 2003)Version 5.1 (1048), June 27, 20031. The 'service setup' dialog always displayed the 'DEMO' license code even though thelicense was entered. (1044, 06-16 2003)2. Email alarm actions were only sent once after the alarm was triggered. (1044, 06-162003)3. When trying to install the SpaceGuard SRM service on a backup domain controller or amember server, the installation failed because the service account rights could not be set.(1044, 06-16 2003)4. When the demo expired the license information was displayed incorrectly. (1044, 06-162003)5. When a valid license code was entered after the DEMO period expired, the serviceengine did not restart immediately. (1044 06-16 2003)6. When sorting the main overview window with the quota state the quotas were not sortedcorrectly (1044, 06-16 2003)7. When the access to a directory was revoked, the SpaceGuard SRM service was notalways able to reset the permissions (1044 06-16 2003)8. When importing email addresses from SpaceGuard 4.2 the 'smtp:' keyword was parsedincorrectly. (1046, 06-19 2003)9. When importing from SpaceGuard 4.2 the import will no longer terminate whenencountering inconsistencies in the database files. (1046, 06-19 2003)10. Several cosmetic changes. (1046, 06-19 2003)11. When importing large amounts of quotas from SpaceGuard 4.2 the client terminatedunexpectedly. (1048, 06-27 2003)Version 5.0 (1030), May 9, 20039