AnotherUCBlog > Exchange, S4B, O365

Share my findings in the Microsoft unified communication world



SfB/Polycom – VVX IPPhones BToE (Shared desktop/VDI)

Here is the situation :

  • Skype for Business
  • Client running Windows 7 under Citrix Xendesktop
  • Wyse terminals
  • Polycom IPPhones VVX

With the release of Polycom BtoE v3.7, Polycom is supporting VDI Citrix Xendesktop environment (HDX Optimization needs to be disabled) for BToe with VVX Phones running UCS v5.7.

We have found that when you install the software with a user, pair the phone with this user using the manual pairing (code pairing). You can sign out and then sign in (windows session), the pairing is restored automatically. If on the same machine, you log on with another user and then sign out and sign in again, the pairing is not restored automatically until you repair the BTOE installation…

This is due to the software not trying to create the following registry values if they do not exist when performing the first pairing for the user who did not install the BTOE software:

[HKEY_CURRENT_USER\Software\Polycom\Polycom BToE Connector]




After deploying a GPO to create those values at log on (create not update), the software is able to register the pairing code and pairing is automatically restored after a sign out sign in.

This issue also occurs in a “normal” enviroment (without Citrix XenDesktop) where desktop are shared between multiple users.

FYI, the pairing code change when the phone change his IP address. The pairing code is kept after a phone reboot.

Hope this will save you time



EXCHANGE/SFB/UM – Callee voicemail language issue

Hello all,

I had an interesting behavior found by customer recently, he tolds me that when he is reaching the voicemail of one of his user (skype call), voicemail language is in English no matter the UM dialplan…

When I tried to call the user from my mobile, I got the voicemail in the right language (french in our example).

I performed multiple tests and got those results :

  • Internal Skype call -> wrong voicemail language
  • Skype call from federated partner -> right voicemail language
  • PSTN call -> right voicemail language

I compared the Skype for Business logs between internal call and federated partner call and found no difference, the same UM diapl plan was called…

Then I finally found that it was due to the caller mailbox language ! If the caller is having an Exchange mailbox in English then he will reach a voicemail in English.

So this is not an issue but it is per design !


Lync/SfB – Simultaneous ringing not working

Hi all,

New day, new challenge !

We faced an issue where users who use/used the Skype for Business mobile client were not able to get simultaneous ringing working…

Even they disconnect and uninstall the application, simultaneous ringing was no more working for their mobile device set in AD but it was working with another number.

Then I launched the lync debug tool and saw that it was trying to reach the sip address (the phone number to reach was on an iPhone)

So I tried to test the push notification with this command on the front-end server :

Test-CsMcxPushNotification -AccessEdgeFqdn EdgeServerFQDN

So I followed the article to configure push notifications :

Then simultaneous ringing start to work again for those users who were using the mobile app.



Domino/Exchange – Perform offline migration nsf to pst

Hi all,

If you cannot or don’t want to have a direct connection between your “old” domino servers and your Microsoft Exchange servers, then you can use Quest Notes Migrator for Exchange to convert nsf files to pst. Here is how to do it :

  1. Export names.nsf (NAB) from domino server and copy it on NME server
  2. Launch the NME program and perform the SQL configuration and logs folder path then close NME
  3. nme1
  4. nme2
  5. In ini conf file, add the following parameters:











  1. With SQL management studio, create the domino server from where the names.nsf is coming with the command below:

INSERT INTO [NME40DB].[dbo].[T_NMEServers] (NMEServerGUID,DisplayName,ServerType,ServerName,HostName) values (‘12345678-1234-1234-1234-123456789123′,’DominoServerName‘,1,’DominoServerName‘,’DominoServerName‘)

For example :

