virtualbox.org

Hi,
I want to install a Windows 10 VM on a Linux based cluster I am a part of. The cluster has VBOX installed and I can create VMs with ease. However, I am kind of stuck trying to install a windows 10 VM as I don't know how to enable a remote connection and how to connect to that remote connection so I can continue the windows installation. The server does not support gui, so I don't have access to the VBOX's graphical interface, so the vm has to run in headless mode. Can someone point me towards what I can do?
Currently what i have tried is having a vm with:
NIC 1: MAC: ************, Attachment: Bridged Interface 'eth0', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
VRDE: enabled (Address 0.0.0.0, Ports 3389, MultiConn: on, ReuseSingleConn: off, Authentication type: external)

I connect to a server using ssh. Furthermore, there is another server I can connect to however that is not directly accessible, i.e. I have to connect to a specific node and then ssh from there to change. In an ideal case, I would love to have a VM on both of these servers.

All the Windows 10 installs I have done had a GUI. Without a GUI on your host, I believe you'll have to either use Virtualbox's VRDP and 'cheat' with another GUI PC, or research how to do a Windows 10 unattended install, and apply the methods to the Virtualbox guest.

You'll probably get a lot farther trying the unattended-install process on a host that has a GUI for practice, so you can see the problems, then try it on the headless server.

Virtualbox 'headless' really means 'monitorless'. The guest GUI-based OS will run a GUI even when running 'headless' in Virtualbox. Enable Virtualbox's VRDP or VNC through the Extension Pack, and you can see the GUI over the network even when running on a true headless host. (Mind that the port number isn't in use by the host itself, and that the host's firewall allows that port.)

Additionally, try VRDP without authentication. I've seen problem reports in the past with using other authentication modes. If you're tunneling the RDP traffic through your SSH connection, and consider that the RDP endpoint really is the Linux server, then you probably don't need RDP authentication at all.

Thanks for the replies, I ended up kind of cheating and installing the Windows by cloning the vm from another pc to the server. The second server luckily had Scientific Linux so there I had access to a GUI.

No cheating there, unless it was a test. That's what I would have done: make it on a GUI host then move it to the headless host.