make data from SharePoint libraries and list available in WSRP format

Here is the toolkit which makes this possible.
http://code.msdn.microsoft.com/WSRPToolkit

Very often in project with integration is crucial, WSRP capability is asked for. Personally i experienced this with government projects.

new logical architecture documentation on technet

Here is a solution using vairous Microsoft technologies.

The Blatchington Mill School IT environment includes separate and dedicated server hardware for Microsoft Office SharePoint Server 2007 (single server), streaming media, Management Information Server, and Microsoft Exchange Server. Additionally, the school uses Microsoft Internet Security and Acceleration Server (ISA) 2006 for its firewall.

Using scripts to automate SharePoint Server 2007 installation

Here is good resource for using scripting for deploying SharePoint components for farm deployments.

http://go.microsoft.com/fwlink/?LinkID=135694&clcid=0x409

White paper: Protecting Office SharePoint Server 2007 by using System Center Data Protection Manager

White paper: Protecting Office SharePoint Server 2007 by using System Center Data Protection Manager

This downloadable white paper compares Microsoft System Center Data Protection Manager to the backup and recovery functionality built in to Microsoft Office SharePoint Server 2007, provides an overview of types of System Center Data Protection Manager backups, and provides detailed instructions for the following recovery scenarios:

• Farm recovery
• Site recovery
• Item recovery

Site Templates vs Site Definition

There was a long discussion on the LinkedIn groups about Site Definitions vs Site Templates.

Here is a URL which is from a MS escalation engineer about Microsoft's stand on Site Templates.
http://blogs.technet.com/stefan_gossner/archive/2007/09/19/save-site-as-template-option-and-the-publishing-feature.aspx

3rd party reporting for SharePoint

http://blogs.msdn.com/sharepoint/archive/2008/12/04/how-we-did-it-nintex-reporting.aspx

DPM 2007 and SharePoint

I have been working with DPM 2007 and protecting a WSS/MOSS installation. Had to learn the hardway is getting hotfixes and services setup correctly. Some DPM documentations on TechNet did not help much.

Finally here is a good write up on DPM's relationship with WSS 3.0/MOSS 2007. http://sharepoint.microsoft.com/blogs/fromthefield/Lists/Posts/Post.aspx?List=0ce77946%2D1e45%2D4b43%2D8c74%2D21963e64d4e1&ID=69

Still i am dealing with an issue of DPM failing to backup metadata catalog and hence won't be able to perform item level recoveries. (above)

Move site collections to a new database (split a content database) (Windows SharePoint Services 3.0)

Here is some information of doing WSS 3.0/MOSS 2007 content db management.

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

i have also copied the content below just incase that link is not available.
=====================================================
Some site collections within a database that hosts multiple site collections are growing faster than expected, and you expect the database to approach its size limit quickly. You can split the database to move the growing site collections to another database or to another server.

Split a content database
You can use this procedure to split a content database that is associated with your site collections. The process of moving a site collection between databases consists of exporting the site collection URL data to a file and then importing the data to a new database.

Important:
Before you use the Stsadm mergecontentdbs operation, make sure that there is free space available on the hard disk that is equivalent to at least three times the size of the source site collection. To determine the size of your site collection, refer to the StorageUsedMB attribute of the Stsadm enumsites operation in step 2 of the following procedure.

Important:
The account used to restore the databases must be a member of the Administrators group on the local computer to complete the following procedure.


Split a content database (move a site collection to a different database)
At a command prompt on the drive where SharePoint Products and Technologies is installed, change to the following directory:

%COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin

Type the following command, and then press ENTER:
Stsadm -o enumsites -url > .xml

where url is the address of the Web application that contains the site collection that you want to move, and path/file name is the name of the XML file that you want to create with the site collection data.

For more information, see Enumsites: Stsadm operation (Windows SharePoint Services).

The previous step creates an XML file that contains all of the site collection URLs in the current database.

Open the XML file that you created in a text editing application. If there are any URLs for site collections that you do not want to move, be sure to delete them from the file. The only URLs that should remain in the XML file should be for the site collections that you want to move.

Note:
There is no need to change the site count or any of the other site collection information in the file. Only the URLs are relevant to this procedure.


Type the following command, and then press ENTER:
Stsadm -o mergecontentdbs -url -sourcedatabasename -destinationdatabasename -operation 3 -filename

where url is the address of the Web application that contains the site collection that you want; sourcedatabasename is the name of the database that you want to move the site collection from; destinationdatabasename is the name of the database that you want to move the site collection to; operation 3 is the “Read from file” operation; and file name is the name of the file that contains the site collection URLs that you want to move.

For more information, see Mergecontentdbs: Stsadm operation (Windows SharePoint Services).

Restart IIS by typing the following command, and then pressing ENTER:
iisreset /noforce

All you need to know to deploy software updates (hotifx, patch) to SharePoint 2007

