Not later than 2 weeks back I’ve been invited to perform some reviewing on an upcoming book for Packt publishing related to integrating Silverlight 4 and SharePoint 2010. Some months back using tips on the web i prepared my W7 x64 as development machine benefiting from VHD boot under Windows 7 to avoid messing up my physical installation with all the betas and RCs circulating around.
I do have that already couple of differential VHDs on my development machine, containing various configurations. Nowadays, after releasing Visual Studio 2010 RC1 it is hard to find any version of Visual Studio 2010 Beta 2, but i did kept close a copy of a DVD i received back at the Tech Days in Paris. The reason I need to use Visual Studio 2010 Beta 2 instead of RC1 is because support for Silverlight 4 is not included! Very important for my current situation!
Now, capitalizing on that experience, along with the fact that i also received a RC1 version of the SharePoint 2010 i set for creating a new differential VHD from my baseline create previously.
Microsoft has made a good job describing finally on TechNet the requirements, you only have to go and grab them on TechNet site. Obviously launching install still throws the same exception about failing package. Now the trick is that in Program Files (x86) one folder will be created where the installation files are extracted
So, before installing, make sure you:
1. Go under Files/Setup/ and add this line in config.xml <Setting Id="AllowWindowsClientInstall" Value="True"/>. When saving, Windows 7 will most probably request that you save it somewhere else, e.g under My Documents folder, unless you are Administrator. Just make sure overwrite the original file with the version containing your changes. Here is how my configuration file looks like.
2. Install pre-requisites, one by one:
- Microsoft "Geneva" Framework (http://go.microsoft.com/fwlink/?LinkID=165752)
- Microsoft Sync Framework v1.0 (http://go.microsoft.com/fwlink/?LinkID=141237&clcid=0x409)
- Microsoft Filter Pack 2.0 (http://go.microsoft.com/fwlink/?LinkId=166504 or C:\Program Files (x86)\MSECache\oserver2010\PrerequisiteInstallerFiles\FilterPack)
- Microsoft Chart Controls for Microsoft .NET Framework 3.5 (http://go.microsoft.com/fwlink/?LinkID=141512)
- Microsoft SQL Server 2008 (i use Express Edition always on my development machine). In this particular case, where i needed to deal with .NET 4.0, i choose to install already the version that has support for .NET 4.0 Beta 2 (use SHAREPOINT as the name of the instance, because otherwise SharePoint 2010 will ignore it and create a new instance during setup). You can find it here SQLEXPR x64 Executable with .Net 4 Support. This will get you 2 benefits: speed up installation of SP2010 (especially that when choosing “Standalone” install it will require and install SQL 2008 Express – you will see later why i choose standalone) and avoid you to install many cumulative package updates which are really a pain. Also very important is that under Windows 7 do add the “Administrators group” already during installing to the SQL Administrators group. Also make sure that the account used for Installing and Configuring is already in the Administrators group of the local machine.
- Obviously you don’t need PowerShell 2.0 CTP3 as Windows 7 already comes with it. Don’t try to download and install the latest release of Windows Management Framework (that contains both PowerShell 2.0, BITS and WINRM), neither of the available packages are good for Windows 7 and will NOT work and believe me SHarePoint 2010 RC1 will function just perfect without it.
You’re done, now you can start installation of SharePoint 2010 RC1 X64 (or build 14.0.4730.1010). Navigate under the same folder under Program Files (x86)/MSECache/oserver2010 and run setup.exe. Next screen shall ask for you key (i assume you have that somewhere handy).
Go on, type it in or copy it, and after validation you shall be presented with the regular screen, you must be probably familiar with from SharePoint 2007. Now this a non-turning point because depending on what you’ve selected you’ll end-up with one useless installation or….not.
The trick here is that if you choose “”Server Farm” instead of “Standalone”, you will get a warning (see bellow) and then, after all setup is finalized and Configuration Wizard starts, UNLESS you are connected to a Active Directory Domain and use a domain account (but rather a Local account – i always create various local accounts, to use best-practices, such as SPService, SPSearch, SPCrawl, etc.), you will end-up with the next error, forbidding you to continue. That’s really ugly, as you either uninstall, and choose the “Standalone” option next time, which of course, only works with MS SQL Express that gets installed behind the scenes for you during setup (and now you see why is good to install it by yourself any way you want it) or add your machine to a Windows Domain so you could use a Domain account.
Now, once this is passed, the rest should be fine. One more tip, try running setup using the Administrator account (or at least during Configuration wizard)! I had a couple of times unexpected failures of the wizard which I could only overcome by running as Administrator.
Provided that everything went fine with the installation, you shall see the Configuration Wizard screen after installation!
However, as soon as it start (while executing initializing Task 2 charged with Creating configuration database, among others) you’ll receive un ugly exception!
Looking in the log file somewhere an exception is logged about an assembly that an assembly is missing called “Microsoft.IdentityModel, Version=18.104.22.168, Culture=neutral, PublicKeyToken=31bf3856ad364e35”.
After some research on this assembly, I was already suspecting that the Geneva framework has something to do with it., i found that this assembly is has something to do with Claims in the Windows Identity Foundation. This got me thinking that Microsoft released not long ago the Microsoft Windows Identity Foundation, already part of the Windows 2008 R2! So, I proceed in downloading and installing this package from Microsoft’s Download Center. Make sure you choose Windows6.1-KB974405-x64.msu. Installation is quick and smooth, and after a new attempt, what do you know, it works like a charm (even if it takes its time).
So here it is, now you have a brand new fresh installation of SharePoint 2010 RC1 on your Windows 7, just like mine. Next time i shall write about integrating Silverlight 4 RIA Services with SharePoint 2010 to “light-up your SharePoint” as some articles keep claiming.
Until next time, happy SharePointing’,