2
Managing many users within a security-strict network makes a VM a bad option. If the admin allows the installation of VirtualBox throughout the network, how can admins force users to setup host-only VMs?
The VirtualBox Manager needs admin rights to install a Host-Only Adaptor, but does not need admin rights to enable NATing on a Virtual network adaptor. My use-case is just the opposite; I need to block NATing.
Is there a post-installation step to disable NATing, uninstall the service, or simply hide it from the VB Manager?
Environment:
- Windows 10 64-bit
- Oracle's VirtualBox
Any tips are welcome.
Tarek Eldeeb
Posted 2018-03-06T11:03:33.090
Reputation: 133
Why would you allow the installation of Virtualization Solutions in the first place in this scenario? – Seth – 2018-03-06T12:10:58.637
Some users really need to have a VM, for tools compatibility, testing on other platforms .. etc. But they should not be allowed to access the network. – Tarek Eldeeb – 2018-03-06T14:04:49.783
Why not offer those VMs from a centralized service rather than on the users computer? You could also check the virtual box manual section 9.20 Locking down the virtual box GUI. Though this could probably be reversed by using vboxmanage I'd guess.
– Seth – 2018-03-06T14:11:35.473