Appendix E: Informational Notes384Virtual Media Support on Windows 7, Windows 2008 and WindowsXP TargetsVirtual media is not supported on a Windows 7, Windows 2008 orWindows XP target server when connecting via VKC and AKC fromWindows 2008 or Windows 2012.Virtual Media Not Refreshed After Files AddedAfter a virtual media drive has been mounted, if you add a file(s) to thatdrive, those files may not be immediately visible on the target server.Disconnect and then reconnect the virtual media connection.Virtual Media Linux Drive Listed TwiceFor KX III, users who are logged in to Linux™ clients as root users, thedrives are listed twice in the Local Drive drop-down.For example, you will see eg /dev/sdc and eg /dev/sdc1 where the firstdrive is the boot sector and the second drive is the first partition on thedisk.Accessing Virtual Media on a Windows 2000A virtual media local drive cannot be accessed on a Windows 2000®server using a D2CIM-VUSB.Disconnecting Mac and Linux Virtual Media USB DrivesIn a Linux® or Mac® environment: For Linux users, if there is /dev/sdb and /dev/sdb1, the client onlyuses /dev/sdb1 and advertise it as removable disk /dev/sdb is not available for the user. For Linux users, if there is /dev/sdb but no /dev/sdb1, /dev/sdb isused as a removable device For Mac users, /dev/disk1 and /dev/disk1s1 is usedTarget BIOS Boot Time with Virtual MediaThe BIOS for certain targets may take longer to boot if media is mountedvirtually at the target.To shorten the boot time:1. Close the Virtual KVM Client to completely release the virtual mediadrives.
