Storage Resource Manager Enterprise Edition Installation Guide

Storage Resource Manager Enterprise Edition C–9
SRM Troubleshooting Guide
The SRM Service Account MUST be a member of the Domain Users group in the
domain in which it exists. It cannot be a local account on the SRM Server machine.
For example, if the SRM Server machine name is PIPER and it is a member of the
domain ENGINEERING, the service account CANNOT be created as
PIPER\SRMSVCUSER. The service account must be in the ENGINEERING domain,
or some other master domain.
The SRM Service Account MUST have Full Control on the following registry key:
HKL-Software-HighGround-SRManager-<version>-Server-Options
The SRM Service Account MUST have Full Control on the following registry key on
ALL Agents:
HKL-Software-HighGround-SRManager-<version>-Agent-Security
The SRM Service Account MUST have a SQL Server login in the SQL Server where
the SRM database resides. It must also have at least PUBLIC access to the SRM
database. In SQL Enterprise Manager, under Databases, select Users. Double click on
the account in the right window and under “Database role membership” be sure that
Public and SRMSvcGroup are selected.
Trust Relationships
The SRM Server Service account MUST be in a domain that trusts all other domains
where Agents will reside. It is common to have a master domain where all user
accounts are maintained.
For example, if the SRM Server is in domain X, SRM Agents are in domain Y, and the
master domain that trusts domain X and Y is MASTER, the service account must be in
the MASTER domain.
IIS
The SRM Web pages must all be configured to run under MTX. Otherwise, all users
accessing the SRM UI will have to be added to SQL Server security.
1. In Internet Service Manager console (MMC), drill down under IIS to Default Web
Site.
2. Right click on StorageResourceManager and select Properties. The
StorageResourceManager window displays, as shown in Figure C–1.