Users Guide

Join a Computer into a Failover Cluster
The prerequisites for joining a computer running Host Integration Tools into a failover cluster are as follows:
● Use an account that is a domain user account with local administrative access. Consider creating a named account such as
ASMadmin to use for ASM/ME operations on the cluster. You can use this account to log on to required services. If any
cluster node is running Exchange and SQL Server (using PS Series iSCSI volumes), you must also make sure that your user
account has the appropriate security group access for those applications.
● Change the login account for the EQLReqService and EqlASMAgent services. If you are using Cluster Continuous Replication
(CCR) or a Database Availability Group (DAG) under Exchange 2016 or Exchange 2019, SQL Server 2016 or SQL Server
2017, you do not need to change the login account.
See Change the login Account for ASM/ME Services (EQLReqService and EqlASMAgent) for instruction on changing the
login account.
● If the host being added is not running the same (or any) version of the Host Integration Tools as the other cluster nodes,
then after you add the host, run ASM/ME and select the Add Hosts Wizard to install ASM/ME and add the new node to
the HIT Group. See the Dell EqualLogic Auto-Snapshot Manager/Microsoft Edition User’s Guide for more information.
About Silent Installations
A silent installation does not require you to monitor and respond to typical installation prompts. You create a template of your
installation selections as you perform a silent installation. You can then clone this installation template to other computers, if the
other computers have:
● Very similar or identical hardware configurations
● The same operating system and service pack level
● The same system configuration for all optionally installed features that are affected by the installation, including (but not
limited to) firewall, iSCSI initiator version and configuration, and MPIO
Cloning an installation works best when you are setting up a large number of identically configured and newly installed
computers. The following considerations apply when performing a silent installation:
● During the installation process, installation messages from third-party products might be displayed, indicating what software
is being installed. However, these messages do not interfere with the installation and can be ignored.
● The drive letter that you specify in the installation script is used on every computer on which you run the script. For
example, if you specified F:\Eql in the script, then all of the other computers on which you run the script will attempt to
install the kit on the F:\ drive.
● The installation applies your selections when you create the original recording of an installation.
NOTE: Note only those Host Installation Tools components that are supported by the target computer are installed.
● When installing on a failover cluster, you must perform the installation from an account that is a member of the domain
administrator group.
Support for a Silent Installation
Host Integration Tools installations are built using a Windows-based installer known as the Install Shield. The Install Shield
product contains built-in support for silent installations.
Syntax
Setup.exe /s /v/qn /V"/q /norestart
[ADDLOCAL = HPC,RemoteSetupWiz,PowerShell,ASMME,COREVSSPROVIDER,VDS,MPIO|
ALL>]
[INSTALLDIR=drive:\install_path]
[IS_NET_API_LOGON_USERNAME=Domain\Username]
[IS_NET_API_LOGON_PASSWORD=password] /l*v log_path"
● Setup.exe or Setup64.exe is the single executable installer for the Host Integration Tools.
● /v"MIGSELECTION=1" enables the capability to import EqualLogic volumes to a PowerStore array.
20
Installation