|
| |
 |
|
SpaceGuard SRM - Knowledge Base | | |  General information | | | Does SpaceGuard SRM support Microsoft Clustering in Active-Passive and Active-Active Configurations? | | 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. | | | Does SpaceGuard SRM work in workgroup environments without any domain? | | 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. | | | | | | How To | | | 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? | 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. The automatic user assignment will resolve the users which are linked to the directory in either the Active Directory or in the permissions. This user will then be used as target for alarm actions such as popup, e-mail or revoke access. | | | Can I assign multiple groups to a single revoke access alarm action, for instance separated by a comma (DOMAINA\GROUP1, DOMAINA\GROUP2)? | | Yes this feature has been implemented in SpaceGuard SRM 6.0 build 1098 or later. The automatic user assignment is now able to resolve multiple users or groups on a folder based on permissions. You can define filters for user or group names and which permissions should be included in the resolve action. You can also directly assign multiple users or groups in the user interface by choosing a manual target for each alarm action. | | | 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? | | The latest production version of SpaceGuard SRM is 6.1 Build 1115. To update your version, go to the Tools4ever upgrade section. During the upgrade process your license code is required for validation. 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. | | | How do I find the port which the SpaceGuard SRM service is currently using for its TCP/IP based RPC communication? | | 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. In SpaceGuard SRM version 5.4 build 1090 or later, the service version and build number is no longer included in the display name, but in the registry key. Look for the key HKEY_LOCAL_MACHINE\SOFTWARE\Tools4ever\SpaceGuard\Service\Version, which contains version and port information. | | | | | | Troubleshooting | | | When I use the test button on the popup alarm action configuration window, I never get the popup message, what is wrong? | 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. | | | Popup messages sent by SpaceGuard SRM do not arrive at their destination, what steps can take to troubleshoot popups? | | Please consult the following forum topic for detailed information: http://forum.tools4ever.com/viewtopic.php?t=29 | | | 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? | | 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 | | | 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? | | Please consult the following forum topic for detailed information: http://forum.tools4ever.com/viewtopic.php?t=188 | | | The application log on the computer running the SpaceGuard SRM service displays lots of 2273 error codes. What do these errors mean? | | Error code 2273 is related to popup messages which have not arrived at their destination. Microsoft introduced default popup blocking (not Internet Explorer popups) in Windows XP Service Pack 2 and Windows Server 2003. Please consult the following forum topic for detailed information: http://forum.tools4ever.com/viewtopic.php?t=188 | | | | | |
|
