SharePoint Speedmetal for Admins by Chris McNulty - SPTechCon


Published on

Technical Class:
Monday, March 4
4:00 PM - 5:15 PM

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Who is Quest? Founded in 1987 we have over 25 years of experience simplifying common IT challenges Some of the largest customers in the world depend on Quest products We have a history of innovation and acquisition that strengthen our product portfolio to deliver increased customer value We’ve historically invested more than our competition, allowing us to out-innovate our peers Nearly 4,000 employees worldwide
  • Typical
  • 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
  • Let’s break down investments by workloads…SitesCommunitiesContentSearchInsightsComposites
  • 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.
  • b
  • 1. Do not manage the Distributed Cache service through either the Services MMC snap-in or the generic Windows Server AppFabric tools! Use SharePoint Central Administration and the SharePoint PowerShell cmdlets designed for the purpose.2. Anytime you need to shut down the Distributed Cache service on a cache host (via Stop-SPDistributedCacheServiceInstance cmdlet), such as to remove a cache host from its cache cluster, use the –Gracefulswitch to avoid data loss. Although it takes longer to shut the service down this way, cached items are preserved (i.e., transferred to another cache host) and end-users get a better experience.3. If your SharePoint Servers (specifically, your cache hosts) are virtual machines (VMs), do not use dynamic memory for those VMs. Dynamic memory allows you to squeeze “more” out of a hardware host, but it can cause problems for the Distributed Cache service since actual physical memory assigned to a VM is variable. For Distributed Cache hosts, used fixed memory allocations in your VM configurations.4. When adding and removing cache hosts to a cache cluster, be aware that the Distributed Cache service depends on Internet Control Message Protocol (ICMP) for operation – likely to ping other cache hosts to determine their availability and readiness. This may require you to make firewall changes in your environment and on your cache hosts.5. All cache hosts in a cache cluster should be configured with the same Distributed Cache service memory allocation, and that value shouldn’t be less than 8GB per server.6. Don’t allocate more than 16GB of memory to the Distributed Cache service on any single cache host – even if the system has more RAM available. Allocating more than 16GB of memory may cause the server to stop responding for periods in excess of 10 seconds.7. The maximum number of cache hosts per cache cluster is 16.8. The Distributed Cache service on a cache host throttles requests when memory consumption approaches 95%. Until memory utilization levels drop back to (approximately) 70%, cache read and write requests are not accepted. Keep an eye on memory usage and the Event Log for signs that a server is memory starved and consider adding additional cache hosts in such circumstances.9. The SharePoint 2013 Health Analyzer has a few rules that will surface issues with the Distributed Cache service. Keep an eye on Central Administration and Health Analyzer Reports.
  •  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 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.
  • Use SP to managed SPBusiness owns home page
  • Typical
  • Guide you around the world, or, ultimately guide you safely homeWe have to keep that light burning
  • SharePoint Speedmetal for Admins by Chris McNulty - SPTechCon

    1. 1. SharePoint SpeedMetal – Admin 101SPTechCon San Francisco 2013Chris McNulty
    2. 2. 25 years Since 1987, Quest has offered a broad and deep selection of products that target common IT challenges 100k 30 Quest products provide over Over thirty acquisitions have 100,000 customers with IT solutions strengthened our product portfolio every day18%Quest has driven innovation by 3,900 Quest employees develop solutions in over sixtyregularly investing 18% or more in offices throughout the worldR&D
    3. 3. Dell Software | SharePoint3 Confidential SharePoint
    4. 4. Chris McNulty • SharePoint BU at Dell Software • 10+ years with SharePoint • 20 years consulting (led KMA SharePoint practice) and financial services technology (Santander, John Hancock/Manulife, GMO, State Street) • MBA in Inv Mgmt from Boston College • Write and speak often on Microsoft IW technologies (blogs & books) • MCSE MCTS MSA MVTSP MCC • Hiking, cooking, playing guitar, colonial history, photography • My family: Hayley, three kids (18, 9, 6) and my dog Stan4 Confidential SharePoint
    5. 5. 5 Confidential SharePoint
    6. 6. 6 Confidential SharePoint
    7. 7. Hometown, Laurel, NY (from Confidential SharePoint
    8. 8. Key Topics8 Confidential SharePoint BU
    9. 9. Presentation Governance• In scope – 2010 Administration ―Core‖• Out Of Scope – 2013 Deep Dives – Deep Dives (e.g. PowerShell, BI, Upgrade, SQL DBA) – Development/Customization – Power User (e.g. Library Customization, Designer Workflows, etc.)• Rules – Move fast, PowerPoint is shared – – Questions – time permitting during session – Any time after session – email etc. - @cmcnulty20009 Confidential SharePoint
    10. 10. Congratulations!• You‘re the new SharePoint Administrator!!!• But…• You‘re still responsible for: – Exchange – Active Directory – SQL – Desktop – Help Desk – Network/Firewall – Cooking & Cleaning – Etc.10 Confidential SharePoint
    11. 11. The Dilemma• SharePoint administration is often an ‗add-on‘ for other IT professionals (SQL DBAs, AD Admins, Exchange Engineers)• Time and focus are scarce resources!• 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 search11 Confidential SharePoint
    12. 12. Microsoft SharePoint Server 2010 … the bright frontier12 Confidential Eastern Long Island, July 4, SharePoint 2010
    13. 13. Architecture and Design15 Confidential SharePoint
    14. 14. Server Farm – Web Front End• Typical Roles: – http services – Search query• Scaling – Add servers to load balanced cluster• Performance Optimization – RAM – Easily virtualized16 Confidential SharePoint
    15. 15. 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 1717 Confidential SharePoint
    16. 16. Server Farm - Database• Typical Roles: – Data storage – SQL Reporting• Scaling – Add storage capacity• Performance Optimization – Disk I/O 1818 Confidential SharePoint
    17. 17. Sizing - Single Server• 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 function19 Confidential SharePoint
    18. 18. Sizing - Medium Farm• 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 databases20 Confidential SharePoint
    19. 19. Sizing - Large Farm• Typical Roles: – Large distributed enterprise users (10000+) – Large pools of documents (>1MM)21 Confidential SharePoint
    20. 20. Sizing – No Servers – Office 365 Office 365 Enterprise Plans E1 E2 E3 E4 • Constraints/Unavailable – Custom, non sandbox solutions SharePoint Online √ √ √ √ – Power Pivot – SQL Server Reporting Service Office Web Apps √ √ √ Integration Local Copy of Office √ √ – Business Connectivity Services Professional 2010 Plus (OK for web services- based remote data in O365 BCS.) – FAST Search Server Integration Forms Services, Vision √ √ – Web Analytics Services, Access Services – Site collections greater than 100GB Monthly cost per user $10 $16 $24 $2722 Confidential SharePoint
    21. 21. Top Level Logical Components• Farm level• Web applications Web Applications – Independent top level URLs – Run inside IIS pools – Consume shared services and admin http://intranet Site Collections from the farm or other farms• Site collections – Security, branding, database frontier Site Hierarchies Sites – Contain single sites or site hierarchies Lists Libraries Pages Web Parts http://centadmin Single Sites• Sites (MySite) – Group related SharePoint elements (lists, libraries, pages, web parts) 2323 Confidential SharePoint
    22. 22. Logical Components• High capacity!• 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• 2013 Notes – Shredded storage?25 Confidential SharePoint
    23. 23. 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 – Archive Rate G% 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) • Content of SharePoint content anddisk dumps (if used for backup) which can add 1-3X. Inputs: Size will grow! non-SharePoint content included in search •For DBs, don‘t forget transaction logs, Searching remote storesneed be provisioned early isn’t free. •In SAN or virtual environments, not all disk saves disk but26 Confidential SharePoint
    24. 24. Database sizing• Automatic database growth: – 50-100MB clumps – not by percentage. – Using a small size leads to more frequent, but smoother, steady state growth.• Presize tempdb to about 20% the size of the single largest content database.27 Confidential SharePoint
    25. 25. Psst…about SQL…• Sidebar on SQL Disk optimization – RAID 1: Mirroring (Wastes disk) – RAID 5: Parity Bit (write performance hit) – RAID 10 Stripes across mirrors (costly)• Physical location of data, log, temp and/or backup files. If virtualization or SAN technology doesn‘t isolate the disks, not much performance gain,• Performance optimization/fault tolerance by: – RAID1 on boot disks – RAID5 on data disks – RAID10 on log disks – No RAID, or RAID 5 on backup disks• RBS reduces size (and count) of content databases but doesn’t reduce size of total storage• IOPS, IOPS, IOPS!30 Confidential SharePoint
    26. 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 Network34 Confidential SharePoint
    27. 27. Internet Topology – Perimeter• More complex• Duplicative networks, backup, AD Edge Router/ WFE App SQL AD Firewall Firewall• External traffic is reserved Internet• Larger server foot print (exposure) in perimeter Perimeter Network Internal Net• Internal users need domain trusts• Internal users access site across firewall35 Confidential SharePoint
    28. 28. Internet Topology – Split Back to Back• Most complex• Intricate firewall rules Edge Router/• App, AD and search roles Firewall WFE Firewall App SQL AD optionally in perimeter Internet• Optional internal WFE or internal users always cross a firewall Perimeter Network Internal Network• Crawl topologies important to avoid overtaxing the firewall36 Confidential SharePoint
    29. 29. Internet Topology – Enhanced Techniques• Multi-farm• SSA farm• Content publishing38 Confidential SharePoint
    30. 30. Platform Basics• SharePoint 2010 is a 64 bit only platform.• Direct upgrades from 32 bit to 64 bit require 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 R240 Confidential SharePoint
    31. 31. Shared Service Applications• 2007 Shared Services Provider has been broken up; each of its elements is now a Shared User Profiles Service Application Search Metadata• Mix and match them singly or in groups, to match farm‘s needs. Excel Calc Visio• Crawl/index no longer a single server role• In 2010, administration can be delegated – Key targets: Enterprise search, metadata, user profiles http://globalweb http://itportal41 Confidential SharePoint
    32. 32. Client/Browser Technology• Internet Explorer 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 lists42 Confidential SharePoint
    33. 33. 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 OWA43 Confidential SharePoint
    34. 34. Installation and Upgrade44 Confidential SharePoint
    35. 35. 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-in45 Confidential SharePoint
    36. 36. 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 run46 Confidential SharePoint
    37. 37. Installation – White Wizard?• Pros – Easy – shaken and stirred – 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• 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 database47 Confidential SharePoint
    38. 38. Predictable Upgrade• Three paths – In place – Database upgrade – Third party tools• Process – Pre-upgrade checker – Visual Upgrade – Resumable upgrade – Progress reports – Parallel DB upgrades48 Confidential SharePoint
    39. 39. Upgrade Preparation• Additional Prepwork – 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!49 Confidential SharePoint
    40. 40. 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 – Site definitions, site templates, features, and language packs – 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.• Doesn’t exist for 2010 – 2013!50 Confidential SharePoint
    41. 41. IT Pro Investments – Visual Upgrade51 Confidential SharePoint
    42. 42. Demo Upgrade SharePoint
    43. 43. Monitoring and Operations53 Confidential SharePoint
    44. 44. 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 usage54 Confidential SharePoint
    45. 45. Logging, Monitoring, and Alerts• Unified Logging• Out-of-the-box reports ULS Logs• Richer Web Analytics• Open Schema Windows Events• SCOM Integration Page Logging requests DB• PLUS – Developer Dashboard – Health Analyzer Feature Logging Health data55 Confidential SharePoint
    46. 46. Developer DashboardImprove customized solutions with the Developer Dashboard57 Confidential SharePoint
    47. 47. Whoops!• Default user screen• Correlation ID is shown!58 Confidential SharePoint
    48. 48. 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].[ULSTraceLog] WHERE CorrelationID = 04377DAE-C2FD-4DBE-A57E- 101B3005059E59 Confidential SharePoint
    49. 49. 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 methods61 Confidential SharePoint
    50. 50. Backup/Recovery• Third Party Tools• 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)62 Confidential SharePoint
    51. 51. STSADM Backup@echo offecho ==================================================echo Backup the farmecho ==================================================@SET stsadm="C:Program FilesCommon FilesMicrosoft SharedWeb ServerExtensions12BINstsadm"rmdir /S /Q "spsql08spbackupfarmold"ren "spsql08spbackupfarm" "farmold"md "spsql08spbackupfarm"%stsadm% -o backup -directory "spsql08spbackupfarm" -backupmethod fullecho complete63 Confidential SharePoint
    52. 52. PowerShell Backup# NOT NEEDED write-outputwrite-host ==================================================write-host Backup the farmwrite-host ==================================================Add-PSSnapIn Microsoft.SharePoint.PowershellRemove-Item -Path "C:PSBackupfarmold― -recurseRename-Item -Path "C:PSBackupfarm" -NewName "farmold"New-Item -type directory -path C:PSBackupfarmBackup-SPFarm -directory "C:PSBackupfarm" -backupmethod full –verbose –percentage5Write-host Backup complete64 Confidential SharePoint
    53. 53. Demo Monitoring DeveloperDashboard Health Analyzer Logging andReporting SharePoint
    54. 54. Optimization69 Confidential SharePoint
    55. 55. Optimization• Disk-based BLOB Caching – 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|wdp|hdp|css|js|asf|avi|flv|m4v|mov|mp 3|mp4|mpeg|mpg|rm|rmvb|wma|wmv)$" maxSize="10" enabled="false" /> – Location = Local Disk Location – maxSize = GB – Enabled = true• Different from RBS/EBS!• For publishing sites71 Confidential SharePoint
    56. 56. Patching – Process through August 2011 • SharePoint Foundation Patch • SharePoint Server Patch • Run SharePoint Products and Technologies Wizard • (Or psconfig)Deploy • Sequential Application to Central Admin, Application Server(s), Web Front End Servers72 Confidential SharePoint
    57. 57. Patching – 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)Deploy • Sequential Application to Central Admin, Application Server(s), Web Front End Servers73 Confidential SharePoint
    58. 58. Patching – Notes• Test before installation!!!• Cumulative Updates every two months• Service Pack every 6-18 months• Service Pack 1 REQUIRES at least the June 2011 CU• December 2011 CU – iOS 5 Mobile Safari support for Performance Point – Fixed Administrator updates to user profile pictures• February 2013 CU most current• Check my blog for latest: &Name=Version-Build Numbers74 Confidential SharePoint
    59. 59. 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 Plans75 Confidential SharePoint
    60. 60. Office Web Apps Server• Off-server installation • On SharePoint – New-SPWOPIBinding -ServerName• Prerequisites <WacServerName> -AllowHTTP – .NET Framework 4.5/ASP.NET 4.5 – Ink and Handwriting • Set zone to regular http – Windows Authentication, NET Extensibility 4.5 – Set-SPWopiZone –zone ―internal-http‖ – ISAPI Extension, ISAPI Filters • Troubleshooting: – Server Side Includes – No system account usage!• Default installation (DNS, https) – Configure system to allow OAuth over http• PowerShell – $config = (Get- – Import-Module OfficeWebApps SPSecurityTokenServiceConfig) – $config.AllowOAuthOverHttp = $true – New-OfficeWebAppsFarm –InternalURL – $config.Update() http://SP2013Demo-WAC –ExternalURL http:// SP2013Demo-WAC.spdemo.corp –AllowHttp – EditingEnabled –ClipArtEnabled• Test - http://servername/hosting/discovery76 Confidential SharePoint BU
    61. 61. Social Administration - Quotas• Check quotas based on errors, usage patterns• Default is 100MB79 Confidential SharePoint
    62. 62. Best Practices 82 Confidential SharePoint
    63. 63. Troubleshooting – Top Support 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)83 Confidential SharePoint
    64. 64. Troubleshooting – More Support 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 & Restore84 Confidential SharePoint
    65. 65. 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 size89 Confidential SharePoint
    66. 66. 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 fresh90 Confidential SharePoint
    67. 67. Congratulations!• You‘re the new SharePoint Administrator!!!• And now• You understand: – Design and Architecture – Installation and Upgrade – Support and Maintenance and Optimization – PowerShell – Customizations – Troubleshooting – Best Practices91 Confidential SharePoint
    68. 68. 92 Confidential SharePoint
    69. 69. Thank you! – Questions – Contact – Email – Blog – Also – Twitter: @cmcnulty2000 – Upcoming: – ICC Heartland Conf, SP Evolutions, DCSPUG, SPUGME, ShareFest Denver93 Confidential SharePoint
    70. 70. While youre in the Bay Area…• Monday 4:00pm - SharePoint SpeedMetal Admin 101• Monday 5:30pm – Lightning Talks• Tuesday 2:00pm – Social 101 and SharePoint• Tuesday 6:00pm – Book Signing, Dell, SharePoint 2013 Consultant‘s Handbook (Advance Edition)• Wednesday 1:15pm – SharePoint Experts Meetup (Managed Metadata)• Wednesday 3:45pm – I Have Excel, I Need PerformancePoint, but I Don‘t Know Analysis Services!94 Confidential SharePoint BU
    71. 71. More information• SharePoint architecture design patterns in Chris‘ e- book entitled SharePoint 2010 Consultant’s Handbook – A Practical Field Guide – Get your free copy here book96 Confidential SharePoint
    72. 72. 97 Confidential SharePoint