Transcript A B C D A B C D  Lots of choices….. Simple co-existence, Cloud IDs….

A
B
C
D
A
B
C
D
 Lots of choices….. Simple co-existence, Cloud IDs…. On-premises,
hybrid, all cloud… ADFS…. DirSync… Where to begin??












Multiple Outsourcers
Highly Complex Environment
Multinational does not equal to a large project team…
Also does not equal to a skilled team
Do you have buy in from BU’s to deploy.
Is deployment shifting to a PoC?
Does Corp IT know what’s the case on the ground, site readiness?
PF’s, Networking, Desktop’s, User Profiles?
Setup Process
Existing FOPE customer
Rename the tenant
Need a lab environment?
 Networking, AD, Messaging, ADFS, Security, Helpdesk etc.
 No Deployment Project Manager or program Manager
 No clear Executive Sponsor
 Authentication change for Outlook Clients
 New URLs, settings and capabilities
 Internal stakeholders, and disaster response teams
 Going Office 365 does not resolve a Basic / fighting fires
environment…. It can exacerbate it
 Customer Maturity to Accepting Change in the Service. i.e. Its never
seamless….
 It’s a Service versus a Product
 Re-Educate yourself and be prepared to adopt a much faster rate of
change than you may have been accustomed to
Onboarding Milestones at a Glance
Checkpoint 1
Checkpoint 3
Customer kickoff meeting
Project team defined
0
Customer Readiness
Infrastructure
Checkpoint 2
Validate
solution
alignment
License
validation
Review
customer
infrastructure
Review
Active
Directory
Weeks
1
Migration planning
Migration schedule
1
10
Service desk training
User and admin training
Communication strategy
11
Plan on-premises infrastructure
and hardware requirements
12
2
3
4
5
Plan for email coexistence
and mail-enabled apps
6
Plan network configuration and
bandwidth requirements
7
Plan client operating systems
and client applications
8
Plan user identity and
account provisioning
9
2
3
4
Production
Velocity mailbox
user
pilot
18 migrations
17
Customer readiness
continues
Service configurations
Email migration and coexistence
tested and
13
. validated
14
Migration completed
On-premises
deprovisioning
defined
Network configuration and
bandwidth updates
15
Run Office desktop setup,
deploy client updates
Verify domains, remediate Active
16 Directory and DirSync errors
7
5
6
Planning
Complete
10
8
9
10
Preparation
Complete
11
12
13 ...
Migration
Complete
 Office 365 Service Descriptions provide descriptions for the
components of the suite.
 Microsoft Office 365 Deployment Guide (MODG) is intended to
help you understand the requirements and workflows for on
boarding your organisation to Microsoft Office 365 enterprise
plans.
 The Office 365 Service Alignment Indicator (OAI) tool can also
help identify the specific areas where your business
requirements do not align with the Office 365 service offering.
 The Exchange Deployment Assistant to give a basis for ‘As Built’
type documentation
 Know what your current provisioning and deprovisioning processes are… Have they changed?
 Do users understand Office applications? Are they
getting a new version?
 How will the Admin and Service Desk role change?
What new skills do they need?
 Get posters and quick start guides out – generate
excitement
 Communications before, during and after….
 Only implement features you really need
 Clear understanding of whether Cloud IDs or Federated identities
will be deployed
 Do you need co-existence and for how long?
 Co-existence mail flow requirements clearly defined
 Clear understanding on whether Directory Synchronisation will be
deployed
 A hybrid deployment with Exchange 2010 requires two CAS servers
for load balancing and redundancy
 Single Sign On requires two or more ADFS backend and proxy
servers
 Will your trial tenant be converted into your production tenant or
thrown away?
 Carefully choose the tenant name as they will appear in Lync Invites
and SharePoint
 There are no tools to rename or migrate data from one tenant
to another
 If you have more than 50,000 objects connect Microsoft Support
before signing up for a production tenant
 Are you already using FOPE standard? Will you migrate the
namespace to Office 365?
 All proxy servers and NAT devices identified and remediated
 Access to manage internal and External DNS records
 Bandwidth upgrades implemented based on estimated network
loads
 The Microsoft Online Deployment Guide is your friend!
Adding a Domain to Office 365
External DNS Records
Third-party SSL Certificates
Ports and Protocols
Firewall Considerations
Proxy Device Considerations
WAN Accelerators
Hardware and Software Load-balancing Devices
Internet Bandwidth Planning
 All AD remediation that was identified by the Office 365 Deployment
Readiness Tool (DRT has been completed
 Do UPN’s need to be updated to externally routable namespaces?
 No [email protected]
 All duplicate attributes remediated
 ProxyAddresses
 UPNs
 Primary SMTP addresses
 Decisions made on large mailboxes – Delete / Archive / Migrate
 Mailbox migration speed tested
 Small mailboxes <100MB
 Medium mailboxes 100-500MB
 Large mailboxes 500-1.5GB or above
 As latency increases mailbox migration throughput slows
 Do you need regional MRS or Outlook Anywhere endpoints?
 Groups created for migration batches
 Geographical
 Business Unit
 Based on relationships
 Manager and PA
 Generic Helpdesk mailbox and Service Desk staff
Existing organisation
Number of mailboxes to
migrate
Do you want to maintain
mailboxes in your onpremises organisation?
Deployment option
Exchange 2010, Exchange
Less than 1,000 mailboxes No
2007 or Exchange 2003
Cutover Exchange
migration
Exchange 2007 or
Exchange 2003
No maximum
Yes
Staged Exchange
migration or hybrid
deployment
Exchange 2010
More than 1,000
mailboxes
No
Hybrid deployment
Exchange 2010
More than 1,000
mailboxes
Yes
Hybrid deployment
Office 365 for
professionals and small
businesses
Fewer than 50 *
Not applicable **
Cutover Exchange
migration
Live@edu
No maximum
Yes
Staged Exchange
migration or IMAP email
migration
Exchange 2000 Server or
previous versions
No maximum
Yes
IMAP email migration
Non-Exchange onpremises messaging
system
No maximum
Yes
IMAP email migration
 Hardware sizing based on current usage profiles and ordered
 High Availability requires
 2 x Exchange 2010 CAS/HT Servers and a load balancer
 Redundant ADFS configuration
 Third party certificates bought and ordered
 Directory Synchronisation healthy
 Trust has been established with the Microsoft Federation Gateway:
http://technet.microsoft.com/en-us/library/dd335198.aspx
 All required SMTP domains have been verified in Office 365
 Exchange Web Services have been published on premises:
http://blogs.technet.com/b/exchange/archive/2010/07/16/3410408.
aspx
 Exchange Server 2010 (SP2) license for Hybrid deployment:
http://www.microsoft.com/exchange/en-us/licensing-exchangeonline-email.aspx
 Healthy and reliable software delivery mechanism e.g. SCCM
 Mail enabled applications identified and tested
 Line of business applications tested
 Computers pre-emptively updated with Software and web browser
requirements for Office 365
 May have enlisted the help of Desktop Deployment Planning
Services (DDPS)
 Software Assurance Planning Services Provider website
 Common server-side applications include:
 Mobile device synchronization services, such as Research in
Motion BlackBerry® Enterprise Server
 Inbound/outbound Fax solutions
 Message Scanning, Hygiene solutions
 Data Leakage protection solutions
 Mail Routing extensions
 What about Multi-function devices?
 What about bulk mailing applications?