Before upgrading our Office Communications Server 2007 (OCS) install to OCS R2, we pushed out the Office Communicator 2007 R2 client to our desktops. As with most software pushes, not everyone received the client successfully. Currently, there are four versions of the Communicator client connected to our R2 server:
UCCAPI/2.0.6362.15
UCCAPI/3.5.6907.0 OC/3.5.6907.0 (Microsoft Office Communicator 2007 R2)
UCCAPI/3.5.6907.9 OC/3.5.6907.9 (Microsoft Office Communicator 2007 R2)
UCCP/2.0.6362.0 OC/2.0.6362.0 (Microsoft Office Communicator)
The only one I couldn’t really figure out was the first one (2.0.6362.15). That client version only has one connection to the server. After looking at the rtc (dbo.Resource table) and rtcdyn (dbo.Endpoint table) databases, I discovered that it is the ForeFront for OCS Proxy account using this client.
The second in the list is the R2 Communicator 2007 client (UCCAPI/3.5.6907.0 OC/3.5.6907.0), without the April 2009 patch (KB 967673).
The third (UCCAPI/3.5.6907.9 OC/3.5.6907.9) is the R2 Communicator 2007 client with the April 2009 patch.
The fourth (UCCP/2.0.6362.0 OC/2.0.6362.0) is the R1 Communicator 2007 client (caused by the R2 client install failures).
[UPDATE] The May 2009 Communicator 2007 R2 hotfix rollup update upgrades clients to the following: UCCAPI/3.5.6907.9 OC/3.5.6907.22 (Microsoft Office Communicator 2007 R2)