How to remove the NetApp Host Utilities hotfix check

 

Update 2018-10-18Check out this comment. Looks like a much easier method than my MSI editing one.

 

Sick of the hotfix requirements for NetApp Host Utilities? Me to.

On a test/dev server I have I’ve been experimenting with Veeam, iSCSI, ReFS and Server 2016. I wanted to run the NetApp Host Utilities against my Server 2016 box and was told I was missing Q3197954:

Problem is this 2016 server is fully patched and if I go manually download Q3197954 (which appears to be a previous rollup) I can’t install it on my fully patch server.

On a hunch I figured I might be able to crack open the MSI and find a way around the hotfix check and I was right. Here is how you do it:

  1. Download and install Orca MSI Editor (Alternate Download)
  2. Download the NetApp Host Utilities package from https://now.netapp.com/ (v7.1 as of this writing)
  3. Launch Orca and open the MSI file with it
  4. Select ‘InstallUISequence’ on the left and then click the ‘Sequence’ column on the top right to sort by lowest value first
  5. Locate ‘CheckMSHotfixes’, right click on it and choose ‘Drop row’
  6. Click ‘Save’
  7. Close Orca
  8. Copy the edited MSI to your server and run the installation as per normal

Digging around the MSI a bit I found references to “IGNORE_HOTFIX_CHECK” listed. I suspect it’s some kind of flag or environment variable that could be set to accomplish the same thing but I was unable to find any documentation on how and a few guesses around using environment variables didn’t pan out so I decided to stick with the above solution.

A note of caution. This is likely 100% unsupported by NetApp and if they found out you did this to get the Host Utilities on your server you might run into support issues.

6 thoughts on “How to remove the NetApp Host Utilities hotfix check”

  1. While editing an MSI is super cool, I wanted to report that I found success by installing the Multipath I/O feature on Server 2016, rebooting, and then installing the NetApp Windows Host Utilities.

    Reply
  2. I got the ame error and fixed it with adding “IGNORE_HOTFIX_CHECK=1” parameter on the commandline of the MSI and voila ;-)

    Reply
    • Thanks for that! I figured there was a flag that could be set but couldn’t figure out how to set it.

      What was the exact command you ran? I’ll update my post with it.

      Reply
      • I think the following should work:
        msiexec /i netapp_windows_host_utilities_7.1_x64.msi MULTIPATHING={0/1} [INSTALLDIR=inst_path] IGNORE_HOTFIX_CHECK=1
        Where INSTALLDIR is only needed, if you want to change the default installation directory.

        Reply

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.