Mes: octubre 2009

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
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
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

Important:

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.

Hola,

el problema con el KB974571 ya esta corregido!! El equipo de producto en su blog http://communicationsserverteam.com/archive/2009/10/14/632.aspx ha publicado que se ha desarrollado un hotfix para el tema de caducidad en el OCS. por favor visiten nuevamente el vinculo del KB MS09-56: Vulnerabilities in CryptoAPI could allow spoofing o http://support.microsoft.com/kb/974571 donde encontraran lo siguiente

…“Resolution for the known issue

A fix that resolves this issue is available for download from the Microsoft Download Center. To obtain the fix, visit the following Microsoft Web page:

http://go.microsoft.com/fwlink/?LinkId=168248 (http://go.microsoft.com/fwlink/?LinkId=168248)

The fix (OCSASNFix.exe) is governed by the Microsoft Software License Agreement for Office Communications Server 2007 R2, Office Communications Server 2007, Live Communications Server 2005, Office Communicator 2007 R2, Office Communicator 2007, and Office Communicator 2005.
This fix works for both clients and servers, and it is applicable to the following roles for all versions of Office Communications Server and Live Communications Server 2005 SP1 and for evaluation versions of Office Communicator:

• Standard Edition Server
• Director server role
• Enterprise Edition Consolidated
• Enterprise Edition Distributed – Front End
• Edge Server
• Proxy server role
• Office Communicator 2007 Evaluation version only
• Office Communicator 2007 R2 Evaluation version only
• Office Communicator 2005 Evaluation version only

To run the fix, type the following command at a command prompt, and then press ENTER:

ocsasnfix.exe

When you run the command on a computer that is running Office Communication Server 2007, Office Communication Server 2007 R2, or Live Communications server 2005 Service Pack 1, you receive a message that resembles the following:

Checking OCS/LCS Server installation…Fixing registry data
Checking Office Communicator 2007 Eval installation…not installed.
Checking Office Communicator 2005 Eval installation…not installed.

When you run the command on a computer that is running an evaluation version of Office Communication Server 2007, Office Communication Server 2007 R2, or Live Communications server 2005, you receive a message that resembles the following:

Checking OCS/LCS Server installation…not installed.
Checking Office Communicator 2007 Eval installation…Fixing registry data
Checking Office Communicator 2005 Eval installation…not installed.

This fix can be applied either before or after you install security update 974571. If you apply the fix after you install security update 974571, we recommend that you apply the fix before you restart the computer. If you already restarted the computer after you installed security update 974571, this fix can still be applied. However, the Office Communication Services must be started manually.
If all services start without any issues, this indicates that this fix has been applied and is working correctly.
This fix sets the OCSASNFIX DWORD value to 1 for the following registry subkey on the OCS 2007/R2 and LCS 2005-SP1 Server:

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesRtcSrvInstallInfoOCSASNFIX

Back to the top

Additional known issues with this security update

When you deploy the Standard Edition role on a new installation of any version of Office Communications Server, activation fails if security update 974571 is installed. To resolve this problem, apply this fix, and then run the activation again. “…

Enjoy!!

Buenos Dias,

Esta semana ha sido bastatnte agitada por un problema que se esta presentando en los servidores de OCS en la que en forma inexplicable, muestra que esta expirada la version de OCS y que se debe instalar la version full.

El error mostrado es:

Event Type:    Error
Event Source:    OCS Server
Event Category:    (1000)
Event ID:    12290
Date:        10/16/2009
Time:        8:14:04 AM
User:        N/A
Computer:    XXXXX
Description:
The evaluation period for Microsoft Office Communications Server 2007 R2  has expired. Please upgrade from the evaluation version to the full released version of the product.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

y este otro:

Event Type:    Error
Event Source:    Service Control Manager
Event Category:    None
Event ID:    7024
Date:        10/16/2009
Time:        8:14:04 AM
User:        N/A
Computer:    XXXXX
Description:
The Office Communications Server Access Edge service terminated with service-specific error 3286842403 (0xC3E93C23).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

Despues de una revision del servidor, se encontro que habian unos parches instalados en la madrugada.

– Cumulative Security Update for ActiveX Killbits for Windows Server 2003 x64 Edition (KB973525)
– Security Update for Windows Server 2003 x64 Edition (KB971486)
– Security Update for Windows Server 2003 x64 Edition (KB974112)
– Security Update for 32-bit Windows Media Format Runtime 9.5 for Windows Server 2003 x64 Edition (KB954155)
– Security Update for Windows Server 2003 x64 Edition (KB974571)
– Security Update for Windows Server 2003 x64 Edition (KB975025)
– Security Update for Windows Server 2003 x64 Edition (KB958869)
– Security Update for Windows Server 2003 x64 Edition (KB969059)
– Security Update for Windows Server 2003 x64 Edition (KB975467)

buscando en internet, se encontro una referencia http://projectdream.org/wordpress/2009/10/13/kb974571-crypto-api-update-may-break-office-communications-server-2007-r2-installations/

se removieron los parches recien instalados y voila! subieron los servicios. en un cliente me mostro un problema de logon en el servicio al tratar de subirlo, asi que se digito nuevamente la contrasena y listo.

 

por favor tenganlo en cuenta en sus clientes. esta semana solo en Colombia he tenido tres de estos problemas.

 

Hans A.

Hola a todos!!

Gracias a los ruegos de todos nosotros y nuestras innumerables veces que estabamos a la mitad del camino en una implementacion de OCS 2007 o de OCS 2007 R2 y a la hora de hacer los certificados surgia mas de una pregunta, Microsoft libero un documento publico que expone este tema con “foticos” y todo.

 

Deploying Certificates in Office Communications Server 2007 and Office Communications Server 2007 R2

Disponible en el sitio publico de Microsoft en el vinculo:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=e9f86f96-aa09-4dca-9088-f64b4f01c703

…“Summary

In this document, you will learn about the properties and attributes of certificates when working with Office Communications Server 2007 and Office Communications Server 2007 R2. This document contains a walkthrough of most of the common, and some optional, tasks that you need to perform to realize the full value of the system. All roles that require certificates for deployment and operation are discussed. The properties are presented along with information to describe what they are and how they are used. This document shows you how to request the right certificate with the right parameters to make sure that you are delivering value to your users, rather than just troubleshooting problems.”…

Por favor, es una lectura obligada para el arquitecto de soluciones de voz y el consultor e implementador.

por favor, Enjoy!!!!

Hans A.