Zarafa SummerCamp 2012 - Project approach when migrating to Zarafa


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

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

No notes for slide
  • - wie bij betrokken - impact - wat moet er aangepast worden - hoe terug te schakelen - hoe te evaulerern - wat zijn de andere dingen
  • Zarafa SummerCamp 2012 - Project approach when migrating to Zarafa

    1. 1. Project approach when migratingExchange to ZarafaMilo Oostergo (
    2. 2. Phases Deployment Migration PoC IT department organisation
    3. 3. Question at Proof of ConceptWhats the impact?Who are involved in the Poc?How do we evaluate? Can i still use existing functionality? What is different?How can we migrate the data back from the PoC?
    4. 4. Zarafa in an easy Proof of Concept setupZarafa on a virtual machineZarafa coupled to local ADS to have Global Addressbook with all existing users/groupsAll outgoing emails from Zarafa are relayed to the existing Exchange serverIncoming emails are forwarded from existing environment to dummy address <username>
    5. 5. Possibilities Zarafa in Proof of ConceptEmails between Exchange and ZarafaMeeting requests between Exchange and ZarafaWebAccess, WebApp and mobile synchronisationWith new Freebusy synchronisation tool, calendar availablity data can be used between the two systems
    6. 6. Impossibilities Zarafa in Proof of ConceptShared folders and public folders can be accessed between the 2 systemsSynchronous replication between Exchange and Zarafa for its mailbox data
    7. 7. From Proof of Concept to productionScaling of PoC virtual machine to productionFurther deployment of infrastructure (firewall, antispam, SMTP, 3rd party apps)Setup of migration and deployment planTesting of plan for IT departmentProduction usage for IT departmentFinetuning of environment after feedback of IT department
    8. 8. From Proof of Concept to production (2)Communication to end users via intranet or email about changes in new environment. Training of power users.Migration of all dataMigration of most recent data and deployment of Zarafa client + including new OL profilesRecoupling of mobile devicesSupport and help of users after migration
    9. 9. Usage of Zarafa migration toolMigrationtool is migrating folders, emails, contacts, tasks, calendars en notesMigrationtool converts Exchange addresses to Zarafa adressesPermissions, rules and settings are not migratedMigrationtool can run on several machines for higher throughput
    10. 10. Zarafa ADS integrationThe following objects can be managed from ADS Users & contacts Security & distribution groups Adresslists Group policies Quotas E-Mailadresses & Aliases Send-As permissions Administrator users Resources
    11. 11. ConclusionTraining of end users is under estimated during migrations, but is key factor for a successful migrationClear communication about changes in the solutionMake very clear migration and deployment guide and test it upfront!Train helpdesk and administrators upfront, to solve questions and issues faster