Как установить sharepoint на windows 7

The problem:  Having to install SharePoint on a server OS has been a consistent cause of complaint for years within the SharePoint community, especially for developers.  The proliferation of virtualization technologies (such as the free Virtual PC and VMWare Server for client OS’s, and Virtual Server and Hyper-V for server OS’s) have helped to soothe the pain – but didn’t make it all better for many.  The picture has gotten more complicated with SharePoint 2010.  Now 64-bit hardware and operating systems are required, which significantly narrows the options for desktop lab environments.  Hyper-V is the only Microsoft virtualization technology capable of running 64-bit guest machines, but it only runs on a Windows 2008 Server host machine.  Even if your laptop or desktop is 64-bit, most of us probably aren’t running a server OS on it.  I did try using Windows 2008 Server as my laptop OS for a couple of months, but the performance load of Hyper-V and the SharePoint guest resource requirements caused a significantly slower environment than I was prepared to accept for my everyday use.  I know there are possibilities for running 64-bit guest machines on a client host OS via VMWare, but I wanted to see if it was practical to use Microsoft software because of my familiarity level with it. 

Two solutions:  However, there are some new developments in SharePoint 2010 and Windows 7 that open some new doors to the desktop / laptop dev environment.  TechNet now documents that 1) SharePoint 2010 offers an option for installing on a client OS – at least for development use, and 2) that a pre-installed and configured vhd can be mounted as a secondary bootable drive on a Windows 7 PC.

In this post, I will document my experience installing SharePoint 2010 directly on my Windows 7, x64, 4gb RAM laptop while I’m home fighting the flu this week.  In another post, I will look at mounting a pre-installed Win2k8 server vhd as a bootable drive.

Installing SharePoint 2010 on a client OS – The nitty gritty

This is the simplest solution for creating a desktop lab environment for SharePoint 2010.  There is no longer a need for a virtualization product, which means fewer resources are needed with no guest OS to provide for.  Bamboo Solutions created a helpful utility for installing WSS 3.0 and MOSS2007 on Windows XP / Vista – so this is not a new idea.  However, this tool doesn’t work on SharePoint 2010.  Fortunately, there is a native (although not obvious) way to accomplish this in the 2010 product line that is documented in the first link above.  It basically boils down to editing a config file and manually installing the pre-reqs.  Here’s the procedure I followed.

****  UPDATED:  This is now confirmed to work for both MSS 2010 and SharePoint Foundation (the replacement for WSS) in the public beta released to MSDN on 11/16/2009.  However, step 4 below is now a necessary addition to the process.****

1. Extract all files from the SharePoint.exe installer file from which you intend to install SharePoint (for any other SharePoint 2010, the replacement for WSS, the filename will likely be OfficeServer.exe instead of SharePoint.exe).  This is done with the /extract:directoryname switch, as shown below.  This may prompt you with one of the wonderful UAC ‘are you sure’ boxes.  If so, just click Yes and move on.
    
   

   Картинка с сайта: www.premierpointsolutions.com

2. The result will be a folder with the entire set of installation files for SharePoint 2010.  Go to ExtractedDirectoryNameFilesSetup, and open the Config.xml file using Notepad.
   

   Картинка с сайта: www.premierpointsolutions.com

    

3. Insert a new line in the <Configuration> section, as shown below:
   <Setting ID=”AllowWindowsClientInstall” Value=”True” />
   

   Картинка с сайта: www.premierpointsolutions.com

    

4. While you have the file open, change to the key in the PIDKEY Value entry from the ‘Please enter key…’ text to your actual MSS 2010 license key.
   (If you don’t do this, you will likely get an error message in step 12 below that says your ‘config.xml is not valid, run setup again without using a setup configuration file, or fix the configuration file’.)
   

   Картинка с сайта: www.premierpointsolutions.com

5. Close and save the file.
6. Now we must install the prerequisites manually.  (The fancy new pre-req installer doesn’t work on a client OS.) 
   First, run all of the installer files found in the subfolders under the ExtractedDirectoryNamePrerequisiteInstallerFiles directory with the exception of the Speech and SpeechLPK folders (ChartControl (for Office Servers only), FilterPack, sqlncli, sync):
    
   

   Картинка с сайта: www.premierpointsolutions.com

7. Download and install the Microsoft Geneva Framework Runtime for x64.
   (This is a tricky one.  Most of the downloads you find with Google are not the correct version for the public Beta, and the one you may have used with the SharePoint 2010 Technical Preview doesn’t work either.  If you don’t have the correct version, you won’t be able to complete the SharePoint 2010 Products Configuration Wizard in step 13 below.  The download available at the link above worked for me with the public Beta.  The key is to have the following DLL version in your c:WindowsAssembly folder:  Microsoft.IdentityModel 1.0.0.0) 
   

   Картинка с сайта: www.premierpointsolutions.com

