Sharepoint – how to “sell” the concept?

If you need to “sell” the concept of Sharepoint to a client or even in your own organization, there are a few pointers to keep in mind, so I will try to sum up the dos and don’ts.

Before the list, keep in mind that Sharepoint is not a complex platform, but it provides MANY functionalities and solutions, and sometimes that is the hardest part . . . how do you explain what is Sharepoint and what can be done with it.

 

First lets talk about what you SHOULD do:

  • Know Sharepoint – this seems a bit obvious, but it is so important for the person that is talking about a solution or product to have REAL knowledge. It is the only way you can “sell” the idea for a specific client or context. Someone that really knows what they are talking about can adapt his speech in a presentation or conversation to the needs and desires of the client, and can clarify any doubts that may appear.
  • Know your client – when you go to an external or internal client, you should know as much as possible about him. This is an advantage when addressing someone, and enables you to adapt your speech / presentation to the clients context. This is so important even for internal clients, if you must have this presentation internally in your organization, try to know exactly to whom are you going to be talking so you can be prepared.
  • Adapt your scenarios – If you are going to talk to Lawyers don’t take them a retail presentation, clients need to have their scenarios or as close as possible, so they can relate to what you are presenting. Even if you are talking to someone in your organization, do adapt your speech and facts to the reality of the clients needs.
  • Take the numbers with you – so you do need to persuade your client to choose Sharepoint, try to have some licensing information, because one of the first questions will e “how much will this cost me?”, this question usually comes from financial or administration profiles. Another typical question is related to hardware, this one comes from the IT departments, “How many servers will I need?”, “What Software will be needed?”. So the architectural knowledge is also important.
  • Prepare and rehearse  your presentations – If you are well prepared for a meeting or presentation, the success probability is huge. By preparing you can improve your own speech and presentation, and at the same time gives you confidence for the talk itself.
  • Keep it simple – if you cannot explain in simple terms what you are talking about, you will not be able to talk clearly to so many client profiles. You need to be ready to talk to administrations, IT departments, Human Resources, Administrative sections, or even profiles like industrial workers.  In your speech do abuse the technical terms, remember that not all people know what you are talking about.

 

Now lets talk about what you SHOULD NOT do:

  • Do not try to teach your client his business, usually they do not like that.
  • be carefull with your speech, keep it clear and simple without the abuse of technical terms.
  • do not go to a presentation without rehearsing it, one of the worst feelings is to be talking about something without knowing the sequence or the subject.
  • At least google about your client, jus to know what they do.
  • If you do not know about what someone asks you, DO NOT make things up!!!

 

These are some of the pointers that I usually use for myself and my team.

Sharepoint 2007 – Updating Child Content Types problem

There are still a lot of implementations of Sharepoint 2007, and I still work with some. This week we came across a problem updating content types across a site collection using the User Interface and I didn’t find any reference to this problem or solutions. So because I had to figure it out on my one, here it is my contribution on this issue. It is a long post, but I am trying to detail as much as I can.

  • Problem:

Actually we had two different problems that resulted in the same behavior, we had to add 4 new site columns to a Site Collection Content Type, that is the Parent of a 120 Child Content Types, most of them direct Parent, some of them is the indirect Parent [Content Type A -> Content Type AA (inherits from A)-> Content Type AAA(inherits from AA)]. And to help the scenario we have these Content Types are applied in document libraries in 450 sites and sub-sites.

Problem 1: We added 4 new site columns to the Base Content Type (Content Type A) and set the update option to true, this option would update all Content Types that inherit from the Content Type A.

Problem 2: We changed the order of the columns in the Content Type A and set the update to true, this option would update all Content Types that inherit from the Content Type A.

  • Behavior:

Problem 1:
When we applied the changes to the dependent Content Types, after a long time, we had the page were we were executing the process, returned a Time Out error.
The result was that we had some document libraries Content Types updated and some not updated. apparently the process was terminated and the update didn’t finish. After a few hours we checked and there was more updates done, but didn’t finish all the updates. No more updates were observed.
During this update process the server started consuming a lot of RAM, sometimes getting to use up to 90% of the available RAM. You can check this using the Task Manager or in the IIS Manager the Worker Processes and looking to the Sites Application Pool process.
The final result was that we had only some Document Libraries Content Types updated, leaving the others to be updated.
Problem 2: The behavior was the same has described in the Problem 1 behavior.
  • Solution:
At least my solution :)
Problem 1:
To force an update in a Content Type we need to change something, otherwise Sharepoint won’t start any update.
We started by trying to update only 1 Site Column, the trick was to remove the 1 site columns from the Content Type A without updating the child Content Types. After this we add the 1 Site Columns again this time setting the update option to true.

This time the process didn’t failed and all Child Content Types were updated with the new field. To the Child Content Types that already had the new field no change was done, and to the ones that didn’t had the new field was added.
Feeling confident we then tried with the remaining 3 Site Columns, again the trick was to remove the 3 site columns from the Content Type A without updating the child Content Types. After this we added the 3 Site Columns again this time setting the update option to true.
This time the process didn’t failed either and all Child Content Types were updated with the new fields. To the Child Content Types that already had the new fields no change was done, and to the ones that didn’t had the new fields were added. In this 3 Site Columns update process was done in 2 separate times, when we checked the update times we had one major update 14 hours before and another 8 hours before.
Problem 2:
So now we had all new Site Columns in the Content Types and we needed to change their order, remember that this update order process had been done and like the Site Columns update had stopped with a Time Out error and only updated some.
To force an update of the order of a Content Type we need to change something, otherwise Sharepoint won’t start any update.
We started by trying to update the order again, the trick was to change the order in the Content Type A without updating the child Content Types. After this we reorder to the desired order again this time setting the update option to true.

