locked
R2 migration... RRS feed

  • Question

  • I have an 07 standard deployment with an edge server.  Only using IM and Livemeeting (no voice except between OC clients).  Im looking to migrate to R2 and have one question since the deployment guides are just not available yet.

    It's going to take a month or two to migrate and I am wondering if I can leave the edge on 07 while having both 07 and R2 running or does the edge need to go to R2 right away?

     

    Thanks.

    Tuesday, January 27, 2009 5:51 PM

All replies

  • Hi

    Based on R2 documentation, the migration path is to install R2 pool in your R1 environment before upgrading Edge. So R1 and R2 pool will use R1 Edge.

    Wednesday, January 28, 2009 9:01 AM
  •  Yes you can leave the Edge role(s) in R1 mode while supporting both R1 and R2 pools but keep in mind that many of the R2 features will have limited functionality depending on where the clients are connecting from.
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Wednesday, January 28, 2009 1:14 PM
    Moderator
  • Jeff and nkv,

      Thanks for the reply.  I will proceed with an R2 server install and leave the edge as is.

     

    nkv,

      You mention documentation.  I have not been able to find anything online yet.  Are you talking pre-release stuff?  Is it available anywhere?  I've done a couple of test installs already and R2 (at least for IM and Livemeeting) seems pretty straight forward.  It would be nice to have a doc to read first just in case I am missing something though.

     

    Thanks again...

    Wednesday, January 28, 2009 2:41 PM
  • There is no document other than few blogs mentioning about what's new in OCS R2. Wait for couple of days to get the R2 Doucmentation.
    Jithendranath Reddy
    Thursday, January 29, 2009 9:42 AM
  •  Here´s some info about R2 , i´ve already posted in another question , but i can´t resist temptation to share , je je je je.

    This is official info by MS.

     

    1.1         Supported Migration Paths and Coexistence Scenarios

     

    Migration of OCS 2007 Standard Edition, Enterprise Edition in a consolidated configuration, and Enterprise Edition in an expanded configuration, either with or without edge servers, is supported.  Migrations can be approached in a phased fashion, starting with the internal network and moving to the perimeter network.  These migrations must be completed starting with internal servers and moving out to the Edge server. 

    The following two migration methods are supported:

    ¾  Side-by-side migration

    In side-by-side migration, a new Office Communications Server 2007 R2 configuration is built alongside the Office Communications Server 2007 configuration. After the new configuration is fully validated, users are moved from the original configuration to the new configuration. This method requires additional servers during the migration, and system names and pool names are different in the new configuration. During this type of migration, service outage is brief or nonexistent.

    ¾  Uninstall / reinstall

    This type of migration is similar to a disaster recovery. All user and configuration data is exported and stored in a backup location. Office Communications Server 2007 is uninstalled, and Office Communications Server 2007 R2 is installed on the same computer, and then all user and configuration data is restored. This migration method does not required additional servers, and the system name and pool name remain the same. During this type of migration, service outage is expected to be longer. This method requires an operating system upgrade from 32-bit to 64-bit.

     

    Supported Migration Scenarios

    Starting Topology

    Target Topology

    Migration Method

    Enterprise Edition, expanded

    Enterprise Edition, consolidated

    ·         Side-by-side migration, from internal network to perimeter network

    ·         Uninstall/reinstall

    Enterprise Edition, consolidated

    Enterprise Edition, consolidated

    ·         Side-by-side migration, from internal network to perimeter network

    ·         Uninstall/reinstall

    Enterprise Edition, expanded

    Enterprise Edition, expanded

    ·         Side-by-side migration, from internal network to perimeter network

    ·         Uninstall/reinstall

    Enterprise Edition, consolidated

    Enterprise Edition, expanded

    ·         Side-by-side migration, from internal network to perimeter network

    Standard Edition

    Standard Edition

    ·         Side-by-side migration, from internal network to perimeter network

    Standard Edition

    Enterprise Edition, consolidated

    ·         Side-by-side migration, from internal network to perimeter network


    The coexistence scenarios described in this section support phased side-by-side migrations. Any coexistence scenario not included in this section is not supported.

    Coexistence Scenarios

    This Communications Server 2007 R2 component

    Can communicate with this Communications Server 2007 / Live Communications Server 2005 component

    Enterprise Edition pool or Standard Edition server

    Director Server

    Edge Server

    Communicator Web Access

    Mediation Server

    Office Communicator 2007

    Office Communicator 2005

    Office Live Meeting 2007

    Mediation Server

    Enterprise Edition pool or Standard Edition server

    Monitoring Server

    Mediation Server
    Clients homed on Enterprise pool or Standard Edition server

    Director Server

    Edge server

    Enterprise Edition or Standard Edition pool server

    A/V Edge Server

    Office Communicator 2007 R2

    A/V Edge Server

    (only for conferences initiated by an A/V Conferencing Server)

    Enterprise Edition or Standard Edition pool server

    Microsoft Office Communicator Web Access (2007 Release)

    Enterprise Edition or Standard Edition pool server

    Mediation Server

    Exchange UM

    Enterprise Edition pool or Standard Edition server

    Enterprise Edition or Standard Edition pool server

    Office Communicator 2007

     

    Coexistence Restrictions:

    ¾  Office Communications Server 2007 R2 Edge servers cannot communicate with Office Communications Server 2007 servers. 

    ¾  The back-end database schema has changed with Office Communications Server 2007 R2, so a new SQL Server instance is required for an Office Communications Server 2007 R2 Enterprise Edition pool. An existing back-end server with the required level of SQL Server 2005 can host an Office Communications Server 2007 R2 Back-End database, but there might be performance limitations for a collocated back-end.

    ¾  Call Control Server (CCS) requires Office Communications Server 2007 R2 Mediation Server. In side-by-side phased migrations, CCS is disabled until Mediation Server is upgraded to Office Communications Server 2007 R2.

    ¾  The following Office Communications Server 2007 R2 components must be upgraded when the pool is upgraded.

    ¡  Archiving and CDR Server must be upgraded to Archiving Server

    ¡  Quality of Experience Monitoring Server (QoE) must be upgraded to Monitoring Server

    ¡  Administrative Tools


    Amado Imperial
    Friday, January 30, 2009 5:23 PM
  • Hi

    If you got the R2 binaries from Connect MS site, you can also download the documentation there.
    Saturday, January 31, 2009 9:49 AM