2 new recently discovered issues with Server 2008 R2 and OCS 2007 R2 - ABServer errors and moving users

Issue #1: Using the OCS 2007 R2 Administration tools on Server 2008 R2 has shown to be problematic for moving users from LCS and OCS 2007 R1/R2 to other OCS servers. For now, it is best to use a non-Server 2008 R2 workstation or server to move users to and from OCS servers. You can 'force' the users to move, but it doesn't always result in a good move. So, avoid it if possible.

Issue #2: If you are trying to run "ABServer.exe -SyncNow" on an OCS 2007 R2 server running on Server 2008 R2, you will need to create a new DWORD registry entry at HKLM\SYSTEM\CurrentControlSet\Control\Lsa\DisableLoopbackCheck set to the value of 1.

Due to .NET 3.5 SP1 on Server 2008 R2, if this registry value is not set, you will receive an error message of "Triggering Address Book Server synchronization pass - function not available when RTCSRV service is not running. Start the RTCSRV service." A reboot may be required for the new registry setting to take effect.

Usually, manual regeneration of the address book is not required since the front end will refresh the contents every night by default. It is only the manual run of ABServer.exe that is affected on Server 2008 R2. It is normally best to leave DisableLoopbackCheck disabled (set to 0) if possible for security reasons.

Thankfully, OCS seems to perform very well on Server 2008 R2 once the known issues are worked around.

Microsoft keeps an updated KB article about these issues, which do not have these documented yet, here.

I also have my original guidance for OCS 2007 R2 on Server 2008 R2 here. I will work on getting these incorporated into the original post when I have a free moment.

Posted by Aaron Tiensivu in Microsoft, OCS / LCS, Server, Windows OS at 20:17 | Comments (4) | Trackback (1)

8221 hits

Trackbacks

Trackback specific URI for this entry

Windows 2008 R2 support for OCS 2007 R2 - guidance
It turns out that a little while ago I had discovered part of the puzzle to getting OCS 2007 R2 working on Windows 2008 R2. Strangely, a somewhat related blog entry I made around the same time was the other piece of the puzzle. Namely, for 2008 R2 sup

Weblog: Aaron Tiensivu's Blog
Tracked: Jun 03, 20:26

Comments

Display comments as (Linear | Threaded)

Thanks for ther heads up here, Aaron. Forwarding to Support folks on the NextHop team.

#1 DrRez (Homepage) on 2010-06-04 09:46 (Reply)

Thanks Aaron for the information concerning the RegKey "HKLM\SYSTEM\CurrentControlSet\Control\Lsa\DisableLookbackCheck = 1"

But in my test environment (Windows Server 2008 R2 servers) this doesn't seem to have any effect when using "abserver.exe -syncnow". After adding the RegKey I performed a server restart. Afterwards the named command still stops giving the same error. No address book update occurs.

Did you test the procedure on your own? Tested it with two different OCS server (ENT and STD edition).

Best Regards
Frank

#2 Frank on 2010-06-17 07:45 (Reply)

This did not work for me either!

Still get:

C:\Program Files\Microsoft Office Communications Server 2007 R2\Server\Core>abserver -syncnow
Triggering Address Book Server synchronization pass - function not available when RTCSRV service is not running. Start the RTCSRV service.

even though as you know the Front End Service RTCSRV is running!

#2.1 Magoo on 2010-07-01 18:35 (Reply)

Hi,

th move user problem can be solved by righ tclick on the OCS 2007 R2 Console - properties - shortcut - advanced "Run as administrator".
Afterwards I was able to move users from OCS 2007 to OCS 2007 R2 Server installed on a Windows 2008 R2.

Best Regards
Michael

#3 Michael Schiff (Homepage) on 2010-09-07 09:57 (Reply)

Add Comment

Name
Email
Homepage
In reply to
Comment	E-Mail addresses will not be displayed and will only be used for E-Mail notifications. Standard emoticons like :-) and ;-) are converted to images.
	Remember Information? Subscribe to this entry