SpaceGuard SRM - Knowledge
Base |
| |
General information |
| 1. |
SRM10132003A: What
is the difference between RESET and RESETFAST when
using
the SpaceGuard
SRM SGFS Access Analyzer? |
| 2. |
SRM10102003A: Does
SpaceGuard SRM support Microsoft Clustering in Active-Passive
and Active-Active Configurations? |
| 3. |
SRM09152003A:
Do the Blaster and the recently released Blaster2
RPC patches (MS
KB824146) from Microsoft affect SpaceGuard SRM
performance? |
| 4. |
SRM09012003B: 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? |
| 5. |
SRM09012003J: Does SpaceGuard SRM work in workgroup
environments without any domain? |
|
| |
How To's
|
| 1. |
SRM11262003A: How do I configure MAPI email for
SpaceGuard SRM? |
| 2. |
SRM11132003A: When using Auto-Add quota's, how
can I define a single disk quota policy so that all
my users automatically have revoke access and
email alarm actions? |
| 3. |
SRM09012003N: How
can I have SpaceGuard SRM automatically resolve
the username associated to a home directory and
execute alarm actions on that user, e.g. send popups
or email messages to all my users when they exceed
their home directories (e.g. H:\UserData\JSmith,
username = JSmith)? |
| 4. |
SRM09012003G: How
does the graphical disk quota bar work, why are the
color positions always the same? |
| 5. |
SRM09012003R: Can
I assign multiple groups to a single revoke access
alarm action, for instance separated by a comma
(DOMAINA\GROUP1, DOMAINA\GROUP2)? |
| 6. |
SRM09012003A: 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? |
| 7. |
SRM09012003S: How
do I find the port which the SpaceGuard SRM service
is currently using for its TCP/IP based RPC communication? |
|
| |
Troubleshooting |
| 1. |
SRM11212003A: When I use the test button on the
popup alarm action configuration window, I never
get the popup message, what is wrong? |
| 2. |
SRM11172003A: When running SpaceGuard SRM on Windows
2003, I get the error "permissions
are
incorrectly ordered". Also, when removing the
remoke access, permissions are not
being reset as they should. How do I solve this? |
| 3. |
SRM11102003A: Popup messages sent by SpaceGuard
SRM do not arrive at their destination, what steps
can take to troubleshoot popups? |
| 4. |
SRM11032003A: When
sending MAPI email alarm actions using SpaceGuard
SRM, the messages do not arrive while the profile
has been configured correctly and works using Outlook.
Also, when testing the MAPI email alarm action, the
SpaceGuard SRM dialog box displaying the sending
status stays on the desktop for a long time. I have
installed Outlook XP (2002) locally on the server.
What is wrong? |
| 5. |
SRM10152003A: When
upgrading the SpaceGuard SRM service to a newer
version, the operation fails and
my log displays an error message. What can I do
to solve this?
|
| 6. |
SRM09152003B: I have a large
number of home directories (several thousands) and
I'm using an Auto-Add user quota to provide an automatic
user quota for each home directory. This process seems
to be very slow, what could be wrong? |
| 7. |
SRM09012003B: 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? |
| 8. |
SRM09012003F: When installing the SpaceGuard SRM
service, I get an LSA error with code 1073741433.
What should I
do? |
| 9. |
SRM09012003Q: 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? |
| 10. |
SRM09012003R: Can I assign multiple groups to a
single revoke access alarm action, for instance separated
by a
comma (DOMAINA\GROUP1, DOMAINA\GROUP2)? |
| 11. |
SRM09012003T: The application log on the computer
running the SpaceGuard SRM service displays lots
of 2273 error
codes. What do these errors mean? |
| 12. |
SRM09012003V: 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? |
|
| |
Upgrade and licensing
information |
| 1. |
SRM09012003A:
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? |
| 2. |
SRM09012003D: Can I run both SpaceGuard SRM and
SpaceGuard 4.2 on the same server? |
| 3. |
SRM09012003E: Can I upgrade my quotas, auto-add
quotas, user and administrative actions and user
defined messages
from SpaceGuard 4.2 to SpaceGuard SRM? |
| 4. |
SRM09012003H: In SpaceGuard 4.2, the service used
to automatically stop when the license was expired.
Does SpaceGuard
SRM behave the same? |
| 5. |
SRM09012003I: 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? |
|
| |
SpaceGuard 4.2 vs. SpaceGuard
SRM |
| 1. |
SRM09012003C: Does SpaceGuard SRM have
import/export capabilities like SpaceGuard 4.2 does? |
| 2. |
SRM09012003K: Does SpaceGuard SRM automatically
delete quotas when the source directory has been
removed? SpaceGuard
4.2 used to maintain "ghost" quotas for
these directories. |
| 3. |
SRM09012003L: SpaceGuard 4.2 auto-add quotas did
not support directory exclusions, does SpaceGuard
SRM support
this? |
| 4. |
SRM09012003D: Can I
run both SpaceGuard SRM and SpaceGuard 4.2 on the
same server? |
| 5. |
SRM09012003E: Can I
upgrade my quotas, auto-add quotas, user and administrative
actions and user defined messages from SpaceGuard
4.2 to SpaceGuard SRM? |
| 6. |
SRM09012003H: In SpaceGuard
4.2, the service used to automatically stop when
the license was expired. Does SpaceGuard SRM behave
the same? |
| 7. |
SRM09012003I: 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? |
| 8. |
SRM09012003M: SpaceGuard 4.2 had a warning and
maximum limit, how can I make this work in SpaceGuard
SRM? |
| 9. |
SRM09012003O: 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? |
| 10. |
SRM09012003P: In SpaceGuard 4.2, when I removed
a disk 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? |
|
|
| |
| Q |
SRM11212003A: When I
use the test button on the popup alarm action
configuration
window, I never
get the popup message, what is wrong? SpaceGuard
SRM shows an error similar to the one below:
Log session started at 16:59:58, 11/20/03.
16:59:10 11/20/2003 Error sending a popup message
to %RELATIVE_QUOTA_DIRECTORY%. Errorcode 2273.
The message alias could not be found on the network.
(2273)
16:59:10 11/20/2003 An error occurred while sending
a test popup message to %RELATIVE_QUOTA_DIRECTORY%.
Errorcode -1. (-1)
16:59:10 11/20/2003 Error testing alarm action.
Errorcode -1 (-1)
16:59:10 11/20/2003 The service on computer W2KSERVER
was unable to process the sent data. Errorcode
-1. (-1)
Log session ended at 16:59:58, 11/20/03. |
| A |
SpaceGuard SRM cannot send test popup messages
to a keyword. This only works when applied to a
directory so SpaceGuard SRM can resolve the keyword
to a part of the directory name. Specify a valid
username and try again. |
|
| |
| Q |
SRM11172003A: When running
SpaceGuard SRM on Windows 2003 or Windows 2000
SP3 and SP4, I get the error "permissions
are incorrectly ordered". Also, when removing
the revoke access, permissions are not being
reset as they should. How do I solve this? |
| A |
In newer versions of the Windows operating system,
Microsoft has changed the ordering method of the
Access Control Lists (ACLs) on files and folders.
SpaceGuard SRM 5.3 build 1067 and later has been
updated to reflect these changes. If you receive
this error message, make sure to perform the steps
below: |
| |
| 1. |
Upgrade to SpaceGuard SRM 5.3 build 1067
or later. |
| 2. |
In the SpaceGuard SRM console, remove all
quotas that have been revoked. |
| 3. |
Manually reset the permissions on your directories.
To do so, go to the security properties of
the folder, click the "Advanced" button. In
the following dialog box, set your custom security
properties and make sure to check the box "Reset
permissions on all child objects and enable
propagation of inheritable permissions". Next,
go to the "Owner" tab, make sure the correct
owner is selected and check the box "Replace
owner on subcontainers and objects". Apply
these settings. |
| 4. |
Reapply the quotas that have been revoked. |
|
|
| |
| Q |
SRM11132003A: When using
Auto-Add quota's, how can I define a single quota
policy so that all
my users automatically have revoke access and
email alarm actions? |
| A |
An Auto-Add disk quota will only work if you use
keywords as user targets for the alarm actions,
otherwise all quotas will be pointed on a single
user. Use the keyword %RELATIVE_QUOTA_DIRECTORY%
for the revoke access alarm action and for the
MAPI email alarm action. The requirement for this
operation is that the last part of the user home
directory is equal to the username and that the
username is equal to the Exchange mailbox alias
name. |
|
| |
| Q |
SRM11032003A: When
sending MAPI email alarm actions using SpaceGuard
SRM, the messages do not arrive while the profile
has been configured correctly and works using Outlook.
Also, when testing the MAPI email alarm action, the
SpaceGuard SRM dialog box displaying the sending
status stays on the desktop for a long time. What
is wrong? |
| A |
When using Outlook 2000 with the Email security
patch or Outlook 2002, SpaceGuard SRM will encounter
a blocking mechanism built by Microsoft to improve
email security. Normally, this would result in
a popup which can be acknowledged by the user working
at the computer, but since the SpaceGuard SRM service
handles the MAPI alarm actions, the popup will
be not displayed and cannot be acknowledged. To
avoid these popup messages, the security settings
need to be modified using a custom policy. |
| |
Additional link: Tools4ever SRM KB - SRM11032003A |
|
| |
| Q |
SRM10152003A: When
upgrading the SpaceGuard SRM service to a newer version,
the operation fails and my log displays
an error similar to the one below:
Log session started at 15:51:43, 10/13/03.
15:50:38 10/13/2003 Error copying file C:\Program Files\Tools4ever\SpaceGuard
SRM\SgMsg.dll to to the directory \\<COMPUTER>\_T4E_TMP_SHARE_3371_$\Program
Files\SpaceGuard Service\ on computer <COMPUTER>. Errorcode 1224. The requested
operation cannot be performed on a file with a user-mapped section open.
(1224)
15:50:38 10/13/2003 An error occurred while copying service files to the directory
C:\Program Files\SpaceGuard Service on computer <COMPUTER>. Errorcode
1224. (1224)
15:50:38 10/13/2003 An error occurred while installing the service on computer <COMPUTER>.
Errorcode 1224. (1224)
Log session ended at 15:51:43, 10/13/03. |
| A |
The event viewer is open while updating the SpaceGuard
SRM service, hence the SpaceGuard SRM event message
DLL (SgMsg.dll) is in use and cannot be replaced.
Close the event viewer and try upgrading the service
again. |
|
| |
| Q |
SRM10132003A: What is
the difference between RESET and RESETFAST when
using the SpaceGuard SRM SGFS Access Analyzer? |
| A |
SpaceGuard SRM includes a command line utility
that can reset all access rights on directories revoked
by the SpaceGuard SRM disk quota engine. The access rights
will be reset to their original state before SpaceGuard
SRM was installed. To reset the access rights, SGFS
has two options: RESET and RESETFAST. The difference
between these options is that RESETFAST doesn't resolve
each user SID at the domain to improve speed. You
can safely use this option, the only side effect
is that SGFS will not list the names of the users
in its output because they are not resolved: |
| |
SGFS F:\music\rock RESET |
| |
File/Dir: F:\music\rock\ledzeppelin, Owner:
BUILTIN/Administrators
Type Flags(H) Size Mask(H) Account name
0 3(H) 20 001f01ff(H) \Everyone
|
| |
SGFS F:\music\rock RESETFAST |
| |
File/Dir: F:\music\rock\ledzeppelin |
|
| |
| Q |
SRM10102003A: Does SpaceGuard
SRM support Microsoft Clustering in Active-Passive
and Active-Active Configurations? |
| A |
Yes, SpaceGuard SRM version 5.3 build 1061 or later
can be used on Microsoft Cluster configurations.
No special additions are needed. All Microsoft Cluster
configurations (Active-Active, Active-Passive) are
supported. It will only take a few minutes to install
the SpaceGuard SRM service on a cluster configuration.
The main purpose of a cluster is protection of data.
For SpaceGuard SRM this means that if one of the
servers of the cluster fails the other server can
take over the monitoring of the quotas. |
| |
How To Install? |
| |
NOTE: The SpaceGuard SRM service does not have
to be defined as a generic service on the cluster.
- Install the SpaceGuard SRM service on all
nodes in the cluster. Please make sure that
the 'Enable cluster software' checkbox in the
advanced
section is checked. (Note: This option can
also be enabled after service installation.
- Make sure that both servers have the same "configuration
path" specified. This path is a relative
path and is created on each shared cluster
disk.
Look in the online HTML or PDF manual
for more information on cluster configuration.
|
|
| |
| Q |
SRM09152003A: Do the
Blaster and the recently released Blaster2 RPC
patches (MS
KB824146) from Microsoft affect SpaceGuard
SRM performance? |
| A |
While SpaceGuard SRM uses authenticated RPC to
communicate between service and client, installing
both patches does not affect SpaceGuard SRM operation
and/or performance. |
|
| |
| Q |
SRM09152003B: I have
a large number of home directories (several thousands)
and I'm using an Auto-Add disk quota to provide an automatic
disk quota for each home directory. This process seems
to be very slow, what could be wrong? |
| A |
When working with several thousands of directories,
SpaceGuard SRM will internally address a buffer for
each subfolder. When using large numbers, this buffer
size will consume lots of memory, thereby decreasing
the engine performance. To remedy this, set an empty
disk quota (no limits) on the Auto-Add quota root (this
will work on top of the already existing Auto-Add
quota). We will address this issue in the next SpaceGuard
SRM version. |
|
| |
| Q |
SRM09012003A: 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 |
The latest production version of SpaceGuard SRM
is
6.0 Build 1114. To update your version, go to the Tools4ever download
section and click the appropriate download button.
When the download is complete, run and complete the
installation wizard using the "Modify" option.
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 |
SRM09012003B: 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 |
SRM09012003C: Does SpaceGuard SRM have
import/export capabilities like SpaceGuard 4.2
does? |
| A |
Yes, SpaceGuard SRM can export/import disk 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 later, please use the migration
wizard included in SpaceGuard SRM. |
|
| |
| Q |
SRM09012003D: 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. Look here for
more information. |
|
| |
| Q |
SRM09012003E: 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.
Look here for
more information. |
|
| |
| Q |
SRM09012003F: 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 priviliges on existing user accounts. |
|
| |
| Q |
SRM09012003G: How does the
graphical disk quota bar work, why are the color positions
always
the
same? |
| A |
The graphical disk quota bar in the quota overview window
shows the quota size as the middle divider and all
limits. On the left side of the disk quota size, the bar
will always be green, where on the right-hand side
it will be red. By looking at the disk 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 |
SRM09012003H: 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 |
SRM09012003I: 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,
please look here for
more information. |
|
| |
| Q |
SRM09012003J: 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. In a workgroup scenario,
the license key is based on the workgroup name instead
of a domain name. |
|
| |
| Q |
SRM09012003K: 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 disk quota is automatically removed. |
|
| |
| Q |
SRM09012003L: 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 |
SRM09012003M: 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
Limit 1: 80%, send a popup to the user assigned to the quota. (exceeds 40MB)
Limit 2: 90%, send a popup to the administrator. (exceeds 45MB)
Limit 3: 100%, revoke the write access of the user assigned to the quota.
(exceeds 50MB)
|
|
| |
| Q |
SRM09012003N: How can
I have SpaceGuard SRM automatically resolve the
username associated to a home directory and execute
alarm actions on that user, e.g. 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 |
SRM09012003O: 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 |
SRM09012003P: In SpaceGuard
4.2, when I removed a disk 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 |
SRM09012003Q: 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. For more
information, look
here. |
|
| |
| Q |
SRM09012003R: 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 |
SRM09012003S: 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 |
SRM09012003T: 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 user 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 |
SRM09012003U: 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 |
SRM09012003V: 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 behaviour is normal, if you wait several
seconds more before accessing the properties, all
information will be available. |
|
| |
