O documento fornece diretrizes para implantação do SharePoint, discutindo armadilhas comuns e melhores práticas. Apresenta um guia para arquitetura do SharePoint, incluindo modelos de hospedagem, ciclo de vida e serviços de aplicativos. Recomenda testes e manter soluções simples para evitar falhas.
2. CÓDIGO DA SESSÃO: ##### Guide to SharePoint Deployment Failures Joel Oleson Sr. SharePoint Architect Quest Software http://www.sharepointjoel.com @joeloleson
3. Who is SharePoint Joel? 10 Years of SharePoint SharePoint Architect, Evangelist & Strategy @ Quest Software Twitter: @joeloleson Email: joel.oleson@quest.com
4. We Don’t Know Why We are Doing SharePoint but someone asked for it, so we do it! Não sei por que estamos fazendo SharePoint, mas alguém perguntou por ele, entao fizemos!
6. Live by the K.I.S.S. PrincipleKeep it Simple Stupid!Mantenha-o EstupidamenteSimples!
7. Our .NET Developers can work in SharePoint without training or experience Nosso. NET desenvolvedores podem trabalhar em SharePoint sem formação ou experiência
8. Two Very Different Models for Hosting Easy to Move to Cloud On Premise – High Business Value
9. Let me optimize the SharePoint Databases Deixe-me melhorar os bancos de dados do SharePoint
10. We don’t need a test environment. It costs too much! Nós não precisamos de um ambiente de teste. Custa muito!
12. Um site collection pode conter tudo One Site Collection Can Fit Everything
13. Permanent Central Portal Enterprise Search Enterprise Browse Corporate Business Taxonomy With Divisional Stakeholders Central Portal Permanent Division Portals Business Process Division News, Scorecards Group Reporting Semi Structured Group, Team, Project Sites and Workspaces Ad Hoc Self Service w/ Life Cycle Management Per User Blogs, bios, Social The SharePoint Pyramid
14. SharePoint works good enough for all our data, so we’re dumping our File Shares. SharePoint trabalha bem com todos os nossos dados, por isso estamos movendo nosso servidor de arquivos para ele.
15. SharePoint’s Social Features will waste people’s Time Social do SharePoint Features vai gastar o tempo das pessoas
17. Forced to Be the One ManBand Forçado a ser o One Man Band
18.
19. Why do we need sandbox solutions when we can create server solutions that are so much easier? Porqueprecisamos de solucoes “sandboxed” quandopodemosdesenvolver solutions “Farm” quesaomuitomais simples.
20. I’ll turn it all on and see what happens… Vouligartudo e ver o queacontece…
28. READY v2.2 in early May introduces 2003-2010 Direct Migrations
29. Just Released to the Web SharePoint 2010: Best Practices for Upgrading and Migrating Get Prescriptive guidance on Upgrade Methods Drill deep into assessment tools Compare Migration tools Save yourself time
31. Learn More about SharePoint 2010 Information forIT Prosat TechNet http://MSSharePointITPro.com Information forDevelopersat MSDN http://MSSharePointDeveloper.com Information forEveryone http://SharePoint.Microsoft.com
These service models provide a starting point to understand the cost implications involved with the solution types that you may want to implement.I want to host team collaboration sites and also my public facing web site on SharePoint.Team sites (Commodity)Public Web Site (Application)Exec Sponsor Governance Plan: Clear Goals, Vision, Mission and MetricsSkilled Team(s)TrainingService Definition & Service ModelEasy to search find and discover: Information ArchitectureStandards and Policies(ITIL/MOF) Change, Configuration and Release Management ProcessesCulture and AdoptionK.I.S.S.