Valkuilen en successen binnen een implementatie van Office 365, SharePoint, Exchange en Lync Online in de Cloud. 4000 seats binnen Zorg - Health. Intramurele en extramurele medewerkers hebben samen een digitale werkomgeving. Het Nieuwe Werken voor een thuiszorginstelling.

2. Rik Dekker
Cas van Iersel
Pitfalls and Success Factors of an
Office 365 Implementation

3. Agenda
• Our Office 365 experience
– Project
– Approach
– Deployment
• The development challenges
– OOTB quick wins
– Sandbox troubles
– Power of the Client

4. What is Office 365?
Online Versions of Microsoft Software
in the Cloud

5. Licenses
• Office 365 for professionals and small
businesses (Plan P)
• Office 365 for midsize businesses and
enterprises
– Kiosk worker (Plan K family)
– Information worker (Plan E family)

7. The project
• Large Office 365 implementation
– 4500 users (of which 3000 kiosk users)
– Social intranet
Personal landingspage Aggregated news Aggregated discussions
My colleagues per Workflows Forms
department
Collaboration portal Personalised actions Last changed /
important documents
Respond Support mobile devices View documents in
browser

8. Why Office 365 for this project?
• Different type of users
– Single Sign On with AD sync
• High availability
• No extra IT staffing needed
• Good cost overview
• Secure

9. Biggest succes factor
• Microsoft takes care of IT
– Updates
• Hotfixes, Service Packs
– Upgrades
• New functionality like BCS
– Scaling
• Extra capacity

10. The approach
• Agile (7 sprints)
– Product backlog
Per sprint
– Stayed as close as possible to OOTB
• Configuration
• Styling
– If required then custom development

11. The team
• Product owner
• Project manager customer
• Developer
– NL and India
• Designer
• Architect/team lead
• Project manager

12. Tools
• Visual Studio
– Powerfull tool for developers
– Only sandboxed solutions for Office365
Development takes more time
• SharePoint Designer
– Rapid development
– Reusable workflows required for our project

13. DTAP environment
• Local development machine
• Test in the cloud
• Acceptance/Production in the cloud
Risk for early adoptors (beta products)
Sandbox solutions makes deployment easy
Office365 environment is quickly available

14. Deployment
• Same deliverables as ‘normal’ SP project
– Web parts
– Page layouts
– Master pages
– WSP’s
– Documentation

15. Deployment challenges
• How to deploy the site structure?
Normal way of deployment not possible:
• No PowerShell
• No console apps
• No content database copy

16. Deployment solution
Options:
• Site templates
• Migration tools
– Different tools available
 Tool together with Web templates
Deployment more difficult

17. Lessons learned
• Some 3d party tools not usable
• Rapid development with the right tools
• Limitations of Sandbox asks for more
creativity
• Use web templates for deployment
• Environment quickly available
• New functionality added to Office365

18. Summary
With Office365 you can create powerfull
solutions like on premise. You just need
some more creativity

19. The development
challenges

20. Development
First challenge: Aggregation
(How may SiteCollections do I need?)

21. DEMO: How to extend the CQWP to fit your
needs

22. Aggregation
• OOTB aggregation
• Easy to configure
• Easy to brand

23. Aggregation
What to do with aggregation over multiple
Site Collections?

24. DEMO: Configure Search to fetch cross-
sitecollection data

25. Aggregation
Another cool way of getting data!

26. DEMO: Configure CQWP + RSS to fetch
cross-sitecollection data

27. Sandboxed Solution
About Sandboxed Solutions..
Farm
Webapplication
Site Collection
Site

28. Sandboxed Solution
(#seats × 200) + 300

29. Sandboxed Solution
AbnormalProcessTerminationCount
CPUExecutionTime
CriticalExceptionCount
InvocationCount
PercentProcessorTime
ProcessCPUCycles
ProcessHandleCount
ProcessIOBytes
ProcessThreadCount
ProcessVirtualBytes
SharePointDatabaseQueryCount
SharePointDatabaseQueryTime
UnhandledExceptionCount
UnresponsiveProcessCount

30. Sandboxed Solution
• Deployment
• Limited but Powerful
• Resource Points System
• SiteCollection context only

31. Client Object Model
Finding the Balance with COM
(Client Object Model)

32. DEMO: Sandboxed WebPart with CSOM

33. Client Object Model
About COM …

34. Client Object Model
No Resource Points
Possibilities same as sandboxed
• More code
• Tools less mature then VS

35. DEMO: All put together, real world SP
Online example

36. Summary
With Office365 you can create powerfull
solutions like on premise. You just need
some more creativity!

37. Questions?
Resources
• http://msdn.microsoft.com/en-us/library/gg615462.aspx
• http://community.office365.com/en-us/f/145/t/8959.aspx
• @rikdekker
• @casvaniersel
• rik.dekker@rapidcircle.com
• cas.van.iersel@rapidcircle.com
Visit our booth!