Getting SharePoint 2010 from Install to Production Ready Joshua Haebets

1. Getting SharePoint 2010 from Install to Production Ready Joshua Haebets Evolve Information Services

2. Who am I Joshua HaebetsPrincipal Consultant Evolve Information Services • Melbourne, Australia • @jhaebets on Twitter

3. Overview • You have run the wizard, now what • What needs changing before you let you users go into the environment • Or worse, developers and their code

4. What we are going to cover • Cleaning up database names • Centralising log files • Create site collection quotas • Web Application Settings • List throttling • SharePoint Designer • External List Limits • Search Service • User Profile Service • Cache • Health and Alerts

5. Get rid of the GUID’s • Does this look familiar? • It isn’t that hard to clean up

6. Demo Renaming databases

7. Rename Databases • For more information on renaming databases seehttp://technet.microsoft.com/en-us/library/ff851878.aspx

8. Centralise your logs • Separate partition so logs don’t kill your OS • Move to a separate disks for performance • All in one directory • SharePoint ULS Logs • SharePoint Usage Logs • IIS Logs

9. Demo Centralise Log Files

10. Quotas • In 2010 we set two quotas • Data – how much can be stored • Sandbox code – resources it can use • Be careful when setting code limits, it will disable the solution for the rest of the day once limits are reached. • Don’t forget to apply to existing site collections

11. Site Collection Quotas • Set limits of size and use of sandbox solutions • Send a warning at 80%, gives owners time to address the issue

12. Web Application Settings • General Settings • Quotas • Using Communicator, if not turn it off • Browser file handling, set to permissive otherwise PDF files will have to be downloaded • Modify the recycle bin to match you quotas • Will impact your quotas • File upload, is 50MB enough

13. List Item Limits • Resource throttling • How many list items can be returned in a query

14. List item limits • Can developers override the list limits? If so to what limit? • If you need a big query when can it be run? • ACL’s per list - How many unique permissions.

15. List Item Limits • How many items can be returned in a view • View default is 20, but user can override this. These are the joins in a query • Again, developers canoverride this, be careful

16. Demo List item limits

17. SharePoint Designer • Allowed? • Or restricted, no need to disable everything

18. Workflow • Can external people participate in workflows? • This will allow internal content to be emailed to 3rd parties

19. BCS limits • We are now talking about data from external systems, what does this mean to you • How many items are returned • Can developers return more, they know what they are doing right?

20. Demo Setting BCS limits

21. Search • Content access account • A service account dedicated to indexing content • Set permissions on User Profile Store • Moving the search index

22. PDF • iFilters • Adobe is free, but others are worth the $$$ • Icon • Copy icon to;c:\program files\common files\Microsoft Shared\Web Server Extensions\14\Template\Images • Update DOCIcon.xml with <Mapping Key=“PDF" Value=“pdficon.gif"/>c:\program files\common files\Microsoft Shared\Web Server Extensions\14\Template\XML • Add to file types

23. Audience Compilation • If you are going to use audiences, make sure they are compiling, more than once a week

24. Health and Monitoring • Disk space alerts • Turn off what you don’t need • Fix service accounts • It is easy to change the service accounts being used, keep everything isolated as much as possible

25. Health and Monitoring • Re-run health timer jobs until everything is clean • Get-SPTimerJob | Where {$_.Name -like "*Health*" -and $_.Name -like "*-any-*"} | Start-SPTimerJob

26. Demo Customising Health and Monitoring

27. User profile service • exclude disable accounts • removing useless properties (schools) • Reordering • Profile sub-types

28. Caching • BLOB Cache • Output Cache • Bit rate throttling • Object Cache, for cross list queries • Reduce calls to SQL • Make sure you have the disk I/O on the WFE/s

29. Blob Cache • Blob Cache • Images • CSS • JavaScript • Static media files • Pretty much anything that is going to be frequently requested BUT in-frequently changed • Ensure you have the disk I/O

30. Output Cache • Can be configured via the site settings menu • Will use system memory • Be careful of inconsistencies between WFE’s • Have separate profiles if you have Anonymous and Authenticated Users • Web.config settings will override UI site collection settings.

31. Bit rate throttling • Available in IIS 7 onwards • Serves media only at a rate that can be consumed by the user • If you are going to me playing media / videos this is a must have • Must have the BLOB cache setup first • Install IIS Media Services v2. • Recommended if serving media great than 10MB

32. Object Cache • Easy to activate • Harder to configure • Setup you accounts • Super Reader – Full Read on Web Application • Super User – Full Control on Web Application • By default • NT Authority\Local Service – Super Reader • System – Super User

33. Object Cache • Powershell to set rights $webapp = Get-SPWebApplication -Identity “Url of web application” $webapp.Properties["portalsuperuseraccount"] = "<SuperUser>“ $webapp.Properties["portalsuperreaderaccount"] = "<SuperReader>" $webapp.Update()

34. Backup • OOTB using Powershell or STSADM • SQL DB’s • Just the site collections • All of the above • 3rd Party tools

35. Kerberos – its not too late • It is best practice after all • Reduces network traffic – a little • Avoid double-hop issues • A must if you are going to work with external data. • Great article with instructions on how to move to Kerberos http://tinyurl.com/37a3b8n

36. Q&A

37. Questions Contact Joshua.haebets@evolve-is.com.au @jhaebets www.robotsdottxt.com www.linkedin.com/in/jhaebets