Release Notes

Table Of Contents
Consequently, the relevant task wizards in Auto-Snapshot Manager (or ASMCLI commands) such as Unmount, Logoff, or
Delete might display a Volume in use error.
If you encounter this problem and you are certain that no application is using the volume, you can select the Ignore option in
Auto-Snapshot Manager or you can set the disk offline on Windows Server 2012 by using the following procedure:
CAUTION: Following this procedure (using either the ASM/ME GUI or the ASMCLI) when one or more files are in use
might result in data loss or corruption.
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 10 or Windows Server 2012 R2 or
Later
The Storage Management Provider (SMP) does not support the following PowerShell cmdlets in Windows 10 and Windows
Server 2012 R2 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.
5