Setting up your Virtual Machine for SharePoint 2010
Update: The below is a guide to install 2010 on a dev style setup for someone that doesnt have HyperV. Here is a link to a full install. (Install SharePoint 2010 and manually Configure Service Accounts)
As most of us know by now either for better or worse, SharePoint 2010 is now officially 64 bit. As I’ve mentioned in previous posts there is a product (free) out called “Suns VirtualBox”. I won’t go too in depth with what this is but in the end know that it is possible (given hardware that supports virtualization) to run a 64 bit guest on a 32 bit host. Crucial if you want to play but don’t have the 64 bit environment to do so.
There have been a lot of folks in the TAP program that have installed SharePoint 2010 and have had their trigger finger ready for when the NDA was lifted. So by now there are a few very solid install guides out there so what I’m about to share is nothing new. However, that said I’m going to approach it from the perspective that you want to build a sandbox that is lightweight and could possibly be on a 32 bit host, so that you can play around with SharePoint 2010 and get used to the new features that are coming down the pipe.
Some expectation setting:
This will be a standalone installation. In my opinion there are some very good reasons as to when you would want to use standalone. None of them usually existing in a production environment, however using it for a sandbox or a demo machine is a really good example
I will be using VirtualBox. Personally, I’m annoyed that I can’t use hyper V on a windows 7 machine, VMWare Workstation isn’t free, VmWare Server is buggy and Virtual PC doesn’t support 64 bit. Hence, VirtualBox.
This install was done on 64 bit with 8 gigs ram. This doesn’t really matter, other that speed nothing should change. Hardware virtualization. Needs to be enabled on your machine. If your cpu doesn’t support this (regardless of 64 bit or not) you’re out of luck using VirtualBox (and maybe some other methods).
You will need:
Access to a Windows Server 2008 (64 bit) cd/dvd/iso (i used standard, R2 gave me hell!)
License key for said install
First thing is first
We need to go download VirtualBox. You can run over to http://www.virtualbox.org/ and get the install. Again it’s free. Go ahead and install the application. Now for the step by step.
1) Once you have your VirtualBox instance installed run the short cut and you should see something similar to what I have here. Obviously minus the virtual machines already listed. Hit “New”
2) Hit “Next” on the welcome prompt
3) Now you will choose a name for your VM (virtual machine). Try to pick something concise yet descriptive you could have a few VMs in the end. On the same screen select “Windows Server 2008 (64bit)” in the Version drop down if this option is not available to you, you have either not enabled “Hardware Virtualization” correctly in your machines Bios, or you don’t have said option and cannot proceed from here. Hit “Next”
(Do a bing search on your laptop and “Hardware Virtualization to find out how to exactly enable it for your machine)
4) Now you will choose how much RAM you want allocated to your VM when it is running. I have an 8 gig machine so I can choose a higher amount. If you have 4 gigs total go with 2 gigs to start. This screen is tricky because if you allocate more than half of the ram you have for your system it will “gray out” the “Next” option. For now, choose a level that will let you continue. You can change this in the “Settings” of that VM later.
5) Now you’ll choose to create a new hard disk. You won’t have one already created unless you imported one so leave this option selected and hit “next”.
6) Click “Next” on the welcome wizard screen
7) The next screen lets you choose if you want fixed or dynamically sliding storage. Keep dynamic selected unless you have a real hardware limitation. Otherwise you’ll run out of space with the install and won’t be able to continue.
8) On the next screen the name of your VM will be visible with the option to create the VM at a specific location. It may be very important to choose an alternate location for your VM at this point. Its not a requirement but you may want the 10+ gig file to live on a specific drive or folder.
Also choose the amount of VIRTUAL storage size you want to give the drive to start out. Just because you give this a Virtual size doesn’t mean that is how much actual physical storage it will take up on a disk, its just how much your VM sees it has to start with.
I recommend choosing at least 50 gigs if you can.
9) Lastly, take note of where the VM has been placed, you’ll need to know this at some point or another later.
10) Once you hit finished on the previous screen, a wizard will pop up letting you know this is the first time you’ve created a VM and suggests allowing you to mount a CD/DVD drive to the VM. If you have a CD/DVD with the Windows Server 2008 installation on it, go ahead and mount the drive. This will allow you to install from the CD/DVD as we’re all used to doing when formatting and installing a new OS.
At this point you will let the VM install in totality the Windows Server 2008 operating system. Sit back and watch TV for a while.
Now the fun stuff
Now we need to run all the patches and updates for the OS in order for SharePoint to run.
1) In the control panel > windows update section, install/allow the windows update to happen. You’ll have a few installs to do here and will need to restart
2) Once you get your machine back up the Server Manager will pop up and you’ll see the area highlighted for “Add Roles” Click this.
3) Next you’ll see a “Before you begin” page, you can check “Skip this page by default” its an annoyance.
4) When adding Roles you’ll want to add at least the two selected below “Application Server” and “Web Server (ISS)” after you check those, hit “Next”
5) For each Role you select, there will be corresponding screens associated with installing the roles you’ve selected. In this screen shot you’ll see me starting to walk through the installation of the “Application Server” role. Hit “Next”
6) I selected the Web Server (IIS) Support box. When doing so I get the sub pop up that tells me the features being installed to support this role. Hit “Add Required Role Services”
7) Now I’m going through the same process for the “Web Server (IIS)” Role I chose to install. Hit “Next”
8) Now you’ll be shown all the services for the IIS Role, hit “Next”
9) Now a quick overview of all the items I’m about to install in total. Hit “Install”
10) The installation process has begun.
11) After all the items have been installed you’ll get a summary screen showing, hopefully, all the successfully installed Roles and features. Hit “Close”
12) Now a quick check to see if .Net 3.5 is installed. Navigate to “C:\Windows\Microsoft.NET\Framework” and see if you have a 3.5 folder. If you do you’re good to go. If you don’t. Go to microsoft’s site and download/install .NET 3.5
13) Next on the list is making sure we install the KB article KB971831 you’ll need to download and install this patch. This is an update that is needed to install SharePoint. I’ll spare you the boring details.
Now for SharePoint itself
Now we’re going to run through the prerequisites and the installation of SharePoint 2010 itself. Keep in mind. Before doing this. You’ll need to make the decision if you want to install active directory and make the server a domain controller as well if you want to install SQL server 05/08. As we stated in the start of this post, this is going to be a streamline version easy on resources for demos and sandbox so we’ll skip that step.
1) First download the SharePoint 2010 Beta Enterprise install file located here
2) Rule the file and you will get the below screen. Hit “Install software prerequisites” (or just hit “P”)
3) Listed are the items that the pre req installer will try to install for you. All needed to run SharePoint 2010 Beta. Hit “Next”.
4) Check the silly agree box and hit “Next”
5) Go grab a coffee or eat lunch/dinner. It’s going to be a little while. The installer will now go through and check to see if it needs to install any of the pre reqs. When it sees one it needs to install it goes through the process.
6) Once it’s all said and done you’ll get the summary screen letting you know what was installed and what was skipped/failed. Review and hit “Finish”
Note: Now is a GREAT time to shut down your VM (don’t save state)and back up the .vdi file (your whole vm) to another location. This will give you a clean installation if for whatever reason later you want to go with a full version of SharePoint with multiple servers or a full farm install. And it will be nice to have a set in stone roll back point that if all else fails you can just replace the file and start over. I HIGHLY suggest you do this now.
7) Now the install part itself. The you need to go back and run click on “install SharePoint Server” on the main screen. It will spin up and ask you for a serial number.
8) Hit that silly “agree” check box then hit “Continue” (continue huh? I was getting tired of typing “Next”)
9) Now back to this little issue. Yes it is usually not a good idea to install SharePoint Standalone. Certainly never do this in a production environment. However again, for this example we’re going with a standalone version. Click “Standalone”
10) And away we go, the installation process is underway. Just let it do its thing.
11) Once it finishes, you’ll want to run the Confi wizard. Select the check box and hit “Close”
12) We go through yet another round of welcome screens. Hit “Next” (oh nice, there’s next again)
13) You will be prompted that you’re about to restart IIS and install stuff on your server, are you ok with that? Sure you are. Hit “Yes”
14) Now you will start the 10 steps to SharePoint bliss. Sit back and let the configuration wizard do its thing.
After a few minutes you should get lucky and see the following:
I had a bit of an issue at the end of my installation. I kept getting an error saying “Configuration Failed. One or more configuration settings failed. Completed configuration settings will not be rolled back. Resolve the problem and run this configuration wizard again. The following error contains detailed information about the failures. Failed to create sample data.”
I attempted to install a few times and kept getting this same error. I finally said forget it and clicked on the Central Administration shortcut anyway and was taken to my Central Administration site. I poked around for a bit then restarted. When I came back up, I ran the configuration wizard again and received a successful configuration prompt. I’m not exactly sure what the issue is but it seemed to be only me having this issue.
A bit of “bing’ing” and I found that people were running into this issue because of lack of memory. I know that’s not the case for me, I had plenty allocated. I think it might be an artifact of using VirtualBox. Other than that I can’t explain it but the environment is setup and is running great. So if you have the same issue I had try opening up C.A., heck even try creating your first web app/site collection. Then restart and run the wizard again, you should be ok.
I hope that was helpful for some of you, enjoy and good luck!