December 2012 Update for OCS 2007 R2

in case you are not aware, Microsoft released the December updates for OCS 2007 R2, here they are:

Product	KB		Download
Product	Version	External	External
Office Communications Server 2007 R2	3.5.6907.266	968802	MS download
Office Communicator 2007 R2	3.5.6907.266	2755391	MS download
Group Chat Server 2007 R2	3.5.6907.266	2783873	MS download
Group Chat Client 2007 R2	3.5.6907.265	2735021	MS download
Group Chat Administration Tool 2007 R2	3.5.6907.265	2728997	MS download

You can find the most recent update information for OCS 2007 R2 at Updates Resource Center for Office Communications Server 2007 R2 and Clients.

#Lync Client #Virtualization the full story #ucoms #Citrix #xendesktop #xenapp

if you have been reading carefully, Citrix released a document the article published here http://support.citrix.com/article/CTX128831 .

by that time, I knew internally that Microsoft didn’t support Client virtualization for OCS/Lync. although if you have been reading and even attended Citrix Xenapp 6 or Xendesktop training you will hear a lot about Lync/OCS client virtualization delivery with Xenapp or Xendesktop.

starting 14/4, Microsoft released a document that explains the supportability statement for Xenapp and Xendesktop and virtualization techniques that they support/no support.

the document is available here http://www.microsoft.com/downloads/en/details.aspx?FamilyID=f865e66d-1163-46ef-ba9c-d585376dfbae.

in summary Microsoft now supports client virtualization through full desktop or application delivery/streaming with some considerations “check the document for more details” it is so amazing to see that Microsoft finally released such a support statement and changed the fully rigid statement of the big NO before.

#Lync Web Scheduler is now RTM #Microsoft #UCOMS

Lync Web Scheduler is a resource kit tool for Microsoft® Lync Server 2010. It provides a Web-based alternative to the add-in for the Microsoft Office Outlook® messaging and collaboration client for the purpose of scheduling a meeting using Lync Server 2010. It also provides a browser-based conference management experience that includes operations such as the following:

· Scheduling a new online Lync meeting.

· Listing all existing Lync Server 2010 meetings that the user has organized.

· Viewing and modifying details of an existing meeting.

· Deleting an existing meeting.

· Sending an email invitation to meeting participants by using a configured SMTP mail server.

· Joining an existing conference.

you can download it from here

http://www.microsoft.com/downloads/details.aspx?FamilyID=b7d8f948-fa64-4c51-8b54-2223954d1fa4

#Lync #ocs upgrade EVAL to volume license version

Thanks to Nathan Winters for sharing it.

to upgrade from the EVAL to the VL version from lync simply follow those steps

after they secure access to volume bits  through a legitimate channel – ie. VL site:

 

On every machine which has EVAL version of Server.MSI installed:

1. run “msiexec.exe /fvomus server.msi EVALTOFULL=1 /qb (Note: the server.msi is from Volume media)
2. run PS cmdlet “enable-cscomputer”

 

#Lync #ocs #ucoms #Microsoft #uc answering, why I should upgrade to Lync

in case you missed my session at PDC last week, also if you are not arabic speaker, I have delivered a session on why you should consider upgrading to Lync and answering the why.

Lync has so many features by I created the most important and killer features, this is not to summarize all of the features of lync but those are the most killers I like about Lync.

the presentation attached I don’t Want to Upgrade to Lync

#Lync #OCS #ucoms Restricted OCS Deployment ports requirements and firewall rules details

we have been working with the OCS PG last week in preparing a detailed table for ports requirements and firewall configuration for restricted OCS deployments.

the difference in this table that we have detailed as much as we can the different communication ports and firewall requirements for all of the segmented including internet, internal and enterprise voice communications.

we also detailed the ports and communication paths so it can be reader-friendly for the Security/Firewall engineers.

the wiki assumes that servers are deployed in the same VLAN and separated by a very restricted firewall configuration, Edge is deployed in the DMZ and again restricted firewall configuration is required.

currently the document still being reviewed, but if you are interested in following it you will find it on the wiki, here http://social.technet.microsoft.com/wiki/contents/articles/ocs-2007-r2-firewall-port-settings.aspx, we will be publishing another one for Lync as well linked to the wiki.

we will validate the wiki this week at a customer location and we will publish the updates later.

Reference: http://www.shudnow.net/2009/08/29/office-communications-server-2007-r2-audiomedia-negotiation/

Thanks to Tom, Rick and Rui for their support during creating this wiki.

well done ya kimooooooooooo

#OCS #Lync Lync 2010 vs OCS 2007 R2 vs OCS 2007 R1 Client Supportability Matrix

if you have been reading Jeff’s Post http://blog.schertz.name/2010/09/lync-client-unsupported-ocs/ then you will know that Lync Client is not supported with OCS, for further details I have prepared this Table to list the supported clients against servers:



#OCS 2007 R2: Over the past 1 minutes Office Communications Server has experienced TLS outgoing connection failures 1 time(s). The error code of the last failure is 0x80090322

in OCS 2007 R2 you might get the following error:

TLS outgoing connection failures.

Over the past 1 minutes Office Communications Server has experienced TLS outgoing connection failures 1 time(s). The error code of the last failure is 0x80090322 (The target principal name is incorrect.) while trying to connect to the host “serer FQDN”.

Cause: Wrong principal error could happen if the peer presents a certificate whose subject name does not match the peer name. Certificate root not trusted error could happen if the peer certificate was issued by remote CA that is not trusted by the local machine.

Resolution:

For untrusted root errors, ensure that the remote CA certificate chain is installed locally. If you have already installed the remote CA certificate chain, then try rebooting the computer.

TLS outgoing connection failures.
Over the past 1 minutes Office Communications Server has experienced TLS outgoing connection failures 1 time(s). The error code of the last failure is 0x80090322 (The target principal name is incorrect.) while trying to connect to the host “oce-fe.pas.com.eg”.Cause: Wrong principal error could happen if the peer presents a certificate whose subject name does not match the peer name. Certificate root not trusted error could happen if the peer certificate was issued by remote CA that is not trusted by the local machine.Resolution:For untrusted root errors, ensure that the remote CA certificate chain is installed locally. If you have already installed the remote CA certificate chain, then try rebooting the computer.

Cause:

This is mainly because of wrong certificate names, validate that edge and OCS front end have the correct FQDN (((Recently I found that FQDN configured in the OCS 2007 R2 Administrative console on Edge and on the front End is case sensetive and has to match the server FQDN and the Certificate FQDN letter cases so make sure that you have the FQDN has the correct letter cases so EDGE.domain.com is not like edge.domain.com)))

An error occurred while trying to start the conference. More details (ID:504) , The following message was not delivered to all participants. More details (ID:504)

when trying send an IM to more than one contact,display the below error:

An error occurred while trying to start the conference. More details (ID:504)

The following message was not delivered to all participants. More details (ID:504)

Solution:

update package for Communicator 2007 R2?

http://support.microsoft.com/kb/978564

And especially this KB.

http://support.microsoft.com/kb/975858/