Skip to main content
SAN hosts and cloud clients

Install Windows Unified Host Utilities 7.2

Contributors netapp-ranuk
PDFs

The Windows Unified Host Utilities (WUHU) enable you to connect a Windows host computer to NetApp storage systems.

The Windows Unified Host Utilities supports the following versions of Windows:

  • Windows 2022

  • Windows 2019

  • Windows 2016

  • Windows 2012R2

  • Windows 2012

Windows Unified Host Utilities includes an installation program that sets the required Windows registry and Host Bus Adapter (HBA) parameters so that a Windows host can correctly handle the storage system behaviors for NetApp ONTAP and E-Series platforms.

When you install the Host Utilities software, the installer sets the required Windows registry and HBA parameters.

The following programs and files are installed on the Windows host computer. The default directory is C:\Program Files\NetApp\Windows Host Utilities.

Program Purpose

emulexhba.reg

Troubleshooting program; run this program only if instructed to do so by technical support personnel.

\NetAppQCLI\fcconfig.exe

Used by the installation program to set the HBA parameters.

\NetAppQCLI\fcconfig.ini

Used by the installation program to set the HBA parameters.

\NetAppQCLI*.*

Used by the installation program to set the QLogic FC HBA parameters.

san_version.exe

Displays the version of the Host Utilities and FC HBAs.

The host utilities support different Windows host configurations, protocols, and multipathing options. For more information, see the NetApp Interoperability Matrix Tool.

Verify your host and storage system configuration

Before you install the host utilities, you must verify that the host utilities version supports your host and storage system configuration so that the software installs correctly.

Steps

  1. Check the supported configuration in the NetApp Interoperability Matrix Tool.

  2. Check the hotfixes required for the respective host in the SAN host Windows documentation.

    Note The Using Windows server 2022 with ONTAP document provides instructions on installing Windows hotfixes for Windows server 2022. Refer to the Windows documents in the host configurations category to find the relevant hotfix information for earlier versions of Windows server.

  3. Add the iSCSI, FCP, or NVMe-oF license and start the target service.

    Note The FC and iSCSI protocols do not require licenses on E-Series storage systems using the SANtricity Storage Manager.

  4. Verify your cabling.

    See the SAN configuration reference documentation for your version of ONTAP or E-Series hardware cabling for detailed cabling and configuration information.

Configure FC HBAs and switches

Install and configure one or more supported FC host bus adapters (HBAs) for FC connections to the storage system.

The Windows Host Utilities installer sets the required FC HBA settings.

Caution Do not change the HBA settings manually.
Steps

  1. Install one or more supported FC HBAs according to the instructions provided by the HBA vendor.

  2. Obtain the supported HBA drivers and management utilities and install them according to the instructions provided by the HBA vendor.

  3. Connect the HBAs to your FC switches or directly to the storage system.

  4. Create zones on the FC switch according to your FC switch documentation.

  5. For ONTAP, zone the switch by the WWPN. Be sure to use the WWPN of the logical interfaces (LIFs) and not the WWPN of the physical ports on the storage controllers. See the SAN configuration reference documentation for more information.

Install the Host Utilities

The installation program installs the host utilities package and sets the Windows registry and HBA settings.

You must specify whether to include multipathing support when you install the Windows Unified Host Utilities software package. The installer prompts you for the following options. You can also run a quiet (unattended) installation from a Windows command prompt.

Multipathing support

  • Choose MPIO if you have more than one path from the Windows host or virtual machine to the storage system.

  • Choose no MPIO only if you are using a single path to the storage system.

The MPIO selection is not available for Windows XP and Windows Vista systems; multipath I/O is not supported on these guest operating systems.
For Hyper-V guests, raw (pass-through) disks do not appear in the guest OS if you choose multipathing support. You can either use raw disks, or you can use MPIO, but you cannot use both in the guest OS.

You can install the host utilities interactively or using the command line. The new Host Utilities installation package must be in a path that is accessible by the Windows host. Follow the instructions for installing the Host Utilities interactively or from the Windows command line.

Install interactively

To install the Host Utilities software package interactively, you must run the host utilities installation program and follow the prompts.

Steps

  1. Download the executable file from the NetApp Support Site.

  2. Change to the directory where you downloaded the executable file.

  3. Run the netapp_windows_host_utilities_7.2_x64 file and follow the instructions on the screen.

  4. Reboot the Windows host when prompted.

Install from a command line

You can perform a quiet (unattended) installation of the host utilities by entering the appropriate commands at the Windows command prompt. The system automatically reboots when the installation is complete.

Steps

  1. Enter the following command at the Windows command prompt:

    msiexec /i installer.msi /quiet MULTIPATHING= {0 | 1} [INSTALLDIR=inst_path]

    • installer is the name of the .msi file for your CPU architecture.

    • MULTIPATHING specifies whether MPIO support is installed. The allowed values are "0" for no and "1" for yes.

    • inst_path is the path where the host utilities files are installed. The default path is C:\Program Files\NetApp\Windows Host Utilities\.

Note To see the standard Microsoft Installer (MSI) options for logging and other functions, enter msiexec /help at the Windows command prompt. For example, the msiexec /i install.msi /quiet /l*v <install.log> LOGVERBOSE=1 command displays logging information.