sharepoint 2010 failed deployments en english y español. 10 pasos para una implementacion exitosa...
DESCRIPTION
From 10 Failed Deployments we'll learn 10 Steps to Successful Deployments. This session was delivered in Mexico City at the SharePoint Seminaro. The Slides are in English 10 Pasos Para una Implementacion Exitosa de SharePoint 2010 Estas diapositivas estan en espaTRANSCRIPT
Joel OlesonSr. Product Architect
Quest Software
http://www.sharepointjoel.com
@joeloleson
10 Steps to Successful Deployment
I’m Back! Otra Vez Con Ustedes!
I don’t know what to do, so I’ll turn it all on…
Nosé que hacer, mejor prendo todo…
Choices - Service Applications
Understanding the MANY SharePoint 2010 Databases
WAN Friendly Service Apps HTTPS WCF + XML
Glo
bally
C
on
sum
able
Business Data Connectivity*
Managed Metadata Service
Search
User Profiles
Secure Store(Single Sign-On)
Web Analytics*
Most Common
*SharePoint
Foundation
Understanding Local Only Service Apps
Local Only
Access Services
Excel Services
Visio Services
Word Auto Conversion
Word Viewing
Office Web Apps
Word Excel PPT OneNote
Lotus Notes Connector
Performance Point
*Enteprise Service Apps
I Need in One Box / Lo Necesito en la Misma Caja:
Project Portfolio Reporting Server PowerPivot Access Services PerformancePoint Fast Search Intranet Publishing Internet Claims based
Extranet…
What’s wrong? They are all MS Products…Cual es el problema, todos son productos de Microsoft…
1010
Live by the K.I.S.S. PrincipleKeep it Simple,Stupid
Vive por el principio M.S.S. Manten SimpleY Sencillo
Our developers don’t like the way SharePoint looks and works, so we’re going to use Site Definitions to get it to look and work the way we want it to…
A nuestros desarrolladores no les gusta como se ve y trabaja SharePoint, por lo que vamos a usar Site Definitions para que se vea y trabaje como queremos …
There aren’t enough triggers for what we need in the databases, we can always remove them later. Come on a little table can easily be removed later…
No hay suficientes triggers para lo que necesitamos en la base de datos, siempre los podemos quitar después. Una pequeña tabla la podemos quitar después…
SharePoint has workflows & approval routing, it’s so much easier when we all work together in the same environment… --- No need for a Test environment…
SharePoint tiene aprobaciones, es mucho mas facil que todos trabajemos en el mismo ambiente.-----No se necesita hacer una prueba de ambiente ----
SharePoint Life Cycle
• Code• Introducti
on• Coexisten
ce
Dev
• UAT• Authoring• POC• Validate
Test• Users• Workflows• BPM
Prod
Code/Codigo
Data/Datos
We use one Site Collection for all the departments data.
Nosotros usamos un solo Site Collection para almacenar toda nuestra informacion.
Pyramid of SharePoint Information
Permanent Central PortalEnterprise SearchEnterprise Browse
Division Portals
Groups & Teams
Projects & Workspaces
My Sites
CorporateBusiness TaxonomyWith DivisionalStakeholders
PerUser
Ad Hoc SelfServicew/ Life CycleManagement
Permanent Division PortalsBusiness Process Division News, ScorecardsGroup Reporting
Semi StructuredGroup, Team, ProjectSites and Workspaces
Blogs, bios, Social
CentralPortal
We believe in SharePoint so we’re shutting down our Public Folders, File Shares and getting rid of attachments in Email.
Nosotros creemos en SharePoint por lo que vamos a cerrar nuestros fólderes públicos, fólderes compartidos, y nos desaremos de los attachments en los e-mails.
“We don’t plan to use My Sites or Social computing in SharePoint 2010 because we don’t want our employees to waste time…”
«No planeamos usar My Sites o Social computing en SharePoint 2010, por que no queremos que nuestros empleados pierdan el tiempo…»
Social Computing in SharePoint 2010 Makes Sense
SharePoint 2010 Social Computing Overview
DEMO
Sandbox solutions are too complex and JQuery doesn’t really add value, server solutions are the only choice.
Las soluciones Sandbox son muy duras y las soluciones Jquery no nos dan nada, server solutiones son la única opcion
We are using InPlace Upgrade because we don’t want to lose anything.
Nosotros usamos InPlace Upgrade por que no queremos perder nada.
10 Major Mistakes I don’t know what to do, so I’ll turn it all on…
Turn the lights on for the Services you need, turn on more as you need them.
Project Management Office needs Project Server, Finance needs Reporting Server, PowerPivot and Access Services, CIO needs PerformancePoint, Enterprise Search for our Intranet, then there’s our Internet Site, oh and our Claims based extranet… we can easily do this in one box… Separate Dev/Test/Prod, but also separate unlike
environments to Keep it Simple. Our developers don’t like the way SharePoint
looks or how it works, so we’re going to use custom Site Definitions to get it to look the way we want it to… Avoid Create Site Defs if at all possible… Use
Solutions Features and Master Pages!
10 Major Mistakes Continued… There aren’t enough triggers for what we need in the
databases, we can always remove them later… Mucking with the database will result in NO SUPPORT from MS,
and failed upgrade. Talk about CO$T! SharePoint has approvals, it’s so much easier when we all
work together in the same environment… Dev environments are required for any Dev work, Test are
mandatory for any SharePoint Environment for testing service packs.
We want our departments to “Share” so we use the same portal for our collaboration, engineering and our intranet publishing, we just use different webs in one site collection. There are many reasons to split out your data 1) Growth 2)
Quota 3) App Dev 4) Manageability 5) Not all departments have the same requirements
10 Major Mistakes Continued. We believe in SharePoint so we’re shutting down our
Public Folders, File Shares and getting rid of attachments in Email. What’s wrong with that? Garbage in Garbage out. Never plan to dump your shares
into SharePoint. We don’t plan to use My Sites or Social computing in
SharePoint 2010 because we don’t want our employees to waste time. Social computing helps overcome silos. Social encourages
cross group collab. Sandbox solutions are too hard and Jquery doesn’t
really get us anywhere. Client solutions free up IT time and provide control.
We are using InPlace Upgrade because we don’t want to lose anything. Study. Database Attach or Hybrid is a better approach.
SharePoint 2010: Best Practices for Upgrading & Migrating
Collection of blogs on Upgrade & Migration Guidance from Joel Oleson, Comics from Dan Lewis, Plus… Anders Rask Upgrading Custom Features & Solutions
Reserve your copy now in Amazon Bit.ly/spupg
Available in Print in August Available now in ebook in Rough
Cuts on Safari http://oreil.ly/SpUpgrade
5 minute Quest Product Update for SharePoint 2010
READY
Cloud Delivered FREE Core Storage Analysis and direct connect to Quest feeds
Available for free at www.quest.com/reportsforsharepoint
v4.0 available now introduces rapid install web client
READY
v3.5 in late April introduces complete support for 2010
READY
v2.2 in early May introduces 2003-2010 Direct Migrations
READY
Accelerate SharePoint 2010 Application Development and build better SharePoint
In beta READY Q3
Recuerde completar el formato de
evaluación para participar en la rifa
de los premios
Patrocinan
KED