#1 Limit your SQL
When you install SharePoint 2010 on a complete mode with a SQL SERVER 2008R2, there is an option on the properties of the server, that you can limit the RAM usage. If you don’t limit the usage, it will use 2.1 petabytes.
The default value for SQL Server 2008R2
Maximum Server Memory setting is 2,147,483,647 MB. Therefore, SQL Server will use all available memory for its own use.
#2 Use different users for your environment
When you will configure Web Applications, Service Applications … Do not forget to create for each of these Applications a user.
The main raison is that when this service or user will get an error it will be easy for us to know with service has failed. (EVENT VIEWER)
Second raison is that on IIS7, the application pool names are getting GUID. So we can have more information just on regarding the username:
If we had the same user for each service, we could never know which GUID was for witch Service.
(1 first) The e6266ed1faa2406cbae0bbbf33f6e4ba is my Access Service..
#3 Use a Warm up Script
Yes, everybody knows SharePoint is slow, and in many cases it’s extremely slow. But there are many solutions therefore. The best solution is to use a WARM UP script.
It will compile everything, and your SharePoint will be very faster.
#4 Disable unused warnings on SharePoint
The SharePoint Health Analyzer detected a condition requiring your attention.
Drives are at risk of running out of free space.
This is an example of a BETA warning on SharePoint; it can be disabled on Review Job Definitions. Do the same of each job that you think that’s unusual for you.
#5 SQL BROWSER
Start your SQL BROWSER service on services.msc on your SQL Server. It is a very useful tool that helps you to see each warning, error … on the SQL Server
It will show you more information about the login failure’s with an explicit SQL ID.
#6 Service Connections
When you will create a new WEB APPLICATION SharePoint will attach each service on your WEB APPLICATION. Even the one that you don’t need, so in place of using de “default” value use the custom value on Central Administration
#7 Made a SHORTCUT 14/
Made a Shortcut to the desktop of you 14 document and it will be easier to check your logs and many other things.
When you use the fully qualified domain name (FQDN) or a custom host header to browse a local Web site that is hosted on a computer that is running Microsoft Internet Information Services (IIS) 5.1 or a later
version, you may receive an error message that resembles the following:
HTTP 401.1 - Unauthorized: Logon Failed
This issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address.
#9 Use a PowerShell Script for downloading prerequisites.
SharePoint prerequisites installer will install “everything” that he thinks that it will be ever used. But in many of cases it’s not true. Take this script modify it and download the applications that “you” need..
#10 don’t use port 80 for Central Administration
When you will install SharePoint Server/Foundation, it will ask to give a Port number for Central Administration; give everything but don’t give 80 (http protocol). So you can hide your Central administration from possible attacks.
It will give a standard IIS page.