Jump to content

Recommended Posts

Posted

For anyone who has used the CC4 VirtualBox package:

Have you had issues with permissions on the folder containing the VDI?

From memory, the path is something like C:\Program Files\RM\VirtualBox VMs but needs modify permissions in order to run the VM

The machines I've tested on, I've got working by adding the modify permissions for Authenticated Users.

 

Just looking for a quick (or better) way of updating the permissions on each machine or even if I've just missed something when importing the package.

  • 1 month later...
Posted

Hi All

 

We have been using this fine now for over a year but unfortunately Windows on the virtual box image now requires activation on every single PC. Mapping of the user drive fails whilst Windows needs activation. Anyway to setup our virtual image so that the activation doesn't expire?

 

Regards

Posted

Hi

 

We originally set this up with a MAK key but weirdly the image on every single PC has now lost its activation. Does it expire if there is no access to the Internet after a year?

 

Regards

Posted (edited)

We originally set this up with a MAK key but weirdly the image on every single PC has now lost its activation. Does it expire if there is no access to the Internet after a year?

 

MAK keys aren't supposed to expire but I notice it mentions they require reactivation on hardware changes. So if you amended VM settings or upgraded to a newer version of VirtualBox both these things could potentially require re-activation?

Edited by flyinghaggis
Posted
We are still using the same version of VBox and have not changed any of the settings. This has happened to every machine (160) at the same time which doesn't make sense.
Posted (edited)

Hi mshill and all

I am responding to mshill. I have successfully implemented the RM VirtualBox at my school. Although some time ago and a right pain in the ass it was! I set it up to start fresh on every lunch. I activate Windows before packaging. Full access to the student N drive mapped. I also remove the NIC before packaging too. It's a sandbox so no access to my network!!! Been doing this for some years now and it works for me. Well until some teacher start asking for additional software on the vm, then back to square one to building a new vm.

 

I must say that I owe a lot to the members of this forum for getting this packaging right.

Edited by WhiteStar1
Posted
We are still using the same version of VBox and have not changed any of the settings. This has happened to every machine (160) at the same time which doesn't make sense.

Did you activate before pacakging? I am unaware of the legal issues for multiple copies of the same vm on many machines but it's the road I went down and it's working for us.

Do you still have the nic on the vm?

  • 3 months later...
Posted

I am just updating the contents of the VM in Virtualbox to update versions of Python, Notepad++ and Small Basic. I changed the disk from immutable to Normal made my changes and then put it back to immutable. Now every time I boot the VM it comes up with a restart dialogue box "You must restart your computer to apply these changes". I can't seem to get rid of this message. If I change the disk back to normal the message comes and then I reboot and it goes away but when I change the disk to immutable the message comes back.

 

Any ideas?

Posted

Hi

 

You need to go into Virtual Media Manager and release and delete the differencing vdi.

 

Then change the disk to normal make the changes you wish. You then change the disk back to immutable after that and it will be remembered.

 

Unfortunately you will probably lose the changes you have already made. If you change the disk to normal whilst the differencing disk is still attached it will always revert back to that.

 

Regards

 

 

I am just updating the contents of the VM in Virtualbox to update versions of Python, Notepad++ and Small Basic. I changed the disk from immutable to Normal made my changes and then put it back to immutable. Now every time I boot the VM it comes up with a restart dialogue box "You must restart your computer to apply these changes". I can't seem to get rid of this message. If I change the disk back to normal the message comes and then I reboot and it goes away but when I change the disk to immutable the message comes back.

 

Any ideas?

  • Thanks 3
Posted (edited)
Hi

 

You need to go into Virtual Media Manager and release and delete the differencing vdi.

 

Then change the disk to normal make the changes you wish. You then change the disk back to immutable after that and it will be remembered.

 

Unfortunately you will probably lose the changes you have already made. If you change the disk to normal whilst the differencing disk is still attached it will always revert back to that.

 

Regards

 

I'm in the virtual media manager and the only option for the differencing vdi (theres 3 of them) is remove. Can't see a release or delete option. We are using Virtual Box 4.3.12

 

edit : Scratch that, I found it.

 

edit : Ok - I removed the differencing vdi's but now the VM won't boot!

Edited by fiza
  • 5 months later...
Posted
How is the VM image created (The one that is copied to each hard drive) Do you export appliance and copy the OVA file?

 

I found doing that reset the hardware and when I imported it to a new machine it wanted to reinstall drivers and lost OS and Office activations.

 

I just copy the VM folder to each machine and that seemed to fix it. As we have it running on a few different PC types I found I had to run it on each type to get the drivers for each set up and then it stopped asking for a reboot as well.

Posted

We are currently having an issue where the VM does not always boot as there are some VBox services running which even admin cannot stop.

 

It seems to occur if the VM has not been shut down cleanly by the previous user. It's become a bit of a nightmare as our VMs are often used in back to back lessons.

 

The next user runs the batch file to launch the VM and it either closes without doing anything or hangs waiting for the VM to finish doing something which can take 15 minutes.

Posted

Yeah that comes up a few times, we've made it impossible to close it without shutting down but that still doesn't stop some from hard-resetting them.

A script on startup (which could be SCCM automated if you wanted) could check files for versions/sizes and replace them for an easy route; we just tend to manually copy the files from a working machine :D

Posted
Yeah that comes up a few times, we've made it impossible to close it without shutting down

 

How did you do that?

 

.... we just tend to manually copy the files from a working machine

 

We do a copy but there are some files that can't be deleted or overwritten if the services are running.

 

It seems to be an issue with more recent versions of VirtualBox but there is no fix for it yet.

Posted

We've kept on the same old version as I had at the start of this thread, so haven't seen any of those issues; likely we'll keep it that way than! :)

One of the switches we used (further back in this thread) prevents closure with the X button, and set up local policy on the vm windows itself to hide all exit points other than shut down.

  • 1 month later...
  • 3 weeks later...
Posted
I have bidirectional clipboard enabled on the VM and users can cut and paste from guest to host but it only does it in mono. Is there any way users can cut and paste text in colour?
  • 3 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...