Raona - Migracion a SharePoint 2010

Notas del editor

• #3:   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 Management Document 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 application Better Performance & Boundaries: To explain… (Web Server throttling,..)   Isolation Tenants: 2 Sharepoint domains (customers, departments, areas,…) can now have data, customizations and processes completely isolated and share the farm and central administration Sandbox Solutions: Isolated applications to avoid a farm crash if the applications trhoughs an exception.   Fast Development Sharepoint  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 Packages Visual Studio now is completely integrated with Sharepoint development Cycle.   Availability Upgrading: 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 2010 2007 and 2010 are .NET platform Based, we have more tools now to do faster migrations and with more successful probability.   Connectivity From BDC (Business Data Catalog in 2007) to BCS (Business Connectivity Services in 2010). Read /Write for External databases, entities and applications.   New Services Access Services: Move your access application from desktop to web with only a little bit effort. Performance Point Services: Powerful Business Intelligence tools Office Web Applications Share, 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 interface Language 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.
• #4:   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 Management Document 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 application Better Performance & Boundaries: To explain… (Web Server throttling,..)   Isolation Tenants: 2 Sharepoint domains (customers, departments, areas,…) can now have data, customizations and processes completely isolated and share the farm and central administration Sandbox Solutions: Isolated applications to avoid a farm crash if the applications trhoughs an exception.   Fast Development Sharepoint  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 Packages Visual Studio now is completely integrated with Sharepoint development Cycle.   Availability Upgrading: 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 2010 2007 and 2010 are .NET platform Based, we have more tools now to do faster migrations and with more successful probability.   Connectivity From BDC (Business Data Catalog in 2007) to BCS (Business Connectivity Services in 2010). Read /Write for External databases, entities and applications.   New Services Access Services: Move your access application from desktop to web with only a little bit effort. Performance Point Services: Powerful Business Intelligence tools Office Web Applications Share, 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 interface Language 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.
• #5: En una migración, de este tipo, es necesario 5 pasos y no nos podemos saltar. Una migración no se hace una semana, es complicada, pero es necesaria!!! Lo que si es cierto, que una migración de 2003 a 2007 no es lo mismo que desde 2007 a 2010, porque simplemente: - la plataforma es .net Y tenemos nuevos wizards Y tenemos las experiencias de otras migraciones 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 Management Document 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 application Better Performance & Boundaries: To explain… (Web Server throttling,..)   Isolation Tenants: 2 Sharepoint domains (customers, departments, areas,…) can now have data, customizations and processes completely isolated and share the farm and central administration Sandbox Solutions: Isolated applications to avoid a farm crash if the applications trhoughs an exception.   Fast Development Sharepoint  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 Packages Visual Studio now is completely integrated with Sharepoint development Cycle.   Availability Upgrading: 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 2010 2007 and 2010 are .NET platform Based, we have more tools now to do faster migrations and with more successful probability.   Connectivity From BDC (Business Data Catalog in 2007) to BCS (Business Connectivity Services in 2010). Read /Write for External databases, entities and applications.   New Services Access Services: Move your access application from desktop to web with only a little bit effort. Performance Point Services: Powerful Business Intelligence tools Office Web Applications Share, 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 interface Language 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.
• #6: En el paso de Aprendizaje debemos asegurarnos que cumplimos los prerrequisitos de SharePoint 2010 (Windows Server 2008 ó 2008-R2, sólo 64 bits, SQL Server 2008, memoria RAM…). También debemos ´pensar qué método de actualización elegimos (instalación encima, asociación de base de datos o migración WID to SQL). Además, debemos ir planificcando cómo hacer que SharePoint esté apagado el tiempo mínimo e ir identificando problemas que vamos a tener con UI, espacio en disco, etc.   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 Management Document 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 application Better Performance & Boundaries: To explain… (Web Server throttling,..)   Isolation Tenants: 2 Sharepoint domains (customers, departments, areas,…) can now have data, customizations and processes completely isolated and share the farm and central administration Sandbox Solutions: Isolated applications to avoid a farm crash if the applications trhoughs an exception.   Fast Development Sharepoint  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 Packages Visual Studio now is completely integrated with Sharepoint development Cycle.   Availability Upgrading: 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 2010 2007 and 2010 are .NET platform Based, we have more tools now to do faster migrations and with more successful probability.   Connectivity From BDC (Business Data Catalog in 2007) to BCS (Business Connectivity Services in 2010). Read /Write for External databases, entities and applications.   New Services Access Services: Move your access application from desktop to web with only a little bit effort. Performance Point Services: Powerful Business Intelligence tools Office Web Applications Share, 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 interface Language 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.
• #7: Lo primero que tenemos que saber es: No vale el mismo entorno de MOSS2007 generalmente, ¿quién tiene su entorno en X64 y con 8GB Ram?
• #8: El software también cambia!
• #9: In Place: en el mismo servidor, como si instalo Windows 7 sobre Windows Vista Database Attach: Copia de BD, y posteriormente creo una nueva web application y le asocio la base de datos de contenido. En este caso, tienes que llevarte la carpeta 12, los assembly. Ahora el directorio es el 14 (no han puesto 13, porque nunca utilizan el 13, por supestición…) Una web application crea una base de datos de contenido In-Place: Pros: La configuración de la granja se mantiene y se actualiza Las personalizaciones están disponibles en el entorno después de la actualización (quién ha instalado todos sus desarrollos con WSP, no ha tocado código en sus plantillas con Designer,…) Contras: La granja se desconecta mientras se actualiza y se queda sin servicio, a no ser que tengamos un entorno de alta disponibilidad. Evidentemente, a no ser que hagamos una copia del entorno, si se «jode» la actualización, nos cargamos el entorno. Los procesos continúan, no paran. No tenemos control de la situación. DB Attach: Pros: Actualizas multiple contenido de base de datos al mismo tiempo Combinas varias granjas en una única granja Cons: Las configuraciones del servidor no están actualizadas Las personalizaciones tienen que ser transferidas manualmente (in-place tb te ocurrirá lo mismo) Se pierden personalizaciones Acceso directo a las BD Attach, porque in-Place te quedas sin servidor si no funciona Customizaciones con paquetes de despliegue (si lo tienes en WSP todo genial, porque lo pasa a 2010) - STP File: Plantilla de sitio
• #10: Pros: La configuración de la granja se mantiene y se actualiza Las personalizaciones están disponibles en el entorno después de la actualización (quién ha instalado todos sus desarrollos con WSP, no ha tocado código en sus plantillas con Designer,…) Contras: La granja se desconecta mientras se actualiza y se queda sin servicio, a no ser que tengamos un entorno de alta disponibilidad. Evidentemente, a no ser que hagamos una copia del entorno, si se «jode» la actualización, nos cargamos el entorno. Los procesos continúan, no paran. No tenemos control de la situación.
• #11: Pros: Actualizas multiple contenido de base de datos al mismo tiempo Combinas varias granjas en una única granja Cons: Las configuraciones del servidor no están actualizadas Las personalizaciones tienen que ser transferidas manualmente (in-place tb te ocurrirá lo mismo) Se pierden personalizaciones Acceso directo a las BD Attach, porque in-Place te quedas sin servidor si no funciona Customizaciones con paquetes de despliegue (si lo tienes en WSP todo genial, porque lo pasa a 2010) - STP File: Plantilla de sitio
• #12: Durante la fase de Preparación debemos encargarnos de documentar todo el entorno (estructura de la granja, language packs y componentes instalados) y empezar a identificar y a juntar en un mismo lugar las personalizaciones para tenerlas todas a mano. En este paso es muy importante preparar la estrategia de actualización. En esta estrategia planearemos el orden de actualización de la granja, el orden de las distintas operaciones a realizar, la reducción al mínimo del tiempo con SharePoint apagado, actualizaciones de hardware, requisitos de espacio y un plan de vuelta atrás. También debemos preparar nuestras soluciones, características y webparts para que sean actualizables.   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 Management Document 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 application Better Performance & Boundaries: To explain… (Web Server throttling,..)   Isolation Tenants: 2 Sharepoint domains (customers, departments, areas,…) can now have data, customizations and processes completely isolated and share the farm and central administration Sandbox Solutions: Isolated applications to avoid a farm crash if the applications trhoughs an exception.   Fast Development Sharepoint  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 Packages Visual Studio now is completely integrated with Sharepoint development Cycle.   Availability Upgrading: 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 2010 2007 and 2010 are .NET platform Based, we have more tools now to do faster migrations and with more successful probability.   Connectivity From BDC (Business Data Catalog in 2007) to BCS (Business Connectivity Services in 2010). Read /Write for External databases, entities and applications.   New Services Access Services: Move your access application from desktop to web with only a little bit effort. Performance Point Services: Powerful Business Intelligence tools Office Web Applications Share, 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 interface Language 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.
• #13: Linea de comandos de todo lo que hay Reports farm and server data Identifies useful farm information Servers, databases, AAM Site definitions, features, language packs SearchContentSourceInfo A list of the content sources and start addresses for each shared service provider in the farm. SearchInfo A 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
• #15: Tipos de error 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
• #16: Refactory
• #17:   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 Management Document 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 application Better Performance & Boundaries: To explain… (Web Server throttling,..)   Isolation Tenants: 2 Sharepoint domains (customers, departments, areas,…) can now have data, customizations and processes completely isolated and share the farm and central administration Sandbox Solutions: Isolated applications to avoid a farm crash if the applications trhoughs an exception.   Fast Development Sharepoint  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 Packages Visual Studio now is completely integrated with Sharepoint development Cycle.   Availability Upgrading: 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 2010 2007 and 2010 are .NET platform Based, we have more tools now to do faster migrations and with more successful probability.   Connectivity From BDC (Business Data Catalog in 2007) to BCS (Business Connectivity Services in 2010). Read /Write for External databases, entities and applications.   New Services Access Services: Move your access application from desktop to web with only a little bit effort. Performance Point Services: Powerful Business Intelligence tools Office Web Applications Share, 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 interface Language 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.
• #18: En el paso de Test tenemos que construir granjas de pruebas que usen datos reales (copias completas de las bases de datos) y, en la medida de lo posible, el mismo hardware. En estas granjas probaremos las técnicas de actualización pensadas en el paso anterior para poder depurarlas y hacerlas mucho más afectivas. Gracias a estas pruebas, conseguiremos encontrar diferentes problemas y estaremos a tiempo de mitigarlos. Este paso puede repetirse todas las veces que sea necesario hasta que se consiga reducir al mínimo el tiempo en el que SharePoint estará apagado. Muy recomendado. Hacer una granja de prueba Una UAT (User Acces Test)
• #19: "Access Denied" to the My Site Host This is often a misconfiguration, not a bug This means that the My Site Host you're visiting is not the default My Site Host for the User Profile Application that is associated with the web app you're on... check that you Service Associations are correct, then check that the My Site Host is correctly referenced in your User Profile Service Application admin area, then iisreset... Going directly to your My Site redirects to "personalsite/_layouts/viewlsts.aspx" This means that this site collection is not yet associated with you as your My Site.  This is often the case if the Content database was upgraded, but the SSP was not (remember, that's not supported).  To get the User Profile Application to understand that this page is your My Site, you have to go to the root of the My Site Host (http://webappURL/mysitehostURL/).  This will kick off the My Site creation process... if you hooked up your User Profile Application properly, it will try to create a site at the URL of your existing private site, realize it's a private site and then make the correct associations so that in the future your upgraded personal site is understood to be your official personal site
• #22: Y por fin llegamos a la fase de Implementación. En esta fase crearemos o actualizaremos (según sea nuestro plan) las granjas, migraremos las bases de datos de contenido y haremos el deploy de las personalizaciones. Debemos ir monitorizando el proceso para asegurarnos que estamos cumpliendo los tiempos planificados y que SharePoint no está apagado más de la cuenta a los usuarios. Si aparecen complicaciones, errores o vamos muy mal de tiempo puede ser necesario iniciar nuestro plan de vuelta atrás.   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 Management Document 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 application Better Performance & Boundaries: To explain… (Web Server throttling,..)   Isolation Tenants: 2 Sharepoint domains (customers, departments, areas,…) can now have data, customizations and processes completely isolated and share the farm and central administration Sandbox Solutions: Isolated applications to avoid a farm crash if the applications trhoughs an exception.   Fast Development Sharepoint  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 Packages Visual Studio now is completely integrated with Sharepoint development Cycle.   Availability Upgrading: 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 2010 2007 and 2010 are .NET platform Based, we have more tools now to do faster migrations and with more successful probability.   Connectivity From BDC (Business Data Catalog in 2007) to BCS (Business Connectivity Services in 2010). Read /Write for External databases, entities and applications.   New Services Access Services: Move your access application from desktop to web with only a little bit effort. Performance Point Services: Powerful Business Intelligence tools Office Web Applications Share, 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 interface Language 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.
• #23: SP2010, 3 wizard de siempre. Prerrequisitos Instalación Configuración Configura los servicios de la granja
• #24: By default the Default Content Access Account is the Farm Account --- need to change this. Customizations: Copy new site definitions into site templates Install upgrade definition file Copy CSS and images Web parts Web services Install features Install solutions (hopefully you have these) Web.config changes (eg: security) Assemblies and references Add the Content Databases to the Web Applications Create Web application(s) Remove content database Begin attaching content databases Root site for Web application must be included in the first content database stsadm -o addcontentdb -url <URL> -databasename <database name> Repeat for each content database Multiple databases at once with multiple instances Pay close attention to SQL performance More Configuration Web.config settings – application settings Trusted paths Managed paths Farm level permissions BDC setup SSP Upgrade: Create a new, blank Web application Start People service and the Managed Metadata service Create a new Metadata service Create a new application pool New People service Proxy needed Associate the new proxy with the default proxy group My Site: Database attach into empty Web application People service you want to associate with the My Sites Setup My Sites My Site host is in your content database Check or set inclusions
• #25:  En la fase de Validación debemos asegurarnos que todo funciona correctamente. Debemos revisar los log y la Administración Central. También tendremos que repasar todas las personalizaciones de interfaz de usuario para asegurarnos que todo funciona correctamente. Recordemos que las CSS de SharePoint cambian totalmente y que el código es ahora XHTML. También debemos revisar posibles problemas con los datos migrados. 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 Management Document 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 application Better Performance & Boundaries: To explain… (Web Server throttling,..)   Isolation Tenants: 2 Sharepoint domains (customers, departments, areas,…) can now have data, customizations and processes completely isolated and share the farm and central administration Sandbox Solutions: Isolated applications to avoid a farm crash if the applications trhoughs an exception.   Fast Development Sharepoint  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 Packages Visual Studio now is completely integrated with Sharepoint development Cycle.   Availability Upgrading: 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 2010 2007 and 2010 are .NET platform Based, we have more tools now to do faster migrations and with more successful probability.   Connectivity From BDC (Business Data Catalog in 2007) to BCS (Business Connectivity Services in 2010). Read /Write for External databases, entities and applications.   New Services Access Services: Move your access application from desktop to web with only a little bit effort. Performance Point Services: Powerful Business Intelligence tools Office Web Applications Share, 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 interface Language 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.
• #26: No preguntas No customizado Estándar mejor Desarrollos, revisarlos Silverlight de puta madre Web Services y Modelo de objetos, se mantiene, pero refactory, cambiar las llamadas a objetos. (A lo mejor en un futuro, no funciona) Lo mejor: El proceso esta mas controlado, hay log Puedes unificar granjas Parching, ahora es controlado, puedes elegir cuando actualizar Upgrade checking  Mucho más fácil, 2003 es una plataforma commplus, y ahora es de .net a .net.
• #27: No preguntas No customizado Estándar mejor Desarrollos, revisarlos Silverlight de puta madre Web Services y Modelo de objetos, se mantiene, pero refactory, cambiar las llamadas a objetos. (A lo mejor en un futuro, no funciona) Lo mejor: El proceso esta mas controlado, hay log Puedes unificar granjas Parching, ahora es controlado, puedes elegir cuando actualizar Upgrade checking  Mucho más fácil, 2003 es una plataforma commplus, y ahora es de .net a .net.
• #28: No preguntas No customizado Estándar mejor Desarrollos, revisarlos Silverlight de puta madre Web Services y Modelo de objetos, se mantiene, pero refactory, cambiar las llamadas a objetos. (A lo mejor en un futuro, no funciona) Lo mejor: El proceso esta mas controlado, hay log Puedes unificar granjas Parching, ahora es controlado, puedes elegir cuando actualizar Upgrade checking  Mucho más fácil, 2003 es una plataforma commplus, y ahora es de .net a .net.
• #29: No preguntas No customizado Estándar mejor Desarrollos, revisarlos Silverlight de puta madre Web Services y Modelo de objetos, se mantiene, pero refactory, cambiar las llamadas a objetos. (A lo mejor en un futuro, no funciona) Lo mejor: El proceso esta mas controlado, hay log Puedes unificar granjas Parching, ahora es controlado, puedes elegir cuando actualizar Upgrade checking  Mucho más fácil, 2003 es una plataforma commplus, y ahora es de .net a .net.