. . . . . . . . . . . . . . . . . . . . . 172 12.5.3 Sluggish response when using Microsoft RDP client . . . . . . . . . . . 172 12.5.4 Running an iSCSI initiator and target on a single system . . . extremely modular design with well-defined internal programming interfaces and a clean separation of client and server code. This makes it easy to control it from several interfaces at once: for example, you Remote Desktop Protocol (RDP) originally built into Microsoft Windows, with special additions for full client USB support. The VRDE does not rely on the RDP server that is built into Microsoft Windows; instead

. . . . . . . . . . . . . . . . . . . . . 173 12.5.3 Sluggish response when using Microsoft RDP client . . . . . . . . . . . 173 12.5.4 Running an iSCSI initiator and target on a single system . . . extremely modular design with well-defined internal programming interfaces and a clean separation of client and server code. This makes it easy to control it from several interfaces at once: for example, you Remote Desktop Protocol (RDP) originally built into Microsoft Windows, with special additions for full client USB support. The VRDE does not rely on the RDP server that is built into Microsoft Windows; instead

recognized . . . . . . . . . . . . . . . . . . 201 12.5.3 Sluggish response when using Microsoft RDP client . . . . . . . 202 12.5.4 Running an iSCSI initiator and target on a single system . . . . . 202 run virtual machines as mere servers for the VirtualBox Remote Desktop Protocol (VRDP), with full client USB support. This allows for consolidating the desktop machines in an enterprise on just a few RDP extremely modular design with well-defined internal programming interfaces and a clean separation of client and server code. This makes it easy to control it from several interfaces at once: for example, you

. . . . . . . . . . . . . . . . . . . . . 168 12.5.3 Sluggish response when using Microsoft RDP client . . . . . . . . . . . 168 12.5.4 Running an iSCSI initiator and target on a single system . . . extremely modular design with well-defined internal programming interfaces and a clean separation of client and server code. This makes it easy to control it from several interfaces at once: for example, you Remote Desktop Protocol (RDP) originally built into Microsoft Windows, with special additions for full client USB support. The VRDE does not rely on the RDP server that is built into Microsoft Windows; instead

. . . . . . . . . . . . . . . . . . . . . 171 12.5.3 Sluggish response when using Microsoft RDP client . . . . . . . . . . . 171 12.5.4 Running an iSCSI initiator and target on a single system . . . extremely modular design with well-defined internal programming interfaces and a clean separation of client and server code. This makes it easy to control it from several interfaces at once: for example, you Remote Desktop Protocol (RDP) originally built into Microsoft Windows, with special additions for full client USB support. The VRDE does not rely on the RDP server that is built into Microsoft Windows; instead

. . . . . . . . . . . . . . . . . . . . . 174 12.5.3 Sluggish response when using Microsoft RDP client . . . . . . . . . . . 174 12.5.4 Running an iSCSI initiator and target on a single system . . . extremely modular design with well-defined internal programming interfaces and a clean separation of client and server code. This makes it easy to control it from several interfaces at once: for example, you Remote Desktop Protocol (RDP) originally built into Microsoft Windows, with special additions for full client USB support. The VRDE does not rely on the RDP server that is built into Microsoft Windows; instead

. . . . . . . . . . . . . . . . . . . . . 174 12.5.3 Sluggish response when using Microsoft RDP client . . . . . . . . . . . 174 12.5.4 Running an iSCSI initiator and target on a single system . . . extremely modular design with well-defined internal programming interfaces and a clean separation of client and server code. This makes it easy to control it from several interfaces at once: for example, you Remote Desktop Protocol (RDP) originally built into Microsoft Windows, with special additions for full client USB support. The VRDE does not rely on the RDP server that is built into Microsoft Windows; instead

. . . . . . . . . . . . . . . . . . . . . 188 12.5.3 Sluggish response when using Microsoft RDP client . . . . . . . . . . . 189 12.5.4 Running an iSCSI initiator and target on a single system . . . extremely modular design with well-defined internal programming interfaces and a clean separation of client and server code. This makes it easy to control it from several interfaces at once: for example, you Remote Desktop Protocol (RDP) originally built into Microsoft Windows, with special additions for full client USB support. The VRDE does not rely on the RDP server that is built into Microsoft Windows; instead

. . . . . . . . . . . . . . . . . . . . . 188 12.5.3 Sluggish response when using Microsoft RDP client . . . . . . . . . . . 189 12.5.4 Running an iSCSI initiator and target on a single system . . . extremely modular design with well-defined internal programming interfaces and a clean separation of client and server code. This makes it easy to control it from several interfaces at once: for example, you Remote Desktop Protocol (RDP) originally built into Microsoft Windows, with special additions for full client USB support. The VRDE does not rely on the RDP server that is built into Microsoft Windows; instead

. . . . . . . . . . . . . . . . . . . . . 200 12.6.3 Sluggish response when using Microsoft RDP client . . . . . . . . . . . 200 12.6.4 Running an iSCSI initiator and target on a single system . . . extremely modular design with well-defined internal programming interfaces and a clean separation of client and server code. This makes it easy to control it from several interfaces at once: for example, you Remote Desktop Protocol (RDP) originally built into Microsoft Windows, with special additions for full client USB support. The VRDE does not rely on the RDP server that is built into Microsoft Windows; instead