3.5.1 Matrix Server Administration Guide

Chapter 3: Configure Servers 52
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
3. Start Matrix Server on server S2a. The server joins the matrix, which
now consists of servers S1, S2, S3, and S2a. Server S2 is down and S1,
S2a, and S3 are up.
4. Delete server S2 from the matrix. This step will remove references to
the server.
5. Update virtual hosts and any other matrix entities that used server S2
to now include S2a.
Matrix Server License File
To operate properly, Matrix Server requires that a license file be installed
on each server in the matrix.
Upgrade the License File
If you have obtained a new license for your matrix but are not upgrading
Matrix Server, you can manually copy the file to
/etc/opt/polyserve/licenses/license on each server or you can install it from
the Management Console.
By default, Matrix Server reads the license file upon startup of the server
and at 15-minute intervals. To cause Matrix Server to read the new license
file immediately, use one of these options:
On the Management Console, select the server, right-click, and then
select Refresh License.
On the command line, enter the following:
mx server read_license <server>
Until the new license file is read on all servers, you may see alerts on the
Management Console reporting that the license file does not match on all
servers.
Supported Matrix Server Features
The license agreement for each server determines which Matrix Server
features are supported on that server. You can use the View Features
option on the Management Console to determine the supported features