• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
SharePoint SpeedMetal - Admin 101 SPSPhilly
 

SharePoint SpeedMetal - Admin 101 SPSPhilly

on

  • 1,080 views

Chris McNulty's presentation on SharePoint Administration, SharePoint Saturday Philadelphia, 4 February 2012

Chris McNulty's presentation on SharePoint Administration, SharePoint Saturday Philadelphia, 4 February 2012

Statistics

Views

Total Views
1,080
Views on SlideShare
1,078
Embed Views
2

Actions

Likes
2
Downloads
37
Comments
0

2 Embeds 2

https://twitter.com 1
http://paper.li 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • We have offices throughout the world and have the resources to support the largest global organizations whether they be in the Americas, Europe, Middle East, Africa, or across the Asia Pacific and Japan region.
  • 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
  • IF YOU DON’T NEED IT – DON’T USE ITPLUS YOU CAN GIVE IT AWAY!
  • 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
  • Keep?
  •  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.
  • Keep?
  • Use SP to managed SPBusiness owns home page
  • Typical
  • I would be happy to discuss what we are trying to put together for partners/TEC.

SharePoint SpeedMetal - Admin 101 SPSPhilly SharePoint SpeedMetal - Admin 101 SPSPhilly Presentation Transcript

  • SharePoint SpeedMetal – Admin 101SharePoint Saturday PhillyChris McNultySharePoint Strategic Product ManagerFebruary 2012 ©2011 Quest Software, Inc. All rights reserved..
  • Quest Market Presence Americas 60 Offices, 3 HQs EMEA APJa Sales/Mrkg 3600+ Employees R&D Support 178 Countries 100,000+ Customers All Verticals Global 200 SMB Multiple Business Lines Database, Monitoring, Data Protection, User Workspace/Virtualization, Windows (SharePoint, AD, Messaging), Identity Mgmt 2 2 ©2011 Quest Software, Inc. All rights reserved.. ©2011 Quest Software, Inc. All rights reserved. Confidential.
  • 3 3 ©2011 Quest Software, Inc. All rights reserved..©2011 Quest Software, Inc. All rights reserved. Confidential.
  • Chris McNulty• SharePoint Strategic Product Manager at Quest 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 (17, 8, 5) and my dog Stan• 411 on 516: Born in Nassau County, grew up in Suffolk County 4 ©2011 Quest Software, Inc. All rights reserved..
  • For tomorrow… 6 ©2011 Quest Software, Inc. All rights reserved..
  • Agenda• The dilemma• Architecture, Design & Planning• Installation and Upgrade • Post Installation Best Practices • Service/Feature Placement• Support • Monitoring and Optimization • Backup • PowerShell • Development Functions • Optimization • Patching • SQL Maintenance• Best Practices @cmcnulty2000 7 ©2011 Quest Software, Inc. All rights reserved..
  • Presentation Governance• Out Of Scope • Deep Dives (e.g. PowerShell, BI, Upgrade, SQL DBA) • Development • Customization • Design & Architecture • Power User (e.g. Library Customization, Designer Workflows, etc.)• Rules • Move fast, PowerPoint is shared – http://[TBD] • Questions – time permitting during session • Any time after session – email etc. - @cmcnulty2000 @cmcnulty2000 8 ©2011 Quest Software, Inc. All rights reserved..
  • Congratulations!o You‘re the new SharePoint Administrator!!!o But…o You‘re still responsible for:• Exchange• Active Directory• SQL• Desktop• Help Desk• Network/Firewall• Cooking & Cleaning• Etc. @cmcnulty2000 9 ©2011 Quest Software, Inc. All rights reserved..
  • The Dilemmao SharePoint administration 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 @cmcnulty2000 10 ©2011 Quest Software, Inc. All rights reserved..
  • Microsoft SharePoint Server 2010 … the bright frontier Eastern Long Island, July 4, 2010
  • Architecture and Design
  • Server Farm – Web Front End• Typical Roles: • http services • Search query• Scaling • Add servers to load balanced cluster• Performance Optimization • RAM • Easily virtualized 13 13 ©2011 Quest Software, Inc. All rights reserved..
  • 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 14 14 ©2011 Quest Software, Inc. All rights reserved..
  • Server Farm - Database• Typical Roles: • Data storage • SQL Reporting• Scaling • Add storage capacity• Performance Optimization • Disk I/O 15 15 ©2011 Quest Software, Inc. All rights reserved..
  • 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 function 16 ©2011 Quest Software, Inc. All rights reserved..
  • 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 databases 17 ©2011 Quest Software, Inc. All rights reserved..
  • Sizing - Large Farm• Typical Roles: • Large distributed enterprise users (10000+) • Large pools of documents (>1MM) 18 ©2011 Quest Software, Inc. All rights reserved..
  • Sizing – No Servers – Office 365Office 365Enterprise Plans E1 E2 E3 E4 • Constraints/UnavailableSharePoint Online √ √ √ √ • Custom, non sandbox solutions • Power PivotOffice Web Apps √ √ √ • SQL Server Reporting ServiceLocal Copy of √ √ IntegrationOffice • Business Connectivity ServicesProfessional 2010Plus (OK for web services- based remote data in O365 BCS.)Forms Services, √ √Vision Services, • FAST Search Server IntegrationAccess Services • Web Analytics • Site collections greater thanMonthly cost per $10 $16 $24 $27user 100GB 19 ©2011 Quest Software, Inc. All rights reserved..
  • Top Level Logical Components• Farm level• Web applications Web Applications • Independent top level URLs • Run inside IIS pools http://intranet Site Collections • Consume shared services and admin from the farm or other Site Hierarchies Sites farms• Site collections http://centadmin Single Sites (MySite) Lists Libraries Pages Web Parts • Security, branding, database frontier • Contain single sites or site hierarchies• Sites • Group related SharePoint elements (lists, libraries, pages, web parts) 20 20 ©2011 Quest Software, Inc. All rights reserved..
  • 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 22 ©2011 Quest Software, Inc. All rights reserved..
  • Disk SizingContent SearchInitial Content Size XXX GB External Crawl Size YYY GBInitial User Pool UUser Collab Size .25GBn YR Growth Rate – G%Archive RateEnd Content Size XXX (1+G)n = ECS End Search Size YYY (1+G)n = ESSEnd User Collab Size .25 * U * (1+G)n = EUCSContent DBs ECS + EUCSSearch DBs .05 * (ECS + EUCS + ESS)Search Index Files .05 * (ECS + EUCS + ESS)• Inputs: Size of SharePoint content and non-SharePoint content included in search• For DBs, don‘t forget 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 @cmcnulty2000 23 ©2011 Quest Software, Inc. All rights reserved..
  • 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 24 ©2011 Quest Software, Inc. All rights reserved..
  • 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 firewall 25 ©2011 Quest Software, Inc. All rights reserved..
  • Internet Topology – Split Back to Back• Most complex• Intricate firewall rules• App, AD and search roles Edge Router/ Firewall WFE Firewall App SQL AD optionally in perimeter Internet• Optional internal WFE or internal users always Perimeter Network Internal Network cross a firewall• Crawl topologies important to avoid overtaxing the firewall 26 ©2011 Quest Software, Inc. All rights reserved..
  • Common Integration TouchpointsInternalActive DirectoryExchange / File SharesIndex and integrate BCS dataExternal• LDAP• Mail Relay• Indexed search contentOther Systems• FAST (Search)• Project Server / TFS• BizTalk• LoB/Dynamics• Oracle (BCS)• Notes (Search)• Wikis and other indexed web sites 27 ©2011 Quest Software, Inc. All rights reserved..
  • Internet Topology – Enhanced Techniques• Multi-farm• SSA farm• Content publishing @cmcnulty2000 28 ©2011 Quest Software, Inc. All rights reserved..
  • Platform Basics• SharePoint 2010 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 @cmcnulty2000 29 ©2011 Quest Software, Inc. All rights reserved..
  • Shared Service Applications• 2007 Shared Services Provider has been broken up; each of its elements is now a User Profiles Metadata Shared Service Application Search• Mix and match them singly Excel Calc or in groups, to match farm‘s Visio needs.• Crawl/index no longer a single server role• In 2010, administration can be delegated http://globalweb http://itportal • Key targets: Enterprise search, metadata, user profiles 30 ©2011 Quest Software, Inc. All rights reserved..
  • 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 lists @cmcnulty2000 31 ©2011 Quest Software, Inc. All rights reserved..
  • 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 32 ©2011 Quest Software, Inc. All rights reserved..
  • Installation andUpgrade
  • 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 @cmcnulty2000 34 ©2011 Quest Software, Inc. All rights reserved..
  • 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 35 ©2011 Quest Software, Inc. All rights reserved..
  • 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 database 36 ©2011 Quest Software, Inc. All rights reserved..
  • Upgrade PreparationAdditional Prepwork • Content pruning • Database alignment • stsadm-o mergecontentdbsDB Attach • Preinstall Required Features • Stsadm –o addcontentdb – databasename DBNAME –url URL –assignnewdatabaseid • PowerShell Mount- ContentDatabase • Test, test, test! 37 ©2011 Quest Software, Inc. All rights reserved..
  • 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 38 Internal Database and larger than 4 GB. ©2011 Quest Software, Inc. All rights reserved..
  • IT Pro Investments – Visual Upgrade 39 ©2011 Quest Software, Inc. All rights reserved..
  • DEMO• Upgrade 40 ©2011 Quest Software, Inc. All rights reserved..
  • Monitoring and OperationsMonitoring
  • 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 42 ©2011 Quest Software, Inc. All rights reserved..
  • Logging, Monitoring, and Alerts• Unified Logging ULS Logs• Out-of-the-box reports• Richer Web Analytics Windows Events• Open Schema Logging• SCOM Integration Page requests DB• PLUS Feature Logging • Developer Dashboard • Health Analyzer Health data 43 ©2011 Quest Software, Inc. All rights reserved..
  • 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 @cmcnulty2000 44 ©2011 Quest Software, Inc. All rights reserved..
  • Developer DashboardImprove customized solutions with the Developer Dashboard 45 ©2011 Quest Software, Inc. All rights reserved..
  • 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-101B3005059E 46 ©2011 Quest Software, Inc. All rights reserved..
  • 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) 47 ©2011 Quest Software, Inc. All rights reserved..
  • 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 complete 48 ©2011 Quest Software, Inc. All rights reserved..
  • 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 –percentage 5Write-host Backup complete 49 ©2011 Quest Software, Inc. All rights reserved..
  • PowerShell• SharePoint Shell vs. 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 @cmcnulty2000 50 ©2011 Quest Software, Inc. All rights reserved..
  • 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) @cmcnulty2000 51 ©2011 Quest Software, Inc. All rights reserved..
  • 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) @cmcnulty2000 52 ©2011 Quest Software, Inc. All rights reserved..
  • Development Support – Three Regions Development Staging/Test Production• often internal to developers • no Visual Studio, no MS • optimized hardware• problem reproduction that Office configurations require advanced inspection • match/mirror production as • highly secure tools (e.g. Visual Studio) are closely as possible; match • no use of user rotating done here hardware/system password accounts as• permissions can be looser, performance as closely as service accounts may have multiple practical • changes here can only be environments for multiple • security permissions match delivered and deployed developers production from source control and• sensitive data from • any sensitive data copied according to production production cannot be here stays under release methods copied here without production-grade controls masking or customer signoff • test accounts should be• changes here can be created in a separate OU if deployed ad hoc possible • changes here can only be delivered and deployed from source control and according to production release methods @cmcnulty2000 54 ©2011 Quest Software, Inc. All rights reserved..
  • demoMonitoringDeveloper DashboardHealth AnalyzerPowerShell 55 ©2011 Quest Software, Inc. All rights reserved..
  • Optimization Optimization
  • 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|cs s|js|asf|avi|flv|m4v|mov|mp3|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 sites @cmcnulty2000 57 ©2011 Quest Software, Inc. All rights reserved..
  • Patching – 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 @cmcnulty2000 58 ©2011 Quest Software, Inc. All rights reserved..
  • 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) • Sequential Application to Central Admin, Application Server(s), Web Front Deploy End Servers @cmcnulty2000 59 ©2011 Quest Software, Inc. All rights reserved..
  • 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 added iOS 5 Mobile Safari support for performance Point• December 2011 CU also fixed Administrator updates to user profile pictures• Check my blog for latest: http://www.chrismcnulty.net/blog/Lists/Categories/Category. aspx?CategoryId=5&Name=Version-Build Numbers @cmcnulty2000 60 ©2011 Quest Software, Inc. All rights reserved..
  • 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 @cmcnulty2000 61 ©2011 Quest Software, Inc. All rights reserved..
  • Best Practices
  • 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) @cmcnulty2000 64 ©2011 Quest Software, Inc. All rights reserved..
  • 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 & Restore @cmcnulty2000 65 ©2011 Quest Software, Inc. All rights reserved..
  • Seven Deadly Sins for the SharePoint Professional
  • 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 @cmcnulty2000 67 ©2011 Quest Software, Inc. All rights reserved..
  • Seven Virtues for the SharePoint Professional
  • 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 @cmcnulty2000 69 ©2011 Quest Software, Inc. All rights reserved..
  • 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 Practices • People from New York? 70 ©2011 Quest Software, Inc. All rights reserved..
  • •Questions•Contact Me•SharePint 71 ©2011 Quest Software, Inc. All rights reserved..
  • Thank you…• Contact • Email chris.mcnulty@quest.com • Blog http://www.chrismcnulty.net/blog • Also http://www.sharepointforall.com • Twitter: @cmcnulty2000 • LinkedIn:http://www.linkedin.com/in/cmcnulty• Upcoming: • Feb 2012 – O365 Sat Redmond, SPTechCon San Francisco • Mar 2012 – SharePoint Conference Heartland (Columbus OH),SharePoint Conference AUS, SharePoint Connections (Las Vegas) • April 2012 – SharePoint Saturday Twin Cities; The Experts Conference San Diego • July 2012 – SharePoint Saturday NYC 73 ©2011 Quest Software, Inc. All rights reserved..
  • Questions?Get more information atwww.Quest.com/ControlYourChaos 74 ©2011 Quest Software, Inc. All rights reserved..