Microsoft has released SP1 for Exchange Server 2013 Rollups for Exchange 2007/2010

Microsoft has released updates for Exchange Server 2013, 2010, and 2007 as part of their quarterly release cadence. The 2007 and 2010 RUs are bug fixes to the product and not introducing new features (well techincally 2007 a few) while the Service Pack for 2013 adds a load of function and features. Like all past updates and future updates the download is huge as it is the entire bit-set rolled up into the distributable so don’t be alarmed to see a 1.53GB file coming down the pipe.

Information regarding the releases and new features may be found on the TechNet Exchange blogs and the links to the downloads may be found below. The TAP program these past few go-arounds have included the Exchange MVPs as well as external client which means the most critical set of eyes were looking at this 2013 release.

Released: Exchange Server 2013 Service Pack 1

Released: Update Rollup 5 for Exchange 2010 Service Pack 3 and Update Rollup 13 for Exchange 2007 Service Pack 3

Windows Server 2012 R2 and Database Availability Groups





Exchange Server 2013 SP1



MS Download

Exchange Server 2010 SP3 RU 5



MS Download

Exchange Server 2007 SP3 RU 13



MS Download

AOL PIC Users Fail / Presence Unknown

As all are aware Office Communication Server 2007 R2 was recently released and with it the ability to run the various code on Windows Server 2008 64bit. Everything appears to run/work correctly with the exception of AOL users via the PIC.


  • AOL Users' Presence is Inaccurate; it may show on-line, unavailable, or presence unknown
  • A message invite may be received from an AOL user but no information is ever received
  • Attempting to respond to an AOL user or start a conversation with an AOL user will fail

The fix was discovered by Microsoft Senior Escalation Engineer Scott Oseychik among others and is documented at:


The fix: in short you must modify the local security policy on the 2008 Edge server rearranging the TLS authentication methods. It is important to note that this fix and the issue do not apply if you have the OCS 2007 R2 bits installed on a Windows Server 2003 64-bit.

Yahoo! Service Outage for PIC Users

Originally published and re-distributed upon request at:

Yahoo! will be undergoing an emergency maintenance from 4:30pm to 4:30am PST. During this period, users will see intermittent presence issues. All other functionality will not be impacted.

More Information:

After the maintenance window expires, if you find you are still having issues, please first log out & then back into your Communicator client. If the issue still reproduces/occurs for you, please restart Edge Front-End services first. Allow me to apologize for this up front; I understand this will require an “emergency service restart change request” for some of you. If all this fails to resolve the PIC issue between your LCS/OCS deployment and Yahoo!, please engage Microsoft Customer Support Services. Premier customers: please leverage your Technical Account Manager to initiate the case creation process. Please be prepared to supply Edge Server logs, remote access via our EasyAssist applications from MSFT, and we will do our best to investigate and resolve this in a timely manner.

Exchange 2007 Roll-up 5 Released

Exchange 2007 RU5 was released yesterday approximately 6 weeks after RU4 was released. The current release corrects numerous bugs with the complete list found at The roll-up does not require a reboot but may take a considerable amount of time to install so be prepared. In testing I have not encountered any issues installing the roll-up and unlike RU4 all services did start as expected. Expect to see the RU released via Microsoft Update the first half of December. Until then, you can download the update directly from Microsoft Download at

Changing the External OCS ABS/Web Conferencing URL

It is not uncommon that I am asked "How do I change the external URL for conferencing within OCS?" There are multiple reasons for a user needing/wanting to change the URL, most often it being either they skipped the entry during setup (it does say <optional>) or the have decided to change the name. Whatever the reason is, the actual update is simple.

The update it self is updating the SQL or MSDE database with the new information. While it is possible to manually 'hack' the database and edit the tables directly, the UC team has made the process much easier using LCSCMD. LCSCMD is a command line application that may be found on the OCS server CD under setup or on your C drive of an OCS server located at C:\Program Files\Common Files\Microsoft Office Communications Server 2007.

To execute the command, simply type:

Lcscmd /web /action:updatepoolurls / /poolname:poolname

The is the DNS name that is resolvable from the outside and is your 'reverse proxy' role as defined in the documentation. the poolname is only the short name of the pool. For SE this would be your server name ( would be server) and for EE it is the common pool name ( would be pool01).