locked
OCS 2007 and OCS 2007 R2 communication RRS feed

  • Question

  • Hi everyone,

    I have a OCS 2007 enviroment with 3 servers:
    1.- OCS 2007 Edge server, for im, conferencing anda audio/video
    2.- OCS 2007 Mediation server
    3.- OCS 2007 standard conferencing server, a/v server, IM server
    all of them in the same siteA and domain, domain.com

    Now i installed a OCS 2007 R2 for IM and conferencing, in the same domain.com but a diferent site, siteB. The reason of that is because i initiate a proces of migration but the 64 bit servers where available in the siteB.

    The steps that i follow where:
    Prepare the domain for OCS 2007 R2.
    instaled OCS 2007 R2 enterprise, pool.
    configure the dns for the the pool.domain.com
    configure certificates and activate the services
    all the services started normally except QoE

    Then i dconfigure de OCS 2007 std as a Director.
    http://technet.microsoft.com/en-us/library/bb870341.aspx
    The users in each site can sign in automatically

    The problem is that I can´t make the users of the OCS 2007 R2 and OCS 2007, communicate each other.
    In the communicator 2007 or 2007 R2, the status of the other server users appear "presence unknown".

    I already installed the coexistence patches.
    http://technet.microsoft.com/en-us/library/dd425356(office.13).aspx

    so there is something that i missed?

    thanks for your help,




    • Changed type Gavin-Zhang Wednesday, March 17, 2010 5:36 AM
    Monday, March 15, 2010 7:04 AM

Answers

  • The problem is, you have no pool that can support users.  You have an edge server, a mediation server, and a director.

    The Director is a Standard Edition server or Enterprise pool that does not home any users, but instead serves as the recommended internal next-hop server to which an Edge Server routes inbound Session Initiation Protocol (SIP) traffic destined to internal servers.

    In your deployment you should have deployed a standard edition pool server.  I would deactivate your director and follow the instructions in the following link or login to the director and activate the missing and required roles.

    http://technet.microsoft.com/en-us/library/dd441141(office.13).aspx


    Unified Communications Consultant
    • Proposed as answer by Aaron Tiensivu Tuesday, March 23, 2010 1:03 AM
    • Marked as answer by Gavin-Zhang Monday, March 29, 2010 2:49 AM
    Monday, March 22, 2010 6:38 PM

