SharePoint Server

WSS 3.0 SQL Choices

9/15/2009 by Michael Losapio

Looking to install Windows SharePoint Services (WSS) 3.0 and don't have a few thousand dollars to throw down on the SQL Server 2008 Ultra-Mega-Hardcore Edition? Fear not, for it can be done on the cheap! Be sure to take a few things into consideration before performing your install, though...

Here are a few of your options we consider at TwinEngines:

Windows Internal Database - Probably the best option for the frugal administrator
Pros
1. No size restriction.
2. Free.

Cons
1. Must be single server installation.
2. No included database tools for administration (but you CAN use the 2005 Express Management Studio - Get it here!).
3. Doesn't allow remote connections out-of-the-box (takes additional after-the-fact configuration to allow for this).
4. Can't set up nightly SQL backups... will need to script an STSADM backup that will run nightly as a Scheduled Task. This is actually a good practice regardless of the SQL version you use...

SQL Server 2005 Standard or Enterprise
Pros
1. Mack-daddy database application
2. No size restriction.
3. Can be multi-server install.
4. Has tools for administration.
5. Can set up nightly SQL backups

Cons
1. Expensive.

SQL Server 2008 Express (not recommended)
Pros
1. Free
2. Can be multi-server install.
3. Has tools for administration (2005 Express Management Studio).

Cons
1. 4 GB limit (I'd say this is a dealbreaker).

Helpful links for SharePoint SQL Server:
Download SQL Server 2008 Express
Download SQL Server Management Studio Express
Administering your Windows Internal Database

SharePoint WSS or Office SharePoint Server 2007 - MOSS Standard or Enterprise

7/20/2009 by Jack Burnett

I help small and mid-market companies solve business problems with IT-based solutions and improved processes.  As a Microsoft Gold Partner, TwinEngines has SharePoint technology as one of the tools in the toolbox.  So after the problem is understood and goals and objectives are finalized, we start defining and architecting the solution that is the right fit for the best value.  When that solution involves collaboration with employees, customers and vendors or business intelligence, then I reach into the toolbox for Microsoft SharePoint as an option.

Solely speaking from the technology perspective, this is where it gets confusing.  That's because we have to answer the question, "what Microsoft SharePoint technology is right for the solution and corporation?"  Is it Microsoft SharePoint Services?  Is it MOSS 2007 Standard Edition?  Is it MOSS 2007 Enterprise Edition?  What about Forms Sever or Search Server?  What are the costs involved?

Windows SharePoint Services, WSS, is a platform for building Web-based business applications.  It has administrative controls for managing storage and Web infrastructure providing a cost-effective way to implement and manage a high-performance collaboration environment. WSS is included in Windows Server 2003 and later versions. If you own Windows Server then you already have WSS.  Since there are no additional licensing costs, I look at WSS as the first choice when architecting a solution.

Office SharePoint Server 2007, MOSS 2007, extends the capabilities of Windows SharePoint Services by providing organization and management tools, and by making it possible to publish information to the entire organization.  MOSS 2007 offers ready-to-go, enterprise-wide functionality for records management, search, workflows, portals, personalized sites, and more.  It has its own licensing costs.

There is a lot of information out there to explain SharePoint, because it can do so many things. In working with Microsoft over the years, I have discovered 3 links that help explain what is the right SharePoint technology and what are the costs:

1. Which SharePoint technology is right for you?

2. Microsoft Office SharePoint Server 2007 and Related Technologies pricing

3. Microsoft Windows Server 2008 Licensing Model

At TwinEngines we bring in licensing specialists as part of our team.  We provide a complete picture of a solution in terms of strategy, technology, process and support.  We also show the short term and long term costs and ROI.  We look at business problems first, and pull out the SharPoint technology tool when we think it will help our customers achieve the goals and objectives, with the best return on investment.

MOSS 2007 Search Configuration Tip

6/16/2009 by Michael Losapio

Greetings, MOSS 2007 enthusiasts! Just wanted to share a quick tip about configuring search in the Shared Service Provider...

Here was the situation:
When setting up a client's MOSS 2007 environment, the server name was used for the main site collection's URL (server: SRV-MOSS, URL: http://SRV-MOSS). As you can see, this isn't the best URL for daily use, so the client requested a default alternate access mapping of http://portal. After making the change the the default access mapping, something happened - site-wide search continued to work, but searching "This Site" and "This List" no longer worked.

Here was the solution:
It turns out that when I'd configured the SSP's search content source, I'd used the http://SRV-MOSS URL for the URL to crawl. DO NOT DO THIS. For all searching to work properly, be certain that the URL you're crawling is identical to the default URL in your alternate access mappings.

Here were a couple helpful links that led me to my solution:
Microsoft TechNet Article
SharepointSearch.com

Hope this saves you some time!

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.

Death and Digital Property

5/12/2009 by Jack Burnett

What happens to your digital property when you pass away?  A morbid topic, I know; but it is a growing question people have to consider with the plethora of online accounts, email addresses, Facebook pages, and other social media information we all have on the Internet.  It was the topic of an NPR radio program involving LegacyLocker.com, a new website where you can store login credentials and inform relatives what should be done with your online assets.  That's right, there is a company that will safely secure your digital property and allow access to your loved ones.  So when you are gone - but not forgotten - you can ensure that the persons you want access to your emails has it.

This has become an issue elevated to national radio coverage because wills typically do not protect your digital assets, and most web sites have little or no provisions for a friend or relative to transfer the account information.  After listening to the program, I considered all the logins to banks, brokers, service providers, my Facebook page, LinkedIn account, Twitter conversations, my photos and music stored online, etc.  I'm not sure I need LegacyLocker yet, but I do realize that I need to plan, collect, organize and secure this information.

Then I considered the small and mid-market companies I work with on a daily basis.  Typically these are family-owned and operated, sometimes with online personal and business accounts co-mingled and serving dual purposes.  What happens when the company founder or owner leaves this earth?  Does the progression plan include access to the company Facebook page or LinkedIn account?  Is the login to a partner's co-branded online service in a secure place or would you need access to their email account to get the forgotten password?  Is there one place where accounts and login credentials to online assests are stored; if so, how is it protected?

At TwinEngines, we built our company Intranet on the Microsoft Office SharePoint Server platform.  Besides being our repository for HR information, company work documents and our knowlegbase to support our business, we have created a  place to keep account information for our vendors, suppliers, partners and our social media sites.  Our customer extranet built on the same SharePoint technology, stores information about each customer and the services we provide.  All this information is secured with login access tied to our Active Directory accounts, and backed up nightly as part of our database backup process.  So as employees come and go or change job positions, we manage our Active Directoy network accounts and access to company digital assests as part of our new employee orientation, termination and job transfer processes.  Access to our digital assets stored in SharePoint are protected without any other special efforts.

Are your company's digital assets protected when key employees leave for another company or pass away?  It's not a pleasant thought, but one that has to be considered.  Do you have a plan, and what technology do you have to store information that is safe and secure?  Fortunately, the technology piece to the puzzle may be closer than you think. A lot of small and mid-market companies do not realize that they own Microsoft SharePoint already, since it is bundled with their Microsoft Server software.  For larger companies SharePoint is included with their enterprise agreement with Microsoft.   Read more information about SharePoint here.