Thomas.Poett@TEAMS (MVP Teams and Cross-Tenant M&A/D Migration Expert Lead)

Lync duplicated phone number or H ow to compare Lync vs. Active Directory user setting I had some issues at a customer site, where the customer was not handling user activation and de-activation in a proper way. So I was guessing we had duplicated phone numbers. Therefor it is necessary identifying which object was involved. No tool can be provided, as once more, scripting is necessary. You need to do some exports and compare it manually. ISSUE: The issue was, if a user X try to make a PSTN call, Lync Client announced:   Call cannot be initiated. Multiple Contacts exist including your phone number.    I suggested, we have an inconsistency between the Lync Server Database and Active Directory Lync Attribute msRTCSIP-Line. Now we need a way to figure out where the other phone number was assigned. Truly we know, it was not AD related, so it must be in the Lync Server User Database. Here the process how we were searching for the duplicated Phone Numb...

You can also use any PSTN Gateway or other SIP Trunk Provider... General deployment of a Branch Site including QSC SIP Trunk connection and dual SIP (PSTN) Gateway Objects. A SBS (Branch Site) can be deployed only with a Central Lync Site according your main Lync Design. It will not replace any associated Lync Pool (Std/EE) and do not hold any core Lync Database. More likely it is a SIP Registrar only, the main functionalities will still be provided from it Central Pool. There is are significant differences between Lync 2010 and Lync 2013, but in general the Voice Resiliency is still the same. e.g. In Lync 2010 you can still use the SBS for RGS or Conferencing Dial-Ins, but all this features are temporarily out of order, if the main Lync Pool is not reachable, also the User Presence. This is different in Lync 2013, where this features set will be continuously available. QSC SIP Trunk requirements Within the QSC SIP Trunk requirements are several aspects we have to take care and a...

When something went wrong during any Lync Installation, e.g. Topology was published with Errors and you tried to install a Lync Server, e.g. SBS, STD Edt, ... You might see the following Error: Cannot open database "xds" requested by the login. The login failed.Login failed for user DOMAIN\ADMINUSER I f this is happened, you fully need to uninstall: 1.) All Lync Server Components, beside: - Administrative Tools, Core Components, Resources Kit (if ist installed) 2.) The entire local SQL Instance, including Client Tools ! - Ensure, also the local Folder: C:\Program Files\Microsoft SQL Server\MSSQL10.RTCLOCAL is entirely deleted! 3.) Restart your Server now. If you are now going to reinstall Lync Server, 4.) make sure the Registry Key is clean: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager PendingFileRenameOperations NOTE: should the Lync Server Replica Replicator Agent should not have been proper uninstalled. You Need to...

In Exchange, as well as in Lync in always have some customers using proxy server. Due to nature of proper certificate validation processes, windows server need to validate the CRL (Certificate Revocation List). Since the CRL is a normal file, which we can download from CA provider, we need to ensure the accessibility of those files. in some customer environments we also find a mysterious behavior and we need to modify the WINHTTP proxy settings manually. there are two ways how to do so, if the normal IE setting will not work: netsh winhttp import proxy ie or netsh winhttp set proxy proxy-server=" http://wstmg.customer.com:3128 " bypass-list="*.customer.com,<local>" while with the bypass-list we need to play around till it fits. Also happened, especially in Exchange, I had to reboot the server before the settings got activated. Also don't forget about the IE Setting: for installation purposes (also for service packs), you should disable t...