ERM will no longer be available for purchase after December 31st, 2009. Existing ERM customers may continue using ERM. 

Verify that a mailbox exists for the resource you are attempting to manage and that the mailbox resides on the ERM host server.

Creating an OU in Active Directory Users and Computers to contain your resource accounts is recommended, but not required.  The “Resources” folder seen in the ERM product documentation is an OU in Active Directory.

1) Download the password change utility from ERMSvcAccPWChange.zip. If you're running ERM 1.2 or earlier, please download ERM1_2_SvcAccPWChange.zip.
2) Reset the password for the service account in Active Directory.
3) From a command prompt on the Exchange server hosting ERM, please run the utility by typing ERMSvcAccPWChange. You will be prompted for the new password.

ERM uses a database on its host server to store global and resource configuration information. Additionally, ERM writes to an existing attribute of the Active Directory to indicate an ERM-enabled resource.

ERM responses are based on the Exchange 2000/2003 store event sink object model. An event registration item is created in the Inbox of the mailbox as an "associated item". The event registration is not visible with Outlook, but can be seen with MDBVue32, OutlookSpy, or the regevent.vbs script from the Exchange SDK. There is not a "service" in the sense of a Windows 2000or 2003 service that appears in the Services MMC. There is, however, a registered COM+ application that is visible in the Component Services MMC. This component is called by the Exchange Event engine when triggered by an item that matches the event registration criteria.

We understand the criticality of the Exchange server environment and are very diligent in our efforts to avoid negatively impacting server performance. We are not aware of any performance degradation as a result of running ERM, though memory utilization is dependent on the number of concurrent messages being processed by ERM-managed mailboxes.

The ERM database uses a very small amount of disk space. 100 records use approximately 1.5 Megabytes of storage space. 1000 records use approximately 1.7 Megabytes of storage space.

Yes, logging levels are adjustable so you are in control of the level of logging that appears in the ERM log files.

Ensure that the RUS has processed the mailbox of the resource. To force an update, log in to the resource mailbox using Outlook Web Access

Ensure that the ERM service account has the correct set of permissions as outlined in the Permissions section of the FAQ. Ensure that you are able to manually startup the COM+ Application that ERM installs (Component services -> Computers -> My Computer -> COM+ applications -> Simpler-Webb Exchange Resource Manager). Should this fail indicating that the configured identity is incorrect, set the credentials of the ERM service account correctly in the identity tab of the COM+ application properties.

When a resource account is deleted in AD while its mailbox is still managed by ERM, the ERM database would have a record corresponding to the resource with the indication that the resource is still being managed. To prevent the problem, please un-manage resources prior to deleting their accounts from AD. To resolve the problem, we have put together a tool called ERMCheckResources.zip that identifies resources that have been deleted while they were still being managed by ERM. The following steps will ensure that the resource configuration corresponding to the deleted resources is removed so additional resources may be managed.
1) To run the tool, simply type ERMCheckResources.exe from a command prompt on the exchange server running ERM. To redirect the output to a text file, type ERMCheckResources.exe 
2) Backup the existing ERM database file ERM_RCS.mdb (available by default in C:\Program Files\Simpler-Webb\Exchange Resource Manager\Data\) by simply making a copy of it in another location.
3) Open up the database using Microsoft Access. From the list of records displayed in step 1, delete the records that have the "Valid?" field set to "No" from the ERM database file. These records correspond to the resources that do not have accounts in AD. Save and close the database file.
4) Exit and reopen the ERM Mailbox Browser and click Help -> About Mailbox Browser to verify that the number of "Managed Resources" is displayed correctly.