This article describes the supportability for the Microsoft Office Communications Server 2007 R2
member server role on a server that has a Windows Server 2008 R2 operating
system installed. However,
the following scenarios are currently not supported
on a Windows Server 2008 R2 operating system:
- Upgrading the operating system to Windows Server 2008 R2 for an existing installation of Office Communications Server 2007 R2 is not supported.
- Office Communications Server 2007 R2 administration tools will only install in native 32-bit or native 64-bit mode. Because of an application compatibility issue with Windows Server 2008 R2, installing 32-bit Office Communications Server 2007 R2 administration tools on 64-bit Windows 2008 R2 operating system is not supported.
- Development with Speech Server (2007) Developer Edition and deployment of the Speech Server 2007 role are not supported on Windows Server 2008 R2.
Take
the following steps to install Office Communications Server 2007 R2 on a server
that is running a Windows Server 2008 R2 operating system:
- Install.NET Framework 3.5.1 by using Roles wizard from
Server Manager. You can do this by selecting the Windows-based application server
role to make sure completeness. This is a manual step. You must have
.NET Framework 3.5 SP1 on a Windows Server 2008 R2 operating system before you
install a version of Office Communications Server 2007 R2 that only includes
.NET Framework 3.5.
- Install the Desktop Experience Features by using Add
Features wizard from Server Manager. This is required for Media format runtime.
The name of the media format runtime package depends on the operating system
and the Office Communications Server 2007 R2 setup that refers to the Windows
Server 2008 or to the Windows Server 2003 Media format runtime installation
package.
- Install the Hotfix that is described in KB 975858 for
Windows Server 2008 R2.
975858
(http://support.microsoft.com/kb/975858/
)
An application or service that
calls the InitializeSecurityContext function together with the
ISC_REQ_EXTENDED_ERROR flag may encounter a TLS/SSL negotiation failure on a
computer that is running Windows Server 2008 R2 or Windows 7 operating system
- Install Office Communications Server 2007 R2 Server
Roles
- For Office Communications Server 2007 R2, Standard Edition,
or Enterprise Edition, or Edge Server role, when KB 974571 is installed,
Activation of the Office Communications Server 2007 R2 server role fails. To
fix this problem, follow these steps:
- Apply the OCSASNFix.exe file. To download the
Ocsasnfix.exe file, visit the following Microsoft Web site:
- Rerun Office Communications Server 2007 R2
Activation
Note This is not specific to Windows Server 2008 R2 operating system.
For more information, visit the following Microsoft Web site: - Install updates for Office Communications Server 2007 R2
that are dated October 2009 (3.5.6907.56), or install later versions. To
download the updates for Office Communications Server 2007 R2, visit the
following Microsoft Web site:
For more information about how to install the Office
Communications Server 2007 R2 updates, click the following article number to
view the article in the Microsoft Knowledge Base: 968802
(http://support.microsoft.com/kb/968802/
)
Updates for Communications Server 2007 R2
- Install updates for Office Communications Server 2007 R2, Group Chat Server, Office Communications Server 2007 R2, Group Chat Admin Tool and Office Communications Server 2007 R2, Group Chat Client that are dated May 2010 (3.5.6907.200), or install later versions.
Note You will experience the issue that is described in Microsoft Knowledge Base article 982129
(http://support.microsoft.com/kb/982129)
if you do not apply the the update that is mentioned in the previous step.
To download the updates for Office Communications Server 2007 R2, Group Chat Server, visit the following Microsoft website:
To download the updates for Office Communications Server 2007 R2 Group Chat Administration Tool, visit the following Microsoft website:
To download the updates for Office Communications Server 2007 R2 Group Chat Client, visit the following Microsoft website:
- The default security setting on Windows Server 2008 R2
operating system for NTLM SSP requires 128-bit encryption. Depending on the
client operating system mix in the enterprise, you may have to reduce this
setting on a Windows Server 2008 R2 operating system that is running Office
Communications Server 2007 R2 as a down level operating system. The key is set
to "No requirement."
- For any down level operating system, such as Windows XP
or for Windows Vista, the default value is set to "No Minimum."
- For a Windows 7 operating system, the default value is
set to "Requires 128-bit encryption."
For more information about the “Changes in NTLM
Authentication” as it applies to Windows 2008 R2 and Windows 7 operating
systems, please visit the following Microsoft Web site:
If you want to change the NTLM setting, follow these steps:
- Start secpol.msc on a Windows Server 2008 R2 operating
system server.
- Click to select Local Policies and then
click Security Options node.
- Make sure that the following values of the policies are
set to "No Minimum."
- Network Security: Minimum session security for NTLM SSP
based (including secure RPC)
- Network Security: Minimum session security for NTLM SSP
based (including secure RPC) servers
For more information about the operating systems that are
currently supported for Office Communications Server 2007 R2, visit the
following Microsoft Web site:
For more information about Office
Communications 2007 R2 running in Windows 2008 R2 Domain and Forest, click the
following article number to view the article in the Microsoft Knowledge Base:
982020
(http://support.microsoft.com/kb/982020/
)
Office Communications Server 2007
R2, Office Communications Server 2007 or Live Communications Server 2005 does
not work correctly after you upgrade a domain controller to Windows Server 2008
R2 operating system
Back to the top
