Important links

Here are some important links that I gathered from Microsoft articles on SharePoint

Microsoft Office SharePoint Server 2007

Link

Security Resource Center for SharePoint Products and Technologies

Link

About performance and capacity planning (Office SharePoint Server)

Link

Plan for redundancy (Office SharePoint Server)

Link

Plan for performance and capacity (Office SharePoint Server)

Link

Performance and Capacity Planning Resource Center for SharePoint Server 2007

Link

Enable Anonymous Access in Windows SharePoint

It's become very common now to use SharePoint servers as Web servers.
For this activity it's necessary to allow anonymous access to the SharePoint portal or a specific site collection.

The routine that required here is pretty simple, but if you miss one of the steps the result is a site that you cannot reach…

Required steps:
1. Modify authentication provider: Central Administration > Application Management > Application Security. Select the required Web Application and change the Zone to anonymous.
All sites under that Web Application are now anonymous enabled.

2. On the Site Collection: Site Action > Site Settings > Advanced Permissions
Select Anonymous Access.

SharePoint 2007 enabled us to allow Anonymous Access to Sites, Document Libraries and lists.
3. When we need to enable Anonymous Access for lists and libraries we need to check this option and browse to the lists or library.

4. From the dropdown menu on the setting tab: Permissions and Management > Permissions for this document library. Select Anonymous Access.

Moving SharePoint DataBase to another SQL Server

This is a guide I wrote to help make this procedure as easy as it can.
You can find more information about "Moving SP to another SQL server" in this site:
microsoft

It is essential to know if you are moving the SP DB to to a different database server or a server with the same name!

This guide is for moving the DB's to a different database server.

Part 1

On the server that is running the Central Administration Web site, stop the following services:
· Microsoft Single Sign-On service
· Office Document Conversions Launcher service
· Office Document Conversions Load Balancer service
· Office SharePoint Server Search service
· Windows SharePoint Services Administration service
· Windows SharePoint Services Search service
· Windows SharePoint Services Timer service
· Windows SharePoint Services Tracing service
· Windows SharePoint Services VSS Writer service

Stop the IIS – CMD - iisreset /stop.

Backup the Content databases for the following SP sites :
· SP site Content DB
· SP Mysite Content DB
· Shared Services DB
· Shared Services Search DB

Backup the top level site with STSADM command:
Stsadm –o backup –url http://spsite/ –filename %system root%:\SPsite.bak
Stsadm –o backup – url http://spmysite/ –filename %system root%:\SPmysite.bak

Part 2

Copy the DB's (LDF & MDF) to the new SQL server:
· SP site Content DB
· SP Mysite Content DB
· Shared Services DB
· Shared Services Search DB

Attach the DB's to the new SQL server – Take online

Run the STSADM command:
stsadm -o renameserver -oldservername -newservername

You can find more about "renameserver" command in this link:
STSADM

Part 3

Log in to the Central Admin.
Start up and configure the services on the farm
Create all web applications exactly as before – use temp DB when you build the DB's.
Redirect the web application to the origin DB's - Application management > content database:
Disconnect all the DB’s for the web applications
Reconnect the origin DB's.

In Central Administration – restore the SSP: Central Administration > Application Management > Manage this Farm's Shared Services - restore the SSP

It worked for me, I hope it'll work for you…

SharePoint 2010 Sneak Peek

Microsoft releases sneak peeks of SharePoint 2010.
You can get a good sense of the application and look and feel overview.

link: SP 2010

How to fix Blank IIS

From time to time I came across SharePoint farms that have a blank IIS server, in some cases the IIS MMC stops responding at all. Those errors accompany by event log errors:
o Event ID 6398
o Event ID 6482
o Event ID 7076

My first action is to reset the IIS – this fix the problem for a short while…

To fix this errors permanently we need to install the appropriate hotfix and restart the server. If you have multiple servers farm, the hotfix must be apply on all servers

The link to download the fix:
link

Lockdown Feature

When publishing Web portal, most of the time we to want prevent users from accessing the application pages: _layouts/…/default.aspx

The reason to activate this feature in an internet environment is to change the permissions level of the anonymous users group Limited Access privilege. Because there is no way to change these permissions through the UI, we need to use this Feature.

The Lockdown feature removes the View Application Pages permission, and the Use Remote Interfaces permission. This is helpful in preventing users from accessing application pages on a public facing/Internet web site

The Command:

stsadm -o activatefeature -url -filename ViewFormPagesLockDown\feature.xml

Note: this is the same like on all features, we can deactivate this feature (unlocked):

stsadm -o deactivatefeature -url -filename ViewFormPagesLockDown\feature.xml

Link to Microsoft LockDown syntax: LINK

Error: Failed to upgrade SharePoint Products and Technologies

The scenario:

When I try to add a new Web server to an existing farm with no Web applications, after installing the server I ran the SharePoint Products and Technologies Configuration Wizard & receive the following error message:

An exception of type-Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information: Failed to upgrade SharePoint Products and Technologies.

And additionally, the Upgrade.log file contains the following error message:

The access control list on %system root%\Program Files\ Common Files \Microsoft Shared\Web server extensions\12\template\layouts\Web.config could not be modified because the path could not be located in the file system.

Why it happened?

This error occurs when the SharePoint Products and Technologies Configuration Wizard cannot locate or modify the Web.config file.
The reason for this error was because the SharePoint Products and Technologies Configuration Wizard cannot locate or modify the Web.config file - which was supposed to be in the 12\template\Layouts folder

How can I fix it?

1. simply copy the Web.config file from the following folder:
%system root%\Program Files\ Common Files\Microsoft Shared\Web server extensions\12\Config

2. plant it in the following folder:
%%system root%\Program Files\ Common Files\Microsoft Shared\Web server extensions\12\Template\Layouts.

3. Run the SharePoint Products and Technologies Configuration Wizard again

Microsoft Technet link