Site Usage Reporting in SharePoint - WSS 3.0
6/09/2009 by Michael Losapio
One of the neat features of WSS 3.0 is the new reporting
capabilities. I'm going to go over enabling this usage reporting in
Windows SharePoint Services 3.0 (note: this configuration is
different if you're using Microsoft Office SharePoint Server
2007).
First what you'll need to do is create a folder somewhere on your
SharePoint server where the usage logs will reside. If you're super
anal retentive like me, you'll probably have a small, dedicated
partition just for logfiles - this is where you should put your new
folder (name it something to the effect of WSSUsageLogs or
SharePointUsageLogs). Be sure the ASPNET and Network Service
account have full access to this folder.
Next you'll need to open up the Central Administration site on your
SharePoint server (Start --> Administrative Tools -->
SharePoint 3.0 Central Administration). Once open, click on the
Operations tab. You should see a "Logging and Reporting" section on
the Operations page, and under that a "Usage analysis process"
link. Click on that link.
On the Usage Analysis Processing page, check the "Enable logging"
checkbox, put in the path to the log folder you created, and set
the "Number of log files to create:" to 1. Finally check the
"Enable usage analysis processing" checkbox and set the Start and
End times for the processing to occur - this should be non-peak
hours, either before or after you run your SharePoint backups...
you do back up your SharePoint site, right (If not, more on that
soon!).
After setting up logging in the Central Administration, you can
then view a site's usage report by visiting the site, clicking Site
Actions, Site Settings, and then the "Site usage report" link on
the Site Settings page (you must have administrative priviledges to
do this). Once on the Site Usage Report page, you can view such
nifty things as metrics showing the most-viewed pages/files as well
as how often individual SharePoint users are visiting your site.
Enjoy!
MOSS 2007 Upgrade
5/21/2009 by Michael Losapio
I recently had the pleasure of updating a client's SharePoint
Portal Server 2003 environment to Microsoft Office SharePoint
Server 2007. If any of you have evern upgraded a SharePoint
environment, you know that it's hit or miss - I've had some
upgrades go without an issue, and I've had some that have resulted
in hours of troubleshooting... I dare say I have even had to call
Microsoft for their support on occcasion - every upgrade is
different.
This particular upgrade went very smoothly, and below are a few
pointers to follow to ensure yours does, too.
1. Take an inventory of your site collections, their sites, and
their web parts. This will come in handy for testing after your
upgrade is complete.
2. For custom web parts, be sure to find comparable web parts
written in .NET 2.0 (this may mean custom development for those web
parts written in-house). We have used Bamboo Solutions for
many of our standard web parts (they have some excellent
roll-up web parts available)... definitely check them out.
<plug>Did I mention that we also develop custom web parts? Check us out,
too.</plug>
3. Create an account in Active Directory that has administrative
priveledges that you will use to run all MOSS 2007 related services
as well as for database access.
4. When creating your MOSS 2007 databases, use a consistent naming
convention on all databases... in other words, don't use all
default names. This is what I typically use in my installs - feel
free to use them.
- MOSS_MySite_Content - content database for the
personalized sites.
- MOSS_WSS_Content - content database for all of your
portal sites that was migrated/upgraded from the SPS 2003
environment.
- MOSS_SharePoint_Config - config database for the
Central Administration site.
- MOSS_SSP_Content - the content database for the sites
associated with the Shared Service Provider.
- MOSS_SSP_DB - this is the config database for your
Shared Service Provider.
- MOSS_SSP_SEARCH_DB - search database that stores the
indexed content from the Shared Service Provider content
sites.
- MOSS_WSS_SEARCH - search database that stores the
indexed content from the portal sites.
4. Pay attention to the PreScan and research any warnings and
definitely errors. A little leg-work up-front can keep you from
spending many hours troubleshooting an unsuccessful upgrade.
5. Back up every SPS 2003 database in case of catastrophe.
6. Use the Database Migration method if at all possible... The
In-Place and Gradual upgrades are incredibly risky due to their
being performed on live data. The Database Migration method allows
both SPS 2003 and MOSS 2007 environments to run side-by-side so
comparisons can be made between the two.
7. If using the Database Migration method, set your SPS 2003
content database to Read Only after running the PreScan (setting it
to Read Only before the PreScan will cause the PreScan to fail).
This allows users to still view their SPS 2003 sites and keeps them
from adding/updating content in your live envinroment as you
perform the upgrade.
8. After the upgrade is complete, check each of the sites that you
inventoried in tip #1, paying close attention to the security
settings in each - MOSS 2007 will upgrade the Security Groups you
had in your SPS 2003 environment, but verify your users have the
appropriate access to their sites.
As I stated before, every upgrade is different - if you
customized your SPS 2003 environment, you may hit a few snags but
following my tips will keep you organized, prepared for disaster
recovery, and help lead you to a successful upgrade.