To manage storage subsystems on a remote computer, you can connect to the computer from Storage Manager for SANs. While you are connected, Storage Manager for SANs allows you to create and manage LUNs on Fibre Channel and iSCSI disk storage subsystems that are discovered by Virtual Disk Service (VDS) on the remote computer.
Storage Manager for SANs can manage storage subsystems discovered on the local computer or a remote computer, but not on both computers at the same time.
Membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure. Review details about using the appropriate accounts and group memberships at http://go.microsoft.com/fwlink/?LinkId=83477.
|To connect to a remote computer from Storage Manager for SANs|
In Administrative Tools, click Storage Manager for SANs.
In the console tree, right-click Storage Manager for SANs, and then click Connect to another computer.
In the Connect to Another Computer dialog box, click Another computer. Then type the name of the computer that you want to connect to (or click Browse to search for a remote computer).
The Connect to another computer command is available only when you open Storage Manager for SANs from Administrative Tools. When you access Storage Manager for SANs from Server Manager, the command is not available.
- You must be logged on to the local computer
with a domain account that is a member of the Administrators
group on the remote computer.
- The remote computer must be running Windows
Server 2008, and it must be a member of the same domain as the
computer you are connecting from. You cannot connect to a remote
computer if both computers are members of a workgroup.
- At least one VDS hardware provider must be
installed on the remote computer. Connecting to a remote computer
from Storage Manager for SANs will start the Virtual Disk service
and the VDS hardware provider(s) installed there.
- The Remote Volume Management firewall
exception must be enabled on both the local computer and the remote
computer. Enable this exception by using Windows Firewall from