Bpos Architectural Consideration Architectural Forum


Published on

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Customer diagramsADExchangeNetworkDNSAssessment questionnairesIdentity Assessment and Detailed DiscoveryNetwork Traffic Estimation SpreadsheetMessaging Assessment and Detailed DiscoveryOffice Communications AssessmentLive Meeting AssessmentSharePoint AssessmentDiscovery ToolsMAPS (Messaging beta only)Active Directory MAPExchange MAPDNSLINTExchange RAPActive Directory RAP
  • Bpos Architectural Consideration Architectural Forum

    1. 1. Microsoft BPOSArchitectural Considerations<br />Andrew D Jones<br />Microsoft Practice Solution Director<br />ajones201@csc.com<br />
    2. 2. Agenda<br />BPOS Overview<br />What is BPOS<br />Flavours of BPOS<br />Feature Comparison<br />Real life Experience (Gain from 9 Engagements)<br />Indentify Management<br />Service Customisation<br />Migration and Bandwidth<br />Approach and Value Add<br />
    3. 3. What is BPOS?<br /><ul><li>BPOS is the Microsoft’s Business Productivity Online Suite comprising of:
    4. 4. Exchange Online
    5. 5. SharePoint Online
    6. 6. Office Communications Online
    7. 7. Office Live Meeting</li></ul>Enterprise software delivered via internet subscription services from Microsoft datacentres, deployed with partners.<br />
    8. 8. BPOS Flavours<br /><ul><li>BPOS is available in two flavours, Standard or Dedicated.</li></ul>Dedicated<br />Standard (aka Shared)<br /><ul><li>Single customer per deployment
    9. 9. Customer needs most server features
    10. 10. Optimized for 20,000+
    11. 11. Multiple customers, one architecture
    12. 12. Customer needs rapid deployment
    13. 13. Cost efficiency a key focus </li></li></ul><li>BPOS Standard (aka Shared) or Dedicated?<br />
    14. 14. Exchange Online Offering Details<br /> Current Feature<br />Future Release<br />Features<br />Deskless1<br />Standard<br />Dedicated<br />Features<br />Deskless1<br />Standard<br />Dedicated<br />Client & Mobility<br />General<br />Coexistence<br />Security & Compliance<br />Migration<br />Extensibility<br />Online Portal<br />UM & Fax<br />3 Free/Busy and GAL is not supported on Outlook 2003 in standard or Entourage for either service<br />4 Only OWA Light is supported on Firefox and Safari browser<br />5 Standard only provide BIS support; Dedicated provide basis Blackberry support (mail, calendar, contacts, GAL)<br />1 Deskless available in both standard and dedicated versions<br />2 Can integrate with on site deployment of Rights Management Service<br />
    15. 15. SharePoint Online Service Features – 1 of 2<br /> Current Feature<br />Future Release<br />Features<br />Deskless1<br />Standard<br />Dedicated<br />Features<br />Deskless1<br />Standard<br />Dedicated<br />Collaboration<br />Portal<br />Search<br />Content Management <br />Forms<br />3 Standard does not include Blank Meeting, Decision Meeting, Social Meeting, Multipage Meeting Workspace<br />4 Standard does not include logging of all actions on sites, content, and workflows, audit log reporting<br />1 Deskless available in both standard and dedicated versions<br />2 Standard does not include My Site Host, News Home Template, Internet Presence Web Site<br />
    16. 16. SharePoint Online Service Features – 2 of 2<br /> Current Feature<br />Future Release<br />Features<br />Deskless1<br />Standard<br />Dedicated<br />Business Intelligence<br />Service Specific<br />
    17. 17. Identity Management<br />
    18. 18. BPOS Identity Management <br />BPOS Dedicated Topology<br />Active Directory is the only directory service that can be used to provision the BPOS services<br />Customers Active Directory must be a multi forests and multi domains (there are forest and domain limits but not yet confirmed)<br />Customer Forest must have the Microsoft Exchange Server schema extensions installed.<br />The Customer Forest must have at least one domain controller installed with a minimum of Windows Server 2003 SP1<br />
    19. 19. Identity remediation, integration and management<br />Customers may have multiple directory sources. There is a need to make Active Directory the single point of truth.<br />Remediation of Active Directory may be needed to help IT charge back the services provisioned to the business units <br />Active Directory needs the Microsoft Exchange Server schema extensions need to be installed.<br />Need for Identity Management as provisioning of services. <br />Microsoft Identity Lifecycle Management provides an integrated, comprehensive product that offers identity synchronisation, certificate management, and user provisioning in one solution that works across the Windows Platform.<br />Migration from another email platform, Lotus Notes for example, would need to make sure there is a common identifier between the Lotus Notes Directory and Active Directory to allow for the automation of mail migration.<br />
    20. 20. Service customisation<br />
    21. 21. SharePoint Customisations<br />There are different types of customisations available to you as a SharePoint Online customer:<br />Customisations that are performed through a Web-based mechanism (for example, style sheets and Web Part pages)<br />Customisations that are performed using HTML editors such as Microsoft Office SharePoint Designer (for example, master page changes and data view Web Parts)<br />Customisations that require the development of .NET-based code and dependent files that must be deployed by the Microsoft Online operations team<br />Third-party solutions and products are available from both developers and vendors for installation in the Microsoft Online environment. Microsoft has evaluated only a limited number of third-party solutions at this time<br />
    22. 22. Branch Office<br /><ul><li>BPOS Dedicated gives IT the flexibility to choose Online deployment by geography, workload or roles
    23. 23. BPOS Dedicated allows flexibility to deploy services On-Premise as well as Online </li></ul>Head<br />Office<br />Flexible Deployment Choices<br />
    24. 24. Migration and bandwidth<br />
    25. 25. Mail Migration Considerations<br />Velocity translates to cost<br />Data (What, When, Who)<br />What (Standard is 250mb per person, reviewed on a customer by customer basis)<br />Calendar <br />Contacts<br />Email<br />When<br />Geographical or Business Function<br />Weekend, Overnight to avoid bandwidth saturation<br />Periodic Freeze<br />Who<br />All users, Business Function Users, Security Users, Compliance<br />Storage<br />Data left behind. What to do with what you don’t migrate<br />
    26. 26. Messaging migration complete<br />Application migration complete<br />Announce transition plan<br />Begin building new applications on Microsoft platform<br />Lotus Notes Migration Considerations<br /><ul><li>Messaging and application migration typically handled as separate and distinct work efforts
    27. 27. Normally they overlap and do not happen all at once
    28. 28. Majority do messaging first and applications second
    29. 29. By starting application migration work early, in parallel with messaging efforts, migration window is maximized
    30. 30. For most customers, the application migration is handled within the context of broader application effort (move to off-the-shelf applications / reduction in custom applications)</li></ul>Typical Notes Application Environment*<br />30% simple/moderate migration<br />Delivery Phase<br />60% retire/archive<br />10%relatively complex<br />Mail Environment Build<br />Mail Migration<br />Mail<br /> Determine approach for complex apps (10% of total)<br /><ul><li>Web enable to eliminate Notes client dependency
    31. 31. Integrate through Web Services/XML
    32. 32. Migrate data and rebuild app</li></ul>Remediate mail dependencies<br />Apps<br />Retire, sunset, integrate or replace Notes applications<br />Application Assessment<br />Assessment Phase<br />(Planning, Testing, Readiness)<br />Installed Base Profile<br />Lotus Notes Messaging Users<br />Exchange/Outlook Users<br />Mail<br />Apps on Target Arch<br />Lotus Notes Architected Applications<br />Apps<br />Retire, Sunset, Integrate<br />
    33. 33. SharePoint Migration Considerations<br />Currently the only way to migrate SharePoint content to the online service is by transferring one or more SharePoint content databases to the SharePoint Online hosted environment. <br />To provide your SharePoint Online base environment as quickly as possible, customers’ pre-existing (on-premises) content will be migrated only after Service Acceptance is declared and relevant customisations are approved by SharePoint Online. <br />SharePoint Online must receive the request 11 business days prior to the change window in which the migration is expected to occur. <br />Data must be received 3 business days prior to the scheduled deployment.<br />100 GB total data per migration event <br />Regular site collections should be limited to 5GB. This limit will allow for growth up to the 10GB quota limit.<br />No single site collection over 80GB (reminder that we have a limit of 10 site collections on the farm with 100GB quota, to be isolated into its own content DB. 80GB limit allows for further site growth)<br />Maximum of 1 content DB under 20 GB per migration event. Multiple content DBs of a smaller size should be consolidated into a single DB using the mergecontentdbs command<br />Migrating content must be in:<br />Same MOSS 2007 build as SharePoint Online (specific version list available upon request).<br />Any build of SQL 2005 (plus service packs) or earlier. <br />
    34. 34. Bandwidth Considerations <br /><ul><li>Bandwidth to support new services
    35. 35. Bandwidth to support coexistence between the existing Mail Platform and BPOS
    36. 36. WAN Bandwidth to support mail caching back to the client after migration </li></ul>256 kbps<br />15360 kbps<br />256 kbps<br />2048 kbps<br />
    37. 37. BPOS Dedicated Network Topology<br />Mail Bandwidth per user from 1.1Kbps to 7.6Kbps (2.1kbps a good average for medium users)<br />OCS Bandwidth per user approximately 2.15kbps for IM (10% concurrency) <br />SharePoint Bandwidth per user approximately 13.13kbps ( 5% concurrency) <br />LiveMeeting Bandwidth per user from 100kbps to 750Kbps<br />Onsite LiveMeeting Traffic<br />Offsite Traffic <br />BPOS Services<br />(excluding LiveMeeting)<br />Customer<br />WAN<br />Firewall<br />Onsite Traffic <br />BPOS Services<br />(excluding LiveMeeting)<br />Internet<br />Managed<br />Zone<br />Customer<br />Zone<br />Management<br />Zone<br />DMZ<br />Firewall<br />Dedicated MPLS lines<br />
    38. 38. Approach<br />
    39. 39. Provisioning Approach Overview<br />Business Productivity Online Suite Provisioning<br />Assessment <br />Provision<br />Customers<br />Detailed<br />Survey<br />MAP Toolkit<br />Assessment Proposal<br />Assessment Survey<br />MSO Team<br />Partners<br />Contract<br />Assessment raw data<br />Automated Discovery<br />Tools<br />Environment Build Out<br />On-boarding Teams<br />~2 to 6 weeks<br />~20 to 38 weeks<br />
    40. 40. Partner Value Add Approach Overview<br />Communications and Collaboration Program<br />Governance<br />Governance<br />MSO Assessment<br />MSO Platform Build<br />Service Acceptance<br />MSO Discovery<br />AD Remediation<br />BPOS readiness and Mail Analysis<br />Desktop/Client Packages<br />MSO Service Ready<br />SharePoint IA & Gov.<br />BC Continuity<br />Early Adopters<br />Service Acceptance<br />Business Change<br />Business Change (Communication and Training)<br />Service Delivery Review<br />Coexistence and Mail Migration<br />Service Delivery Transformation<br />Domino <br />Application Analysis <br />Domino Application Migration, Retirement, Remediation and Web Enabling<br />Assessment Phase<br />Provision Phase<br />Application Migration duration is defined in the Assessment Phase<br />Contract<br />
    41. 41. Questions<br />