SharePoint 2010 Failed Deployments en English y Español. 10 Pasos Para una Implementacion Exitosa de SharePoint 2010
Upcoming SlideShare
Loading in...5
×
 

SharePoint 2010 Failed Deployments en English y Español. 10 Pasos Para una Implementacion Exitosa de SharePoint 2010

on

  • 2,648 views

From 10 Failed Deployments we'll learn 10 Steps to Successful Deployments. This session was delivered in Mexico City at the SharePoint Seminaro. ...

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 espa

Statistics

Views

Total Views
2,648
Views on SlideShare
2,587
Embed Views
61

Actions

Likes
1
Downloads
38
Comments
0

3 Embeds 61

http://www.slideshare.net 59
http://facebook.slideshare.com 1
http://www.lmodules.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution License

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

SharePoint 2010 Failed Deployments en English y Español. 10 Pasos Para una Implementacion Exitosa de SharePoint 2010 SharePoint 2010 Failed Deployments en English y Español. 10 Pasos Para una Implementacion Exitosa de SharePoint 2010 Presentation Transcript

  • 10 Steps to Successful Deployment
    Joel Oleson
    Sr. Product Architect
    Quest Software
    http://www.sharepointjoel.com
    @joeloleson
  • I’m Back! OtraVez 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
    Most Common
    *SharePoint Foundation
  • Understanding Local Only Service Apps
    *EntepriseService Apps
  • I Need in One Box / Lo Necesito en la MismaCaja:
    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…
  • Live by the K.I.S.S. PrincipleKeep it Simple,Stupid
    Vive por el principio M.S.S. Manten Simple
    Y 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 SiteDefinitions 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/Codigo
    Data/Datos
  • We use one Site Collectionfor all the departments data.
    Nosotrosusamos un solo Site Collection paraalmacenartodanuestrainformacion.
  •  
    Pyramid of SharePoint Information
    Permanent Central Portal
    Enterprise Search
    Enterprise Browse
    Corporate
    Business Taxonomy
    With Divisional
    Stakeholders
    Central
    Portal
    Permanent Division Portals
    Business Process
    Division News, Scorecards
    Group Reporting
    Semi Structured
    Group, Team, Project
    Sites and
    Workspaces
    Ad Hoc Self
    Service
    w/ Life Cycle
    Management
    Per
    User
    Blogs, bios,
    Social
  • 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 desaremosde 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 Computingin SharePoint 2010 Makes Sense
  • SharePoint 2010 Social Computing Overview
    DEMO
  • Sandbox solutions are too complex and JQuerydoesn’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 InPlaceUpgrade 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
  • READY
    v3.5 in late April introduces complete support for 2010
  • READY
    v2.2 in early May introduces 2003-2010 Direct Migrations
  • Accelerate SharePoint 2010 Application Development and build better SharePoint
    In beta READY Q3
  • Recuerdecompletar el formato de evaluaciónparaparticipar en la rifa de los premios
  • Patrocinan
    KED