HP StorageWorks SAN Virtualization Services Platform 3.0.2 Release Notes (5697-0347, May 2010)

Operating system issues
The Windows Server 2008 UAC prevents applications requiring admin privileges from working
Due to security concerns within organizations, users may be prevented from logging into the VSM
server with administrative privileges. The User Account Control (UAC) in Windows Server 2008
prevents applications like the VSM Monitor from running unless an administrator authorizes
administrative privileges. Logging in without these privileges may result in an “Assertion failed” screen
for the VSM Monitor.
To overcome this issue, a one-time procedure can be performed:
1. Log in to the VSM server using a user account that is part of the local administrators group only
(but not using the administrator account itself).
2. Go to Start > Programs > SVSP and right-click SVSP Monitor.
3. Click Properties, and then select the Compatibility tab.
4. Under Privilege Level, select Run this program as an administrator, and then click OK.
Windows offers to format newly discovered disks resulting in data loss
With Windows 2008 running on VSM servers, a dialog box occasionally appears asking if a
discovered disk should be formatted with the default set to yes. This also occurs when performing an
“import-in-place” for LUNs containing data and for SVSP setup volumes. Letting Windows format the
disk results in data loss on imported LUNs or having the setup volumes erased. Do not use Windows
to format LUNs or volumes when you receive this message. HP is working with Microsoft to resolve
the issue.
Windows partitions on imported LUNs can be seen in the VSM on Windows Explorer but not
in the device or Disk Manager window
A LUN after an Import-in-Place operation can be accessed (read/write) as a normal disk from the
VSM server. The process of Windows mounting the device on the VSM server can result in corruption
if the device is still mounted when the VSM server is rebooted. Windows Server 2008 on the VSM
server will run the Check Disk utility on that LUN and cause applications that may be accessing this
volume through SVSP to question its integrity. An HP engineering advisory was written for this issue.
To disable Windows 2008 Auto Mount (after the VSM software is installed on both VSM servers,
after the setup volumes are created, and after performing one test of VSM failover and failback), enter
these commands from the command line: Diskpart, Automount disable, and exit.
If the LUN is already imported and mounted to the VSM, use the MountVol D:\ /P command
(where D is the drive letter assigned to the mounted, imported LUN) for every LUN receiving an
Import-in-Place. This unmounts the LUN and prevents Windows Server 2008 from remounting it after
a reboot. Be sure that you do not unmount the setup virtual disk.
Miscellaneous Windows issues
The following are currently issues with Microsoft Windows:
• For a Windows HyperV environment, the only supported guest operating systems are the Windows
operating systems—Windows Server 2003 SP2, Windows Server 2008 SP1/SP2, and Windows
Server 2008 R2. HP DSM is not expected to support any non-Windows guest operating system
in a HyperV environment.
12