Product specifications

Installing the Interplay | Engine on the First Node

- If you are setting up an Avid ISIS dual-connected configuration, proceed to “Adding a

Second IP Address (Dual-Connected Configuration)” on page 96

Avid does not recommend starting the server at this stage, because it is not installed on the other

node and a failover would be impossible.

Creating the Database Share Manually

If the File Server resource or the database share (WG_Database$) is not created (see “Checking

the Status of the Resource Group” on page 93

), you can create it manually by using the following

procedure.

If you copy the commands and paste them into a Command Prompt window, you must

replace any line breaks with a blank space.

To create the database share and File Server resource manually:

1. In the Failover Cluster Manager, make sure that the “Avid Workgroup Disk” resource (the S:

drive) is online.

2. Open a Command Prompt window.

3. To create the database share, enter the following command:

net share WG_Database$=S:\Workgroup_Databases /UNLIMITED

/GRANT:users,FULL /GRANT:Everyone,FULL /REMARK:"Avid Interplay database

directory" /Y

If the command is successful the following message is displayed:

WG_Database$ was shared successfully.

4. Enter the following command. Substitute the virtual host name of the Interplay Engine

service for

ENGINESERVER

cluster res "FileServer-(ENGINESERVER)(Avid Workgroup Disk)" /priv

MyShare="WG_Database$":str

No message is displayed for a successful command.

5. Enter the following command. Again, substitute the virtual host name of the Interplay

Engine service for

ENGINESERVER

cluster res "Avid Workgroup Engine Monitor"

/adddep:"FileServer-(ENGINESERVER)(Avid Workgroup Disk)"

If the command is successful the following message is displayed:

Making resource 'Avid Workgroup Engine Monitor' depend on resource

'FileServer-(ENGINESERVER)(Avid Workgroup Disk)'...

6. Make sure the File Server resource and the database share (WG_Database$) are listed in the

Failover Cluster Manager (see

“Checking the Status of the Resource Group” on page 93).