<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Inside OCS</title>
	<atom:link href="http://blog.insideocs.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.insideocs.com</link>
	<description>Microsoft Office Communications Server - Tips, Tricks, and Insight</description>
	<lastBuildDate>Thu, 26 Jan 2012 18:22:01 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Communicator &amp; Lync Sign-In Troubleshooting Tool (Version 3) by Curtis Johnstone</title>
		<link>http://blog.insideocs.com/2011/07/19/communicator-lync-lync-sign-in-troubleshooting-tool-version-3/comment-page-1/#comment-11866</link>
		<dc:creator>Curtis Johnstone</dc:creator>
		<pubDate>Thu, 26 Jan 2012 18:22:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insideocs.com/?p=1252#comment-11866</guid>
		<description>Hi Greg, most Lync &amp; Communicator sign-in errors are related to DNS or Certificates, and this tool greatly helps resolve sign-in troubles in these two areas.  Just enter your user SIP address in the box and hit the &quot;Go&quot; button.  The tools will use DNS to show which server it will use to sign-in (the top match).  You can then make sure the server is online and remotely retrieve the certificate.

If you are using Lync Online, the server certificate is likely configured correctly. 

I have seen heard of a similar error with Lync Online.  Read this thread - there is a suggested work around: &lt;a href=&quot;http://community.office365.com/en-us/f/166/t/3771.aspx&quot; rel=&quot;nofollow&quot;&gt;http://community.office365.com/en-us/f/166/t/3771.aspx&lt;/a&gt;.

