<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.bricomp.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Unified Communications : PIC, OCS</title><link>http://blogs.bricomp.com/blogs/uc/archive/tags/PIC/OCS/default.aspx</link><description>Tags: PIC, OCS</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>AOL PIC Users Fail / Presence Unknown</title><link>http://blogs.bricomp.com/blogs/uc/archive/2009/04/06/aol-pic-users-fail-presence-unknown.aspx</link><pubDate>Mon, 06 Apr 2009 18:35:00 GMT</pubDate><guid isPermaLink="false">66976a03-1853-4e59-b4ff-5e5c16101910:12</guid><dc:creator>Brian Ricks</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.bricomp.com/blogs/uc/rsscomments.aspx?PostID=12</wfw:commentRss><wfw:comment xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.bricomp.com/blogs/uc/commentapi.aspx?PostID=12</wfw:comment><comments>http://blogs.bricomp.com/blogs/uc/archive/2009/04/06/aol-pic-users-fail-presence-unknown.aspx#comments</comments><description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Symptoms:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;AOL Users&amp;#39; Presence is Inaccurate; it may show on-line, unavailable, or presence unknown&lt;/li&gt;
&lt;li&gt;A message invite may be received from an AOL user but no information is ever received&lt;/li&gt;
&lt;li&gt;Attempting to respond to an AOL user or start a conversation with an AOL user will fail&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The fix was discovered by Microsoft Senior Escalation Engineer Scott Oseychik among others and is documented at:&lt;/p&gt;
&lt;p class="MsoNormal" style="margin:0in 0in 0pt;"&gt;&lt;span style="color:#1f497d;"&gt;&lt;a href="http://blogs.msdn.com/scottos/archive/2009/04/03/resolved-ocs-2007-r2-pic-fails-against-aol.aspx"&gt;&lt;span style="font-family:Calibri;color:#0000ff;font-size:small;"&gt;http://blogs.msdn.com/scottos/archive/2009/04/03/resolved-ocs-2007-r2-pic-fails-against-aol.aspx&lt;/span&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p class="MsoNormal" style="margin:0in 0in 0pt;"&gt;&lt;span style="color:#1f497d;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p class="MsoNormal" style="margin:0in 0in 0pt;"&gt;&lt;span style="color:#1f497d;"&gt;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.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.bricomp.com/aggbug.aspx?PostID=12" width="1" height="1"&gt;</description><category domain="http://blogs.bricomp.com/blogs/uc/archive/tags/OCS/default.aspx">OCS</category><category domain="http://blogs.bricomp.com/blogs/uc/archive/tags/R2/default.aspx">R2</category><category domain="http://blogs.bricomp.com/blogs/uc/archive/tags/AOL/default.aspx">AOL</category><category domain="http://blogs.bricomp.com/blogs/uc/archive/tags/PIC/default.aspx">PIC</category><category domain="http://blogs.bricomp.com/blogs/uc/archive/tags/Edge/default.aspx">Edge</category></item><item><title>Yahoo! Service Outage for PIC Users</title><link>http://blogs.bricomp.com/blogs/uc/archive/2008/12/07/yahoo-service-outage-for-pic-users.aspx</link><pubDate>Sun, 07 Dec 2008 10:45:00 GMT</pubDate><guid isPermaLink="false">66976a03-1853-4e59-b4ff-5e5c16101910:11</guid><dc:creator>Brian Ricks</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.bricomp.com/blogs/uc/rsscomments.aspx?PostID=11</wfw:commentRss><wfw:comment xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.bricomp.com/blogs/uc/commentapi.aspx?PostID=11</wfw:comment><comments>http://blogs.bricomp.com/blogs/uc/archive/2008/12/07/yahoo-service-outage-for-pic-users.aspx#comments</comments><description>&lt;p class="MsoNoSpacing"&gt;&lt;span style="color:black;"&gt;Originally published and&amp;nbsp;re-distributed upon request at: &lt;a href="http://blogs.msdn.com/scottos/archive/2008/12/05/office-communicator-clients-cannot-communicate-with-contacts-homed-on-yahoo-messenger-network.aspx"&gt;http://blogs.msdn.com/scottos/archive/2008/12/05/office-communicator-clients-cannot-communicate-with-contacts-homed-on-yahoo-messenger-network.aspx&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p class="MsoNoSpacing"&gt;&lt;span style="color:black;"&gt;Yahoo! will be undergoing an emergency maintenance from 4:30pm to 4:30am PST. During this period, users will see intermittent presence issues.&lt;span&gt;&amp;nbsp; &lt;/span&gt;All other functionality will not be impacted.&lt;/span&gt;&lt;/p&gt;
&lt;p class="MsoNoSpacing"&gt;&lt;b&gt;&lt;span&gt;More Information:&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
&lt;p class="MsoNoSpacing"&gt;&lt;span&gt;After the maintenance window expires, if you find you are still having issues, please first log out &amp;amp; then back into your Communicator client. &lt;/span&gt;&lt;span&gt;If the issue still reproduces/occurs for you, please restart Edge Front-End services first.&lt;span&gt;&amp;nbsp; &lt;/span&gt;Allow me to apologize for this up front; I understand this will require an &amp;ldquo;emergency service restart change request&amp;rdquo; for some of you. &lt;/span&gt;&lt;span&gt;If all this fails to resolve the PIC issue between your LCS/OCS deployment and Yahoo!, please &lt;a href="http://support.microsoft.com/oas/default.aspx?acty=ProductList&amp;amp;ctl=productlist&amp;amp;wf=PID&amp;amp;trl=PID%7EProductList&amp;amp;ln=en-us&amp;amp;prid=10580&amp;amp;gprid=525957"&gt;engage Microsoft Customer Support Services&lt;/a&gt;.&lt;span&gt;&amp;nbsp; &lt;/span&gt;Premier customers: please leverage your Technical Account Manager to initiate the case creation process. &lt;/span&gt;&lt;span&gt;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.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.bricomp.com/aggbug.aspx?PostID=11" width="1" height="1"&gt;</description><category domain="http://blogs.bricomp.com/blogs/uc/archive/tags/OCS/default.aspx">OCS</category><category domain="http://blogs.bricomp.com/blogs/uc/archive/tags/PIC/default.aspx">PIC</category><category domain="http://blogs.bricomp.com/blogs/uc/archive/tags/Yahoo_2100_/default.aspx">Yahoo!</category></item><item><title>AOL Root Certificate Update causing Presence Unknown in PIC</title><link>http://blogs.bricomp.com/blogs/uc/archive/2008/12/07/aol-root-certificate-update-causing-presence-unknown-in-pic.aspx</link><pubDate>Sun, 07 Dec 2008 10:36:00 GMT</pubDate><guid isPermaLink="false">66976a03-1853-4e59-b4ff-5e5c16101910:10</guid><dc:creator>Brian Ricks</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.bricomp.com/blogs/uc/rsscomments.aspx?PostID=10</wfw:commentRss><wfw:comment xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.bricomp.com/blogs/uc/commentapi.aspx?PostID=10</wfw:comment><comments>http://blogs.bricomp.com/blogs/uc/archive/2008/12/07/aol-root-certificate-update-causing-presence-unknown-in-pic.aspx#comments</comments><description>&lt;p&gt;For those that subscribe to the Public Internet Connector (PIC) feature in Office Communication Server, a recent change at AOL may impact you. As with all communication to and from OCS, certificates are used to encrypt and authenticate traffic. The PKI infrastructure AOL utilized in the past has changed and they have moved to their new AOL root certificates. Because of this, the OCS Edge/Access Proxy servers will not be able to validate any AOL traffic without a root certificate update.&lt;/p&gt;
&lt;p&gt;The official notice may be found here: &lt;a href="http://blogs.msdn.com/scottos/archive/2008/12/02/office-communicator-clients-cannot-communicate-with-contacts-homed-on-aol.aspx"&gt;http://blogs.msdn.com/scottos/archive/2008/12/02/office-communicator-clients-cannot-communicate-with-contacts-homed-on-aol.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;A link to the AOL certificates may be found directly here: &lt;a href="https://pki-info.aol.com/AOL/"&gt;https://pki-info.aol.com/AOL/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Remember. only the edge servers (those authenticating traffic) require the updates - not your clients - and a restart/reboot is not required.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.bricomp.com/aggbug.aspx?PostID=10" width="1" height="1"&gt;</description><category domain="http://blogs.bricomp.com/blogs/uc/archive/tags/OCS/default.aspx">OCS</category><category domain="http://blogs.bricomp.com/blogs/uc/archive/tags/AOL/default.aspx">AOL</category><category domain="http://blogs.bricomp.com/blogs/uc/archive/tags/PIC/default.aspx">PIC</category></item></channel></rss>