In a discussion on twitter yesterday a number of people expressed their opinions on how best to run SharePoint in a dev environment or simply on your laptop.  People are looking for easy to run and configure and minimize memory with validation, development, demos, and prototyping as goals.

Quick Links to the SharePoint VHDs and Bits

• SharePoint 2010 Beta 2 Windows Server 2008 VHD (IW Demo)
• Microsoft Office SharePoint Server 2007 VHD – You can use this to replicate your environment for sample upgrades or for testing upgrade
• Microsoft® Hyper-V™ Server 2008 R2 – You can use this to Boot to VHD and install SharePoint 2010
• MS SDPS Partners have a SharePoint 2010 VHD and optional content packs that make it easy to focus on the right demos
• SharePoint 2010 Public Beta bits

Understanding the Debate

A lot of frustration was expressed at Microsoft’s virtualization desktop strategy in how it appears to be lacking.  Most of the frustration is specifically pointed at both Virtual PC and Virtual Server not supporting x64 or any 64bit guest OS for that matter.  Microsoft’s current released x64 virtualization strategy has put all the eggs in the Hyper V basket without support for desktop OS’s like Windows 7.  We don’t like running Windows Server on our laptops because there is NO hibernate or sleep.  Very inconvenient for meetings and power consumption if you simply close the lid.  Windows Server 2008 really wasn’t designed for laptops.

Eli Robillard, SharePoint MVP in Toronto explains this great debate in his post How to build a SharePoint 2010 dev environment, “Windows 2008 R2 with Hyper-V is a good choice for virtualization on desktop or server installs, but is not supported by Microsoft for use on laptops. Hyper-V was really never intended for use on laptops, and so conveniences like Sleep and Hibernation aren’t there. Other notable things not usable on Windows 2008 R2 are Bluetooth, Zune software and Call of Duty, and there are others. I really like Windows 7 but I don't want to do development on my daily-use OS, so third-party virtualization like VirtualBox or VMWare are the clear winners for me, both of which support a 64-bit client OS. That said, many of the SharePoint MVPs who presented at SharePoint Conference 2009 (#spc09) use a configuration that can dual-boot into either Windows Server for development and presentations, or into Windows 7 for personal use.”

There are so many options now, and it’s confusing to know which to use.  Is there a right answer?  Not sure yet, let’s look at this.  You got your new laptop or new desktop hardware and want to way out the options.  Make sure you’re aware of common issues: 10 Tips Troubleshooting Installations for SharePoint 2010 and SharePoint Foundation.  Becky has a good list from her experience as well SharePoint 2010 Knock Out edition What You Need to Know!.   Including known issues with beta 2 SharePoint 2010 from the SharePoint team blog and for Known Issues Download List for FAST. I wanted to simply get this out there and let you know what my experience has been.  Experience is definitely all over the map based on the conversation on twitter.  To understand SharePoint 2010 Virtualization in a production environment you should view the recent presentation on SharePoint 2010 Virtualization Farm Architecture by Michael Noel, MVP.

The Laptop Options for Running SharePoint 2010

Assumptions:

1. SharePoint 2010 2) 64 bit 3) Need for portability/laptop

