10 Reasons to Switch to SharePoint 2010
•Descargar como PPTX, PDF•
0 recomendaciones•1,548 vistas
Si tienes dudas sobre si merece la pena el esfuerzo de migrar a Sharepoint 2010, quizá esta presentación puede ayudarte.
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a 10 Reasons to Switch to SharePoint 2010
Similar a 10 Reasons to Switch to SharePoint 2010 (20)
Más de Raona
Más de Raona (20)
Último
Último (20)
10 Reasons to Switch to SharePoint 2010
- 1. 10 razones para pasarse a Sharepoint 2010 SharePoint 2010 “Roadmap” de adopción Jorge Ramo López Jorge.ramo@raona.com
- 2. SharePoint 2010 ¿Porqué Pasarme a Sharepoint 2010? … Si ya tengo Sharepoint 2007 … Si ya tengo una web en marcha … Si ya tengo un gestor de contenidos X, Y o Z … Si yahagogestión documental … Si ni siquiera sé lo que es Sharepoint
- 3. SharePoint 2010 1 Experiencia de Usuario
- 4. SharePoint 2010 Ribbon 1 Experiencia de Usuario Es contextual Análoga al paquete Office
- 5. SharePoint 2010 Interfaz Asíncrona 1 Experiencia de Usuario No hay recarga
- 6. SharePoint 2010 Integración de aplicaciones Silverlight 1 Experiencia de Usuario Sólo indicando el fichero Silverlight
- 7. SharePoint 2010 Integración de aplicaciones Office 1 Experiencia de Usuario Actualizado en tiempo real
- 8. SharePoint 2010 Cross- Browser Compatibility 1 Experiencia de Usuario Cumple con Standards Web
- 9. SharePoint 2010 Funcionalidades Sociales 1 Experiencia de Usuario Características de Red Social Corporativa
- 10. SharePoint 2010 Funcionalidades Sociales 1 Experiencia de Usuario
- 11. SharePoint 2010 2 Gestión de Documentación
- 13. El rendimiento del servidor se adapta al volumen de documentación asociado
- 14. Podemos publicar tipos de contenido entre los diferentes apartados de un portal
- 15. Podemos gestionar los metadatos de forma centralizada a través de taxonomías
- 17. SharePoint 2010 3 Búsqueda
- 19. Búsqueda social teniendo en cuenta las actividades, publicaciones, notas, metadatos, tags de nuestros usuarios
- 21. Mayor escalabilidad en la definición de los componentesQuery Servers Index Partition Indexer Crawler Content Content Content Es más fácil «buscar» y «encontrar»
- 22. SharePoint 2010 3 Búsqueda Resultados de ejemplo de búsqueda Win7 Connector Related searches Launch in Office Web Apps Refinement panel Federated results
- 23. SharePoint 2010 Content search 3 Se incorpora FAST como producto FAST Search for SharePoint Búsqueda Enterprise Crawler JDBC FAST Query Language (FQL) OM extensions Web Part extensions People search SharePoint Server
- 24. SharePoint 2010 4 Arquitectura de Servicios
- 26. Ahora cada servicio se provee por sí mismo.
- 27. Muchos más servicios (Office Services) y posibilidad de crear nuevos.
- 28. Podemos elegir qué partes de nuestro Sharepoint son accesibles a quién
- 30. Más escalable,
- 31. Más flexible
- 32. Aprovecha mejor las máquina dedicadas a Sharepoint
- 33. Mejora la seguridad de acceso
- 35. SharePoint 2010 5 Aislamiento
- 37. Los Datos
- 38. El uso de las aplicaciones
- 41. Las operaciones
- 43. Intranet
- 44. Extranet
- 45. Webs
- 47. SharePoint 2010 6 Desarrollo Ágil
- 48. SharePoint 2010 Aumentar Capacidades de cada perfil 6 Desarrollo Ágil Visual Studio Dev SharePoint Designer InfoPath RAD Application Complexity PIW SharePoint Browser UI IWs Technical Difficulty
- 50. Un paquete es compatible entre SPD y Visual Studio
- 52. SharePoint 2010 7 Alta Disponibilidad
- 53. SharePoint 2010 7 Proceso controlado de Patching Alta Disponibilidad
- 54. SharePoint 2010 7 Sistema unificado Monitorización Alta Disponibilidad 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)) 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 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 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 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 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 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 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 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 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 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 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 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 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 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
- 55. SharePoint 2010 8 Migración de Plataforma
- 56. SharePoint 2010 Learn 8 Proceso Simplificado Requirements/prerequisites Upgrade methods Downtime mitigation Common issues Prepare Validate Migración de Plataforma Document environment Manage customizations Plan upgrade strategy Make items upgradable Upgrade event failures UI/UX issues Data issues Test Implement Build test farms Use real data Evaluate techniques Find issues early Build/upgrade farms Deploy customizations Minimize downtime Monitor progress Cuidado, no hace milagros
- 57. SharePoint 2010 9 Conectividad
- 59. Manteniendo integridad referencial (Lecturay Modificación)
- 60. Se pueden incluir como metadatos de los elementos actuales
- 61. Conexión con Bases de Datos, Web Services, otras aplicaciones
- 62. Podemos desarrollar nuestros propios conectores
- 63. Podemos crear ECT desde SharepointDesignerBCS External Data Source (Web Service, DB, .Net object, LOB system, Web 2.0 service, etc.) External Content Type (ECT)
- 64. SharePoint 2010 10 Nuevas funcionalidades
- 67. Migración de 2007 a 2010 SharePoint 2010 “Roadmap” de adopción Jorge Ramo López Jorge.ramo@raona.com
- 68. SharePoint 2010 Learn Requirements/prerequisites Upgrade methods Downtime mitigation Common issues Prepare Validate Document environment Manage customizations Plan upgrade strategy Make items upgradable Upgrade event failures UI/UX issues Data issues Test Implement Build test farms Use real data Evaluate techniques Find issues early Build/upgrade farms Deploy customizations Minimize downtime Monitor progress
- 69. SharePoint 2010 Learn Requirements/prerequisites Upgrade methods Downtime mitigation Common issues Prepare Validate Document environment Manage customizations Plan upgrade strategy Make items upgradable Upgrade event failures UI/UX issues Data issues Test Implement Build test farms Use real data Evaluate techniques Find issues early Build/upgrade farms Deploy customizations Minimize downtime Monitor progress
- 70. LEARN SharePoint 2010 x64 Dual processor CPU 8 GB Memory 80 GB DVD Drive Storage
- 71. LEARN SharePoint 2010 x64 edition Service Pack 2 + Cumulative Update 12 Service Pack 3 + Cumulative Update 2 x64 edition Standard SP1 + KB970315 x64 Windows Server 2008 SP2 Standard X64 Windows Server 2008 R2 Standard SQL Server 2005 SQL Server 2008 Operating System
- 73. LEARN SharePoint 2010 In-Place Pros/Cons Pros Cons Farm wide settings are preserved and upgraded Customizations are available in the environment after the upgrade Servers and farms areoffline while the upgradeis in progress The upgrade proceeds continuously
- 74. LEARN SharePoint 2010 DB Attach Pros/Cons Pros Cons Upgrade multiple content databases at the same time Combine multiple farmsinto one farm The server and farm settings are not upgraded Customizations must be transferred manually Missing customizations Time and network bandwidth Direct access to thedatabase servers
- 75. LEARN SharePoint 2010 Supported Paths In-Placex86 x86 x64 x86 x86 x64 MSS 2010 x86 x64 2010 MOSS2007 SP2 MOSS2007 SP2 MOSS2007 SP2 MOSS2007 SP2 WSS v3.0 SP2 WSS v3.0 SP2 WSS v3.0 SP2 MSS 2010
- 78. PREPARE Pre-Upgrade Checker CommandInformational All servers that are running SharePoint bits in the farm Server Info The components of the farm Farm Info The upgrade types supported by the farm Upgrade Type List of site definitions Site Templates List of features installed Features Language packs required Language Packs AAM URLs within the current environment AAM URLs
- 79. PREPARE Pre-Upgrade Checker CommandErrors Check for the 64-bit edition of Windows Server 2008or later installed OS Type Content databases are modified Database Schema Content DB orphans Data Orphan Sites can be referenced Site Orphan Farm is in a gradual still Unfinished Gradual Upgrade
- 80. PREPARE Pre-Upgrade Checker CommandErrors Web application missing web.config MissingWeb Config Invalid host names InvalidHost Names Application Pool account Invalid Service Account List databases that are RO in SQL-we can’t upgrade RO DatabaseRead Only DB >4GB Site collections Wyukon
- 81. SharePoint 2010 Learn Requirements/prerequisites Upgrade methods Downtime mitigation Common issues Prepare Validate Document environment Manage customizations Plan upgrade strategy Make items upgradable Upgrade event failures UI/UX issues Data issues Test Implement Build test farms Use real data Evaluate techniques Find issues early Build/upgrade farms Deploy customizations Minimize downtime Monitor progress
- 83. To determine upgrade performance
- 85. Search
- 86. Customizations
- 88. SharePoint 2010 Wizards Microsoft SharePoint Products and Technologies 14 Preparation Tool Setup Wizard SharePoint Product and Technologies Configuration Wizard Server Farm Configuration Wizard Implement Implement
- 89. Default Services Access Services Application Registry Service Business Data Catalog Excel Services Lotus Notes Connector Enables users to view, edit, and interact with Access databases in a Web browser Enables users to search and collaborate around business data Enables structured data from line-of-business applications, such as SAP and Siebel systems, to be integrated into SharePoint Server 2010 Enables users to view and interact with Microsoft Office Excel® spreadsheets in a Web browser Enables users to search data on a Lotus Notes server Implement
- 90. Default Services Managed Metadata Service People Search Service Application Secure Store Service State Service 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 Enables users to search for people within their organization to, for example, find skills, memberships within enterprise communities, and shared interests Enables users to index content, gather information, and perform search queries Enables users to store data securely and associate it to a specific identity or group of identities Enables users to temporarily store user session data for SharePoint Server 2010 components Implement
- 91. Default Services Usage and Health data collection Visio Graphics Service Web Analytics Web Service Word Conversion Service Application 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 Enables users to perform automated bulk document conversions Collects farm-wide usage and health data so users can view usage and health reports Enables users to view and refresh published Visio diagrams Implement
- 92. SharePoint 2010 Learn Requirements/prerequisites Upgrade methods Downtime mitigation Common issues Prepare Validate Document environment Manage customizations Plan upgrade strategy Make items upgradable Upgrade event failures UI/UX issues Data issues Test Implement Build test farms Use real data Evaluate techniques Find issues early Build/upgrade farms Deploy customizations Minimize downtime Monitor progress
- 93. Validate Discussion Verify High Impact/High Profile sites Create a new Site Collection/Libraries and verify basic functionality Application event log and upgrade log failures UI/UX Issues (XHTML/XSLT/MasterPages) External Data Sources Security requires special attention post-upgrade: Eg: migration to claims Validate
- 94. SharePoint 2010 “Roadmap” de adopción
Notas del editor
- 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.