Upgrade Path for "OCS 2007" to "OCS 2007 R2"

All replies

• 

  

  0

  Sign in to vote

  I haven't seen a public release of the documentation, but the short version is that you would need to bring up a second pool of R2 servers (64 bit only) and move your users over to it.  It's conceptually similar to an Exchange 2003 -> 2007 migration.

  ---

  Mike Stacy | Evangelyze Communications | http://www.evangelyze.net/cs/blogs/mike

  Friday, January 23, 2009 10:38 PM

  Moderator
• 

  

  0

  Sign in to vote

  Thanks Mike, we are already on x64 servers so I was hoping that we could do an inplace upgrade on those same boxes.

  Saturday, January 24, 2009 5:35 AM
• 

  

  0

  Sign in to vote

  You can migrate up to R2 by rebuilding one box at a time keeping in mind which clients are connecting to which pool. It's very similar to migrating from LCS to OCS where downlevel servers can't support uplevel clients.  To do an in-place upgrade on the same equipment you'd effectively have to wipe the OS and perform a restore on the SQL and AD settings, so best to stand up a new pool and move over to it.  Then flip over the additional roles like Edge, Mediation, Archiving, etc if applicable.

  ---

  Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS

  • Marked as answer by JP-M Sunday, January 25, 2009 12:09 AM

  Saturday, January 24, 2009 7:12 PM

  Moderator
• 

  

  0

  Sign in to vote

  Thanks Jeff, this is what I needed to know.

  Sunday, January 25, 2009 12:10 AM
• 

  

  0

  Sign in to vote

   Hi Jeff,

   You don't think that (if you have duplicated or more environment):

  1. releasing at first one server from the existing pool

  2. move the first group of users to new pool

  3. release next server

  4. etc..
  

  Is valid method to reuse already existing hardware? Of course there might be a problem if rest of the servers in old pool cannot handle the load, but still I wonder should you replace whole amount of HW.

  --

  -Petri-

  Monday, January 26, 2009 8:06 AM
• 

  

  0

  Sign in to vote

  Petri,

  You can definitely do it that way.  I believe you and Jeff are in agreement - you just expanded on the details a bit.  As you mentioned, you certainly want to keep an eye on your overall load if you do this by removing an existing pool server.

  ---

  Mike Stacy | Evangelyze Communications | http://www.evangelyze.net/cs/blogs/mike

  Friday, January 30, 2009 1:10 PM

  Moderator
• 

  

  1

  Sign in to vote

   Hope it Helps¡

  Greets

  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

  • Proposed as answer by aimperialg Tuesday, February 3, 2009 9:17 PM

  Friday, January 30, 2009 4:54 PM