3.6.1 HP PolyServe Matrix Server Administration Guide (T5392-96018, August 2008)

Chapter 4: Matrix Administration 21

• Active Directory user and groups should be used in filesystem ACLs

and SQL Server service accounts and roles. Do not use local users and

groups for these purposes because they are meaningless to other

nodes in the matrix.

• Matrix Server nodes should not be used as domain controllers because

the two services will compete for resources, resulting in decreased

performance.

• The DNS servers used by Active Directory and Matrix Server should

not reside on Matrix Server nodes. Placing the DNS servers on Matrix

Server nodes creates a race condition that prevents Matrix Server from

starting.

• If you are using HP PolyServe Software for Microsoft SQL Server and

want to use Kerberos for Windows authentication, you will need to

for the sqlserver service is a domain admin or Localsystem, register an

SPN for the Virtual SQL Server/hostname. If the startup account for

the sqlserver service is not a domain admin or Localsystem, then

should not be registered for the Virtual SQL Server.) For more

information, see “DNS Misconfiguration Causes Connection Failure”

in the HP PolyServe Software for Microsoft SQL Server Installation and

Administration Guide.

Other Considerations

• If Role-Based Security is used, assign users/groups to appropriately

configured roles that give Matrix Server administrators the least-

privilege needed to perform operations.

• For best performance, we recommend that you monitor the matrix

from a separate administrative station rather than from a server in the

matrix. The PolyServe Management Console can be installed on

Windows systems outside the matrix.

• Using search bots and running parallel searches across the matrix can

have a negative impact on performance. Users should be aware of the

potential effects of various search activities.