All replies

  • By the way, i can not move the users from the OCS 2007 std to the OCS 2007 R2 ent. I get a message that ask me to check the log, but i cannot find it.
    Monday, March 15, 2010 7:11 AM
  • Check the below link for more information:

    http://technet.microsoft.com/en-us/library/dd425356(office.13).aspx

    Coexistence Restrictions

    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 pool. An existing Back-End Database 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.

    Office Communications Server 2007 R2 Administrative Tools cannot be used to manage Office Communications Server 2007 servers. Install Office Communications Server 2007 Administrative Tools to manage Office Communications Server 2007 components during migration.

    Office Communications Server 2007 R2 Archiving Server cannot interoperate with Office Communications Server 2007 components, and Office Communications Server 2007 Archiving Server cannot interoperate with Office Communications Server 2007 R2 components. The Archiving Server version must match the version of the pool.

    Office Communications Server 2007 R2 Mediation Servers and clients homed on Office Communications Server 2007 R2 cannot interoperate with the Office Communications Server 2007 QoE Monitoring Server. Office Communications Server 2007 pools also cannot interoperate with Office Communications Server 2007 R2 Monitoring Server. However, if both an Office Communications Server 2007 R2 pool and an Office Communications Server 2007 R2 Monitoring Server are installed, Office Communications Server 2007 Mediation Server can interoperate with them (that is, it can successfully send QoE reports that are captured by the Office Communications Server 2007 R2 Monitoring Server).

    Outside Voice Control requires Office Communications Server 2007 R2 Mediation Server. In side-by-side phased migrations, do not enable Outside Voice Control until all Mediation Servers are upgraded to Office Communications Server 2007 R2.

    Office Communications Server 2007 R2 Edge Servers cannot communicate with Office Communications Server 2007 Enterprise pools or Standard Edition servers because migration from Office Communications Server 2007 must be inside-out. However, Office Communications Server 2007 R2 Edge Servers and Directors can communicate with Live Communications Server 2005 with SP1 Enterprise pools or Standard Edition servers, thus supporting an outside-in migration path from Live Communications Server 2005 SP1.

    Applications that use the Live Communications Server 2005 application programming interface (API) are not supported.

    If you have built, or plan to build, applications that use the UC AJAX API for Office Communications Server 2007 but also plan to deploy Office Communications Server 2007 R2, you must have Communicator Web Access (2007 release) deployed successfully before you run the Active Directory preparation steps for Office Communications Server 2007 R2. You can either keep an existing version of Communicator Web Access (2007 release), or you can deploy a new version of Communicator Web Access (2007 release) before you run the Active Directory preparation steps for Office Communications Server 2007 R2. For details, see the migration documentation in the Office Communications Server 2007 R2 TechNet Library at the Microsoft Web site: http://go.microsoft.com/fwlink/?LinkID=132106.

    Users using Office Communicator 2007 R2 cannot be homed on a Communications Server 2007 or a Live Communications Server 2005 with SP1 Enterprise pool or Standard Edition server.

    Updates Required for Coexistence Scenarios

    Some product updates are required to support coexistence between certain earlier components and Office Communications Server 2007 R2 during migration. The following updates are required:

    • For Office Communicator 2007 to coexist with Office Communications Server 2007 R2, you need to apply the latest update rollup package for Office Communicator 2007. The rollup package is provided in the Microsoft Knowledge Base article 957465. For details, see Knowledge Base article 957465, "Description of the Communicator 2007 hotfix rollup package: December 19, 2008," at http://go.microsoft.com/fwlink/?LinkId=139874.
    • For Mediation Server 2007 to coexist with Office Communications Server 2007 R2, you need to apply the update provided in the Microsoft Knowledge Base article 956829. For details, see Knowledge Base article 956829, "Description of the update package for Communications Server 2007 Mediation Server October, 2008," at http://go.microsoft.com/fwlink/?LinkId=139876. In addition, you need a script to associate Mediation Server 2007 with Office Communications Server 2007 R2 to send QoE reports. For details, see “Associate Office Communications Server 2007 or Office Communications Server 2007 R2 Mediation Server with Office Communications Server 2007 R2 Pool” at http://go.microsoft.com/fwlink/?LinkId=144354.
    • For Office Communications Server 2007 to coexist with Office Communications Server 2007 R2, you need to apply the update provided in the Microsoft Knowledge Base article 956389. For details, see Knowledge Base article 956389, "Description of the update package for Communications Server 2007: November 2008," at http://go.microsoft.com/fwlink/?LinkId=137299.
    • For Office Communicator 2005 to coexist with Office Communications Server 2007 R2, you need to apply the latest update rollup package for Office Communicator 2005. The rollup package is provided in the Microsoft Knowledge Base article 949280. For details, see Knowledge Base article 949280, "Description of the Communicator 2005 hotfix rollup package: December 19, 2008," at http://go.microsoft.com/fwlink/?LinkId=139875.

    Tek-Nerd
    Monday, March 15, 2010 12:59 PM
  • Would you please implement migration step by step refers to below link. And record the errors then post it up here. Which step does this error occur?
    http://technet.microsoft.com/en-us/library/dd572505(office.13).aspx


    Best Regards!
    Tuesday, March 16, 2010 7:21 AM
  • Would you please check if the configurations of certificates, DNS SRV record and ports are correct ?
    Friday, March 19, 2010 8:26 AM
  • Would you please enable logs on the server ,and put all warning and errors up here for us to narrow down the issue.

    And validate the server check the errors.

    Then check if the configurations of certificates, DNS SRV record and ports settings are correct.

    After all, If your are working on LAB testing ,I would suggest you rebuild them and create pure 64-bit environment for further testing. 

    BTW,OCS 2007 R2 supports multiple SIP domains across forest but not support multiple pools,The pool definition as "A combination of one or more Front-End Servers and a Back-End Database that is hosted either on the Front-End Server (Standard Edition) or on one or more Back-End Database servers (Enterprise Edition)."

    Good Luck ! Waiting your feed back.


    Best Regards!
    Monday, March 22, 2010 10:12 AM
  • The problem is, you have no pool that can support users.  You have an edge server, a mediation server, and a director.

    The Director is a Standard Edition server or Enterprise pool that does not home any users, but instead serves as the recommended internal next-hop server to which an Edge Server routes inbound Session Initiation Protocol (SIP) traffic destined to internal servers.

    In your deployment you should have deployed a standard edition pool server.  I would deactivate your director and follow the instructions in the following link or login to the director and activate the missing and required roles.

    http://technet.microsoft.com/en-us/library/dd441141(office.13).aspx


    Unified Communications Consultant
    • Proposed as answer by Aaron Tiensivu Tuesday, March 23, 2010 1:03 AM
    • Marked as answer by Gavin-Zhang Monday, March 29, 2010 2:49 AM
    Monday, March 22, 2010 6:38 PM