8. Download and install the ADO.NET Data Services v1.5 (runtime only), or whatever is the most current version when you’re reading this.
9. Download and install the SQL Server Analysis Services – ADOMD.Net, or whatever is the most current version when you’re reading this.
10. Install the IIS pre-reqs by entering (or, lets be honest – copying and pasting) the following command without any line breaks:

    start /w pkgmgr /iu:IIS-WebServerRole;IIS-WebServer;IIS-CommonHttpFeatures;
    IIS-StaticContent;IIS-DefaultDocument;IIS-DirectoryBrowsing;IIS-HttpErrors;
    IIS-ApplicationDevelopment;IIS-ASPNET;IIS-NetFxExtensibility;
    IIS-ISAPIExtensions;IIS-ISAPIFilter;IIS-HealthAndDiagnostics;
    IIS-HttpLogging;IIS-LoggingLibraries;IIS-RequestMonitor;IIS-HttpTracing;IIS-CustomLogging;
    IIS-Security;IIS-BasicAuthentication;IIS-WindowsAuthentication;IIS-DigestAuthentication;
    IIS-RequestFiltering;IIS-Performance;IIS-HttpCompressionStatic;IIS-HttpCompressionDynamic;
    IIS-WebServerManagementTools;IIS-ManagementConsole;IIS-IIS6ManagementCompatibility;
    IIS-Metabase;IIS-WMICompatibility;WAS-WindowsActivationService;WAS-ProcessModel;
    WAS-NetFxEnvironment;WAS-ConfigurationAPI;WCF-HTTP-Activation;
    WCF-NonHTTP-Activation
    
            
    
              Картинка с сайта: www.premierpointsolutions.com
            
          

11. Restart your PC.
12. Run the SharePoint installer file setup.exe in the root of your ExtractedDirectoryName.

    (Microsoft recommends configuring only a ‘Stand-Alone’ SharePoint instance on Windows 7, but it will allow you to choose advanced and Complete in order to specify a SQL Server if you wish.)

13. When the installer finishes and you begin the ‘SharePoint Products and Technologies Configuration Wizard’, a popup will warn you that this use is not supported for production environments.  Click OK and proceed through the wizard.

NOTE:  If you need to install SharePoint in using the ‘Complete’ option to be able to use the full version of SQL Server, you will not be able to use a local user account in the config wizard.  This is possible with the New-SPConfigurationDatabase PowerShell cmdlet, though.  I’ll blog about using that cmdlet in a later post.






Картинка с сайта: www.premierpointsolutions.com

Well, firstly I would like you guys to know that in no way it is an “original” post. I was installing SharePoint Server 2010 in my Windows 7 machine (which is not supported by default by SharePoint )so this all about the whole process … possible errors and their solutions. So you can say its kind of consolidation of different posts which I looked for answers. (And link to those posts are in the end) with my own workaround…

With that said, lets begin our journey of Installing SharePoint Server 2010 in Windows 7 …

As first step, download demo of SharePoint Server 2010 from official Microsoft site. And then run the installer. With surprise you will be greeted with error saying that you need to have Windows Server 2008 (x64)with SP1. Means that as a minimum system rec. you need to have 64bit edition of Windows Server 2008. Which I don’t have… So I did little “Googling” and with no surprise there were lots of people were complaining about this rec. (mostly people like me who just want to try SharePoint ) … and I stumbled across my fav. Site (the Code Project) where someone had posted a solution to this problem.

Go to “C:\Program Files (x86)\MSECache\oserver2010”
Find FILES folder Then Setup folder Edit config.xml file (using Notepad with Admin privileges) … and add …
<Setting Id=»AllowWindowsClientInstall» Value=»True»/>

Re-run the setup from there, and you will find it go through without any further complains …

Once the installation is done, you will need to configure the SharePoint using “SharePoint 2010 Products Configuration Wizard” … so, start the wizard … and soon you will see another error it may be something like,

Failed to Create Configuration Database

An exception of type System.IO.FileNotFoundException was thrown.  Additional exception information: Could not load file or assembly ‘Microsoft.IdentityModel, Version 3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35? or one of its dependencies.  The system cannot find the file specified.

Which suggests that there is something wrong with creation of database, so you might think its because of SQL Server … but no, its because you don’t have installed something called “Windows Identity Foundation” pack a.k.a. WIF … so download / install it from MSFT Site and you are all set … re-run the configuration wizard. Then, I was met with another error which was again failed to create configuration database, but because of different object …

Картинка с сайта: gaurangpatel.net

Failed to Create Configuration Database

An exception oftype Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: Failed to call GetTypes on assembly Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Could not load file or assembly ‘System.Web.DataVisualition, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find thefile specified.

And again with little Googleing, I found that its because something called “Chart Control” is not installed !! So, I downloaded it from MSFT site again. And then again I tried to run the configuration wizard … and guess what ?? it just went all the wayyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy … 

