blinklasas.blogg.se - Skype for business contact card editing

#Skype for business contact card editing full#
#Skype for business contact card editing Pc#
#Skype for business contact card editing download#

This is much safer than manually modifying the database. I decided to do the same for all the accounts having this issue. Re-adding the user brought with it only the correct numbers. By removing the account from SfB, it cleared out all contact card information for this account. This ended up fixing the problem for this user. While waiting, I had the “bright” idea to simply remove and re-add this user account from SfB.

The Microsoft tech was working on a solution to modify the database directly and remove these incorrect numbers. This number is probably stored in binary format and not plain text. I used some scripts to search through the tables but I could not find any references to “+0740892387”. I spent another few hours looking (carefully) through the RTCLOCAL instance databases on the Skype FE server using SQL Management Studio. Now you have a list of all user accounts having this issue. PS C:tempSQLExports> Get-ChildItem -recurse | Select-String -pattern “+074089” | group path | select name *> C:tempSQLExportsUsersWithWrongNumbers.txt & ‘c:Program FilesSkype for Business Server 2015ResKitDBAnalyze.exe’ /report:user /sqlserver:SFBFE01RTCLocal > c:tempSQLExportssqlexport$SamName.txtįinally, run the below PowerShell command to search through all the output files for the string “+074089”, and write the filenames to another TXT file called “UsersWithWrongNumbers.txt. This information told me that the incorrect number came from the old Lync 2013 server during the user migration.īelow is a script I used to check all 300+ users in SfB using the DBAnalyze.exe tool. We could also see the “LastPubTime” was in 2015. In the output we could see the incorrect number showing. The tool grabs all data from a particular user from the Skype Database and spits it out in plain text. The MS tech ran the DBAnalyze.exe tool from the SfB Reskit.Ĭ:Program FilesSkype for Business Server 2015ResKitDBAnalyze.exe /report:user /sqlserver:SFBFE01RTCLocal > c:tempSQLExportssqlexportusername.txt I opened a case with Microsoft support to help us with this issue. So clearly this number was stored someone in the FE server. This means that every time I searched for this user in my SfB client, it would send a SUBSCRIBE message to the FE, and I would get back a 200 OK containing this incorrect number. The number was then stored in the CoreContact.cache file on my client, but not in the GalContacts.db. In this file I searched for my incorrect number “+0740892387” and found it buried in a 200 OK response from the Front-End server.

#Skype for business contact card editing Pc#

This log file can be found on your PC at C:UsersusernameAppDataLocalMicrosoftOffice16.0LyncTracing I then looked in the SfB client log file called “Lync-UccApi-0.UccApilog” using Snooper. With the help of a colleague, we looked through the Exchange GAL and local Outlook address book, but found nothing. In fact, opening the GalContacts.db file with Notepad showed the correct number.

#Skype for business contact card editing download#

Delete the test account Profile folder in Start-up SfB client to download the new Address book.

I then did the usual steps of refreshing the Global Skype address book. With the help of Ken Lasko’s blog, I tweaked my rules and ended up with this: My first thought was that I had messed up the normalization rules. For some users, both numbers were showing in the contact card. The interesting thing was that the incorrect numbers were an exact copy of the correct number, but with a “+” in front. Users would click on these “incorrect” numbers to dial a colleague and it would fail: They already had IM & Presence on a Lync 2013 Front-End server and the plan was to migrate all users and settings to the new SfB FE, and decommission the Lync 2013 FE.Įverything went smoothly until the customer noted that the phone numbers showing in their SfB and Lync clients weren’t correct.

#Skype for business contact card editing full#

Recently, I deployed a full Skype for Business Server 2015 solution with Enterprise Voice for a customer.