1. Running a Successful Voice ADS (UC83PAL)

2. Session Objectives And Takeaways Session Objective(s): Learn best practices for OCS and Lync 2010 Architecture Design Sessions Make it easier to win large FY11 Lighthouse deployments Key Takeaways Preparation is key Begin with the goal in mind: Successful deployment and good customer experience Recognize and complete the whole picture

3. Agenda Define ADS Preparation Key Voice Architecture Topics and Gotchas! Microsoft’s support on ADS Reviews

4. Define ADS Design session to gather required information in order to architect the end to end solution The partner engages with key technical stakeholders within the customer organization ADS is typically performed once the customer is committed to deploy

5. Preparation Objectives and Qualification Partner Participants and Agenda Objection Handling Key Topics Review

6. Preparation Objectives and Qualification Objectives for any Voice ADS Capture technical aspects of the infrastructure dependencies Design Architecture that meets customers’ requirements Sufficient information to validate proposal Result - an implementable Architecture and a high level deployment plan that would help write a good Statement of Work Objectives for any Voice ADS Capture technical aspects of the infrastructure dependencies Design Architecture that meets customers’ requirements Sufficient information to validate proposal Result - an implementable Architecture and a high level deployment plan that would help write a good Statement of Work Architecture Questionnaire from Customer Deployment Engineering would be a good tool to use to cover the various topics Another good tool to use would be OCS and or Lync 2010 Planning tool

7. Preparation New OCS/Lync 2010 deployment at customer: need a detailed ADS! Expansion of existing deployment: determine the extent of detail for an ADS Is customer ready to expand? Is architecture aligned with customer requirements? Does partner have sufficient information? If this is a new engagement for a large deployment (>2000 users)  Consult with V-PAM or V-TSP and engage with Customer Deployment Engineering (lynceng@microsoft.com) for additional guidance New OCS/Lync 2010 deployment at customer: need a detailed ADS! Expansion of existing deployment: determine the extent of detail for an ADS Is customer ready to expand? Is architecture aligned with customer requirements? Does partner have sufficient information? If this is a new engagement for a large deployment (>2000 users)  Consult with V-PAM or V-TSP and engage with Customer Deployment Engineering (lynceng@microsoft.com) for additional guidance Partner

8. Preparation Recommended IT Roles/Responsibilities Represented at a UC Architectural Design Session (ADS) 1.Executive sponsor Minimum: for the kickoff and first hour Best for entire session 2.Project manager Could be partner or Customer or both 3.Key technical resources 1.Microsoft Technologies Windows Server infrastructure Active Directory OCS/LCS/Lync 2010 Storage – (SQL Server) Exchange Recommended IT Roles/Responsibilities Represented at a UC Architectural Design Session (ADS) 1.Executive sponsor Minimum: for the kickoff and first hour Best for entire session 2.Project manager Could be partner or Customer or both 3.Key technical resources 1.Microsoft Technologies Windows Server infrastructure Active Directory OCS/LCS/Lync 2010 Storage – (SQL Server) Exchange Participants and Agenda

9. Preparation 2. Network infrastructure Includes DNS and DHCP 3. Security and firewall (including PKI) 4. Telephony PSTN PBX Voice mail 5. Desktop software and software distribution 6. Business continuance (backup, disaster recovery) 7. End-user support/training 2. Network infrastructure Includes DNS and DHCP 3. Security and firewall (including PKI) 4. Telephony PSTN PBX Voice mail 5. Desktop software and software distribution 6. Business continuance (backup, disaster recovery) 7. End-user support/training LEARNING Agree on detailed agenda with times and stakeholder participation to ensure closure LEARNING Agree on detailed agenda with times and stakeholder participation to ensure closure Participants and Agenda

10. Preparation Objection Handling 1.Lync Roadmap 2.Various interoperability scenarios Objection Handling 1.Lync Roadmap 2.Various interoperability scenarios Objection Handling

