SharePoint - SQL query to find SSRS reports

Use database_name
SELECT [DirName],[LeafName]    
 FROM [dbo].[AllDocs] (nolock) where Extension='rdl'
GO

Note: You can replace file type from rdl to doc,docx, xlsx etc.. to find different documents with file types. You can modify query to count for total etc..

Create and build power shell commands for SharePoint
Powershell Command builder:

http://www.microsoft.com/resources/TechNet/en-us/Office/media/WindowsPowerShell/WindowsPowerShellCommandBuilder.html

SSRS Cascading reports using sharepoint 2007 list data

SSRS Cascading reports using Office sharepoint 2007 lists

Tools used: Report Builder 3.0

I'll Update this shortly..

Customize your sharepoint site using Sample master pages

Source
************

http://office.microsoft.com/en-us/sharepointdesigner/HA102223711033.aspx

Download the sample master pages from the below location ,

http://www.microsoft.com/downloads/details.aspx?FamilyID=7C05CA44-869A-463B-84D7-57B053711A96&displaylang=en

Instructions
***************************
To install this download:

***************************

1. Run MasterPage.exe to unpack the master page package to a location on your computer.
2. Right click on the extracted file, MasterPageExamples.zip and select "Extract All..."
3. Complete the Extraction Wizard.
4. Open your Windows SharePoint Service 3.0 site in Microsoft Office SharePoint Designer 2007.
1. Open SharePoint Designer.
2. On the File menu, click Open Site.
3. In the Open Site dialog box, type the URL of the site that you want to open in the Site name box, and then click Open.
5. Import the master page files into your site.
1. On the File menu, select Import > File...
2. In the Import dialog box, select Add Folder...
3. Browse to location of the extracted master page files, and then browse to a specific master page set.
4. Select the "_catalogs" folder and click Open.
5. Repeat steps 2-4 for the "images" folder and the "styles" folder.
6. Click Ok to finish importing the files.

Instructions for use:
***********************************

To set the imported master page as the default master page:

1. Open the Folder List. On the Task Panes menu, select Folder List.
2. On the Folder List, within the _catalogs folder, open the masterpage folder.
3. In the master page folder, find the master page style and color you want to apply, right-click on the file and then click "Set as Default Master Page" on the shortcut menu.

Please refer to the Microsoft Office SharePoint Designer Master Pages site for additional help and how-to articles that cover the use of master pages.

To remove this download:
*********************************

* Delete the package and uncompressed files from your computer.

Reporting Services GUI Configuration

Reporting Services GUI Configuration with WSS 3.0 / MOSS
****************************************************************


http://blogs.msdn.com/sharepointbi/archive/2009/05/29/ssrs-integrated-mode-with-sharepoint-and-report-builder-2-0.aspx

http://www.helloitsliam.com/archive/2007/10/23/moss2007-%E2%80%93-reporting-services-general-ui-configuration.aspx



Key words
------------

SSRS with sharepoint ,

Configure Excel Services

http://technet.microsoft.com/en-us/library/cc263517.aspx



http://msdn.microsoft.com/en-us/library/ms496823.aspx



http://msdn.microsoft.com/en-us/library/cc514223.aspx#MOSS2007TenTips_QuickTipsforCommonExcelServicesIssues

SharePoint IIS Traffic Analysis

SharePoint IIS Traffic Analysis

SharePoint IIS Traffic Analysis
***************************************

Internally we have experienced situations where internal users have built tools or solutions which have negatively affected performance for our SharePoint users. This can be done in different ways such as Setting up multiple MOSS Farms to crawl our customer facing front ends at high performance setting or creating a custom application to execute against various MOSS web services without throttling the application in any way. From that need spawned a little tool we created with the help of log parser J The following is an example of how you could setup a scheduled task to notify you on number of Hits against your moss environments and how much bandwidth each user is consuming.



Please remember to never perform any of the following on production without first trying it out in a test environment, all items here are merely examples of how you ‘could’ perform such an action. J



Skills and Items required / assumed to perform this task.

· A SQL 2005 server with XP_CMDSHELL enabled

· Read Permissions for SQL Server Account Granted to the IIS Log directory of your SharePoint Servers

· Access to create and modify databases on your SQL Server

· Logparser 2.2 Installed on your SQL Server