INSERT INTO [NME40DB].[dbo].[T_NMEServers] (NMEServerGUID,DisplayName,ServerType,ServerName,HostName) values (‘12345678-1234-1234-1234-123456789123′,’CHMAMA01′,1,’CHMAMA01′,’CHMAMA01’)

  1. Launch again NME and perform the “Discover Notes Information” by adding the “names.nsf” you got from step 1 this will help NME to translate Domino user names into Exchange user names
  2. nme3 nme4 nme5
  3. Then you can start your migrations/conversions by creating the collection of mailboxes you want to migrate and then launch the locate Notes datastore to define where to search the nsf files :
  4. nme6 nme7
  5. Finally you can launch the migration with the final step “Migrate user data”



SFB – Dial-In number displayed twice for new Skype meeting

Hi all,

On a fresh install of Skype for Business, I created one and only one dial-in number but this one wear appearing twice when creating a “New Skype meeting” from Outlook.

We discover that this was the case only when using Outlook 2010 or 2013 with the Skype for Business client 2016.

This was not the case when using Outlook 2016 or OWA.

The only workaround I found was to create a second dial-in number for a different language (One for English and one for French) then both numbers were appearing and no duplicates.

FYI, I was running Skype for Business Server 2015 with CU4.

Hope it will save you time troubleshooting.


EXCHANGE – X-OWA-Error: Microsoft.Exchange.Data.Storage.StorageTransientException


New day, new problem !

Some users for an unknown were not able to connect to OWA and Outlook suddenly, I never had time to find why unfortunately…

The error in OWA was : X-OWA-Error: Microsoft.Exchange.Data.Storage.StorageTransientExceptiontransienterrorexchange2013

What I did to correct the issue was simply to modify one digit  of the legacyExchangeDN, the last part which is random.

/o=blabla/ou=exchange administrative group (fydibohf24spdlt)/cn=recipients/cn=ef520295b5ab4cc3949fd9e06b7b6285-dbrooks


/o=blabla/ou=exchange administrative group (fydibohf24spdlt)/cn=recipients/cn=ef520295b5ab4cc3949fd9e06b7b6287-dbrooks

Hop this will save time in case it happens to you



O365 – Create Mail User from AADConnect synced user

Hello all,
A few days ago, I had to make a user in a local AD appearing as a contact in O365 address book.
The local AD was not having a local Exchange so I couldn’t use the ECP to populate the right attribute…
Here are the required attribute to fill in the local AD user to make it appear in O365 address book as a contact (mail user):
mail =
mailNickName = internal.username (should be the same value as samAccountName)
targetAddress =
proxyAddresses =
Hope this will save time to you

Skype for Business – Unable to share Poll, whiteboard and Powerpoint presentation

Hello all,

I had an issue recently where one user was not able to share a poll, a whiteboard and a Powerpoint presentation.

The infrastructure was Skype for Business 2015 Server Standard with last CU (June 2016) and the clients were all having Skype for Business version 16.0.4432.1000.

But for only user this was not working and when he tried on another computer then it was working so it was due to his computer…

Indeed the KB3118288 was missing and as soon as we installed it, everything started to work on this computer.

Installing the KB does not change the client version and stay 16.0.4432.1000

Hop this will help some of you !

LYNC/SKYPE FOR BUSINESS – Fail to escalate IM conversation to Microsoft Whiteboard sharing or Microsoft PowerPoint sharing session with a federated user

Hi Guys,

I have go a lot of things to say this week !

I had a new issue corrected thanks to a great MS Engineer ! We were having an error when trying to share a PowerPoint file with a federated user, this one was going to the lobby for a minute and then it failed. See below :


Again thanks to this great MS Engineer, we found that it was due to this known issue : and indeed we were using the Lync 2013 client (or Skype for Business 2015 which is Lync 2013 with SFB UI)

So after launching the following commands :

Get-CsConferencingPolicy | Set-csconferencingpolicy -AllowAnonymousParticipantsInMeetings $true -AllowFederatedParticipantJoinAsSameEnterprise $true

Set-CsAccessEdgeConfiguration -AllowAnonymousUsers $true

All was working fine !

Enjoy !!!

Blog at

Up ↑