June 2009 - Posts
You'll want to pay special attention to these if you are running the evaluation version of OCS 2007 R2 or Communicator 2007 R2. You can read more about it here: http://communicationsserverteam.com/archive/2009/06/10/523.aspx and here: http://support.microsoft.com/?kbid=972041
Read More...
I ran across this issue awhile back. I had a Tanjay running version 1.0.522.101. I updated it to the R2 software, version 3.5.6907.0. I then logged into the phone with a user homed on an R1 pool. Because I had the R1 Update Server deployed, the phone
Read More...
I've seen the following trip up a couple people when trying to manage an OCS 2007 R2 server installed on Windows 2008 remotely. The solution is simple. You need to allow Remote Administration in the Windows Firewall on your OCS 2007 R2 servers. Once you
Read More...
The first step is to stop all of the OCS services on all of the servers in the pool. Next you will want to backup the existing databases (rtc, rtcconfig, and rtcdyn). Open SQL Management Studio and connect to the instance that holds the OCS databases.
Read More...
Burried on page 329 of the OCS 2007 R2 Planning Guide is this important note about Windows 2008 Domain Controllers: Windows Server 2008 Support Office Communications Server 2007 R2 supports Windows Server 2008, both for servers running Office Communications
Read More...
