Running a VM as a user after configuring as an admin

[supercrazymark]

Hello,
I am working on getting a Virtualbox solution running at the school I am the Network Manager at.

All has gone really well and my setup is as follows:

- Virtualbox is installed locally on each computer
- The virtualbox files (.vbox etc) are located in C:\Virtualbox on each computer
- Everyone has full control of C:\Virtualbox and, for good measure, C:\Program Files\Oracle\VirtualBox

After configuring (register & test) a VM while logged in as an admin I am able to log off (or reboot) and log in as any of my other admin accounts and run Virtualbox with no issues.

However, if I log in as a student (as standard user) when I click to open Virtualbox nothing happens. No errors, nothing!

Is there any other locations that I should be allowing a standard user access to?

I am so close! When i open as an admin my Virtual image is perfect... this is the last hurdle

[supercrazymark]

...after a bit more research I have found the log file. Here is a sample logfile:

Code: Select all   Expand viewCollapse view

VirtualBox COM Server 4.2.16 r86992 win.x86 (Jul  4 2013 16:33:12) release log
00:00:00.000000 main     Log opened 2013-07-11T10:27:51.335592800Z
00:00:00.000000 main     OS Product: Windows 7
00:00:00.000000 main     OS Release: 6.1.7601
00:00:00.000000 main     OS Service Pack: 1
00:00:00.093000 main     DMI Product Name: RM EXPERT 3040
00:00:00.156000 main     DMI Product Version: 1.0
00:00:00.156000 main     Host RAM: 3031MB total, 1594MB available
00:00:00.156000 main     Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.156000 main     Process ID: 2492
00:00:00.156000 main     Package type: WINDOWS_32BITS_GENERIC
00:00:00.515000          usbLibDevStrDrEntryGet: DeviceIoControl 1 fail winEr (31)
00:00:00.968000          VDInit finished
00:00:00.984000          ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={3b2f08eb-b810-4715-bee0-bb06b9880ad2} aComponent={VirtualBox} aText={Could not find a registered machine named 'VirtualComputingVM'}, preserve=false


Is it possible to auto register the VM when the user opens it?

Currently my bat file to open the VM looks like this:

Code: Select all   Expand viewCollapse view

cd "C:\Program Files\Oracle\VirtualBox\"

vboxmanage setproperty machinefolder "C:\VirtualBox"

pause

VBoxManage registervm "C:\VirtualBox\VirtualComputingVM.vbox"

pause

VBoxManage setextradata global GUI/Customizations noMenuBar,noStatusBar

pause

VBoxManage setextradata "VirtualComputingVM" GUI/RestrictedCloseActions SaveState,Restore

pause

VBoxManage setextradata "VirtualComputingVM" GUI/Input/MachineShortcuts "FullscreenMode=None,SeamlessMode=None,SettingsDialog=None,TakeSnapshot=None,ScaleMode=None"

pause

VBoxManage modifyvm "VirtualComputingVM" --biosbootmenu disabled

pause

VBoxManage modifyvm "VirtualComputingVM" --memory "1024"

pause

VBoxManage modifyvm "VirtualComputingVM" --bioslogoimagepath "C:\Program Files\Oracle\VirtualBox\SWGSSplashscreen.bmp"

pause

VBoxManage startvm "VirtualComputingVM"

pause


(pauses in there so I can see whats happening).

Am I doing it right or is there a different way of doing this?

Any help/advice is very much appreciated...

Mark

[supercrazymark]

Just incase anyone is reading this thread, I may have solved it (but not tested properly yet).

I copied the VirtualBox.xml file from the .Virtualbox directory of the admin account and copied it into the user account, logged on as the user and it worked.

Am looking into testing this further....

[noteirak]

Looks like a permission issue actually - each user should be able to create the .Virtualbox folder in its own home folder, you shouldn't require admin rights.
I guess you locked down the profiles a bit too much on this one

[supercrazymark]

Looks like a permission issue actually - each user should be able to create the .Virtualbox folder in its own home folder, you shouldn't require admin rights.
I guess you locked down the profiles a bit too much on this one

I think you are right Being a school we have to have student stations locked down as much as possible...

Copying the xml file from a share (sourced from my admin login) into the correct user loaction works (as I have written an exe that does all sort of houskeeping when the VB is started).

Interestingly, Virtualbox only starts one in every two to three clicks and I can't work out why lol...

[noteirak]

Interestingly, Virtualbox only starts one in every two to three clicks and I can't work out why lol...

Most likely more permission issues.

[supercrazymark]

Interestingly, Virtualbox only starts one in every two to three clicks and I can't work out why lol...

Most likely more permission issues.

Thats what I thought, but if it was permission issues surely it would either work all the time or not work all the time? Today I am going to try and relax the security on the %user%\.Virtualbox folder and see if that makes a difference.... I'll update this post with my results

[mpack]

Running the installer with admin rights is ok (in fact necessary I believe). Installing while logged in as user "Admin" is not so ok, unless that is how you'll always be wanting to use the VM.

[supercrazymark]

Running the installer with admin rights is ok (in fact necessary I believe). Installing while logged in as user "Admin" is not so ok, unless that is how you'll always be wanting to use the VM.

Here is what I currently do:

1 - Log into the computer as an administrator
2 - Install VB
3 - Configure VB
4 - log off

Then, when I log in as a user I can run a bat file that runs various vbmanage commands then starts a vm. It's this stage that only seems to run once every 2-3 attempts...

[noteirak]

Then, when I log in as a user I can run a bat file that runs various vbmanage commands then starts a vm. It's this stage that only seems to run once every 2-3 attempts...

What happens if you actually run the commands yourselves?

[supercrazymark]

I will run some extensive testing next week (when the school is on summer holiday) as this week is a very busy week. My goal is to get everything working by September 2nd so wil be "on it" a lot more over the coming weeks