Article here

Related posts:

1. Collaborative Workflow Improvements in SharePoint 2010
2. Hello world!
3. SharePoint 2010 Download

Question: Can you audit permission changes in a site collection?

Answer: This is possible, but by default security changes are not audited. To enable auditing:

1. Select Site Actions + Site Settings + Modify All Site Settings at the site collection root site.
2. Click the Site collection audit settings link.
3. Select the Editing users and permissions option:

Once turned on, changes to permissions on sites, lists and items will be audited. To view the audit log:

1. Click the Audit log reports link on the “Site Settings” page for the site collection.
2. Click the Security Settings link:

This will open the audit log in an Excel spreadsheet. The following example shows a summary showing a single security change resulting from a breaking of permission inheritance:

More detailed information is available in the “Report Data” sheet in the Excel workbook.

Source

Related posts:

1. HowTo: Create Site Collections with Create Site
2. QOD: Navigation Breadcrumb For My Site
3. HOW TO: Import User Profile Information of Enabled User Accounts

Encounter error messages:

Exception from HRESULT: 0x80040E14.
Troubleshoot issues with Windows SharePoint Services.

HTTP 500 – Internal server error

Unable to perform the following operations:

Edit columns on a list

Import a spreadsheet

Add choices to a choice field

To resolve this, run the following command for

Windows SharePoint Services 2.0

1.Click Start, click Run, type cmd in the Open box, and then click OK.

2.At the command prompt, type the following lines, and then press ENTER after each line:

cd /d %commonprogramfiles%\Microsoft Shared\Web Server Extensions\60\Bin
stsadm -o upgrade -forceupgrade

3.Type exit to exit Command Prompt.

Windows SharePoint Services 3.0

1.Click Start, click Run, type cmd in the Open box, and then click OK.

2.At the command prompt, type the following lines, and then press ENTER after each line:

cd /d %commonprogramfiles%\Microsoft Shared\web server extensions\12\BIN
stsadm -o upgrade -forceupgrade

3.Type exit to exit Command Prompt.

Sourced from Microsoft KB 841216

Related posts:

1. How to set restrictions on a site collection
2. HowTo: Change Service Accounts and their Passwords
3. HowTo: SlipStream WSS and MOSS Security Updates

Navigate to Pages library on your site to to see who has this checked out this page.

Image Source | Content Source

Related posts:

1. Upgrading an Existing Master Page to the SharePoint Foundation Master Page
2. Hello world!
3. Tip: Recycle IIS Application Pool

Piyush Mittal has documented his field experience.

Simple answer:

Using a dedicated application pool can help avoid conflict with existing Web applications.

Refer to this Microsoft article for more info.

If you install SharePoint Services after Reporting Services is already installed and configured, your Reporting Services installation will be unusable until you perform the following steps:

1. Start the Reporting Services Configuration tool.

STSADM.EXE -o addpath -url http://localhost/ReportServer -type exclusion
and
STSADM.EXE -o addpath -url http://localhost/Reports -type exclusion
By default, the Stsadm.exe file is located in C:\Program Files\Common Files\Microsoft Shared\Web server extensions\60\bin

2. Configure the Report Server virtual directories.

Check out this link to configure the directories.

Thanks Piyush.

Related posts:

1. How to set restrictions on a site collection
2. WSS SP3: Post Installation Issues
3. SharePoint guidance for SQL Server 2008 database administrators