Here’s an interesting thing a colleague noticed – SharePoint folders with names ending in _FILE are renamed to end in _FILE_. In the image below the names and titles were the same when I typed them in:
Notice the line for A_FILE. Name and title are now different. No idea why that happens. I’m guessing that SharePoint uses folders with a suffix of _FILE for it’s own internal stuff… 
Was just asked about this and Joel’s post made my day much easier. What discs in what configuration is an important subject for any server – there’s plenty of performance to gain here for fairly little effort.
Themes in SharePoint are tough. I think this quote describes it nicely:
If you have attempted to override the styles on an out of the box SharePoint site, you know that it isn’t a very easy thing to do. The core.css file that contains the basic rules has 979 different style rules.
The core.css file uses a palette of 132 colors and 143 images.
The default page of a newly provisioned team site uses only 61 of those rules.
So, unless you have branded a lot of SharePoint sites and are intimately familiar with core.css and the default master pages and page layouts, just figuring out where to start modifying can be a daunting task.
So Doug has built SharePoint Skinner to make that easier. I’ve not tried it (yet) but I like his thinking…
I just found a post where someone had gotten confused about tokens in MOSS workflow:
This is an obscure error:
Error in commiting pending workflow batch items: System.InvalidOperationException: The event receiver context for Workflow is invalid.
at Microsoft.SharePoint.SPEventReceiverDefinition.ValidContext()
at Microsoft.SharePoint.SPEventReceiverDefinition.ValidReceiverFields()
at Microsoft.SharePoint.SPEventReceiverDefinition.
GetSqlCommandToAddEventReceivers(IList`1 erds)
at Microsoft.SharePoint.Workflow.SPWinOESubscriptionService.
CommitNewSubscriptions(Transaction txn, IList`1 erds)
at Microsoft.SharePoint.Workflow.SPPendingWorkBatch.
ProcessWorkItemBatch(Transaction transaction, Work method, IList`1 workItemBatch)
at Microsoft.SharePoint.Workflow.SPPendingWorkBatch.
Commit(Transaction transaction, ICollection items)
Let’s skip over wondering what an erd is (event receiver definition maybe?)- the solution to this is simple, but not obvious. Check you have created properties for TaskID, TaskProperties and Correlation Token. I found this solution at Robert Bogue’s blog. As a side note it is a REAL pain in the ass that setting up TaskIDs and TaskProperties is so manual – or at the very least that tasks with unassigned values for these do not appear with the red ‘warning’ exclamation mark in Visual Studio.
There was me thinking that this wasn’t possible –You can save an Excel spreadsheet presented via Excel Services. Well, kind of. It’s prototype code, and unsupported, but still, that’s waaayyy cool. Now, all it needs is to work with check-in/check out or ‘last wins’.
More linkage – I know, quite a lot now – but this is stuff I’m sure I’ll want to remember later: Add your own Timer service by Andrew Connell
Excellent work from Ton Stegeman – Adding a custom action to the MOSS expiration policy. Also, MOSS Custom policies parts One, Two and Three. I was particularly interested in Part 2, ‘cos it is programmatically submitting an item to the Records Repository (via a web service. I guess that’s okay, but I was surprised that this didn’t appear to be in the Object Model. Or maybe it is and I just can’t find it!)
I keep referring to this – the Plan for Availability in Technet. Although it’s the plan for availability, it’s got a good discussion of server topologies.
First part of an article here, about setting up the config, second part here about setting up the routing, and best of all, a sample custom router. Thank you thekid!
Andy Burns' Blog 