To run the PowerShell script module

1. If you have not already done so, install Enterprise Vault 12.1 or later on each node in the Windows Server failover cluster.

   If you are performing a new installation of Enterprise Vault, follow the installation instructions in the Enterprise Vault Installing and Configuring guide. If you are upgrading, follow the instructions in Upgrade Instructions.

2. Check that all the Enterprise Vault services are running on the active node in the cluster.

3. Copy the EVClusterMigration.psm1 script  to the active node.

4. On the active node, start the 64-bit version of either Windows PowerShell or Windows PowerShell ISE with the "Run as administrator" option. For the purposes of this procedure, it is essential to run the 64-bit version rather than the 32-bit version.

   The version of PowerShell must be 3.0 or later. You can determine the version that you are running by typing the following at the PowerShell prompt:

   $PSVersionTable.PSVersion

5. If you are running Windows Server 2012, type the following command to allow PowerShell to run scripts that have been digitally signed by a trusted publisher:

   Set-ExecutionPolicy AllSigned

   If the active node is running Windows Server 2012 R2, this command is optional. By default, this version of Windows allows downloaded, digitally-signed scripts to run.

6. Type the following command to import the downloaded script module into the current PowerShell session:

   Import-Module path_to\EVClusterMigration.psm1

   For example:

   Import-Module C:\EVClusterMigration.psm1

7. Type the following command to start the migration process:

   Start-EVClusterMigration [-ClusterGroup ] [-Verbose]

   The parameters are optional and have the following functions:

   -ClusterGroup	Specifies the name of the cluster group. If you omit this parameter, Start-EVClusterMigration uses Microsoft Cluster PowerShell cmdlets to determine the cluster group that contains the Enterprise Vault resources.
   -Verbose	Instructs the script to display detailed information while it performs the migration process.

   For example, you might type the following:

   Start-EVClusterMigration -ClusterGroup "EVCluster" -Verbose

8. Follow the instructions on your screen. At each step in the migration process, Start-EVClusterMigration prompts you to confirm that you want to continue. The process has completed when Start-EVClusterMigration displays the following message:

   Migration of Enterprise Vault from 32-bit cluster resource DLLs to 64-bit cluster resource DLLs is now complete.

9. On each passive node in the cluster, open a Command Prompt window with the "Run as administrator" option and then type the following to register the new 64-bit cluster resource DLL:

   regsvr32.exe "%programfiles(x86)%\Enterprise Vault\x64\EVServiceResEx.dll"

   For example:

   regsvr32.exe "C:\Program Files (x86)\Enterprise Vault\x64\EVServiceResEx.dll"
10. Restart the Failover Cluster Manager snap-in on each node to put the changes into effect.

11. If you want to remove the EVClusterMigration module from the current PowerShell session, type the following command:

    Remove-Module EVClusterMigration

IMPORTANT: Do not edit this content

Enterprise Vault 12.1 and higher comes with 64-bit versions of the cluster resource DLLs. These 64-bit DLLs can be deployed to all the nodes in a Windows Server failover cluster by running the PowerShell script module EVClusterMigration.psm1, which is available from this page.

This script module does the following:

1. Installs the Failover Cluster Command Interface feature on the cluster nodes, if it is not already installed.
2. Takes the Enterprise Vault cluster resource instances offline.
3. Removes the Enterprise Vault cluster resource instances.
4. Unregisters the 32-bit Enterprise Vault cluster resource types.
5. Registers the 64-bit Enterprise Vault cluster resource types.
6. Recreates the Enterprise Vault cluster resource instances.
7. Brings the Enterprise Vault cluster resource instances online.

Enterprise Vault can be clustered in a Windows Server failover cluster to provide a high availability solution for Enterprise Vault. However, in Windows Server 2012 and Windows Server 2012 R2 environments, the Enterprise Vault cluster resource group may fail to come online after an automatic failover from the active node to a passive node. The reason for this is that the cluster resource DLLs in Enterprise Vault 12 and earlier are 32-bit, but these are deprecated in Windows Server 2012 and Windows Server 2012 R2.