2. Agenda BPOS Overview What is BPOS Flavours of BPOS Feature Comparison Real life Experience (Gain from 9 Engagements) Indentify Management Service Customisation Migration and Bandwidth Approach and Value Add
14. Exchange Online Offering Details Current Feature Future Release Features Deskless1 Standard Dedicated Features Deskless1 Standard Dedicated Client & Mobility General Coexistence Security & Compliance Migration Extensibility Online Portal UM & Fax 3 Free/Busy and GAL is not supported on Outlook 2003 in standard or Entourage for either service 4 Only OWA Light is supported on Firefox and Safari browser 5 Standard only provide BIS support; Dedicated provide basis Blackberry support (mail, calendar, contacts, GAL) 1 Deskless available in both standard and dedicated versions 2 Can integrate with on site deployment of Rights Management Service
15. SharePoint Online Service Features – 1 of 2 Current Feature Future Release Features Deskless1 Standard Dedicated Features Deskless1 Standard Dedicated Collaboration Portal Search Content Management Forms 3 Standard does not include Blank Meeting, Decision Meeting, Social Meeting, Multipage Meeting Workspace 4 Standard does not include logging of all actions on sites, content, and workflows, audit log reporting 1 Deskless available in both standard and dedicated versions 2 Standard does not include My Site Host, News Home Template, Internet Presence Web Site
16. SharePoint Online Service Features – 2 of 2 Current Feature Future Release Features Deskless1 Standard Dedicated Business Intelligence Service Specific
18. BPOS Identity Management BPOS Dedicated Topology Active Directory is the only directory service that can be used to provision the BPOS services Customers Active Directory must be a multi forests and multi domains (there are forest and domain limits but not yet confirmed) Customer Forest must have the Microsoft Exchange Server schema extensions installed. The Customer Forest must have at least one domain controller installed with a minimum of Windows Server 2003 SP1
19. Identity remediation, integration and management Customers may have multiple directory sources. There is a need to make Active Directory the single point of truth. Remediation of Active Directory may be needed to help IT charge back the services provisioned to the business units Active Directory needs the Microsoft Exchange Server schema extensions need to be installed. Need for Identity Management as provisioning of services. 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. 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.
21. SharePoint Customisations There are different types of customisations available to you as a SharePoint Online customer: Customisations that are performed through a Web-based mechanism (for example, style sheets and Web Part pages) Customisations that are performed using HTML editors such as Microsoft Office SharePoint Designer (for example, master page changes and data view Web Parts) Customisations that require the development of .NET-based code and dependent files that must be deployed by the Microsoft Online operations team 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
22.
23. BPOS Dedicated allows flexibility to deploy services On-Premise as well as Online Head Office Flexible Deployment Choices
25. Mail Migration Considerations Velocity translates to cost Data (What, When, Who) What (Standard is 250mb per person, reviewed on a customer by customer basis) Calendar Contacts Email When Geographical or Business Function Weekend, Overnight to avoid bandwidth saturation Periodic Freeze Who All users, Business Function Users, Security Users, Compliance Storage Data left behind. What to do with what you don’t migrate
32. Migrate data and rebuild appRemediate mail dependencies Apps Retire, sunset, integrate or replace Notes applications Application Assessment Assessment Phase (Planning, Testing, Readiness) Installed Base Profile Lotus Notes Messaging Users Exchange/Outlook Users Mail Apps on Target Arch Lotus Notes Architected Applications Apps Retire, Sunset, Integrate
33. SharePoint Migration Considerations 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. 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. SharePoint Online must receive the request 11 business days prior to the change window in which the migration is expected to occur. Data must be received 3 business days prior to the scheduled deployment. 100 GB total data per migration event Regular site collections should be limited to 5GB. This limit will allow for growth up to the 10GB quota limit. 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) 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 Migrating content must be in: Same MOSS 2007 build as SharePoint Online (specific version list available upon request). Any build of SQL 2005 (plus service packs) or earlier.
36. WAN Bandwidth to support mail caching back to the client after migration 256 kbps 15360 kbps 256 kbps 2048 kbps
37. BPOS Dedicated Network Topology Mail Bandwidth per user from 1.1Kbps to 7.6Kbps (2.1kbps a good average for medium users) OCS Bandwidth per user approximately 2.15kbps for IM (10% concurrency) SharePoint Bandwidth per user approximately 13.13kbps ( 5% concurrency) LiveMeeting Bandwidth per user from 100kbps to 750Kbps Onsite LiveMeeting Traffic Offsite Traffic BPOS Services (excluding LiveMeeting) Customer WAN Firewall Onsite Traffic BPOS Services (excluding LiveMeeting) Internet Managed Zone Customer Zone Management Zone DMZ Firewall Dedicated MPLS lines
39. Provisioning Approach Overview Business Productivity Online Suite Provisioning Assessment Provision Customers Detailed Survey MAP Toolkit Assessment Proposal Assessment Survey MSO Team Partners Contract Assessment raw data Automated Discovery Tools Environment Build Out On-boarding Teams ~2 to 6 weeks ~20 to 38 weeks
40. Partner Value Add Approach Overview Communications and Collaboration Program Governance Governance MSO Assessment MSO Platform Build Service Acceptance MSO Discovery AD Remediation BPOS readiness and Mail Analysis Desktop/Client Packages MSO Service Ready SharePoint IA & Gov. BC Continuity Early Adopters Service Acceptance Business Change Business Change (Communication and Training) Service Delivery Review Coexistence and Mail Migration Service Delivery Transformation Domino Application Analysis Domino Application Migration, Retirement, Remediation and Web Enabling Assessment Phase Provision Phase Application Migration duration is defined in the Assessment Phase Contract
