• Open wireless access is available.• Feel free to Tweet (#SPcincy2012) and blog during the session.
Tony MaddinAscendum SolutionsSenior Practice Consultant Tony is a Senior Practice Consultant at Ascendum Solutions with 15 years of experience as a web developer, web administrator, web applications administrator, and six years as a SharePoint administrator. His perspective on SharePoint administration encompasses: installation, automation, workflows, power user items, disaster recovery, and performance tuning. He especially enjoys leveraging SharePoint as a platform to achieve quality business results with a variety of customers – both technical and lines of business. Tony serves on many local boards (including the University of Dayton MIS Advisory Board), is the founder of DAYSPUG, and now serves as the SharePoint Saturday – Dayton event coordinator. Twitter: @TonyMaddin Blog: tonymaddin.net
Clint RichardsonAscendum SolutionsSenior Practice Consultant Clint has over 12 years of progressive IT experience with extensive knowledge of network troubleshooting, security, and architecture, specializing in SharePoint Administration and infrastructure for the past five years. He has assisted multiple branches of the military (most recently in Baghdad, Iraq) to plan, build, and optimize large-scale SharePoint deployments in locations around the world. Recently Clint co-authored his first book: SharePoint Server 2010 Administration 24- Hour Trainer and currently holds the position of Senior Practice Consultant at Ascendum Twitter: @ClinteRich Solutions. Blog: pointblankadmin.com
Tasks for the Site Collection Admin ◦ Tony Maddin Tasks for the Farm Admin ◦ Clint Richardson Q&A Closeout ascendum.com
Site Collection Administration Agenda List Limits Security Recycle Bins Document Library’s/Lists Sub-Sites
List LimitsLarge lists can have an impact with SharePoint performance.By default, the list view threshold prevents operations that willinvolve more than 5,000 items, such as queries that will returnmore than 5,000 items or adding a column to a list thatcontains more than 5,000 items.
List LimitsAlthough this is a configurable default, it is stronglyrecommend that you keep it. If poorly performing queries areused on lists with more than 5,000 items, overall throughputcan significantly decrease when you increase this limit.
List LimitsWhy? – SQL ServerSQL Server uses row-level locking as a strategy to ensure accurate updateswithout adversely affecting users who are accessing other rows. However, if aread or write database operation, such as a query, causes more than 5,000rows to be locked at the same time, then it is more efficient for SQL Server toescalate the lock to the entire table until the database operation is completed.When this lock escalation occurs, it prevents other users from accessing thetable.
Security The integrity, confidentiality, and privacy of your organization’s mission-critical information rests on how secure you make your site — specifically, to whom you choose to grant access to your site. Granting and restricting access to your site is called managing permissions, and it’s one of your most important responsibilities as a site owner.
Security Follow the Principle of Least Privilege Give people access by adding them to standard, default SharePoint groups (such as Members, Visitors, and Owners).
Security Use permissions inheritance to create a clean, easy-to- visualize hierarchy. ◦ That is, avoid granting permissions to individuals, instead work with SharePoint groups. ◦ Where possible, have sub-sites simply inherit permissions from your team site, rather than having unique permissions. Organize your content to take advantage of permissions inheritance: ◦ Consider segmenting your content by security level – create a site or a library specifically for sensitive documents, rather than having them scattered in a larger library and protected by unique permissions.
Recycle Bins Please note items in the Recycle Bins hit against quotas.
Document Library’s/Lists Monitor Versions Versions are exact copies. Versions are a cost ◦ Storage ◦ Backups
Sub-Sites Being able to spontaneously create new sub- sites can be a great benefit to your organization. But unrestricted site creation can get out of hand. When sub-sites proliferate freely, problems can arise
Sub-Sites It’s hard for users to find the right sub-site, or be sure if they have. Information can be duplicated in several sub-sites, using up expensive storage space, and requiring duplicated effort to maintain. Out-of-date information can reside on sub-sites, potentially for years, showing up in search results. It can be hard to tell what version of information is correct.
Sub-Sites (Questions to Ask) How much information may be stored on a site? (That is, how much server disk space can it take up?) Who should have access to this sub-site? How long should information be stored on the sub-site? How long should the sub-site last?#SPcincy2012 on Twitterwww.sharepointcincy.com
Don’t touch SharePoint only when it’s on fire SharePoint is a very complex product and without regular check can take on a life of its own Left unchecked this can lead to problems that you don’t necessarily need to have So what are the tasks that you need to perform to insure that this doesn’t happen? www.sharepointcincy.com
Daily Tasks for the Farm Admin Check the event viewer on all servers Monitor server performance Check disk capacity Failed timer jobs Errors in crawl logs Errors with user profile sync Monitor backup jobs
Weekly Tasks for the Farm Admin SharePoint health monitor Use fiddler to check page load times Monitor network performance via NetMon Select a few random databases and perform a test restore to DEV Archive event logs Check for security updates on all servers
Monthly Tasks for the Farm Admin Use WinDiff or Xml Notepad compare previous web.config to current Compare previous baseline screenshots to current settings Update and compare performance baselines Analyze performance and growth data to project resource requirements Security audit of environment Test your DR plan