Embed Size (px)
DESCRIPTION
Agenda Introduction Architectural changes Setup & Deployment Questions?
Citation preview
Agenda• Introduction
• Architectural changes
• Setup & Deployment
• Questions?
Agenda• Introduction
• Architectural changes
• Setup & Deployment
• Questions?
IntroductionCaveat:Some aspects are still being firmed up – information herein is subject to change
Agenda• First look at Communicator “14”
• Architectural changes
• Setup & Deployment
• Questions?
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
Software requirements • Communications Server “14”
− Windows Server 2008 SP2 x64 − Windows Server 2008 R2 x64− Powershell V2
• Admin Tools, and Core − Win 7 (x64 only)− Vista SP2 (x64 only)− Powershell V2
• SQL Backend− SQL 2005 (SP3) x64− SQL 2008 (SP1) x64
• AD Forest/Domain level − Windows Server 2003− Windows Server 2008 − Windows Server 2008 R2
OCS 2007 R2 Voice Components
PICMSN
AOL
Yahoo
RemoteUsers
EdgeServer
DMZData
MediaSIP
FederatedBusinesses
FE Server(s)
PSTN
BE SQL server
Media GW
ExUM
UC endpoints
ArchivingMonitoring
AD
SIP Trunk
On-premises
Mediation ServerMediation Server Mediation Server
Direct SIP
Moving toward…
PICMSN
AOL
Yahoo
RemoteUsers
EdgeServer
DMZData
MediaSIP
FederatedBusinesses
FE Server(s)
PSTN
BE SQL server
Media GW
ExUM
UC endpoints
ArchivingMonitoring
AD
SIP Trunk
On-premises
Mediation ServerMediation Server Mediation Server
Direct SIP
CS "14" Voice Components
PICMSN
AOL
Yahoo
RemoteUsers
EdgeServer
DMZData
MediaSIP
FederatedBusinesses
PSTN
Media GW
ExUM
UC endpoints
ArchivingMonitoring
AD
SIP Trunk
On-premisesor
Online
Direct SIP
FE Server(s)(Registrar, Mediation,Web, LIS, CAC, CMS…)
BE SQL server A/V Conf server
SBA
Analog
Devices
Tanjay, Aries:- IW phones- Common area phones
Mediation Server
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
Note: Voice and conferencing via certified gateway if PBX does not natively support Direct SIP
Direct SIPOCS PBX
CONFERENCING
Direct SIPOCS PBX
VOICE
SIP get and set
PRESENCE
OCS user PBX user
PBX user w/ OCS conf
OCS PBX
PBX user w/ OCS IM/P
PBX InteroperabilityFor Customers not yet ready to replace PBX
PBX InteroperabilityCommon Options Chosen by Customers1. 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
Agenda• Introduction
• Architectural changes
• Setup & Deployment
• Questions?
OCS 2007 and 2007 R2Limitations with previous releases• Configuration Data in AD, SQL, WMI• Changes to OCS configuration required changes to
the AD schema• Edge server with local WMI configuration
Required schema delayed or blocked deployment Configuration could get out of sync
Communications Server “14”Configuration data moved to custom store
• Introducing Central Management Store− XML documents stored in SQL database− Contain all data: Topology, Policies, Configuration− Single master 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 DMZ
• Replica− Each server has replica copy of master DB− Servers continue to operate without access to
master DB
Communications Server “14”Data still in Active Directory
• AD User extensions
• Back Compat Schema − OCS 2007 R2/2007 schema extensions− To enable interop and migration from older
versions− CS “14” will create back compat entries for
legacy versions − 3rd Party application compatibility
Central Management StoreImpact on Setup and Deployment
• Topology doc contains− Pools, server (FQDN/IP addresses/Ports),− Server roles/components and dependencies
• Local Setup uses Topology doc to install and activate − Topology document needs to be authored before any
server role can be installed
• A SQL DB is required for initial deployment− Enterprise Edition Pool requires full SQL instance deployed− Standard Edition uses a SQL Express instance which has
to be installed in a separate step
Setup Flow
Install Topology Builder
AD Setup
AD
Domain Joined System CS Systems
Author desired Topology
SQL Backend
Publish Topology
Local SetupInstalls Core
SQL
SQL
SQL
RetrieveTopology
Install Components
Activate
Certificates
SQL DBs setup performed by Topology Builder
SQL InstanceCentral Management topology and configuration store
Setup UI Splash screen
Prepare Active Directory
Local SetupRunning “Install or Update Communications Server system”
Agenda• Introduction
• Architectural changes
• Setup & Deployment
• Questions?
© 2009 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.