The update process failed again and we had to check which Child Content Types were updated with the new order. What we found was that some of the updates that previously failed were now done, but not all.
So, what can we do???? run it again :)
So always apply the complete changes you want to do, in this case I changed the order of new all fields, without updating the Child Content Types, and then reorder them all to the desired place before updating the Child Content Types. Done, updated them again and  . . .
This time we didn’t get the Time Out error, the process ended and all Child Content Types were updated with the correct order.
This solution to update the order is not a pretty one, but im my case it worked and did the trick. You can do these  updates using code, or running the STSADM extensions, just remember that if you already have information in Site Columns in a List or Library you cannot simply remove that columns and added again, that was my case, and that is why we choose to run the User Interface process. It works, but sometimes it needs a little push :)
Hope this helps someone!

FINALLY, Microsoft Embraces Social — And It’s Going to be Big

FINALLY, Microsoft Embraces Social — And It’s Going to be Big

I have come accross an article in Forbes web site on Social Enterprise in Microsoft products and strategy, if you follow the Sharepoint evolution you know that this is one of the areas that has been growing in every new version of the product.

Since the 2007 version (MOSS) that Microsoft has started a trail of Enterprise Social networking, providing  features that allow knowledge sharing, profiles connections among others. These were upgraded in the 2010 version but are still in a very early stage, and we hope that in the next version of Sharepoint this can be really an investment.

Check out the Frobes article at: http://www.forbes.com/sites/markfidelman/2012/03/13/finally-microsoft-embraces-social-and-its-going-to-be-big/

 

Manage Farm Solutions: Successfully copied solution files to IIS site

Well, every Sharepoint project seems to teach me something new, this time it was about farm servers and solutions deployments.

The Scenario:

1 Farm
2 WebFront servers
2 Applicational Servers
1 Cluster SQL

When we started to setup and configure the farm, the server WebFront1 started having some bizarre behavior, that at the time it could be related to FBA configuration (that it didn’t explained the scenario). The decision at the time was to take stop the Web Applicatoin service of this server leaving the farm with only one WebFront (webfront2) and 2 applicational servers.
When the project was ready to go live, we tried to recheck the server Webfront1 by atarting the web application service and check that every other configuration was ok. After doing so this webfront just didn’t behaved has expected, having a number of non-explicit errors.

After some analisys and some checking with some good friends and Sharepoint Community coleagues, I tries to rule out some possible causes, like:
- checking all services were running, including the Sharepoint 2010 Administration
- Checking every eventviewer entry related to this to try and get some more info
- and finally to check if all clocks in all servers were in synch !!!!!!

Well guess what??? the server Webfront1 was about 5/6 minutes in advanced on the other 3 servers.

As soon as the systems team performed a synchronization with the Domain Controller every thing started working just fine.

So, if by any change you have a message on your Manage Farm Solutions like “Successfully copied solution files to IIS site” and you simply don’t know what might be the problem, just check your servers clocks, it might be the problem, at least in my case it was.

Hope this post can help, because when I tryed to find the cause of this problem it simply wasn’t any information available.

Meeting of the SPUGPT – Portuguese Sharepoint Community

It will be held a meeting of the SPUGPT – Portuguese Sharepoint Community next saturday the 8th May, during the morning.

If you are interested in attending do register at the SPUGPT (http://www.sharepointpt.org/Register.aspx) site to receive an invitation.

You can also follow the SPUGPT in the following media:

Hope to see you there.

I will be presenting at TechDays 2010 in Portugal (22 April – 15:15)

This year I will be attending and presenting at the Portuguese TechDays 2010, my session is scheduled for the 22nd April, 15:15 and it is on the subject of “Creating better solutions for the citizen using Sharepoint and CRM“.

The main focus is the Citizen Services Platform from Microsoft, more specifically the sub-set of Sharepoint and CRM and how this integration can be a great solution for the Citizens and for the provider.

The rest of the days I will be attending and helping promote the SPUGPT – Portuguese Sharepoint Community.

Sharepoint 2010 Development environment – Windows 7 (Part 2)

Following the first article on setting up a Sharepoint 2010 development environment, this time I will focus on another very cool choice having your development environment on a Windows 7.

If you have the experience of MOSS you know that you could only have it installed in a Windows server OS (2003 or 2008), and this would make you use virtual machines or setting up development servers. This time the people of Microsoft allows you to set up the development in a common Windows 7 (64 bits) machine, personally I find this option a great advantage to every developer that needs to start “playing” with Sharepoint 2010.

I have already a Sharepoint 2010 environment set up in a Windows 7 machine, and so far so good, let me highlight that this solution should be used to discover and build the first experiences, but for a real world set up you should build a more solid solution.

So, cutting back on the small talk . . .  I followed the MSDN article – Setting Up the Development Environment for SharePoint Server.

Good Sharepointing!!