· Good Understanding of SQL Server and TSQL

· Good Understanding of IIS

· Access to all customer Facing SharePoint Front Ends

· Good Understanding of SharePoint J





Step 1: Create a reporting database on your SQL Server, for the benefit of this blog entry we will call this database IISReports. Set that reporting database to autogrow for the data file and log file.



Step 2: Grant read permissions to all IIS log directories where your Web application Logs are stored on all servers you wish to report on.

Example: %WINDIR%\System32\Logfiles\ex080218.log For better performance internally we place our IIS Log files on a serperate drive



Step 3: Install Logparser 2.2 to a directory on your sql server(make note of this directory) For the purpose of this entry we will call this c:\temp\logparser.exe

Logparser 2.2 can be downloaded @ http://www.microsoft.com/technet/scriptcenter/tools/logparser/default.mspx



Step 4: Create Tables that we will use to pull in and manipulate the data

Click Here to open example Script

Step 5: execute the Create script for the stored procedure that will be used to pull the data.

Click Here to Open example Script – Make sure to read the /**notes**/ as they direct you to make changes to the script to cater to your environment.

Step 6: If everything has been followed and updated accordingly you can now run the following in SQL.. shortly there after you will receive an email similar to the following J



use [IISReports]

go

exec IISLogtracking

go

Configure Kerberos authentication (Office SharePoint Server)

Other useful articles
*************************
http://blogs.msdn.com/martinkearn/archive/2007/04/23/configuring-kerberos-for-sharepoint-2007-part-1-base-configuration-for-sharepoint.aspx

Testing SharePoint Kerberos Configuration
******************************************

http://www.wssdemo.com/Blog/archive/2009/06/12/Testing-SharePoint-Kerberos-Configuration.aspx

Master Page and Themes on WSS sites in MOSS

Master Page and Themes on WSS sites in MOSS




Applying a Site Master



Create a "team" site (team template)
In site settings, go to site collection features and activate the "Office SharePoint Server Publishing Infrastructure" feature
Under Look and feel in site settings, go to Master Page
for Site Master page choose BlackVertical.master (check the box to apply to sub sites)
Expected result... go to home page and I'd see a fancy site with the black sides (no MS blue right?)

Wrong. Apparently the Site Master applies to publishing pages only (works for Intranet or Internet Portal Templates, but you'll discover it doesn't apply to sub sites with WSS templates)


Applying a System Master


5. Go back to site settings, Master Page, and for System.Master page choose BlackVerticle.Master (check the box to apply to sub sites)

Site Settings looks MS blue
Go to home page.
WooHoo now we have the new master page... ,
Wait the bars on the web parts are MS blue...

9. Go to site settings, under look and feel choose Site themes and choose Obsidian. Click apply.

10. Site settings, now looks like the black obsidian theme, but going to the home page or any list still has the blue web part bar.

So, how do we solve that?


Applying a Custom CSS (from a theme)


11. Go to site settings, click view source, you'll see the reference to the theme in the style sheet just a few lines down... Look for:

12. Copy the href URL path of the css reference (minus the querystring): /sites/tr5iw/_themes/Obsidian/Obsi1011-65001.css

13. Go to Master Page, scroll to the bottom, choose Specify a CSS file to be used and put in the URL to the CSS. "/sites/tr5iw/_themes/Obsidian/Obsi1011-65001.css" check the box to apply to sub sites and “click Apply”

14. Go to homepage

15. We did it. No blue.

Finish… Without opening any tools our UI in our team site has a consistent theme across site settings, the homepage and list pages.

So what did we learn? There is a difference between site.master and system.master in relation to the pages and templates.

Site Master: The site master page will be used by all publishing pages. (That’s great for the Internet and Intranet publishing site, but not for many of the subsites)

