List Template Id

ListId - Description

100 Generic list

101 Document library

102 Survey

103 Links list

104 Announcements list

105 Contacts list

106 Events list

107 Tasks list

108 Discussion board

109 Picture library

110 Data Sources list

111 Site Template Gallery

113 Web Part Gallery

114 List Template Gallery

115 XML Form Library (InfoPath)

120 Custom grid for list

200 Meeting Series list

201 Meeting Agenda list

204 Meeting Decisions list

207 Meeting Objectives list

210 Meeting text box

211 “Things to Bring” Meeting list

212 Meeting Workspace Pages list

300 Portal Sites list

1100 Issue Tracking list

2002 Personal document library

2003 Private document library

Sharepoint Banner

1. Create you banner.jpg and 
   
2. Copy to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\IMAGES
   
3. Make modification in the core.css as shown below.("C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033\STYLES\CORE.CSS")

Before Modification:

.ms-globalbreadcrumb{

font-size:8pt;

text-align:right;

background-color:#ebf3ff;

padding:2px 10px 2px 5px;

}

After Modification:

.ms-globalbreadcrumb{

font-size:8pt;

text-align:right;

background-color:#ebf3ff;

background-image:url("/_layouts/images/banner.jpg");

padding:2px 10px 79px 5px;

}

Override BDC default Action

Create a new Property element in the Properties element of the Entity.  Give it an attribute of DefaultAction and specify the name of the Action we defined earlier. 

Default

Specify your custom Actoin with Name="Default".

eg.        

      Action Position="1" IsOpenedInNewWindow="false" Url="{0}" ImageUrl="" Name="Default"

    

When you import the application definition, you will receive a warning like the following. 

"Could not create profile page for Entity MyEntity.  The error is: Default action exists for application ‘MyInstance’, entity ‘MyEntity’.  Profile page creation skipped.

This really isn’t an error.  It is just telling you that since you specified a default action, it did not automatically generate a profile page for the entity.

Identify WFE Vs Complete option used

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

“You must use the Complete installation option on all computers you want to be index servers, query servers, or servers that run Excel Calculation Services.”

To identify which Sharepoint Server is installed using complete option, just check the Excel Calculation Services Tab is available in the Services on the Server.

To Change a server with WFE to Complete, follow the following steps

1. Remove Server from the Farm

2. Uninstall Moss

3. Install Moss with complete Option. Install the updates(e.g., SP2)

4. Add to the Existing Farm.

That is it.

Get SSP URL

 Use the following Chunk 2 get the SSP URL. This uses reflection mechanism.

 private string getSSPURL()

{

     string uri = string.Empty;

     ServerContext sc = ServerContext.Default;

     object ssp = sc.GetType().GetProperty("SharedResourceProvider",BindingFlags.Instance | BindingFlags.NonPublic).GetValue(sc, null);

     Guid sspGuid = (Guid)ssp.GetType().GetProperty("AdministrationSiteId").GetValue(ssp, null);

     using (SPSite sspSite = new SPSite(sspGuid))

     {

       uri = sspSite.WebApplication.GetResponseUri(SPUrlZone.Default).AbsoluteUri + "ssp/admin";

     }

     return uri;

  }

Kerberos - Pros & Cons

Pros:

1. Faster performance is experienced when using Kerberos as it caches information about the client after authentication. This means that it can perform better than NTLM particularly in large farm environments
2. Delegation - Kerberos can delegate the client credentials from the SharePoint front-end web server to other back-end servers like Oracle. So you are eliminating double hops. (Login Challenges)
3. You can also with MOSS 2007 utilize RSS feeds "Within your SharePoint Environment" 
4. Microsoft recommends to "Use Kerberos authentication for sites with a high security service level agreement."
5. Federated Search between Farms (e.g., will work based as the user credentials are passed automatically.)
6. Planning on utilizing BDC some LOB Applications will require Kerberos authentication.
7. SQL Serer Reporting Services integration works well with Kerberos.
8. Switch back to NTLM is possible.

 

Cons:

1. In Active Directory, SPN should be configured carefully .If not troubleshooting is difficult

 

Related Links:

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

http://ablog.apress.com/?p=1127

http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/de88fb8c-0101-4413-9855-34501569e077

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

 

Compiling audience object model.

Refer the community content by me at

http://msdn.microsoft.com/en-us/library/microsoft.office.server.audience.audiencemanager.aspx

MSDN Note "Compiling audiences is not supported in the object model."

Actually we can compile the audience.
Following code to compile all the audiences.
Add Reference Microsoft Search Component(Microsoft.Office.Server.Search.dll)
using Microsoft.Office.Server.Search.Administration;

using (SPSite site = new SPSite(txtSite.Text))
{
ServerContext context = ServerContext.GetContext(site);
SearchContext searchContext = SearchContext.GetContext(context);
string[] args = new string[3];
args[0] = searchContext.Name;
args[1] = "1"; //"1" = start job, "0" = stop job
args[2] = "1"; //"1" = full compilation, "0" = incremental compilation (optional, default = 0)
AudienceJob.RunAudienceJob(args);
System.Threading.Thread.Sleep(3000);
}

To Compile a specific audience, add the optional arg[3] after making the String array size to 4 and specify the Audience Name.