6. Ieviešanas plānošana - Predeployment
Definējam sasniedzamos mērķus
Pakalpojuma izvēle atbilstoši biznesa mērķiem
Proof of concept
Izpratne par iespējamajiem migrācijas scenārijiem
Izpratne par vides gatavību un nepieciešamo resursu ieguldījumu
Reģistrācija Office 365
Izpratne par licencēšanas plāniem un izmaksām
Vienošanās par atbildības un darbu sadalījumu, ja ieviešana netiek veikta
iekšējiem resursiem
7. Ieviešanas plānošana – Plan (1)
Projekta uzsākšanas sanāksme
Komunikācijas stratēģija
Risku vadība
Interneta kanāla jaudas apzināšana
Co-existence stratēģijas izveide
Datu migrācijas stratēģijas izveide
8. Ieviešanas plānošana – Plan (2)
Veiksmes kritēriju definēšana
Identitātes vadības procedūru izmaiņas pēc migrācijas
Active Directory servera sagatavošana
Testēšanas fāzes apsvērumi
Citas lietojumprogrammas
9. Ieviešanas plānošana – Plan (3)
Izpratne par esošo infrastruktūru
Izpratne par izmantotajām mobilajām iekārtām
Apmācības un atbalsta stratēģija
Migrācijas plāna izveide
10. Ieviešanas plānošana – Prepare (1)
Nepieciešamās komunikācijas nodrošināšana
E-pasta domain pievienošana
Datu kanāla sagatavošana
Active Directory sagatavošana
Active Directory sinhronizācijas uzstādīšana
Single sign-on uzstādīšana
Co-existance realizācija
15. Kam pievērst uzmanību
Pasūtītājs un ieinteresētās puses
Projekta plāna izveide
Komunikācijas plāna izveide
Risku vadības plāna izveide
Apmācības plāna izveide (Lietotāji, atbalsts un administratori)
Kritisko soļu identifikācija (datu kanāla rezervēšana, Active Directory
sagatavošana, lietojumprogrammu izplatīšana)
Integrācija esošajā vidē
17. Active Directory sinhronizācija
On-premises Microsoft Online Services
Exchange
Server DirSync
Web Service Live ID
Exchange
Online
Active Online
DirSync
Directory Directory
SharePoint
Online
Lync
Online
18. Active Directory sinhronizācija
DirSync – rīks, kas paredzēts, lai veiktu AD objektu sinhronizāciju
starp Active Directory un Office 365 online servisiem
«Software based appliance» – nokonfigurējam un aizmirstam
Ļauj nodrošināt Single Sign-On
Ļauj izveidot coexistence scenārijus
Nodrošina GAL sinhronizāciju
Nodrošina AD objektu sinhronizāciju
Nodrošina e-pasta maršrutēšanu starp datucentru un Office 365
viena domain ietvaros
Nav paredzēts izmantošanai vienreizējai lietotāju datu augšupielādei
19. Priekšnoteikumi DirSync izmantošanai (1)
Izvietojuma un konfigurācijas prasības
Datoram uz kura atrodas DirSync ir jābūt domainā
DirSync nepieļauj instalāciju uz domain kontroliera
Nodrošināta komunikācija ar visiem domain kontrolieriem
Programmatūras prasības
Windows Installer 4.5
Windows Power Shell 2.0
.NET Framework 3.5
X64 operētājsistēma
20. Priekšnoteikumi DirSync izmantošanai (2)
Aparatūras prasības
Minimums 1GB diska vietas
Prasības atbilstoši koponentiem:
Windows Server operētājsistēma
SQL Server 2008 R2 Express Edition
Forefront Identity Manager 2010 (x64)
Number of objects in
CPU Memory Hard disk size
Active Directory
Fewer than 10,000 1.6 GHz 4 GB 70 GB
10,000–50,000 1.6 GHz 4 GB 70 GB
50,000–100,000 1.6 GHz 16 GB 100 GB
100,000–300,000 1.6 GHz 32 GB 300 GB
21. Priekšnoteikumi DirSync izmantošanai (3)
Tīkla konfigurācija
Service Protocol Port
LDAP TCP/UDP 389
Kerberos TCP/UDP 88
DNS TCP/UDP 53
Kerberos Change
TCP/UDP 464
Password
RPC TCP 135
RPC randomly
1024 - 65535
allocated high TCP TCP
49152 - 655351
ports
SMB TCP 445
SSL TCP 443
SQL TCP 1433
23. Kas ir coexistence
Situācija, kad daļa no lietotāju datiem faktiski atrodas uzņēmuma datu
centrā, bet cita daļa Microsoft datu centrā.
Veids kā nodrošināt Active Directory objektus GAL (Global Address
List) vienlaicīgi abos datu centros.
Nodrošina e-pasta pārsūtīšanu viena e-pasta ietvaros starp
uzņēmuma datucentru un Office 365
Divi scenāriji – Simple Coexistence un Hybrid coexistence
24. Simple / Hybrid co-existence
Feature Simple Hybrid
Mail routing between on-premises and cloud (recipients on either side)
Mail routing with shared namespace (if desired) on both sides
Unified GAL
Free/Busy and calendar sharing cross-premises
Out of Office
Mailtips, messaging tracking, and mailbox search work cross-premises
OWA redirection cross-premise (single URL)
Single tool to manage cross-premises Exchange functions
Mailbox moves support both onboarding and offboarding
No outlook reconfiguration or OST resync required after mailbox
migration
Preserve auth header (interal email recognition, resolve against GAL,
etc.)
Centralized mail flow , ensures that all email routes inbound/outbound
via on-premises
25. Arhitektūra
On-premises Exchange
Org
Office 365 Directory
Users, Groups, Contacts via
Synchronization Office 365
DirSync
App
Secure Mail Flow
Sharing (free/busy, MailTips,
archive, etc.)
Mailbox Data via MRS
Existing Exchange
Exchange 2013 CAS
2007 or and MBX
later
https://portal.microsoftonline.comjurz@DPALtd.onmicrosoft.comparole: s
Network RemediationUnderstand on-premises network infrastructure designUnderstand inbound/outbound internet routingUnderstand potential impact of proxy/firewall rulesInbound/outbound user authentication required?Provision temporary/permanent bandwidth increase?Identify bandwidth requirements during run-state (post-deployment)Will users have a good run-state experience?Identify bandwidth requirements for data migrationsHave enough bandwidth to migrate data quickly enough?Bring visibility early in planning phase to avoid negatively impacting overall timelineActive Directory RemediationUnderstand on-premises Active Directory infrastructure designForest/domain designDNS NamespaceUPN suffixes in useIdentify amount of AD remediation requiredDeployment Readiness ToolComplete AD remediation work prior to implementing Directory Synchronization and SSOBring visibility early in planning phase to avoid negatively impacting overall timeline
Network RemediationUnderstand on-premises network infrastructure designUnderstand inbound/outbound internet routingUnderstand potential impact of proxy/firewall rulesInbound/outbound user authentication required?Provision temporary/permanent bandwidth increase?Identify bandwidth requirements during run-state (post-deployment)Will users have a good run-state experience?Identify bandwidth requirements for data migrationsHave enough bandwidth to migrate data quickly enough?Bring visibility early in planning phase to avoid negatively impacting overall timelineActive Directory RemediationUnderstand on-premises Active Directory infrastructure designForest/domain designDNS NamespaceUPN suffixes in useIdentify amount of AD remediation requiredDeployment Readiness ToolComplete AD remediation work prior to implementing Directory Synchronization and SSOBring visibility early in planning phase to avoid negatively impacting overall timeline
Network RemediationUnderstand on-premises network infrastructure designUnderstand inbound/outbound internet routingUnderstand potential impact of proxy/firewall rulesInbound/outbound user authentication required?Provision temporary/permanent bandwidth increase?Identify bandwidth requirements during run-state (post-deployment)Will users have a good run-state experience?Identify bandwidth requirements for data migrationsHave enough bandwidth to migrate data quickly enough?Bring visibility early in planning phase to avoid negatively impacting overall timelineActive Directory RemediationUnderstand on-premises Active Directory infrastructure designForest/domain designDNS NamespaceUPN suffixes in useIdentify amount of AD remediation requiredDeployment Readiness ToolComplete AD remediation work prior to implementing Directory Synchronization and SSOBring visibility early in planning phase to avoid negatively impacting overall timeline
Network RemediationUnderstand on-premises network infrastructure designUnderstand inbound/outbound internet routingUnderstand potential impact of proxy/firewall rulesInbound/outbound user authentication required?Provision temporary/permanent bandwidth increase?Identify bandwidth requirements during run-state (post-deployment)Will users have a good run-state experience?Identify bandwidth requirements for data migrationsHave enough bandwidth to migrate data quickly enough?Bring visibility early in planning phase to avoid negatively impacting overall timelineActive Directory RemediationUnderstand on-premises Active Directory infrastructure designForest/domain designDNS NamespaceUPN suffixes in useIdentify amount of AD remediation requiredDeployment Readiness ToolComplete AD remediation work prior to implementing Directory Synchronization and SSOBring visibility early in planning phase to avoid negatively impacting overall timeline
Network RemediationUnderstand on-premises network infrastructure designUnderstand inbound/outbound internet routingUnderstand potential impact of proxy/firewall rulesInbound/outbound user authentication required?Provision temporary/permanent bandwidth increase?Identify bandwidth requirements during run-state (post-deployment)Will users have a good run-state experience?Identify bandwidth requirements for data migrationsHave enough bandwidth to migrate data quickly enough?Bring visibility early in planning phase to avoid negatively impacting overall timelineActive Directory RemediationUnderstand on-premises Active Directory infrastructure designForest/domain designDNS NamespaceUPN suffixes in useIdentify amount of AD remediation requiredDeployment Readiness ToolComplete AD remediation work prior to implementing Directory Synchronization and SSOBring visibility early in planning phase to avoid negatively impacting overall timeline
Network RemediationUnderstand on-premises network infrastructure designUnderstand inbound/outbound internet routingUnderstand potential impact of proxy/firewall rulesInbound/outbound user authentication required?Provision temporary/permanent bandwidth increase?Identify bandwidth requirements during run-state (post-deployment)Will users have a good run-state experience?Identify bandwidth requirements for data migrationsHave enough bandwidth to migrate data quickly enough?Bring visibility early in planning phase to avoid negatively impacting overall timelineActive Directory RemediationUnderstand on-premises Active Directory infrastructure designForest/domain designDNS NamespaceUPN suffixes in useIdentify amount of AD remediation requiredDeployment Readiness ToolComplete AD remediation work prior to implementing Directory Synchronization and SSOBring visibility early in planning phase to avoid negatively impacting overall timeline
Network RemediationUnderstand on-premises network infrastructure designUnderstand inbound/outbound internet routingUnderstand potential impact of proxy/firewall rulesInbound/outbound user authentication required?Provision temporary/permanent bandwidth increase?Identify bandwidth requirements during run-state (post-deployment)Will users have a good run-state experience?Identify bandwidth requirements for data migrationsHave enough bandwidth to migrate data quickly enough?Bring visibility early in planning phase to avoid negatively impacting overall timelineActive Directory RemediationUnderstand on-premises Active Directory infrastructure designForest/domain designDNS NamespaceUPN suffixes in useIdentify amount of AD remediation requiredDeployment Readiness ToolComplete AD remediation work prior to implementing Directory Synchronization and SSOBring visibility early in planning phase to avoid negatively impacting overall timeline
Network RemediationUnderstand on-premises network infrastructure designUnderstand inbound/outbound internet routingUnderstand potential impact of proxy/firewall rulesInbound/outbound user authentication required?Provision temporary/permanent bandwidth increase?Identify bandwidth requirements during run-state (post-deployment)Will users have a good run-state experience?Identify bandwidth requirements for data migrationsHave enough bandwidth to migrate data quickly enough?Bring visibility early in planning phase to avoid negatively impacting overall timelineActive Directory RemediationUnderstand on-premises Active Directory infrastructure designForest/domain designDNS NamespaceUPN suffixes in useIdentify amount of AD remediation requiredDeployment Readiness ToolComplete AD remediation work prior to implementing Directory Synchronization and SSOBring visibility early in planning phase to avoid negatively impacting overall timeline
Note that Exch 2013 hybrid no longer supports Exch 2003Customers who have Exch 2003 can still use Exch 2010 hybridExch 2010 hybrid will be able to connect to an O15 tenant once Exch 2010 SP comes out SP3 in 1st half of 2013 per this EHLO blog entry:http://blogs.technet.com/b/exchange/archive/2012/09/25/announcing-exchange-2010-service-pack-3.aspx