System Master: Use the system master page for all forms and view pages in this site. (let me amend this with these are all the site templates and pages that the site master does not apply to, including team sites, document workspaces, web part pages, and all non publishing pages.

MSDN has some good content on modifying master pages:

Master Pages



Customizing Master Pages in Windows SharePoint Services


SharePoint Designer on Office Online has some good info as well..

Troubleshooting for Office SharePoint Server 2007

Troubleshooting for Office SharePoint Server 2007


http://technet.microsoft.com/en-us/library/cc462944.aspx

Content Deployment - Step By Step

Content Deployment - Step By Step Tutorial

http://blogs.msdn.com/jackiebo/archive/2007/02/26/content-deployment-step-by-step-tutorial.aspx



Related References -

Content Deployment Post by Tyler Butler:

http://blogs.msdn.com/sharepoint/archive/2006/05/02/588140.aspx

MOSS SDK on Content Deployment:

http://msdn2.microsoft.com/en-us/library/ms549024.aspx

TechNet on Plan Content Deployment:

http://technet2.microsoft.com/Office/f/?en-us/library/edcdacca-8013-460e-95a0-d2b83b6cc7ef1033.mspx

TechNet on Design Content Deployment Topology:

http://technet2.microsoft.com/Office/f/?en-us/library/1d6d6040-6cbb-4685-a40e-1e9086d426831033.mspx

MOSS 2007 User and Profiles import from Active Directory

MOSS 2007 User and Profiles import from Active Directory.


Its very normal to have a scenario in which the user profile information in stored in directory service like Active Directory. Since personalization in sharepoint largely depends upon user profiles it becomes imperative to not only import the user information in AD into sharepoint as user profiles but also to run incremental imports to sync up user profiles with new information added into the Active directory.

As you know sharepoint integrates with Active directory and a user profile record gets created in sharepoint when an AD authenticated user first accesses a site. Assumption here is that the user already has adequate permissions on the site. As noted above incremental imports facilitate synchronizing user information stored in AD with the profile created in sharepoint.

The following steps need to be followed to configure import of user profiles from Active Directory -

Scenario-1 - All users are in the current domain.


1. Go to User Profile and Properties under Shared Services Administration.

2. Click on configure profile import link. Select current domain as the profile datasource.

3. Make sure default access account is specified and is valid.

4. Run full import or incremental report.


Scenario-2 - Users are scattered into multiple domains or other data sources.


1. Go to User Profile and Properties under shared services administration.

2. Click on Import New Connection. Add a new connection for each of the data sources where you users are located. Delete any unwanted connections that might already be there.

3. Configure the import as mentioned above and make sure that Custom source is selected.

4. Run the full import or incremental import.

Configure Search On MOSS 2007

The following procedures step you through the process of configuring Office SharePoint Server 2007 search services, creating a Web application for the SSP, creating the SSP, and configuring indexing settings.



Start and configure the Search service

On the SharePoint Central Administration home page, click the Operations tab on the top navigation bar.
On the Operations page, in Topology and Services, click Servers in farm.
On the Servers in Farm page, click the server on which you want to configure the search service.
Click Start next to Office SharePoint Server Search.
On the Office SharePoint Server Search Settings page, in the Query and Indexing section, make sure that the Use this server for indexing content and Use this server for serving search queries check boxes are selected.
In the Default Catalog Location section, type a path to a physical folder to store the index files, or use the default location that is specified.
In the Contact E-Mail Address section, specify a valid e-mail address.
In the Service Account section, click Configurable, and in User name and Password, type the user name and password for the user account under which you want the Search service to run. The user account must be a member of the Administrators group on the computer that is running the Search service. If you want to use the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers, see the Known Issues/Readme for Office SharePoint Server 2007 Beta 2. The user name must be in the format DOMAIN\username.
In the Web Front End And Crawling section, do one of the following:
If you are configuring the search service on a server that provides Web services and renders Web content, click No dedicated Web front-end computer for crawling
If you are configuring the search service on a server that is a standalone search server that does not provide Web services and render Web content, click Use a dedicated web front end computer for crawling, and then, in Select a web front end computer, click the computer you want to use for crawling.
Click Start.


Start the Windows SharePoint Services Web Application service
You must start the Windows SharePoint Services Web Application service on every computer that you want to act as a Web server and was set up using the Complete option during Setup. This service is started by default on servers that were set up using the Web Front End option. To enhance security, you can leave this service turned off on application servers that do not provide Web content to client computers. Also, you do not need to turn this service on to use SharePoint Central Administration on a server.

On the SharePoint Central Administration home page, click the Operations tab on the top navigation bar.
On the Operations page, in Topology and Services, click Servers in farm.
On the Servers in Farm page, click the server on which you want to start the Windows SharePoint Services Web Application service.
Click Start next to Window SharePoint Services Web Application.

Create the Shared Services Provider

On the SharePoint Central Administration home page, click the Application Management tab on the top navigation bar.
On the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farm's shared services.
On the Manage this Farm's Shared Services page, click New SSP. Important: If you have not created a Web application for the SSP administration site, you need to create one before you create the SSP. If you have already created a Web application for the SSP administration site, skip to step 14.
On the New Shared Services Provider page, click Create a new Web application.
On the Create New Web Application page, in the IIS Web Site section, click Create a new IIS web site, and do not modify the default settings in this section.
In the Security Configuration section, under Authentication provider, select the appropriate option for your environment, and do not modify the default settings in the remainder of this section.
In the Load Balanced URL section, do not modify the default settings.
In the Application Pool section, click Create new application pool.
In Application pool name, enter the name of your application pool or use the default name.
Click Configurable, and in User name and Password, type the user name and password for the user account under which you want the application pool to run. The user account does not have to be a member of any particular security group. It is recommended that you use the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Office SharePoint Server 2007 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user name must be in the format DOMAIN\username.
In the Database Name and Authentication section, verify the database information and make sure that Windows Authentication (recommended)is selected.
In the Search Server section, do not modify the default settings.
Click OK. Upon successful creation of the Web application, the New Shared Services Provider page appears.
In the SSP Name section, in Web Application, select the Web application that you created for the SSP, and do not modify any of the default settings in this section.
In the My Site Location section, do not modify any of the default settings.
In the SSP Service Credentials section, in User name and Password, type the user name and password for the user account under which you want the SSP to run. The user account does not have to be a member of any particular security group. It is recommended that you use the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Office SharePoint Server 2007 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user name must be in the format DOMAIN\username.
In the SSP Database section, you can either accept the default settings (recommended), or specify your own settings for the database server, the database name, or the SQL authentication credentials.
In the Search Database section, you can either accept the default settings (recommended), or specify your own settings for the search database server, the database name, or the SQL Server authentication credentials.
In the Index Server section, in Index Server, click the server on which you configured the Search service. Note: If there is no index server listed in the Index Server section, then no server in your farm has been assigned the index server role. To assign the index server role to a server in your farm, follow the instructions in the "Configure the Search service" section earlier in this topic.
In the SSL for Web Services section, click No.
Click OK. Upon successful creation of the SSP, the Success page appears.
On the Success page, click OK to return to the Manage this Farm's Core Services page.

Configure indexing settings

On the SharePoint Central Administration home page, click the Application Management tab on the navigation bar.
On the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farm's shared services.
On the Manage this Farm's Shared Services page, click SharedServices1.
On the Shared Services Administration page, in Search, click Search Settings.
On the Configure Search Settings page, in the Crawl Settings section, click Default content access account.
In the Default content access account section, in Account, Password, and Confirm Password, type the user name and password for the user account that you want to use to crawl content on your sites. This account must be a domain user account. It is recommended that you use the principle of least privilege and select a unique user account that cannot modify content and does not have administrative rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Office SharePoint Server 2007 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user account that you specify will be added to the Web application Full Read policy for your farm. The user name must be in the format DOMAIN\username.
Click OK.
In the Crawl Settings section, click Content sources.
On the Manage Content Sources page, click Local Office SharePoint Server sites.
On the Edit Content Source page, in the Crawl Schedules section, under Full Crawl, click Create schedule.
In the Manage Schedules dialog box, configure schedule settings for full crawls of your content, and then click OK.
In the Crawl Schedules section, under Incremental Crawl, click Create schedule.
In the Manage Schedules dialog box, configure schedule settings for incremental crawls of your content, and then click OK.
In the Start Full Crawl section, select the Start full crawl of this content source check box, and then click OK.



You are done!

MOSS workflows

http://technet.microsoft.com/en-us/library/cc263148.aspx#section2

Understanding workflow
http://technet.microsoft.com/en-us/library/cc263374.aspx

Plan workflows
http://technet.microsoft.com/en-us/library/cc262708.aspx

Plan workflows for document management
http://technet.microsoft.com/en-us/library/cc262233.aspx

Plan workflow for form templates
http://technet.microsoft.com/en-us/library/cc262853.aspx

Plan content approval and scheduling
http://technet.microsoft.com/en-us/library/cc263156.aspx

Authoring Windows SharePoint Services Workflows
http://technet.microsoft.com/en-us/library/cc263088.aspx

Introduction to Workflows in Windows SharePoint Services
http://msdn.microsoft.com/en-us/library/ms434426.aspx

Workflows in Office SharePoint Server 2007
http://msdn.microsoft.com/en-us/library/ms549489.aspx

How to: Design a Workflow Task Form to Use Task Data
http://msdn.microsoft.com/en-us/library/ms550782.aspx

Index for Stsadm operations and properties (Windows SharePoint Services)
http://technet.microsoft.com/en-us/library/cc288413.aspx

Job-workflow: Stsadm property (Windows SharePoint Services)
http://technet.microsoft.com/en-us/library/cc424946.aspx

Alerts-enabled: Stsadm property (Windows SharePoint Services)
http://technet.microsoft.com/en-us/library/cc287644.aspx

Timer Job: Stsadm properties (Windows SharePoint Services)
http://technet.microsoft.com/en-us/library/cc424953.aspx

2007 RTM White Papers

Step 1 – Let’s get the Active Directory Ready.
When you E-Mail enable a library in a site it will create a new contact in the OU we specify for the AD. Therefore it makes sense to have an OU dedicated to MOSS2007 list e-mail addresses.
On a Domain Controller Open Active Directory Users and Computers in the administration tools and create a new Organizational Unit under your main domain name. In my case I used the OU name sharepointdl in the domain trainsbydave.com

Steps to move SQL server from one machine to another

STEP BY STEP PROCEDURE TO MOVE SQL SERVER FROM ONE MACHINE TO ANOTHER :-

1.) Back Up Data
a.) Click Start, point to All Programs, point to SharePoint Portal Server, and
then click SharePoint Portal Server Data Backup and Restore.
b.) The Microsoft Office SharePoint Portal Server 2003 Backup and Restore dialog
box opens.
c.) Click the Backup tab.
d.) In the Backup location and name box, do the following:
e.) Type or browse to the location where you want to store the backup files.
f.) After the folder name, type the file name that will be the prefix for each
backup file.
g.) In the tree view, expand Available components by clicking the plus sign.
h.) Click the components that you want to back up.
i.) In the Backup comment box, type a comment.
j.) Optionally, select the Overwrite existing files check box.
k.) Click Backup.
l.) On the successful completion message box, click OK.


