OCS R2 Summary – Virtualization – Collocation and PIC

Hola este es un pequeno resumen de OCS en estos tres ambitos:

Enjoy!!

OCS R2 en Virtualizacion:

Summary Support Statement*
This configuration is Supported.
* Customers with Premier-level support agreements should contact their account manager for more information
* Additional information is available in the “Support policy for Microsoft software running in non-Microsoft hardware virtualization software” which can be viewed here
Support Statement Details
Product: Office Communications Server 2007 R2 on Hyper-V with Windows Server 2008 R2 (x64) Guest OS
Search the Knowledge Base for information related to this configuration
More Information
For more information about OCS 2007 R2 Support on Virtualization, please see here
clip_image001 Supported features: Enterprise front-end server (Presence and IM), IM Conferencing Server, Access Edge Server, Back-End SQL Server 2008, Group Chat Channel Servers, Group Chat Look-up Server, Group Chat Compliance Servers, Group Chat Compliance back-end server, Archiving Servers, Monitoring (CDR only) Servers, Edge Access Servers
clip_image002 Unsupported features: Enterprise front-end server (Enterprise Voice audio and video), Standard Edition Server, Director, Audio/Video Conferencing Server, Application Sharing Conferencing Server, Web Conferencing Server, Telephony Conferencing Server, Mediation Server, Outside Voice Control Service, Conferencing Attendant Service, Response Group Service, Conferencing Announcement Service, Update Server, Communicator Web Access
**********************************************************************************************************************************************************************************************
Co-residencia de roles en OCS 2007 R2

Supported Server Role Collocation

This section identifies the Office Communications Server components that can be collocated on the same computer and the components that explicitly cannot be collocated. Any combination that is not identified has not been tested and is not supported.

The following table identifies the Office Communications Server roles and components that can and cannot be collocated. In addition to the server roles identified in the table, the following collocation scenarios are explicitly not supported for Office Communications Server 2007 R2:

  • Any server role on an Active Directory domain controller
  • Exchange UM and Office Communications Server

clip_image003Important:

Note that the following table identifies supported, not necessarily recommended, collocations.

Table 1. Server Role Collocation

This server role/configuration

Can collocate with this server role/component

Cannot collocate with this server role/component

Standard Edition configuration

· Archiving Server (not recommended)

· Monitoring Server

· Director

· Communicator Web Access

· Edge Server

· Mediation Server

· Group Chat Server or Compliance Server

Enterprise Edition consolidated configuration

None

Never collocated

Back-End Database

· Archiving database (in a shared SQL Server instance)*

· Monitoring database (in a shared SQL Server instance)*

· Group Chat database (in a shared SQL Server instance)*

· Compliance database (for Group Chat) (in a shared SQL Server instance)*

· Director database (only on a shared server; must run in a dedicated SQL Server instance)

· Back-End Database for a different pool

· Director database in a shared SQL Server instance

· Any other Office Communications Server role

Enterprise Edition expanded configuration, Front End Server

None

Never collocated

Enterprise Edition expanded configuration, Web Conferencing Server

None

Never collocated

Enterprise Edition expanded configuration, Application Sharing Server

None

Never collocated

Enterprise Edition expanded configuration, A/V Conferencing Server

None

Never collocated

Enterprise Edition expanded configuration, Web components

· Archiving Server

· Monitoring Server

· Front End Server

· Web Conferencing Server

· Application Sharing Server

· A/V Conferencing Server

· Director

· Communicator Web Access

· Edge Server

· Mediation Server

· Group Chat Server or Compliance Server

Director

None

Never collocated

Communicator Web Access

None

Never collocated

Edge Server

None

Never collocated

Mediation Server

None

Never collocated

Archiving Server

· Web components

· Monitoring Server

· Standard Edition server (not recommended)

· Front End Server

· Web Conferencing Server

· Application Sharing Server

· A/V Conferencing Server

· Director

· Communicator Web Access

· Edge Server

· Mediation Server

· Group Chat Server or Compliance Server

Monitoring Server

· Web components

· Archiving Server

· Standard Edition server

· Front End Server

· Web Conferencing Server

· Application Sharing Server

· A/V Conferencing Server

· Director

· Communicator Web Access

· Edge Server

· Mediation Server

· Group Chat Server or Compliance Server

Group Chat Server

None

Never collocated

Compliance Server (for Group Chat)

None

Never collocated

* Published performance test results assume that the Back-End Database runs in a dedicated SQL Server instance.

***************************************************************************************************************************************************************************************************************************************

Para el tema de federacion con Hotmail debemos tener en cuenta:

http://www.microsoft.com/communicationsserver/en/us/public-im-connectivity.aspx

Licensing Requirement

…“public instant messaging connectivity (PIC) license requirements for Office Communications Server connectivity to the Windows Live and AOL public IM networks. Now, customers with Office Communications Server 2007 R2 Standard CAL (or equivalent Software Assurance rights) will no longer require an additional license to connect with the millions of people who use Windows Live and AOL for instant messaging and presence. This change took place in July for Windows Live, and is scheduled for AOL in October 2009.”…

Licensing requirements for Public IM Connectivity depends on the service providers you want to connect with and your Communications Server client access licenses.

· Windows Live and AOL: Customers with Office Communications Server 2007 R2 Standard Client Access License or Office Communications Server 2007/ Live Communications Server 2005 SP1 Standard CAL license with active Software Assurance (SA) qualify for federation with Windows Live Messenger and AOL without additional licensing requirements. Customers who do not meet the qualifying requirement should buy the Office Communications Server Public IM Connectivity license for federation with Windows Live Messenger and AOL.

· Yahoo!: Federation with Yahoo! requires the Office Communications Server Public IM Connectivity (PIC) per user subscription license.

The Office Communications Server PIC license is sold separately on a per-user, per-month basis as a Microsoft service. PIC service licenses are available for Microsoft Volume License customers only.

· Google Talk: Federation with Google Talk can be enabled through the Microsoft Office Communications Server 2007 R2 XMPP Gateway, available at no additional licensing cost. This Gateway provides presence sharing and instant messaging (IM) with XMPP (Extensible Messaging and Presence Protocol) networks like Google Talk.

Provisioning Requirements

To provision your Office Communications Server environment for federation with public IM service providers (Windows Live, AOL, Yahoo!), the following information is required:

· The fully qualified domain name (FQDN) of your Access Edge service

· The name of your SIP domain

If Public IM Connectivity licenses were purchased through Microsoft Volume Licensing, details on how to submit this information will be available through the Microsoft Volume Licensing website.

If you qualify for federation with Windows Live and AOL through Office Communications Server 2007 R2 Standard CAL, please contact your Account Manager for details on submitting information about provisioning your network.

For more information on the provisioning process, please read the Office Communications Server Public IM Connectivity Provisioning Guide.

For more information on the Microsoft Office Communications Server 2007 R2 XMPP Gateway, please visit the download page.

Un comentario en “OCS R2 Summary – Virtualization – Collocation and PIC”

Deja un comentario

Tu dirección de correo electrónico no será publicada. Los campos obligatorios están marcados con *