Migration vers Lync 2013 et Lync online

1 882 vues

Publié le

Que vous soyez sur OCS 2007 en fin de support ou de Lync 2010, cette session présentera les bonnes pratiques de migration d'un existant vers Lync 2013 on premise, online ou hybride, l'une des évolutions de la version Lync 2013. Préparation des environnements, migration des utilisateurs et des infrastructures, conduites du changement, vous connaitrez tous les secrets pour réussir votre migration.

Publié dans : Technologie
0 commentaire
0 j’aime
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

Aucun téléchargement
Nombre de vues
1 882
Sur SlideShare
Issues des intégrations
Intégrations 0
Aucune incorporation

Aucune remarque pour cette diapositive
  • Serveur Lync 2013 (plus de version Standard ou enterprise)
  • Persistant chat intégrésur le serveur Lync
  • Slide Objective: Provide an overview of the phased items specific to a Lync 2010 to Lync 2013 Preview migration, as compared to the previous slide. This is a very high-level outline.Notes: When migrating from Lync Server 2010, the process is more streamlined. Lync 2010 already utilizes the CMS and Lync 2013 Preview will simply use the existing CMS instance. The CMS can be moved to a Lync 2013 Preview instance. Typically, this would be at the end of the migration from Lync 2010 to Lync 2013 Preview.Users are migrated using either Lync Control Panel or PowerShell (Move-CsUser).
  • Slide Objective: Provide an overview of the different cmdlets by phase that will be involved for co-existent and migration to a Lync Server 2013 Preview environmentNotes: So, just to summarize, for topologies, we ran the Merge Wizard from topology builder which synced up the Server entries for both OCS 2007 R2 and Lync Server 2013 Preview environments. The wizard will also import all conferencing directories. If you want to run these steps from Lync Management Shell you have to use the following commands: Merge-CsLegacyTopology to import the topology and Import-CsLegacyConferenceDirectory to import conferencing directories. Rerun these steps whenever you change your Legacy topology.If you have applications from other third-party vendors or if you developed applications within your environment using UCMA, the merge will also move those customer Server entries for those applications so that they can talk between OCS 2007 R2 and Lync Server 2013 Preview Servers. So one of the other things to consider is if you have applications from another third-party vendor, is to reach out to those vendors prior to migration and investigate their plans with how their going to address integration with Lync Server 2013 Preview during the coexistence period. For configuration, we ran the following command:Import-CSLegacyConfiguration – to import/move the configurationIt is important to know that the Move-CsLegacyUser cmdlet relies on information imported by Import-CsLegacyConfiguration. That means that, when running Move-CsLegacyUser, you might receive an error message telling you that you must run Import-CsLegacyConfiguration before proceeding. If that happens you must re-run Import-CsLegacyConfiguration before you will be able to move the Legacy user. The parameter ReplaceExisting instructs Import-CsLegacyConfiguration to overwrite any previously imported policies or settings that have changed since the last time the cmdlet was run.For users, we’ve got the following:Users can be moved with Lync Server Control Panel. If you want to use Lync Management Shell – recommended if you move large number of users – the following cmdlets can be used.Move-CSLegacyuser – which will be the preferred command for moving users from OCS 2007R2 Pools to Lync Server 2013 Preview PoolsMove-CSUser – will be used to move users from a Lync Server 2013 Preview Pool back to an OCS 2007R2 Pool. Again, there will be some data loss, which is to be expected as it is not a perfect scenario, but it is a way of recovering if something happens on the Lync Server 2013 Preview Pool that your end users do not expect.There are also other “move” cmdlets:Move-CSApplicationEndpoint – this will be the cmdlet that your vendors will run if they need to move the application endpoints themselves, being the contact objects stored in Active Directory. The cmdlet is also used, when moving dial in conferencing numbers from OCS 2007 R2 to Lync.Move-CSRgsConfiguration – this is the cmdlet that will move the Response Groups from your OCS 2007 R2 environment to a Lync Server 2013 Preview Pool and we’ve got a slide later that we’ll talk about that walks through that process further, as well as what Response Group Service (RGS) interoperability capabilities will be available to you.Move-CsExUmContact – this moves your Exchange UM contact objects – the subscriber access and the auto attendant – from OCS 2007 R2 to LyncMove-CsConferenceDirectory – this will move the conference directory from OCS 2007 R2 completely to Lync and needs to be done before decommissioning your OCS 2007 R2 Pool. If you fail to move the directory before decommissioning your Pool, dial-in conferences created on the old Pool will not work anymore. If the directory is moved while you have still active users on your OCS 2007 R2 Pool, a new conferencing directory will be created on the OCS 2007 R2 Pool.
  • Migration Cote à cotePhase piloteValider les bonsfct, prod
  • Topo : Prendre Topology builder 2013, importer la topo 2010, faire modif et importer
  • Lync 2010 : Users via la console Lync ouCommandepowershell
  • Edge : Ne pas active la Federation ni XMPP
  • Validation Remote Acces Lync 2013, configuration manuelle des clients tests vers le Edge (pas de federation)
  • Lync 2010 Legacy Move-CsUserOCS 2007 R2 Legacy Move-CsLegacyUsers
  • Intro Serveurs / Entreprise / Reseaux / IT
  • Slide Objective: Discuss all available scenarios with Lync Server 2010 in Office 365 GA releaseNotesYou should be sure to review this slide in presentation mode to be familiar with how it builds.As seen bePoure, there are two deployment models available in office 365 GA with Lync:Pure cloud: this is a scenario geared towards new customers. Existing customers can also move to the Office 365 Pour Exchange Online et Lync Online, however, not all Lync features are available in the Office 365 GA offering: Pour instance, telephony features are not available. It does mean that companies that deployed Lync Enterprise Voice cannot move to Lync Online in the Office 365 release because of the non-availability of Enterprise Voice feature.The other available scenario is here to give companies the opportunity to use some Office 365 cloud services, such as Exchange Online et SharePoint Online while keeping their existing Lync Server 2010 on-premises infrastructure. In such a scenario, companies can take the benefits of using Exchange Online et continue to use their on-premises Lync 2010 infrastructure that is already providing Enterprise Voice features.It is important to note that in an Interoperability scenario as defined in this slide, presence et voicemail integration is possible between Exchange Online et Lync Server on-premises. Actually, it does mean that:Presence in Outlook Web App in Office 365 works: this is technically possible through Fédération between Office 365 et Lync Server on-premises deployment (via Edge server)User mailboxes in Exchange Online can be enabled Pour voicemail feature: Exchange Online UM servers will record the caller’s voice message et sent it to the recipient as a regular voicemail message
  • Slide Objective: Discuss scenarios between on-premises et cloud deployments of Lync Server 2010NotesIn the previous slide, we have seen that it is possible to use either Lync Online with Exchange Online or Lync Server 2010 on-premises with Exchange Online. Now, let’s take a look on what’s possible between Lync Online et Lync Server on-premises deployments.In order to do IM/P between users online et users on-premise you essentially have two separate Lync orgs that are federated together.In Office 365 GA, there is no Split-Domain support Pour SIP domains: it does mean that in order to have some users homed on Lync Online et other users homed on Lync Server 2010 on-premises deployments, it is not possible Pour all of them to have the same SIP domain. Communications between Lync Online et Lync Server 2010 on-premises deployments is done through Lync Fédération et the current status Pour Fédération is that it is not possible to federate with the same SIP domain that is defined as a SIP domain Pour the on-premises company.In other words, it is currently a requirement to have separate SIP domains in case a company wants to have some users homed on Lync Online et other users homed on Lync Server 2010 on-premises deployments.With this kind of architecture, users can see presence et communicate together even if they are on separate Lync deployments, thanks to Lync Fédération. However, as explained bePoure, two separate domains Pour on-premises et Online deployments are required. Also, Lync Annuaire search is not supported over Fédération, which means that Online users will not be able to search Pour users homed on the Lync Server on-premises deployment et vice-versa.
  • Slide Objective: Discuss integration scenarios betweenLync, Exchange, et SharePointNotesNo matter what the combination is between on-premises et Online deployments, Lync client presence integration always works. It is possible because this kind of integration is done at the client level et not between Lync et Exchange servers.Another thing to highlight is that when using a Lync Server on-premises deployment, users get the same features no matter if Exchange Online or Exchange on-premises is used. As mentioned earlier, IM/P in OWA et voicemail integration when using Lync Server on-premises with Exchange Online is possible thanks to Lync Federation between Office 365 et Lync Server 2010 on-premises.Also, note that no voicemail integration is possible between Lync Online et Exchange Online because Lync Online does not provide Enterprise Voice feature.When looking at the integration matrix between Lync et SharePoint, it is possible to see that in every case Lync client presence integration works: it is possible because integration is done at the client level et not between Lync et SharePoint servers.Note that Skill search in Lync client is only available when using a combination of Lync Server on-premises et SharePoint Server on-premises.
  • Slide Objective: Present Lync 2013 Preview Hybrid migrationNotesHere is some background on each of the various rows in this table.Rows 1 & 2Migration et Online coexistence work only with versions starting from OCS 2007 R2Row 3Migration with OCS R2 requires you to move the user to Lync 2013 as we won’t support tri-existence with online (ie. You can’t have OCS R2 et Lync 2010 on premise with Lync 2013 online)An alternative solution could be to complete a full on premise migration to Lync 2010, removing OCS R2 et then configure Coexistence with the online service.Co-existence with the online service will require the administrator to deploy a Lync 2013 edge et next hopRow 4Migration from Lync 2010 doesn’t require any additional configuration Pour IM/P however the user et administrator will need to make some configuration changes Pour Conferencing et VoiceRow 5Migration from Lync 2013 doesn’t require any additional configuration Pour IM/P however the user et administrator will need to make some configuration changes Pour Conferencing et VoiceMigration operation does not keep all data. Pour instance, scheduled conferences must be recreated after the user has been migrated from on-premises to Online et vice-versa.
  • Slide Objective: Discuss Hybrid deployment requirementsNotesAs Pour any typical deployment providing rich experience with Office 365, there components are required et are actually common with Exchange:DirSync: used to synchronize on-premises Active Annuaire with Office 365 in order to maintain a consistent address list et avoid the administrator to have to create user accounts in Office 365AD FS: used to enable single sign-on (SSO) on Office 365 services Pour company users. It does allow users to authenticate with their Active Annuaire credentials instead of having to remember new et different credentials Pour their account in the cloud.In order to have the on-premises et online deployment that communicate, a Lync 2010 Fédération Edge is required. You can use a Lync Server 2010 or Lync Server 2013 Preview Edge Server.In order to migrate users between on-premises et online deployments, Lync 2013 Management Shell must be used. Also, if the customer does want to use Hybrid Voice, a Lync 2013 Preview pool must be deployed on-premises.
  • Slide Objective: Explain Hybrid CoexistenceNotesAs said earlier, there are 2 prerequisites Pour Hybrid deployment to work: Deploy DirSync to have user provisioning et GAL managed in the cloud based on the admin operations perPourmed on-premises (user creation, modification, removal…)Deploy AD FS to enable users to use their corporate credentials Pour accessing cloud servicesOn this diagram where we says Lync 2010+ pool this could be 2010 (with appropriate Cus) or 2013.Fédération must use a Lync 2010+ Fédération Edge which must route traffic to a Lync 2010+ pool. If the company is only using OCS 2007 R2, they will have to deploy Lync 2010 or Lync 2013 Preview to be able to federate with Office 365 in case the company wants to deploy a Hybrid scenario or wants to migrate existing on-premises users to the cloud.When looking at this type of architecture, it is important to keep in mind that redundancy is important. Edge as well as the next-hop pool must be redundant to ensure that flow between on-premises et online deployments will not get stopped in case of a single-server failure.
  • Slide Objective: Explain Cross-premise migration approachNotesMigration to Lync 2013 Preview online is possible for company that are running OCS 2007 R2 or later. There are some prerequisites to meet in order to perform a successful migration:- From OCS 2007 R2: a Lync 2013 Preview infrastructure must be deployed on-premises to enable migration to user to the cloud- From Lync Server 2010: it is not necessary to deploy Lync 2013 Preview server on-premises to enable migration of users to the cloud, except if Hybrid Voice is required: in this case, Lync Server 2013 Preview must be deployed on-premisesFrom Lync Server 2013 Preview: there is no other requirement to meet.Regarding the migration strategy, it is important to note that companies running OCS 2007 R2 will have to migrate user accounts to Lync 2013 Preview pool and deploy the Lync 2013 Preview client to users before the user account is migrated to the cloud. This is required because Office Communicator 2007 R2 cannot connect to the Lync Online infrastructure.Note that in all cases, no matter the on-premises version users are migrated from, it is always required to rescheduled meeting.
  • Slide Objective: Checklist for Split DomainNotesThis slide describes the required steps for deploying a Split Domain infrastructure:Deploy DirSync on the company premises: at this time, the server is prepared but the DirSync Configuration wizard is set to not runGet a Lync 2013 Preview tenant in Office 365Add the SIP domains to the list of approved domains in Office 365Enable Directory Synchronization for the tenant: this will allow DirSync to synchronize data from corporate Active Directory to Office 365Deploy and configure AD FS: AD FS and AD FS Proxy servers must be deployed. Also, certificates with correct entries must be deployed on these servers as well as DNS entries.
  • Slide Objective: Explain how to configure Edge server for HybridNotesIn order to allow Split Domain and migration of users from on-premises deployment to the cloud deployment, it is required to configure the Edge server to allow federation. In addition to that, a new Hosting Provider must be declared. Note that there are two particular parameters:EnableSharedAddressSpace:indicates that the hosting provider is being used in a split domain scenarioHostsOCSUsers: indicates that the hosting provider is used to host Lync Server accountsMoving a user to the cloud is straightforward: instead of running Move-CsUser <Identity> -Target <OnPremisePool>, the Hosting Provider is specified as the target for the move operation with the credentials that have admin rights on the Office 365 tenant.
  • Slide Objective: Compare IM/P featuresNotesThe key points of this slide is that Office 365 2013 Preview release (last column) does provide most of features that a Lync 2010+ on-premises infrastructure does. IM archiving can be done thanks to Exchange Server 2013 Preview. However, persistent chat is not planned for this release in Office 365.Note: Slide should be reviewed before presentation to ensure accuracy.
  • Slide Objective: Compare IM/P featuresNotesThe key points of this slide is that Office 365 2013 Preview release (last column) does provide most of features that a Lync 2010+ on-premises infrastructure does. IM archiving can be done thanks to Exchange Server 2013 Preview. However, persistent chat is not planned for this release in Office 365.Note: Slide should be reviewed before presentation to ensure accuracy.
  • Slide Objective: Compare Conferencing featuresNotesSlide should be reviewed before presentation to ensure accuracy.
  • Slide Objective: Compare Voice featuresNotesThere are two types of Voice for Office 365: Lync Lync to Phoneand Lync Hybrid Voice. We will not go into great detail or comparison of them. However, note that:Lync Online Hybrid Voice does require Lync 2013 Preview infrastructure deployed on-premises in order to enable telephony interoperability via Mediation Server. Most of the capabilities of an on-premises Lync deployment are available.Lync Online Hosted Voice does not required Lync 2013 Preview infrastructure deployed on-premises. As a result, less capabilities are available than in a Hybrid Voice deployment.Note: Slide should be reviewed before presentation to ensure accuracy. Note: Lync to phone is no longer being covered as a separate module so you should review the Lync to Phone module so that you understand it and explain it here.
  • Migration vers Lync 2013 et Lync online

    1. 1. 8 pays sont certifiés GOLD260 certifications (dont plus de 50 surl’UC)AustriaBelgiumCzech Rep.FranceGermanyHungaryItalyPolandPortugalSlovakiaSpainUKGoldRegisteredRegisteredGoldGoldRegisteredGoldGoldGoldRegisteredGoldGoldUne forte expertise sur l’UC :Engagé dans le programme UC Microsoft depuis 2007Des offres de services adaptées : Certifiés PSLP
    2. 2. En…. 25 Minutes !CompatibilitésMigrationClients LyncCOL203 Migration vers Lync 2013
    3. 3. N (15) : Lync 2013N-1 (14) : Lync 2010*N-2 (13) : Office Communications Serveur (OCS) 2007 R2Client N-1 (Lync 2010) avec Lync Serveur 2013Client N-2 (Communicator 2007 R2) avec Lync Serveur 2013Le client Lync 2013 est supporté par le Serveur Lync 20104
    4. 4. N-1 (14) : Lync 2010 Group ChatN-2 (13) : Office Communications Serveur (OCS) 2007 R2 Group ChatClient Chat N-1 (Lync 2010) avec Lync 2013 Persistent Chat ServeurClient Chat N-2 (Communicator 2007 R2) avec Lync 2013 Persistent Chat ServeurLe client Lync 2013 n’est pas compatible avec les serveurs Group Chat5
    5. 5. Pas de déplacement du rôle d’archivage et de surveillanceRôles Archivage et de surveillance intégré dans Lync Serveur 2013Possibilité de coexistence6
    6. 6. Pool LyncServeur deMédiationLync Serveur 2013 15 15 SupportéLync Serveur 2013 - Lync Serveur201015 14 Supporté14 15 SupportéLync Serveur 2013 - OCS 2007 R215 13 Supporté13 15 Non SupportéServeur deMédiationNext Hop Serveur Pool LyncLync Serveur 2013 15 15 15 SupportéLync Serveur 2013 - Lync Serveur201015 15 14 Supporté14 14 15 SupportéLync Serveur 2013 - OCS 2007 R215 15 13 Supporté13 13 15 SupportéAppel SortantsAppels EntrantsPool Lync 2010 Pool Lync 2013Lync 2010 SBA Supporté SupportéLync 2013 SBA Non Supporté SupportéSurvivable Branch Appliance (SBA)7
    7. 7. Download la topologie dans le Lync Topology BuilderCréer le nouveau Pool Lync 2013 et publier la nouvelle topologieNe pas utiliser le Lync 2010 topology builderVia Lync Server Control PanelDepuis des commandes powershell : Move-CsLegacyUser8
    8. 8. Topology BuilderImporter la topologie et dossiers de conférenceRerun when Legacy topology changesPublier la nouvelle topologieMigrer d’autres configurations via les commandesPowershell:Import-CsLegacyConfigurationVia Lync Server Control PanelDepuis des commandes powershell :Move-CsLegacyUserApplications: Move-CsApplicationEndpointResponse Group: Move-CsRgsConfigurationContacts Exchange UMMove-CsExUmContactConferencing : Move-CsConferenceDirectory9
    9. 9. Etape 1PréparationFaire tous les updates (Clients/Server)Best Practices AnalyserSauvegardesChoisir des utilisateurs de testFaire updatesFaire updatesFaire updatesFEUpgrade du schemaProductionDirectorADFederationRemote AccessEdge11
    10. 10. Etape 2Installer le premier PoolLync Serveur 2013Topology Builder Lync 201312Remote Access FederationDirectorEdgeFEADFEBEBEProduction Pilote
    11. 11. Etape 3RoutingRoutage des 2 pools via le DirectorAccès Extérieurs via L’Egde Serveur13Remote Access FederationDirectorEdgeFEADFEBEBEProduction Pilote
    12. 12. Etape 4Utilisateurs de testMigration des utilisateurs test vers le pool Lync 2013Déploiement des clients test Lync 2013Validation des fonctionnalités et du bonfonctionnement14Remote Access FederationDirectorEdgeFEADFEBEBEProduction Pilote
    13. 13. Etape 5Création des Serveurs EdgeDéployer Les serveurs Edge Lync 2013 en parallèlesur le site piloteEn Option, déployer le rôle Director de Lync 201315Remote Access FederationDirectorEdgeFEADFEBEBEProduction PiloteDirectorRemote AccessEdge
    14. 14. Etape 6Validation des routesConfigurer les utilisateurs de test via le Edge Lync2013Garder la fédération via l’ancien serveur EdgeVérification des différents scénarios16Remote Access FederationDirectorEdgeFEADFEBEBEProduction PiloteRemote AccessDirectorEdge
    15. 15. Etape 7Passage en production17Remote AccessFederationDirectorEdgeFEADFEBEBEProductionDirectorRemote AccessEdgeProductionMigration de tous les utilisateurs
    16. 16. Etape 8Valider le serveur EdgeLync 2013 pour laproductionCréer la fédération et le XMPP via le Edge Lync 2013Configurer tous les utilisateurs en remote acces via leEdge Lync 2013Désactivation de l’ancien Serveur Edge,Lancer le Wizard pour supprimer l’anciennetopologie18FEServeur Lync 2013ProductionDirector Lync 2013ADFederationRemote AccessEdge Lync 2013
    17. 17. 20
    18. 18. FeatureClient IM Presence Voice Video App Sharing* File Transfer**Lync 2013 Preview Rich Client X X X X X XLync 2013 Preview Web App N/A – conference only until 15.1 which will support sign inLync 2013 Preview Mobile X XLync 2013 Preview Phone Edition X X XLync 2010 Rich Client X X X X X XLync 2010 Web App N/A – conference onlyLync 2010 Attendee N/A – conference onlyLync 2010 Attendant X X XLync 2010 Mobile X XLync 2010 Phone Edition X X XOffice Communicator 2007 R2 Rich Client X X X X X XPublic IM Connectivity (PIC) (AOL, Yahoo) X XPIC (Messenger) X X X X21
    19. 19. 22
    20. 20. 23
    21. 21. • Société de conseil et d’expertises technologiques.• Spécialiste à forte valeur ajoutée• Recrutement Stand 40 sur Techdays• Communication Unifiée : Déploiement et gestion desolutions de communication unifiées pour la mise en placede communications intuitives et simples sur la messagerieélectronique, la messagerie instantanée, la voix, lesdonnées, la vidéo et la conférence Web.Exakis
    22. 22. En…. 25 Minutes !Présenter l’environnementLync 2013 HybridePrésenter les étapes demigrationsRéférencer les fonctionsd’interopérabilitéEn 25 Minutes !!!!!!!
    23. 23. COL203 Migration vers Lync 3013• Scénario d’usage– 100 % Cloud• Nouveaux utilisateurs ou externalisation– Hybride /• Utilisateurs locaux (sur site) / Utilisateurs Lync Online• Exemple :– Population fixe (Sur Site) et nomade (Online)» Nomades : commerciaux, Externes, invités• Coexistence réussie– Bonne connaissance des limites et des contraintesLync Online
    24. 24. Lync OnlineExchange OnlineSharePoint OnlineIM/PrésenceRéunions en LigneConférences Audio ettéléphoniques (Sur Site)Voix et TéléphonieCommunautés et sitesContenu et rechercheMessagerie, Calendrier &ContactsMessagerie Vocale28COL203 Migration vers Lync 3013
    25. 25. 29
    26. 26. Exchange Online Exchange Serveur(sur site)Lync Online  Intégration de la présence ClientLync Présence et MessagerieInstantanée en OWA Intégration de la présenceClient LyncLync Server on-premises Intégration de la présence ClientLync Présence et MessagerieInstantanée en OWA Intégration Mess. vocale Exchange Intégration de la présenceClient Lync Présence et MessagerieInstantanée en OWA Intégration Mess vocaleExchangeSharePoint Online SharePoint Serveur(sur site)Lync Online  Intégration de la présence ClientLyncIntégration de la présenceClient LyncLync Server on-premises Intégration de la présence ClientLyncIntégration de la présenceClient Lync Skill search in Lync client30Intégration de laprésence• Message dabsencedu bureau dansLync• Statut de présencebasé sur lescalendriers• Présence dansMicrosoft Outlooket OfficeIntégration de laprésence• Présenceintégrée dansles sitessharepoint
    27. 27. Migration Online coexistenceIM/P Conf Voix IM/P Conf VoixLCS 2005 SP1  N/A N/A  N/A N/AOCS 2007      OCS 2007 R2      Lync Server 2010      Lync Server 2013      Legend Aucune action Spécifiquerequise Action utilisateurs & Ouadmin requises Non Supporté31OCSR2 – Lync Online va demander de :1. Déplacer les utilisateurs vers Lync 2013 car lacoexistence à trois niveaux de version nest passupportée.2. Nécessitée de déployer un serveur Edge Lync 2013Lync 2010 -> Lync OnlineLa migration avec Depuis Lync va demander desajustements techniques concernant la configuration desfonctionnalités de conférence et voixLync 2013 -> Lync OnlineLa migration depuis Lync va demander des ajustementstechniques concernant la configuration desfonctionnalités de conférence et voixLa migration des utilisateurs de permet pas de migrerl’intégralité des données (Exemple Conférences planifiées)
    28. 28. Composants Description NotesOffice 365 DirSync Synchronisation de lActive Annuaire Locale avec Office365Prérequis identiques pour ExchangeActive Annuaire FédérationServices (AD FS)Infrastructure dauthentification unique (SSO). Permet àlutilisateur dêtre authentifié avec son compte AD local(Sur site)Prérequis identiques pour ExchangeLync 2010+ FédérationEdgeInteropérabilité entre le service online et local basé surla fédérationCoexistence entre Online et sur site• Messagerie Instantanée• ConférencesInterface administrationLync 2013Migration vers Lync Online Via Lync Powershell Linterface dadministration peutêtre utilisée pour déplacer desutilisateurs 2010 / 2013 verslenvironnement OnlineLync 2013 pool PourHybrid Voice featuresLe support des fonctions E911 et MédiaByPassnécessite que le Pool Lync 2013 soit déployé en localUniquement requis pour ces deuxfonctions spécifiquesDéploiement Serveur32
    29. 29. ActiveDirectoryLync 2010 PoolMicrosoftFédération GatewayLyncFédération EdgeAD FS v2(Geneva)DirSync – Provisioning, GALFédération Pour SSOLync Hybrid InteroperabilityIntégration It Local et lecloudLync OnlineOffice 365Exchange OnlineLegacy OCS 2007 R2Lync 2010+ PoolSharePointOnlineAnnuaire SyncEdgeIdentiqueExchange33
    30. 30. Lync Hybrid coexistence requires Lync 2013 Preview server roles on-premisesVersion sur site Lync 2013 hybrid topology Stratégie de MigrationOCS 2007 R2  Ferme Utilisateurs OCS 2k7 R2 Lync 2013 Fédération Edge(Route de fédération) Lync 2013 Pool (CMS)1. Déplacer les utilisateurs vers le Pool Lync20132. Déployer les clients Lync 20133. Déplacer les utilisateurs vers Lync Online4. Tache post migratoireRe-planifier les réunionsLync Serveur 2010  Demande linstallation de Lync2010 CU5 sur le Edge gérant lafédération Lenvironnement Voix Hybridedemande linstallation de Lync2013 en Local !1. Déplacer les utilisateurs Lync 2010 versLync Online2. Note : les clients Lync 2010 et 2013 sontsupportés3. Tâches post MigrationRe-planifier les réunionsServeur Edge et PoolLync 20131. Déplacer les utilisateurs Lync 2013 versLync Online2. Tâches post Migration3. Re-planifier les réunions34
    31. 31. Task DetailsDéployez DirSync en localTenant Lync 2013 créé dans Office 365 Provisionnez le tenant sur l’environnement Office365Ajouter les domaines pourl’environnement HybrideCréez les enregistrements TXT/CNAME record pourOffice 365.Activer les domaines pour DirSync Activez le tenant dans l’interface d’administrationPositionnement des certificats locauxpour AD FSMettez en place les certificats numériques pourpermettre le fonctionnement de AD FS pourfonctionner avec Office 365 SN: sts.<domaine> SAN: sts.domaines additionnelsEnregistrement DNS pour AD FS. Publiez un enregistrement A pour le domainests.domain pointant sur le serveur AD FS Local35
    32. 32. Activation de la federation sur le serveur EdgeSet-CsAccessEdgeConfiguration –AllowFederatedUsers $trueConfigure un partenaire d’hébergementNew-CsHostingProvider-Identity “LyncOnline”-Enabled $True-EnabledSharedAddressSpace $True-HostsOCSUsers $TRUE-ProxyFqdn “sipfed.online.lync.com"-IsLocal $False-VerificationLevel UseSourceVerification-AutoDiscoveryURLDéplacer l’utilisateurMove-CsUser <Identity> –Target sipfed.online.lync.com –Credentials $cred36
    33. 33. Fonctionnalités Lync OCS 2007 R2on-premises Lync2010+Office 365 GALync OnlineOffice 3652013 LyncOnlinePrésence enrichie    Messagerie instantanée    PC-to-PC appelaudio/video   Click To Communicate ausein d’ Office   Fédération avec LyncOnline/Live   Client Mac    Mobilité - iPhone N/A   Archivage IM    37
    34. 34. Fonctionnalités Lync OCS 2007 R2On-premises Lync2010+Office 365 GALync OnlineOffice 3652013 LyncOnlineFlux d’activitées N/A   Persistent chat    IM/Présence* (via OWA)    Recherche dans SharePoint N/A   Fédération avec Yahoo,AOL   TBDMobilité - BES N/A   Mobilité - Nokia    Mobilité - Windows    38
    35. 35. Fonctionnalités Lync OCS 2007 R2Lync on-premisesLync 2010Office 365Lync OnlineOffice 365 2013Lync Onlineaudio/video Multi parties    Rendez-vous non programmés   Appel Externe vers le PSTNC    Partage de bureau    Partage d’application    Reunions programmées    Intégration clients “riches”dans les réunions   Reach client for meetings    CAA PSTN dial-in in meetings    Partenaires de conferenceAudio (Dialin)   Archivage des contenus deréunions   39
    36. 36. Fonctionnalités Lync OCS 2007R2on-premisesLync 2010+Lync OnlineHybrid VoiceLync OnlineLync to phoneMise en attente d’appel etreprise   Transfert d’appel    Suivi d’appel    Messagerie vocale (UM)    Périphérique USB    Appels externes- mobile    Délégation, Appels deGroupe   Intégration avec les PBXLocaux   Remote call control (RCC)    40
    37. 37. 1. Bonne connaissance et recensement des infrastructures existantes– Serveurs, Sba, Matériels & équipements utilisateurs– Contraintes réseaux, Service de base de données/ Prérequis clients pour Lync 20132. Validation de l’infrastructure cible– Rédiger un Document d’Architecture Technique– Maquette avec nom de domaine test sur Office365– Objectifs : valider les contraintes, les limitations et les fonctionnalités• Impact bande passante. (Utilisez le Bandwidth Calculator)• Ouverture des flux réseaux– Valider les fonctions de continuité de services et de reprise d’activité– Installer l’environnement de production en coexistence• Préparer l’existant (passage du CU5) sur Lync 20103. Migrez par étapes– Migration des utilisateurs a travers un pilote• Valider les impacts poste de travail• Planifier une période d’observation– Généraliser la migrationRésumé
    38. 38. • Blog– Franck : http://www.franckannet.fr/– Laurent : http://unifiedit.wordpress.com/– Nexthop : http://blogs.technet.com/b/nexthop/• Technet Lync 2013– http://technet.microsoft.com/en-us/library/gg398616.aspx• Outils :– Remote connectivity : https://testconnectivity.microsoft.com/– Lync 2010 Bandwidth Calculator: http://www.microsoft.com/en-us/download/details.aspx?id=19011• Matériels– Répartiteurs de charges (F5 / Kemp etc..)– Équipement utilisateur (Plantronics / Polycom et..)Quelques liens utiles