SpaceGuard SRM
|
Q: |
How do I upgrade my version of SpaceGuard SRM to the latest production version? Do I need to reinstall or do I need to backup my configuration? |
| A: | Download the latest version and run the installation file. When starting the new SpaceGuard SRM version and connecting to a service, you will notice that SpaceGuard SRM asks for an update confirmation. Click "Yes" to automatically update the SpaceGuard SRM service. All configuration information will be retained. |
Q: |
Your website states that SpaceGuard SRM supports MAPI Exchange integration for sending alarm actions, but I can't find it in my version. What is wrong? |
| A: | SpaceGuard SRM supports MAPI since version 5.2. A new tab has been added to the service configuration (Right-click computer in network tree, Service Management -> Configuration... -> MAPI E-mail tab). Use this tab to configure a MAPI profile so SpaceGuard SRM can login on the Exchange server and send out email. Once a profile has been setup, you can use the MAPI E-mail alarm action and specify an Exchange alias as email target. More information is available in the SpaceGuard SRM manual. |
Q: |
Does SpaceGuard SRM have import/export capabilities like SpaceGuard 4.2 does? |
| A: | Yes, SpaceGuard SRM can export/import quota configuration settings. However, exported settings from 4.2 cannot be imported in SRM 5.x or later and vice versa. To transfer configuration settings from SpaceGuard 4.2 to SRM 5.x or late. |
Q: |
Can I run both SpaceGuard SRM and SpaceGuard 4.2 on the same server? |
| A: | You should only run both the SpaceGuard 4.2 and the SpaceGuard SRM on the same computer when running the migration wizard. |
| Q: | Can I upgrade my quotas, auto-add quotas, user and administrative actions and user defined messages from SpaceGuard 4.2 to SpaceGuard SRM? |
| A: | Yes, SpaceGuard SRM 5.1 has a migration wizard which fully migrates all SpaceGuard 4.2 settings. |
| Q: | When installing the SpaceGuard SRM service, I get an LSA error with code 1073741433. What should I do? |
| A: | This issue has been fixed in SpaceGuard SRM 5.1 build 1046. Please upgrade to version 5.1 build 1046 and try to install the service again. SpaceGuard SRM will now also correctly update and assign all correct privileges on existing user accounts. |
| Q: | How does the graphical quota bar work, why are the color positions always the same? |
| A: | The graphical quota bar in the quota overview window shows the quota size as the middle divider and all limits. On the left side of the quota size, the bar will always be green, where on the right-hand side it will be red. By looking at the quota bar, you can quickly determine if one or more limits have been exceeded and if the current size is more than the quota size. |
| Q: | In SpaceGuard 4.2, the service used to automatically stop when the license was expired. Does SpaceGuard SRM behave the same? |
| A: | No, SpaceGuard SRM will not automatically stop the service when the demo period has been expired. New quota's cannot be added or modified, only deleted and alarm actions will not be executed. If a license code has been specified and validated, SpaceGuard SRM will resume all activities. |
| Q: | I have just upgraded to SpaceGuard SRM, but it won't accept my license code you gave me when I bought version 4.2. What is wrong? |
| A: | The SpaceGuard 4.2 and SRM license codes are incompatible. To use SpaceGuard SRM, you will need a license code. |
| Q: | Does SpaceGuard SRM work in workgroup environments without any domain? |
| A: | Yes, SpaceGuard SRM can directly connect to local services installed on any computer in a LAN environment. If the computer is not browsable in the network tree, you can add the computer manually, specify its NETBIOS name and then install a service. |
| Q: | Does SpaceGuard SRM automatically delete quotas when the source directory has been removed? SpaceGuard 4.2 used to maintain "ghost" quotas for these directories. |
| A: | Yes, SpaceGuard SRM's engine continuously monitors the file system and correctly removes quotas in case its directory no longer exists. Also, when directories are renamed, the quota is automatically removed. |
| Q: | SpaceGuard 4.2 auto-add quotas did not support directory exclusions, does SpaceGuard SRM support this? |
| A: | Yes, SpaceGuard SRM 5.1 or later features auto-add quotas including directory exclusions per auto-add quota. |
| Q: | SpaceGuard 4.2 had a warning and maximum limit, how can I make this work in SpaceGuard SRM? |
| A: | SpaceGuard SRM features unlimited limits, so you can define limits like this: Quota size: 50MB |
| Q: | How can I have SpaceGuard SRM automatically send popups or email messages to all my users when they exceed their home directories (e.g. H:\UserData\JSmith, username = JSmith)? |
| A: | You can use the %RELATIVE_QUOTA_DIRECTORY% keyword, which resolves the last part of any directory string. When specified in an alarm action, you can have SpaceGuard use this as the actual username. |
| Q: | SpaceGuard 4.2 had a detection tab where you could specify the engine scan rate to improve performance. Why doesn't SpaceGuard SRM have this option? |
| A: | SpaceGuard SRM's engine is radically faster compared to 4.2's engine, so this option has become effectively obsolete. SpaceGuard SRM's engine always works in real-time without degrading server performance. |
| Q: | In SpaceGuard 4.2, when I removed a quota that had its access revoked, SpaceGuard would not reset the access rights and I was forced to use the SGFS.EXE command utility. What does SpaceGuard SRM do when deleting quotas? |
| A: | When removing quotas, SpaceGuard SRM will completely revert the directory back to its original ACL state by resetting all access rights. |
| Q: | I've just tried importing my SpaceGuard 4.2 quotas with SpaceGuard SRM 5.1 build 1044 and I'm getting all kinds of errors. What should I do? |
| A: | The migration wizard in SpaceGuard SRM 5.1 build 1044 has a specific issue with importing smtp user targets. Also, when dealing with corrupted configuration information, the complete import operation is cancelled. Please upgrade to version 5.1 build 1046 or later, then delete all migrated quotas and run the migration wizard again. |
| Q: | Can I assign multiple groups to a single revoke access alarm action, for instance separated by a comma (DOMAINA\GROUP1, DOMAINA\GROUP2)? |
| A: | No, SpaceGuard SRM supports assigning a single group to a revoke access limit. No more than 1 revoke alarm action is allowed per quota. |
| Q: | How do I find the port which the SpaceGuard SRM service is currently using for its TCP/IP based RPC communication? |
| A: | The port number is listed in the service display name in either the service control manager (NT4) or the services MMC-Snapin (W2K/W2003). For instance, "SpaceGuard Service ((46185,1046))" means port number 46185 and build number 1046. |
| Q: | The application log on the computer running the SpaceGuard SRM service displays lots of 2273 error codes. What do these errors mean? |
| A: | Error code 2273 means that the target user assigned to a quota limit is not currently logged on to the network, so that popup messages have failed to arrive at their destination. Note that sending the messages completes successfully, and that Windows reports this error message when it fails to find any computer to deliver the alert. |
| Q: | When migrating my quota's from SpaceGuard 4.2, the process seems to complete but then the SpaceGuard client suddenly terminates. When I restart, no quotas are visible, what is wrong? |
| A: | This is an issue in SpaceGuard SRM 5.1 build 1046 and earlier. Please upgrade to version 5.1 build 1048 or later, then rerun the migration wizard. |
| Q: | When I modify some properties of one of my quotas (e.g. new limit or alarm action) and click OK, then immediately access the properties again, the settings appear to be missing, what is wrong? |
| A: | SpaceGuard SRM is a client/server based application and all settings are saved on the service side. This means that the SpaceGuard SRM client has to transmit all settings to the service which may take a second or more depending on network connectivity. When you access the same settings again, the information will be retrieved from the service which hasn't been updated yet. This behavior is normal, if you wait several seconds more before accessing the properties, all information will be available. |
 |
ADDITIONAL INFORMATIONDisk Quota Options
|
 |
VIDEOS
|