You are probably NOT a SharePoint Configuration ‘Expert’ if…

After reading Mark Rackley’s recent post, I found that while it was amusing, it was extremely helpful for me, being a consultant on the infrastructure side of SharePoint, as a reference when talking to developers well as great interview material.  I struggled with the title to use for this post, but I went with Configuration Expert because titles such as Architect or Administrator can be somewhat ambiguous and broadly defined.  I will be the second, after Mark, to say that I am not a SharePoint expert as I find that I learn new things specifically about SharePoint every day. 

What am I saying: If you call yourself an expert, the following should apply.
What am I not saying: If any of the following do not apply, then you are not an expert.

Now, let’s begin:

You are not a SharePoint Configuration Expert if you still refer to SharePoint 2010 as MOSS.

Microsoft Office SharePoint Server 2007 was commonly referred to as MOSS.  Valid options for referring to Microsoft SharePoint Server 2010 are SharePoint, SharePoint 2010, or SP2010 and maybe a few others, but not MOSS.

You are not a SharePoint Configuration Expert if you install SharePoint without a plan…

There are so many different configurations with which SharePoint can be installed, that it is crucial to gather requirements prior to beginning an installation.  Governance, Information architecture, performance, growth, service applications, and the list goes on, all play a vital role in a successful SharePoint deployment, and any SharePoint Infrastructure Expert should be able to speak to each of these and why they are important to a successful implementation.

You are not a SharePoint Configuration Expert if you ever recommend using the Basic Install...

These two articles, here and here, go into a number of reasons why no one should use the Basic Install.  The bottom line is if you look at the limitations and the long term consequences of running the basic install, only the Advanced installation option should ever be run.

You are not a SharePoint Configuration Expert if you use the Product Configuration Wizard to install all of your service apps into production...

I run the Product Configuration Wizard for installing my dev environments.  It’s easy and it’s simple. Best of all, I don’t have to worry about using PowerShell! (*sarcasm*)

This is a debatable topic, so I don’t think I can come out and say that you shouldn’t run the Product Configuration Wizard for any of the service applications ever.  There are a few that you should never run it for (example User Profile Service), but there are some, that if you can accept ugly database GUIDs in the database names, it could be argued that there is no technical reason to avoid it.  That being said, I will always recommend manually creating each service application as needed because the wizard does take some shortcuts, and I am rather particular about nomenclature in my installations.

You are not a SharePoint Configuration Expert if you use a single service account in your farm...

This particular topic is a perfect example of an ‘it depends’ topic.  The number of service accounts required for SharePoint may depend on the particular business requirements for a specific installation.  While there are some extremes on both sides, my point in this one is I believe best practice is to use more than one account.  There is just too much security risk associated with using a single service account as your Farm Account, service application accounts and especially user profile service account.  Todd Klindt has a good list of suggested service accounts.

You are not a SharePoint Configuration expert if you can't name the default authentication zones and know how many zones you can have...

This includes knowing how to extend a web application in order to implement the required zones.  This TechNet article speaks to zones in SharePoint 2010.

You are not a SharePoint Configuration expert if you can't configure FBA…

First of all, FBA is not a directory, it is an authentication type.  You can use FBA to authenticate against a customized claims provider, but you can also use it to authenticate against Active Directory.  FBA is often a valid business requirement for remote or extranet access.

You are not a SharePoint Configuration expert if you always recommend the same farm configuration for every installation…

Wait, you mean I can’t just offer a cookie cutter SharePoint implementation?  Businesses all have unique needs and unique processes.  SharePoint is no different.  Business requirements should dictate SharePoint deployments and not the other way around.

I’ll take a couple of points now from Mark’s blog:

You are not a SharePoint expert if you do not capitalize the P in SharePoint...

You are not a SharePoint Configuration Expert if you allow SharePoint Development Experts to manually copy DLLs...

I will also reiterate that you are not a SharePoint Configuration Expert if you are not involved in the community...

I will clarify my point in that it’s not about if you can drop the names of SharePoint ‘Experts’, but that you are sharing your experiences and offering your help to the community.  Basically I would hope to be able to find some reference to you somewhere in the SharePoint community if you are touting yourself as a SharePoint expert.

Finally, I agree totally with Mark in that SharePoint consultants and experts who don’t know everything are far less dangerous than those who think they know it all and are unwilling to listen to reason, the community, or their peers.  It takes more than just the ability to click next a few times to understand the SharePoint infrastructure. 


Thanks to @SharePointLola and @mrackley for the assist on this post!