Configure features of an information management policy
[NOTE : Some of these features are available only with 2007 Office aplications, so please read carefully]

Site administrators may have access to all or some of the following features depending on which information management features have been enabled in Central Administration. You may also have additional custom features that have been created specifically for your organization

Open the Edit Policy page
You can access the Edit Policy page from either a site collection policy or a policy that has been added to a site content type.
Open the Edit Policy page for a site collection policy
1. On the home page of the site collection, click Site Actions, point to Site Settings, and then click Modify All Site Settings.
2. On the Site Settings page, in the Site Collection Administration section, click Site collection policies.
3. Select the policy whose features you want to configure.
Open the Edit Policy page for a content type policy
1. On the home page of the site collection, click Site Actions, point to Site Settings, and then click Modify All Site Settings.
2. On the Site Settings page, in the Galleries section, click Site content types.
3. Select the content type that the policy has been associated with, and then click Information management policy settings.
4. Click Define a policy to open the Edit Policy page for the content type.
Top of Page
Learn about the label policy feature
The label policy feature enables site administrators to create uniform labels for 2007 Microsoft Office system documents. Labels are useful for ensuring that information about document properties is attached to a document when it is printed. Item properties stored in columns, such as file name, author, creation date, status, project name, and schedule information, can be included in a label.
By default, labels are displayed in the document header; however, end users can insert a label anywhere in the document by using the Insert tab in 2007 Office release programs, such as Microsoft Office Word 2007, Microsoft Office Excel 2007, and Microsoft Office PowerPoint 2007. Labels are applied to all documents to which that policy is applied.
Policy administrators can determine the following label attributes:
 What information to include in the label, such as metadata defined in item columns as well as hard-coded text and formatting characters. Labels can contain up to ten column references, each of which can be up to 255 characters long.
 The label format, including its overall height and width, text style, font, and size, line breaks, and tabs. By default, the label height is one inch, but label height can be set from .25 to 20 inches. Label width can be from .25 to 20 inches. Label text is always vertically centered within the label image.
 Whether 2007 Office release programs prompt end users to insert a label before a document is saved or printed, or whether the label can be manually added at the discretion of the end user. Users are also able to delete a label from a document if needed.
 Whether the label content should be locked when it is first added to a document, or whether it can be updated as column information changes. Labels are only locked when all required metadata is present on the label.
Top of Page
Add labels to a policy
1. Open the Edit Policy page for the policy to which you want to add labels.
2. On the Edit Policy page, in the Labels section, click Enable labels.
3. To ensure that a label is always added to a document, select the check box Prompt users to insert a label before saving or printing.
NOTE All settings apply to the entire label. You may need to adjust either the text formatting or the label size to ensure that the text displays properly.
Clear this check box if the label policy is optional and you want end users to manually insert a label into their documents.
4. To lock a label so that it cannot be changed, even if column information changes, select the check box, Prevent changes to labels after they are added.
To allow label changes when information in the column settings changes, clear this check box.
5. In the Label Format box, type the text of the label as you want it to be displayed.
 Type the names of the columns that you want displayed in the order in which you want them to appear in the label. Enclose column names in curly braces ({ }) as shown on the page.
 If desired, you can type a column identifier outside the braces as shown in the example on the page.
 To add a line break to a label, type \n in the label box where you want the line break to appear.
 To add a tab, type \t in the label field where you want the text indented.
6. In the Appearance section, select the text formatting for the label. Be sure to use a font and font style that will be available on end-users' computers. The font size also will affect how much text can be displayed on the label.
7. In the Label Size section, type the height and width of the label. Label height can be from .25 to 20 inches long and label width can be from .25 to 20 inches wide. Label text is always vertically centered within the label image.
8. Click Refresh to preview the label content.
Make sure that your text fits into the label height and width specified. Text that is too large for the label will not be displayed.
NOTE Actual column values will not be displayed in the preview.
9. Click OK to apply the label feature to the policy.
Troubleshooting labels
To ensure that labels print correctly, check the following:
 All columns that are listed in the label format exist in the document library.
 Label content is not longer than the length of the label.
 Text formatting (such as font style) is valid. If formatting parameters are invalid or refer to fonts that don't exist on the client system, a label is created, but uses the default formatting values.
If some of the metadata values currently required for the label are not yet filled in, a notification dialog is displayed telling users that some of the metadata required for the label is missing. Users can go to the Document Information Panel to fill in the missing metadata.
Top of Page
Add event auditing to a policy
The auditing feature of site collection policy enables companies to create and analyze audit trails for their documents as well as for nondocument list items, such as task lists, issues lists, discussion groups, and calendars. The feature provides an audit log that records events, such as when content is viewed, edited, published, and so on. When auditing is enabled in a policy, policy administrators can view the audited data in Excel-based policy usage reports, which summarize current usage. You can review each report to review how information is being used within the organization. Audit log reports can help organizations verify and document regulatory compliance or investigate potential concerns.
The audit log captures the following information:
 Event name.
 Date and time of the event.
 System name of the user performing the action.
