Hello Folks,

We are in the Process of configuration the Hybrid setup for Lync online (AKA Skype For business online), I need information related to Lync 2010 and lync 2013 in regards to Edge servers .

Current Setup :

1 Lync 2010 FE

1 Lync 2010 Edge

1 DB (SQL 2008 R2)

all 3 servers are currently updated with Latest CU.

We want to introduce A New Edge 2013 Edge server so that we can configure the Hybrid from Lync 2013 for better integration with Lync online.

we will be still using the Existing Lync 2010 FE with DB server.

first step we gonna do is to introduce Lync 2013 with Same IP's but (different server Name), point all the configuration to new Lync 2013 Edge server in the Topology builder so that Lync 2010 FE can communicate with New Lync 2013 Edge and we will keep the Old Lync 2010 Edge server down for a week just to be sure everything work as expected.

Once confirm we will configure the Hybrid and start moving the users to Lync online,

Later on we will introduce the Lync 20103 FE and migrate only those users who need the ENT VOICE feature.

I want know if the above migration strategy is good enough for smooth migration and i wants to know If Lync 2010 FE can support new Lync 2013 Edge without any issues.

Note: I am aware we can still configure the hybrid using existing Lync 2010 Edge but i heard some issues with directory search, etc with Lync online and also anyhow we are going to migrate Skyper for business 2015 at end of the project for Lync 2013 FE and Edge by using Inplace upgrade.

eagerly awaiting your expert advice and thanks in advance.

• Edited by Tech_Bug Saturday, August 22, 2015 7:30 PM typo

Hi

it is not supported to install a Lync 2013 Edge server without first introducing Lync 2013 Front End as 2013. You are not going to get any benefit from installing an 13 edge server (even if it is possible) as you'd only be able to take advantage of 2010 features only. If you attempt this and install with same IPs etc, then even if it is possible, there would be an outage, for the simple reason of basic IP rules in that no 2 systems can coexist with the same IP at any one time. Remember doing this would invalidate your Microsoft Support and you'd be on your own.

Ideally what you need to do is install from the inside out - that means FE first, then mediation, then persistent chat, then edge. not the other way around. Even if you do not use your Lync 2013 Fe immediately, you're going to be doing it anyway according to your strategy, so not to follow the supported installation practice is just asking for trouble.

In terms of directory search issues, I believe you are referring to Skype consumer directory search which does not need hybrid connectivity to work as it is a separate service from a public IM provider and not Office 365. In this case directory search (basic) is only available with for users homed on a Lync 2013 FE pool. This would give them access to add Microsoft Live IDs who have a Skype account as contacts. SFB homed users with SfB edges would allow for proper directory search capabilities for Skype consumer accounts with both Live IDs and SkypeIDs as well as searching based on name and location, such as John Doe in Montana for instance.

IMHO, if the end goal is to migrate to SfB, then do this now from 2010 to SfB in one jump rather than try and get to the end goal in an unsupported, highly risky and problematic way. All you are achieving here is to give yourself a headache and double your workload and increase your delivery time. That's my honest opinion anyway.

thanks

I don't think you need to do this at all, you can use a Lync 2010 Edge server with Lync 2010 Front Ends and get the shared sip address space still.  Shared SIP domains weren't supported with the introduction of Lync 2010, however they are now.  All you need is a Lync 2010 deployment and the Lync 2013 Admin Tools installed.  You don't need a Lync 2013 Edge and adding a Lync 2013 Edge with a 2010 Front End will give you no additional functionality whatsoever.  You will however want to make sure your 2010 environment is using the latest CU so your hybrid deployment goes smoothly.

If the model is to go hybrid now, I'd stick with 2010, use the 2013 Admin Tools Management Shell to get a shared sip domain, then as Mark said, go to Skype for Business in one jump directly from 2010 (side by side upgrade).

http://imaucblog.com/archive/2013/05/10/step-by-step-guide-enabling-split-domain-within-office-365-lync-online/