Skip to main content

Oracle Virtual Box – Increasing Allocated Disk Space

 

For working with Windows Server 2012 & SharePoint 2013 this time I choose Oracle Virtual Box. Microsoft has recommended 60GB of harddisk space for running Windows Server 2012 and SharePoint 2013. When creating new virtual machine (VM) the Vbox took 25 GB as the default for hard disk space. It also mentioned that it is dynamic allocation. I guessed that this will increase as and when the VM needs more space. 

I was wrong. I created new VM and installed Server 2012 successfully. But when I was installing SharePoint 2013 the istallation did not succeed because of less disk space. 

After some googling, I found a command (run from command prompt) to increase disk apace allocated to the VM. Below are the steps for the same.

  1. Open command prompt on host system.
  2. Navigate to C:\Program Files\Oracle\VirtualBox.
  3. Execute below command: VBoxManage modifyhd filename.vdi --resize 61440
  4. Above command will increse the allocated disk space to 60 GB.
  5. After running this command, I was still not able to see change in the VM. So in the VM I went to Server Manager. Click on “File and Storage Services”.
  6. Now click on “Disks”

 7. Right click on C: in Volumes section and click on Extend Volume.

  
8. Now enter the New Size and click OK.



After these steps, I was able to proceed with SharePoint 2013 installation. Hope this helps people who are working on Virtual Box. 

-Vighnesh Bendre




 


Labels:

Comments

Post a Comment

Popular posts from this blog

Working with large xml files in c# .net

Working with large (huge) xml files is always a pain in the … The reason? These files can’t be loaded in to memory. On my desktop, where I have 2 gigs memory, I can’t open the file in even notepad. I was presented with a challenge recently to manipulate one such large xml file. The xml file was of 550+ MB. I know many would say I have seen bigger xml files than this. But the heart of the matter is if I can’t open 550+ MB file in notepad or in xmldocument in c#, then I can’t open any file bigger than this. And hence the logic to play with these files would remain same. The scenario: We have an xml file from which we want to remove a single node without removing its children. In the below sample xml fragment, the node has to be removed. The children nodes, must then be attached to ( node’s parent) node. One Two 100.22 GoodDay 3 4 Five 200.09 Cra...
3 comments
Read more

Error while activating feature - SharePoint 2010

Hi all, While I was working on SharePoint 2010 recently I came across some issues. I am putting them across so that anyone facing the same issue may find solution easily. Error: Error occurred in deployment step 'Activate Features': Feature with Id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' is not installed in this farm, and cannot be added to this scope. Solutions: I was getting this error while ‘deploy’ing a feature from Visual Studio 2010. I searched the entire project for this GUID which is mentioned in the error. I did not find it anywhere. While troubleshooting, I opened the physical folder and opened ‘Feature1.feature’ file in notepad. This xml file was using the before mentioned GUID. I was not able to find it in VS 2010 :( I copied the GUID mentioned in the ‘Feature1.feature’ file and pasted it in the Feature ID section in ‘Feature1.Template.xml’ file. This solved the problem. Why I thought to mention it is because the exception thrown is confusing. It does not tell you...
10 comments
Read more

Upgrade and Migration for SharePoint Foundation 2010

      1.1 Introduction Microsoft SharePoint Foundation 2010 has been designed for scale and performance and as such requires new hardware and software requirements. There are 3 major steps while upgrading. 1. Plan and Prepare 2. Perform a database attach upgrade 3. Verify upgrade 1.2 Plan and Prepare   Before we run any process to upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010, we have to determine which upgrade approach to take. In our scenario, Database Attach Upgrade seems to be appropriate approach to follow. We can upgrade the content for the environment on a separate farm. The result is that you do not upgrade any of the services or farm settings. You can upgrade the databases in any order and upgrade several databases at the same time. While each database is being upgraded, the content in that database is not available to users. 1.2.1 Upgrade Approach A database attach upgrade enables you to move to...
4 comments
Read more