3 configuration changes needed to enable anonymous access for a public-facing MOSS site

1. IIS - Grant Read rights to the Internet Guest Account (that is used in inetmgr anonymous access settings) for the site’s physical folder under inetpub

2. Central Admin – Navigate to Application Management -> Authentication Providers. Edit the “Default” zone and select “Enable Anonymous Access”

3. Site Collection – Navigate to Site Actions -> Site Settings -> Advanced Permissions. Navigate to Settings -> Anonymous Access. Select “Entire Web site”.

How to create a new scope in SharePoint?

In order to create and activate new scope, you have to do next steps:

First step:

You have to create "Metadata property mappings"

Go to SSP, Click on the "Search Settings";

Click "Metadata property mappings";

Click "New Managed Property";

Give "Property Name", type;

Also in our example you need to "Add Mapping"

Click "Add Mapping", Choose category "People" and select a crawled property "People:FirstName(Text)";

And Check "Allow this property to be used in scopes"

Second Step:

Next Go to SSP, Click on the "Search Settings"

Go to the Scopes area and Click "View scopes"

Click "New Scope"

Specified "Title" and click "OK"

Then Click on the Scope that you just created and choose "Edit Properties"

Now you need to specify "Rule". Click "Empty - Add rules"

In our example we using "Property Query"

Now you have to update, Click "Start Update Now"

Choose from "Property Query" area Managed Property that you created in First Step = FirstName (For Example: Eugene)

Third Step:

Go to you site collections:

Click SiteActions -> Site Settings -> Modify All Site Settings

Then Click "Search Scopes" in Site Collection Administration area.

Click "Search Dropdown" and check your scope.

Click OK

and in order to see changes in dropdown list you need to do iisreset.

Ctrl+R and type iisreset

Done

Search Architecture Terminology

Index Engine - processes the chunks of text and properties filtered from content sources, storing them in the content index and property store.

Query Engine - executes keyword and SQL syntax queries against the content index and search configuration data. 

Content Index - stores information about words and their location in a content item.

Property Store - stores a table of properties and associated values. 

Search Configuration Database - stores information used by the Search service, including crawl configuration, property schema, scopes, and so on. 

Wordbreakers - used by the query and index engines to break compound words and phrases into individual words or tokens.

Sharepoint - SQL Server

SQL Server provides unified storage by storing all user and config data with exception of search indices and site definitions (XML files) 

• Configuration Database – info about web farm configuration
  
• Content Database (Site) –sites, lists, list items, and documents
  
• Profile Database – user profiles and audience targeting
  
• Services database – search configuration info
  
• Single Sign On (SSO) – credentials to access other line of business apps 
  

Some tables from one application in your database:

dbo.Sites - Stored Site Collection

dbo.Webs - Stored Each Individual Site in the Site Collection

dbo.Lists - All the lists within all sites collection

dbo.AllUserData - Stored list's items

dbo.AllDocs - Stored documents and information about

Sharepoint Server Glossary

1. Application page is an a template page from _layouts virtual directory with following characteristics:

• it is available within every site
  
• only one copy of this page on the server
  
• It is not accessible through Designer when editing a site
  
• It is accessible through IIS
  

2. Safe page is a template page that comes from site definitions (For example: default.aspx in “Team Site” template).

• it exists only on sites where it’s been specified by a template or created by a user
• many copies can exist on the server
  
• It is accessible through Designer when editing a site
  
• It is not accessible through IIS
  

SharePoint Web Application is an IIS website that has a SharePoint Web Application Service running

Basic Web Application – such as default web site or external site (extranet.company.com), stores site collections where end-users and site administrators work

Central Administration – used by system administrators to manage the server farm

Shared Services –  manages features that are common to all web applications such as search, user profiles, business data catalog

Personal Sites – contains personal user site collection (one per user)

Sharepoint Designer - Contributor Settings

Let’s take a look at the next scenario. You need to create new group for users which will have the full control in the browser. But will limited for using specific folders, creating files with specific extensions etc. in SharePoint Designer.

In this case we need to use Contributor Settings (Contributor Mode)

First Step.

Create New Permissions Level (Site Settings > Permissions > Permission Levels)

Click "Add a Permission Level"

Second Step.

Create Group using Permission Level that you created in previous step (Site Settings > Permissions)

Click "New Group"

Third Step.

Open SharePoint Designer.

Go to "Site" menu > "Contributor Settings"

Setup "Site Manager" as default and delete others Groups.

Then Click "Add" new group

Give the name and choose site permissions level that you created in the first step. After that switching menu on the right chooses the settings that you need.

Click Ok

How to Back Up and Restore IIS

Back Up the IIS Configuration

To back up your IIS configuration, follow these steps:

1. In the IIS snap-in on the local computer, click the Computer icon under Internet Information Services.
2. Click Action and select Backup/Restore Configuration.
3. Click Create backup, choose a name for your backup file, and then click OK. NOTE: The default location of the backup is the %SystemRoot%\system32\inetsrv\MetaBack folder. If you want to save your backup file to another location, you can copy the file from this default location to another location. Keep a copy in the default location to allow for an easy restoration.
4. Click Close. NOTE: This backup method provides a way to restore only your IIS settings, not your content files. This backup method does not work if you reinstall your operating system. Backup files cannot be used to restore an IIS configuration on other computers that are running Windows 2000.

