Upgrading from version 4.2

SpaceGuard SRM is a completely new SpaceGuard, therefore all configuration information and disk quota settings made in SpaceGuard 4.2 or before cannot be used with SpaceGuard SRM. Also, SpaceGuard 4.2 and SpaceGuard SRM license code are not compatible. To use SpaceGuard SRM, you will need new license codes, look here for more information.

Quota and settings migration

SpaceGuard SRM 5.1 or later features a migration wizard to import all SpaceGuard 4.2 quotas, auto-add quotas, user and administrative actions and user configured messages to SpaceGuard SRM. This migration wizard will NOT delete any SpaceGuard 4.2 information in the migration process. The migration wizard requires both the SpaceGuard 4.2 and SpaceGuard SRM 5.1+ service to be installed on the same computer, while the migration operation may be started from a remote SpaceGuard SRM 5.1+ client. To run the migration wizard:

Install the latest version (6.0 Build 1114) of the SpaceGuard SRM client software.
Install a SpaceGuard SRM service.
Choose File -> Import -> From SpaceGuard 4.2...
Add the computer running a SpaceGuard 4.2 service (the SpaceGuard 4.2 service doesn't have to be running for the migration to work).
Choose the migration options. Tools4ever strongly recommends stopping the SpaceGuard 4.2 service and setting its startup type to "manual". The migration wizard enables this option by default.
Click Finish to start importing all SpaceGuard 4.2 settings.
The migration may complete with one or more errors. SpaceGuard SRM produces a detailed import log located in the folder <COMPUTERNAME>_SG42 inside the SpaceGuard SRM client program files directory. These errors may be due to inconsistencies in the original SpaceGuard 4.2 configuration files. Whenever such an error occurs in the "names.db" file, the corresponding alarm actions in SpaceGuard SRM will be filled with "(import error)". When the error occurs in the "spaceOb.db" file, the corresponding disk quota will be ignored.
Use the Quota overview on the target computer to verify the migration completion status.
Uninstall both the SpaceGuard 4.2 client and service by running the original SGNT.EXE setup file.
Do NOT remove the SpaceGuard 4.2 service account (default username: 'spaceguard') immediately after the migration process. When migrating, the SpaceGuard SRM disk quota engine needs this old service account to reset and update the access rights on all quota directories. When removing the old service account, please verify the engine completion status by checking the access rights on your quota directories.

For more information, please consult the SpaceGuard SRM online manual.

Upgrade pricing and support

SpaceGuard 4.2 and SpaceGuard SRM are separate products and require different license codes to operate. All existing customers with a valid maintenance contract can upgrade to SpaceGuard SRM at no charge. If you own SpaceGuard 4.2 but are not on support, you must renew support in order to upgrade to SpaceGuard SRM at no charge. To summarize,

Customers on support	Free upgrade to SpaceGuard SRM, contact your local Tools4ever partner for new license codes.
Customers not on support	Customers not on support will be required to upgrade, or buy the new product outright in order to receive license codes for SpaceGuard SRM.

We will provide support for SpaceGuard 4.2 until the end of 2004.