1. Open the Edit Policy page for the policy to which you want to add auditing.
2. On the Edit Policy page, in the Auditing section, select the Enable auditing check box, and then select the check boxes next to the events you want to keep an audit trail for.
3. Click OK to apply the auditing feature to the policy.
When auditing is enabled, events related to items covered by this policy will be listed in the log. To view the audit logs, on the Site Settings page, click Audit log reports, and then select the report that you have set up.
NOTE Auditing provides information on when an item is changed, but not the details of what has changed. Thus, it should not be considered as a document versioning or backup tool.
Top of Page
Add barcodes to a policy
Barcodes are particularly useful for managing physical records because they provide a way to track nondigital assets, such as printed documents, and physical items, such as products, prototypes, and computer hardware. Unlike labels, barcodes do not display information about the item, so sensitive information can be safely stored online and associated with hardcopy or physical items without disclosing the information.
When barcodes are enabled as part of a policy, they are added to document properties and displayed in the header area of the document to which the barcode is applied. Like labels, barcodes can also be manually removed from a document.
You can specify whether users should be prompted to include the barcode when printing or saving an item or if the barcode should be inserted manually using the Insert tab in 2007 Office release programs.
The barcode policy generates Code 39 standard barcodes. Each barcode image includes text below the barcode symbol that represents the barcode value. This enables the barcode data to be used even when scanning hardware is not available. Users can manually type the barcode number into the Microsoft Office SharePoint Server 2007 search box to locate the item on a site.
1. On the Edit Policy page, in the Barcodes section, select the Enable Barcodes check box.
2. To prompt users to insert these barcodes into documents, select the Prompt users to insert a barcode before saving or printing check box.
3. Click OK to apply the barcode feature to the policy.
Top of Page
Add item retention and expiration features to a policy
When enabled, the expiration policy searches the site collection to find those items that have exceeded the retention period. What happens to those items depends how your system has been set up to handle items that have exceeded their retention period. For example, items can be moved to the recycle bin, an expiration workflow can be started, or a customized process can be performed.
The expiration policy is enabled by setting both a retention period and an expiration action.
1. Open the Edit Policy page for the policy to which you want to set item retention and expiration.
2. On the Edit Policy page, select the Enable Expiration check box to establish how to dispose of content that is managed by this policy.
3. Select a retention period option to specify when documents will be set to expire. This can also be expressed in a separate workflow or a custom retention formula.
 To set the expiration date based on a date property, click A time period based on the item's properties, and then select the action and the time period (days, months, or years). Type a number in the box between the lists to define the time period.
NOTES
 When you're creating a policy as part of a content type, you can select any date property defined in that content type to use as an expiration value.
 These options are only available when you are creating a site collection policy.
 To use a workflow or custom retention formula to determine expiration, click Set programmatically.
4. Define what actions you want to happen when the document expires.
 To enable a predefined action (such as delete), click Perform this action, and then select an action from the list.
 To start an expiration workflow, click Start this workflow, and then select the name of the workflow.
NOTE This feature is only available if you are defining a policy for a content type that already has a workflow associated with it.
5. Click OK to apply the expiration feature to the policy.

Default Custom Action Locations and IDs

