180 days is approaching

It’s now nearly 180 days since theĀ MOSS 2007 SP2 product expiration problem was discovered. Any systems that are running with the original version of SP2 will expire 180 days after it was installed. There are some quite simple solutions to this problem, but it’s worth assessing the state of your systems to make sure they aren’t at risk.

If the original version of SP2 has been installed on any systems, this can be fixed by re-entering the original product key or by applying this hotfix. If the service pack installer was downloaded after 29/7/09, this fix is included. Any questions should be answered by the original post’s Q&A.

SharePoint 2007 administration part V: Site Collection administration

This is the fifth post in a six-part series on SharePoint 2007 administrative commands. So far I’ve covered:

In this post I will review Site Collection-scoped administrative functions. Continue reading “SharePoint 2007 administration part V: Site Collection administration”

SharePoint 2007 administration part IV: SSP administration

Audiences

This is the fourth post in a six-part series on SharePoint 2007 administrative commands. The first part was an overview, the second covered Farm administration, the third covered web application administration, and this post is devoted to Shared Service Provider (SSP) administration. The bulk of this post only applies to MOSS, as there is no SSP for WSS. Continue reading “SharePoint 2007 administration part IV: SSP administration”

Windows 7 and Windows Server 2008 R2 Federated Search

Federated Search is one of the most useful and interesting additions to MOSS 2007 since it was launched. It’s now been announced for Windows 7 and Windows Server 2008 R2.

Federated Search was integrated into MOSS 2007 with the post-SP1 Infrastructure Update, which effectively brought the Search Server 2008 product to the MOSS 2007 platform. Federated Search will pass a query from a single interface to multiple OpenSearch-compatible indices. It will then render matching results from these indices asynchronously as they return. In MOSS 2007 a federated search web part is added to a search results page and each web part renders only if results are found through that Search Connector. This works brilliantly, as local results will typically return first, then remote sources will render in due course.

This functionality has now been added to Windows Search. I think this is a fantastic move, as these choices will often be very preferential. I may want Wikipedia while you will want Britannica. I may roam among three branch offices and need to query each of the regional SharePoint portals. It’s very powerful stuff – especially when it moves to the client and can be configured to individual needs.

Find more Search Connectors on the Enterprise Search site. Read the Windows 7 Federated Search Provider Implementer’s Guide.

SharePoint 2007 administration part III: web application administration

This is the third post in a six-part series on SharePoint 2007 administrative commands. The first part was an overview and the second covered Farm administration. This part covers web application administration, which is carried out in SharePoint Central Administration. These administrative functions are carried out by farm administrators, but scoped at the application level rather than across the entire farm. Continue reading “SharePoint 2007 administration part III: web application administration”

SharePoint 2007 administration part II: Farm administration

This post is part two of a six part series on SharePoint 2007 administrative commands. The first post is an overview of the effort. This section identifies what farm administrators can do at the farm level. Farm administrators also administer SharePoint web applications, but I will be covering that functionality in the next post.

Note: farm administrators can take ownership of any site collections or deny access to entire web applications, so the people filling this role must be trusted. Auditing can identify and alert the Site Collection Owners to the act of taking ownership, but damage can be done in the intervening period.

As mentioned in the first post, this is a brief command reference organised by administrative scope. Continue reading “SharePoint 2007 administration part II: Farm administration”

SharePoint 2007 administration part I: Overview

Last night I remembered that after I read the SharePoint Administrator’s Companion I put together my own administrative guide. I needed something much shorter that would take the SharePoint administrative interfaces as a starting point. This was effectively a click-by-click administrative reference. In fact, I assembled it by going through each button click available. Continue reading “SharePoint 2007 administration part I: Overview”

SharePoint history and pre-history

Jeff Teper, the Microsoft SharePoint Corporate Vice President has posted a history of SharePoint on the team blog. Note: it could use a proofread, but I think it’s worth sticking with it if you’re not intimately familiar with the product already.

I found a couple of thing particularly interesting:

  • The Office 2010 Engineering blog. I’m a beta tester for Office 2010 and love it. This looks like an excellent introduction to the new features
  • The Microsoft Townsquare prototype. As Jeff Teper says, it’s interesting for us to see how this publicised work from June 2008 has formed the basis of SharePoint 2010’s social networking features

Custom STSADM command for BackConnectionHostNames

Gary Lapointe recently released a custom STSADM command for setting the BackConnectionHostNames registry key. The relevant Microsoft KB article recommends specifying each host header with theĀ  BackConnectionHostNames key rather than disabling the loopback check, as this check is a valuable security fix. As Gary Lapointe mentions, Spencer Harbar put together some thorough background information on the roots of the fix. Without this command, setup and maintenance can be a bit of a hassle if you have lots of SharePoint applications or lots of Alternate Access Mappings (or if any of this information changes with any regularity). These registry changes need to be made on each web server for any sites with host headers. This includes Central Administration if it’s not configured on <servername:port>. So this could get quite laborious if the farm is fairly large. The UpdateFarm parameter may be particularly helpful in this regard.