sharepoint 2010 operational management sp-saturday nz
TRANSCRIPT
SharePoint Saturday NZ – SharePoint Operational Management December 10th 2010
Chandima Kulathilake – Director, Technology
Who am I?
• Chandima – aka “Chan” @chandimak on twitter
• Director @ Knowledge Cue
• Started with SharePoint 2001... It’s been a great journey
• SharePoint MVP since 2007
• www.chandima.net/blog
Knowledge Cue
• Help with strategy and planning for SharePoint • Sense making for large enterprise projects • Pre RFP stage expectation setting • SharePoint best practices/ “real world”
balancing act • Consulting and deployment support • Microsoft certified SharePoint experts • @knowledgecue on twitter • www.knowledgecue.co.nz
Session Agenda
• SharePoint Platform 101
– The Definition
– The Technologies
• Operational Management
– Servers and “farms”
– Sites and Solutions
• Demos
Software Platform
• In computing, a platform describes some sort of hardware architecture and software framework (including application frameworks), that allows software to run. Typical platforms include a computer's architecture, operating system, programming languages and related user interface (runtime libraries or graphical user interface).
• -thanks Wikipedia.org
SharePoint - Platform
FAST Search Service
SharePoint Platform
Solu
tio
n
Solu
tio
n
Solu
tio
n
Solu
tio
n
Technology
Business
SharePoint Platform
Pro
ject
Sit
es
On
line
P
roce
du
res
Fin
ance
Te
am S
ite
HR
- L
eave
M
anag
emen
t
Technology
Business
SharePoint - The Technology Layer
Active Directory
User Profiles and
Organisational Information
ForeFront Identity
Manager
Internet Information Services
.Net Framework ASP.net
Exchange Server +
Lync Server
Messaging and Communication
SQL Server 2005/2008 (x64)
Configuration and Service Databases
Content Databases
Data Recovery
Platform Infrastructure and SharePoint
• Internal Authentication from Active Directory • Web Hosting via IIS • Data Storage through SQL Server • Enhanced Security via Rights Management • Directory Synchronisation via Identity Integration • Performance through disk and file management • Performance through physical network topology • Resilience through scalability and load balancing • Virus checking through ForeFront or other • Connectivity to LOB via Single Sign on
Choosing where to start
• Ensuring the platform (SharePoint) you choose is implemented and managed correctly – Operating System Layer
– Technology Layer
– Backup, Redundancy, Recovery
– IT SLAs
• Separate the technical foundation deployment from functional or solution (ex: Intranet, DM, RM)
What is the core platform?
• Hardware
• Network
• Software
• Management and Operations
Microsoft Operational Framework (MOF)
• Framework for delivering IT Service Solutions
Plan
• IT Strategy
• Standards
• Policies
• Finances
Deliver
• Envisioning
• Planning
• Building
• Testing
• Deploying
Operate
• Operating
• Monitoring
• Supporting
• Addressing Issues
Manage
• Managing Governance
• Risk
• Compliance
• Changes
• Configurations
Operate phase of MOF
SMF Operations Service Monitoring and Control
Customer Service Problem Management
What it does
Defines, documents, and executes the work necessary to efficiently and successfully operate IT services.
Observes IT service health and initiates remedial actions to minimize the impact of service incidents and system events.
Provides users with a positive experience and addresses complaints or issues.
Determines the root causes of problems and predicts future problems.
What it delivers
Operations Guide IT health data Effective user service
Effective problem resolution
Roles and Responsibilities
• Varies from organisation to organisation
– IT Infrastructure Architects
– SQL Server Database Administrators
– IT Security Architects
– Technology/Product Solution Specialists
– Project Managers
– (what NO Developers?)
Operate
Manage
What’s your scope?
• Internet (WCM)
• Intranet + Extranet
• Business Application Platform
– DM/RM
– Team Sites
– BI Portals
– Reporting
– Point Solution
Platform - Planning activities
• Workshop – involving
– Technology
– Business
– 3rd parties
– Microsoft – If under “premier” support
Planning questions
• Server capacity?
• Virtualisation?
• Custom applications supported?
• Everything outsourced?
– Network
– Servers
– SQL
– In-house and outsourced mix?
SharePoint 2010 – The decomposition
• Logical Architecture – Server farms
– Service applications
– Application pools
– Web applications
– Zones
– Policy for a Web application
– Content databases
– Site collections
– Sites
Finding balance
• You don’t need to scale if you don’t have to..
• Best practice is within your operational procedures and what you are trying to achieve – Ex. Does your SQL DBA periodically run
maintenance checks of databases?
• Expectation management – Ex. A SharePoint server built for an publishing
Intranet will not be able to do Business Intelligence solutions or external user access
What about this “Governance” thing?
• As an IT pro should I go on a “Governance Master class”?
• You are already doing it – Probably don’t call it that
• Do you have organisation SLAs? – Server management, Business continuity
• Who looks after support?
• Who is responsible for managing your servers? – Defined metrics or duties that must be done?
I will shoot the dog if you don’t apply Governance to my SharePoint!
Governance – is common sense
SharePoint Go LIVE Documents
Shar
eP
oin
t O
ps/
Engi
ne
eri
ng
Shar
eP
oin
t D
eve
lop
er(
s)
Pro
ject
Man
age
r
IT M
anag
er
SP D
esi
gne
r (C
on
sult
ant)
Sup
po
rt D
esk
Le
ad/S
MEs
SP A
rch
ite
ct (
Co
nsu
ltan
t)
HR
Dir
ect
or
or
Biz
Re
p
Mar
keti
ng
Dir
ect
or
or
Biz
Re
p
Oth
er
LOB
or
De
par
tme
nt
Business Requirements Document C I A I I I C R R R
Functional Design Doc R C A C I I C I I I
Branding Design &Page Layout Plans I C A I R I C C C I
Communication & Launch Plans C I R,A R I C C C I
Change Management & Control Process R C I A C
Operations & Maintenance Plan R,A I I C I I C
Platform Security Doc & Review R I A I I C
Support Training Material R A I C C
End User Training C A I R C C C C
Responsible for completing that step in the process Accountable for ensuring that step is completed Consulted prior to the completion of that step
Informed of the results once that step is completed
Operational Teams
SharePoint Go LIVE Documents SharePoint Operational
Team
Business Requirements Document C
Functional Design Doc R
Branding Design &Page Layout Plans I
Communication & Launch Plans C
Change Management & Control Process R
Operations & Maintenance Plan R,A
Platform Security Doc & Review R
Support Training Material R
End User Training C
Good questions to ask your “SharePoint Expert”
• How do you propose to separate the platform from solutions?
• Are you architecting the platform or the solution?
Development Test Production
SharePoint Platform
Solu
tio
n
Solu
tio
n
Solu
tio
n
Solu
tio
n
Solu
tio
n
Solu
tio
n
Solu
tio
n
Solu
tio
n
Solu
tio
n
Daily Tasks
• Performing Physical Environmental Checks
• Performing and Monitoring Backups
• Checking Disk Usage
• Checking the Event Viewer
• Monitoring Server Performance
• Monitoring Network Performance
Weekly Tasks
• Archive Event Logs
• Check for Security Updates
• Review SLA Performance Figures
• Archive Data
• Environmental Tests
• Database Maintenance
Monthly Tasks
• Security Checks
• Capacity Planning
• Disaster Recovery Test
Re-consider
Result will always be..
• No planning
• Slow performance
• Ad-hoc backups
• Mixed expectations
• Dissatisfied users/business
Web /App Server Virtualised all in
one box!
Database Backend (Shared with lots of
other apps)
SharePoint 2010 – The decomposition
• Logical Architecture – Server farms
– Service applications
– Application pools
– Web applications
– Zones
– Policy for a Web application
– Content databases
– Site collections
– Sites
DEMO
Resources
• TechNet Script Center
– http://gallery.technet.microsoft.com/ScriptCenter/en-us
Web Front End
Servers (WFE)
Typical NZ deployment scenarios
Start
• Dual/Quad Core Processors
• 8GB for WFE (Virtualised)
• 8GB for APP (Virtualised)
• 8GB for SQL < Shared/Dedicated
Suitable for typical medium size organisations in NZ (200-500 users)
• Collaboration sites (light)
• Project Sites
• Intranet
Application
Servers (WFE)
Database
Backend (Shared)
Web Front End
Servers (WFE)
Typical NZ deployment scenarios
Good
• Dual/Quad Core Processors
• 8GB for WFE (Virtualised)
• 8GB for APP (Virtualised)
• 16GB for SQL on a cluster or log shipping
• Can support more than 1500+ users
Application
Servers (WFE)
Database
Backend (Shared)
Web Front End
Servers (WFE)
Large deployment scenarios
Best (Large high availability)
• Quad Core Processors
• 8>12GB for WFE x 2
• 8>12GB for APP x 2
• 16>32GB for SQL on a cluster with log shipping/mirror
• 10k users
Application
Servers (WFE)
Database
Backend
(Dedicated)
NLB
Managing SharePoint - Discussion
Thank you..
• [email protected] for any questions and feedback on today
• Do you want to work with us?
– Auckland
– Wellington
– Christchurch
• And everywhere else in between…
Thank you to our Sponsors
MS COMMUNITIES