44CO175 – SharePoint 2010 Administrator Bootcamp (BPIO)
Step-by-step understanding is key to successfully implementing and deploying SharePoint 2010. This 15-module course will guide you through each critical stage, giving you exactly the skills you need to leverage full value from the latest SharePoint technology.
Module 0 – Getting Ready for a SharePoint 2010 Implementation: Why Governance and Business Requirements are Essential for a Successful Implementation.
Module 1 – Understanding the Architecture of SharePoint Server 2010
Module 2 – Installing SharePoint Server 2010.
Module 3 – Administrating and Configuring Farm Settings in SharePoint Server 2010
Module 4 – Understanding and Administrating Web applications
Module 5 – Managing Web Applications
Module 6 – Introduction to Site Collections
Module 7 – Creating Site Collections
Module 8 – Managing Site Collections
Module 9 – Working with SharePoint Server 2010 Portals
Module 10 – Governance and Information Assurance
Module 11 – Enterprise Content Types & Managed Metadata
Module 12 – Managing Documents and Records
Module 13 – Workflow
Module 14 – Implementing and Managing Search
Module 15 – People & Social Networking
Module 16 – Disaster Recovery
A handful of notes from the week..
Installation Preparation for Service & Install Accounts
The SharePoint Installation Account
While I’ve become used to installing applications on servers with either the local or domain admin account, SharePoint 2010 really really really needs to have its own account created for the installation process. If you don’t you’ll have to correct the various service and app pool accounts later and that’s a pain.
Key points about the account used to install with –
- It will become the application pool account used in IIS for the Central Admin
- If you do plan to let SharePoint create your databases (content DBs’ etc…) this account needs rights to the SQL database to create DB’s (DBCreator and DBAdmin)
- If DB’s are already created then it only needs DBAdmin
- It only needs Local Admin permissions on the installation machine
- Not to be used in day-to-day admin
- Imagine this account to be “enterprise admin” of SharePoint.
- It should never be used again after the initial install, obviously that doesn’t mean disable or delete it.
Example User Account – spinstall
The Farm Admin Account
The farm admin account is an account that should be used by as few people as possible.
- It either needs to be a local admin on the SharePoint front end or create a new supper user or login as spinstall(logging in as spinstall is not recommended)
- The farm admin account change services running on the machine hence the need for local admin rights, farm admin right in SharePoint central admin isn’t enough
Example User Account – spfarmadmin
During the SharePoint 2010 install
Make sure you move index location during install off from the C:…14data location
This index file is a flat file used in search and can grow very large in next to no time.
After the install – the Configuration Wizard
Do not use it, it doesn’t follow best practice.
Turn off Auto Growth
While it’s been mentioned a thousand times and shouldn’t need to be mentioned…
To prevent it happening in existing installations for any new databases:
SQL Management Studio > Database > Model. Under the file groups section change the properties for .mdf to grow by 50MB at a time
Fixing it for existing databases:
Open the properties of each database and under the file groups section, change the properties for .mdf to grow by 50MB at a time
Note: Why 50MB? Because it’s just right for SharePoint since it aligns with the default maximum upload file size.
Registering Managed Service Accounts for SharePoint 2010
- Best practice is to add them here first then start to use them to run services
- All are generally fine as just domain user accounts without elevated privileges
Application Pool Accounts in IIS for SharePoint 2010
Never change the app pool account from inside IIS as the config DB will not know about the change, web apps will not know about the change and new servers added to the farm will not know which account to use.
One of the few things you can and do need to configure in IIS is SSL certificates and also needs to be done on each and every web front end.