Installation and Setup – Preparing your Server Environment

For SharePoint Installation, i don't think any other article on the web could be better then this.
http://mindsharpblogs.com/bill/archive/2006/06/27/1153.aspx

The thing that is missing on most of the articles are regarding the principal acocunts and permissions.

Proper planning is crucial to the successful implementation of any MOSS 2007 Farm.

Below is guide to preparing your server environment by creating the proper accounts and simplifying permissions by making of use of Active Directory groups.


Step 1 – Create Accounts and Admin Group in Active Directory

The following user accounts should be created:

SAMPLE USER ACCOUNTS:

Server Farm Account = Domain\SP-ServerFarm
Setup User Account = Domain\SP-SetupUser
SQL Service Account = Domain\SP-SQLService

SAMPLE DOMAIN GLOBAL GROUP:

AD Global Group = Domain\SharePointAccounts

Step 2 – Add Accounts to Administrative Group

Add the three setup accounts created in Step 1 to the Active Directory Global Group created in Step 2.

Step 3 – Add Domain Group to Local Administrators Group on SharePoint Servers

Add the Active Directory Global Group (Domain\SharePointAccounts) to the Local Administrators Group of every Web Front End or Application Server within your SharePoint Farm.

Note: You may also use Active Directory Group Policies to accomplish this.

Step 4 – Add Account to the SQL Server Local Admin Group

Add the SQL Service Account (Domain\SP-SQLService) to the Local Administrator Group of your SQL Server.

Step 5 - Assign SQL Server Roles

Create the following Logins and assign the defined Roles on the SQL Instance to be used for the installation of MOSS 2007:

Logins Roles
Domain\SP-ServerFarm dbcreator, securityadmin
Domain\SP-SetupUser dbcreator, securityadmin
Domain\SP-SQLService dbcreator, securityadmin, sysadmin
========= ===== === ==== = ================= =============


Domain-level SharePoint User Accounts (Farm Deployment Only)

Setup User Account

SQL Server Service Account

SharePoint Farm Account

Shared Services Provider (SSP) Account

SSP Service Account (Timer Service)

My Sites Application Pool Account

Search Service Account

Content Access Account

User Profiles Access Account

Excel Services Account

Application Pool Identity Account

STSADM command to update the solution

stsadm -o upgradesolution -name -filename C:\join0120\ -allowGacDeployment -immediate

The trial period for this product has expired

you may get this error sometime while working with a website that is developed using Sharepoint.With this error message do not think that the trial period of your shrepoint has got expired.Rather this error comes due to a DCOM permissions bug.
To fix please add your MOSS web application's IIS Application Pool domain account to the local BUILTIN\Administrators user group and then it works fine.

SharePoint Designer Server error: This item cannot be deleted because it is still referenced by other pages

Server error: This item cannot be deleted because it is still referenced by other pages

You might get this error when you try to delete a master page from the _catalogs directory.

Following solution worked for me.

Open the Master gallery in Explorer view
Create a Directory named "Delete"
Cut all the un-wanted Master Pages and paste it inside the "Delete" directoty
Delete the "Delete" Directory

SharePoint Master Pages Components Overview

Master Pages

A single master page file can control the look and feel of countless pages within a site/application. It is basically a next generation approach of how to include common content in lieu of frames or server side include files.

Content Pages
Master pages store the layout and design, while content pages define the content. The content page is bound to a master page. Together the two create the presentation layer of content for a site/application.
In SharePoint content pages are called Page Layouts. But they work similar to content pages. The master page file is combined with the page layout to create the presentation layer of content for the SharePoint site. Master Page and Page Layout combine to create the rendered page

The Components of a SharePoint Master Page File

The master page will contain all of the user interface layout code for the site. This includes CSS, JavaScript and HTML.

Examples of what you would put in the master page:
• Header code including company logo and branding images
• Navigation
• Footer code including copyright statements and links
• CSS (cascading style sheet) styles
• Body background colors, images or styles
• Common JavaScript functions

SharePoint 2007 Backup Schedule in Windows 2008

There is no feature available in Microsoft SharePoint 2007 Central adminisration to schedule the back up/restore operations.
The best method is to create a batch file, write the stsadm command for taking and storing backup on some floder of your server or netwrok folder, and finaly put that on windows task scheduler.

Open 'Notepad'

Type Following and save as "SharepointBackschedule.bat"


@echo off
echo =============================
echo Back up sites for the Server farm to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\SharePoint\

echo =============================

@SET STSADM="c:\program files\common files\microsoft shared\web server extensions\12\bin\stsadm"

cd C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\SharePoint\

@echo off

md "%DATE:/=_%"

echo ========================================

echo Directory based on the current date daytime created

echo ========================================

%STSADM% -o backup -directory "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\SharePoint\%DATE:/=_%" -backupmethod full -overwrite

echo completed


Now Click on

Click on Trigger, click on New and select the schedule (Daily/Weekly etc)

Click on the Action and click on new and browse the batch file you have created.

Click Ok

And your scheduler is ready.

How to use JS in Sharepoint Masterpages

Save you js file under 12 hive on the following location of the sharepoint server

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\1033

Add the reference In your master page