Business Intelligence in SharePoint 2013 by Jason Himmelstein - SPTechCon
What’s your Social IQ? Succeeding with SharePoint Social by Chris McNulty - SPTechCon
1. What’s Your Social IQ?
Succeeding with SharePoint Social
SPTechCon San Francisco 2013
Chris McNulty
2. 25 years
Since 1987, Quest has offered a
broad and deep selection of
products that target common IT
challenges
100k
Quest products provide over 100,000
30
Over thirty acquisitions have strengthened
customers with IT solutions every day our product portfolio
18% 3,900
Quest has driven innovation by Quest employees develop solutions in over sixty
regularly investing 18% or more in offices throughout the world
R&D
11. Presentation Governance
• Out Of Scope
– Quest / Dell
– Deep Dives (e.g. PowerShell, BI, Upgrade, SQL DBA)
– BI Installation and Configuration
• Rules
– Questions – time permitting during session
– Any time after session – email etc. - @cmcnulty2000
– Slides posted to www.sharepointforall.com http://bit.ly/WSFXPO
• Prerequisites
– Comfortable with SQL
– Can write T-SQL
– SharePoint Customization Expertise
12 Confidential SharePoint
12. What is
enterprise
social, and
why
13 Confidential SharePoint BU
13. 3. Social
Collaborate directly in the social interface
• Personal social site not just
for quick status updates
• Easily post links, docs, video,
pictures and pictures
• Share “in place” instead of
moving
• Follow people, conversations,
tags – and documents
• Yammer not yet integrated.
14 Confidential SharePoint
14. 4. Community
Between team site and my site…”our site”
• Combines social features of a My Site with those of a Team Site
• Rich way to add discussion areas, post questions, rate results
• Use a badging system to spotlight top contributors and performers
automatically.
• Simple to dynamically assemble a custom pool of users for any community
at all.
15 Confidential SharePoint
15. 5. Newsfeeds – everywhere!
•
• Its more than RSS…
• Every site can have an (optional)
custom community social stream.
16 Confidential SharePoint
16. 6. Learning from Twitter
• Every microblog update can now
include:
– #tags (dynamically pulled from or
added to MMS)
– @targets (default pulls from your
social colleagues list but you can post
the updates to any SharePoint user)
17 Confidential SharePoint
17. Why social?
• Pros • Cons
– “The way we live now” – Change management
– Matches consumer communication – Immature governance
style – Vastly complex IA
– Accelerates information discovery – – Security model grows exponentially
the searches you don’t need to run with diverse sharing
– It is collaboration
– Staff retention
18 Confidential SharePoint
18. Demo –
SharePoint
2013 Social
and
Communities
19 Confidential SharePoint
19. Engineering Training
How to
establish –
culture and
technology Management Adoption
20 Confidential SharePoint
20. Social engineering
SharePoint Social
User
Office Web Distributed
Profile Search
Apps Cache
Service
21 Confidential SharePoint
21. User Profile Service
• My Sites – Don't trust the white wizard!
– IT STILL CREATES BAD GUIDs
– Puts My Sites in the same Web Application
• Dedicate a web application and content
database
• Configure search center!
• Configure profile import
– Provision against AD, ideally
22 Confidential SharePoint
22. Search
• Defaults are OK
• Create an Enterprise Search Center http://site/search
• Will use in My Sites Setup
23 Confidential SharePoint
23. 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-
– ISAPI Extension, ISAPI Filters http”
– Server Side Includes • Troubleshooting:
• Default installation (DNS, https) – No system account usage!
– Configure system to allow OAuth
• PowerShell over http
– Import-Module OfficeWebApps – $config = (Get-
SPSecurityTokenServiceConfig)
– New-OfficeWebAppsFarm –InternalURL
– $config.AllowOAuthOverHttp = $true
http://SP2013Demo-WAC –ExternalURL http://
– $config.Update()
SP2013Demo-WAC.spdemo.corp –AllowHttp –
EditingEnabled –ClipArtEnabled
• Test - http://servername/hosting/discovery
24 Confidential SharePoint BU
24. Distributed Cache
• Automatically installed and uses 10% default RAM in the pool
• Size of cache affects speed and size of recent newsfeeds
• Bad - Services MMC or Windows Server AppFabric
• Good - Central Administration or PowerShell commands.
• Decommission gracefully
• User fixed memory on VM’s, not dynamic!
• In a cache cluster, all same, minimum 8GB, max 16GB, maximum 16 hosts
• Keep usage to 70% available cache memory
• Keep an eye on Central Administration and Health Analyzer Reports.
25 Confidential SharePoint
25. Social
management
and
administration
26 Confidential SharePoint
26. Social Administration – Tags, Notes, Following
• Social tagging administered from UPS SSA
• Following is throttled but not directly administered
27 Confidential SharePoint
27. Social Administration - Quotas
• Check quotas based on errors, usage patterns
• Default is 100MB
28 Confidential SharePoint
28. Social Administration – Promoted Sites (UPS SSA)
• This:
• Comes from:
29 Confidential SharePoint
30. Social
Governance
and Adoption
31 Confidential SharePoint BU
31. Social governance and training
• Governance
– “…the set of policies, roles, responsibilities, and processes that guide, direct, and
control how an organization's business divisions and IT teams cooperate to
achieve business goals.” -TechNet
– Highlights:
– People and process
– Guide and control
– Business/IT cooperation
– Business goals
• Visibility and self-governance
• Share behavior with training, examples, policy
– My files go where?
– 2010: Share by moving
– 2013: Share by sharing
32 Confidential SharePoint BU
32. User training : SkyDrive and SkyDrive Pro
• SkyDrive Pro (labeled as ‘SkyDrive’)
– User personal file storage on
SharePoint 2013 OR Office 365
• SkyDrive
– Free Microsoft file storage in cloud
• SkyDrive Pro
– Offline clients sync from Office
2013, Windows 8, iOS coming early
2013 (SPC12, ZDNet)
33 Confidential SharePoint
33. Social adoption – technical architecture
• Implement User Profiles!
• Let loose community sites – lean governance
• Enable pervasive newsfeeds
• Big quotas for social (100MB default is awfully low)
• Managed metadata – we follow sites, people, documents, conversations and
terms – pay attention
• Use followed sites and suggestions
34 Confidential SharePoint
34. Social adoption – know the culture
• Choose initial usage pools with greater than 50% likelihood of penetration
– High interactivity
– “Geo-chrono” dispersed
– Tech friendly
• Information architecture – social becomes a secondary structure
35 Confidential SharePoint
35. Social adoption – work management
• Tasks and WMS only help when you have task sources – like Project Server
or the Tasks app (off by default) – but if so they’re a great app
• Integrates local, project, site tasks with conversation followup […]
36 Confidential SharePoint
37. What is it
• The SharePoint Maturity Model was developed in the Fall of 2010 for the
purpose of bringing a holistic view to a SharePoint implementation,
and bringing standardization to the conversation around functionality, best
practices, and improvement.
• The benefits of the Model are:
– It gives you a holistic understanding of your SharePoint implementation’s current
state, and lets you define a benchmark for future improvement
– It helps you define your strategic roadmap.
– Participaltino expands group data
• Does NOT cover:
– Public-facing websites
– Compliance and regulatory issues
– Visual design and branding
38
– Cloud / online versions of SharePoint
Confidential SharePoint BU
38. What it covers
• Publication • Integration
• Collaboration • Insight
• Business Process • Infrastructure
• Search • Staffing & Training
• People & Communities • Customizations
• Composites & Applications
39 Confidential SharePoint BU
39. Levels defined
500 Optimizing
•The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics.
ROI is demonstrable.
400 Predictable
•The particular area is centrally supported, standardized, and implemented across the entire organization. Governance is
defined and understood / followed.
300 Defined
•The way the particular area is implemented is defined and/or standardized, but not in use across the entire organization.
Governance is defined but may not be widely understood / followed. ROI is considered.
200 Managed
•The particular area is managed by a central group (often IT), but the focus and definition varies by functional area, or is
limited to a single area.
100 Initial
•The starting point of SharePoint use.
40 Confidential SharePoint BU
40. Social/Communities (SPMaturity.com)
500 Optimizing
• Users can edit certain profile data that writes back to AD or HRIS. MySites template is customized. Communities extend to external participants.
• Forms connect with LOB data. New capabilities & requirements are surfaced & integrated into downstream capabilities.
• External data (partner/supplier or industry) is integrated with SP.
• Analytics and trending are employed.
400 Predictable
• Profile fields may integrate with LOB data. MySites are centralized (only one instance per user). Communities flourish under governance.
• InfoPath forms improve the user experience. Mobile functionality is supported.
• Most of the systems that are desired to be integrated, are integrated. A data warehouse may be integrated with SP.
• Items are actionable.
300 Defined
• Custom profile fields reflect company culture; photos are updated from central source.
• MySites rolled out to all users, supported, trained. Community spaces connect a particular set of users.
• Most critical business forms are online; some involve automated workflows.
• Multiple systems are integrated with SP.
• Reports allow drill-down and charting.
200 Managed
• MySites rolled out to pilot groups or users. Out-of-box profiles implemented. Community spaces may be piloted.
• Increasing use of SP lists to replace Excel spreadsheets and paper forms. Applications are opened up to a larger group of users.
• A single system is integrated with SP (Line-of-business, document management, etc.).
• Reports are aggregated through customization.
100 Initial
• Basic profile data imported from AD or other source. MySites host not created.
41 Confidential SharePoint BU
43. Social ISVs
• Colligo
• NewsGator
• Neudesic Pulse
• Dell Social Hub
• Yammer
44 Confidential SharePoint BU
44. Yammer
• Microsoft owned
• Integrates directly into Office 365
• SharePoint to come
• Multiple clients (iOS, mobile, web,
SP) and apps
• Cloud based – integrates to
SkyDrive Pro
45 Confidential SharePoint
45. NewsGator
• Social Sites (general) and Tomoye
(public sector)
• Enhanced community
collaboration on SharePoint 2007,
2010, 2013
• High capacity, multiple clients
• Complex
• Moving away from SharePoint as
required technology
46 Confidential SharePoint
46. Neudesic Pulse
• Grew from real world
enhancements and integration
• Integrates to SharePoint full screen
or web part), Dynamics
• Hosted or on-premises model
• Groups, newsfeeds, microblogs
47 Confidential SharePoint
47. Dell Social Hub
• Free SharePoint 2013/Office
365 app in the Microsoft App
Store
• Adds Facebook, Twitter,
LinkedIn and RSS social feeds to
SharePoint
• Improves “single pane of glass”
story for adoption
• Free
48 Confidential SharePoint
48. Colligo
• Extend SharePoint content into
Outlook (Harmon.ie)
• Extend content to
desktop/offline/iOS/Outlook
• Interact from a different social
context
49 Confidential SharePoint
51. While you're 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!
52 Confidential SharePoint BU
52. 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 http://www.quest.com/get-
chris-book
54 Confidential SharePoint
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
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.
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.
Guide you around the world, or, ultimately guide you safely homeWe have to keep that light burning