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
Apply the following registry entries to prevent EHCM sessions to volumes from being dropped when using HBAs (iSCSI
Offload):
● Host— [HKEY_LOCAL_MACHINE\SOFTWARE\EqualLogic\EHCM\HBA\Broadcom Corporation\Broadcom NetXtreme II C-
NIC iSCSI Adapter] MaxConnections"=dword:00000080
● QLogic drivers—: [HKEY_LOCAL_MACHINE\SOFTWARE\EqualLogic\EHCM\HBA\QLogic Corporation\QLogic C-NIC
iSCSI Adapter] MaxConnections"=dword:00000080
Restart EHCM service.
ASM Error When Updating to Window Server 2016 or Windows Server Core 2016
After updating the operating system from Windows Server 2012 R2 to Windows Server 2016 (including Windows Server Core
2012 R2 to Windows Server Core 2016) with HIT/ME version 5.0.0 installed, ASM generates an error message. At this point it is
no longer possible to perform any operations from ASM.
To correct this issue, perform the following steps:
1. Run Windows Update and confirm you are running the latest version of the Windows Server 2016 software. If additional
updates are available, install them before continuing.
2. Re-run the HIT/ME installation kit to re-register the VSS provider.
Windows 2016 Schedules Not Running When Re-Enabled
After disabling and re-enabling a schedule, the schedule does not perform the scheduled task.
Workaround: When enabling a schedule, change the trigger start date and time to a new date and time when the scheduled task
should be performed.
Set-ASMCollection Cmdlet Not Functioning as Designed
When using the Set-ASMCollection PowerShell Tools cmdlet to change a collection name and modify its components, Set-
ASMCollection should replace the existing components with the specified components. Instead, Set-ASMCollection appends
the new components to the existing components.
Installing SCVMM 2012 R2 UR5 Causes EqualLogic Storage Discovery Issues
When Update Rollup 5 (UR5) is installed for System Center Virtual Machine Manager 2012 R2, SCVMM encounters issues
discovering EqualLogic Storage and reports that EqualLogic Storage was already discovered.
To resolve this issue, install Update Rollup 6 (UR6) or the latest available update rollup.
Windows 2016 SharePoint Components Not Enumerated After Fresh Install of
HIT Kit
After installing HIT/ME in an environment consisting of a Windows 2016 host with SQL 2016 and a Windows 2016 host with
SharePoint 2016, the left panel of the ASM GUI shows the components in a Warning state and the farm components are not
enumerated.
To correct (or prevent) this issue, download and install Microsoft update KB3118289 for Microsoft SharePoint Server 2016.
You can find this update at: support.microsoft.com/kb/3118289
Exchange Replica Smart Copies Might Require Manual Soft Recovery
Verification and soft recovery of Exchange replica Smart Copies are performed on the replication partner. Verification consists
of two steps: the actual verification, and the soft recovery, where the database is brought from a dirty shutdown state
to a clean shutdown state. Soft recovery requires read-write access to the database. In the case of replica Smart Copies,
this process requires some additional planning.
You can give read-write access to the Smart Copy in the following ways:
11