Summerschool 2010 - Unified Now with Unified Communications. Presented by Joachim Farla (joachim.farla@e-office.com), UC Community Engineer

1. Microsoft Communications Server “14”Setup and Deployment Joachim Farla UC Community Engineer e-office Required Slide SESSION CODE: UNC315

2. Session Objectives and TakeawaysCommunications Server “14” Setup and Deployment Session Objectives Prerequisites: Software and Hardware requirements Changes in Setup and Deployment in this release Overview of End-to-End Setup and Deployment process Central Management Server and Store Planning Tool, Topology Builder, and Setup Demo Takeaways Communications Server “14” what has changed and why Purpose of Planning Tool, Topology Builder, and Setup UI and how it integrates

3. AgendaCommunications Server “14” Setup and Deployment Hardware recommendations and Software requirements Changes in Setup and Deployment Central Management Store and data in AD Setup Components and Setup Flow Prepare AD Setup and Deploy Demo Database setup Other setup tasks

4. AgendaCommunications Server “14” Setup and Deployment Hardware recommendations and Software requirements Changes in Setup and Deployment Central Management Store and data in AD Setup Components and Setup Flow Prepare AD Setup and Deploy Demo Database setup Other setup tasks

5. Hardware Recommendations Communications Server “14” “Backend” (BE) Spec* CPU 8 cores (Dual Quad-Core) 2.00 GHz+ 32 GB* Attached storage (10Krpm+, 72GB+), multiple spindles 2 NICs 1 GBps+ Server Virtualization support Including Audio/Video/AppSharing roles “Frontend” (FE) Spec* CPU 8 cores (Dual Quad-Core) 2.00 GHz+ 12 gigabytes (GB)* Attached storage (hard disk drive 10K rpm+, 72GB+) Applicable to other roles (Edge, Monitoring/Archiving) 2 network cards (NICs) 1 GB+ per second (GBps) * Baseline for 100,000 user pool with 10 FEs and 1 BE

6. Software requirements Communications Server “14” Communications Server “14” roles Windows Server 2008 SP2 x64 Windows Server 2008 R2 x64 PowerShell V2 Admin Tools, and Core Component Windows 7 (x64 only) Windows Vista SP2 (x64 only) PowerShell V2 SQL Server® Backend SQL 2005 (SP3) x64 SQL 2008 (SP1) x64 Active Directory Forest/Domain level Windows Server 2003 Windows Server 2008 Windows Server 2008 R2