[From : http://msdn.microsoft.com/en-us/library/bb802730.aspx ]

The following table shows the locations, custom action group IDs and, custom action IDs that are used in the CustomAction and CustomActionGroup elements of custom actions that are installed by default in Windows SharePoint Services 3.0.

Each location value that is listed in the table corresponds to the Location attribute of CustomAction, each group ID corresponds to the GroupId attribute of CustomAction or to the Id attribute of CustomActionGroup, and each custom action ID corresponds to Id attribute of CustomAction.

You can create a Feature that implements the HideCustomAction element to hide any default custom action that is identified in the table.

Location	Custom Action Group ID	Group Description	Default Custom Action IDs
DisplayFormToolbar	N/A	Location corresponds to the display form toolbar of lists.	ExportEventToolbarButton (calendars) ExportContactToolbarButton (contacts)
EditControlBlock	N/A	Corresponds to the per-item edit control block (ECB) menu.
EditFormToolbar	N/A	Location corresponds to the edit form toolbar of lists.
Microsoft.SharePoint.Administration.ApplicationCreated	Links	Application Created page.	CreateSite HomePage
Microsoft.SharePoint.Administration.ApplicationManagement	ApplicationSecurity	Application Security section on Central Administration Application Management page.	WebPartSecurity SelfService WebApplicationSecurity ManagePolicy ManageAuthenticationProviders
Microsoft.SharePoint.Administration.ApplicationManagement	ExternalService	External Service Connections section on Central Administration Application Management page.	OfficialFile HtmlViewer DocConversion
Microsoft.SharePoint.Administration.ApplicationManagement	SiteManagement	SharePoint Site Management section on Central Administration Application Management page.	CreateSite DeleteSite SiteUse QuotaDefinition SiteQuota SiteOwners ListSiteCollections
Microsoft.SharePoint.Administration.ApplicationManagement	WebApplicationConfiguration	SharePoint Web Application Management section on Central Administration Application Management page.	Extend Unextend Delete ManagedPaths EmailSettings GeneralSettings ManageContentDatabases ManageWebAppFeatures ListWebApplications
Microsoft.SharePoint.Administration.ApplicationManagement	WorkflowManagement	Workflow Management section on Central Administration Application Management page.	WorkflowManagement
Microsoft.SharePoint.Administration.Operations	BackupRestore	Backup and Restore section on Central Administration Operations page.	Backup BackupHistory Restore BackupStatus
Microsoft.SharePoint.Administration.Operations	DataConfiguration	Data Configuration section on Central Administration Operations page.	DefaultDatabase DataRetrieval
Microsoft.SharePoint.Administration.Operations	GlobalConfiguration	Global Configuration section on Central Administration Operations page.	RunningJobs JobDefinitions AlternateAccessMappings ManageFarmFeatures Solutions
Microsoft.SharePoint.Administration.Operations	LoggingAndReporting	Logging and Reporting section on Central Administration Operations page.	DiagnosticLogging UsageAnalysis
Microsoft.SharePoint.Administration.Operations	Security	Security Configuration section on Central Administration Operations page.	ServiceAccount Irm Antivirus BlockedFileTypes AdministrationRoles
Microsoft.SharePoint.Administration.Operations	Topology	Topology and Services section on Central Administration Operations page.	FarmServers TopologyServices IncomingEmailServer ApproveDGs EmailConfiguration
Microsoft.SharePoint.Administration.Operations	Upgrade	Central Administration Operations page.	SiteUpgradeStatus FinalizeUpgrade
Microsoft.SharePoint.ContentTypeSettings	Fields	Columns section on Site Collection Content Type page.	AddField ReorderFields
Microsoft.SharePoint.ContentTypeSettings	General	Settings section on Site Collection Content Type page.	ChangeNameDescription ChangeOptionalSettings ChangeWorkflowSettings RemoveContentType
Microsoft.SharePoint.ContentTypeTemplateSettings	Fields	Columns section on List Content Type page.	AddField ReorderFields
Microsoft.SharePoint.ContentTypeTemplateSettings	General	Settings section on List Content Type page.	ChangeNameDescriptionGroup ChangeOptionalSettings ChangeWorkflowSettings RemoveContentType
Microsoft.SharePoint.Create	WebPages	Web Pages section on Create page.
Microsoft.SharePoint.GroupsPage	NewMenu	New menu on site collection People and Groups page.
Microsoft.SharePoint.GroupsPage	SettingsMenu	Settings menu on site collection People and Groups page.
Microsoft.SharePoint.ListEdit	Communications	Communications section on Customize page for list or document library.
Microsoft.SharePoint.ListEdit	GeneralSettings	General Settings section on Customize page for list.
Microsoft.SharePoint.ListEdit	Permissions	Permissions and Management section on Customize page for list or document library.
Microsoft.SharePoint.ListEdit.DocumentLibrary	GeneralSettings	General Settings section on Customize page for document library.
Microsoft.SharePoint.PeoplePage	ActionsMenu	Actions menu on site collection People and Groups page.
Microsoft.SharePoint.PeoplePage	NewMenu	New menu on site collection People and Groups page.
Microsoft.SharePoint.PeoplePage	SettingsMenu	Settings menu on site collection People and Groups page.
Microsoft.SharePoint.SiteSettings	Customization	Look and Feel section on Site Settings page.	ProjectSettings NavOptions Theme TopNav QuickLaunch SaveAsTemplate ReGhost
Microsoft.SharePoint.SiteSettings	Galleries	Galleries section on Site Settings page.	MasterPageCatalog ManageCType ManageField SiteTemplates ListTemplates WebParts Workflows
Microsoft.SharePoint.SiteSettings	SiteAdministration	Site Administration section on Site Settings page.	RegionalSettings LibrariesAndLists WebUsage UserAlerts RSS SrchVis ManageSubWebs ManageSiteFeatures DeleteWeb
Microsoft.SharePoint.SiteSettings	SiteCollectionAdmin	Site Collection Administration section on Site Settings page.	DeletedItems SiteCollectionUsage Storage ManageSiteCollectionFeatures Hierarchy Portal
Microsoft.SharePoint.SiteSettings	UsersAndPermissions	Users and Permissions section on Site Settings page.	PeopleAndGroups SiteCollectionAdministrators User
Microsoft.SharePoint.StandardMenu	ActionsMenu	Actions menu in list and document library views.
Microsoft.SharePoint.StandardMenu	ActionsMenuForSurvey	Site Actions menu for surveys.
Microsoft.SharePoint.StandardMenu	NewMenu	New menu in list and document library views.
Microsoft.SharePoint.StandardMenu	SettingsMenu	Settings menu in list and document library views.
Microsoft.SharePoint.StandardMenu	SettingsMenuForSurvey	Site Settings links for surveys.
Microsoft.SharePoint.StandardMenu	SiteActions	Site Actions menu.
Microsoft.SharePoint.StandardMenu	UploadMenu	Upload menu in document library views.
Microsoft.SharePoint.User	ActionsMenu	Actions menu on Web site Permissions page.
Microsoft.SharePoint.User	NewMenu	New menu on Web site Permissions page.
Microsoft.SharePoint.User	SettingsMenu	Settings menu on Web site Permissions page.
Microsoft.SharePoint.Workflows	LeftNavBarLinks	Left navigational area on pages for managing workflow.
NewFormToolbar	N/A	Location corresponds to the new form toolbar of lists.
ViewToolbar	N/A	Location corresponds to the toolbar in list views.

Sharepoint - Challenges
Ready to turn off your File Servers?
SharePoint is great as a DMS, ECM, RMS – but I would not go as far as to suggest that you should move all of your files off your file servers and put it into SharePoint.
When storing content in SharePoint you are using SQL storage space. This generally means more fault tolerant disks, possibly a SAN in many cases. Your file servers may be using a more economical form of storage. So consider what content is worthwhile moving to SharePoint and what should remain.
In addition, there are some files that don’t benefit from the SharePoint storage features such as installation media. Other very large files such as videos and virtual machine images are not suited for SharePoint storage.
Easy to view external data, not update
While you can very quickly implement a solution in SharePoint to view information from many systems, it is not so quick to implement a user interface to update information that does not live within SharePoint. It’s still possible, but you will either have to install 3rd party web parts or develop your own
Think about your data structures
For content that you are going to store in SharePoint, you need to put some fore-thought into how you are going to structure it. You cannot treat a SharePoint list in the same way as you would a database table. Concepts like referential integrity are not supported by lists. You also have to determine the best way to scale up your data requirements. If you are going to be handling large numbers of items, you may want to split them across different lists, sites or content databases
Not designed as an OLTP System
The needs of an Online Transaction Processing System are very different to those of a document management and collaboration system. If you are looking to implement a solution that is going to have to process a large number of concurrent transactions, you should be considering other platforms in your Enterprise Architecture
High-end Digital Asset Management
As we mentioned in our discussion on File Servers, SharePoint does not handle large files particularly well, and when we get up to the high end digital asset management, we are dealing with files in the 100s of megabytes. SharePoint does have the Image Library out-of-the-box for basic image management needs today. Microsoft have also announced the Interactive Media Manager which will be built on the MOSS platform
Software Development Lifecycle
Finally, when your developers do start working on the SharePoint platform, there are a few things you should be aware of. SharePoint only runs on Windows Server 2003. This means that developers will either run a VPC or a development PC with Windows 03.
Deploying changes between Dev, Test and Production environments needs to be thought through in advance. Certain changes can be easily deployed using features. However, configuration changes can be more difficult to track, especially if you cannot simply backup and restore.
Customizing the look and feel has improved a lot since the previous version. However, it is still not straighforward, and your designers are going to need to get familiar with the process and limitations.

Performance issues with using all front-end Web servers for crawling
Crawling content in your farm places a heavy load on the front-end Web servers. This tends to cause spikes and surges in network traffic, and is CPU and memory intensive. Crawling content in your farm can potentially cause more traffic on the network than user requests. This network traffic can negatively impact the performance of all front-end Web servers in your server farm, and thereby impact end-user's requests for content from your SharePoint sites.
Recommended solution
We recommend that you use a dedicated front-end Web server for crawling, especially if you are crawling a server farm that contains more than 500 gigabytes (GB) of content.
Note:
You can specify any front-end Web server in your farm that is not part of a network load balanced cluster as a dedicated front-end Web server for crawling.
For best performance, we recommend that you configure the index server as the dedicated front-end Web server for crawling if your index server has the memory capacity for both roles. By using the same server as both the index server and dedicated front-end Web server, you eliminate the need for the index server to send requests to a different server when crawling content. Consequently, you boost crawl performance and reduce the overall traffic on the network. If this is not possible, you can use a different server in your server farm.
Note:
You cannot configure earlier versions of SharePoint Products and Technologies to use a dedicated front-end Web server and index server on the same computer.
We recommend that you do not include the dedicated front-end Web server in the network load balancing rotation for incoming user requests. Otherwise, user requests that the network load balancer directs to the dedicated front-end Web server for crawling will be subjected to inconsistent performance, as described earlier in this article.
When not to configure a dedicated front-end Web server for crawling
Do not configure a dedicated front-end Web server for crawling if the any of the following conditions exist:
· Another application is running on the index server. Doing so might mean that those applications (such as the Excel Calculation service) can no longer communicate with other servers in the farm.
If other applications are running on the index server, you must first move those applications to another application server before configuring a dedicated front-end Web server for crawling.· The index server is not also the query server. Configuring a dedicated front-end Web server for crawling can disable the index server's ability to propagate the index to another server.

Preparing to crawl content (Office SharePoint Server 2007)
After new sources of content that you need to crawl have been identified, you must make the necessary preparations before you are ready to crawl that content. Preparing to crawl content includes the following tasks:
· Add a content source for search (Office SharePoint Server). You use content sources to specify what content to crawl.
· Install IFilters (Office SharePoint Server 2007). Ensure that the required IFilters are installed on the index server. Microsoft Office SharePoint Server 2007 uses IFilters to open and read the content that is crawled so that it can be indexed.
· Install protocol handlers (Office SharePoint Server). Ensure that the protocol handlers that are required to access the content specified in the content sources are installed on the index server.
· Configure proxy server settings for search (Office SharePoint Server 2007). Ensure that you make any proxy server setting changes that are necessary to crawl the new content. For example, you might specify that the proxy server should not be used to access some addresses in your content sources.
· Configure SSL certificate warning (Office SharePoint Server 2007). Verify whether Office SharePoint Server 2007 should ignore Secure Sockets Layer (SSL) certificate name warnings. If you are using the HTTPS protocol to crawl content and you know that the SSL certificate name does not exactly match the name that is expected, you can choose to turn off these warnings.
· Change the contact e-mail address (Office SharePoint Server 2007). Ensure that administrators of crawled servers can reach the search administrator by supplying a contact e-mail address that is highly available.
· Manage crawler impact rules (Office SharePoint Server 2007). Manage the impact that crawling has on the servers being crawled. · Specify timeout settings (Office SharePoint Server 2007). Make any necessary changes to the time-out settings to compensate for the speed at which the servers you want to crawl can serve content requests.

List of Out of Box (OOB) Site Templates
You can import sites only into sites that are based on the same template as the exported site.
A bit of MSDN searching yielded this forum thread, where someone was kind enough to provide a code snippet and output that listed out all the default templates.

Template ID = 0 Desc: This template is used for initializing a new site. Title: Global template Name: GLOBAL#0
Template ID = 1 Desc: A site for teams to quickly organize, author, and share information. It provides a document library, and lists for managing announcements, calendar items, tasks, and discussions. Title: Team Site Name: STS#0
Template ID = 1 Desc: A blank site for you to customize based on your requirements. Title: Blank Site Name: STS#1
Template ID = 1 Desc: A site for colleagues to work together on a document. It provides a document library for storing the primary document and supporting files, a tasks list for assigning to-do items, and a links list for resources related to the document. Title: Document Workspace Name: STS#2
Template ID = 2 Desc: A site to plan, organize, and capture the results of a meeting. It provides lists for managing the agenda, meeting attendees, and documents. Title: Basic Meeting Workspace Name: MPS#0
Template ID = 2 Desc: A blank meeting site for you to customize based on your requirements. Title: Blank Meeting Workspace Name: MPS#1
Template ID = 2 Desc: A site for meetings that track status or make decisions. It provides lists for creating tasks, storing documents, and recording decisions. Title: Decision Meeting Workspace Name: MPS#2
Template ID = 2 Desc: A site to plan social occasions. It provides lists for tracking attendees, providing directions, and storing pictures of the event. Title: Social Meeting Workspace Name: MPS#3
Template ID = 2 Desc: A site to plan, organize, and capture the results of a meeting. It provides lists for managing the agenda and meeting attendees in addition to two blank pages for you to customize based on your requirements. Title: Multipage Meeting Workspace Name: MPS#4
Template ID = 3 Desc: A site for central administration. It provides Web pages and links for application and operations management. Title: Central Admin Site Name: CENTRALADMIN#0
Template ID = 4 Desc: A site for a community to brainstorm and share ideas. It provides Web pages that can be quickly edited to record information and then linked together through keywords Title: Wiki Site Name: WIKI#0
Template ID = 9 Desc: A site for a person or team to post ideas, observations, and expertise that site visitors can comment on. Title: Blog Name: BLOG#0
Template ID = 7 Desc: A site to centrally manage documents in your enterprise. Title: Document Center Name: BDR#0
Template ID = 14483 Desc: This template creates a site designed for records management. Records managers can configure the routing table to direct incoming files to specific locations. The site prevents records from being modified after they are added to the repository. Title: Records Center Name: OFFILE#0
Template ID = 14483 Desc: This template creates a site designed for records management. Records managers can configure the routing table to direct incoming files to specific locations. The site prevents records from being modified after they are added to the repository. Title: Records Center Name: OFFILE#1
Template ID = 40 Desc: This template creates a site for administering shared services Title: Shared Services Administration Site Name: OSRV#0
Template ID = 20 Desc: This template is obsolete. Title: SharePoint Portal Server Site Name: SPS#0
Template ID = 21 Desc: This web template defines a Personal Space for an individual participating on a SharePoint Portal. Title: SharePoint Portal Server Personal Space Name: SPSPERS#0
Template ID = 22 Desc: A site for delivering personalized views, data, and navigation from this site collection into My Site. It includes personalization specific Web Parts and navigation that is optimized for My Site sites. Title: Personalization Site Name: SPSMSITE#0
Template ID = 30 Desc: This template is obsolete. Title: Contents area Template Name: SPSTOC#0
Template ID = 31 Desc: This template is obsolete. Title: Topic area template Name: SPSTOPIC#0
Template ID = 32 Desc: This template is obsolete. Title: News Site Name: SPSNEWS#0
Template ID = 39 Desc: A blank site for expanding your Web site and quickly publishing Web pages. Contributors can work on draft versions of pages and publish them to make them visible to readers. The site includes document and image libraries for storing Web publishing assets. Title: Publishing Site Name: CMSPUBLISHING#0
Template ID = 53 Desc: This template creates a site for publishing Web pages on a schedule, with workflow features enabled. By default, only Publishing subsites can be created under this site. A Document and Picture Library are included for storing Web publishing assets. Title: Publishing Site Name: BLANKINTERNET#0
Template ID = 53 Desc: This template creates the Press Releases subsite for an Internet-facing corporate presence website. Title: Press Releases Site Name: BLANKINTERNET#1
Template ID = 53 Desc: A site for publishing Web pages on a schedule by using approval workflows. It includes document and image libraries for storing Web publishing assets. By default, only sites with this template can be created under this site. Title: Publishing Site with Workflow Name: BLANKINTERNET#2
Template ID = 33 Desc: A site for publishing news articles and links to news articles. It includes a sample news page and an archive for storing older news items. Title: News Site Name: SPSNHOME#0
Template ID = 34 Desc: A site for listing and categorizing important sites in your organization. It includes different views for categorized sites, top sites, and a site map. Title: Site Directory Name: SPSSITES#0
Template ID = 36 Desc: This template is obsolete. Title: Community area template Name: SPSCOMMU#0
Template ID = 38 Desc: A site for creating, managing, and delivering Web pages, dashboards, and key performance indicators that communicate metrics, goals, and business intelligence information. Title: Report Center Name: SPSREPORTCENTER#0
Template ID = 47 Desc: A starter site hierarchy for an intranet divisional portal. It includes a home page, a News site, a Site Directory, a Document Center, and a Search Center with Tabs. Typically, this site has nearly as many contributors as readers and is used to host team sites. Title: Collaboration Portal Name: SPSPORTAL#0
Template ID = 50 Desc: A site for delivering the search experience. The welcome page includes a search box with two tabs: one for general searches, and another for searches for information about people. You can add and customize tabs to focus on other search scopes or result types. Title: Search Center with Tabs Name: SRCHCEN#0
Template ID = 51 Desc: This template creates a profile site that includes page layout with zones Title: Profiles Name: PROFILES#0
Template ID = 52 Desc: A starter site hierarchy for an Internet-facing site or a large intranet portal. This site can be customized easily with distinctive branding. It includes a home page, a sample press releases subsite, a Search Center, and a login page. Typically, this site has many more readers than contributors, and it is used to publish Web pages with approval workflows. Title: Publishing Portal Name: BLANKINTERNETCONTAINER#0
Template ID = 54 Desc: A site used for hosting personal sites (My Sites) and the public People Profile page. This template needs to be provisioned only once per Shared Service Provider, please consult the documentation for details. Title: My Site Host Name: SPSMSITEHOST#0
Template ID = 90 Desc: A site for delivering the search experience. The site includes pages for search results and advanced searches. Title: Search Center Name: SRCHCENTERLITE#0
Template ID = 90 Desc: The Search Center template creates pages dedicated to search. The main welcome page features a simple search box in the center of the page. The template includes a search results and an advanced search page. This Search Center will not appear in navigation. Title: Search Center Name: SRCHCENTERLITE#1

So now you have a handy reference. You can find the code that was used to generate this at Crate site collection and specify a Particular Template - MSDN Forums, but I'll include it here for convenience:
SPSite siteCollection = new SPSite(parentURL))
SPWeb parentWeb = siteCollection.OpenWeb();
SPWebTemplateCollection Templates = siteCollection.GetWebTemplates(Convert.ToUInt32(LOCALE_ID_ENGLISH));
foreach (SPWebTemplate temp in Templates)
{
Logger.Logger.log(
@"Template ID = " + temp.ID + Environment.NewLine +
" Desc: " + temp.Description + Environment.NewLine +
" Title: " + temp.Title + Environment.NewLine +
" Name: " + temp.Name);
}

