This issue has come up a couple of times when customers are trying to move legacy users to a Lync Server 2010 pool that is behind a hardware load balancer (HLB). When trying to move the legacy user, Move-CsLegacyUser returns the following error:
Unable to connect to some of the servers in pool "<pool name>" due to a Distributed Component Object Model (DCOM) error. Verify that Front End service is running on servers in this pool. If the pool is set up for load balancing, verify that load balancer is configured correctly.
There are two ways to work around this issue. Both are listed in KB926642 (http://support.microsoft.com/kb/926642). In the steps below for Method 1, pay close attention to Step 6, as this is what you need to change to get things working again:
Method 1 (recommended): Create the Local Security Authority host names that can be referenced in an NTLM authentication request
To do this, follow these steps for all the nodes on the client computer:
Method 2: Disable the authentication loopback check
Re-enable the behavior that exists in Windows Server 2003 by setting the DisableLoopbackCheck registry entry in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa registry subkey to 1. To set the DisableLoopbackCheck registry entry to 1, follow these steps on the client computer:
After making one of the above changes on each Front End Server in the Lync pool and restarting the servers, you should now be able to move users from legacy pools.
Thanks for this post. Helped me to solve the issue!
on which server do we need to make either of these changes, OCS front end servers or Lync FrontEnd servers
You make the changes on the Lync Front End Server(s).
I think this was my issue. I did not “hack” around the registry to fix this. :) I substituted the FQDN for the control panel with the IP address of one of the FE servers, bypassing the HLB, to access the control panel. So I am going to do this for legacy
moves. This post pointed me in the right direction though. Hope this helps someone.