Should you use SharePoint?  Should you use SharePoint for your public facing website?  Is SharePoint a good CMS?  Does SharePoint have shortcomings as a web content management platform?  Is SharePoint overkill?  Is SharePoint design friendly?

The SharePoint debate is definitely a heated one.  Some people love SharePoint.  Some folks hate SharePoint.  Some people that have never seen or use SharePoint even hate SharePoint.  Some people hate Microsoft and thus by the transitive property also hate SharePoint.

Platform Argument.  SharePoint is a more than just a single web site tool.  This is a great platform that you can use build your Intranet, Extranet, private social network, professional network, search engine tools, and public facing website.  Once you and your team know a little bit about SharePoint, you can focus on doing your job and not learning and supporting niche applications and tools.

Capability.  SharePoint is extremely feature rich.  SharePoint is documents, pages, images, videos, discussions, blogs, wikis, calendars, sites, subsites, security, workflow, search, dashboards, and much more.  The fact that you can construct so many types of solutions without ever writing code is a powerful feature in itself.  If you do write code, then the SharePoint world is your oyster.

Speed of Innovation.  SharePoint is bigger than Microsoft.  There are literally thousands of options available products, add-ons, solution starters, templates, samples, examples, and even source code (see CodePlex).  Even companies that are competitive with Microsoft develop products that ‘tie in’ to SharePoint – even IBM.

Availability of Information.  Do a search for “whatever solution you are thinking about using”.  Then do a search for SharePoint.  Then go to Amazon.  Search for books related to your subject.  Then search for books related to SharePoint.  If you want to become completely self-sufficient (and not rely on the vendor/consultant/IT guy) – there is no platform that has more information available than SharePoint.

Community.  There are more developers, end users, architects, consultants, companies, vendors, Microsoft partners working around SharePoint than any other solution or platform I have every seen.  The SharePoint community exists both online and in person!  There are user groups that regularly meet and talk SharePoint in every major metro area – and many international!  The single most important facet of the community is welcoming attitude of the SharePoint community.  Join any group and participate, or just sit back and watch.  The community is extremely helpful.

Conferences.  There are so many conferences every year that I can’t even keep an accurate count.  Even if the conference isn’t dedicated to SharePoint, there are SharePoint tracks or sessions.

Stability.  I’ve worked with a lot of niche applications that have brand new releases and upgrades every few months.  Wow that sounds exciting!  In an enterprise environment where I’m trying to focus on the business at hand (whether that’s creating content, selling products, providing services, fund raising, representing members, or managing our community), the last thing that I want to do is spend time, resources, and money on continual upgrades.  SharePoint’s major versions are released every few years.  If I do want to continually upgrade and provide new features – I do have the speed of innovation of the entire community.

Speed to Launch.  One of the arguments that I have heard is “I can have a WordPress site up and running in under an hour.”  I’ve always found that amusing…  Are you really going to launch your corporate web site or Intranet or ANY site with that little planning?  Guess what.  If you want to, you can do the same with SharePoint.  There are tons of hosting providers that automatically provision your site and have it turned on and working with any selectable template immediately – even Microsoft.

Marketability.  I’m talking directly to the techies here.  I know many IT folks that have resisted SharePoint.   The best advice I can give any IT person out there is to learn SharePoint.  Take a few moments and peruse the job listings.  Really.  Go to Monster and look around.  SharePoint is an extremely in-demand skill set and has been for years.  From commercial organizations to non-profits and associations to the federal government, SharePoint is in use, and SharePoint experts are in-demand.

Return on Investment.  This is one that gets thrown around a lot – largely because of rumors and suppositions.  One of the most ill informed arguments I’ve heard is that SharePoint is expensive and open source is free!  This final point is one that I could spend entire days discussing.  Here are a couple of high level points.  First, SharePoint Foundation is free.  If you are running Windows Server 2008, you can download SharePoint and use it for … wait for it … FREE!    Okay, but let’s be realistic.  I know that you’ve heard this before – nothing is free.  You have to pay for servers, bandwidth, resources, skills, education, support – regardless of the technology.  If you run any technology platform – you pay for it.   Every preceding item in this blog post also influence ROI.  Availability of information, stability, education costs, capabilities, stability, recurring investments.  Also, what happens when angry IT guy that put in the LAMP solution quits or goes out of business.  Who, where, how are you going to get support?  Is the community and ecosystem big enough to support you in a year?  What about in 5 years?

