As I mentioned in my previous post: https://blog.terenceluk.com/2011/01/quick-note-about-changes-to-how-lync.html the GUI of Lync Server 2010’s Control Panel only allows you to put in a domain and not a path after the URL. In OCS 2007 R2,
One of the changes I noticed with Lync Server 2010 during my earlier deployments was that you can no longer enter a URL for your External web services to download your Lync client’s address book.
Let me first apologize about the delay to everyone who I’ve promised that I’ll write a blog post about setting up coexistence between Microsoft OCS 2007 R2 and Lync Server 2010 as it’s been extremely
Lately, I’ve been asked quite a few times about how to handle coexistence between Lync Server 2010 and OCS 2007 R2 for automatic sign-on when you’re deploying Lync Server 2010 in parallel with your legacy
It’s been a week since I had the chance to go back to the Lync Server 2010 environment I was testing with earlier this month and as I continued the deployment after going through the
I’m not sure if it’s just me but I had a hard time finding documentation that clearly outline the steps required to completely remove Microsoft Lync Server 2010 from your environment. Yes, there are bits
While the error message: “Automatic collection of configuration data failed.” isn’t something you would normally encounter if you were following the Microsoft Lync Server 2010 deployment guide or have a healthy Lync environment, I have
I’m not exactly sure why I haven’t encountered this problem as often as I have during the past deployments I’ve been involved in but I finally did earlier this month when one of our clients
For those who have come across my previous blog posts about Lync Server 2010 users haven’t problems viewing OCS 2007 R2 users’ presence: https://blog.terenceluk.com/2011/01/presence-issues-between-microsoft-lync.html, the problem in this post is the exact reverse where: OCS
If you ever come across the following message while opening the Microsoft Lync Server 2010 Control Panel: It may be because you haven’t created an A record for your Enterprise pool. To fix this issue,
