10 SharePoint Configuration Mistakes, and How to Avoid Them (Part 2)

Tags: , ,

Last week we have started a discussion on the topic of configuration mistakes in SharePoint and what the correct course of actions to avoid making such mistakes is. If you haven’t read the previous article, then please follow the link here. Just to remind you, the reason for such topic is simple: SharePoint is a very complex and multifunctional system that can improve overall workflow at any company. But at the same time, its complexity is a double-edged sword, and it is not uncommon when organizations face troubles with SharePoint. Immediately they are starting with trying to fix the issue, not realizing that the bad seed was planted at the very beginning.

Now that everyone has caught up, we may carry on. Our list has stopped at number 5, so without further ado let’s start.

Another List of SharePoint Configuration Mistakes

Number 6 – Not Being a SharePoint Admin

It’s a little bit controversial, but hear us out, please. The job of SharePoint administrator is not easy and it is very different from working on any other similar environment. It’s true that many server and Windows admins can manage SharePoint but this person requires initial training first. That doesn’t mean you as a manager shouldn’t hire someone who is inexperienced in working with SharePoint. But what it does mean is that your future admin should undergo certain training first before taking on full duty.

Number 7 – PDF iFilter Is Not Installed

Many users complain about SharePoint being too slow. Usually, the performance drops down due to one of the mistakes that we mentioned. But regardless of origin, slow performance would ultimately reduce your search capacity, especially when it comes to a vast library of PDF files. Any firm has an enormous collection of these files and they carry a great chunk of valuable data, so by implementing PDF iFilter you can speed up search process permanently.

Number 8 – Servers Are Not Pointing at Themselves

This is another very common SharePoint 2013 configuration mistake. Not working SharePoint could bring a realm of nightmares into your world. So when things go down, you need some effective means of troubleshooting. So make sure that each and every server is pointing at itself for all applications across the entire infrastructure. If they don’t, then you wouldn’t know straight away where exactly the root of the problem is. Not knowing which ULS (user location server) log contains an error can be a real pain.

Number 9 – Not Using SharePoint Solutions Framework

This is a mistake done on both administration and development sides. Any changes done to the SharePoint Root folder will bring about a row of misfortunes, believe us. When adding servers and apps the files could go missing, even permissions may start behaving differently, which leads to total confusion.

How to avoid that? Try not to tinker around with SharePoint farm manually.

Number 10 – BLOB Caching

This is one of the cheapest and most effective ways of improving SharePoint performance. It eases up the stress on the SQL Server side of things which speeds up SharePoint on its own, plus it helps to get files across to the end user more quickly. It’s one of the easiest solutions to SharePoint speed issues.

That concludes our list of top 10 SharePoint Configuration Mistakes. We hope that you found our two-part article helpful. If it happens that your organization made one of these mistakes or is simply facing problems with SharePoint performance, then don’t hesitate to contact us at Digital Design. We would be happy to assist you and your business in SharePoint optimization. At our company, we utilize only best industry practices. We don’t just treat the symptoms – we fix the problem itself, making your system better.