A growing commonality we're seeing is allowing external visitor access to SharePoint, whether it's a police department rolling it out their community or an organization wanting to allow it's 80+ volunteers access. The most cost effective way to do this is to use forms authentication and SQL server to store the membership database. You can use the same Active Directory your site is running on now but then you need to license each user in your network. Using SQL server stores the user account... [More]

Unfortunately I know this first hand. We were working on a customer's SharePoint instance and had to uninstall a feature. So using stsadm we went to uninstall the feature and forgot to include the feature part of the command. So we ran stsadm -o uninstall........... and uninstall it did! It completely uninstalled SharePoint from the server with no prompt or warning! The only thing left was the configuration wizard and the IIS websites were stopped. I reran the configuration wizard and received ... [More]

In one of my customer's MOSS implementations we're using SharePoint's resident permission management to control who has access to what InfoPath forms. The issue we came across is that if a user has read-only access to a form and opens it, they can see the Update button. Clicking it does error and denies the change, and after the error the user gets the typical form closed message. We wanted to hide the button from the view of a user who has read-only permissions to deny the error all together... [More]