Technology decisions are complex.  Do I think SharePoint is a good fit for every organization?  Yes!  (just kidding).  I think we can all agree that there is no single technology that is a perfect fit for every organization for every solution.  I think every organization should give serious consideration to the big picture when selecting technology platforms.  Do you want a single platform or individual niche applications?  Do you want commercially supported tools or open source (or a hybrid)?  While I don’t work for Microsoft, I’ve never heard of an IT manager getting fired for choosing Microsoft as a technology platform.

One of the SharePoint features that many end users and site administrators have a hard time understanding is the concept of Audience Targeting.  In fact, I received a question recently asking me to describe how “Audience Targeting” differs from the authentication needed for features like “Collaborative Workspaces”.

The short answer is that Audience Targeting is not security.  Audience Targeting is a type of personalization.  Personalization is not security.

Authentication is the process by which a unique identifier (such as a username and password pair) is used to validate the identity of the user.  The authentication is then used to authorize the requested access, such as gaining access to the Team Workspace areas, working on documents, accessing protected areas of content, etc. 

SharePoint provides the ability for SharePoint Administrators to segment users into logical groupings called ‘Audiences’.  An audience could be ‘new members’.  An audience could be ‘everyone who lives in Dallas’.   Audience Targeting is a way to flag content to be highlighted to authenticated users that are part of a specific Audience.  While Audience Targeting may seem like a complex topic, it can really be thought of as a ‘filter’.  Audience Targeting can be used to show an advertisement, a graphic, a video, a link, or any piece of content to a specific group of users (in the audience).  This does not prevent other users from finding the content (though other links or searching) – it just highlights the content for the targeted users.

To make matters even more confusing for folks, you can actually use SharePoint Security Groups and Authentication Groups (such as AD Domain Groups or custom Roles) as audiences as well – extremely useful but confusing to some nevertheless.

I get asked for SharePoint server recommendations nearly every day.  Like nearly all ‘best practices’, there is no single answer for perfect server recommendations.  The answer always seems to be, “It depends.”  What is your budget?  How many users?  What type of users?  What type of activity are the users doing?  What type(s) of SharePoint sites are you running?  Web Content Management sites?  Team Sites?  BI tools?   If you look online for SharePoint 2010 farm configurations, you will see incredible descriptions of server clusters, farms, SAN configurations, hundreds of GBs of memory, incredible RAID configurations, clusters of servers for every imaginable service and other configuration scenarios that most nonprofits could never afford.  If you want some great fun with environment configuration recommendations, download the HP Sizer for Microsoft SharePoint 2010.  I recently ran a scenario through the HP Sizer and got a recommendation for a 32 server environment with full details. 

Most of the nonprofits I work with don’t have the resources available for 32 new servers to run SharePoint.  Is there anything you can do on a shoestring budget to maximize performance with your SharePoint environment?  Absolutely!  You can run SharePoint on a single server.  It doesn’t matter which version of SharePoint, either.  You can run SharePoint 2010 Standard, SharePoint 2010 Enterprise, SharePoint Foundation, Windows SharePoint Services, and MOSS 2007 all on a single server.  Will it be the absolute best performing SharePoint environment ever?  Probably not.  But you can run an effective and efficient solution on a single server.

If you are running SharePoint on a single server, there are some things that you should take into account.

1. Dedicate your server to running SharePoint.  I’ve seen a variety of configurations where a single server was used to run custom apps, ColdFusion, PHP, Media Streaming Services, Exchange, and a host of other things.   Sure you can do this, but should you?
2. Stop unused services.  Do you really need the audio services running on Server? Stop and disable any of the services that you are not using.
3. Add RAM.  RAM is cheap.  Whether virtual or physical – allocate memory to your server.  I run 6GB dedicated to the VM on my laptop – and I’m the only user. 
4. Plan you drives and partitions.  There are heated debates over partitions, RAID systems and drive configurations on the web.  Like RAM – more is better.  If you are purchasing a single machine to run SharePoint – hardware is cheaper than software at this level.  Purchasing a flexible server with multiple SAS drive controllers and fast drives gives you flexibility to run different RAID configurations (RAID 10 is faster than RAID 5).  Running 3 partitions on the same physical drive is slower than running 3 separate drives.  Want to know something interested – partitioning segments of a drive and leaving the drive largely empty often gives the best performance.  If you have a 1TB drive and put a 250GB partition on it and ONLY use the 250GB – you will get better performance than if you use the whole drive.   Sure you are ‘wasting’ 750GB worth of space, but this recommendation is about getting optimal performance from a single server – not conserving drive space.
5. Plan SQL.  If you are using SQL Server Express (which is the default version used during a stand-alone install), then there is very little configuration control you have using the install wizard.   If you are using a Standard version of SQL Server 2008, then you have a ton of control over configuration options.  You can split data, logs, temp db, OS, and page files all to different drive arrays.  If you dedicate controllers/drive arrays to each of these operations then you will gain significant performance gains from SQL.

