Hi

I did a mistake and have decommissioned OCS systems, when I have forgot to move dial-in access number to LYNC.
The old access number is deprecated, since we use a new number on the LYNC and it works fine.
But, the old number still shows under "find a local number" which is somehow not hygienic.

The Get-CsConferenceDirectory PS lists me the following:

Identity             : 1
ServiceId            : UserServer:LYNC.domain.com
TargetServerIfMoving :
Id                   : 1
Fingerprint          : 4a72adaf-5ded-406b-b226-5015225200b3

Identity             : 3
ServiceId            : BackCompatSite-UserServices-1
TargetServerIfMoving :
Id                   : 3
Fingerprint          :

The Identity 3 is the one to be removed.

Do anyone has any ideas how to resolve this situation?
Thank you in advance

Herbert Knavs

• Edited by Herbert Knavs Thursday, March 31, 2011 7:20 AM Typos corrected

Hi,

Here is the guidance about how to remove BackCompatSite.

http://technet.microsoft.com/en-us/library/gg429693.aspx

Hope this useful to you.

Regards,

Sharon

Hi Sharon

Thank you for your answer, but unfortunatelly this does not help. The Conference Dial-In from retired OCS systems is still in configuration.

Regards,
Bert

Hi,

Which steps have you done till now?

The following link may meet your request.

http://64.4.11.252/en-us/library/gg412782.aspx

Regards,

Sharon

I have tried your suggestions.

The last suggestion does not work since with Get-CsDialInConferencingAccessNumber I get only the one that I have on Lync server (thats the actual one) and not the old one from the OCS.

I believe that I have here orphaned object undel Lync's SQL database.

Those are also the steps I had tried:

Remove-CsConferenceDirectory -Identity 3
Also with the force switch and the result is:

Remove-CsConferenceDirectory : Cannot find a definition for a conference direct
ory home pool with service ID "BackCompatSite-UserServices-1".
At line:1 char:29
+ Remove-CsConferenceDirectory <<<< -Identity 3
    + CategoryInfo : NotSpecified: (:) [Remove-CsConferenceDirectory]
   , ConferenceDirectoryException
    + FullyQualifiedErrorId : Cannot find a definition for a conference direct
   ory home pool with service ID "BackCompatSite-UserServices-1".,Microsoft.R
  tc.Management.ConferenceDirectoryCmdlets.RemoveConferenceDirectoryCmdlet

Move-CsConferenceDirectory -Identity 3 -TargetPool lync.domain.com
Also with the force switch the result is:

Move-CsConferenceDirectory : Cannot find configuration data for the currently a
ssigned service for conference directory with ID "3". The service ID "BackCompa
tSite-UserServices-1" might be invalid.
At line:1 char:27
+ Move-CsConferenceDirectory <<<< -Identity 3 -TargetPool lync.domain.com -
Force
    + CategoryInfo : NotSpecified: (:) [Move-CsConferenceDirectory],
   ConferenceDirectoryException
    + FullyQualifiedErrorId : Cannot find configuration data for the currently
    assigned service for conference directory with ID "3". The service ID "Ba
  ckCompatSite-UserServices-1" might be invalid.,Microsoft.Rtc.Management.Co
 nferenceDirectoryCmdlets.MoveConferenceDirectoryCmdlet

Then I have swept AD for the entry:
The only entry about conferences is under:

CN=Conference Directories,CN=RTC Service,CN=Services,CN=Configuration,DC=domain,DC=com

But the one the is the new one from the Lync system and not from OCS.

Regards
Bert

This worked for me.

Set-CsDialInConferencingAccessNumber –Identity <Existing Dialing Conf> –ScopeToSite

Note: <Existing Dialing Conf> is the “good” entry.

• Proposed as answer by Waite, James A Monday, April 18, 2011 10:01 AM
• Unproposed as answer by Herbert Knavs Monday, April 18, 2011 10:46 AM
• Proposed as answer by DeonSt Thursday, July 19, 2012 4:20 PM

Hi James

The good nuber works and it is a "primary" number.

The problem is that the old number which was in use on OCS, still shows when selecting "find a local number" on the meeting properties.

This number is nowhere in the Lync environment, except as an orphaned object, i believe in SQL.

I don't see how your proposal will remove the orphaened dial-in number?

Can you tell me more?

Yes.  The 'old' OCS dial in number still shows in, find a local number and in meeting requests.

When you run Get-CsDialInConferencingAccessNumber against your Lync server, only the current 'good' dial-in number present, according to your earlier post. 

Is the issue that this number may be in the DB somewhere, and / or that you may have an AD object buried somewhere.  Or that the 'old' / bad number is listed on meeting invitations and provided to attendees as an option for dialing in to conferences? 

Set-CsDialInConferencingAccessNumber –Identity <Existing Dialing Conf> –ScopeToSite

ScopeToSite - If present, the dial-in conferencing number will be scoped to the site where the contact object’s Registrar pool resides.

