First you need to be made a farm admin, them a member of the owners group on the SSP site, then you have to give yourself the "Manage Usage Analytics" permission in Personalization Services Permissions under the User Profiles and My Sites Section on the SSP home page.

Once you have done that, you can enable Search reporting too. More details on http://support.microsoft.com/kb/825541

There is a great post on Spence Harbar's blog on how to deal with the problem that the SharePoint Central Administration Site only exists on one server, so if that server goes down, you have no way to administer your MOSS farm. The solution is to have it on more than one, and this post explains how, thanks Spence! http://www.harbar.net/articles/spca.aspx

Here are a few limits you should know about when planning your SharePoint deployment:

The 2,000 rule: because stored procedure calls to SQL Server slow down as you reach 2,000 items, have less than that in a view on a List. Less than 200 ideally to have optimum performance.

Have less than 2000 AD users or groups in a SharePoint Group for the same reason. An AD group in a SharePoint group counts as one item, but the first time a user edits content in a site collection, they are added to the user list for that site collection. The best way to avoid this problem is to have lots of site collections so the users and groups are more spread out.

Indexing an item with about 1,000 entries on it's ACL (access control list) will fail. The limit is 64k for the ACL of any item being crawled, on the file system or in SharePoint. Avoid this by assigning access via AD groups rather than directly.

Any user can only be in 1024 AD groups. To avoid this, you could put the users in SharePoint groups if you think this limit might be reached.

The bottom line is you can have as many readers as you like on SharePoint site collections as you like, but if you get to between 1,500 and 2,000 contributors (to reach that 64k limit) you will get errors. Note these are Windows limits that SharePoint is dependent on since it is built on Windows. SQL adds the performance limits for views on lists.

These points are examined in more detail here as well as linking to details of the issues in MS KB articles: http://weblogs.asp.net/erobillard/archive/2008/09/11/sharepoint-security-hard-limits-and-recommended-practices.aspx thanks Eli!

In a SharePoint farm, having more than one server serving pages to users gives you some resiliance. Network Load Balancing is a way to do that. Here's an article that introdices the topic:

http://windowsitpro.com/article/articleid/49925/what-is-network-load-balancing-nlb.html

This is a matter of installing via the command line, details here:

http://www.chandima.net/Blog/Lists/Posts/Post.aspx?List=466e85c0%2D8506%2D4dad%2Db674%2Db825d88a30bc&ID=89

Here is the answer from Gary: http://msmvps.com/blogs/shareblog/archive/2006/08/23/108885.aspx

The instructions are here:

http://www.sharepointblogs.com/mirjam/archive/2007/08/06/renaming-a-moss-server.aspx

Apparently yes. though I have not tried it, loads of links here:

http://blogs.msdn.com/miketag/archive/2007/06/06/configure-moss-to-crawl-lotus-notes.aspx