Windows Server 2008, 2012, 2016, and 2019 instructions

This section describes how to install, remove, and uninstall the Windows tape and medium changer device drivers on Windows Server 2008, 2012, 2016, and 2019.

Installation overview

The installation process consists of the following steps:
  1. Verify that the hardware and software requirements are met.
  2. Install the host bus adapters and drivers.
  3. Shut down the system.
  4. Connect the tape and medium changer devices to the host bus adapters.
  5. Power® on the tape and medium changer devices.
  6. Restart the system.
  7. Log on as Administrator.
  8. Install and configure the devices and device drivers with the installation application.

Installation procedures

These procedures make the following assumptions:
  • No other driver is installed that claims the tape and medium changer devices.
  • If you are updating the device driver from a Microsoft certified version to an uncertified version, you must first uninstall the certified driver. Refer to Uninstalling the device drivers.
  • The host bus adapter is installed, configured properly, and is running supported microcode and driver levels.
  • Device drivers are installed with Windows Server 2012 or 2012R2, with V6.2.5.3 or later; Windows Server 2016, with V6.2.6.0 or later; or Windows Server 2019, with V6.2.6.8 or later.
    Note: The latest driver level to include support for Windows Server 2008 is V6.2.5.2
  • Different registry keys are created to configure different parameters. They can be at System\CurrentControlSet\Services\ and the subkeys are created depending on the Windows Server version. With Windows Server 2008 they are:
    • ibmcg2k8
    • ibmtp2k8
    • ibmtpbs2k8
    With Windows Server 2012 they are:
    • ibmcg2k12
    • ibmtp2k12
    • ibmtpbs2k12
    With Windows 2016, they are:
    • ibmcg2k16
    • ibmtp2k16
    • ibmtpbs2k16
    With Windows 2019, they are:
    • ibmcg2k19
    • ibmtp2k19
    • ibmtpbs2k19
    Refer to this list when in doubt of the registry key's name and instructions that involve modifying the registry. Caution and a backup are advised due to the registry's nature.
  • Drivers are identified by the following conventions, where nnnn refers to a version of the driver. If there is more than one version, use the current one.
    • Windows Server 2019 for extended 64-bit architectures (Intel EM64T and AMD64),
      IBMTape.x64_w19_nnnn.zip
To install the device drivers, follow this procedure.
  1. Log on as Administrator.
  2. Download the appropriate driver. Refer toAccessing documentation and software online.
  3. Extract the driver package to a hard disk drive directory of your choice, other than the root directory.
  4. Ensure that the tape and medium changer devices are connected to your host bus adapter and configured properly by locating the devices in Device Manager.
  5. Double-click either install_exclusive.exe or install_nonexclusive.exe.
    • install_exclusive.exe The driver issues automatic reserves on open. It also prevents multiple open handles from the host to a drive from existing at the same time, as is required by applications such as Tivoli® Storage Manager. This driver is also required for the failover feature to work as it uses persistent reservation (by default).
    • install_nonexclusive.exe The driver permits open handles from the host to a drive to exist at the same time, as is required by applications such as Microsoft Data Protection Manager (DPM).
    Figure 1. Installation application in Windows Explorer
    Installation application in Windows Explorer
    Note:
    1. More installation features are available through the command prompt interface (CLI), which include
      • Installing only the tape or medium changer device drivers (-t or -c)
      • Running in debug mode, which creates the file debug.txt in the driver package directory (-d)
      • Running in silent mode, which suppresses messages that require user intervention, but only with Microsoft-certified IBM drivers (-s)
      • Disabling DPF from installation (-f), available in driver packages v6.2.0.1 and later
      • Enabling Persistent Reserve from installation if DPF is disabled (-p), available in driver packages v6.2.0.6 and later.
      • Disable Media Polling (-m).
      • Disable Dynamic Runtime Attributes (-a).
      • Exclude devices from being claimed by the driver (-e), available in driver packages v6.2.5.3 and later.
      To install the device drivers with any of these features, instead of double-clicking the installation executable file, open a command prompt window and cd to the driver package directory. For the usage information, type install_exclusive.exe -h or install_nonexclusive.exe -h at the prompt.
    2. If the Windows Found New Hardware Wizard begins during installation, cancel the wizard. The installation application completes the necessary steps.
  6. If you are installing a Windows Server 2008, Windows Server 2012, 2016, or 2019 driver that is not certified by the Microsoft Windows Hardware Quality Laboratories (WHQL), it likely has a VeriSign digital signature. During installation, you might be presented with a prompt to install the software. Mark the Always trust software from IBM Corporation check box and click Install. You see this screen the first time that you install the drivers, provided you click the Always trust software box.
    Note: Starting with Windows Server 2016 release 1607, non-WHQL signed kernel drivers might not load on a production server, per Microsoft documentation:
    "What are the exact exceptions? Are cross-signed drivers still valid? Enforcement happens only on fresh installations, with Secure Boot on, and applies only to new kernel mode drivers:
    • PCs upgrading from a release of Windows before Windows 10 Version 1607 still permit installation of cross-signed drivers.
    • PCs with Secure Boot OFF still permit installation of cross-signed drivers.
    • Drivers that are signed with an end-entity certificate issued before 29 July 2015 that chain to a supported cross-signed CA continues to be allowed.
    • To prevent systems from failing to boot properly, boot drivers are not blocked, but they are removed by the Program Compatibility Assistant. Future versions of Windows block boot drivers.

    To summarize, on non-upgraded fresh installations of Windows 10, version 1607 with Secure Boot ON, drivers must be signed by Microsoft or with an end-entity certificate issued before 29 July 2015 that chains to a supported cross-signed CA."

    All drivers that are released by IBM went through a complete test to ensure that they are stable and conform to specified requirements.

    Go to https://blogs.msdn.microsoft.com/windows_hardware_certification/2016/07/26/driver-signing-changes-in-windows-10-version-1607/ for details.

    Figure 2. Windows logo testing screen
    Windows logo testing screen
  7. To verify that the tape and medium changer devices and drivers are installed correctly, follow the instructions in Verifying correct attachment of your devices.

Device removal or disable procedure

If you must remove a device, or if you are altering the hardware configuration, you must uninstall or disable the device first.

  1. Right-click My Computer, select Manage to open the Computer Management Console, and click Device Manager.
  2. Right-click the device that you want to uninstall and select Uninstall .... If you want to disable the device without uninstalling it, you can select Disable.
  3. You are prompted to confirm the uninstallation. Click OK.
  4. In Device Manager, under System devices, right-click Changer Bus Enumerator and select Uninstall.
  5. In Device Manager, under System devices, right-click Tape Bus Enumerator and select Uninstall.
Note: This removal procedure removes the device from the device tree, but it does not uninstall the device driver files from your hard disk.

Uninstalling the device drivers

To uninstall the device drivers from the system, which includes deleting the system files and deallocating other system resources, complete the following steps.

  1. Quiesce all activity on the tape and medium changer.
  2. Double-click uninst.exe in the driver package.
    Note: This action removes all the files in the system directories that were created during the installation of the device driver. It does not delete the compressed file or the files that were extracted from the compressed file. If you want to remove these files, you must delete them manually. For v.6.2.5.3 and later, it is not required to manually remove the devices at the Device Manager.
  3. Restart the system.