3.6.0 Matrix Server 3.6.0 Administration Guide (5697-7081, December 2007)

Chapter 4: Matrix Administration 21

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 MxDB for SQL Server and want to use Kerberos for

Windows authentication, you will need to register a valid SPN for the

Virtual SQL Server. If the startup account 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 register an SPN for the USER

account. (If Kerberos is not used, an SPN should not be registered for

the Virtual SQL Server.) For more information, see “DNS

Misconfiguration Causes Connection Failure” in the MxDB for 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.

• To ensure that file times are consistent across the matrix, it is

important that all matrix servers operate with synchronized time-of-