10 razones para pasarse a SharePoint 2010

3,686 views
3,557 views

Published on

Si tienes dudas sobre si merece la pena el esfuerzo de migrar a Sharepoint 2010, quizá esta presentación puede ayudarte.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
3,686
On SlideShare
0
From Embeds
0
Number of Embeds
25
Actions
Shares
0
Downloads
117
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  •  User Experience: Ribbon: Once you begin to understand how ribbon works, who will roll back to Office 2003 interface. If you still want to go back, Sharepoint 2010 is not for you.. Future neither.Asynchronous interface.Easy adoption for Silverlight applications Standards: Use Firefox, Chrome, Internet Explorer with no different behaviours.Social capabilities: like an enterprise facebook, ratings, better blogs & wikis (now we can inser images directly from our computer, we don’t need to preupload the image) Document ManagementDocument Centers, Documents Sets, Content Type Hubs,..Less Boundaries for large document management repositories,..Now Sharepoint can compete with ECM Market Leaders (Documentum, Oracle UCM,…) Search:User of wildcards (s*, s* author:ja*,..), refinements, Results management, Search is aware about social behavior of users (if I am a sharpeoint expert I will be a result where someone searches for sharepoint).Use of Fast increases our search control.. Service Architecture.Take Decisions about where services we need to start and which services are engaged with each web applicationBetter Performance & Boundaries: To explain… (Web Server throttling,..) IsolationTenants: 2 Sharepoint domains (customers, departments, areas,…) can now have data, customizations and processes completely isolated and share the farm and central administrationSandbox Solutions: Isolated applications to avoid a farm crash if the applications trhoughs an exception. Fast DevelopmentSharepoint  Designer now is a powerful tood for rapid application development. We can define more workflow actions, modify lists views, create external lists and do and deploy with WSP PackagesVisual Studio now is completely integrated with Sharepoint development Cycle. AvailabilityUpgrading: Better Patch Management, I hope we can avoid Service packs hell…WSP makes deployments easier , Sandbox makes sharepoint more stable. Easy Easier Migration From 2007 to 20102007 and 2010 are .NET platform Based, we have more tools now to do faster migrations and with more successful probability. ConnectivityFrom BDC (Business Data Catalog in 2007) to BCS (Business Connectivity Services in 2010). Read /Write for External databases, entities and applications. New ServicesAccess Services: Move your access application from desktop to web with only a little bit effort.Performance Point Services: Powerful Business Intelligence toolsOffice Web ApplicationsShare, edit, and review your Excel, powerpoint, word files with only a browser.   And what’s more important, A few reasons not key to migrate: Sharepoint Mobile: Actually I haven’t seen any changes in mobile interfaceLanguage Support: ok, we can use resource files and change the language on real-time, but… What about same site language publishing…Web publishing: I think ribbon here is not a useful feature.. and I can’t see any improvement here. Maybe Sharepoint standard license for internet sites?Next, Next, Next…. Installed. Not true in real customer scenarios. Capacity Plan, Service Architecture,…With Office Web Applications I don’t need to pay Office Client License… Ha, ha, ha.. Sure?Claim Authentication will solve single sign on problems between companies.. Claims are a not a mature technology as fas as I can test… Even there aren’t good tools for manage it.
  • Importante punto a mejorar en cualquier versión de cualquier producto, y es que la experiencia de usuario no es sólo satisfacción, sinó también tiempo. Sharepoint 2010 mejora mediante elementos como la interfaz basada en Atlas (Ajax), la ribbon, o la integración nativa de aplicaciones Silverlight.  Los usuarios ahora se encontraran en un entorno más productivo, aunque como pasó ya con la Ribbon en Office 2007, cuesta un poquito acostumbrarse.. JSin olvidar tampoco que la adopción de standards en esta versión nos evitará más de un dolor de cabeza.
  • Muchas de las funcionalidades que demandamos los implantadores en el pasado para competir con los grandes ECM’s del mercado se han visto resueltas en esta versión. Podemos manejar grandes volúmenes de documentos sin limitación y, sobretodo, sin que el servidor vea penalizado su rendimiento. Y ahora incorporamos nuevas funcionalidades como por ejemplo los conjuntos de documentos (document sets), o los publicadores de tipos de contenidos, entre otras..
  • La incorporación de FAST ha sido un punto de mejora importante, pero realmente no necesitamos incorporar FAST a nuestra instalación de 2010 para beneficiarnos de una, ahora sí, buena búsqueda ya desde la versión más básica del producto. Ya podemos filtrar por propiedades (Author: Me), utilizar wildcards (shp*) o lógica combinatoria en el cuadro de búsqueda. (Sharepoint AND 2010)  
  • La incorporación de FAST ha sido un punto de mejora importante, pero realmente no necesitamos incorporar FAST a nuestra instalación de 2010 para beneficiarnos de una, ahora sí, buena búsqueda ya desde la versión más básica del producto. Ya podemos filtrar por propiedades (Author: Me), utilizar wildcards (shp*) o lógica combinatoria en el cuadro de búsqueda. (Sharepoint AND 2010)  
  • Motor de FAST: Por ejemplo, tiene en cuenta si búscas una fecha su formato. Tiene un diccionario avanzado.,…
  • Los proveedores de servicioscompartidosya no seránnuncamásunabarreraarquitectónica. Ahora tenemos muchos más servicios disponibles y  podemos decidir que topología debe tener nuestra granja con completa libertad. Lo que nos permite aprovechar mejor los recursos hardware, mejorar la seguridad y aumentar el rendimiento y seguridad de nuestro despliegue.
  • El uso de “Tenants” nospermiteaislar los datos, adaptaciones, procesos y servicios. Podemos aprovechar esta nueva tecnología para ubicar diversos clientes, departamentos o zonas de seguridad en un mismo sharepoint. El uso de soluciones “sandbox”, además, ahora nos permite que si un código falla, no afecte al resto del portal.
  • Esa palabra que nadie entiende pero que todos estábamos buscandoIsolation of data, operational services, and managementDataUsageAdministrationCustomizationsOperations
  • Tanto SharepointDesigner como Visual Studio son ahora herramientas más potentes y más integradas tanto con sharepoint como entre ellas. Todos los despliegues ahora se realizan con paquetes, lo que ayuda a formalizar y controlar mucho más el proceso.
  • Tanto SharepointDesigner como Visual Studio son ahora herramientas más potentes y más integradas tanto con sharepoint como entre ellas. Todos los despliegues ahora se realizan con paquetes, lo que ayuda a formalizar y controlar mucho más el proceso.
  • Tanto SharepointDesigner como Visual Studio son ahora herramientas más potentes y más integradas tanto con sharepoint como entre ellas. Todos los despliegues ahora se realizan con paquetes, lo que ayuda a formalizar y controlar mucho más el proceso.
  • Las tecnologías que acabamos de comentar (despliegue con paquetes WSP, sandboxsolutions, tenants) nos permiten aumentar alta disponibilidad del servidor. Además, el proceso de actualización del servidor resulta ahora más cómodo y controlado. 
  • Las tecnologías que acabamos de comentar (despliegue con paquetes WSP, sandboxsolutions, tenants) nos permiten aumentar alta disponibilidad del servidor. Además, el proceso de actualización del servidor resulta ahora más cómodo y controlado. 
  • Las tecnologías que acabamos de comentar (despliegue con paquetes WSP, sandboxsolutions, tenants) nos permiten aumentar alta disponibilidad del servidor. Además, el proceso de actualización del servidor resulta ahora más cómodo y controlado. 
  • Ahora ya podemos comprobar si nuestra instalación actual dará problemas antes de poner una mano encima de un bit J. Y si da problemas, podemos pasar el sitio “tal cual” se ve en 2007 a la versión 2010 gracias al modo de compatibilidad. Esto es posible gracias a que de 2007 a 2010 no nos movemos de plataforma J (de .NET a .NET) mientras que de 2003 a 2007 debíamos de pasar de COM a .NET. L. Pero no todo es felicidad en la vida del implementador, los desarrollos realizados en 2007 habrá que revisarlos con lupa…
  • ¿Coger datos de una Fuente externa y tratarlos en modo lectura /escritura como si de listas de sharepoint se tratara?, ¿Qué esas fuentes externas no tiene porqué ser bases de datos, sinó que pueden ser entidades, repositorios externos o podemos incluir lógica de negocio? Sí, eso es la conectividad en 2010.. Bienvenidos a Business ConnectivityServices.
  •         Y por supuesto, aquellos nuevos desarrollos que nos harán la vida un poquito más fácil… no?.                a.       Access Services: o Cómo pasar de tu Access en escritorio a un entorno web…b.      Performance Point Services: Herramientas absolutamente útiles para Business Intelligence (ahora llamada Insights)c.       Office Web Applications: Para compartir en tiempo real, ver o editar en nuestro navegador documentos Office.
  •         Y por supuesto, aquellos nuevos desarrollos que nos harán la vida un poquito más fácil… no?.                a.       Access Services: o Cómo pasar de tu Access en escritorio a un entorno web…b.      Performance Point Services: Herramientas absolutamente útiles para Business Intelligence (ahora llamada Insights)c.       Office Web Applications: Para compartir en tiempo real, ver o editar en nuestro navegador documentos Office.
  •         Y por supuesto, aquellos nuevos desarrollos que nos harán la vida un poquito más fácil… no?.                a.       Access Services: o Cómo pasar de tu Access en escritorio a un entorno web…b.      Performance Point Services: Herramientas absolutamente útiles para Business Intelligence (ahora llamada Insights)c.       Office Web Applications: Para compartir en tiempo real, ver o editar en nuestro navegador documentos Office.
  •         Y por supuesto, aquellos nuevos desarrollos que nos harán la vida un poquito más fácil… no?.                a.       Access Services: o Cómo pasar de tu Access en escritorio a un entorno web…b.      Performance Point Services: Herramientas absolutamente útiles para Business Intelligence (ahora llamada Insights)c.       Office Web Applications: Para compartir en tiempo real, ver o editar en nuestro navegador documentos Office.
  •  User Experience: Ribbon: Once you begin to understand how ribbon works, who will roll back to Office 2003 interface. If you still want to go back, Sharepoint 2010 is not for you.. Future neither.Asynchronous interface.Easy adoption for Silverlight applications Standards: Use Firefox, Chrome, Internet Explorer with no different behaviours.Social capabilities: like an enterprise facebook, ratings, better blogs & wikis (now we can inser images directly from our computer, we don’t need to preupload the image) Document ManagementDocument Centers, Documents Sets, Content Type Hubs,..Less Boundaries for large document management repositories,..Now Sharepoint can compete with ECM Market Leaders (Documentum, Oracle UCM,…) Search:User of wildcards (s*, s* author:ja*,..), refinements, Results management, Search is aware about social behavior of users (if I am a sharpeoint expert I will be a result where someone searches for sharepoint).Use of Fast increases our search control.. Service Architecture.Take Decisions about where services we need to start and which services are engaged with each web applicationBetter Performance & Boundaries: To explain… (Web Server throttling,..) IsolationTenants: 2 Sharepoint domains (customers, departments, areas,…) can now have data, customizations and processes completely isolated and share the farm and central administrationSandbox Solutions: Isolated applications to avoid a farm crash if the applications trhoughs an exception. Fast DevelopmentSharepoint  Designer now is a powerful tood for rapid application development. We can define more workflow actions, modify lists views, create external lists and do and deploy with WSP PackagesVisual Studio now is completely integrated with Sharepoint development Cycle. AvailabilityUpgrading: Better Patch Management, I hope we can avoid Service packs hell…WSP makes deployments easier , Sandbox makes sharepoint more stable. Easy Easier Migration From 2007 to 20102007 and 2010 are .NET platform Based, we have more tools now to do faster migrations and with more successful probability. ConnectivityFrom BDC (Business Data Catalog in 2007) to BCS (Business Connectivity Services in 2010). Read /Write for External databases, entities and applications. New ServicesAccess Services: Move your access application from desktop to web with only a little bit effort.Performance Point Services: Powerful Business Intelligence toolsOffice Web ApplicationsShare, edit, and review your Excel, powerpoint, word files with only a browser.   And what’s more important, A few reasons not key to migrate: Sharepoint Mobile: Actually I haven’t seen any changes in mobile interfaceLanguage Support: ok, we can use resource files and change the language on real-time, but… What about same site language publishing…Web publishing: I think ribbon here is not a useful feature.. and I can’t see any improvement here. Maybe Sharepoint standard license for internet sites?Next, Next, Next…. Installed. Not true in real customer scenarios. Capacity Plan, Service Architecture,…With Office Web Applications I don’t need to pay Office Client License… Ha, ha, ha.. Sure?Claim Authentication will solve single sign on problems between companies.. Claims are a not a mature technology as fas as I can test… Even there aren’t good tools for manage it.
  •  User Experience: Ribbon: Once you begin to understand how ribbon works, who will roll back to Office 2003 interface. If you still want to go back, Sharepoint 2010 is not for you.. Future neither.Asynchronous interface.Easy adoption for Silverlight applications Standards: Use Firefox, Chrome, Internet Explorer with no different behaviours.Social capabilities: like an enterprise facebook, ratings, better blogs & wikis (now we can inser images directly from our computer, we don’t need to preupload the image) Document ManagementDocument Centers, Documents Sets, Content Type Hubs,..Less Boundaries for large document management repositories,..Now Sharepoint can compete with ECM Market Leaders (Documentum, Oracle UCM,…) Search:User of wildcards (s*, s* author:ja*,..), refinements, Results management, Search is aware about social behavior of users (if I am a sharpeoint expert I will be a result where someone searches for sharepoint).Use of Fast increases our search control.. Service Architecture.Take Decisions about where services we need to start and which services are engaged with each web applicationBetter Performance & Boundaries: To explain… (Web Server throttling,..) IsolationTenants: 2 Sharepoint domains (customers, departments, areas,…) can now have data, customizations and processes completely isolated and share the farm and central administrationSandbox Solutions: Isolated applications to avoid a farm crash if the applications trhoughs an exception. Fast DevelopmentSharepoint  Designer now is a powerful tood for rapid application development. We can define more workflow actions, modify lists views, create external lists and do and deploy with WSP PackagesVisual Studio now is completely integrated with Sharepoint development Cycle. AvailabilityUpgrading: Better Patch Management, I hope we can avoid Service packs hell…WSP makes deployments easier , Sandbox makes sharepoint more stable. Easy Easier Migration From 2007 to 20102007 and 2010 are .NET platform Based, we have more tools now to do faster migrations and with more successful probability. ConnectivityFrom BDC (Business Data Catalog in 2007) to BCS (Business Connectivity Services in 2010). Read /Write for External databases, entities and applications. New ServicesAccess Services: Move your access application from desktop to web with only a little bit effort.Performance Point Services: Powerful Business Intelligence toolsOffice Web ApplicationsShare, edit, and review your Excel, powerpoint, word files with only a browser.   And what’s more important, A few reasons not key to migrate: Sharepoint Mobile: Actually I haven’t seen any changes in mobile interfaceLanguage Support: ok, we can use resource files and change the language on real-time, but… What about same site language publishing…Web publishing: I think ribbon here is not a useful feature.. and I can’t see any improvement here. Maybe Sharepoint standard license for internet sites?Next, Next, Next…. Installed. Not true in real customer scenarios. Capacity Plan, Service Architecture,…With Office Web Applications I don’t need to pay Office Client License… Ha, ha, ha.. Sure?Claim Authentication will solve single sign on problems between companies.. Claims are a not a mature technology as fas as I can test… Even there aren’t good tools for manage it.
  •  User Experience: Ribbon: Once you begin to understand how ribbon works, who will roll back to Office 2003 interface. If you still want to go back, Sharepoint 2010 is not for you.. Future neither.Asynchronous interface.Easy adoption for Silverlight applications Standards: Use Firefox, Chrome, Internet Explorer with no different behaviours.Social capabilities: like an enterprise facebook, ratings, better blogs & wikis (now we can inser images directly from our computer, we don’t need to preupload the image) Document ManagementDocument Centers, Documents Sets, Content Type Hubs,..Less Boundaries for large document management repositories,..Now Sharepoint can compete with ECM Market Leaders (Documentum, Oracle UCM,…) Search:User of wildcards (s*, s* author:ja*,..), refinements, Results management, Search is aware about social behavior of users (if I am a sharpeoint expert I will be a result where someone searches for sharepoint).Use of Fast increases our search control.. Service Architecture.Take Decisions about where services we need to start and which services are engaged with each web applicationBetter Performance & Boundaries: To explain… (Web Server throttling,..) IsolationTenants: 2 Sharepoint domains (customers, departments, areas,…) can now have data, customizations and processes completely isolated and share the farm and central administrationSandbox Solutions: Isolated applications to avoid a farm crash if the applications trhoughs an exception. Fast DevelopmentSharepoint  Designer now is a powerful tood for rapid application development. We can define more workflow actions, modify lists views, create external lists and do and deploy with WSP PackagesVisual Studio now is completely integrated with Sharepoint development Cycle. AvailabilityUpgrading: Better Patch Management, I hope we can avoid Service packs hell…WSP makes deployments easier , Sandbox makes sharepoint more stable. Easy Easier Migration From 2007 to 20102007 and 2010 are .NET platform Based, we have more tools now to do faster migrations and with more successful probability. ConnectivityFrom BDC (Business Data Catalog in 2007) to BCS (Business Connectivity Services in 2010). Read /Write for External databases, entities and applications. New ServicesAccess Services: Move your access application from desktop to web with only a little bit effort.Performance Point Services: Powerful Business Intelligence toolsOffice Web ApplicationsShare, edit, and review your Excel, powerpoint, word files with only a browser.   And what’s more important, A few reasons not key to migrate: Sharepoint Mobile: Actually I haven’t seen any changes in mobile interfaceLanguage Support: ok, we can use resource files and change the language on real-time, but… What about same site language publishing…Web publishing: I think ribbon here is not a useful feature.. and I can’t see any improvement here. Maybe Sharepoint standard license for internet sites?Next, Next, Next…. Installed. Not true in real customer scenarios. Capacity Plan, Service Architecture,…With Office Web Applications I don’t need to pay Office Client License… Ha, ha, ha.. Sure?Claim Authentication will solve single sign on problems between companies.. Claims are a not a mature technology as fas as I can test… Even there aren’t good tools for manage it.
  • Reports farm and server dataIdentifies useful farm informationServers, databases, AAMSite definitions, features, language packsSearchContentSourceInfoA list of the content sources and start addresses for each shared service provider in the farm.SearchInfoA list of the components of the search topology for the farm.See Pre-upgrade scanning and reporting for future releases (Office SharePoint Server) http://technet.microsoft.com/en-us/library/dd793609.aspx#bk_rules
  • 956201 The LargeLists rule in Pre-Upgrade Checker for Windows SharePoint Services 3.0 Service Pack 2 can warn about large lists circuit breaker 956447 The ModifiedWorkflowActionsFile rule in Pre-Upgrade Checker can warn that the default declarative workflow actions file has been modified 956448 The CustomWorkflowActionsFiles rule in Pre-Upgrade Checker in Windows SharePoint Services 3.0 Service Pack 2 can warn that custom .ACTIONS files exist in the farm 956449 The ModifiedWebConfigWorkflowAuthorizedTypes rule in Pre-Upgrade Checker for Windows SharePoint Services 3.0 Service Pack 2 can warn that Web.config files contain modified authorized types for workflow 956450 The CustomListView rule in Pre-Upgrade Checker can warn that customized list views that will not be upgraded 956451 The CustomFieldType rule in Pre-Upgrade Checker in Windows SharePoint Services 3.0 Service Pack 2 can warn that customized field types will not be upgraded
  •  User Experience: Ribbon: Once you begin to understand how ribbon works, who will roll back to Office 2003 interface. If you still want to go back, Sharepoint 2010 is not for you.. Future neither.Asynchronous interface.Easy adoption for Silverlight applications Standards: Use Firefox, Chrome, Internet Explorer with no different behaviours.Social capabilities: like an enterprise facebook, ratings, better blogs & wikis (now we can inser images directly from our computer, we don’t need to preupload the image) Document ManagementDocument Centers, Documents Sets, Content Type Hubs,..Less Boundaries for large document management repositories,..Now Sharepoint can compete with ECM Market Leaders (Documentum, Oracle UCM,…) Search:User of wildcards (s*, s* author:ja*,..), refinements, Results management, Search is aware about social behavior of users (if I am a sharpeoint expert I will be a result where someone searches for sharepoint).Use of Fast increases our search control.. Service Architecture.Take Decisions about where services we need to start and which services are engaged with each web applicationBetter Performance & Boundaries: To explain… (Web Server throttling,..) IsolationTenants: 2 Sharepoint domains (customers, departments, areas,…) can now have data, customizations and processes completely isolated and share the farm and central administrationSandbox Solutions: Isolated applications to avoid a farm crash if the applications trhoughs an exception. Fast DevelopmentSharepoint  Designer now is a powerful tood for rapid application development. We can define more workflow actions, modify lists views, create external lists and do and deploy with WSP PackagesVisual Studio now is completely integrated with Sharepoint development Cycle. AvailabilityUpgrading: Better Patch Management, I hope we can avoid Service packs hell…WSP makes deployments easier , Sandbox makes sharepoint more stable. Easy Easier Migration From 2007 to 20102007 and 2010 are .NET platform Based, we have more tools now to do faster migrations and with more successful probability. ConnectivityFrom BDC (Business Data Catalog in 2007) to BCS (Business Connectivity Services in 2010). Read /Write for External databases, entities and applications. New ServicesAccess Services: Move your access application from desktop to web with only a little bit effort.Performance Point Services: Powerful Business Intelligence toolsOffice Web ApplicationsShare, edit, and review your Excel, powerpoint, word files with only a browser.   And what’s more important, A few reasons not key to migrate: Sharepoint Mobile: Actually I haven’t seen any changes in mobile interfaceLanguage Support: ok, we can use resource files and change the language on real-time, but… What about same site language publishing…Web publishing: I think ribbon here is not a useful feature.. and I can’t see any improvement here. Maybe Sharepoint standard license for internet sites?Next, Next, Next…. Installed. Not true in real customer scenarios. Capacity Plan, Service Architecture,…With Office Web Applications I don’t need to pay Office Client License… Ha, ha, ha.. Sure?Claim Authentication will solve single sign on problems between companies.. Claims are a not a mature technology as fas as I can test… Even there aren’t good tools for manage it.
  •  User Experience: Ribbon: Once you begin to understand how ribbon works, who will roll back to Office 2003 interface. If you still want to go back, Sharepoint 2010 is not for you.. Future neither.Asynchronous interface.Easy adoption for Silverlight applications Standards: Use Firefox, Chrome, Internet Explorer with no different behaviours.Social capabilities: like an enterprise facebook, ratings, better blogs & wikis (now we can inser images directly from our computer, we don’t need to preupload the image) Document ManagementDocument Centers, Documents Sets, Content Type Hubs,..Less Boundaries for large document management repositories,..Now Sharepoint can compete with ECM Market Leaders (Documentum, Oracle UCM,…) Search:User of wildcards (s*, s* author:ja*,..), refinements, Results management, Search is aware about social behavior of users (if I am a sharpeoint expert I will be a result where someone searches for sharepoint).Use of Fast increases our search control.. Service Architecture.Take Decisions about where services we need to start and which services are engaged with each web applicationBetter Performance & Boundaries: To explain… (Web Server throttling,..) IsolationTenants: 2 Sharepoint domains (customers, departments, areas,…) can now have data, customizations and processes completely isolated and share the farm and central administrationSandbox Solutions: Isolated applications to avoid a farm crash if the applications trhoughs an exception. Fast DevelopmentSharepoint  Designer now is a powerful tood for rapid application development. We can define more workflow actions, modify lists views, create external lists and do and deploy with WSP PackagesVisual Studio now is completely integrated with Sharepoint development Cycle. AvailabilityUpgrading: Better Patch Management, I hope we can avoid Service packs hell…WSP makes deployments easier , Sandbox makes sharepoint more stable. Easy Easier Migration From 2007 to 20102007 and 2010 are .NET platform Based, we have more tools now to do faster migrations and with more successful probability. ConnectivityFrom BDC (Business Data Catalog in 2007) to BCS (Business Connectivity Services in 2010). Read /Write for External databases, entities and applications. New ServicesAccess Services: Move your access application from desktop to web with only a little bit effort.Performance Point Services: Powerful Business Intelligence toolsOffice Web ApplicationsShare, edit, and review your Excel, powerpoint, word files with only a browser.   And what’s more important, A few reasons not key to migrate: Sharepoint Mobile: Actually I haven’t seen any changes in mobile interfaceLanguage Support: ok, we can use resource files and change the language on real-time, but… What about same site language publishing…Web publishing: I think ribbon here is not a useful feature.. and I can’t see any improvement here. Maybe Sharepoint standard license for internet sites?Next, Next, Next…. Installed. Not true in real customer scenarios. Capacity Plan, Service Architecture,…With Office Web Applications I don’t need to pay Office Client License… Ha, ha, ha.. Sure?Claim Authentication will solve single sign on problems between companies.. Claims are a not a mature technology as fas as I can test… Even there aren’t good tools for manage it.
  •  User Experience: Ribbon: Once you begin to understand how ribbon works, who will roll back to Office 2003 interface. If you still want to go back, Sharepoint 2010 is not for you.. Future neither.Asynchronous interface.Easy adoption for Silverlight applications Standards: Use Firefox, Chrome, Internet Explorer with no different behaviours.Social capabilities: like an enterprise facebook, ratings, better blogs & wikis (now we can inser images directly from our computer, we don’t need to preupload the image) Document ManagementDocument Centers, Documents Sets, Content Type Hubs,..Less Boundaries for large document management repositories,..Now Sharepoint can compete with ECM Market Leaders (Documentum, Oracle UCM,…) Search:User of wildcards (s*, s* author:ja*,..), refinements, Results management, Search is aware about social behavior of users (if I am a sharpeoint expert I will be a result where someone searches for sharepoint).Use of Fast increases our search control.. Service Architecture.Take Decisions about where services we need to start and which services are engaged with each web applicationBetter Performance & Boundaries: To explain… (Web Server throttling,..) IsolationTenants: 2 Sharepoint domains (customers, departments, areas,…) can now have data, customizations and processes completely isolated and share the farm and central administrationSandbox Solutions: Isolated applications to avoid a farm crash if the applications trhoughs an exception. Fast DevelopmentSharepoint  Designer now is a powerful tood for rapid application development. We can define more workflow actions, modify lists views, create external lists and do and deploy with WSP PackagesVisual Studio now is completely integrated with Sharepoint development Cycle. AvailabilityUpgrading: Better Patch Management, I hope we can avoid Service packs hell…WSP makes deployments easier , Sandbox makes sharepoint more stable. Easy Easier Migration From 2007 to 20102007 and 2010 are .NET platform Based, we have more tools now to do faster migrations and with more successful probability. ConnectivityFrom BDC (Business Data Catalog in 2007) to BCS (Business Connectivity Services in 2010). Read /Write for External databases, entities and applications. New ServicesAccess Services: Move your access application from desktop to web with only a little bit effort.Performance Point Services: Powerful Business Intelligence toolsOffice Web ApplicationsShare, edit, and review your Excel, powerpoint, word files with only a browser.   And what’s more important, A few reasons not key to migrate: Sharepoint Mobile: Actually I haven’t seen any changes in mobile interfaceLanguage Support: ok, we can use resource files and change the language on real-time, but… What about same site language publishing…Web publishing: I think ribbon here is not a useful feature.. and I can’t see any improvement here. Maybe Sharepoint standard license for internet sites?Next, Next, Next…. Installed. Not true in real customer scenarios. Capacity Plan, Service Architecture,…With Office Web Applications I don’t need to pay Office Client License… Ha, ha, ha.. Sure?Claim Authentication will solve single sign on problems between companies.. Claims are a not a mature technology as fas as I can test… Even there aren’t good tools for manage it.
  •         Y por supuesto, aquellos nuevos desarrollos que nos harán la vida un poquito más fácil… no?.                a.       Access Services: o Cómo pasar de tu Access en escritorio a un entorno web…b.      Performance Point Services: Herramientas absolutamente útiles para Business Intelligence (ahora llamada Insights)c.       Office Web Applications: Para compartir en tiempo real, ver o editar en nuestro navegador documentos Office.
  • 10 razones para pasarse a SharePoint 2010

    1. 1. 10 razones para pasarse a Sharepoint 2010<br />SharePoint 2010<br />“Roadmap” de adopción<br />Jorge Ramo López<br />Jorge.ramo@raona.com<br />
    2. 2. SharePoint 2010<br />¿Porqué Pasarme a Sharepoint 2010?<br />… Si ya tengo Sharepoint 2007<br />… Si ya tengo una web en marcha<br />… Si ya tengo un gestor de contenidos X, Y o Z<br />… Si yahagogestión documental<br />… Si ni siquiera sé lo que es Sharepoint<br />
    3. 3. SharePoint 2010<br />1<br />Experiencia de Usuario<br />
    4. 4. SharePoint 2010<br />Ribbon<br />1<br />Experiencia de Usuario<br />Es contextual<br />Análoga al paquete Office<br />
    5. 5. SharePoint 2010<br />Interfaz Asíncrona<br />1<br />Experiencia de Usuario<br />No hay recarga<br />
    6. 6. SharePoint 2010<br />Integración de aplicaciones Silverlight<br />1<br />Experiencia de Usuario<br />Sólo indicando el fichero Silverlight<br />
    7. 7. SharePoint 2010<br />Integración de aplicaciones Office<br />1<br />Experiencia de Usuario<br />Actualizado en tiempo real<br />
    8. 8. SharePoint 2010<br />Cross- Browser Compatibility<br />1<br />Experiencia de Usuario<br />Cumple con Standards Web<br />
    9. 9. SharePoint 2010<br />Funcionalidades Sociales<br />1<br />Experiencia de Usuario<br />Características de Red Social Corporativa<br />
    10. 10. SharePoint 2010<br />Funcionalidades Sociales<br />1<br />Experiencia de Usuario<br />
    11. 11. SharePoint 2010<br />2<br />Gestión de Documentación<br />
    12. 12. SharePoint 2010<br />Mejoras funcionales y de rendimiento<br />2<br />Gestión de Documentación<br /><ul><li>Sin limitaciones de límite de documentos en cada centro documental
    13. 13. El rendimiento del servidor se adapta al volumen de documentación asociado
    14. 14. Podemos publicar tipos de contenido entre los diferentes apartados de un portal
    15. 15. Podemos gestionar los metadatos de forma centralizada a través de taxonomías
    16. 16. Mediantes conexiones a datos externos podemos conectar con cuadros de clasificación ya existentes</li></li></ul><li>SharePoint 2010<br />Document set<br />2<br />Gestión de Documentación<br />Caso Típico de «Expediente»<br />
    17. 17. SharePoint 2010<br />3<br />Búsqueda<br />
    18. 18. SharePoint 2010<br />3<br />Búsqueda<br />OpenSearch Source<br />Query Object Model<br /><ul><li>Podemos usar Wildcards en nuestra búsqueda, incluso utilizando Metadatos:</li></ul>S* b* author:ja* AND B*J*<br /><ul><li>Los resultados tienen filtros para ayudarnos a refinar la búsqueda
    19. 19. Búsqueda social teniendo en cuenta las actividades, publicaciones, notas, metadatos, tags de nuestros usuarios
    20. 20. Búsqueda fonética («maikel»)
    21. 21. Mayor escalabilidad en la definición de los componentes</li></ul>Query Servers<br />Index Partition<br />Indexer<br />Crawler<br />Content<br />Content<br />Content<br />Es más fácil «buscar» y «encontrar»<br />
    22. 22. SharePoint 2010<br />3<br />Búsqueda<br />Resultados de ejemplo de búsqueda<br />Win7 Connector<br />Related searches<br />Launch in Office Web Apps<br />Refinement panel<br />Federated results<br />
    23. 23. SharePoint 2010<br />Content search<br />3<br />Se incorpora FAST como producto<br />FAST Search <br />for SharePoint<br />Búsqueda<br />Enterprise Crawler<br />JDBC<br />FAST Query Language (FQL)<br />OM extensions<br />Web Part extensions<br />People search<br />SharePoint Server<br />
    24. 24. SharePoint 2010<br />4<br />Arquitectura de Servicios<br />
    25. 25. SharePoint 2010<br />4<br />Servicios a la carta<br />Arquitectura de Servicios<br /><ul><li>Desaparece el concepto de «Proveedor de servicios compartidos».
    26. 26. Ahora cada servicio se provee por sí mismo.
    27. 27. Muchos más servicios (Office Services) y posibilidad de crear nuevos.
    28. 28. Podemos elegir qué partes de nuestro Sharepoint son accesibles a quién
    29. 29. Tenemos un modelo
    30. 30. Más escalable,
    31. 31. Más flexible
    32. 32. Aprovecha mejor las máquina dedicadas a Sharepoint
    33. 33. Mejora la seguridad de acceso
    34. 34. Web Server Throttlingo servidor adaptado al rendimiento</li></li></ul><li>SharePoint 2010<br />SSP<br />Search<br />UserProfiles<br />Excel Calc<br />UserProfiles<br />Search<br />BDC<br />Visio <br />Excel Calc<br />BDC<br />WAC<br />3rd party Service<br />http://itweb/<br />http://hrweb/<br />http://hrweb/<br />http://itweb/<br />Corp Farm<br />Corp Farm<br />MOSS 2007 Model<br />O14 Model<br />
    35. 35. SharePoint 2010<br />5<br />Aislamiento<br />
    36. 36. SharePoint 2010<br />Tenants<br />5<br />Aislamiento<br /><ul><li>1 tenantes un espacio donde se aislan:
    37. 37. Los Datos
    38. 38. El uso de las aplicaciones
    39. 39. La administración
    40. 40. Las personalizaciones
    41. 41. Las operaciones
    42. 42. Ejemplo: 1 tenant por cliente. Cada cliente es un espacio completamente independiente de los demás bajo un mismo despliegue de Sharepoint.</li></li></ul><li>SharePoint 2010<br />Mejorar ROI de hardware<br />5<br />Aislamiento<br /><ul><li>Gracias a la arquitectura de servicios y al aislamiento 1 misma granja de servidores puede albergar diversos usos
    43. 43. Intranet
    44. 44. Extranet
    45. 45. Webs
    46. 46. Certificando la seguridad y la alta disponibilidad</li></li></ul><li>SharePoint 2010<br />Sandboxsolutions<br />5<br />Aislamiento<br /><ul><li>Las aplicaciones de los desarrolladores se ejecutan en espacios aislados de manera que si provocan un error o consumen muchos recursos no afectan a la granja.</li></ul>Quota/Blocked Solutions<br />Limited <br />OM<br />CAS<br />Developers<br />External Process<br />
    47. 47. SharePoint 2010<br />6<br />Desarrollo Ágil<br />
    48. 48. SharePoint 2010<br />Aumentar Capacidades de cada perfil<br />6<br />Desarrollo Ágil<br />Visual Studio<br />Dev<br />SharePoint Designer<br />InfoPath<br />RAD<br />Application Complexity<br />PIW<br />SharePoint Browser UI<br />IWs<br />Technical Difficulty<br />
    49. 49. SharePoint 2010<br />6<br />SharepointDesigner es más potente<br />Desarrollo Ágil<br /><ul><li>Todo se despliega con paquetes
    50. 50. Un paquete es compatible entre SPD y Visual Studio
    51. 51. Podemos hacer Workflows más potentes, conectar con datos externos</li></li></ul><li>SharePoint 2010<br />6<br />Visual Studio 2010<br />Desarrollo Ágil<br />Nueva versión completamente integrada con Sharepoint 2010<br />
    52. 52. SharePoint 2010<br />7<br />Alta Disponibilidad<br />
    53. 53. SharePoint 2010<br />7<br />Proceso controlado de Patching<br />Alta Disponibilidad<br />
    54. 54. SharePoint 2010<br />7<br />Sistema unificado Monitorización<br />Alta Disponibilidad<br /> 0x1640 Windows SharePoint Services 4 Monitoring nasq Medium Entering monitored scope (Request (GET:http://cp-ap02l:8080/_layouts/WebAnalytics/WebAppSelection.aspx?t=WebApplicationSelectionReport&l=wa)) <br />07/29/2009 18:32:48.35 w3wp.exe (0x15A8) 0x1640 Windows SharePoint Services 4 Logging Correlation Data xmnv Medium Name=Request (GET:http://cp-ap02l:8080/_layouts/WebAnalytics/WebAppSelection.aspx?t=WebApplicationSelectionReport&l=wa) 750cfa80-cba6-4516-b367-a68698421c23<br />07/29/2009 18:32:48.64 w3wp.exe (0x15A8) 0x1640 Windows SharePoint Services 4 Logging Correlation Data xmnv Medium Site=/ 750cfa80-cba6-4516-b367-a68698421c23<br />07/29/2009 18:32:48.75 w3wp.exe (0x15A8) 0x1640 Windows SharePoint Services 4 Topology b9h6 Medium The configuration database was queried for a non-existent object with the id d2a43842-8650-4522-9e8c-a838795933bd. Most commonly, this is caused by removing an SPFeatureDefinition without writing upgrade code to remove references to the feature from each site. 750cfa80-cba6-4516-b367-a68698421c23<br />07/29/2009 18:32:48.75 w3wp.exe (0x15A8) 0x1640 Windows SharePoint Services 4 Monitoring b4ly Medium Leaving Monitored Scope (Request (GET:http://cp-ap02l:8080/_layouts/WebAnalytics/WebAppSelection.aspx?t=WebApplicationSelectionReport&l=wa)). 750cfa80-cba6-4516-b367-a68698421c23<br />07/29/2009 18:32:48.75 w3wp.exe (0x15A8) 0x1640 Windows SharePoint Services 4 Monitoring nass Medium ____SPRequest Objects=2 750cfa80-cba6-4516-b367-a68698421c23<br />07/29/2009 18:32:48.75 w3wp.exe (0x15A8) 0x1640 Windows SharePoint Services 4 Monitoring nass Medium ____SQL Query Count=3 750cfa80-cba6-4516-b367-a68698421c23<br />07/29/2009 18:32:48.75 w3wp.exe (0x15A8) 0x1640 Windows SharePoint Services 4 Monitoring nass Medium ____Execution Time=412.184230118632 750cfa80-cba6-4516-b367-a68698421c23<br />07/29/2009 18:32:48.75 w3wp.exe (0x15A8) 0x1640 Windows SharePoint Services 4 Monitoring nass Medium ____Current User= 750cfa80-cba6-4516-b367-a68698421c23<br />07/29/2009 18:32:48.75 w3wp.exe (0x15A8) 0x1640 Windows SharePoint Services 4 Monitoring nass Medium ____WebPart Events Offsets=1 750cfa80-cba6-4516-b367-a68698421c23<br />07/29/2009 18:32:48.75 w3wp.exe (0x15A8) 0x1640 Windows SharePoint Services 4 Monitoring nass Medium ____Page Checkout Level=Published 750cfa80-cba6-4516-b367-a68698421c23<br />07/29/2009 18:32:48.75 w3wp.exe (0x15A8) 0x1640 Windows SharePoint Services 4 Monitoring nass Medium ____Current SharePoint Operations=0 750cfa80-cba6-4516-b367-a68698421c23<br />07/29/2009 18:32:48.75 w3wp.exe (0x15A8) 0x1640 Windows SharePoint Services 4 Monitoring nass Medium ____Critical Events=0 750cfa80-cba6-4516-b367-a68698421c23<br />07/29/2009 18:32:48.75 w3wp.exe (0x15A8) 0x1640 Windows SharePoint Services 4 Monitoring nass Medium ____Working Set Delta=1.09765625 750cfa80-cba6-4516-b367-a68698421c23<br />07/29/2009 18:32:48.75 w3wp.exe (0x15A8) 0x1640 Windows SharePoint Services 4 Monitoring nass Medium ____Log Correlation Id=750cfa80-cba6-4516-b367-a68698421c23 750cfa80-cba6-4516-b367-a68698421c23<br />
    55. 55. SharePoint 2010<br />8<br />Migración de Plataforma<br />
    56. 56. SharePoint 2010<br />Learn<br />8<br />Proceso Simplificado<br />Requirements/prerequisites<br />Upgrade methods<br />Downtime mitigation<br />Common issues<br />Prepare<br />Validate<br />Migración de Plataforma<br />Document environment<br />Manage customizations<br />Plan upgrade strategy<br />Make items upgradable<br />Upgrade event failures<br />UI/UX issues<br />Data issues<br />Test<br />Implement<br />Build test farms<br />Use real data<br />Evaluate techniques<br />Find issues early<br />Build/upgrade farms<br />Deploy customizations<br />Minimize downtime<br />Monitor progress<br />Cuidado, no hace milagros<br />
    57. 57. SharePoint 2010<br />9<br />Conectividad<br />
    58. 58. SharePoint 2010<br />9<br />Conexión con datos Externos<br />Conectividad<br /><ul><li>Se tratan como si fueran listas de Sharepoint
    59. 59. Manteniendo integridad referencial (Lecturay Modificación)
    60. 60. Se pueden incluir como metadatos de los elementos actuales
    61. 61. Conexión con Bases de Datos, Web Services, otras aplicaciones
    62. 62. Podemos desarrollar nuestros propios conectores
    63. 63. Podemos crear ECT desde SharepointDesigner</li></ul>BCS<br />External Data Source<br />(Web Service, DB, .Net object, LOB system, Web 2.0 service, etc.)<br />External Content Type (ECT)<br />
    64. 64. SharePoint 2010<br />10<br />Nuevas funcionalidades<br />
    65. 65. SharePoint 2010<br />10<br />Performance Point Services<br />Nuevas funcionalidades<br /><ul><li>Plataforma de Business Intelligence integrada en Sharepoint</li></li></ul><li>SharePoint 2010<br />10<br />Office Web Applications<br />Nuevas funcionalidades<br /><ul><li>Word, Excel, OneNote & PowerPoint en versión web.
    66. 66. Compatibles con otros navegadores</li></li></ul><li>SharePoint 2010<br />TheEnd<br />
    67. 67. Migración de 2007 a 2010<br />SharePoint 2010<br />“Roadmap” de adopción<br />Jorge Ramo López<br />Jorge.ramo@raona.com<br />
    68. 68. SharePoint 2010<br />Learn<br />Requirements/prerequisites<br />Upgrade methods<br />Downtime mitigation<br />Common issues<br />Prepare<br />Validate<br />Document environment<br />Manage customizations<br />Plan upgrade strategy<br />Make items upgradable<br />Upgrade event failures<br />UI/UX issues<br />Data issues<br />Test<br />Implement<br />Build test farms<br />Use real data<br />Evaluate techniques<br />Find issues early<br />Build/upgrade farms<br />Deploy customizations<br />Minimize downtime<br />Monitor progress<br />
    69. 69. SharePoint 2010<br />Learn<br />Requirements/prerequisites<br />Upgrade methods<br />Downtime mitigation<br />Common issues<br />Prepare<br />Validate<br />Document environment<br />Manage customizations<br />Plan upgrade strategy<br />Make items upgradable<br />Upgrade event failures<br />UI/UX issues<br />Data issues<br />Test<br />Implement<br />Build test farms<br />Use real data<br />Evaluate techniques<br />Find issues early<br />Build/upgrade farms<br />Deploy customizations<br />Minimize downtime<br />Monitor progress<br />
    70. 70. LEARN<br />SharePoint 2010<br />x64<br />Dual processor<br />CPU<br />8 GB<br />Memory<br />80 GB<br />DVD Drive<br />Storage<br />
    71. 71. LEARN<br />SharePoint 2010<br />x64 edition<br />Service Pack 2 + Cumulative Update 12<br />Service Pack 3 + Cumulative Update 2<br />x64 edition<br />Standard<br />SP1 + KB970315<br />x64 Windows Server 2008 SP2 Standard<br />X64 Windows Server 2008 R2 Standard<br />SQL Server 2005<br />SQL Server 2008<br />Operating System<br />
    72. 72. LEARN<br />SharePoint 2010<br />
    73. 73. LEARN<br />SharePoint 2010<br />In-Place Pros/Cons<br />Pros<br />Cons<br />Farm wide settings are preserved and upgraded<br />Customizations are available in the environment after the upgrade<br />Servers and farms areoffline while the upgradeis in progress<br />The upgrade proceeds continuously<br />
    74. 74. LEARN<br />SharePoint 2010<br />DB Attach Pros/Cons<br />Pros<br />Cons<br />Upgrade multiple content databases at the same time <br />Combine multiple farmsinto one farm<br />The server and farm settings are not upgraded<br />Customizations must be transferred manually<br />Missing customizations<br />Time and network bandwidth <br />Direct access to thedatabase servers<br />
    75. 75. LEARN<br />SharePoint 2010<br />Supported Paths In-Placex86<br />x86<br />x64<br />x86<br />x86<br />x64<br />MSS 2010<br />x86<br />x64<br />2010<br />MOSS2007<br />SP2<br />MOSS2007<br />SP2<br />MOSS2007<br />SP2<br />MOSS2007<br />SP2<br />WSS v3.0<br />SP2<br />WSS v3.0<br />SP2<br />WSS v3.0<br />SP2<br />MSS 2010<br />
    76. 76. LEARN<br />SharePoint 2010<br />What is “Visual Upgrade”<br />A feature that separates data upgrade from UI upgrade:<br /><ul><li>Data and code upgrade happens all at once. Site UI has two modes: this version and last version
    77. 77. Pages and components make the decisionat runtime, and it’s safe by default</li></li></ul><li>SharePoint 2010<br />Learn<br />Requirements/prerequisites<br />Upgrade methods<br />Downtime mitigation<br />Common issues<br />Prepare<br />Validate<br />Document environment<br />Manage customizations<br />Plan upgrade strategy<br />Make items upgradable<br />Upgrade event failures<br />UI/UX issues<br />Data issues<br />Test<br />Implement<br />Build test farms<br />Use real data<br />Evaluate techniques<br />Find issues early<br />Build/upgrade farms<br />Deploy customizations<br />Minimize downtime<br />Monitor progress<br />
    78. 78. PREPARE<br />Pre-Upgrade Checker CommandInformational<br />All servers that are running SharePoint bits in the farm<br />Server Info<br />The components of the farm<br />Farm Info<br />The upgrade types supported by the farm<br />Upgrade Type<br />List of site definitions<br />Site Templates<br />List of features installed<br />Features<br />Language packs required<br />Language Packs<br />AAM URLs within the current environment<br />AAM URLs<br />
    79. 79. PREPARE<br />Pre-Upgrade Checker CommandErrors<br />Check for the 64-bit edition of Windows Server 2008or later installed<br />OS Type<br />Content databases are modified<br />Database Schema<br />Content DB orphans<br />Data Orphan<br />Sites can be referenced<br />Site Orphan<br />Farm is in a gradual still<br />Unfinished Gradual Upgrade<br />
    80. 80. PREPARE<br />Pre-Upgrade Checker CommandErrors<br />Web application missing web.config<br />MissingWeb Config<br />Invalid host names<br />InvalidHost Names<br />Application Pool account<br />Invalid Service Account<br />List databases that are RO in SQL-we can’t upgrade RO<br />DatabaseRead Only<br />DB >4GB<br />Site collections<br />Wyukon<br />
    81. 81. SharePoint 2010<br />Learn<br />Requirements/prerequisites<br />Upgrade methods<br />Downtime mitigation<br />Common issues<br />Prepare<br />Validate<br />Document environment<br />Manage customizations<br />Plan upgrade strategy<br />Make items upgradable<br />Upgrade event failures<br />UI/UX issues<br />Data issues<br />Test<br />Implement<br />Build test farms<br />Use real data<br />Evaluate techniques<br />Find issues early<br />Build/upgrade farms<br />Deploy customizations<br />Minimize downtime<br />Monitor progress<br />
    82. 82. TEST<br />SharePoint 2010<br />Build Test Farms<br />Use real data (copies of entire databases)<br /><ul><li>To identify trouble areas
    83. 83. To determine upgrade performance
    84. 84. Measure sequences and actions</li></ul>Use similar hardware if possible<br />Evaluate:<br /><ul><li>Content
    85. 85. Search
    86. 86. Customizations
    87. 87. …</li></li></ul><li>SharePoint 2010<br />Learn<br />Requirements/prerequisites<br />Upgrade methods<br />Downtime mitigation<br />Common issues<br />Prepare<br />Validate<br />Document environment<br />Manage customizations<br />Plan upgrade strategy<br />Make items upgradable<br />Upgrade event failures<br />UI/UX issues<br />Data issues<br />Test<br />Implement<br />Build test farms<br />Use real data<br />Evaluate techniques<br />Find issues early<br />Build/upgrade farms<br />Deploy customizations<br />Minimize downtime<br />Monitor progress<br />
    88. 88. SharePoint 2010<br />Wizards<br />Microsoft SharePoint Products and Technologies 14 Preparation Tool<br />Setup Wizard<br />SharePoint Product and Technologies Configuration Wizard<br />Server Farm Configuration Wizard<br />Implement<br />Implement<br />
    89. 89. Default Services<br />Access Services<br />Application Registry Service<br />Business Data Catalog<br />Excel Services<br />Lotus Notes Connector<br />Enables users to view, edit, and interact with Access databases in a Web browser<br />Enables users to search and collaborate around business data<br />Enables structured data from line-of-business applications, such as SAP and Siebel systems, to be integrated into SharePoint Server 2010<br />Enables users to view and interact with Microsoft Office Excel® spreadsheets in a Web browser<br />Enables users to search data on a Lotus Notes server<br />Implement<br />
    90. 90. Default Services<br />Managed Metadata Service<br />People<br />Search Service Application<br />Secure Store Service<br />State Service<br />Enables teams or departments to manage their own taxonomy, hierarchies, keywords, and social tagging infrastructure, so that, for example, taxonomies and content types can be shared across the organization<br />Enables users to search for people within their organization to, for example, find skills, memberships within enterprise communities, and shared interests<br />Enables users to index content, gather information, and perform search queries<br />Enables users to store data securely and associate it to a specific identity or group of identities<br />Enables users to temporarily store user session data for SharePoint Server 2010 components<br />Implement<br />
    91. 91. Default Services<br />Usage and Health data collection<br />Visio Graphics Service<br />Web Analytics Web Service<br />Word Conversion Service Application<br />Collects data about how users access pages in a deployment of SharePoint Server, such as the search engine used and keywords that the end user types to find a site<br />Enables users to perform automated bulk document conversions<br />Collects farm-wide usage and health data so users can view usage and health reports<br />Enables users to view and refresh published Visio diagrams<br />Implement<br />
    92. 92. SharePoint 2010<br />Learn<br />Requirements/prerequisites<br />Upgrade methods<br />Downtime mitigation<br />Common issues<br />Prepare<br />Validate<br />Document environment<br />Manage customizations<br />Plan upgrade strategy<br />Make items upgradable<br />Upgrade event failures<br />UI/UX issues<br />Data issues<br />Test<br />Implement<br />Build test farms<br />Use real data<br />Evaluate techniques<br />Find issues early<br />Build/upgrade farms<br />Deploy customizations<br />Minimize downtime<br />Monitor progress<br />
    93. 93. Validate Discussion<br />Verify High Impact/High Profile sites<br />Create a new Site Collection/Libraries and verify basic functionality<br />Application event log and upgrade log failures<br />UI/UX Issues (XHTML/XSLT/MasterPages)<br />External Data Sources<br />Security requires special attention post-upgrade:<br />Eg: migration to claims<br />Validate<br />
    94. 94. SharePoint 2010<br />“Roadmap” de adopción<br />
    95. 95. SharePoint 2010<br />TheEnd<br />

    ×