As you can see, there are tons of things you can do to optimize performance for a single server environment.  All of these steps should be considered with multi-server environments as well.

To paraphrase (and completely rewrite an old saying), your environment is only as fast as the most restrictive bottleneck.

If you are a techie, you probably already know what SharePoint is.  If not, SharePoint is website building software.  Sounds simple, doesn’t it?  It is.  SharePoint is software created and maintained by Microsoft to create and manage websites.  What kind of websites?  All kinds.  Big sites and small sites.  English sites and multilingual sites.  Simple sites and complicated sites.

SharePoint can be used to build internally facing websites for organizations.  Websites for staff only,  Intranets, Department websites, Team websites, Project websites, Time tracking websites, Inventory management websites, Charitable Contributions websites, Business Intelligence solutions, Portals, and much more.

SharePoint can be used to build public facing websites.  Public facing websites are sites that don’t require you to login.  You can build websites for your company, your brand, your organization, foundation, trade show, convention, meeting, store, hotel, or any other site you want.   There are thousands of sites on SharePoint, like Ferrari, ISACA, Ohio U Alumni, Australia’s Southwest, Barilla, Choose Chicago, and of course, The Library of Congress. 

SharePoint can be used to build other types of sites as well: Social Network sites, Professional Networks, Extranets, Communities, Portals, Document Collaboration, Wikis, Blogs, Calendars, Project Management sites, Club Sites, Home Owners Association sites, school sites, soccer team sites, government agency sites,  and so much more. 

If you are looking for really simple intros into SharePoint, hopefully this will help some.  If you are a techie, Microsoft has some great information on their many websites.   

Marketing stuff: http://sharepoint.microsoft.com/en-us/Pages/default.aspx
Developer stuff: http://msdn.microsoft.com/en-us/sharepoint/default.aspx
IT Stuff: http://technet.microsoft.com/en-us/sharepoint/ee263917.aspx#tab=1

When configuring a new SharePoint 2010 server using Active Directory authentication, I was setting up the AD Synchronization and received the error “MOSS MA not found”.  This was a simple fix: The Forefront Identity Manager Service was not started.  Started up this service and then was able to configure a new AD synchronization connection.

To create the connection, just go to SharePoint 2010 Central Admin > Application Management > Service Applications > Manage Service Applications > Manage User Profile Store (note that your link will reference the actual name of your Profile Store Service Application).

Under Synchronization, select Configure Synchronization Connections.  If you need a new connection, select Create New Connection or you can edit an existing connection.

I am impressed with the number of connection types that SharePoint supports out of the box: Active Directory, Active Directory Logon Data, Active Directory Resource, Business Data Connectivity, IBM Tivoli Directory Server (ITDS), Novell eDirectory, and Sun Java System Directory Server. 

And, of course, the three primary Authentication Provider types: Windows Authentication, Forms Authentication, and the new Trusted Claims Provider Authentication.

For an AD authentication, I am a huge fan of being able to utilize specific containers for synchronization.  In my demo environment, I’ve created a couple of AD Organizational Units that I’m using for synchronization testing.

In this entire configuration scenario, I find a one item specifically interesting (and humorous) – the error message: MOSS MA not found.  I know that there was a tremendous code base that needed updated, but an error message string still has ‘MOSS’?  The SharePoint 2010 product no longer has the acronym MOSS.  It’s just interesting that there wasn’t a task to do a code search for this Acronym for the new build.  Maybe someone at Microsoft could shed some insight on this.  Just makes me wonder what else will be uncovered.