We need to configure the Enterprise vault with the virtual name but since the wizard is for configuring a stand alone node it fails as it would try to find a DNS alias for the physical hostname.

The wizard does not launch correctly as it finds that the cluster is not configured. The wizard checks following registry key to find the cluster configuration status.

HKEY_LOCAL_MACHINE\Software\Veritas\VCS\Base\Clusternodemode

ClusterNodeMode=0 -  This indicates VCS is not installed and will result in the 'VCS not installed' error during the system scan
ClusterNodeMode=1 -  This indicates VCS is installed, but not configured
ClusterNodeMode=2 -  This indicates VCS is installed and configured (server is already part of a cluster)

1. Ensure that the cluster is configured and the required service group for Enterprise vault is setup using the Enterprise vault cluster setup wizard.

2. Check the above mentioned registry key. Sometimes the registry value would be set to ClusterNodeMode=1 even after the cluster configuration has been completed and this causes the wizard to not work as expected.

3. Change this registry key value to ClusterNodeMode=2

4. In addition the following keys are also used by some wizards. 

ClusterID

Clustername

NodeID

5. Create these registry values if they are missing.

6. Capture the ClusterID from the llttab.txt file located at C:\Program Files\Veritas\comms\llt

7. Capture the Clustername from the VCS Java console or the main.cf file located at C:\Program Files\Veritas\cluster server\conf\config

 8. Capture the NodeID from llthost.txt file located at C:\Program Files\Veritas\comms\llt

9. Relaunch the Enterprise Vault configuration wizard and verify if the Create a new Enterprise Vault server with cluster support is now available. 

Instead the wizard launches the following window which is for a stand alone Enterprise Vault configuration.