Installing software updates for WSS 3.0 is not like installing on a Window Server role. For one, all the servers in a WSS 3.0 needs to be in sync with the latest binary changes that an update may have.

Even in a single server applying a hotfix involves other tasks like executing the Configuration Wizard.
http://technet.microsoft.com/en-us/library/cc288269.aspx

Training videos on SharePoint's BI feature

http://office.microsoft.com/en-us/sharepointserver/HA102824571033.aspx?pid=CH101785431033

BT involved in the SPK Kit Open Source project

BT is involved as an early adopter in the SharePoint Prodcasting Kit Open Source project.
http://blogs.msdn.com/sharepoint/archive/2008/06/10/announcing-open-source-podcasting-kit-for-sharepoint-the-power-of-social-media-for-the-enterprise.aspx

The evaluation version of Microsoft Office SharePoint Server 2007 for this server has expired

Here is a fix for the above problem from my buddy Murthy, as we work on a SharePoint migration/implementation.
--

This issue happened when I try to access the Mysite (web application) pages or any pages in the SSP admin web application.
There is no issue in accessing the Team sites, it is working fine.

Hmm, Strange Error made me to explore
The windows event log
Sharepoint log
SQL server log
Etc etc…

Many articles suggests different solution and one is as below

http://blogs.msdn.com/joelo/archive/2008/01/02/evaluation-version-expired-but-not-really.aspx
http://mosschampions.com/blogs/moss/archive/2006/11/02/False-Expiry-messages-in-SharePoint.aspx


RESOLUTION: We gave group WSS_WPG Read permissions to following registry key HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Office Server\12.0 We gave group WSS_ADMIN_WPG Full permissions to the same registry key HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Office Server\12.0 We added application pool Account ("dcomcnfg.exe") to the Distributed users We rebooted the server

No Use with all those solutions.

Then I did Uninstall MOSS, and reconfigured the whole farm again, still got the issue.

Spent the whole day, finally I got one article says peculiar solution to this problem, it worked for me too.

Here is the link to the article https://blogs.pointbridge.com/Blogs/ayyapusetty_raja/Pages/Post.aspx?_ID=10

Here is the solution, Believe it


The evaluation version of Microsoft Office SharePoint Server 2007 for this server has expired
By: Raja Ayyapusetty Posted: November 22, 2007 at 1:24 PM
Add Comment Share It Category: SharePoint Server

Definitely not the message you want to see after paying a whole lot of bucks. This happened to a colleague of mine when he tried to setup "My Sites". In fact, same error message was thrown whenever he tried to use any feature of "MOSS Enterprise".
After opening MS ticket and much debugging, here is the solution:
Open the associated web.config
Make any change and undo it
Save the web.config
Believe it or not that is your solution. Hope this helps to somebody.


Regards
Murthy

MOSS Faceted Search

Ever wanted to customize search results ? Look here first.
http://www.codeplex.com/FacetedSearch

Also there is the MSPress book, Inside the Index and Search Engines Microsoft Office SharePoint Server 2007 by by Patrick Tisseghem and Lars Fastrup.

Also some good development references on SharePoint and WSS for understanding the SDK

Using Federated Search in Geographic Environments

SharePoint 2007 document teams blog.
http://blogs.technet.com/tothesharepoint/archive/2008/07/18/3090988.aspx

Deploying Microsoft Office SharePoint Server 2007 geographically

This is a very good read for geographically dispersed MOSS 2007 deployments.

http://blogs.msdn.com/sharepoint/archive/2008/02/22/deploying-microsoft-office-sharepoint-server-2007-geographically.aspx

SharePoint Server 2007 Powers Beijing 2008 Olympic Games

http://blogs.msdn.com/sharepoint/archive/2008/08/06/sharepoint-server-2007-powers-beijing-2008-olympic-games.aspx

The case study is here: http://www.microsoft.com/casestudies/casestudy.aspx?casestudyid=4000002332

The SharePoint IT Pro documentation team has a blog.

What are their main goals in having the blog:

Help you find relevant and/or new content on TechNet
Highlight product features and associated content
Let you know when we make major updates to a content area
Preview content for new releases as early as we can (even before we publish it on the TechNet Library)

New Updates Resources Center for SharePoint

There is now Updates Resource Center for SharePoint Products and Technologies on TechNet.

Here is the link: http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx

Looking to add social networking component to SharePoint?

Check out the blueKiwi SharePoint Connector article at the SharePoint Team blog.
http://blogs.msdn.com/sharepoint/archive/2008/06/08/how-we-did-it-bluekiwi-sharepoint-connector-and-officeassistant.aspx

Note: blueKiwi Software is the leading European provider of Enterprise Social Software.

Posters for SharePoint

Get them here:

http://blogs.msdn.com/sharepoint/archive/2008/05/12/posters-for-sharepoint-stsadm-command-line-parameters-now-available.aspx