2.) Delete Portal Site, leave databases by doing the following:
a.) Go to the SharePoint Portal Server Central Administration for portal>
b.) Go to the heading "Portal Site and Virtual Server Configuration"\select "List
and manage portal sites"
c.) select your Portal website and in the drop down box select "Delete Portal
Sites"
d.) It will launch a "Delete dialog box
e.) Next to the heading "Associated Databases", it has a checkbox named "delete
all database" make sure this checkbox is NOT checked, then click OK


3.) Go to Topology page, remove all roles by doing the following:
a.) Go to SharePoint Portal Server Central Administration for portal>
b.) go to the heading "Server Configuration"\select "Configure server topology"
c.) SharePoint Portal Server Central Administration Configure Server Topology
page
d.) select "Change Component Assignments" button and uncheck everything next to
Component Assignment, job, server, index, and set your "Job Server" to none.
e.) click OK
(FYI: If it prompts you for username and password, go ahead and enter an admin's
account)


4.) Disconnect from Config DB by doing the following:
a.) Go to SharePoint Portal Server Central Administration for portal>
b.) go to the heading "Server Configuration"\select "Configure configuration
database server"
c.) select the radio button "Disconnect from configuration database" this
references all the old SQL Server location\click OK
(FYI: When you delete your config database and create a new one you do not lose
anything. It does not contain any data in it. It is just a connection between
sharepoint and SQL.)


