SharePoint 2010 Training: 5 Most Common Configuration Mistakes
SharePoint 2010 is a difficult beast to tame. Even after all these years, users still make some configuration mistakes. This article explains some of the common errors and also provides the correct way to go about it.
Aggressive Virtualization
Virtualization is great but only if done intelligently and unaffecting other resources. The most common error we come across is over-virtualized deployments, that eat into the resources assigned for other tasks. SharePoint feels the crunch when it doesn't get enough RAM, and squeezes its operations including the ability to cache. This results in a poor user experience. The solution to this problem is adding another RAM. As per norms, you need 8 GB of RAM and 80 GB C-drive to optimally run SharePoint. However, it also depends on the production levels and memory utilization.
Farm Configuration Wizard
This wizard can really wreak havoc in your system by making your task even more tedious and troublesome. It creates irksome GUIDs, content web apps, a My Site host on that web app, and service applications which you are not interested in. The only solution is to clean up all the handprints left over by this wizard. Also, remember to backup your data before attempting to remove any of these places.
A Single Account for Everything
This is another blunder you must avoid to commit. It's very easy and convenient, but really a bad idea. Do not put the security and confidentiality of SharePoint in jeopardy. If you have just one account, then the possibility of it being hacked or broken into, can cost the company million of dollars. It also affects server uptime. To overcome this, you need to create multiple accounts. Stop using sp_farm and create a separate admin account.
Default Settings
Never make this error of going by the default settings as listed in your deployment. For example the autogrow default settings on 1 MB tend to slow down your server. It is suggested that you change them to 500 MB or 1 GB, depending upon your workload requirements. Ideally, autogrow should be the last option, and a DBA or SP admin should take the responsibility of pre-growing the database at regular intervals.
Another one is when the database recovery model is set to Full. This hogs up unnecessary space and slows down the server. What you can do is that change your recovery settings to normal so that it is consistent with your plan of disaster recovery.
No BLOB Caching
If you wish to speed up your operations and SP 2010 response time, why not enable BLOB Caching. It is one of the best ways to enhance performance, since it not only quickens file transfer, but also eases the server of its overloaded burden.
Try to avoid these 5 most common configuration mistakes in SharePoint 2010 Training, and you may end up achieving efficiencies you never before thought possible. Koenig Solutions, an IT Training company renowned world over for its offshore training model, offers this course in Delhi, Bangalore, Dehradun, Shimla and Goa.
Aggressive Virtualization
Virtualization is great but only if done intelligently and unaffecting other resources. The most common error we come across is over-virtualized deployments, that eat into the resources assigned for other tasks. SharePoint feels the crunch when it doesn't get enough RAM, and squeezes its operations including the ability to cache. This results in a poor user experience. The solution to this problem is adding another RAM. As per norms, you need 8 GB of RAM and 80 GB C-drive to optimally run SharePoint. However, it also depends on the production levels and memory utilization.
Farm Configuration Wizard
This wizard can really wreak havoc in your system by making your task even more tedious and troublesome. It creates irksome GUIDs, content web apps, a My Site host on that web app, and service applications which you are not interested in. The only solution is to clean up all the handprints left over by this wizard. Also, remember to backup your data before attempting to remove any of these places.
A Single Account for Everything
This is another blunder you must avoid to commit. It's very easy and convenient, but really a bad idea. Do not put the security and confidentiality of SharePoint in jeopardy. If you have just one account, then the possibility of it being hacked or broken into, can cost the company million of dollars. It also affects server uptime. To overcome this, you need to create multiple accounts. Stop using sp_farm and create a separate admin account.
Default Settings
Never make this error of going by the default settings as listed in your deployment. For example the autogrow default settings on 1 MB tend to slow down your server. It is suggested that you change them to 500 MB or 1 GB, depending upon your workload requirements. Ideally, autogrow should be the last option, and a DBA or SP admin should take the responsibility of pre-growing the database at regular intervals.
Another one is when the database recovery model is set to Full. This hogs up unnecessary space and slows down the server. What you can do is that change your recovery settings to normal so that it is consistent with your plan of disaster recovery.
No BLOB Caching
If you wish to speed up your operations and SP 2010 response time, why not enable BLOB Caching. It is one of the best ways to enhance performance, since it not only quickens file transfer, but also eases the server of its overloaded burden.
Try to avoid these 5 most common configuration mistakes in SharePoint 2010 Training, and you may end up achieving efficiencies you never before thought possible. Koenig Solutions, an IT Training company renowned world over for its offshore training model, offers this course in Delhi, Bangalore, Dehradun, Shimla and Goa.
Source...