You may have problems installing UcmaRedist.msi (the Microsoft Office Communications Server 2007 R2, Microsoft Unified Communications Managed API 2.0 Core Redist 64-bit) on Windows Server 2008 or 2008 R2. I ran across this myself when installing the Microsoft Office Communications 2007 R2 Web Service Provider for Lync Server 2010.
You receive the following error:
Microsoft Office Communications Server 2007 R2, Microsoft Unified Communications Managed API 2.0 Core Redist 64-bit installation requires Microsoft .NET Framework 3.5. Installation can not continue.
This happens if you have the .NET Framework 4.0 installed. Uninstall both of the .NET Framework 4.0 components in Programs and Features, restart the server, and install UcmaRedist.msi.
The Test-ReplicationHealth cmdlet in Exchange 2007 will show an inaccurate warning for the ClusterNetwork check if your CCR nodes are configured in geographically dispersed clusters.
Exchange 2007 CCR clusters must be located on the same subnet(s) when deployed on Windows 2003 servers. Clustering enhancements in Windows Server 2008 enable you to create clusters in different subnets, negating the need to do networking acrobatics like stretching VLANs across geographic sites. Unfortunately, the Test-ReplicationHealth cmdlet still expects that the network adapters are on the same network and will display the following warning if they are not:
Server Check Result Error
—— —– —— —–
EXNODE1 PassiveNodeUp Passed
EXNODE1 ClusterNetwork WARNING Warnings:
Network ‘EXNODE2 Public’ used for client connectivity is up but node ‘EXNODE1’ does not have a Network Interface Card configured on it. Check that a NIC is configured for this network and is enabled.
Network ‘EXNODE2 Private’ used for internal cluster communications is up; however, node ‘EXNODE1’ does not appear to have a configured network interface card (NIC). Check that a NIC is configured and enabled for this network on this node.
Network ‘EXNODE1 Private’ used for internal cluster communications is up; however, node ‘EXNODE2’ does not appear to have a configured network interface card (NIC). Check that a NIC is configured and enabled for this network on this node.
Network ‘EXNODE1 Public’ used for client connectivity is up but node ‘EXNODE2’ does not have a Network Interface Card configured on it. Check that a NIC is configured for this network and is enabled.
EXNODE1 QuorumGroup Passed
EXNODE1 FileShareQuorum Passed
EXNODE1 CmsGroup Passed
EXNODE1 NodePaused Passed
EXNODE1 DnsRegistrationStatus Passed
EXNODE1 ReplayService Passed
EXNODE1 DBMountedFailover Passed
EXNODE1 SGCopySuspended Passed
EXNODE1 SGCopyFailed Passed
EXNODE1 SGInitializing Passed
EXNODE1 SGCopyQueueLength Passed
EXNODE1 SGReplayQueueLength Passed
VLEM SGReplayQueueLength Passed
This behavior also affects System Center Operations Manager 2007, since SCOM uses the same Test-ReplicationHealth cmdlet to monitor Exchange 2007 replication health. This will cause the CCR nodes to show in a critical condition for the Exchange 2007 Test Replication Health Monitor – Log Shipping monitor.
Microsoft maintains a website on TechNet that contains a comprehensive list of all the hotfixes that pertain to Windows Server 2008 Hyper-V R2 and Windows Server 2008 Hyper-V.
Hyper-V Update List for Windows Server 2008 R2
Hyper-V Update List for Windows Server 2008
Each update includes a description and a link to download the hotfix or patch.
These sites also highlight one of the great features of TechNet – the Community Content area at the bottom of the page where users can annotate TechNet articles. You will see that users have listed other updates that they feel are missing from Microsoft’s lists.