[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1129
  • Last Modified:

OCS 2007 R2 and Lync 2013 coexist

Looking for a workable solution for creating a temporary SIP domain for OCS and Lync to coexist. I cannot find good information on step-by-step process.
0
Group_007
Asked:
Group_007
  • 2
  • 2
1 Solution
 
Jakob DigranesSenior ConsultantCommented:
you won't need a separate SIP-domain for these to coexist.
0
 
Group_007Author Commented:
I am needing to add a Lync Edge server. Right now everything is going through the OCS Edge. I have specific external IP's that are NATing my OCS services. Because I cannot NAT the same SIP domain to 2 separate external IP addresses; how will your comment work? Can you elaborate on your thought a little more please.

Also, I am not interested in doing a rip and replace method as this is not ideal for our situation.
0
 
Jakob DigranesSenior ConsultantCommented:
The easiest way is to do a switchover to Lync Edge. OCS clients can log into OCS using Lync Edge and Lync clients can log in using Lync Edge.

So with the Lync Edge - it can serve both OCS and Lync Clients. . Here's how, this also goes for internal clients.

Before all starts, browse this doc; http://technet.microsoft.com/en-us/library/gg413057%28v=ocs.14%29.aspx  (Lync2010) or http://technet.microsoft.com/en-us/library/jj205375.aspx (Lync 2013)

#1: Make sure all OCS Communicator software is updated to latest patch, and OCS servers are updated:
http://technet.microsoft.com/en-us/office/dn788954.aspx 
#2: Install Lync front end and in Topology Builder in 2013, choose merge topology (http://technet.microsoft.com/en-us/library/jj205044.aspx)
#3: Change Service records and internal DNS to point to Lync server. _sipinternaltls._tcp.domain.com -> Lync server
This works so that ALL clients connect to Lync server, and Lync server is responsible for moving legacy clients to OCS2007 automatically and seamless.
#4: When all internal clients log in and everything is OK - deploy Lync Edge with the same public and internal IP-addresses as OCS Edge, if this is a Virtualized Environment you can disconnect NICs in VMWare and configure IP-addresses and everything ready.
#5: switch firewall config to point to Lync Edge and change topology to use Lync Edge rather than OCS Edge:
http://technet.microsoft.com/en-us/library/jj721925.aspx 
#6: Remember to switchover TMG/Reverse Proxy config aswell
#7: Happy days, this works like a charm and you can start moving users to Lync :-)

You cannot create a separate sip domain. without creating a sub-domain for new infrastructure. As long as they're in the same domain - OCS and Lync needs to be merged.  (more or less)
If you MUST keep these separate:

* Install new Lync servers
* assign internal Certs
* reserve 4 additional public IP-addresses for Lync infrastructure
* register new public DNS for sip. av. conf. meet. dialin. lync.
* when moving users you need to backup contact list, remove OCS attributes for users, add to Lync - restore contacts
- as you see, this would add several extra caveats for failure
0
 
Group_007Author Commented:
Excellent! Thank you so much!
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now