Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Need help with creating topology RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I've downloaded the OCS 2007 Planning Kit, but I'm not sure I agree with the topology.  Basically we are trying to figure out what we will need server-wise to complete the first phases of OCS 2007 R2 implementation. 

    Our current configuration is that of one virtualized LCS 2005 SP1 Enterprise Edition server that supports internal IM, Presence and Desktop Sharing on three SQL back-end database (RTC, RTConfig and RTCArchive). 

    We want to implement the following capabilities next year:  OCS 2007 R2 Enterprise for internal IM and Presence; Application/Desktop Sharing; Group Chat; Teleconferencing and Voicemail.  I understand that we will need to be up to Exchange 2007 for the voicemail capabilities.  I also understand the requirements for OCS 2007 R2 and Group Chat need to be on Windows Server 2008 and 64-bit.  I also see that we can virtualize OCS and Group Chat servers for this implementation. 

    What I'm not sure about is what other servers we will need to accomplish this task.  We only have about 1800 users (only about half are active on LCS today).  According to the OCS Planning Kit, we need 1-OCS Server,  1 - CWA Server, 1 - Archiving Server, 1 - Group Chat Server, 1-Consollidated Edge Server, 1-Reverse Proxy, 2-Enterprise Edition Directors.  Really??? 

    Do I really need all of these servers, and if so, what can be virtualized?  Please let me know if I need to provide more info.  Thanks in advance for your help!
    Monday, October 19, 2009 6:03 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    For an 1800 user deployment and the desire to virtualize some of the components, this is a more realistic approach:

    1 Physical Enterprise Edition Server
    1 Physical Back-End SQL Server (can be an existing SQL 2005/2008 production server with a new SQL instance installed on it)
    1 Physical Consolidated Edge Server
    1 Physical HyperV/Vmware Virtual Server running 2 virtual guests: (a) Archiving + Communicator Web Access, (b) Group Chat Server.

    You can install the Group Chat and Archiving databases into the same back-end SQL instance that was configured for the EE pool databases.  And if you don't already have an ISA Server to use for the reverse proxy you can virtualize that role in a 3 VM guest as well; although it ideally should be (virtually hosted) on a physical server in a perimeter network and not the same physical server as used internally.

    Just make sure that you don't attempt to install the OCS databases in the same SQL instance that LCS is currently in; the database names will conflict.  You MUST a new SQL instance, and I'd recommend to leave that dedicated to all the OCS dbs (pool, Archiving, Group Chat, etc).

    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    • Marked as answer by bridog Tuesday, October 20, 2009 11:51 AM
    • Unmarked as answer by bridog Tuesday, October 20, 2009 12:39 PM
    • Proposed as answer by Gavin-ZhangModerator Monday, October 26, 2009 10:34 AM
    • Marked as answer by Gavin-ZhangModerator Friday, October 30, 2009 9:57 AM
    Monday, October 19, 2009 6:20 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Correct, you don't need the Edge or Reverse Proxy if you don't need external access or federation.  In order to integrate Exchange UM and OCS you do not require a Mediation server connected to any telephony system, if you only need to use VM for internal user communication.  If you want outside PSTN callers to be able to leave messages in those voicemail boxes then some telephony integration is then needed.

    The Mediation Server is not supported virtualized, although it can technically run and I've done it before.  Usually just in proof-of-concept labs but some very small-scale deployments can run the Mediation Server in a virtual, but it's not recommended.

    AD 2003 is fine for using OCS R2, you only need to have the functional levels raised above Server 2000 for R2 deployment.  No Server 2008 hosts or domain controllers are required.
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Tuesday, October 20, 2009 1:30 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    For an 1800 user deployment and the desire to virtualize some of the components, this is a more realistic approach:

    1 Physical Enterprise Edition Server
    1 Physical Back-End SQL Server (can be an existing SQL 2005/2008 production server with a new SQL instance installed on it)
    1 Physical Consolidated Edge Server
    1 Physical HyperV/Vmware Virtual Server running 2 virtual guests: (a) Archiving + Communicator Web Access, (b) Group Chat Server.

    You can install the Group Chat and Archiving databases into the same back-end SQL instance that was configured for the EE pool databases.  And if you don't already have an ISA Server to use for the reverse proxy you can virtualize that role in a 3 VM guest as well; although it ideally should be (virtually hosted) on a physical server in a perimeter network and not the same physical server as used internally.

    Just make sure that you don't attempt to install the OCS databases in the same SQL instance that LCS is currently in; the database names will conflict.  You MUST a new SQL instance, and I'd recommend to leave that dedicated to all the OCS dbs (pool, Archiving, Group Chat, etc).

    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    • Marked as answer by bridog Tuesday, October 20, 2009 11:51 AM
    • Unmarked as answer by bridog Tuesday, October 20, 2009 12:39 PM
    • Proposed as answer by Gavin-ZhangModerator Monday, October 26, 2009 10:34 AM
    • Marked as answer by Gavin-ZhangModerator Friday, October 30, 2009 9:57 AM
    Monday, October 19, 2009 6:20 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks Jeff!  That is what I was hoping!  Now to draw it all out!  :-) 
    Monday, October 19, 2009 6:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    What about Active Directory?  I assume we will need to upgrade this for Exchange 2007 UM for voicemail?  What about teleconferencing?  We are currently running AD 2003...
    Monday, October 19, 2009 6:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I apologize for asking additional questions, please let me know if I should create a new thread.  So I drew this all up and I have one more piece that I am unsure about.  First, we are not planning to open this up to external users at this time, so it will be for internal use only.  Therefore we will not need the Consolidated Edge Server, reverse proxy or CWA, right?  What we do want, however, is within Exchange 2007 UM, is internal users to be able to schedule a conference call and to check voicemail through Outlook.  From what I can see we will need a Mediation Server and possibly a media gateway to our existing PBX.  Does this sound right?  Can the Mediation Server be virtualized?  Can we do all of this on our existing Active Directory 2003 infrastructure, or will that need to be upgraded too?  This really can get confusing when all you need is a subset of the R2 features.  Thanks again for your help!
    Tuesday, October 20, 2009 12:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Correct, you don't need the Edge or Reverse Proxy if you don't need external access or federation.  In order to integrate Exchange UM and OCS you do not require a Mediation server connected to any telephony system, if you only need to use VM for internal user communication.  If you want outside PSTN callers to be able to leave messages in those voicemail boxes then some telephony integration is then needed.

    The Mediation Server is not supported virtualized, although it can technically run and I've done it before.  Usually just in proof-of-concept labs but some very small-scale deployments can run the Mediation Server in a virtual, but it's not recommended.

    AD 2003 is fine for using OCS R2, you only need to have the functional levels raised above Server 2000 for R2 deployment.  No Server 2008 hosts or domain controllers are required.
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Tuesday, October 20, 2009 1:30 PM
    Moderator