Curtis</description>
		<content:encoded><![CDATA[<p>Hi Greg, most Lync &amp; Communicator sign-in errors are related to DNS or Certificates, and this tool greatly helps resolve sign-in troubles in these two areas.  Just enter your user SIP address in the box and hit the &#8220;Go&#8221; button.  The tools will use DNS to show which server it will use to sign-in (the top match).  You can then make sure the server is online and remotely retrieve the certificate.</p>
<p>If you are using Lync Online, the server certificate is likely configured correctly. </p>
<p>I have seen heard of a similar error with Lync Online.  Read this thread &#8211; there is a suggested work around: <a href="http://community.office365.com/en-us/f/166/t/3771.aspx" rel="nofollow">http://community.office365.com/en-us/f/166/t/3771.aspx</a>.</p>
<p>Curtis</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Communicator &amp; Lync Sign-In Troubleshooting Tool (Version 3) by greg dent</title>
		<link>http://blog.insideocs.com/2011/07/19/communicator-lync-lync-sign-in-troubleshooting-tool-version-3/comment-page-1/#comment-11864</link>
		<dc:creator>greg dent</dc:creator>
		<pubDate>Thu, 26 Jan 2012 11:46:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insideocs.com/?p=1252#comment-11864</guid>
		<description>What does this tool actually do? I&#039;m getting 2 different sign-in errors on Lync and cant for the life of me understand why.

&quot;There was a problem acquiring personal certificate required to sign in&quot; is what I keep seeing. Any help would be hugely appreciated.

We&#039;re using Lync hosted off-prem by the way, using Office 365.</description>
		<content:encoded><![CDATA[<p>What does this tool actually do? I&#8217;m getting 2 different sign-in errors on Lync and cant for the life of me understand why.</p>
<p>&#8220;There was a problem acquiring personal certificate required to sign in&#8221; is what I keep seeing. Any help would be hugely appreciated.</p>
<p>We&#8217;re using Lync hosted off-prem by the way, using Office 365.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lync &amp; OCS Migration Top 10 by Migrating your OCS Federated Partner Settings to Lync &#171; Inside OCS</title>
		<link>http://blog.insideocs.com/2011/01/11/lync-ocs-migration-top-10/comment-page-1/#comment-11838</link>
		<dc:creator>Migrating your OCS Federated Partner Settings to Lync &#171; Inside OCS</dc:creator>
		<pubDate>Tue, 24 Jan 2012 16:26:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insideocs.com/?p=1153#comment-11838</guid>
		<description>[...] InsideOCS &#8211; Lync &amp; OCS Migration Top 10 [...]</description>
		<content:encoded><![CDATA[<p>[...] InsideOCS &#8211; Lync &amp; OCS Migration Top 10 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lync &amp; OCS Migration Top 10 by Jonas Mellquist</title>
		<link>http://blog.insideocs.com/2011/01/11/lync-ocs-migration-top-10/comment-page-1/#comment-11632</link>
		<dc:creator>Jonas Mellquist</dc:creator>
		<pubDate>Sat, 07 Jan 2012 16:30:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insideocs.com/?p=1153#comment-11632</guid>
		<description>This is good stuff Curtis - precise and to the point!</description>
		<content:encoded><![CDATA[<p>This is good stuff Curtis &#8211; precise and to the point!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lync &amp; OCS Migration Top 10 by Curtis Johnstone</title>
		<link>http://blog.insideocs.com/2011/01/11/lync-ocs-migration-top-10/comment-page-1/#comment-11627</link>
		<dc:creator>Curtis Johnstone</dc:creator>
		<pubDate>Sat, 07 Jan 2012 03:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insideocs.com/?p=1153#comment-11627</guid>
		<description>Hi Octavio,

My understanding is that all OCS *servers* had to be upgraded to either R1 or R2 - you can&#039;t have a mixed server environment before introducing Lync - but in terms of mixing R1 and R2 clients, I think this is mostly supported. Did you read somewhere that mixing the R1 and R2 clients were not supported in a mixed server environment?

The general rule on the client-side is that previous client version have the most recent updates (hotfixes) installed.

You should read the section “Client Interoperability” section in the Migrating from Office Communications Server 2007 R2 to Lync Server 2010 Guide (&lt;a href=&quot;http://www.microsoft.com/download/en/details.aspx?id=9109&quot; rel=&quot;nofollow&quot;&gt;http://www.microsoft.com/download/en/details.aspx?id=9109&lt;/a&gt;).

There is also a section on “Lync Server 2010 Interoperability with Previous Client Versions”.  It details what functionality is supported with previous client versions and Lync.  In a nutshell, IM and Presence and Video are supported.  There is some limitations on the voice.  There are some noteworthy points about the conferencing functionality in there too.

Caveat – I have never mixed R1 and R2 clients in a mixed-server environment, but looking at that guide, I think you will be ok.

You should re-post this question to the Microsoft Lync Server Forums (&lt;a href=&quot;http://social.technet.microsoft.com/Forums/en-US/category/ocs&quot; rel=&quot;nofollow&quot;&gt;http://social.technet.microsoft.com/Forums/en-US/category/ocs&lt;/a&gt;) for more answers.

Hope that helps,
Curtis</description>
		<content:encoded><![CDATA[<p>Hi Octavio,</p>
<p>My understanding is that all OCS *servers* had to be upgraded to either R1 or R2 &#8211; you can&#8217;t have a mixed server environment before introducing Lync &#8211; but in terms of mixing R1 and R2 clients, I think this is mostly supported. Did you read somewhere that mixing the R1 and R2 clients were not supported in a mixed server environment?</p>
<p>The general rule on the client-side is that previous client version have the most recent updates (hotfixes) installed.</p>
<p>You should read the section “Client Interoperability” section in the Migrating from Office Communications Server 2007 R2 to Lync Server 2010 Guide (<a href="http://www.microsoft.com/download/en/details.aspx?id=9109" rel="nofollow">http://www.microsoft.com/download/en/details.aspx?id=9109</a>).</p>
<p>There is also a section on “Lync Server 2010 Interoperability with Previous Client Versions”.  It details what functionality is supported with previous client versions and Lync.  In a nutshell, IM and Presence and Video are supported.  There is some limitations on the voice.  There are some noteworthy points about the conferencing functionality in there too.</p>
<p>Caveat – I have never mixed R1 and R2 clients in a mixed-server environment, but looking at that guide, I think you will be ok.</p>
<p>You should re-post this question to the Microsoft Lync Server Forums (<a href="http://social.technet.microsoft.com/Forums/en-US/category/ocs" rel="nofollow">http://social.technet.microsoft.com/Forums/en-US/category/ocs</a>) for more answers.</p>
<p>Hope that helps,<br />
Curtis</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lync &amp; OCS Migration Top 10 by Octavio</title>
		<link>http://blog.insideocs.com/2011/01/11/lync-ocs-migration-top-10/comment-page-1/#comment-11594</link>
		<dc:creator>Octavio</dc:creator>
		<pubDate>Fri, 06 Jan 2012 00:01:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insideocs.com/?p=1153#comment-11594</guid>
		<description>Hello Curtis. I have read that prior to bringing up my Lync pool and first servers, that I need to have all OCS R2 servers and clients on the latest version/build. I have not however found any published notes about what is broken if say a certain users is running the OCS 2007 R1 client. I surmise that when I run the AD Schema prep for Lync, that something changes which breaks the possibility for an older R1 client to connect to our existing 2007 R2 front end as it does today. We have one group of users that we have had to keep using the R1 client of OCS. Its complicated, but due to their hardware setup. Do you happen to know exactly what breaks, or better yet if OCS 2007 R1 client should still connect and work properly with the R2 FE even when I add the Lync pool?</description>
		<content:encoded><![CDATA[<p>Hello Curtis. I have read that prior to bringing up my Lync pool and first servers, that I need to have all OCS R2 servers and clients on the latest version/build. I have not however found any published notes about what is broken if say a certain users is running the OCS 2007 R1 client. I surmise that when I run the AD Schema prep for Lync, that something changes which breaks the possibility for an older R1 client to connect to our existing 2007 R2 front end as it does today. We have one group of users that we have had to keep using the R1 client of OCS. Its complicated, but due to their hardware setup. Do you happen to know exactly what breaks, or better yet if OCS 2007 R1 client should still connect and work properly with the R2 FE even when I add the Lync pool?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Office 2010 Beta Integration with Communicator R2 &amp; the Live Meeting Add-In by Curtis Johnstone</title>
		<link>http://blog.insideocs.com/2009/12/10/office-2010-beta-integration-with-communicator-r2-the-live-meeting-add-in/comment-page-1/#comment-11585</link>
		<dc:creator>Curtis Johnstone</dc:creator>
		<pubDate>Thu, 05 Jan 2012 14:53:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insideocs.com/?p=702#comment-11585</guid>
		<description>Right-click on the Communicator icon in Windows taskbar and select &quot;Configuration Information...&quot;.  What does it say for &quot;MAPI Status&quot; ?

Curtis</description>
		<content:encoded><![CDATA[<p>Right-click on the Communicator icon in Windows taskbar and select &#8220;Configuration Information&#8230;&#8221;.  What does it say for &#8220;MAPI Status&#8221; ?</p>
<p>Curtis</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Remote UC Troubleshooting Tool (RUCT) by Dmitriy</title>
		<link>http://blog.insideocs.com/2011/11/14/the-remote-uc-troubleshooting-tool-ruct/comment-page-1/#comment-11579</link>
		<dc:creator>Dmitriy</dc:creator>
		<pubDate>Thu, 05 Jan 2012 10:44:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insideocs.com/2011/11/14/the-remote-uc-troubleshooting-tool-ruct/#comment-11579</guid>
		<description>Not possible to specify a separate external server dns</description>
		<content:encoded><![CDATA[<p>Not possible to specify a separate external server dns</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Office 2010 Beta Integration with Communicator R2 &amp; the Live Meeting Add-In by Pandey</title>
		<link>http://blog.insideocs.com/2009/12/10/office-2010-beta-integration-with-communicator-r2-the-live-meeting-add-in/comment-page-1/#comment-11549</link>
		<dc:creator>Pandey</dc:creator>
		<pubDate>Wed, 04 Jan 2012 07:25:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insideocs.com/?p=702#comment-11549</guid>
		<description>MS Communicator 2007 R2 + Office 2010 + WIN7 64x
-------------------------------------------------
After installing Office 2010 on my system &quot;Properties&quot; option on click of user name right click is disabled in comunicator. Any idea how can I fix the issue?

The issue was found after installation of Office 2010. It was with various users.

Thanks</description>
		<content:encoded><![CDATA[<p>MS Communicator 2007 R2 + Office 2010 + WIN7 64x<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br />
After installing Office 2010 on my system &#8220;Properties&#8221; option on click of user name right click is disabled in comunicator. Any idea how can I fix the issue?</p>
<p>The issue was found after installation of Office 2010. It was with various users.</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on iPhone Client for OCS by Vasanth Ram</title>
		<link>http://blog.insideocs.com/2009/10/06/iphone-client-for-ocs/comment-page-1/#comment-11211</link>
		<dc:creator>Vasanth Ram</dc:creator>
		<pubDate>Tue, 20 Dec 2011 21:18:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insideocs.com/?p=556#comment-11211</guid>
		<description>try fuze messenger its free on ios 4</description>
		<content:encoded><![CDATA[<p>try fuze messenger its free on ios 4</p>
]]></content:encoded>
	</item>
</channel>
</rss>