So, once done .. I fired  “SharePoint 2010 Central Administration”  .. in essence its centralized page for SharePoint administration, but man I met again another problem … my admin page was nothing but blank !!! So, again I went back to Google to ask question, and I found that … I need to enable Windows Authentication and disable Anonymous Access in my IIS (yes, you need IIS for SharePoint Server) … once it is done … everything was in place … and my own SharePoint Server 2010 is all up and running !!!

Картинка с сайта: gaurangpatel.net

And as I mentioned earlier, this post is almost consolidation of all stuffs I found over internet. And the links are as follows,

The Code Project Page go bypass Windows 2008 limitation

Dealing with Errors at Configuration Stage of SharePoint Server

Dealing with Blank Screen in place of  SharePoint Server Administration Page

Its Just a Thought …

This content is 16 years old. I don’t routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Windows SharePoint Services (WSS) is not supported on a client operating system, but that’s not to say it shouldn’t run – right? After all, Windows client releases include a web server and can run a database service – that should pretty much cover the basics (back in the days of Windows NT it was generally reckoned that the differences between the Workstation and Server releases were just a few registry entries – but even if that was true then, there are a few more differences today)! In response to this, the guys at Bamboo Nation came up with an installer for SharePoint on Vista and, even though it’s been around for a while (thanks to Garry Martin for alerting me to this), last week I finally got around to trying it out on Windows 7.

It seems to work well but, having never installed SQL Server 2008 Express Edition (WSS needs access to a SQL database) I needed to combine two very good resources (the Jonas Nilsson’s installation guide for Windows SharePoint Services 3.0 SP1 on Windows Vista and Symantec’s article on installing and configuring SQL Server 2008 Express) – the result is my installation notes (repeated in full here in case either of those articles ever disappears but for screen shots, refer to the originals – or to Jim Parshall’s video tutorial):

1. Gather together all the resources that will be required. Assuming that Windows is already running, the remaining components are:
   • SQL Server Express Edition.
   • Bamboo Nation’s WSSonVista Setup Helper.
   • Windows SharePoint Services (I used WSS 3.0 SP1 32-bit – a x64 version is also available).
2. Install and configure SQL Server 2008 Express Edition:
   • SQL Express may be downloaded with or without tools – I went for the “without” option but the tools may be useful for troubleshooting purposes. If you’re installing on an older platform, there are some pre-requisites (.NET Framework 3.5 SP1, Windows Installer 4.5 and Windows PowerShell 1.0) but my Windows 7 client already had these (or later versions).
   • Run the SQL Server Express installer and follow the wizard. It’s fairly straightforward but there are a couple of things to watch out for:
     • For the instance configuration, specify MSSQLSERVER as both the named instance and the instance ID.
     • For the server configuration, use NT AUTHORITY\SYSTEM (no password) as the SQL Server database engine account name and set the SQL Server Browser startup type to Automatic.
     • For database engine configuration, either Windows or mixed mode authentication may be used (I stuck with the defaults) but the installer will not continue until users or groups are specified for unrestricted access to the SQL server. SQL DBAs and security guys will probably have lots of best practice advice here for use with production servers but I took the view that it’s probably nothing too much to worry about on a developer workstation and simply gave the necessary rights to the account I was running as.
3. Install and configure Internet Information Services in Control Panel, Programs and Features by clicking the option to turn Windows features on or off and enabling:
   • Internet Information Services
     • Web Management Services
       • IIS 6 Management Compatibility
         • IIS 6 Management Console
         • IIS 6 Scripting Tools
         • IIS 6 WMI Campatability
         • IIS 6 Metabase and IIS 6 configuration capability
       • IIS Management Console
     • World Wide Web Services
       • Application Development Features
         • .NET Extensibility
         • ASP.NET
         • ISAPI Extensions
         • ISAPI Filters
       • Common HTTP Features
         • Default Document
         • Directory Browsing
         • HTTP Errors
         • HTTP Redirection
         • Static Content
       • Health and Diagnostics
         • HTTP Logging
         • Request Monitor
       • Performance Features
         • HTTP Compression Dynamic
         • Static Content Compression
       • Security
         • Basic Authentication
         • Request Filtering
         • Windows Authentication
4. Install the WSS on Vista setup helper application by running wssvista.msi.
5. Install WSS by:
   • Locating the WSS on Vista helper application files in %programfiles%\WSSonVista\Setup and running setuplauncher.exe.
   • Pointing the setuphelper to the WSS installer (sharepoint.exe)
   • Following the WSS installation wizard, selecting an advanced installation for a web front-end server, creating a new server farm, and supplying the details for the local SQL database (including the account details).
6. At the end of the WSS installation, take a note of the port number used, and then navigate to http://localhost:portnumber/. If all goes well, then you should see the SharePoint Central Administration site in your browser:
   

   Картинка с сайта: www.markwilson.co.uk

Finally, a couple of additional notes:

• I ran all of this as a standard user, answering just a few UAC prompts at the appropriate points to elevate my privileges).
• These instructions will allow access to SharePoint site from the local machine; however it will be necessary to create some firewall exceptions if remote client access is required.