1. What’s new in Communications Server “14” Architecture & Deployment Ferjan Ormeling ferjanor@microsoft.com

2. Agenda Introduction Architectural changes Setup & Deployment Questions?

3. Agenda Introduction Architectural changes Setup & Deployment Questions?

4. Introduction Caveat: Some aspects are still being firmed up – information herein is subject to change

5. Agenda First look at Communicator “14” Architectural changes Setup & Deployment Questions?

6. Architectural Enhancements Streamlined server deployment −Eliminated need for standalone mediation −Co-location of all server roles except monitoring Data center disaster recovery options −Single pool split across separate data centers −Automatic failover to secondary data center

7. Software requirements

8. PIC MSN AOL Yahoo Remote Users Remote Users Edge Server DMZ Data Media SIP Federated Businesses FE Server(s) PSTN BE SQL server Media GW ExUM UC endpoints Archiving Monitoring AD On-premises Mediation Server

9. PIC MSN AOL Yahoo Remote Users Remote Users Edge Server DMZ Data Media SIP Federated Businesses FE Server(s) PSTN BE SQL server Media GW ExUM UC endpoints Archiving Monitoring AD On-premises Mediation Server

10. PIC MSN AOL Yahoo Remote Users Remote Users Edge Server DMZ Data Media SIP Federated Businesses PSTN Media GW ExUM UC endpoints Archiving Monitoring AD On-premises or Online FE Server(s) (Registrar, Mediation, Web, LIS, CAC, CMS…) BE SQL serverA/V Conf server SBA Analog Devices Tanjay, Aries: - IW phones - Common area phones Mediation Server

11. VOICE −OCS voice networks with any PBX −Direct SIP for signaling −G.711 & other standard codecs CONFERENCING −OCS conferencing connects to any PBX −Direct SIP for signaling −G.711 & other standard codecs PRESENCE −OCS presence is available to any PBX −SIP verbs to get and set presence Direct SIP OCS PBX CONFERENCING Direct SIP OCS PBX VOICE SIP get and set PRESENCE OCS userPBX user PBX user w/ OCS conf OCS PBX PBX user w/ OCS IM/P For Customers not yet ready to replace PBX PBX Interoperability For Customers not yet ready to replace PBX

12. PBX Interoperability Common Options Chosen by Customers 1. Full UC with legacy phone elimination Communications Server connects to PSTN or PBX via SIP Trunking, Direct SIP or gateway. User’s DID homed on Communications Server, user provided with optimized device. 2. Full UC with legacy phone left in place for transition period Same as above, but with the PBX phone left in place for transition, often with Simultaneous ringing used to have both Communicator and PBX phone ring. User has separate numbers for Communicator and PBX phones. 3. Legacy phone with OCS unified conferencing Office Communications Server connects to existing PBX systems via Direct SIP or SIP/PSTN gateway. Communicator allows user to “Join From” their PBX phone when in audio conferences

13. Agenda Introduction Architectural changes Setup & Deployment Questions?

14. Limitations with previous releases OCS 2007 and 2007 R2 Limitations with previous releases

15. Configuration data moved to custom store Communications Server “14” Configuration data moved to custom store

16. Data still in Active Directory Communications Server “14” Data still in Active Directory

17. Impact on Setup and Deployment Central Management Store Impact on Setup and Deployment

18. Setup Flow Install Topology Builder AD Setup AD Domain Joined System CS Systems Author desired Topology SQL Backend Publish Topology Local Setup Installs Core SQ L Retrieve Topology Install Components Activate Certificates SQL DBs setup performed by Topology Builder SQL Instance Central Management topology and configuration store

19. Setup UI Splash screen

20. Prepare Active Directory

21. Running “Install or Update Communications Server system” Local Setup Running “Install or Update Communications Server system”

22. Agenda Introduction Architectural changes Setup & Deployment Questions?