1. Win 7 with SP bare metal – Code Project: Running SharePoint 2010 on Windows 7 x64 ; Upside: Very accessible and quick to get in and out of.  Downside it’s always running in the background eating up RAM.  Other desktop operations will be slower as a result, UNLESS you shut down the services <updated 2/4/10> which is explained in this post by Emmanuel: Stop and Go with SharePoint on your workstation. (Note the .zip attachment in the post) Thanks for the tip @harbars.  As well check out Spence’s Tips and Tricks for running SharePoint 2010 on Win 7. 
2. W2K8 with SP bare metal - MOSS How to: Installing SharePoint 2010 Beta on Windows 2008 : Upside You’re running server! Great for development environment Downside: Not good for a desktop environment. Many desktop apps aren’t written for server, while they may or may not work.  Some drivers have issues as well.  It’s a you figure it out what works and doesn’t. Better have a server license or have a TechNet/MSDN subscription. 
3. Dual Boot Win 7 and W2K8 – Upside: Your desktop environment is clean. Reboot to easily get into your SharePoint or Desktop.  Downside: You have to reboot every time you want to get into your SharePoint environment.  Not a good option for a developer.  Ok for demos.
4. Win 7 Boot to SP on W2K8 R2 VHD - Sharepoint 2010 Development environment – Windows 7 boot VHD ; Upside Dual boot and easy to rollback and reconfigure if you want to update the image.  It’s a VHD.  Very cool. Downside: You have to reboot every time you want to get into your image and go back to do your desktop apps.  Ok for demos, but rough on a developer. (* Update: In the comments Todd argues that boot to VHD isn’t virtualization.  I understand his point, even though the V in VHD stands for virtual)
5. Win2K8 R2 Boot to SP VHD - Pete Rodriguez's Blog : Running SharePoint on a native boot VHD – Upside: Dual boot and easy to rollback and reconfigure if you want to update the image.  It’s a VHD.  Very cool. Downside: You have to reboot every time you want to get into your image and go back to do your desktop apps.  Ok for demos, but rough on a developer. (* See point for for more details.)
6. W2K8 with HyperV SP VHD – CJG: SharePoint 2010 - Step by Step Install (HyperV with Full SQL) Upside: Most likely to mimic what you’ll do in production and image should be compatible to copy from test environment.  You can shut down the image when you’re not using it.  As well if you were to do this with Windows Server 2008 Core, it makes sense from a security perspective and sounds very clean.  Easily swap out the images.  Downside: You’re always running 2 OS’s to do anything.  Takes a lot of RAM.  Both Host and Guest must be 64 bit.  With W2K8 as your desktop there are definitely downsides to what won’t work including lack of hibernation.  Hyper V is a lot of management for a simple image.
7. Win 7 with VMware Workstation or ESX or Fusion, etc.. with SP - Faizal: Step by Step SharePoint 2010 Installation Guide (Standalone on VMware Workstation) Upside: Great management UI that’s easy to use and has support behind the solution. Well understood by the industry. Supports 32 or 64 bit host and 32 and 64 bit host. Current virtualization Leader. Downside: It’s not bare metal so you’re running both your client and the server requiring more memory. Microsoft would prefer you not talk about this one as the best one, but based on my experience, it is extremely common.  Cost - It’s the paid solution and a competitive one at that.  VMWare Workstation is $189 (go to VMWare for the real details or to get a 30 day trial), but many IT departments already have licensing for it.
8. Win 7 with VirtualBox SP – Eric Harlan: Setting up your Virtual Machine for SharePoint 2010 (VirtualBox) Upside: Free personal use virtualization, turn it on when you need it, shut it down when you don’t. I think the major battles between Sun and MS are pretty much over as any recent news is about virtualization and partnering, so I don’t think this offends too many people.  It is also very slim and very simple to setup and configure.  It also works with Hyper V images, a huge bonus.  Supports 32 or 64 bit host and 32 and 64 bit host.  (Quick Hint: Make sure you choose Windows Server 2003 x64 if you create or add through the interface.) It’s an easy download from Virtualbox.org. Very handy and feels light weight.  Downside: It’s not fully an MS Solution, it’s not your desktop, and it’s Sun.  Does politics stop you? I saw an image for oracle on the homepage of virtualbox.org oooooh Sometimes.

Common reference on TechNet: Setting Up the Development Environment for SharePoint Server

What I’ve done…

I’ve setup a 64bit Win7 machine and failed silently I have to assume due to the 2GB RAM that was on it.  I’ve successfully used HyperV to manage a number of 2010 images including some I’ve built on a tower at home. :) I’ve briefly used VMware (during the Tech Preview of 7).  I currently am using VirtualBox and will be using it next week at SPTechCon.  I’ve setup that laptop with boot to VHD, but need to first upgrade that image with R2, so it will work.   Loving my new Dell Latitude 14in laptop with backlit screen 8GB RAM with all the bells and whistles (minus the solid state drive I need or want… need!).  Thanks Todd and Eric for that discussion in Sweden.  I’ll be sure to blog about the boot to VHD experience, I’ve already captured a lot of lessons and screenshots.  It could end up being the most simple solution in the long run, but not a long term solution either.

Conclusion.  The debate continues.

This poll that speaks 1000 words…

What virtualization technology are you using for evaluating SharePoint 2010 Beta2?

The count which should be added is 4 for Boot to VHD and I think that would be higher if formalized as an answer.  This is a snapshot and expect this to get more votes by Mar 31 when the poll ends.

Commentary: In the running neck in Neck is VMWare in the lead (especially if you combine VMWare solns) and MS HyperV with VirtualBox not far behind…

Be sure to add your vote to the poll! (Thanks @Chakkaradeep) Let me know if you think this debate is much simpler than I think!  Feel free to add your thoughts and comments and help us get to a happy place.

I think we’d all be happy to see Microsoft Virtualization team come up with a laptop/desktop virtualization strategy for Windows 7 to support x64 especially if it could support 64 bit guest OS on a 32 or 64 bit host.  (I know they are listening! :))