SharePoint24x7 It's all about SharePoint.


Article – Setting up a SharePoint 2010 environment for try-outs or development – Part II – Windows Server or Windows 7?

Posted by Joy

In the previous article we discussed the different deployment options we do have with SharePoint 2010. The best part is all of those options give us again to select either server operating system or a client operating system as the underlying operating system to deploy SharePoint 2010.

WSS 3.0 or MOSS 2007 didn’t support client operating systems such as Windows XP or Windows Vista. Lot of developers dropped the idea of testing the product right after they hear that we need a server operating system to install SharePoint. SharePoint 2010 supports installing in both Windows Vista with Service Pack 2 and Windows 7. This is a huge step in the SharePoint history and we can easily get started without having to format or install existing systems. Isn’t it awesome?

The best part is its not limited to SharePoint Foundation 2010 which is free and equivalent to WSS 3.0 and it also supports installing SharePoint Server 2010 Standard and Enterprise as well.

However, I have seen that capabilities of SharePoint 2010 get limited/ trimmed when you install on a client operating system and I recommend to always go for Windows Server 2008 instead of a client operating system. Following are few points which you may consider before choosing a client operating system such as Windows Vista or Windows 7. Going forward I may refer as client operating systems and it refers to both Windows Visa and Widows 7 and remember SharePoint 2010 doesn’t support Windows XP at all.

  • Client operating systems support only Stand-alone mode of the installation. Which means you will not be able to setup a Farm. Whatever the features available for farm installation will not be available when you go for stand-alone.
  • Client operating systems doesn’t support using a full-blown version of SQL Server. It uses SQL Server Express edition as the database and it has a 4 GB database limit which will exceed very soon. Even if you install SharePoint Server, it still uses SQL Server Express.
  • Everything will be configures using a system account or network service account.
  • Definitely there is a feature drop. This is something you should keep highlighted while selecting a client operating system.
  • Some nice add-on products such as Office Web Applications, PowerPivot, etc… will not be able to install on client operating systems just because they need Active Directory integrated installation of SharePoint.
  • More interesting point is, Windows Vista and Windows 7 requires lot of resources compared to Windows Server 2008 R2 and you may want to consider this if you have very limited hardware resources.

Above list is not even close to the complete list of the differences between installing SharePoint 2010 on a client operating system and a server operating system. But this list is more than enough for you to easily go for Windows Server instead of client operating systems.

Let’s enjoy unlimited, zero restricted set of features of SharePoint 2010 with Windows Server family.


Article – Setting up a SharePoint 2010 environment for try-outs or development – Part I – Introduction

Posted by Joy

We didn’t have much trouble installing MOSS 2007 since we didn’t have many options at that time. It supported only Windows Server 2003 or 2008 and it was not supported by client operating systems such as Windows XP or Windows Vista. So we ended up following same set of instructions which demonstrated of installing MOSS 2007 on Windows Server 2003 or 2008.

I know you guys will say, “No we did install WSS 3.0 on Windows XP ad Windows Vista using Bamboo Solutions”, but don’t forget it was an unsupported installation as per Microsoft. Above all, it didn’t support installing MOSS 2007 and only supported WSS 3.0.

And how did you try MOSS or WSS? Did you go about installing everything into your local machine? What if your environment gets dirty when you try all the features and customization? I guess you had to re-install right? The other option would have been using a virtualization technology such as VMware, Virtual PC or Hyper-V. The moment we talk about virtualized environments we also talk about having to have high configuration PCs with at least 4 GB RAM. But the trade-off between PC configurations versus portability was acceptable. Because you get an ability to switch between different environments when you have a virtualized environment.

Now we are in year 2010 with the latest release of SharePoint which is SharePoint Foundation 2010 (FREE) and SharePoint Server 2010. After collecting feedback from the previous release, Microsoft now provides handful different options for us to setup a SharePoint 2010 environment. They are:

  1. Base machine installation (AKA On-the-metal installation)
  2. Bootable VHD
  3. Virtualization

Base machine (on-the-metal) installation

In this option you will be installing everything in your base machine and we require following hardware configurations:

Hardware/ Software:

  • Intel Core 2 Duo Processor with 64-bit support
  • Minimum 4 GB RAM
  • Minimum 80 GB Hard Disk space

An advantage of this approach is that you can start it with standard hardware and you will be able to consume all the resources to your SharePoint farm.

Disadvantage of this approach is that if anything bad happens to your SharePoint farm, you need to re-install everything starting from the operating system.

Personally, I don’t recommend going for this option.

Bootable VHD

This is a new feature provided only by Widows Server 2008 R2 and Windows 7 operating systems. With this feature you can have any of the above operating system as your primary operating system and any no of bootable .VHDs running from above mentioned operating systems based on your disk space available.

Advantages of this approach are, though it looks like dual-boot but it is not and it is booting an operating system from a single .vhd file. In that case, you can easily back up your .vhd file and copy whenever you need to switch back to a different environment. For  instance you can have one .vhd with SharePoint Foundation 2010 installed and one more with SharePoint Server 2010 Standard and one more with SharePoint Server 2010 Enterprise and one more with SharePoint Server 2010 Enterprise with PowerPivot so on. Other advantage is that you can use all the resources of your base machine when you load from bootable VHD. In this way you can get started easily with the same hardware I recommended for base machine (on-the-metal) installation also you have a nice fail-safe environment for your SharePoint 2010 farm.

Disadvantage I see here is usually bootable VHD performs 3% lesser compared to actual dual boot even with the same hardware configuration.

Personally this is my favorite and I’m ok not to consider 3% performance drop compared to great deal of portability, fail-safe features offered by this option.


Virtualization can be achieved by using either VMware or Hyper-V. Hyper-V comes free as an add-on to Windows Server 2008 R2 and for VMware you need to pay additionally for licensing. Hyper-V comes only with the Windows Server and will not be available with any of the client operating systems. But VMware can be installed to any of the operating systems.

Advantage of using virtualization is that you can use it for production as well. Also it helps you to maintain different environments running at the same time depending on the memory capacity of your system. Also both the virtualization products provide the concept of snapshots so that we can maintain different versions of the same virtual environment. Also it can be exported and imported into different systems without any issues and you don’t have this facility in the above mentioned approaches.

Disadvantages I see in this approach are that if you go for VMware you need to pay additionally. But VMware can be loaded on any operating system which means we can have SharePoint 2010 running on any operating system. In case of Hyper-V you don’t have to pay additionally other than the Windows Server license but it forces you to use Windows Server and most of the developers don’t like it because of its look and feel. But you can follow this link and it guides you how you can configure Windows Server to look and act like Windows 7. Also this approach requires lot of hardware resources depending on the no of virtual machines you are planning to run simultaneously. If it’s just 01, you need minimum 6 GB RAM and enough free disk space no matter whether it’s VMware or Hyper-V.

Personally, I hate Hyper-V just because it depends heavily on hardware and I had a situation I had to install Windows Server 2008 R2 Service Pack 1 beta to get my blue screen issues resolved. I like VMware but you need to have a license for that and we MVPs get one free.


Conclusion to this 1st part of the article is that in this release of SharePoint we have 03 options to choose from when we want to setup a test or development environment. Which is better over the other is all depend on the features you look at and how much you can pay for hardware resources.