Release Notes

Table Of Contents
Windows Server Core 2012 and Later
All HIT/ME services run in Windows Server Core and the PowerShell Tools are supported. To use ASM/ME, you must add the
server to ASM/ME on Full UI OS and mange the Server Core machines.
ASM/ME does not allow use of the GUI to set MPIO parameters. Instead, use the Dell EqualLogic PowerShell Tools.
Operation
The following operational constraints apply in this release for all supported operating systems.
VSS Does Not Allow Backup and Restore Operations on tempdb
Each time the SQL Server is started, a clean copy of the system database tempdb is recreated. This database minimally logs
operations such as temporary tables and stored procedures. This logging enables transactions to be rolled back.
The VSS does not allow backup and restore operations to work on tempdb. After the current SQL Server session disconnects,
and no other connections are active at system shutdown, the temporary tables and stored procedures are automatically dropped
from the database. Because no type of data is permanently stored in tempdb from one SQL Server session to another, the
database does not need to be saved.
For more information about the tempdb system database, see the Microsoft Knowledge Base article at msdn.microsoft.com/
en-IN/library/ms190768.aspx.
VMM Selective Restore of a Rapid Provisioned HA VM Smart Copy Fails With
Error
You cannot perform a selective restore operation on VM components that are on volumes without mount points. The selective
restore operation uses file copy operations that requires the volume to have a mount point.
The files are in \\?\{GUID} format.
Smart Copy is Disabled for Cluster Shared Volumes
The Smart Copy feature is disabled for Cluster Shared Volumes when:
Components for Hyper-V writer and SQL writer are on the same CSV.
SQL components are on the same CSV, but no SQL instance is owned by the current node.
Networking
This section contains information about network and firewall configuration, and general networking constraints.
Using the HPC Server with Broadcom Ethernet NICs
When setting up systems equipped with Broadcom Ethernet NICs to be used as HPC base or compute nodes with iSCSI storage,
you might find that the Broadcom card does not accept the IQN string set for it by the HPC server. This failure will cause login
failures when the node attempts to boot from its iSCSI volume, because the HPC head node configures the iSCSI boot volumes
with IQN-based ACLs.
To resolve this issue, change the BIOS setting on the Broadcom card and use a template string in the HPC settings when you
configure the node template, as shown in the following procedure:
1. Start the HPC iSCSI Settings App from the Start Menu, click Start All Programs EqualLogic HPC iSCSI Provider
Settings.
2. Click Create new volumes with open ACLs.
This option allows any initiator to log in to the volume.
6