leedesmond’s blog

For an OCS 2007 R2 infrastructure configured for federation, running the Validation Wizard on your Standard or Enterprise edition Front-End server* and selecting “Validate Connectivity” may report back with a failure message similar to the one here:

Failure
[0xC3FC200D] One or more errors were detected

Global Federation Route edgehostname.swissitpro.ch

DNS Resolution succeeded:  w.x.y.z
TLS connect failed due to incorrect remote subject name: w.x.y.z:5061 Error Code: 0×80090322 outgoing TLS negotiation failed; HRESULT=-2146893022

where w.x.y.z = internal NIC IPv4 address of Edge Server (edgehostname.swissitpro.ch)

This failure is caused by a certificate misconfiguration. Typically, an Edge Server is not part of the internal AD domain. As a standalone server, there is no FQDN per sec for the Edge Server; only the hostname (or NetBIOS name if you will). Therefore, ensure that the Subject (CN) of the certificate that is assigned to the internal NIC matches the hostname of the machine. A single entry in the Subject Alternative Name (SAN) with the same information is also recommended.

* forest node / server edition / server FQDN / Validation / Front End Server

Technorati tags: LCS/OCS, OCS 2007 R2

No Comments »

- OCS 2007 R2 Group Chat Hotfix KB980042
This hotfix is described in more details under KB 980042, 980043, and 982128, bringing Group Chat to version 6907.198

- OCS 2007 R2 Group Chat SDK (KB981449)
This is the Apr 2010 update of the Group Chat SDK for Office Communications Server 2007 R2 platform (version 6907.198) which includes documentation and sample applications (download).

- Microsoft Unified Communications Business Value Tool (link)

Technorati tags: LCS/OCS, OCS 2007 R2

No Comments »

Mark your calendars for the next Swiss IT Pro User Group events. Taking place on the first Tuesday of every month in Zurich, you are invited to join the PowerShell Script Club on 4 May and 1 Jun 2010. This is moderated by our very own PowerShell MVP.

Registration for this free event and more information here.

Technorati tags: Windows 7, Windows Server 2008 R2, PowerShell, Community/User Group, Events

No Comments »

Hot off-the-press!

The RTM of Office 2010, SharePoint 2010, Visio 2010 and Project 2010 have been announced! Join in the virtual event launch on 12 May 2010 at 1100 hrs (US Eastern). More information at www.the2010event.com. Retail availability of Office 2010 is expected in June 2010 with pre-order possible at store.microsoft.com/OfficePreorder today.

In the meantime, check out the “Office 2010: Product Guides” (download). This provides a good overview of what’s new with a deep look into Office Web Apps and Office Mobile 2010. On a related note, the final release of Silverlight 4.0 is now shipping; check it out here for more.

Other items of interest:
- Microsoft Office Protocol Documentation
- Microsoft Office File Formats Documentation
- Microsoft SharePoint Products and Technologies Protocol Documentation
- Microsoft Online Services Sign In (Windows)
- Office 2010 Reaches RTM! (Office 2010 product development group)

Technorati tags: Office 2010, SharePoint 2010

No Comments »

Here is a quick digest of the most recent updates for OCS 2007 R2, Communicator 2007 R2 and Communicator Phone Edition 2007 R2.

-  OCS R2 Hotfix KB968802 (download)
Apply this hotfix to bring the various server roles to version 6907.196.

- Communicator 2007 R2 Hotfix KB978564
This cumulative update brings MOC up to version 6907.196*.

- OCS R2 Attendant Hotfix KB980936

- Office Communicator Phone Edition (2007 R2)
This cumulative update is described in KB981526.

- Unified Communications Retired Devices Optimized for Microsoft Office Communicator (link)

- Unified Communications Phones and Peripherals Datasheet (link)

See also:
- Important OCS CUCM Interop Update: RTCP Timer Issue Solved
- INFO: OCS 2007 R2 Cumulative Update 5 - Une mise à jour conséquente…

* update #7 for MOC R2

Keywords: patch, hotfix, update, rollup package, moc, ocs, 2007, r2

Technorati tags: LCS/OCS, OCS 2007 R2, Mobile

No Comments »

Bumping into the errors listed here can mean one or more things. In this case, it was attributed to a CD/DVD authoring software suite which took more space than expected during installation. The executable itself is about 200MB in size.

This happened when the application’s setup started to extract temporary files on the system (boot) volume defined by %temp% and %tmp%. In the end, it consumed more than 1.5GB of disk asset, reducing hard disk space to an absolute minimum that even risks crashing the operating system itself.

As a result, even Windows disk clean-up Wizard volunteered to check and run through spring-cleaning. If you start Outlook during this time, the error(s) will send you around scratching your head. The solution is obvious; free up ample space and make sure that there is always at least 10% of free disk space on the system volume (general guide).

—————————
Microsoft Office Outlook Offline Folders
—————————
The file C:\Users\name\AppData\Local\Microsoft\Outlook\outlook.ost cannot be accessed.
—————————
OK
—————————

and

Cannot open your default e-mail folders

This error can occur if you attempt to run Outlook from a Terminal Server session when the OST file is in use by the console session.

To access this instance of Outlook, exit the current Terminal Server session, and then start a new session by using the following Run command in Microsoft Windows:
mstsc.exe /CONSOLE

You must be an administrator on the computer that is accessing the console session. You cannot access a console session from a computer running Microsoft Windows XP Home edition. But you can do so from a computer running Microsoft Windows Server 2003, Microsoft Windows XP Professional, or Microsoft Windows Vista.

For more information, see Microsoft Knowledge Base article 826488.

Technorati tags: Exchange, Outlook

No Comments »

This guest post is contributed by Hugh Marlor, Senior Consultant, BT (Idaho, US). For questions, comments, feedback or any topics you would like to share, feel free to submit them directly by using the comment feature linked to this (or related) blog post.
—

When planning for the deployment of certificates in an OCS Pool, you should pay special attention to the use of the SAN (Subject Alternate Name) fields.

The OCS R2 Enterprise Edition Deployment Guide indicates that SAN fields are only required for multiple SIP domains. In the Certificate deployment document, it states that wildcards are allowed in the SAN fields of OCS Pool certs. The truth is that if you are supporting web conferencing from the public internet then your OCS pool certificate must contain in the SAN fields the FQDNs of each FE server. If you use wildcards in the SAN fields, the OCS services won’t even start.

There is also no mention when deploying external web conferencing that you must include the FQDN of each FE server in the SAN field of the OCS Pool cert. This is because the Access Edge servers connect directly to the FQDNs of the OCS FE servers when external users join a meeting.

Technorati tags: LCS/OCS, OCS 2007 R2

No Comments »