5.) Create new config database, on new SQL server by doing the following:
a.) Go to SharePoint Portal Server Central Administration for portal>
b.) go to the heading "Server Configuration"\select "Configure configuration
database server"
c.) select the radio button "Create configuration database"
enter all your new SQL Server database name
d.) click OK


5.) VIA SQL, backup the SQL databases from the old server and restore to the new
server by doing the following:
a.) go to the old SQL Server Database and you will have three database to backup
up the SITE, SERV, and PROF
b.) right click on one of your databases\select "All Tasks"\"Backup database..."
c.) under the General Tab\select the database name, select Add button
d.) select Filename and put the path and the name of one your backup like
portalsite_backup.bak
e.) click OK and do this for the other ones like SERV and PROF
f.) You do not need to backup the Config database we went a clean one from the new
SQL Server database.
g.) Go to your new SQL Server Enterprise Manager and we have to restore all the
databases from the old server to the new one
h.) right click on Databases folder\select "All Tasks"\"Restore Database..."
i.) under General tab enter the name you want the "Restore database as" for
example SITE
j.) Next to the Restore heading select the "From Device" radio button\select the
"select devices" button
k.) select Add button\ in the Filename enter the path to your backup file that you
created earlier that I called portalsite_backup.bak
l.) select OK and make sure Database - Complete is checked.
m.) now do the restore steps for your backup SERV and PROF databases to this new
SQL server