Restoring the IIS Configuration Without an IIS Reinstallation

To restore your IIS configuration if you have not removed and reinstalled IIS, follow these steps:

1. In the IIS snap-in on the local computer, click the Computer icon under Internet Information Services.
2. Click Action and select Backup/Restore Configuration.
3. In the Configuration Backup Name dialog box, select a backup file and click Restore. When you are asked if you want to restore your configuration settings, click Yes.

Restoring the IIS Configuration After an IIS Reinstallation

To restore your IIS configuration after you have removed and reinstalled IIS, follow these steps:

1. In the IIS snap-in on the local computer, click the Computer icon under Internet Information Services.
2. Click Action and select Backup/Restore Configuration.
3. In the Configuration Backup Name dialog box, select the backup file that you created and click Restore. Although an error message states that the restoration has failed, a portion of your backed-up configuration is restored.
4. At a command prompt, type the following: cscript.exe X:\InetPub\AdminScripts\Adsutil.vbs enum w3svcwhere X is the letter of the drive on which IIS is installed. From the listed settings, locate the WamUserName and the associated WAMUserPass value.NOTE: To use the Adsutil.vbs utility, you must have Windows Script Host installed.
5. Click Start, point to Settings, click Control Panel, double-click Administrative Tools, and then double-click Computer Management. Click Local User Managers and click Users.
6. Double-click the IWAM_computername user account. Type the WAMUserPass value that you retrieved from the previous step and click OK.
7. In the Configuration Backup Name dialog box, select the backup file that you created and click Restore. This fully restores your configuration.NOTE: If you change the identity of your out-of-process applications, those applications revert back to the previous IWAM user name.
   

Mostly used short cuts and file locations working with Sharepoint

Run commands

mstsc - Remote Desctop Connection
inetmgr - IIS Manager (Internet Information Services Manager);
run - windows key + R
cmd - command prompt
iisreset - Reseting Internet Information Services

Host File - C:\WINDOWS\system32\drivers\etc
GAC (Global Assembly Cache) - C:\Windows\assembly

Applications Locations (by Default) - C:\Inetpub\wwwroot\wss\VirtualDirectories

Copy dll files from the GAC - Open Run Window, and type C:\Windows\assembly\gac\

How to get PublicKeyToken? right-click on the assembly name and open the properties dialog box to view the assembly name and public key.

Direct links to some of pages in sharepoint site

Web Part Gallery Page
http://yourserver/sitecol/_catalogs/wp/Forms/AllItems.aspx

Visual Studio 2005 (useful short cuts)
Code Reformating - Select the code, and click Ctrl+K & Ctrl+F;

How to Deploy Web Parts?

Deployment for Development Purposes*

1. manually copy the web part’s signed assembly (.dll) to the
   Global Assembly Cache (GAC);
2. manually add the corresponding element to
   SharePoint’s Web.config file;
3. use a site collection’s web-part gallery pages to add the
   web part.

Moving to Production (You need to create a solution package to deploy it to your SharePoint farm). For creating solution, we have to use Microsoft add-in called Windows SharePoint Services 3.0 Tools: Visual Studio 2005 Extensions, Version 1.1. Click Here to Download it.

*The preferred method for deploying a web part for an entire SharePoint web application or web farm is through a SharePoint solution.

Adventure Works SQL Server 2005 SP2a sample databases

Here you can find all sample databases:

Visit the SQL Server Samples and Community Projects page on CodePlex at:

http://codeplex.com/SqlServerSamples 

For those people who looking something specific as follow the same link above, you can see the original names of databases below. And also you can see step by step manual how to install and attach database to your SQL server.

 

AdventureWorks - AdventureWorksDB.msi 

AdventureWorksDW - AdventureWorksBI.msi 

Northwind and pubs Sample Databases for SQL Server 2000 Download

(by default after installation completed you can find northwind database, under this location

C:\SQL Server 2000 Sample Databases\. For installation in more detail click here)

 

First Step. Download the file you need. Install (by default it will install it C:\Program Files\Microsoft SQL server\MSSQL.1\MSSQL\Data\nameofdatabase.mdf)

 

Next Step. Open SQL server, right click on Databases (on your left). Select Attach then press add button. Select database that you need and press OK.

 

Feature '75a0fea7-cd50-401e-af0e-782f3662a299' is not installed in this farm, and can not be added to this scope.

When I was trying to create Top-Level site using "Help Desk" template I got next error "Feature '75a0fea7-cd50-401e-af0e-782f3662a299' is not installed in this farm, and can not be added to this scope"

One of the ways to resolve this issue to install Windows SharePoint Services 3.0 Application Template: Application Template Core.

Install:

stsadm -o addsolution -filename path\mySolution.wsp

stsadm -o execadmsvcjobs