11. IP PSTN Gateways* Gateways* PSTN Public Internet Public Internet Active Directory Active Directory Exchange Server 2007 Exchange Server 2007 Unified Messaging Director EE Pool Consolidated Back End SQL Server Front End Servers Load Balancer** Consolidated Edge Server Consolidated Edge Server Load Balancer** Access Edge Web Conf Edge A/V Edge HTTP Reverse Proxy HTTP Reverse Proxy Existing PBX Network Or PSTN Existing PBX Network Or PSTN TDM or IP 11 Federated Networks Federated Networks Reference Topology and Key Topics CWA Server CWA Server Web Access Load Balancer** MediationServer(s)*MediationServer(s)* Hybrid Gateways Internal LAN and WAN Internal LAN and WAN Microsoft Infrastructure Telephony infrastructure Security Network Impact Customer User & Business Requirements Overall Project Management OCS 2007 R2 ArchivingArchiving IM Archiving Monitoring * CDRs and QoE Voice Quality Network Alerts

12. IP PSTN Gateways* Gateways* PSTN Public Internet Public Internet Active Directory Active Directory Exchange Server 2010 Exchange Server 2010 Unified Messaging Director EE Pool Back End SQL Server Front End Servers + A/V MCUs Load Balancer** Consolidated Edge Server Consolidated Edge Server Load Balancer** Access Edge Web Conf Edge A/V Edge HTTP Reverse Proxy HTTP Reverse Proxy Existing PBX Network Or PSTN Existing PBX Network Or PSTN TDM or IP 12 Federated Networks Federated NetworksMediationServer(s)*MediationServer(s)* Gateways/SBAs Internal LAN and WAN Internal LAN and WAN Microsoft Infrastructure Telephony infrastructure Security Network Impact Customer User & Business Requirements Overall Project Management Lync 2010 Archiving/MonitoringArchiving/Monitoring IM Archiving CDRs and QoE Voice Quality Network Alerts Reference Topology and Key Topics

13. Key Architecture Topics Understanding Customer Requirements Understanding the Existing IT Infrastructure Growing Existing Deployments Network Assessment Designing OCS/Lync 2010 & interop Infrastructure Additional Project Considerations Avoiding Failure

14. Understanding Customer Requirements Core to designing and deploying new technology What is the customer expecting from the implemented product? Ensure return on investment and productivity gains Requirements: Business; User; Operational; System Important: Need to understand Service Availability requirements

15. Understanding Existing IT Infrastructure Critical to the topology design – how can we fit the OCS/Lync 2010 topology into this existing infrastructure Team delivering ADS must use the time to understand the existing IT infrastructure Bigger organizations usually have multiple teams assigned to each infrastructure area Create an agenda to meet with each team – ask pertinent questions to understand specific technology areas Explain project vision to each team – identify risk areas

16. IT Infrastructure Areas to Consider Microsoft Infrastructure LCS 2005 or OCS 2007 or OCS 2007 R2 (Existing) Active Directory Services Phone Number Storage DNS Infrastructure (Internal & External) Network Time Services Certificate Services (Internal & External) Messaging Infrastructure Security Firewall Infrastructure Remote Access Services Networking Wide Area Networking Local Area Networking Requirement for Call Admission Control (CAC)

17. IT Infrastructure Areas to Consider Telephony PBX Infrastructure Media and Signaling Flow Operational Backup and Restore Disaster Recovery Antivirus and Content Filtering Environment Monitoring Client Environment Desktop Management Systems? Policies: Active Directory and Network Software Distribution

18. Microsoft Infrastructure Considerations Active Directory Forest topology? Single Forest, Single Domain Multi-Forest Special security considerations? PKI / Certificate Infrastructure What technology is implemented? What is the PKI topology Messaging Infrastructure Do they have Microsoft Exchange deployed? What version? What is the Exchange topology? How and where will Exchange UM be deployed?

19. Security Related Considerations Understand the customer’s perimeter security requirements Do they require a dedicated ‘security’ design? Other special considerations? Understand the Firewall topology What are the Service Availability requirements for Edge Access? Are there multiple Internet connections? Hosting live Internet IP’s in perimeter?

