See Also
Following are coexistence concerns that affect how you plan your Office Communications Server 2007 R2 migration and deployment:
- The enhanced presence is a user attribute, not a client
attribute. Users who are enabled for enhanced presence and log on
with the Office Communicator 2007 R2 client will no longer be able
to log on with an Office Communicator 2005 client, use the
Communicator Web Access (2005 release) or Office Communicator
Mobile (2005 release).
- During a side-by-side migration, coexistence between Office
Communications Server 2007 R2 and Live Communications Server is
possible. Office Communications Server 2007 R2 Edge Servers can
communicate with Live Communications Server.
- Some limitations exist for coexistence. If you are using the
Director role, Edge Servers running Office Communications Server
2007 R2 must have Office Communications Server 2007 R2 Director. As
your migration moves forward, Office Communications Server 2007 R2
Edge Server will support the Live Communications Server pool. Live
Communications Server Directors and Access Proxy will not support
the Office Communications Server pool.
- The back-end database schema has changed with Office
Communications Server 2007 R2. As a result, a new SQL Server
instance is required for an Office Communications Server 2007 R2
Enterprise pool. An existing back-end server with SQL Server 2005
with Service Pack 2 can host an Office Communications Server 2007
R2 Back-End Database, but there might be performance limitations
for a collocated back-end.
- Archiving is not compatible between versions. For those
deployments that require archiving, you should deploy Office
Communications Server 2007 R2 Archiving Server before moving and
activating users on the new Office Communications Server 2007 R2
pool(s).