Release Notes
Table Of Contents
- Dell EqualLogic Host Integration Tools for Microsoft Edition Version 5.3 Release Notes
- Revision History
- Platforms Affected
- HIT/ME Components
- Supported Versions of the Windows Operating System
- Requirements
- New in This Release
- Usage Constraints
- Known Issues
- _
- Known Issues with PowerStore Import
- HIT/ME Online Help link in ASM tool navigates to HIT/ME 5.0 Online Help
- Importing The SMP Provider by Using SCVMM 2016 Displays an Error Message
- The Change Option is not Available to Add or Remove any Components or Features of HIT/ME
- EHCM Might Drop Sessions When Using Broadcom or QLogic HBAs for iSCSI
- ASM Error When Updating to Window Server 2016 or Windows Server Core 2016
- Windows 2016 Schedules Not Running When Re-Enabled
- Set-ASMCollection Cmdlet Not Functioning as Designed
- Installing SCVMM 2012 R2 UR5 Causes EqualLogic Storage Discovery Issues
- Windows 2016 SharePoint Components Not Enumerated After Fresh Install of HIT Kit
- Exchange Replica Smart Copies Might Require Manual Soft Recovery
- Deleting a VSS Snapshot Occasionally Results in an Error Condition in the Group Manager Due to iSCSI Log Off Failure
- _
- Support Resources
1. Identify the correct iSCSI target.
2. Launch the command prompt by clicking Start → Run, then type cmd.
3. Enter diskpart at the Windows command prompt to display the DISKPART> prompt.
4. Enter list volume to list all volumes known to Windows.
5. Examine the column headed Volume ### and identify the volume (or volumes) associated with the iSCSI target.
6. Enter select volume
volume_name
, where volume_name is the volume that you identified in the previous step.
7. Enter offline disk to set the physical disk for the volume offline.
8. Enter exit to close the diskpart menu.
9. Enter exit to close the command window.
After setting the disk offline, you can successfully log out from the iSCSI target using the iSCSI initiator GUI or CLI.
Unsupported PowerShell Cmdlets for Windows 8 or Later or Windows Server
2012 or Later
The Storage Management Provider (SMP) does not support the following PowerShell cmdlets in Windows Server 2012 or later
and Windows 8 or later:
● New-StoragePool
● Remove-StoragePool
● Add-PhysicalDisk
● Add-VirtualDiskToMaskingSet
● Rename-MaskingSet
● Repair-VirtualDisk
● Set-PhysicalDisk
● Set-ResiliencySetting
● Reset-PhysicalDisk
● Remove-InitiatorId
HIT Must Be Installed on Each VM in a Windows Server Configuration
In a Windows Server configuration using Cluster Shared Volumes, HIT/ME must be installed on each VM. Installing HIT/ME
ensures Smart Copies of VMs will work correctly in all configurations, including Enterprise, Datacenter, Core, or any other
Windows Server release configuration.
This requirement applies whether you start the Smart Copy operation or when you create a schedule from the VM or the
Volume node in the ASM/ME GUI.
If HIT/ME is not installed on each VM, you can create a Smart Copy, but an error displays stating that ASM/ME could not
open a connection to the VM. The Smart Copy will not be file-system consistent, but is crash consistent with respect to the file
system in the VM. You might have to run the chkdsk utility the next time the VM restarts.
Cluster Shared Volume VSS Writer Does Not Report Remote VMs
Under rare circumstances the Cluster Shared Volume (CSV) VSS Writer in Windows Server 2012 does not report remote VMs.
This omission results in remote VMs not being included in Smart Copies of Cluster Shared Volumes.
This issue occurs when multiple requestors query the components at the same time. You might be able to avoid this issue by:
● Closing the ASM/ME GUI windows when they are not in use
● Not allowing the Smart Copy schedules to overlap
5