7. Operating System Component PrerequisitesCommunications Server “14” PowerShell V2 RTM Not supported are PowerShell V1 and PowerShell V2 prerelease versions Internet Information Services (IIS) rewrite module 2.0 (redistributable) Selected IIS modules .NET 3.5 (SP1) Visual C++ (redistributable) Message Queuing MSMQ required for selected roles if Monitoring and/or Archiving functionality is deployed Active Directory® Domain Services Tools ( optional for AD Prep SQL 2005 Back Compatibility module required by Install-CsDatabasecmdlet

8. AgendaCommunications Server “14” Setup and Deployment Hardware recommendations and Software requirements Changes in Setup and Deployment Central Management Store and data in AD Setup Components and Setup Flow Prepare AD Setup and Deploy Demo Database setup Other setup tasks

9. Changes in Setup and DeploymentCommunications Server “14” All New! Why?

10. Microsoft Office Communications Server 2007 and 2007 R2Improvements over Previous Releases Configuration Data in AD, SQL, Windows Management Instrumentation (WMI) Now centralized with Communications Server “14” Changes to Office Communications Server (OCS) 2007 and OCS 2007 R2 configuration required changes to the AD DS schema Required schema changes delayed or blocked deployment Little or no schema changes moving forward Edge server with local configuration Edge configuration won’t get out sync Service User Accounts and password expiration Communications Server “14” services run as Network Service

11. AgendaCommunications Server “14” Setup and Deployment Hardware recommendations and Software requirements Changes in Setup and Deployment Central Management Store and data in AD Setup Components and Setup Flow Prepare AD Setup and Deploy Demo Database setup Other setup tasks

12. Configuration Data Moved to Custom StoreCommunications Server “14” Introducing Central Management Store (CMS) XML documents stored in SQL database Contain all data: Topology, Policies, Configuration Single master database (DB) per deployment Central Management Server Runs on one Pool per deployment Pushes (replicates) changes to configuration to each server Replication via HTTPS to Edge servers in Perimeter Network Replica Each server has replica copy of master DB Servers continue to operate without access to master DB

13. Data remaining in Active DirectoryCommunications Server “14” Active Directory User extensions Back Compatibility Schema Office Communications Server 2007 and 2007 R2 schema extensions Enables interoperability and migration from previous versions Communications Server “14” will create back compatibility entries for previous versions Third party application compatibility Will be discontinued in future releases

14. Central Management Store (CMS)Communications Server “14” Impact of the CMS on Setup and Deployment Topology document contains Pools, server (fully qualified domain name (FQDN/ IP addresses/Ports), Server roles/components and dependencies Local Setup uses Topology document to install and activate Topology document needs to be authored before any server role can be installed SQL Server Database is required for initial deployment Enterprise Edition Pool requires full SQL Server deployed Standard Edition uses a SQL Server Express - separate option in Setup Menu

15. AgendaCommunications Server “14” Setup and Deployment Hardware recommendations and Software requirements Changes in Setup and Deployment Central Management Store and data in AD Setup Components and Setup Flow Prepare AD Setup and Deploy Demo Database setup Other setup tasks

16. Setup ComponentsCommunications Server “14” Communications Server “14” Core (OCSCore.msi) Core component and DLLs PowerShell Provider (PowerShell V2 is required) Planning Tool Topology Builder Setup User Interface (UI) - local Setup

17. Setup flowCommunications Server (CS) “14” AD SQL Backend Domain Joined System CS “14” server If first pool is Standard Edition: SQL instance is SQL Express Local Setup Installs Core AD Setup Add/Remove Retrieve Topology Install Topology Builder Install Components Author desired Topology SQL SQL SQL Activate SQL Instance Central Management topology and configuration store Publish Topology Certificates Certificate Maintenance

18. Setup UI Main screenCommunications Server “14”

19. AgendaCommunications Server “14” Setup and Deployment Hardware recommendations and Software requirements Changes in Setup and Deployment Central Management Store and data in AD Setup Components and Setup Flow Prepare AD Setup and Deploy Demo Database setup Other setup tasks

20. Prepare Active DirectoryCommunications Server “14”

21. Prepare Active DirectoryPowershellCmdlets Schema Prep Install-CSADServerSchema –ldf <PathtoLDFfiles> Current state: Get-CSSchemaState Forest Prep Enable-CSAdForest Current state: Get-CSForestState Domain Prep Enable-CSAdDomain Current state: Get-CSDomainState

22. AgendaCommunications Server “14” Setup and Deployment Hardware recommendations and Software requirements Changes in Setup and Deployment Central Management Store and data in AD Setup Components and Setup Flow Prepare AD Database setup Other setup tasks

23. AgendaCommunications Server “14” Setup and Deployment Hardware recommendations and Software requirements Changes in Setup and Deployment Central Management Store and data in AD Setup Components and Setup Flow Prepare AD Database setup Other setup tasks

24. Database Setup CmdletInstall-CsDatabase, and when to use CmdletInstall-CsDatabase Reads Topology document and configures SQL Stores based on assigned roles (remotely) Access SQL instance and check for connectivity and permissions Creates databases and table Creates DB roles and store procedures Run by Topology Builder Integrated in Topology Builder Requires admin to have SQL admin Run as standalone cmdlet SQL admin may be separate from Communications Server “14” Admin More flexibility Special usages: Custom path, SQL cluster, SAN storage

25. AgendaCommunications Server “14” Setup and Deployment Hardware recommendations and Software requirements Changes in Setup and Deployment Central Management Store and data in AD Setup Components and Setup Flow Prepare AD Database setup Other setup tasks

26. Other Setup tasksCommunications Server “14” Kerberos Authentication option IIS as Network Service, service principal name (SPN) for Pool Solution via using a Computer Account in Active Directory Computer Account password does not fall under password expiration policies PS Cmdlet available to create, assign, and manage account name and password Optional configuration If not configured, NTLM authentication is used

27. Takeaways Communication Server “14” Platforms and perquisites New configuration store and application Setup and Deployment overview New deployment tools See articles on NextHop for details about Migration and Coexistence

28. Microsoft Communications Server “14” Setup and Deployment Q&A

29. Unified Communications Track Call to Action! Learn More! View Related Unified Communications (UNC) Content at TechEd/after at TechEd Online Visit microsoft.com/communicationsserver for more Communications Server “14” product information Find additional Communications Server “14” content in the Technical Library, weekly technical articles at NextHop, and follow DrRez on Twitter Check out Microsoft TechNet resources for Communications Server and Exchange Server Visit additional Exchange 2010 IT Professional-focused content Partner LinkorCustomer Link (Name: ExProPword: EHLO!world) Try It Out! Exchange 2010 SP1 Beta downloadis now available from the download center!

30. © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.