Currently I am using Windows RDP to gain access to my VMs.
Does anyone use anything other than Windows RDP? If so what is it and can you please post a link to documentation on it and explain some of the benefits of your designated RDP Service and why you use it for VMs versus Windows default RDP Service?
Thanks in advance!
VirtualBox RDP
-
frank
- Oracle Corporation
- Posts: 3362
- Joined: 7. Jun 2007, 09:11
- Primary OS: Debian Sid
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Linux, Windows
- Location: Dresden, Germany
- Contact:
Re: VirtualBox RDP
VirtualBox has a built-in RDP server. It has two benefits: First, the RDP server is available for every guest, even for non-Windows guests and for guests without a graphical output. And second, the built-in server provides some extensions, for example, with Linux hosts you can forward USB devices along the RDP connection to the guest.
-
naemrr
- Posts: 83
- Joined: 17. Dec 2011, 22:56
- Primary OS: Ubuntu other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: ubuntu natty, windows 2k3, windows xp pro, windows vista x86 & x64, debian squeeze
Re: VirtualBox RDP
If your Virtual machines are also accessible by others in any way, using the virtualbox built in RDP server instead of the windows onboard TS system is an effective attack surface reduction, you also only have to remember 1 ip or hostname, as all RDP requests are sent to the host rather than to each guest. so your access becomes more centralized.
RDP login can be setup as single login authenticated by virtualbox itself, can be setup for no login granting faster access, but less security, or even with other authentication including windows account login, which allows virtualbox to fit right in with an AD-DS enabled network. it can even grant you RDP access to a guest that normally by AD or group policy would have its rdp server demon disabled.
the windows onboard rdp however, is more compartmentalized, so if you must grant others access to a machine via rdp, there is less chance of them accessing a different machine then what they are authorized for. onboard rdp also provides quicker access to client side resources, such as hard drives and printers.
the best bet is to read the virtualbox help file on rdp, and then read the microsoft technet article for rdp and compair the features each offer, with your needs.
https://www.virtualbox.org/manual/ch07.html#idp5900528
http://support.microsoft.com/kb/300698
http://blogs.msdn.com/b/brendangrant/ar ... about.aspx
however both setups have there pros and cons, and your needs dictate what method to use,
you could enable both RDP in virtualbox and in the windows guest, and play with there features a bit, see which one fits your needs best, then simply turn off the other.
RDP login can be setup as single login authenticated by virtualbox itself, can be setup for no login granting faster access, but less security, or even with other authentication including windows account login, which allows virtualbox to fit right in with an AD-DS enabled network. it can even grant you RDP access to a guest that normally by AD or group policy would have its rdp server demon disabled.
the windows onboard rdp however, is more compartmentalized, so if you must grant others access to a machine via rdp, there is less chance of them accessing a different machine then what they are authorized for. onboard rdp also provides quicker access to client side resources, such as hard drives and printers.
the best bet is to read the virtualbox help file on rdp, and then read the microsoft technet article for rdp and compair the features each offer, with your needs.
https://www.virtualbox.org/manual/ch07.html#idp5900528
http://support.microsoft.com/kb/300698
http://blogs.msdn.com/b/brendangrant/ar ... about.aspx
however both setups have there pros and cons, and your needs dictate what method to use,
you could enable both RDP in virtualbox and in the windows guest, and play with there features a bit, see which one fits your needs best, then simply turn off the other.