It seems that whenever they tried to connect to a remote server and use the Disk Management snap-in, they got this error: And this is what it looks like: Searching Google for an answer brought a few results, but I thought I’d list it here for my other readers, as it seems that the configuration steps that are needed in order to get remote disk management going are a bit vague.
In order to remotely manage disks on a Windows Server 2008 R2 machine, you need to perform the following tasks: On the target server (the one you want to connect to) you need to set the Virtual Disk Service (VDS) to Automatic, and start it.
Windows Resource Protection did not find any integrity violations. However, rather than format and reinstall from scratch I would first try in in-place reinstall, which generally leaves most settings and configurations intact.
Ping statistics for .22: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Only you can make that assessment.
Most documents and manuals fail to specify that, and unless you enable the rules on both machines, you will not be able to connect. I don't know why but for some reason I can't make the resident protector to work on my W2k pro.I am getting this error message: "The AAVM subsystem detected an RPC error! I don't know why but for some reason I can't make the resident protector to work on my W2k pro.RPC is an interprocess communication (IPC) method that is used by clients and servers to communicate with each other.Simply put, RPC is used by programs, typically on a client computer, to execute a program on a server computer.So, open a Command Prompt window and type the following command to enable the remote-volume-management firewall exceptions: Again, this can also be done through the Windows Firewall with Advance Security snap-in.