Product specifications

Before You Begin the Server Failover Installation
31
The account for these objects must be disabled so that when the Create Cluster wizard
and the Interplay Engine installer are run, they can confirm that the account to be used
for the cluster is not currently in use by an existing computer or cluster in the domain.
The cluster creation process then enables the entry in the AD.
For more information on the cluster creation account and setting permissions, see the
Microsoft article “Failover Cluster Step-by-Step Guide: Configuring Accounts in Active
Directory” at http://technet.microsoft.com/en-us/library/cc731002%28WS.10%29.aspx
n
Roaming profiles are not supported in an Interplay Production environment.
• Cluster administration account: Create or select a user account for logging in to and
administering the failover cluster server. Depending on the account policies of your site, this
account could be the same as the cluster installation account, or it can be a different domain
user account with administrative permissions on the servers that will become cluster nodes.
n
Do not use the same username and password for the Server Execution User and the cluster
installation and cluster administration accounts. These accounts have different functions and
require different privileges.
List of IP Addresses and Network Names
You need to reserve IP host names and static IP addresses on the in-network DNS server before
you begin the installation process. The number of IP addresses you need depends on your
configuration:
• An Avid ISIS environment with a redundant-switch configuration requires 4 public IP
addresses and 2 private IP addresses
• An Avid ISIS environment with a dual-connected configuration requires 8 public IP
addresses and 2 private IP addresses
n
Make sure that these IP addresses are outside of the range that is available to DHCP so they
cannot automatically be assigned to other machines.
n
If your Active Directory domain or DNS includes more than one cluster, to avoid conflicts, you
need to make sure the cluster names, MSDTC names, and IP addresses are different for each
cluster.
n
All names must be valid and unique network host names.