This document will assist with silently installing NetApp Data ONTAP DSM for Windows MPIO v4.1. These processes should be performed in the following order:
1) HOWTO: Silent Installation for NetApp Data ONTAP DSM for Windows MPIO v4.1
2) HOWTO: Silent Installation for NetApp Windows Host Utilities 6.0.2
3) HOWTO: Silent Installation for NetApp SnapDrive for Windows v7.0.3
4) HOWTO: Verify NetApp SnapDrive for Windows 7.0.3 Installations were successful
The following pre-requisites and requirements are assumed:
· ntap_win_mpio_4.1P1_setup_x64.msi and/or ntap_win_mpio_4.1P1_setup_x86.msi downloads from the NetApp NOW site
o NOTE: NO testing has been done for 32 bit OS, and no provisions exist in the current batch file. It is assumed that you are on an actual modern server OS, and it is x64. If not… perform the installation manually.
· 215-08396_A0 – Installation and Administration Guide.pdf from NetApp NOW site
· As this was intended for UPGRADES of systems with at least SnapDrive for Windows, we are assuming that the .NET 3.5 pre-requisite has been met. Additional work will be required in order to provide the error checking and installation processes for .NET 3.5, as each OS has a slightly different method of doing so. I’d recommend creating a standardized “INSTALL_DOTNET_35.BAT” that could be called by any other installation that requires it, to keep the process modular.
· The following Windows HotFixes:
I:\INSTALLS\NETAPP\Data ONTAP DSM for Windows v4.1\WINDOWS_HOTFIXES\2008\Windows6.0-KB2684681-x64.msu
I:\INSTALLS\NETAPP\Data ONTAP DSM for Windows v4.1\WINDOWS_HOTFIXES\2008\Windows6.0-KB2754704-x64.msu
I:\INSTALLS\NETAPP\Data ONTAP DSM for Windows v4.1\WINDOWS_HOTFIXES\2008R2\Windows6.1-KB2520235-x64.msu
I:\INSTALLS\NETAPP\Data ONTAP DSM for Windows v4.1\WINDOWS_HOTFIXES\2008R2\Windows6.1-KB2528357-v2-x64.msu
I:\INSTALLS\NETAPP\Data ONTAP DSM for Windows v4.1\WINDOWS_HOTFIXES\2008R2\Windows6.1-KB2684681-x64.msu
I:\INSTALLS\NETAPP\Data ONTAP DSM for Windows v4.1\WINDOWS_HOTFIXES\2008R2\Windows6.1-KB2754704-x64.msu
I:\INSTALLS\NETAPP\Data ONTAP DSM for Windows v4.1\WINDOWS_HOTFIXES\2008R2\Windows6.1-KB979711-x64.msu
I:\INSTALLS\NETAPP\Data ONTAP DSM for Windows v4.1\WINDOWS_HOTFIXES\2008R2SP1\Windows6.1-KB2528357-v2-x64.msu
I:\INSTALLS\NETAPP\Data ONTAP DSM for Windows v4.1\WINDOWS_HOTFIXES\2008R2SP1\Windows6.1-KB2684681-x64.msu
I:\INSTALLS\NETAPP\Data ONTAP DSM for Windows v4.1\WINDOWS_HOTFIXES\2008R2SP1\Windows6.1-KB2754704-x64.msu
I:\INSTALLS\NETAPP\Data ONTAP DSM for Windows v4.1\WINDOWS_HOTFIXES\2008SP2\Windows6.0-KB2684681-x64.msu
I:\INSTALLS\NETAPP\Data ONTAP DSM for Windows v4.1\WINDOWS_HOTFIXES\2008SP2\Windows6.0-KB2754704-x64.msu
I:\INSTALLS\NETAPP\Data ONTAP DSM for Windows v4.1\WINDOWS_HOTFIXES\2008SP2\Windows6.0-KB968675-x64.msu
I:\INSTALLS\NETAPP\Data ONTAP DSM for Windows v4.1\WINDOWS_HOTFIXES\2012\Windows8-RT-KB2796995-x64.msu
o NOTE: the Folder path for the HotFixes from Microsoft MUST be:
§ IN the installation folder
§ IN a folder called “WINDOWS_HOTFIXES”
§ IN folders based on OS of 2008, 2008SP2, 2008R2, 2008R2SP1, 2012 (there are no 2012R2 hotfixes required)
o Links to obtain the hotfixes are located in the Administration Guide, on Page 56. Links will have a HF # only, eg: “2796995”. These links may include downloads for multiple OS’s (eg: Vista/Windows 7 – equal to 2008 and 2008 R2), and each must be downloaded and located separately. These hotfixes will unfortunately be named such as “457359_intl_x64_zip.exe” for KB2796995. This is unfortunate as it is near impossible to correlate the versions and the files. I would recommend saving the files as “KB2796995-457359_intl_x64_zip.exe” with the KB######## as the prefix. Upon downloading, UNZIP the files in the same folder/folder structure, and you will note the final output of “Windows8-RT-KB2796995.msu”. You will quickly be able to tell if you have only downloaded one version if you see “Windows6.1” for a 2008 file and “Windows6.0 for a 2008R2” file, etc.
· You are installing as “Local System” account vs a named service account – there is no interaction with the NetApp Filer, so there is no functional reason to use a named service account
· You have been given the MPIO-WIN 14 digit product key from the NetApp NOW Licencing portal.
The general process in the installation batch file is:
· LOG output is in the PRODUCT_FOLDER as %BATCH%.LOG
· MSI LOG is to %TEMP% as %BATCH%.LOG, and is NOT cleaned up after installation. Use for troubleshooting.
· Check if the product is already installed, using WMIC. If installed, jumps to CLEANUP
· Check for OS version to determine what hotfixes are required
· Copy hotfixes locally – they will not run properly via a UNC path as they update the system via DISM and the machine account likely has no rights to the share
· Run the installers for the hotfixes and wait for each to complete – it does not check if they are missing or already present
· Copy installation MSI locally
· Run the installer for the MSI and wait for complete
· Updates the registry with 190 second MPIO timeouts in two places
· Cleans up local files
=== INSTALL_NETAPP_DSM_MPIO_41.BAT ===
@echo off
REM
REM Enter the path to the installation folder – does not require quotes, quotes are assumed, with or without spaces – MUST not contain training «\»
REM
set INSTALL_FOLDER=\\netwise.ca\DFS\INSTALLS\NetApp\Data ONTAP DSM for Windows v4.1
set PRODUCT_NAME=Data ONTAP DSM for Windows MPIO
set LOG_FILE=»%INSTALL_FOLDER%\%~n0.LOG»
ECHO. >>%LOG_FILE%
REM Obtain Licence Code and update
set LICENSECODE=XXXXXXXXXXX
:CHECK_ALREADY_INSTALLED
REM
REM Use a Product Name substring search and the exact version number. Note the double percent characters are correct
REM
wmic product where «Name like ‘%%DSM%%’ and Version like ‘4.1.4348.1209’» get Name, Version | find /i «4.1.4348.1209»
if %ERRORLEVEL%==1 goto CHECK_OS_VERSION
if %ERRORLEVEL%==0 echo %COMPUTERNAME% %DATE% %TIME% – %PRODUCT_NAME% already installed! >>%LOG_FILE%
goto CLEANUP
:CHECK_OS_VERSION
REM
REM Check for OS Version
REM
set OS_VER=0
set OS_NAME=0
for /f «tokens=1-5* delims=[] » %%A in (‘ver’) do set OS_VER=%%D
if %OS_VER%==6.3.9200 set OS_NAME=2012R2
if %OS_VER%==6.2.9200 set OS_NAME=2012
if %OS_VER%==6.0.6001 set OS_NAME=2008
if %OS_VER%==6.0.6002 set OS_NAME=2008SP2
if %OS_VER%==6.1.7600 set OS_NAME=2008R2
if %OS_VER%==6.1.7601 set OS_NAME=2008R2SP1
goto INSTALL_PREREQ_HOTFIXES
:INSTALL_PREREQ_HOTFIXES
REM
REM Will copy ALL *.MSU files locally from matching folder name to OS_NAME list above, and then install ALL *.MSU files from the local drive,
REM waiting for each to complete before continuing.
REM
ECHO %COMPUTERNAME% %DATE% %TIME% – %PRODUCT_NAME% copying pre-requisite hotfixes locally >>%LOG_FILE%
xcopy «%INSTALL_FOLDER%»\WINDOWS_HOTFIXES\%OS_NAME%\*.msu %TEMP%\DSM.INST /s /e /c /k /i /y
ECHO %COMPUTERNAME% %DATE% %TIME% – %PRODUCT_NAME% installing pre-requisite hotfixes >>%LOG_FILE%
for /f «tokens=1* delims=» %%A in (‘dir %temp%\DSM.INST /b’) do start /w wusa.exe %temp%\%%A /quiet /norestart
goto INSTALL_DSM_MPIO
:INSTALL_DSM_MPIO
ECHO %COMPUTERNAME% %DATE% %TIME% – %PRODUCT_NAME% copying installation files locally >>%LOG_FILE%
xcopy «%INSTALL_FOLDER%»\»ntap_win_mpio_4.1P1_setup_x64.msi» %TEMP%\DSM.INST /s /e /c /k /i /y
ECHO %COMPUTERNAME% %DATE% %TIME% – %PRODUCT_NAME% installing main application >>%LOG_FILE%
msiexec.exe /quiet /i»%TEMP%\DSM.INST\ntap_win_mpio_4.1P1_setup_x64.msi» /l*v %TEMP%\%~n0.LOG LICENSECODE=%LICENSECODE% USESYSTEMACCOUNT=1 /norestart
wmic product where «Name like ‘%%DSM%%’ and Version like ‘4.1.4348.1209’» get Name, Version | find /i «4.1.4348.1209»
if %ERRORLEVEL%==1 echo %COMPUTERNAME% %DATE% %TIME% – %PRODUCT_NAME% reports as NOT INSTALLED >>%LOG_FILE%
if %ERRORLEVEL%==0 echo %COMPUTERNAME% %DATE% %TIME% – %PRODUCT_NAME% reports as INSTALLED >>%LOG_FILE%
goto CLEANUP
:CLEANUP
ECHO %COMPUTERNAME% %DATE% %TIME% – %PRODUCT_NAME% cleaning up installation files locally >>%LOG_FILE%
if exist %TEMP%\DSM.INST rmdir %TEMP%\DSM.INST /q /s
REM
REM Set Registry keys for both NetApp MPIO and Windows MPIO to 190 second timeouts
REM
ECHO %COMPUTERNAME% %DATE% %TIME% – %PRODUCT_NAME% updating registry with 190 second MPIO timeouts >>%LOG_FILE%
REG add HKLM\System\CurrentControlSet\Services\ontapdsm\Parameters /v PDORemovePeriod /t REG_DWORD /d 190 /f
REG add HKLM\SYSTEM\CurrentControlSet\Services\Disk /v TimeoutValue /t REG_DWORD /d 190 /f
REG QUERY «HKLM\SYSTEM\CurrentControlSet\Control\Session Manager» /v PendingFileRenameOperations | find /i «C:»
if %ERRORLEVEL%==0 ECHO %COMPUTERNAME% %DATE% %TIME% – %PRODUCT_NAME% HAS a reboot pending… >>%LOG_FILE%
ECHO. >>%LOG_FILE%
=== INSTALL_NETAPP_DSM_MPIO_41.BAT ===
=== SAMPLE LOG OUTPUT ===
SRVDC113B 11/09/2014 16:46:13.13 – Data ONTAP DSM for Windows MPIO already installed!
SRVDC113B 11/09/2014 16:46:13.13 – Data ONTAP DSM for Windows MPIO cleaning up installation files locally
SRVDC113B 11/09/2014 16:46:13.13 – Data ONTAP DSM for Windows MPIO updating registry with 190 second MPIO timeouts
SRVD511 Thu 09/11/2014 16:49:06.95 – Data ONTAP DSM for Windows MPIO copying pre-requisite hotfixes locally
SRVD511 Thu 09/11/2014 16:49:07.08 – Data ONTAP DSM for Windows MPIO installing pre-requisite hotfixes
SRVD511 Thu 09/11/2014 16:49:07.25 – Data ONTAP DSM for Windows MPIO copying installation files locally
SRVD511 Thu 09/11/2014 16:49:07.36 – Data ONTAP DSM for Windows MPIO installing main application
SRVD511 Thu 09/11/2014 16:49:46.44 – Data ONTAP DSM for Windows MPIO reports as INSTALLED
SRVD511 Thu 09/11/2014 16:49:46.44 – Data ONTAP DSM for Windows MPIO cleaning up installation files locally
SRVD511 Thu 09/11/2014 16:49:46.45 – Data ONTAP DSM for Windows MPIO updating registry with 190 second MPIO timeouts
=== SAMPLE LOG OUTPUT ===
The following post
runs through a complete install of the NetApp Software Stack on a Windows
Server 2008 R2 SP1 to which NetApp storage is to be attached.
— FC Host Utilities for Windows
— iSCSI Host Utilities for
Windows
— Multipath I/O for Windows
Note: The links for FC Host Utilities and iSCSI Host Utilities both
lead to downloading the Windows Host Utilities.
Installation Order
1. FC/iSCSI Host Utilities for
Windows
2. Multipath I/O for Windows
Latest Versions
For this post we will use a
fully patched Windows Server 2008 R2 SP1 box and these latest versions:
— FC/iSCSI Host Utilities for
Windows: Windows Host Utilities 6.0.2 (11 April 2013)
— Multipath I/O for Windows:
Data ONTAP DSM 4.0 for Windows MPIO (14 Feb 2013)
— SnapDrive for Windows:
SnapDrive 6.5
Installing
NetApp FC/iSCSI Host Utilities
The Windows Host Utilities require the following hotfixes
to be downloaded and installed first (the installer will prompt for these to be
installed if they haven’t been already):
Q2528357 — storport.sys
(Required: 6.1.7601.17610)
Q2684681 — msiscsi.sys
(Required: 6.1.7601.17792.21938)
Q2754704 — mpio.sys
(Required: 6.1.7601.18015.22177)
Note: When
downloading the hotfix, tick only the Windows 7/Windows Server 2008 R2 SP1 checkbox
(Windows version 6.1)
Double-click the downloaded hotfixes to unpack:
432658_intl_x64_zip.exe
445355_intl_x64_zip.exe
456116_intl_x64_zip.exe
Double-click the patches to install:
Windows6.1-KB2528357-v2-x64.msu
Windows6.1-KB2684681-x64.msu
Windows6.1-KB2754704-x64.msu
Reboot to complete the hotfix installs.
Double-click the downloaded netapp_windows_host_utilities_6.0.2_x64.msi to install the NetApp
Windows host utilities.
Image: Welcome to
the NetApp Windows Host Utilities 6.0.2 Setup Wizard
Follow through the wizard, accepting the EULA.
Select whether to install support for Multipath I/O or
not.
Note: Selecting ‘Yes,
install support for Multipath I/O’ automatically installs the Windows Server
2008 R2 feature ‘Multipath I/O’.
Image: NetApp Windows
Host Utilities Support for Multipathing?
Choose an install location (default is C:\Program Files\NetApp\Windows Host
Utilities\).
Complete the wizard, and then click Install and — once
complete — click Finish.
Reboot to complete the host utilities install.
The install will create a folder in All Programs for >
NetApp > Windows Host Utilities, with a shortcut to SAN Version
Image: All Programs
> NetApp > Windows Host Utilities
In the install folder — ‘C:\Program Files\NetApp\Windows
Host Utilities’ — contains:
LinuxGuestConfig.iso,
mbralign.exe, san_version.exe, sanpolicy.txt
In ‘C:\Program Files\NetApp\Windows Host Utilities\NetAppQCLI’
we have (amongst other files):
enable_disable_x64.exe,
fcconfig.exe, qaucli.exe, qlnic.exe
Installing NetApp
Multipath I/O for Windows
Note: It is not
essential for this to be installed for the server to understand multipath to
NetApp storage. Windows Server 2008 R2 MPIO natively has support for NetApp.
Image: Windows
Server 2008 R2 MPIO Devices pre NetApp Multipath I/O install.
Double-click the downloaded ntap_win_mpio_4.0_setup_x64.msi to install NetApp Multipath I/O for
Windows.
Note: With the
NetApp Windows Host Utilities already installed, no patches are required here.
Image: Welcome to
the Data ONTAP DSM for Windows MPIO Setup Wizard
Click OK to the ‘Data ONTAP(R) DSM requires ALUA to be
enabled on your storage controller for the associated FC igroups’.
Enter the 14-character license key.
Image: Data ONTAP
DSM for Windows requires a License Key!
Specify the account information for the installed
services.
Image: Data ONTAP
DSM Management Service
Select whether to install Hyper-V Guest Utilities or not.
Image: Data ONTAP
DSM for Windows — Hyper-V Guest Utilities
Verify the driver information before installing or updating.
Image: Data ONTAP
DSM for Windows — Driver Information
Choose an install location (default is C:\Program Files\NetApp\MPIO\)
Reboot to complete the NetApp Multipath I/O for Windows
install.
Image: Windows
Server 2008 R2 MPIO Devices post NetApp Multipath I/O install.
Note: The NetApp
Data ONTAP DSM install does not add anything to All Programs.
Installing
NetApp SnapDrive for Windows
Double-click the downloaded SnapDrive6.5_x64.exe to install NetApp SnapDrive for Windows.
Follow through the SnapDrive — Installation Wizard.
Image: SnapDrive
Installation Wizard
SnapDrive can be licensed in two ways, either ‘Per
Storage System’ or ‘Per Server’. If per-server then a Valid SnapDrive License
Key is required before continuing!
Image: SnapDrive
Installation Wizard — SnapDrive License
Enter Customer Information.
Choose an install location (default is C:\Program Files\NetApp\SnapDrive\)
Tick or not the box to ‘Enable SnapDrive to communicate
through the Windows Firewall’
(If required) Enable SnapDrive with VMware vCenter
integration and specify the account information for the installed services.
Image: SnapDrive —
VirtualCenter or ESX Server Web Service Credentials
(If required) Enable SnapDrive with Virtual Storage
Console integration and specify VSC details.
Image: SnapDrive —
Virtual Storage Console Details
Specify SnapDrive Service Credentials.
Image: Specify
SnapDrive Service Credentials
Specify SnapDrive Web Service port configuration. The
default SnapDrive ports are:
808 —
SnapDrive Web Service Tcp/Ip Endpoint
4094 —
SnapDrive Web Service HTTP Endpoint
4095 —
SnapDrive Web Service HTTPS Endpoint
Specify the Transport Protocol Default Setting — RPC,
HTTP, or HTTPS.
Image: SnapDrive —
Transport Protocol Default Setting
Specify SnapDrive Protection Manager integration.
Image: SnapDrive —
OnCommand Configuration
A reboot is
not
required after installing
SnapDrive.
After install, SnapDrive is available via All Programs
> NetApp > SnapDrive.
The following Windows Services exist in services.msc:
— Data ONTAP VSS
Hardware Provider / navssprv.exe (Manual — only runs when in use)
— SnapDrive /
swsvc.exe (Automatic — Started)
— SnapDrive
Management Service / sdmgmtsvc.exe (Automatic — Started)
THE END
Image: Windows
Server 2008 R2 > Programs and Features — showing the installed NetApp
software stack
Latest (downloaded
16/05/2013):
Data ONTAP DSM for
Windows MPIO — 4.0.4594.1228
NetApp Windows Host
Utilities 6.0.2 — 6.0.4649.1236
SnapDrive — 6.5.0.5474
Update: 01 December, 2023
This document describes the installation and administration guide for IBM System Storage N series Data ONTAP DSM 3.5 for Windows MPIO.
File format: PDF
Size: —
MD5 Checksum: AFC7A1800AE4E0073E0A8CC72E61C040
Publication date: 01 December, 2023
Downloads: —
PDF Link:
IBM System Storage N series Data ONTAP DSM 3.5 for Windows MPIO Installation and Administration Guide PDF
Created On
Last Updated On
The following is an abbreviated procedure for configuring NetApp SnapDrive for Windows with Clustered ONTAP. The full article can be found at How to configure SnapDrive for Windows with clustered Data ONTAP.
Before you begin, check the compatibility matrix and review the alerts and informational notices for the SDW entry in the Interoperability Matrix Tool.
Configure the SVM
- Set a password for the vsadmin account and save it for later reference. Run the following command to set the password for the SVM admin user:
::> security login password -username vsadmin -vserver <vserver_name> - Run the following command to unlock the vsadmin account:
::> security login unlock -username vsadmin -vserver <vserver_name> - In the storage system, create a SVM management LIF with the data protocol set to
NONEand the firewall policy set toMGMT.Note: Data LIFs cannot be added to SnapDrive as preferred storage system IP addresses.::> net int create -vserver <vserver_name> -lif <lif_name> -role data -data-protocol none -home-node <node_name> -home-port <port_name> -address xx.xx.xx.xx -netmask xx.xx.xx.xx -status-admin up -firewall-policy mgmt - Ensure that an A record and associated PTR record exist in DNS for the SVM management LIF and that the record is associated uniquely with the management LIF IP address. If necessary, create an A record and an associated PTR record in DNS.Note: If CIFS is enabled on the SVM, the CIFS name registered with DNS must be different from the SVM name, because CIFS traffic cannot use the SVM management LIF you created in Step 3. It is highly recommended that NAS (CIFS/NFS file services) be separated from SAN services in separate SVMs.
- From a client machine, validate forward and reverse DNS works for the SVM management LIF.
Configure the Windows Server(s)
- Verify that DSM and the Host Utilities Kit is installed, as appropriate, for direct-connected iSCSI or FCP LUNs prior to installing SDW. It is recommended to use the native Microsoft DSM is used. However, you can install the Data ONTAP DSM.Related Links:
- Installing the Data ONTAP DSM for Windows MPIO
- How to set up MSDSM for NetApp LUNs in Windows Server 2008
- Host Utilities Kit Download
- Install SnapDrive on the server, or if part of a Windows Failover cluster – all nodes of the Windows Failover cluster.
- The SnapDrive service account must be a member of the Local Administrators group. If you install SnapDrive in a Windows Failover Cluster environment, you must use the same DOMAIN USER account as the service account on each node the Windows Failover Cluster.Related Link: What are the required capabilities for SnapDrive for Windows service account?
- Add a preferred storage system IP address for the vServer management LIF in the SnapDrive GUI or from the SnapDrive CLI:
C:\> sdcli preferredip set –f <hostname> -IP <ip address>
C:\> sdcli preferredip listNote: If SnapDrive is to be used for Management, you cannot use a NetBIOS (clustered Data ONTAP 8.3) to mount the SMBv3 CIFS shares.
- Verify that the default transport settings are disabled, and adjust the default transport settings to use HTTPS or HTTP and specify the vsadmin credentials:
- In the SnapDrive management snap-in, right-click hostname and select Transport Protocol Settings > Default. Verify that the default settings are disabled.
- In the SnapDrive management snap-in, right-click hostname, select Transport Protocol Settings > Storage Systems, and click Add. Add the vServer name that you configured above with the vsadmin username and password that you configured earlier.
- Perform the following steps in SnapDrive in order to fully test SnapDrive function:
- Create a disk
- Create a snapshot
- Delete a snapshot
- Create a FlexClone
- Delete a FlexClone
- Delete the disk
Data ONTAP DSM driver is a windows driver .
Common questions for Data ONTAP DSM driver
Q: Where can I download the Data ONTAP DSM driver’s driver?
Please download it from your system manufacturer’s website. Or you download it from our website.
Q: Why my Data ONTAP DSM driver doesn’t work after I install the new driver?
1. Please identify the driver version that you download is match to your OS platform.
2. You should uninstall original driver before install the downloaded one.
3. Try a driver checking tool such as DriverIdentifier Software .
As there are many drivers having the same name, we suggest you to try the Driver Tool, otherwise you can try one by on the list of available driver below.
Please scroll down to find a latest utilities and drivers for your Data ONTAP DSM driver.
Be attentive to download software for your operating system.
If none of these helps, you can contact us for further assistance.