Downloaded 101 times
![Installation – Grey Wizard
• Initial
– Product Key
– Type of installation - Always SERVER
FARM
– Installation Type - Complete [Not
Single Server]
– Accept default file locations – index
files will stay on C:Program
FilesMicrosoft Office
Servers14.0Data
– At end NO Wizard
– Run OWA Setup
– Then, WIZARD! The wizard starts,
and yes, it’s OK for IIS to reset
during the wizard…
• Create a new farm
– Set farm account
– Pick configuration database,
Passphrase, CentralAdmin Port
(Conventions)
– Final confirm and let the wizard run](https://image.slidesharecdn.com/kmworld-admin101-111101151800-phpapp02/85/KMWorld-SharePoint-2010-Admin-101-44-320.jpg)
![Upgrade Techniques
• For smaller, braver sites, perform an in place upgrade.
– Site should be running at least MOSS 2007 SP2 (October 2009 CU even
better) to use preupgradecheck.
– All systems must be running Windows 2008 X64 - no in place upgrade
available for 32 bit SharePoint 2007.
• The alternate technique is to build a new 2010 system, 64 bit,
and then attach your 2007 databases.
– Build a new, empty SP2010 farm
– Build a new web app with a deleteable content db and drop the content
db in Central Admin
– Copy (detach/attach) the old content databases to a new server or
name.
– Prescan the database using the PowerShell command Test-
SPContentDatabase -Name [database] -WebApplication [url]
– Attach the new database to the web app using the command line:
stsadm -o addcontentdb -url [URL] –databasename [database] –
assignnewdatabaseid
– Review the migrated database content
• Alternatively, if you have more exotic upgrade needs (e.g. 2003-
2010), non SharePoint migrations (Notes, file systems), needs to
restructure content, etc. - third party tools help.](https://image.slidesharecdn.com/kmworld-admin101-111101151800-phpapp02/85/KMWorld-SharePoint-2010-Admin-101-48-320.jpg)
![Monitoring – WSS_Logging
• Query Database Views Directly
• Requires Timer Jobs Enabled
– Diagnostic Data Provider: Trace
Log
– Diagnostic Data Provider: Event
Log
• ULS Configuration Matters
• Database will GROW!
• Aggregates from ALL Servers
• Sample:
– SELECT * FROM
[WSS_Logging].[dbo].[ULSTraceL
og] WHERE CorrelationID =
'04377DAE-C2FD-4DBE-A57E-
101B3005059E'](https://image.slidesharecdn.com/kmworld-admin101-111101151800-phpapp02/85/KMWorld-SharePoint-2010-Admin-101-59-320.jpg)
![Some Useful PowerShell Snippets
• Visual Update a range of sites:
$webapp = Get-SPWebApplication http://sitename
foreach ($s in $webapp.sites)
{$s.VisualUpgradeWebs() }
• Site Backup
• Add MMS Term
$str = “SAMPLE”
$site = new-object Microsoft.SharePoint.SPSite("http://MYSITE")
$session = new-object
Microsoft.SharePoint.Taxonomy.TaxonomySession($site)
$termstore = $session.TermStores[“MYTERMSTORE"]
[…create group…]
[…create term set…]
$term = $termset.CreateTerm($str, 1033)](https://image.slidesharecdn.com/kmworld-admin101-111101151800-phpapp02/85/KMWorld-SharePoint-2010-Admin-101-64-320.jpg)
![Some Useful PowerShell Snippets II
• Create and configure a library
#Load the Sharepoint .net Assembly
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoin
t")
#set the url of the site collection to a variable
$siteurl = "http://msshome2010/"
$subsitename = "Marketing"
$newlibraryname = "NewLib"
$newlibrarydesc = "NewLib Description"
#create the new object passing the site collection URL, attach subsite
$mysite=new-object Microsoft.SharePoint.SPSite($siteurl)
$subsite = $mysite.openweb($subsitename)
#make the new library - 101 is the generic for DocumentLibrary
template
$subsite.lists.add($newlibraryname ,$newlibrarydesc, 101)
#open the new library and break inheritance
$mylib = $subsite.lists[$newlibraryname]
$mylib.BreakRoleInheritance($false)](https://image.slidesharecdn.com/kmworld-admin101-111101151800-phpapp02/85/KMWorld-SharePoint-2010-Admin-101-65-320.jpg)
Uploaded byChris McNulty
KMWorld SharePoint 2010-Admin 101
This document provides an overview and agenda for administering Microsoft SharePoint 2010. It discusses the common dilemma administrators face in taking on SharePoint responsibilities in addition to other roles. The agenda covers architecture, design, installation, upgrade, support functions like monitoring, backup, and optimization. It also addresses customization topics like content administration and best practices.
More Related Content
Similar to KMWorld SharePoint 2010-Admin 101
KMWorld SharePoint 2010-Admin 101
- 1. SharePoint 2010 –Admin 101 CHRIS MCNULTY
- 2. Chris McNulty • SharePointStrategic Product Manager at Quest Software • Formerly KMA SharePoint Practice Lead/Manager • Working with SharePoint technologies since 2000/2001 • 20 years consulting and financial services technology (Santander, John Hancock/Manulife, GMO, State Street) • MBA in Investment Management from Boston College Carroll School of Management • Write and speak often on Microsoft IW technologies (blogs & books) • Microsoft MCSE/MCTS/MSA/MVTSP • Hiking, cooking, playing guitar, colonial history, photography • My family: Hayley, three kids (16, 7, 5) and my dog Stan
- 4. About Home (4) Twitter hashtag: Copyright 2011 © Knowledge Management Associates, LLC. All rights reserved. Twitterhashtag: #spssan
- 5. Agenda • The dilemma • Architecture, Design & Planning • Installation and Upgrade • Support – Monitoring – Backup – PowerShell – Development Functions – Optimization & Patching • Customization – Content Administration • Best Practices
- 6. Congratulations! o You’re thenew SharePoint Administrator!!! o But… o You’re still responsible for: • Exchange • Active Directory • SQL • Desktop • Help Desk • Network/Firewall • Cooking & Cleaning • Etc.
- 7. The Dilemma o SharePointadministration is often an ‘add-on’ for other IT professionals (SQL DBAs, AD Admins, Exchange Engineers) o Time and focus are scarce resources! o Common pain points include • Upgrades are complex and hard to monitor • Dispersed workforce, little control of browsers and Office versions • Hard to understand and troubleshoot “behind the scenes” performance and capacity planning • Best practices not always understood or compared to system health • “All or nothing” administration means IT must be engaged for all admin responsibilities, even search
- 8. Microsoft SharePoint Server2010 … the bright frontier Eastern Long Island, July 4, 2010
- 9. Microsoft SharePoint 2010 Ribbon UI SharePoint Workspace SharePoint Mobile Office Client and Office Web App Integration Business Connectivity Services Standards Support InfoPath Form Services External Lists Workflow SharePoint Designer Sites Tagging, Tag Cloud, Ratings Visual Studio Social Bookmarking API Enhancements REST/ATOM/RSS Composites Communities Blogs and Wikis My Sites Activity Feeds Profiles and Expertise Org Browser PerformancePoint Services Insights Content Excel Services Chart Web Part Visio Services Web Analytics Enterprise Content Types Search Metadata and Navigation SQL Server Integration PowerPivot Document Sets Multi-stage Disposition Social Relevance Audio and Video Content Types Phonetic Search Remote Blob Storage Navigation List Enhancements FAST Integration Enhanced Pipeline
- 10.
- 11. Server Farm –Web Front End • Typical Roles: • http services • Search query • Scaling • Add servers to load balanced cluster • Performance Optimization • RAM • Easily virtualized 11
- 12. Server Farm -Application Server • Typical Roles: • Search index/crawl • Excel calculation • User profiles • Managed Metadata • Scaling • Add search servers and partitions • Move shared services to dedicated servers • Performance Optimization • CPU 12
- 13. Server Farm -Database • Typical Roles: • Data storage • SQL Reporting • Scaling • Add storage capacity • Performance Optimization • Disk I/O 13
- 14. Sizing - SingleServer • Typical Roles: • Small teams • Small pools of documents • Considerations • Performance & fault tolerance less of a concern • SQL & Web on same system • Search not a core function
- 15. Sizing - MediumFarm • Typical Roles: • 100-10,000 users • 10,000 – 1MM documents • Scenarios • Enterprise portal • Large scale collaboration • Broader applications platform • Larger external search pool • Mix and match internal external front end servers on common content databases
- 16. Sizing - LargeFarm • Typical Roles: • Large distributed enterprise users (10000+) • Large pools of documents (>1MM)
- 17. Top Level LogicalComponents • Farm level • Web applications Web Applications • Independent top level URLs http://intranet Site Collections • Run inside IIS pools • Consume shared Site Hierarchies Sites services and admin from the farm or other farms http://centadmin Single Sites (My Site) Lists Libraries Pages Web Parts • Site collections • Security, branding, database frontier • Contain single sites or site hierarchies • Sites • Group related SharePoint elements (lists, libraries, pages, web parts) 17
- 18. Mid-Level Logical Components(http://intranet) • Sites also contain lists, pages, and web parts
- 19. Logical Components • Highcapacity! • Maximums • 250,000 sites per site collection • 5,000 site collections per content DB • 200GB max content DB (single site collection) • >200GB post SP1 • 300 Content DBs per web application • 30MM documents/library • 2GB document size • 2011 News – 14TB Demo
- 20. Disk Sizing Content Search Initial Content Size XXX GB External Crawl Size YYY GB Initial User Pool U User Collab Size .25GB n YR Growth Rate – G% Archive Rate End Content Size XXX (1+G)n = ECS End Search Size YYY (1+G)n = ESS End User Collab Size .25 * U * (1+G)n = EUCS Content DBs ECS + EUCS Search DBs .05 * (ECS + EUCS + ESS) Search Index Files .05 * (ECS + EUCS + ESS) • Inputs: Size for SharePoint content and non-SharePoint content included in search • For DBs, don’t forget to consider transaction logs, disk dumps (if used for backup) which can add 1-3X. • In SAN or virtual environments, not all disk need be provisioned early
- 21. Memory Sizing • WebFront End (WFE) – 8GB minimum – 12GB larger – 16GB max • Application – 8-12GB • SQL – 8-20GB • HP Sizing Tool – http://h71019.www7.hp.com/activeanswers/Secure/54 8230-0-0-0-121.html • Don’t forget about the swap files (1-2X size of RAM)
- 22. Server Counts -Redundancy • WFE – Load balanced clusters – Internal – external isolation – 500-1000 simultaneous users • Application – Indexes Redundant – Distribute Queries • Database – Cluster – Mirroring – Log Shipping – EBS or RBS
- 23. Authentication Architecture • Classic Mixed Authentication Multi-Authentication – Zones mapped SharePoint Farm SharePoint Farm – Single URL for each Web Application Windows Web Application Windows Authentication authentication Zone: Default Authentication Zone: Default Regular label-callout text FBA Authentication method: Extended Web Application Extended Web Application Zone: Extranet FBA Zone: Extranet SAML Based Authentication Authentication FBA Authentication – e.g. Extended Web Application Zone: Intranet ... Extended Web Application Zone: Intranet Windows Authentication • Default: Windows Extended Web Application Zone: Internet ... Extended Web Application Zone: Internet ... • Forms (LDAP, SQL, Extended Web Application Extended Web Application ADAM) Zone: Custom ... Zone: Custom ... – Generate an NTToken to represent SPUser • Claims – Unified URL – Multiple sources (Windows, FBA, SSO) combine to generate a single SAML token to represent SPUser 24
- 24. Authentication Scenarios Mixed Mode s
- 25. Authentication Scenarios Multi Authentication s
- 26. Internet Topology –Edge Firewall • Traditional • Inexpensive • Simple Edge Firewall WFE App SQL AD • Only one firewall Internet • External traffic comes inside Internal Network internal network
- 27. Internet Topology –Perimeter • More complex • Duplicative networks, Edge Router/ WFE App SQL AD backup, AD Firewall Firewall • External traffic is Internet reserved • Larger server foot Perimeter Network Internal Net print (exposure) in perimeter • Internal users need domain trusts • Internal users access site across firewall
- 28. Internet Topology –Split Back to Back • Most complex • Intricate firewall rules • App, AD and search Edge Router/ Firewall WFE Firewall App SQL AD roles optionally in Internet perimeter • Optional internal WFE Perimeter Network Internal Network or internal users always cross a firewall • Crawl topologies important to avoid overtaxing the firewall
- 29. Internet Topology –Enhanced Techniques • Multi-farm • SSA farm • Content publishing
- 30. SharePoint Family Platforms SharePointFoundation 2010 Search Server 2010 & Express Microsoft SharePoint Server 2010 (MSS) • Standard & Enterprise • FIS-S FIS-E Project Server 2010 / Team Foundation Server FAST SharePoint 2007
- 31. Platform Basics • SharePoint2010 is a 64 bit only platform. Direct upgrades from 32 bit to 64 bit requires prep work. • Windows Server 2008 or Windows Server 2008 R2 X64 • SQL Server 2005 x64 SP3 CU3 Or • SQL Server 2008 x64 SP1 CU2 Or • SQL Server 2008 R2
- 32. Shared Service Applications •2007 Shared Services Provider has been broken up; each of its User Profiles elements is now a Search Metadata Shared Service Application Excel Calc • Mix and match them Visio singly or in groups, to match farm’s needs. • Crawl/index no longer a single server role • In 2010, administration can be delegated – Key targets: http://globalweb http://itportal Enterprise search, metadata, user profiles
- 33. Client/Browser Technology • InternetExplorer 7/8/9, Firefox and Safari are all supported. • Some support for Chrome • IE6 is not supported • Most other browsers are still supported for Internet configurations • Office 2010 includes optimizations for the new platforms • Offline Access – 2007: used Outlook 2007 and Groove – SharePoint Workspace 2010 integrates offline documents and lists
- 34. Office Web Applications •SharePoint 2010 provides a server version of Office applications – Office Web Access, or “OWA”. • In part, this enables simultaneous multiuser editing of Office documents: – Excel in OWA, not client – Word/PowerPoint on client only if file opened from a shared document library – OneNote client or OWA
- 35. Design Workshop – Group exercise – Medium software development and services
- 36. Design Workshop • Techcoto use SharePoint technologies to consolidate: – Mediawiki 50GB • Corporate content is out of date, hard to find and organize – Internal WSS 3.0 50GB • Internal SharePoint sites used mostly as corporate directories (e.g., corporate “Facebook”-type page). – GoLive Sites 100GB • Sites set up using WSS2.0 for collaboration among integrated project teams working on professional services group (PSG) engagements. – Extranet 800GB • Sites set up for product release and technical support teams where code, log files, and other data can be shared in a controlled, secure environment. – Search against 10TB of legacy file system data • Other inputs – About 200-300 internal users – About 200 external consumers of data – Allowing users to login against either Windows AD or a separate user store for external users – Emailing documents directly to SharePoint libraries – Enabling self-service user password management
- 37. Design Workshop -Physical User Requests Internet Usage Network Load Balancer Web Front End Servers (WFE) Serve as http: URL connectionn points WFE 2x dual core, 64-bit 8 GB RAM Local Storage (ca 80-200GB) Win 2008R2 App/Index/Query Server Serve purpose of offloading indexing And query activities from WFE Need for one or more driven by detailed search requirements, external data sources to be indexed, application support External data stores Index to be searched 2X dual core (e.g., file shares, 64-bit Web sites, 8 GB RAM LOB applications, etc.) Local Storage (ca. 1.5TB) TBD Win 2008 R2 Microsoft SQL Server Database Servers Store SharePoint data and content. Single vs clustered MSSQL DB is dependent on: corpus of data, tolerance for downtime, and desired performance. MSSQL DB 2x quad core 64-bit 8-12 GB RAM SAN – RAID 5/10 Storage 2.5-3TB/TBD Win 2008 R2
- 38. Design Workshop -Logical App Pool App Pool App Pool Internal External Administrative Claims Web Classic Classic Application Claims App: Windows Only Web App Web App Windows/FBA Windows Site Site Site Site Central Content Collection Collection Collection Collection Archives Admin Types Hub Extranet PSG/GoLive Intranet MediaWiki SC/Database SC/Database SC/Database SC/Database Database Database Database Database Database Database PSG Extranet Intranet Mediawiki
- 39. Design Workshop -Questions • Third Party Tools • Database Structure or EBS/RBS • URL design and shareability • 10TB Indexing
- 40. Office 365 • Formerly“BPOS” • Reduced Functionality in Shared Environments • Pricing and capacity vary from self-hosted material • Following material is subject to change:
- 41.
- 42.
- 43. Installation - Prerequisites •Servers: – Windows 2008 R2 X64 Enterprise Edition – SQL Server 2008 R2 x64 • Service Accounts – spfarm (Farm acct; local admin on the SharePoint servers and either sa or dbcreate, dbowner and security admin on the SQL server.) – svcsql (SQL Server service acct) – sppool (IIS pool acct) – spcrawl (Search accts) – spadmin Interactive admin (install account; local, site collection and farm admin privileges) • Install as SPAdmin • Install Software Prerequisites - Checks for following elements: – Application Server Role, Web Server (IIS) Role, Microsoft SQL Server 2008 Native Client, Hotfix for Microsoft Windows (KB976462), Windows Identity Foundation (KB974405), Microsoft Sync Framework Runtime v1.0 (x64), Microsoft Chart Controls for Microsoft .NET Framework 3.5, Microsoft Filter Pack 2.0, Microsoft SQL Server 2008 Analysis Services ADOMD.NET, Microsoft Server Speech Platform Runtime (x64), Microsoft Server Speech Recognition Language - TELE(en-US), SQL 2008 R2 Reporting Services SharePoint 2010 Add-in
- 44. Installation – GreyWizard • Initial – Product Key – Type of installation - Always SERVER FARM – Installation Type - Complete [Not Single Server] – Accept default file locations – index files will stay on C:Program FilesMicrosoft Office Servers14.0Data – At end NO Wizard – Run OWA Setup – Then, WIZARD! The wizard starts, and yes, it’s OK for IIS to reset during the wizard… • Create a new farm – Set farm account – Pick configuration database, Passphrase, CentralAdmin Port (Conventions) – Final confirm and let the wizard run
- 45. Installation – WhiteWizard? • Pros – Easy – All SSAs Configured – Saves time and PowerShell hand tooling of SSAs • Cons – My Sites setup in same app and DB as primary – Database Names are default, GUID happy – Kills kittens (ask SharePoint 911!) • What it does – Sets up service acct for SSAs and other services (sppool) – Sets up a port 80 web app with a My Sites Host sub-site collection in WSS_Content database
- 46. Typical Service Placement App Web Server Service Access Database Service Application Registry Service Servers Y Y Servers N Y • Guidelines, not rules • Minimize service on Business Data Connectivity Service Y N Central Administration Y Y Claims to Windows Token Service N N Document Conversions Launcher Service N N Document Conversions Load Balancer Service Excel Calculation Services N Y N N WFEs Lotus Notes Connector N N • Similar Decisions Managed Metadata Web Service Y N Microsoft SharePoint Foundation Incoming E-Mail Y Y Microsoft SharePoint Foundation Sandboxed Code Service N N about Feature Microsoft SharePoint Foundation Subscription Settings Service N N Microsoft SharePoint Foundation Web Application N Y Microsoft SharePoint Foundation Workflow Timer Service Y Y PerformancePoint Service PowerPoint Service Y Y N N Activations for Farm, Search Query and Site Settings Service Y Y Secure Store Service SharePoint Foundation Search Y N N N Site Collections, Sites SharePoint Server Search Y Y SQL Server PowerPivot Service User Profile Service N Y Y N – (Following Slides For User Profile Synchronization Service Y N Visio Graphics Service Web Analytics Data Processing Service Y Y N Y Examples) Web Analytics Web Service Y Y Word Automation Services Y N Word Viewing Service Y N
- 47. Predictable Upgrade • Threepaths – In place – Database upgrade – Third party tools • Process – Pre-upgrade checker – Visual Upgrade – Resumable upgrade – Progress reports – Parallel DB upgrades
- 48. Upgrade Techniques • Forsmaller, braver sites, perform an in place upgrade. – Site should be running at least MOSS 2007 SP2 (October 2009 CU even better) to use preupgradecheck. – All systems must be running Windows 2008 X64 - no in place upgrade available for 32 bit SharePoint 2007. • The alternate technique is to build a new 2010 system, 64 bit, and then attach your 2007 databases. – Build a new, empty SP2010 farm – Build a new web app with a deleteable content db and drop the content db in Central Admin – Copy (detach/attach) the old content databases to a new server or name. – Prescan the database using the PowerShell command Test- SPContentDatabase -Name [database] -WebApplication [url] – Attach the new database to the web app using the command line: stsadm -o addcontentdb -url [URL] –databasename [database] – assignnewdatabaseid – Review the migrated database content • Alternatively, if you have more exotic upgrade needs (e.g. 2003- 2010), non SharePoint migrations (Notes, file systems), needs to restructure content, etc. - third party tools help.
- 49. Upgrade Preparation • AdditionalPrepwork – Content pruning – Database alignment • stsadm-o mergecontentdbs • DB Attach – Preinstall Required Features – Stsadm –o addcontentdb – databasename DBNAME –url URL – assignnewdatabaseid – PowerShell Mount- ContentDatabase – Test, test, test!
- 50. Pre-Upgrade Check • SharePoint 2007 SP2 minimum, October 2009 CU best – STSADM.exe –o preupgradecheck • Documentation – All servers and components in the farm, and whether the servers meet 64-bit hardware/OS requirements – Alternate access mapping URLs – A list of all site definitions, site templates, features, and language packs that are installed in the farm. – Unsupported farm customizations (such as database schema modifications). – Database or site orphans – Missing or invalid configuration settings in the farm (missing Web.config file, invalid host names, invalid service accts). – Whether the databases meet the requirements — for example, databases are set to read/write, and any databases stored in Windows Internal Database and larger than 4 GB.
- 51. IT Pro Investments– Visual Upgrade
- 52. Batched Visual Upgrade • PowerShell allows a range of sites in a web application to be Visually Upgraded at once: $webapp = Get-SPWebApplication http://sitename foreach ($s in $webapp.sites) {$s.VisualUpgradeWebs() }
- 53.
- 54. Monitoring and Operations Monitoring (56) Twitter hashtag: #sptechcon Copyright 2011 © Knowledge Management Associates, LLC.
- 55. Proactive Issue Resolution •Developer Dashboard – Empower developers and users • Integrated Health Analyzer – Runs when necessary – Alerts anomalies – Fixes when it can • Web Analytics – User usage – Resource usage
- 56. Logging, Monitoring, andAlerts • Unified Logging • Out-of-the-box ULS Logs reports Windows Events • Richer Web Analytics • Open Schema Page requests Logging DB • SCOM Integration • PLUS Feature Logging – Developer Dashboard Health data – Health Analyzer
- 57. Monitoring – General •Monitoring – SCOM – Central Admin • Health Analyzer – Site Collection Web Analytics – Developer Dashboard • stsadm –o setproperty –pn developer-dashboard –pv OnDemand • (Get- SPFarm).PerformanceMonitor.DeveloperDashboardLevel = "OnDemand" – Troubleshooting • Correlation ID – One GUID to rule them all! • ULS Logs, Event Logs, Performance Monitor – OR • WSS_Logging DB
- 58. Developer Dashboard Improve customizedsolutions with the Developer Dashboard
- 59. Monitoring – WSS_Logging •Query Database Views Directly • Requires Timer Jobs Enabled – Diagnostic Data Provider: Trace Log – Diagnostic Data Provider: Event Log • ULS Configuration Matters • Database will GROW! • Aggregates from ALL Servers • Sample: – SELECT * FROM [WSS_Logging].[dbo].[ULSTraceL og] WHERE CorrelationID = '04377DAE-C2FD-4DBE-A57E- 101B3005059E'
- 60. Backup/Recovery • Third PartyTools • Recycle Bin • Granular / Site Collection Backup (UI) – *.bak file – Restore-SPSite • Unattached Recovery – Browse unattached content database – Account needs DB permissions – Database need not be on the same server! – No more granular than list or library! – Browse Content • Export Site or List – Export as a CMP file – PowerShell restore • PS: Import-SPWeb http://msshome2010 –Path C:ListRecovery.cmp • SQL Backup • SharePoint Backup (UI or script)
- 61. STSADM Backup @echo off echo ================================================== echoBackup the farm echo ================================================== @SET stsadm="C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12BINstsadm" rmdir /S /Q "spsql08spbackupfarmold" ren "spsql08spbackupfarm" "farmold" md "spsql08spbackupfarm" %stsadm% -o backup -directory "spsql08spbackupfarm" - backupmethod full echo complete
- 62. PowerShell Backup # NOTNEEDED write-output write-host ================================================== write-host Backup the farm write-host ================================================== Add-PSSnapIn Microsoft.SharePoint.Powershell Remove-Item -Path "C:PSBackupfarmold“ -recurse Rename-Item -Path "C:PSBackupfarm" -NewName "farmold" New-Item -type directory -path C:PSBackupfarm Backup-SPFarm -directory "C:PSBackupfarm" - backupmethod full –verbose –percentage 5 Write-host Backup complete
- 63. PowerShell • SharePoint Shellvs. Base Shell – Add-PSSnapin Microsoft.Sharepoint.Powershell • Command -? – Get-Help Command – Get-Help Command –examples • Pipe – Get-Command –Noun SP* – Get-Command – Noun SP* | Select Name – Get-Command – Noun SP* | Select Name | Out-File Commands.txt • Get-SPSite –limit all | Get-SPWeb –limit all | Select URL, webtemplate | Out-GridView – WindowsPowerShell Integrated Scripting Environment to allow Out-GridView
- 64. Some Useful PowerShellSnippets • Visual Update a range of sites: $webapp = Get-SPWebApplication http://sitename foreach ($s in $webapp.sites) {$s.VisualUpgradeWebs() } • Site Backup • Add MMS Term $str = “SAMPLE” $site = new-object Microsoft.SharePoint.SPSite("http://MYSITE") $session = new-object Microsoft.SharePoint.Taxonomy.TaxonomySession($site) $termstore = $session.TermStores[“MYTERMSTORE"] […create group…] […create term set…] $term = $termset.CreateTerm($str, 1033)
- 65. Some Useful PowerShellSnippets II • Create and configure a library #Load the Sharepoint .net Assembly [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoin t") #set the url of the site collection to a variable $siteurl = "http://msshome2010/" $subsitename = "Marketing" $newlibraryname = "NewLib" $newlibrarydesc = "NewLib Description" #create the new object passing the site collection URL, attach subsite $mysite=new-object Microsoft.SharePoint.SPSite($siteurl) $subsite = $mysite.openweb($subsitename) #make the new library - 101 is the generic for DocumentLibrary template $subsite.lists.add($newlibraryname ,$newlibrarydesc, 101) #open the new library and break inheritance $mylib = $subsite.lists[$newlibraryname] $mylib.BreakRoleInheritance($false)
- 66. DEMO • Monitoring • Developer Dashboard • Health Analyzer • PowerShell
- 67. Visual Studio 2010Support Extensibility for SharePoint artifacts Support for SharePoint Import solutions from Sandboxed Solutions SharePoint Designer, including Workflow
- 68. Development Continuum Business Analyst/Process Designer/IW/Power User Professional developer Designer Import WSP Package Export
- 69. Development Support –Three Regions Development Staging/Test Production • often internal to developers • no Visual Studio, no MS Office • optimized hardware • problem reproduction that • match/mirror production as configurations require advanced inspection closely as possible; match • highly secure tools (e.g. Visual Studio) are hardware/system performance • no use of user rotating done here as closely as practical password accounts as service • permissions can be looser, • security permissions match accounts may have multiple production • changes here can only be environments for multiple • any sensitive data copied here delivered and deployed from developers stays under production-grade source control and according • sensitive data from production controls to production release methods cannot be copied here without • test accounts should be masking or customer signoff created in a separate OU if • changes here can be deployed possible ad hoc • changes here can only be delivered and deployed from source control and according to production release methods
- 70. Optimization Optimization (72) Twitter hashtag: #sptechcon Copyright 2011 © Knowledge Management Associates, LLC.
- 71. Patching • Release Cycle – Major Service Packs 6-12 Months – Aggregated Cumulative Updates every two months. • Announcements – Microsoft usually announces them on the SharePoint Team MSDN blog, http://blogs.msdn.com/b/sharepoint/ and consolidates the latest patch news at: http://technet.microsoft.com/en- us/sharepoint/ff800847.aspx – Patch versions and build numbers on my blog at http://blogs.kma-llc.net/microknowledge/version-build- numbers/ • Service Packs are usually directly available for download. • For Cumulative Updates, you have to supply an email address, and you’ll be sent a link to a password encrypted download file.
- 72. Patching – HighLevel Process through August 2011 • SharePoint Foundation Patch • SharePoint Server Patch • Run SharePoint Products and Technologies Wizard • (Or psconfig) • Sequential Application to Central Admin, Application Server(s), Web Front Deploy End Servers
- 73. Patching – HighLevel Process After August 2011 • Separate patch longer needed – single patch CU now available Patch • SharePoint Foundation • OR SPF/Server Patch • OR SPF/Server/Project Server • Run SharePoint Products and Technologies Wizard • (Or psconfig) • Sequential Application to Central Admin, Application Server(s), Web Front Deploy End Servers
- 74. SQL Maintenance • Backups – Local Disk – easy but storage intensive – Agents – remote, requires extra software • RBS Maintenance – BLOB Orphans • Log Sizing – Full logged (default) generates huge t-logs – Simple doesn’t but prevents point in time restore • Maintenance Plans
- 75. Optimization • IIS BitRate Throttling (Video) – Part of IIS Media Services 2.0 or greater – Download http://www.iis.net/download/BitRateThrottling – Configured through IIS Manager • Large File Upload Support: – Central Admin: 600MB Upload Size – IIS7 Connection Timeout 65536 seconds – Web app web.config = change line to • <httpRuntime maxRequestLength="2097151" executionTimeout="999999" /> – in 14hivetemplatelayoutsweb.config, change above line to same – Finally, as per http://support.microsoft.com/kb/944981/en-us add section to web.config to allow 600MB content length (it’s a new requirements in IIS7). • <system.webServer> • <security> • <requestFiltering> • <requestLimits maxAllowedContentLength="629145600"/> • </requestFiltering> • </security>
- 76. Optimization • Disk-based BLOBCaching – Local store for audio/video, PDF other frequent read only files – Edit in Web.config (C:Inetpubwwwrootwssvirtualdirectories...) – <BlobCache location="" path=".(gif|jpg|jpeg|jpe|jfif|bmp|dib|tif|tiff|ico|png|w dp|hdp|css|js|asf|avi|flv|m4v|mov|mp3|mp4|mpeg|mpg|rm|rmv b|wma|wmv)$" maxSize="10" enabled="false" /> • Location = Local Disk Location • maxSize = GB • Enabled = true • Different from RBS/EBS!
- 77. SharePoint Customization Ribbon UI SharePoint Workspace SharePoint Mobile Office Client and Office Web App Integration Business Connectivity Services Standards Support InfoPath Form Services External Lists Workflow SharePoint Designer Sites Tagging, Tag Cloud, Ratings Visual Studio Social Bookmarking API Enhancements REST/ATOM/RSS Composites Communities Blogs and Wikis My Sites Activity Feeds Profiles and Expertise Org Browser PerformancePoint Services Insights Content Excel Services Chart Web Part Visio Services Web Analytics Enterprise Content Types Search Metadata and Navigation SQL Server Integration PowerPivot Document Sets Multi-stage Disposition Social Relevance Audio and Video Content Types Phonetic Search Remote Blob Storage Navigation List Enhancements FAST Integration Enhanced Pipeline
- 78. Enterprise Content Management “SENTENCESTRUCTURE” Adjective Noun Verbs Example Red Spreadsheets Copy to Folder SharePoint 2007 -- Content Type “Copy” SharePoint 2010 Managed Documents Copy, Link, Move, Metadata Update (Content Types and/or Find and use! Taxonomy)
- 79. What is metadata? •Literally, “after data” • In practical usage, it means data about data • For SharePoint, it usually means data that describes or classifies: – other data (lists) – documents (libraries)
- 80. 2010 Managed MetadataService • Centralized enterprise repository for tag hierarchies and keywords • Publish and subscribe model for distributed content types
- 81. Using MMS Taxonomy •Add from common button • Select from list tor type-ahead • Consume from views, navigation, and search!
- 82. Folksonomy • Informal listof ad-hoc tags or terms, usually built up over time through user defined keywords • Centrally stored in the MMS application • Easily enabled option for all document libraries • Can also be applied to content outside SharePoint
- 83. Taxonomy Administration • Creatingand managing terms and term sets • Attaching to a library • Taxonomy navigation
- 84. Taxonomy Operations • Termsets can be copied, relocated, and reused from existing terms • Terms can be copied, reused, merged, deprecated, etc. • Keywords (folksonomy) can be moved into a managed term set or deleted
- 85. DEMO • MMS Usage
- 86. Enterprise Content Management • Approvals and Versioning • Content Aggregation • Drop-off Library & Content Organizer • Digital Media Management • Records Management & Records Center – In Place vs. Records Center • Hold and Discovery • ILM and Retention Policies
- 87. Versioning and Approval •Classic product functions • User options • Interactive approval • Workflow approval
- 88.
- 89. Rules-based Routing • Drop-offLibrary and Content Organizer • Move content based on content type • Move content based on metadata and properties
- 90. Digital Media ContentManagement
- 91. Records Management andHolds • In place vs. Records Center • Enablements – Site Collection Feature “In Place Records Management” – Records Center – Custom Site Collection – Hold and eDiscovery Site Feature – Custom Send To Actions (Cent. Admin) • Move, Copy, Move and Leave Link
- 92. Information Lifecycle Management •Default behavior is defined for Content Types (MMS) • Redefine (override) at library/folder level • Rich array of functions and custom workflow
- 93. All together now • Multiuser editing • Work in SharePoint Workspace Initial Collaboration • Work in OWA • Send from Document Center and leave behind a link • Look for PowerPoint Files Drop-off Library • Require a Department • If Marketing Send to Home Page Library Routing • If Not Send to Presentation Archive • Marketing Forever Retention • Others Three Months
- 94. DEMO • SharePoint ECM
- 95. So many documents,so little time…
- 96. ECM Pyramid Actions 100s Documents 1000s Descriptions, Tags, Classifications 10 X 1000s
- 97. Classification challenges • “Verbs”- Actions – ECM – Search, navigation, findability • “Nouns” – Documents • “Adjectives” - Classifications – Manual data entry • The cost of the * – Custom development • Text vs. context • Event receivers • Workflow models • FAST Pipeline – Auto-classification
- 98. ECM Cheat Sheet Function Feature Scope Where to configure it Content Organizer Site Site Settings | Content Organizer Rules Hold and eDiscovery Site Site Settings | Hold and eDiscovery Section In place Records Site Collection Context Menu | Management Compliance Details Send to Records Center Define in Central Admin Central Admin: General Settings | Send TO Connections ILM Variable Content Type definition; or override at library/folder level in library settings – Information Management Policy Settings
- 99.
- 100. Troubleshooting – TopSupport Questions • Users Receive “Cannot Connect to Configuration Database” Web Page – SharePoint farm account is locked out • No one can upload anything but site is up – Database disk volume is full – check transaction logs, backups – In virtualized environment, host file systems may be full • I can’t find a document I think I should see; Someone can’t see a file I just uploaded – Security and permission variations – Document “movement” (a/k/a ECM) try search by name or Document ID. Check ECM logs/audits – Confirm permissions, and make sure document is checked in (Required properties may be missing)
- 101. Troubleshooting – MoreSupport Questions • Repeated requests to re-enter Windows credentials – Add to Local intranet zone, add site, custom level, automatic login with current user name and password (it’s the last thing in the item list) – OR Trusted sites • My workflow didn’t start – Recycle timer service – “FixSharePoint.exe” = IISReset & Timer Service Recycle • I’m not seeing the right search results – Confirm that crawls are running and complete by checking crawl logs; restart a full crawl if crawls finish OK • I need a file back that I deleted – Recycle Bin Recovery – Use Backup & Restore
- 102. Miscellaneous Tips andTricks • Bad web parts on page – ?Contents=1 on end of URL • HyperV & DiskPart – From the run menu type "diskpart.exe" to enter the command line utility to resize disk partitions in Windows Server 2003. – The command list volume will show you all the available volumes. – Select your volume as shown below. select volume 1 corresponds to the "D" volume. – Extend the volume with the extend command; the partition will be immediately extended under the Disk Management snap in. • User Profile Sync – DirSync permissions in AD are essential (Replicating Directory Changes ) • PSCONFIG for a stuck wizard – psconfig.exe -cmd upgrade -inplace b2b -wait • 14HIVEbin on PATH • How big is that site collection anyway? – Site Settings | Site Collection Analytics | Scroll down to Inventory and choose Storage Usage • How do I make a bigger template? – stsadm -o setproperty -propertyname max-template-document-size -propertyvalue size_in_bytes • Save site as template – To save any site as a template, just go to Site Actions | Site Settings | Save Site as template. This saves the site as a standard .WSP package in the Site Collection Solutions Gallery (/_catalogs/solutions/Forms/AllItems.aspx) • Auditing – In Central Admin | Security, configure Information Management Policy (/_admin/Policyfeatures.aspx). Make sure Auditing is Available – At the Site Collection Audit Settings screen (in Site Collection Administration) select the events you want to audit – Site Setting | Site Collection Administration | Audit Log Reports • Service Account Management in Central Admin – Security | Managed Service Accounts • When all else fails – web.config!!!!
- 103. Where Governance Begins? Portal Lighter governance Dept Sites Higher Visibility Project/Team Sites Personal / My Sites
- 104. Seven Deadly Sinsfor the SharePoint Professional
- 105. Seven Deadly Sins •No SQL maintenance plans • Default names for every database (WSS_CONTENT_12345abc…) • No patching • One environment for everything • One acct for everything • Single server install with SQL Express • Runaway content database size
- 106. Seven Virtues forthe SharePoint Professional
- 107. Seven SharePoint Virtues •Security Applied via AD Groups and SharePoint Groups • Review System Health • Test Restore and Recovery • Monthly Web Analytics Review – Usage, Storage, Search • PowerShell instead of STSADM • Governance • Use ECM, MMS, Clients, Archiving and Training to Keep Content in SharePoint, reduce accidental duplication and keep searching and browsing fresh
- 108. Congratulations! o You’re thenew SharePoint Administrator!!! o And now o You understand (maybe): • Design and Architecture • Installation and Upgrade • Support, Maintenance and Optimization • PowerShell • Customizations • Troubleshooting • Best Practices
- 109. Resources • From Microsoft: – SharePoint 2010 site: http://sharepoint.microsoft.com – SharePoint Team Blog: http://blogs.msdn.com/sharepoint/default.aspx – From KMA – Webinars, white papers and blogs at www.kma-llc.net
- 110. 114 ©2011 Quest Software,Inc. All rights reserved..
- 111. • Questions? • Evaluations •Next Steps – SPS Denver Nov 2011 – SPS South Florida Dec 2011 – SPS Austin, SPTechCon San Francisco, Project Conference 2012, TEC2012 San Diego
- 112. Thank you… • Email chris.mcnulty@quest.com • Blog http://www.chrismcnulty.net/blog • Also http://blogs.kma-llc.net/microknowledge • Twitter: http://twitter.com/cmcnulty2000 • LinkedIn:http://www.linkedin.com/in/cmcnulty
Editor's Notes
- #7 Typical
- #8 Walkthrough examplesWe sometime work closely w business, sometimes ITSometimes IT has dedicated SP resourcingSample – Midwestern manufacturer – sponsor is a program manager (electronics) – core team includes C# developers for their product team, some knowledge of SQL, no other time
- #10 Let’s break down investments by workloads…SitesCommunitiesContentSearchInsightsComposites
- #34 IF YOU DON’T NEED IT – DON’T USE ITPLUS YOU CAN GIVE IT AWAY!
- #45 These are the domain accounts that are generally needed in a standard SharePoint installation. These accounts are shown with suggested names; names can be adjusted to confirm to any corporate naming standard for service accounts. For example, you may wish to designate ALL service accounts with a sv- or svc- prefix. Similarly, you may want to designate “regions” with a suffix, such as –dev, -tst, or –prd. Likewise, if you have already established SQL service account conventions, those accounts are fine as well.
- #72 Why: Protecting customer assets Assuring smooth transition of developed solutions to production environment Minimizing incidents/downtime in production environment Best practices have a permissions barrier between development and production environments ConceptsProduction regions should be optimized for maximum performance and reliability. Test or staging regions should match production as closely as is practicalAvoid the use of shared physical assets across the three regions. Although SharePoint and SQL can support multiple instances on the same physical hardware, they also share access to some .NET code libraries (.e.g. the global assembly cache, or GAC), that make it impossible to release code to testing without also installing it into production. Virtualization can provide federation without additional physical hardwareChange management requires acceptance and advance approval of scheduled changes to production environmentsAll changes MUST be documented and captured in a configuration master database and/or documentationReleases by release engineers with temporary permission accounts (“firecall”)
- #75 b
- #80 Let’s break down investments by workloads…SitesCommunitiesContentSearchInsightsComposites
- #91 Doc sets adds cap to bundle together types of content as a single entityAdd metadata to doc setAdd policy to doc set
- #93 1) Media is more native2) Shows streaming of video3) OOB media webpart
- #94 More users are now part of the RM scenarioDeclare rec in team siteDisp pol is broken down in to stagesCreateArchiveElimination
- #107 SharePoint 2010 provides more opportunities, and more importance for reengaging users and sponsors about governance issues than beforeMajor toolsSandbox codeQuery governorsSharePoint DesignerNow free (since 2008)Allowed or denied or restricted - PlaceholderMainSocial tagging and ratingsI like it/I hate itRatings and adverse feedbackECMRecords management - In place vs. Record CenterContent Organizer etc.Who controls the lifecycle?QuotasWho gets a site?
- #108 Keep?
- #109 No SQL maintenance plansAll gardens need weeding. SQL databases need tending too. Left on their own, content databases and config databases will generate runaway transaction logs. Combined with overzealous local backup retention plans and you’ll quickly fill up you storage. Take a little time to understand Full Recovery vs. Simple Recovery in SQL. Or, more importantly, use a maintenance plan to backup and truncate your logs – it’s not that hard.Default names for every databaseThe default database name for a SharePoint content database is “WSS_Content”, and if you take the defaults, all subsequent databases will take the default format WSS_Content_[really-long-GUID]. Don’t do this – down the road, during backup, restore or SQL maintenance operations you'll be constantly jumping into Central Admin to figure out which sites use “WSS_Content_abdc1234-1111-2222-878adf0e”. Much better to name the databases according to a person- friendly standard – “WSS-Content-HRPortal”, etc. Even if it’s obvious to you, it may not be obvious to your DBA or someone else who has to support it in the future. No patchingGiven my crazed obsession with SharePoint version numbers (see http://blogs.kma-llc.net/microknowledge/version-build-numbers/) this is not a stretch. Microsoft has made it as easy as possible to stay in sync with the latest patches, Service Packs and Cumulative Updates. Do you need to update your systems every two months? Probably not. Should you still be running the nearly four year old RTM version of SharePoint 2007? Definitely not.One environment for everythingDon’t build a development environment. Don’t build a test environment. Just make all changes live, in production. What could ever go wrong?One acct for everythingBig, big no-no here. If you don’t pay attention, you may be tempted to use one master account for the SQL service, for the installation, for the farm account, for search, for content access, and for the IIS pools. Then, when you administer the site, it’s always easy to work around security restrictions by handing out those account credentials to a wide group of people. Next thing you know, someone forgets the password and locks out the account. The great news is that you don’t need to build a monitoring system for this alert, because everyone and I mean everyone, will get the dreaded web page that reads:Cannot connect to configuration database.So don’t give out the admin accounts, and, especially, don’t reuse the farm account.Single server install with SQL ExpressIf you don’t pay close attention on the original installation sequence, you may pick a “standalone” single server installation. You’re starting with only one server for now, right? Unfortunately, you’ll wind up with a server that can’t be expanded, running SQL Express Edition. And limited to 4GB of content database size. Well, at least you’ll avoid the next problem:Runaway content database sizeMicrosoft recommends that SharePoint content databases stay below 100GB (200GB if it’s the only content DB in a SharePoint 2010 site collection). But SharePoint doesn’t stop you from adding more – it’s a recommendation for optimal user performance. However, I’ve seen too many installations that grew grew grew to 250GB, 500GB or more. Plan your content database sizes in advance of critical sizes. You can add databases and site collections to create more manageable units, or use Remote Blob Storage (RBS) to pull those file of attachments out of the databases and into external storage, reducing file sizes.
- #110 Keep?
- #111 Use SP to managed SPBusiness owns home page
- #112 Typical