Determine how to handle customizations (Office SharePoint Server)
If you have extensively customized your Microsoft® SharePoint® Portal Server 2003 sites (by using Microsoft Office FrontPage® 2003), you need to determine how you want to handle your customized sites when you upgrade. Your approach will vary based on the extent of the customizations, the complexity of your site, and your goals for upgrading. You can choose to:
1. Keep the customizations While this approach allows you to keep the same look and feel, you won't be able to take advantage of the new capabilities available in the new version. If you really want to keep your pages looking just as they did, there are three ways to keep the customizations:
· Do an in-place upgrade.
By default, an in-place upgrade preserves customizations and does not reset to the site definition. Some controls, such as the Site Actions menu, may not be available in your upgraded site.
· Do a gradual upgrade, and keep the site in the previous version environment (do not upgrade the site).
This maintains the site exactly as it is, with the previous version functionality only. This is usually a short-term solution, as most organizations do not want to support both versions over the long term.
· Do a gradual upgrade and upgrade the site, but don't reset any pages to the site definition.
This approach might result in an uneven look if you didn't customize every page. Customized pages retain the previous version's look and functionality, while uncustomized pages have the new version's look and functionality. Some controls, such as the Site Actions menu, may not be available in your customized pages.
Note
By default, custom pages are kept as is after upgrade (except for themes).
2. Throw out the customizations If you are planning a complete site redesign, or if you are significantly changing the information architecture, then the upgrade is your chance to start over with a new look or a new organization. There are two ways to throw out your customizations and start with a fresh site:
· Go ahead and upgrade (either in-place or gradual), and reset all pages to use the default pages from the site definition. For an in-place upgrade, after upgrading, use Microsoft Office SharePoint Designer 2007 to reattach the default page layouts. For a gradual upgrade, use the upgrade option to reset the entire Web site to use the site definition pages.
With this approach, you can start with the new look and functionality, and then decide whether or not to customize the site again. Site owners can reapply customizations when they review the upgraded sites.
Note
If you have added a completely custom page to your site (for example, if you replaced default.aspx with a completely different file rather than making changes to the existing default.aspx file), that page has no association with the site definition and therefore it cannot be reattached to the page layout. If you want your custom page to have the same look and feel as the other pages in your site, consider creating a new page based on the site definition and transferring your content to that new page.
· Start fresh with a new site in the new environment.
This approach works when you're dramatically redesigning your site and do not need to have either the structure or most of the content in the new site. Create a brand-new site, create a new site design, and transfer your content into the new site. This is not an upgrade path, but rather an opportunity to design your new site from scratch.
3. Redo the customizations This approach allows you to take advantage of the new capabilities, modify your design slightly if desired, and move to a more manageable design. You can take advantage of the new Master Pages model to apply your design, rather than customizing each individual page. Converting the customized landing pages to use page layouts instead also cuts down on future maintenance costs, because you can simply change the page layouts rather than each individual page. There are three ways to redo the customizations:
· Do an in-place or gradual upgrade and do not reset the pages to the site definition version. After upgrade, modify the appropriate master pages and page layouts in the upgraded site to take on the previous version's look and feel, and then reattach the page layouts to all customized pages. This gives all formerly customized landing pages the same look as the un-upgraded site. You can incorporate the new controls, such as the Site Actions menu, into your new page layouts as part of this work.
· Do an in-place upgrade and do not reset the pages to the site definition. After upgrade, open the site and copy the customizations, then reattach the page layouts and reapply your customizations to the master pages and page layouts as appropriate.
By default, an in-place upgrade preserves customizations and does not reset the pages to the site definition version. When you open the site by using a Web page editor compatible with Microsoft Office SharePoint Server 2007, such as Office SharePoint Designer 2007, you can copy the customizations and then reset the original pages to get the new functionality. Then you can reapply any customizations to the master pages and page layouts that still make sense. Doing this process with an in-place upgrade is somewhat complicated because you need to copy the customized pages before resetting them. Consider using the gradual upgrade method below instead.
Note
When you perform an in-place upgrade, it does not preserve the previous version of the site. If you want to be able to have the previous version and the new version of the site side by side so you can transfer customizations from the previous version site to the new version site, use a gradual upgrade — or, if you are performing an in-place upgrade, be sure you have a mirrored server or server farm that is running the previous version.
· Do a gradual upgrade and, in the upgraded site, reattach the page layouts. Then transfer the customizations from your original site to the master pages and page layouts in the upgraded site by using Office SharePoint Designer 2007.
This option provides you with the most flexibility. Because you can refer to the original site, you can see exactly how you did the previous customizations. And because you reattached the page layouts, you can see the new functionality and decide which customizations to reapply to the master pages and page layouts and which to ignore.
Note
Again, not all custom pages have an equivalent page in the site definition, so reattaching the page layouts will not work for truly custom pages. If you want your custom pages to have the same look and feel as the other pages in your site, consider creating a new page based on the site definition and transferring your content to that new page.
For more information about reapplying customizations after upgrade, see Reapply customizations in the browser and Microsoft Office SharePoint Designer 2007.
Worksheet
Record any customized site definitions or page templates you are using in the Custom templates and mapping files worksheet (http://go.microsoft.com/fwlink/?LinkId=73751&clcid=0x409).

Building and implementing enterprise search solutions

The following 14 recorded presentations are based on training modules from three-day, in-person training sessions. The presentations provide details about key enterprise search capabilities in Microsoft Office SharePoint Server 2007. Additionally, the presentations provide guidance about how to combine SharePoint products and technologies in order to build, implement, and manage enterprise search solutions.

Module 1: Workshop Overview (http://go.microsoft.com/fwlink/?LinkId=115635&clcid=0x409)
Module 2: Enterprise Search Overview (http://go.microsoft.com/fwlink/?LinkId=115636&clcid=0x409)
Module 3: SharePoint Search 2007 Walkthrough (http://go.microsoft.com/fwlink/?LinkId=115637&clcid=0x409)
Module 4: Search Architecture and Deployment Scenarios (http://go.microsoft.com/fwlink/?LinkId=115638&clcid=0x409)
Module 5: Crawl and Query Processes (http://go.microsoft.com/fwlink/?LinkId=115639&clcid=0x409)
Module 6: Relevance Ranking (http://go.microsoft.com/fwlink/?LinkId=115640&clcid=0x409)
Module 7: Customizing the End-User Experience (http://go.microsoft.com/fwlink/?LinkId=115641&clcid=0x409)
Module 8: Developing Search Solutions (http://go.microsoft.com/fwlink/?LinkId=115642&clcid=0x409)
Module 9: Business Data Catalog Search (http://go.microsoft.com/fwlink/?LinkId=115643&clcid=0x409)
Module 10: Extensibility and Integration for Search (http://go.microsoft.com/fwlink/?LinkId=115644&clcid=0x409)
Module 11: Search Administration (http://go.microsoft.com/fwlink/?LinkId=115646&clcid=0x409)
Module 12: Security for Search (http://go.microsoft.com/fwlink/?LinkId=115647&clcid=0x409)
Module 13: Performance Scalability and Capacity Planning for Search (http://go.microsoft.com/fwlink/?LinkId=115648&clcid=0x409)
Module 14: Search Operations (http://go.microsoft.com/fwlink/?LinkId=115649&clcid=0x409)

Get SharePoint training on your desktop
Explore Office SharePoint Server 2007 with training from Microsoft experts, right from your desktop. Download a simple file to get the grand tour of the latest features and changes, including automated workflows to track approval cycles, business dashboards showing how well you are performing on your goals, and syncing documents to Outlook. The training, which includes articles, videos, and interactive tutorials, will lead you step-by-step through the rich features of Office SharePoint Server.
We offer two training editions. If you just want to view the training on your desktop, then download our Standalone Edition. After you install the training, you’ll see an icon on your desktop that will make it easy to find the training when you need it.
For our Portal Edition, you’ll need to enlist the help of your friendly IT team. They can install it on your company’s Office SharePoint Server 2007 site. Then they can even track who has used the training, and what trainings they’ve taken.

Download now :

Install on your desktop
Deploy on your SharePoint Server

Using business intelligence features

Roadmap to business intelligence features of SharePoint Server 2007

Introduction to Business Intelligence features

Introduction to business intelligence in SharePoint Server 2007

Connect a Filter Web Part to a Data View Web Part

Demo: Add KPIs to your SharePoint site

Demo: Display KPIs in a dashboard

Blueprint for using data in SharePoint Server

Connect a Filter Web Part to a List View Web Part

Introduction to the Report Center

Connect a Query String (URL) Filter Web Part to another Web Part

An overview of integrating SQL Server Reporting Services with the Report Center

Watch this: Find just the data you need by using Filter Web Parts in a dashboard

Use the Filter Actions Web Part

Demo: Make better business decisions with reports and dashboards

Working with a Report Center site

Publish a report to the Report Center

Share Excel 2007 workbooks as interactive reports

Share Excel 2007 worksheets and KPIs by using dashboards

Add a report to a dashboard

Show or hide dashboard pages in a report library

Work with filter Web Parts

Create and publish Key Performance Indicators (KPIs)

Share and manage connections to external data

Introduction to information management policies

Organizations can define and use information management policies on Microsoft Office SharePoint Server 2007 sites to enforce compliance with corporate business processes or legal or governmental regulations for the management of information. Information management policies enable site administrators or list managers to control how content is managed.
In this article
What is an information management policy?
How information management policies can be used in a site

What is an information management policy?
An information management policy is a set of rules for a type of content. Information management policies enable organizations to control and track things like how long content is retained or what actions users can take with that content. Information management policies can help organizations comply with legal or governmental regulations, or they can simply enforce internal business processes. For example, an organization that must follow government regulations requiring that they demonstrate "adequate controls" of their financial statements might create one or more information management policies that audit specific actions in the authoring and approval process for all documents related to financial filings.
Policy features included in Office SharePoint Server 2007
Each individual rule within an information management policy is a policy feature. Office SharePoint Server 2007 includes several predefined policy features that organizations can use individually or in combination to define information management policies for their sites. The policy features included in Office SharePoint Server 2007 are:
Auditing The Auditing policy feature helps organizations analyze how their content management systems are used by logging events and operations that are performed on documents and list items. Organizations can configure the Auditing policy feature to log events such as when a document or item is edited, viewed, checked in, checked out, deleted, or has its permissions changed. All of the audit information is stored in a single audit log on the server, and site administrators can run reports on it. Organizations can also use the Office SharePoint Server 2007 Object Model to write and add custom events to the audit log.
Expiration The Expiration policy feature helps organizations delete or remove out-of-date content from their sites in a consistent, trackable way. This policy feature helps organizations manage both the cost and risk associated with retaining out-of-date content. Organizations can configure an Expiration policy to specify that certain types of content expire on a particular date or within a calculated amount of time after some document activity (such as creating or editing).
Barcodes The Barcodes policy feature enables organizations to track physical copies of documents or list items that have been printed from a site. The Barcode policy feature creates a unique identifier value for a document. Users can then insert a barcode image of that value into the Microsoft Office documents they create. They can also use a barcode on a physical copy of a document to search for the original copy of that document on the server. By default, barcodes are compliant with the common Code 39 standard (ANSI/AIM BC1-1995, Code 39). Organizations can use the Office SharePoint Server 2007 Object Model to install other barcode providers.
Labels The Labels policy feature also enables organizations to track physical copies of documents or list items that have been printed from a site. The Labels policy feature automatically generates text labels based on document properties and formatting that a site administrator or list manager specifies. When users insert labels into Microsoft Office documents, the labels are updated automatically with the information from the document's properties.
Top of Page
Custom policy features
Organizations can also create and deploy custom policy features to meet specific needs. For example, a manufacturing organization might want to define an information management policy for all draft product design specification documents that prohibits users from printing copies of these documents on nonsecure printers. To define this kind of information management policy, the organization can create and deploy a Printing Restriction policy feature that can be added to the relevant information management policy for the product design specification content type.
Top of Page
Information management policy integration with 2007 Microsoft Office system programs
There are a couple of ways that Office SharePoint Server 2007 information management policies can be exposed to users within the 2007 Office release client programs. When you configure an information management policy on the server for a specific content type, list, or library, you can write a policy statement that is displayed to users who work with the content that is subject to this policy. The policy statement can inform users that the information management policies are enforced for the document, or it can provide detailed information, such as the fact that a document expires after a certain period of time. When users open documents that are subject to information management policies in one of the 2007 Office release client programs, this policy statement is displayed. Additionally, if an information management policy includes the Barcode or Label policy feature, the policy can be configured to require users to insert barcodes or labels into Microsoft Office documents when they try to save or print them from an 2007 Office release client program.
Top of Page
How information management policies can be used on a site
To implement an information management policy, you must add it to a list, library, or content type on a site. The locations where you either create or add an information management policy affect how broadly the policy applies or how broadly it can be used. You can:
Create a site collection policy and then add this policy to a content type, list, or library You can create a site collection policy in the Site Collection Policies list for the top-level site in a site collection. After you create a site collection policy, you can export it so that site administrators of other site collections can import it into their Site Collection Policies list. Creating an exportable site collection policy enables you to standardize the information management policies across the sites in your organization.
When you add a site collection policy to a site content type, and an instance of that site content type is added to a list or library, the owner of that list or library cannot modify the site collection policy for the list or library. Adding a site collection policy to a site content type is a good way to ensure that site collection policies are enforced at each level of your site hierarchy.
For more information, see Create an information management policy for a site collection.
Create an information management policy for a site content type in the top-level site's Site Content Type Gallery, and then add that content type to one or more lists or libraries You can also create an information management policy directly for a site content type and then associate an instance of that site content type with multiple lists or libraries. If you create an information management policy by using this method, every item in the site collection of that content type or a content type that inherits from that content type has the policy. If you create an information management policy directly for a site content type, it is more difficult to reuse this information management policy in other site collections, because policies that are created this way cannot be exported.
Note To control which policies are used in a site collection, site collection administrators can disable the ability to set policy features directly on a content type. When this restriction is in effect, users who create content types are limited to selecting policies from the Site Collection Policies list.
For information about creating an information management policy for a site content type, see Change a site content type.
Create an information management policy for a list or library If your organization needs to apply a specific information management policy to a very limited set of content, you can create an information management policy that applies only to an individual list or library. This method of creating an information management policy is the least flexible, because the policy applies only to one location, and it cannot be exported or reused for other locations. However, some organizations may need to create unique information management policies with limited applicability to address specific situations.
Notes
You can create an information management policy for a list or library only if that list or library does not support multiple content types. If a list or library supports multiple content types, you need to define an information management policy for each individual list content type that is associated with that list or library. (Instances of a site content type that are associated with a specific list or library are known as list content types.)
To control which policies are used in a site collection, site collection administrators can disable the ability to set policy features directly on a list or library. When this restriction is in effect, users who manage lists or libraries are limited to selecting policies from the Site Collection Policies list.