I have a issue with my upgrade from OCS 2007 R2 to Lync 2010. As the title says, the OCS server is using the same FQDN for the Pool, Web Conferncing, and Front Edge server. I run into the problem when I am running the Merge 2007 or 2007 R2 toplogy wizard and trying to add the OCS server. It gives me a red X stating that it can not use the same FQDN as the Edge Pool internal FQDN. Any ideas?

Jeff, first of all an in-place upgrade from OCS to Lync 2010 isn't possible, it's always required a side by side migration.

When you are referring to the FQDN are referring to the Pool FQDN or Lync Web Services FQDN? 

I don't understand what do you meant by that "It gives me a red X stating that it can not use the same FQDN as the Edge Pool internal FQDN". If possible give us a better description from your environment.

JC

It's just good practice to not re-use FQDNs.  Build new Lync servers with new pool names and FQDNs and move people over, you won't have to touch the clients for this as they'll all use autodiscover to find the servers anyhow.  I'm not sure I understand the question, but if I do, the answer is to simply use different FQDNs.

Hey JC,

Let me try to explain this a bit better. We have deployed a Pilot Pool with Lync 2010. It is running currently, however, according to the OCS 2007 R2 to Lync 2010 migration guide (Can't link to it, but it is on technet) There is a step using the Lync 2010 Topology builder to connec the Pilot Pool to Legacy Edge Servers. This is where I am getting stuck. When I run the Merge 2007 or 2007 R2 in the Topology builder, it asks me to add the Legacy Edge servers by FQDN. When I try this, with the legacy (OCS 2007 R2) I cannot use the same FQDN for Edge Pool, Web Conferencing, and Front-End in this wizard.

Thank you,

Jeff Hickman

Out of curiosity, how many users are we talking about?  And what functionality was employed with OCS that needs to be migrated?

Hello Anthony,

We are talking about a small amount of users (50). We are really only using it for IM at this point.

I have an idea of where you are headed with that question, should we just scrap merging typologies and just migrate the users to Lync 2010? As I understand it, they can still use the OCS 2007 R2 client (as long as the policy allows it) to connect to the Lync 2010 pool. Then deploy the Lync client at our leisure. It will be what we do if we cannot find a solution to this issue.

I'm not sure how you built the OCS 2007 R2 topology with the same name on two servers....I guess its because the Edge server was not in the domain....

Anyway what I would do if i were you would be to run the merge and don't enter the Edge server details at all. This will go ahead and merge and then you can build your new Edge server on 2010 and associate this server in the Topology Builder, you can see this step here: http://technet.microsoft.com/en-us/library/gg398731(v=ocs.14).aspx

Hello Anthony,

We are talking about a small amount of users (50). We are really only using it for IM at this point.

I have an idea of where you are headed with that question, should we just scrap merging typologies and just migrate the users to Lync 2010? As I understand it, they can still use the OCS 2007 R2 client (as long as the policy allows it) to connect to the Lync 2010 pool. Then deploy the Lync client at our leisure. It will be what we do if we cannot find a solution to this issue.

You're right where I was headed.  I was thinking if it's a small deployment and really only for IM, just use DBIMPEXP to grab everyone's contact lists and start from scratch, forget the topology merge if it's looking like too much trouble.  Yes you can use OCS R2 with Lync 2010 to an extent, since it's just IM that should be no problem.  Livemeeting/Lync conferencing are a bit different though, so I'd get those clients updated when you can.

Hello Martin,

Maybe I am completely lost, but the OCS 2007 R2 is installed as a stand-alone server, so there is no edge specific server it is all-in-one. The same topology will be in place for the Lync server. Thank you for the link, I will review it and get back to you.

you don't have an edge server so!!!

An edge server is a separate server on the DMZ network for external access. So as i suggested leave the edge blank and click next in merge! :)

In Lync, if you want external remote access, federation or public meetings you will need a separate Edge server.

Thank you both Martin and Anthony for clearing that up for me! I was getting a bit confused with some of the changes in terminologies from OCS to Lync. Thank you again!

no problem, good luck with your Lync 2010 

One other quick question if you have a moment! When I am trying to Authorize Connection to OCS 2007 R2 from Lync, I don't have the Internal tab when I right click the Office Communicator 2007 R2 object in the Computer Management MMC snap-in on the OCS server. Here is a screen shot to demonstrate:

Any idea how I can authorize connection to the OCS from Lync?

im not sure what you mean here, but you dont need to authorise lync server on OCS.

See this link here for steps: http://technet.microsoft.com/en-us/library/gg413057(v=ocs.14).aspx

Make sure you don't skip any in the link above and you will have them merged pretty quick.

Phase 5, step 2: Authorize Connection to Office Communications Server 2007 R2 Edge Server

Do I not need to do this because we are not using A/V?