20. Telephony Considerations Meet the telephony team Clearly understand the existing telephony infrastructure Understand user dialing requirements – how users use phones Understand the Dial Plans What are the Media and Signaling Flows Special considerations: Emergency Calling Understand the long-term PBX replacement Plan Business and User requirements would drive telephony design Is there a requirement for branch office survivability?

21. Network Considerations Is there a requirement for Call Admission Control? Can existing data networks carry additional Voice data? What is the available bandwidth in the WAN? Are there QoS considerations Network Assessment is recommended Considerations: Special network policies in place? Special devices present on network to ‘shape’ data – how will this affect Media path?

22. Network Assessment Benefits Understand your UC network requirements Document your current network topology Identify your high level UC architecture Model your bandwidth and usage requirements Assess your current network Evaluate your network for bandwidth, jitter, and latency Reduce UC deployment risk and predetermine “Quality of Experience” Identify problematic network paths Analyze results of network assessment Predict future call quality Identify network problems prior to deployment Reduce the overall cost of your UC solution Guidance on next steps

23. Network Assessment for UC Microsoft Services Offering

24. Business Process Improvement with UC

25. Designing the UC Infrastructure UC Design Session Microsoft Infrastructure Networking Security Telephony IT Operations Client Environment Messaging Customer Requirements Project Vision

26. Additional Project Considerations Project Planning Dedicated Project Office – Project Manager; Project Plans. Risk Management End-User Change Management User Training Device distribution and removal Migration Planning Transition existing telephony to OCS Transition existing LCS 2005 or OCS 2007 deployments to latest OCS 2007 R2 or Lync 2010

27. Additional Project Considerations Service Availability Planning Service availability requirements defined by customer for: IM & Presence Enterprise Voice Conferencing Remote Access / Edge Services Exchange Unified Messaging Driven by customer requirements

28. Avoiding Failure Project Planning Core to assign dedicated Project Manager Must drive delivery through Project Plan Consider End-user Impact What it takes to change working environment for 2,000+ users World-wide deployment: Availability of training material Project Logistics Multi-site deployment / world-wide deployment What it takes to convert multiple remote locations Engineering resources; Physical Resource distribution (servers; gateways; client devices) Consider Operational Side Once first users are deployed there is suddenly a new operational component Helpdesk Ensure the project is governed by a signed off SOW

29. Growing an Existing Deployment Special considerations for existing Voice Pilot or Lighthouse deployments Voice Pilot, Conferencing and LDS deployments are often small Production deployments Initially not designed for Enterprise deployment How to transition these existing deployments into Enterprise deployments? Growing from Exchange UM to OCS/Lync Voice UM integrated into existing PBX Add OCS/Lync 2010 Enterprise Voice integration What if entire org will not use OCS/Lync 2010 Enterprise Voice (EV)? Impact of multiple Exchange UM Dial Plans and Pilot Numbers

30. Support Offerings from MSFT Engineering - Architecture Review for Enterprise Voice Deployments (>2K users)  The Architecture Review and Recommendations are for guidance to ensure good customer experience  Review is conducted for large deployments (>2,000 seats or above)  Applies to Microsoft FY11 Lighthouse/LDS/LHW Programs  Deployment Partner required to submit all relevant OCS/Lync 2010 architecture data to the online tool at http://www.ucnomination.comhttp://www.ucnomination.com  Architecture Questionnaire accompanying this deck can help facilitate the conversation during ADS, e.g. ask the right questions to ensure that technical aspects are covered  If you have questions about the Architecture Review please email lynceng@microsoft.co

31. Support Offerings from MS Engineering - Architecture Review: FY11 Lighthouse/LDS/LHW Programs The Architecture Review and Recommendations are for guidance to ensure good customer experience The review is conducted for large deployments (2,000 or above) only Deployment Partner required to submit all relevant OCS/Lync 2010 architecture data in online form Architecture to be reviewed by OCG Customer Deployment Engineering Team (lynceng@microsoft.com )lynceng@microsoft.com

32. Call to Action! Download This deck and familiarize yourself with both the materials and resources A sample of the ADS Session Agenda Architecture Questionnaire Use the resources linked in this deck Make sure the Voice SSP/ Voice PAM/ Voice TSP is engaged for large voice opportunities