stsadm -o deploysolution -name mySolution.wsp -immediate -allowGacDeployment -force

Uninstall:

stsadm -o retractsolution -name mySolution.wsp -immediate

stsadm -o execadmsvcjobs

stsadm -o deletesolution -name mySolution.wsp -override

stsadm -o execadmsvcjobs

Web Template IDs in Sharepoint

STS#0 Team site
STS#1 Blank site
STS#2 Document workspace
MPS#0 Basic meeting workspace
MPS#1 Blank meeting workspace
MPS#2 Decision meeting workspace
MPS#3 Social meeting workspace
MPS#4 Multipage meeting workspace
WIKI#0 Wiki
BLOG#0 Blog

BDR#0 Document center—A central document management location for an enterprise
OFFILE#0 Records center—A central location in which records
OFFILE#1 managers can define routes for incoming files
CMSPUBLISHING#0 Publishing site
BLANKINTERNET#0 Publishing site—A site for publishing web pages on a schedule with workflow features enabled
BLANKINTERNET#1 Press releases site
BLANKINTERNET#2 Publishing site with workflow—A publishing site for web pages using approval workflows
SPSNHOME#0 A site for publishing news and articles
SPSREPORTCENTER#0 Report center—A site for creating, managing, and delivering web pages, dashboards, and Key Performance Indicators (KPIs)
SPSPORTAL#0 A starter hierarchy for an intranet divisional portal
PROFILES#0 A profile site that includes page layouts with zones
BLANKINTERNETCONTAINER#0 Publishing portal—a site collection preconfigured for revision-controlled, secure content creation and publication

BDR#0 Document center—A central document management location for an enterprise
OFFILE#0 Records center—A central location in which records
OFFILE#1 managers can define routes for incoming files
CMSPUBLISHING#0 Publishing site
BLANKINTERNET#0 Publishing site—A site for publishing web pages on a schedule with workflow features enabled
BLANKINTERNET#1 Press releases site
BLANKINTERNET#2 Publishing site with workflow—A publishing site for web pages using approval workflows
SPSNHOME#0 A site for publishing news and articles
SPSREPORTCENTER#0 Report center—A site for creating, managing, and delivering web pages, dashboards, and Key Performance Indicators (KPIs)
SPSPORTAL#0 A starter hierarchy for an intranet divisional portal
PROFILES#0 A profile site that includes page layouts with zones
BLANKINTERNETCONTAINER#0 Publishing portal—a site collection preconfigured for revision-controlled, secure content creation and publication

How to see the actual error in SharePoint

In order to see the actual error you need to make a few modifications of web.config file. Take the web.config file from application\site that gives the error.

Open in Notepad:
First, change customErrors mode in "Off"

Second, change CallStack="true"

Refresh the page with error

FatalError: Could not find Feature S2SiteAdmin.

I was importing one of my site and I got the next message:

Problem:

Progress: Initializing Import.

FatalError: Could not find Feature S2SiteAdmin.

Solution:

You need to install "Infrastructure Update for Microsoft Office Servers (KB951297)"

Brief Description

The Infrastructure Update for Microsoft Office Servers (KB951297) includes the latest performance updates and fixes for the Microsoft Office Servers.

Download

How to create host name top level site with stsadm

For example, if you have a Web application named http://sharepoint.com and you want to add a host-named site collection with the URL http://about.sharepoint.com, use the following command:

stsadm.exe -o createsite -url http://about.sharepoint.com -ownerlogin domain\siteowner -owneremail siteowner@sharepoint.com -hhurl http://sharepoint.com

Renaming Site
stsadm -o renamesite -oldUrl http://www.name.com -newUrl http://www.newname.com

How to install and unistall WSP solution template using stsadm

Install:

stsadm -o addsolution -filename path\mySolution.wsp

stsadm -o execadmsvcjobs

stsadm -o deploysolution -name mySolution.wsp -immediate -allowGacDeployment -force

Uninstall:

stsadm -o retractsolution -name mySolution.wsp -immediate

stsadm -o execadmsvcjobs

stsadm -o deletesolution -name mySolution.wsp -override

stsadm -o execadmsvcjobs

Key classes in the SharePoint object model

Document Libraries (Microsoft.Sharepoint)

SPDocumentLibrary

SPPictureLibrary

Features (Microsoft.Sharepoint)

SPFeatureDefinition

SPElementDefinition

SPFeatureProperty

SPFeatureScope

SPFeature

Sites (Microsoft.SharePoint)

SPSite

SPSiteCollection

SPSiteAdministration

SPWeb

Business Data Catalog (Microsoft.Office.Server.ApplicationRegistry.Administration)

EntityCollection

ApplicationRegistry

Meetings (Microsoft.SharePoint.Meetings)

SPMeeting

MtgUtility

Solutions (Microsoft.SharePoint.Administration)

SPSolution

SPFeatureReceiver

SPSolutionCollection

Lists (Microsoft.SharePoint)

SPList

SPListItem

SPListItemCollection

User Profiles (Microsoft.Office.Server.UserProfiles)

UserProfile

UserProfileManager