6.) Go to Topology page, add all roles by doing the following:
a.) Go to SharePoint Portal Server Central Administration for portal>
b.) go to the heading "Server Configuration"\select "Configure server topology"
c.) SharePoint Portal Server Central Administration Configure Server Topology
page
d.) select "Change Component Assignments" button and check everything next to
Component Assignment, job, server, index, and set "Job Server" to your new server
e.) click OK


7.) Create a new portal site, choose the restore option by doing the following:
a.) Go to the SharePoint Portal Server Central Administration page
b.) Go to the heading "Portal Site and Virtual Server Configuration"\select
"Create a portal site"
c.) in the Create Portal Site dialog box select the radio button "Restore a
portal"
In the section Restore Portal From Database this will let you specify the new SQL
server and restored databases
Enter all our new SQL Server name and pointing to the SITE, SERV, and PROF on your
new SQL Server
d.) select OK

Refresh your website and see if your portal is up and running

Stsadm - template codes

You are check out the template codes when we try to apply them using the stsadm command.

Site Template Codes when using STSADM.

Each Site Template that is installed on SharePoint 2007 will have a unique name and number to allow for referencing when coding applications or using STSADM for site deployment (when using the -sitetemplate parameter, e.g. -sitetemplate STS#0 would apply a team site template)



WSS Templates

Team Site: STS#0

Blank Site: STS#1

Document Workspace: STS#2

Wiki Site: WIKI#0

Blog Site: BLOG#0

Basic Meeting Workspace: MPS#0

Blank Meeting Workspace: MPS#1

Decision Meeting Workspace: MPS#2

Social Meeting Workspace: MPS#3

Multiple Meeting Workspace: MPS#4

MOSS Templates

Document Center: BDR#0

Site Directory: SPSSITE#0

Report Center: SPSREPORTCENTER#0

Search Center with Tabs: SRCHCEN#0

My Site Host: SPSMSITEHOST#0

Search Center: SRCHCENTERLITE#0

Personalisation Site: SPSMSITE#0

Collaboration Portal: SPSPORTAL#0

Publishing Portal: BLANKINTERNETCONTAINER#0

Publishing Site: CMSPUBLISHING#0

Publishing Site with Workflow: BLANKINTERNET#2

News Site: SPSNHOME#0

Turning a domain user into a full MOSS2007 farm administrator

Turning a domain user into a full MOSS2007 farm administrator
================================================================

Imagine you have a farm administrator. He’s just on his own, because MOSS is so easy to manage that you don’t need more people. He does it all: Creating web applications, site collection, manages the Business Data Catalog, Search, Shared Services, you name it, he does it. And then it happens: He leaves for a better job. I agree, that will not happen very fast and often because, well, SharePoint just rocks, but it happens. So after your done crying and sobbing, you find someone who will and can take his place. This person is now a hero and can’t wait to get started. So the leaving farm administrator needs to grant him the necessary permissions to become a full blown farm administrator. What does he need to do?
Well that’s easy you think. Just make the user a member of the SharePoint Group “Farm Administrators” and your done. Well not quite, there is a bit more to it. Yes, you can do a lot of things in the Central Administration, but not everything. You need to set permissions at more locations in the Central Administration and Shared Services Provider to make someone a full blown farm administrator. To get a better idea of the levels of administration in MOSS, read this article from Technet.
Central Administration
To grant someone permissions to the Central Administration so that he can perform the necessary administrative tasks there you need to do the following:
• Add the user to the Farm Administrators group in the Central Administration. This will grant permissions for performing most of the administrative tasks in the Central Administration.
• Add the user to the Site Collection Owners of the Central Administration. This is needed for site collection management tasks within the Central Administration.
• Make the user a member of the Administrators group of the server. Because adding a user to the Farm Administrators group does not give full administrative rights in the Central Administration, you also need to add the user to the Administrators group of the server. The extra tasks that can performed then are:
o From the SharePoint Web Application Management, the option “Create of extend Web application”. This option is security trimmed, where the other options that are not available to you in this tab are not. To be able to perform this operation, you need to be a local administrator.
o From the InfoPath Forms Services section, the option “Upload form template”. To be able to use this, you need to be a local administrator.
o From the Office SharePoint Shared Services section, the option “Create of configure this farm’s shared services”. You need to be a local administrator for this.
Note: You need to be a local administrator to be able to add a user to the Farm Administrators group!

Shared Services Provider Administration
When the user also need to perform SSP administrative tasks (And he does, because you want him to be a full blown farm administrator right?) you need set some additional permissions. And as you have read in the Technet article, there is also something like Services administration. You need to set permissions on those explicitly. These services are:
• Personalization services
• Audiences
• Search settings
• Usage reporting
• Business data catalog
So you start by making the user a Site Collection Owner for the Shared Services Provider site. The user is then able to perform the following administrative tasks:
• User Profiles and My Sites:
o Trusted My Site Host Locations
o Published links to Office client applications
o Personalization site links
o Personalization services permissions
• All of the administrative tasks under Search
• All of the administrative tasks under Office SharePoint Usage Reporting
• All of the administrative tasks under Excel Services Settings
• Business Data Catalog
o Business Data Catalog permissions
Note: It is possible that you see a login box when you want to see the Search usage reports page. This is caused by a bug in the
.NET Framework 2.0. Read my previous blog post for more information.

Next thing you need to do is set the Personalization services permissions and Business Data Catalog Permissions. For the Personalization services permissions is the minimum that you need the “Manage permissions” permission. For the Business Data Catalog permissions is the minimum that you need the “Set permissions” permission. But since we want a full blown farm administrator just check all checkboxes.
Note: Because you are the site collection administrator you are able to set those permissions yourself!

Once you done this, you have created a full blown farm administrator.
Summary
Summarizing is this what you need:
• Member of the Administrators group on the server. Doing this makes you a local administrator.
• Site Collection Owner of the Central Administration site
• Member of the Farm Administrator group in the Central Administration
• Site Collection Owner of the Shared Services site
• Granted all permissions for the Personalization services
• Granted all permissions for the Business Data Catalog

important shortcut links to any Sharepoint sites

Following are important shortcut links to any Sharepoint sites………..

Site settings Page /_layouts/settings.aspx
Web Parts Maintenance Page /default.aspx/?contents=1
Master page /_Layouts/ChangeSiteMasterPage.aspx
Title, description and icon /_layouts/prjsetng.aspx
Navigation /_layouts/AreaNavigationSettings.aspx
Page layouts and site templates /_Layouts/AreaTemplateSettings.aspx
Welcome page /_Layouts/AreaWelcomePage.aspx
Tree view /_layouts/navoptions.aspx
Site Themes /_layouts/themeweb.aspx
Reset to site definition /_layouts/reghost.aspx
Searchable columns /_Layouts/NoCrawlSettings.aspx

Galleries
Site Content types /_layouts/mngctype.aspx
Site Columns /_layouts/mngfield.aspx
Site Templates /_catalogs/wt/Forms/Common.aspx
List Templates /_catalogs/lt/Forms/AllItems.aspx
Web Parts /_catalogs/wp/Forms/AllItems.aspx
Workflows /_layouts/wrkmng.aspx
Others
Create Site /_layouts/newsbweb.aspx
New Site Content Type /_layouts/ctypenew.aspx
Site Usage Report /_layouts/usageDetails.aspx
Recycle Bin /_layouts/RecycleBin.aspx
Site Collection Recycle Bin /_layouts/AdminRecycleBin.aspx