I just recently discovered that Ryan McCutchen, a colleague of mine here at Statera, started blogging last month.  In this past month he has already put together a number of excellent posts discussing MOSS from an information worker, architect, and end-user perspective.

Two posts that jumped out at me:

• Starting the WSS Search Service - I encountered this problem myself, recently.  Too bad I hadn't read this post first.
• Architecture of MOSS Web Application Separation - Ryan discusses the separation of web applications in MOSS (e.g. separating out team sites).

This is definitely another blog to add to the blogroll!

A neat trick to help you diagnose troublesome security problems.  Modify your the audit settings for process tracking, so that successes and failures are logged in your Security log.

1. Go to Start -> Run.
2. Type: gpedit.msc
3. Expand Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Audit Policy.
   
   
   
4. Review the "Audit process tracking" policy.
5. Right-click the "Audit process tracking" policy, and select Properties.
6. On the Local Security Setting folder, check the "Success" and "Failure" checkboxes under "Audit these attempts".

   

7. Click OK to continue.

If you define this policy setting, you can specify whether to audit successes, audit failures, or not audit the event type at all. Success audits generate an audit entry when the process being tracked succeeds. Failure audits generate an audit entry when the process being tracked fails.

These audits are now tracked in the Security log in the Event Viewer.  Here's an example of a "Detailed Tracking" event.

Some additional details can be found on TechNet.

Pretty easy to configure, and very useful when you're trying to figure out why applications are not running appropriately and you think it might be related to security issues.