Meeting invitations and 'Find a local Number'  should then only return your 'good' number for conferences.

Hi James

I am really sorry for late response.

Your advise did the trick, doe still not clean, since the old number is somewhere in the DB, but good enough to resolve the "visible" problem.

Thank you again

I realize I am resurrecting an old thread but I have a similar problem except we never implemented any Enterprise Voice features in OCS.  We have decommissioned OCS but I am unable to remove the old conferencing directories from Lync.  I never saw any guidance on that anywhere such as you really should move the directories to Lync first (unless you were using dial-in conferencing) so I did not think of it.

I've tried using Remove-CsConferenceDirectory -Force but that did nothing.  I just get the same error as noted above.  If they are stuck there forever but will not hurt anything, so be it.  But if they can be removed I would rather just get rid of them.

Thanks.

MacGeever, did you ever get a resolution to this problem? I'm in the same boat and cannot find a solution to getting rid of the old conference. Nothing from the command line works.

Jason

The James Waite gave the only working workaround.

I have made a call to MS for this, but they couldn't help me out here.

The problem is that in the earlier version of migration whitepaper from MS was missing the important notice stated that you need to remove old conferences from OCS.

After my call, they really couldn't help me (the old OCS was already decommissioned)... but they updated whitepaper (after my call). ;)

I think MS should response here with a sollution to remove unexsistant conference.

If you find any sollution to this, please, update with this post.

Bert

Hi,

Which steps have you done till now?

The following link may meet your request.

http://64.4.11.252/en-us/library/gg412782.aspx

 

Regards,

Hi,

I solved it in my case, but I think it is not recommended.

I forgot to delete the number in OCS, too.

I created a new dail in number in Lync (the same number).

I deleted the contact object per adsiedit which is in the following container:

"CN=Application Contacts,CN=RTC Service,CN=Services,CN=Configuration,DC=contoso,DC=com"

After that the new lync number also disappeared (I deleted only the old one).

So I created the number again. Now I see only the new created number and the old one is gone.

If you got a test environment you can try to reproduce it.

No need so complicated;

I resolved the issue by simple;

created a new Lync conference dialin phone # is identical as old OCS phone # that you want to delete.

Wait for awhile, when you see the magic from the dialin web page, the old OCS phone actually gets replaced with new lync conference #, all old OCS information is gone!

Now you can delete it , or do whatever you want...

Problem resolved, no need Powershell or AD search anymore...

• Proposed as answer by supergsm Tuesday, October 23, 2012 8:02 PM
• Edited by supergsm Wednesday, October 24, 2012 9:12 PM

No need so complicated;

I resolved the issue by simple;

created a new Lync conference dialin phone # is identical as old OCS phone # that you want to delete.

Wait for awhile, when you see the magic from the dialin web page, the old OCS phone actually gets replaced with new lync conference #, all old OCS information is gone!

Now you can delete it , or do whatever you want...

Problem resolved, no need Powershell or AD search anymore...

I had the same problem by delete the dialin access number in OCS before run move-CsApplicationEndPoint. The set-csdialinconferencingaccessnumber -scopetosite  methode can only mask the problem for the site, but if you want to see the access number from other sites, you need to use -scopetoglobal parameter, which will display the deleted access number again.  Here is what I did to remove it completely.

1. Open Lync client, tools, Dial-in Conference Settings, find the region for the deleted access number.

2. In Lync Power Shell, run get-CsDialInConferencingAccessNumber -region "Region from step 1", you will see some warning "Cannot find the contact object associated with the entry for line URI "tel:+xxxxxx".

3. Assign the "region from step 1" to a dial-plan in the Lync Control Panel, Voice Routing.

4. Go to Lync Control Panel, Conferencing, Dial-in Access Number, create a new Access Number to match the display Number, Line URI, Primary Language.  The SIP URI can be any unique string.

5. run PS command set-CsDialinConferencingAccessNumber -Identity "sip:xxxxx" -scopetoglobal,  Here identity use the one created in step 4.

6. run the same PS command in step 2, you should not see the same warning as step 2, and will display the info for the access number created in step 5.

7. Delete the Dial Access Number you created in step 4, and run PS command in Step 6 to verify it is deleted. wait for a few minutes, you should not see the dial access number you want to remove from the local access number listing.

• Proposed as answer by Andrew MorpethMVP Thursday, November 07, 2013 10:17 PM
• Marked as answer by Herbert Knavs Friday, November 08, 2013 8:37 AM

Awesome!! I have been wondering how I would get rid of this for a while now, and you made it easy.

Something to note - for me because OCS had been decommissioned so long ago I didn't actually know what the number was because it was different to the display number. Luckily the error "Cannot find the contact object associated with the entry for line URI "tel:+xxxxxx" reveals this. Once I set that as the telURI it worked a treat.

Thanks again!

Hi Cheng, you have just made my day. :)

Thumbs up.

Thank you

This worked great. Thanks for your help.

-Jose