Thomas.Poett@TEAMS (MVP Teams and Cross-Tenant Migration Specialist)

A most amazing tool and option bringing our world closer together. Making contact with other people around the world, with different languages and culture. Humanization is the ultimate goal for peace and happiness in our modern World. I took strong faith in this to be happened. Please try this out and open your mind towards an peaceful, harmonizing world. Get out and reach others, not only for business purposes. The privat side of live is important too. Watch this amazing Preview Video from Microsoft. Translating Voice on the fly with Skype Translator is the correct way in doing so. https://www.youtube.com/watch?v=G87pHe6mP0I Thanks you Author: Thomas Poett MVP, Principal Consultant Microsoft Unified Communication

Do not forget and update the Lync backend databases. ;) We need to patch all the databases, and the LIS / XDS from CMS. First we remember, the Standard Edition has its own local SQL Server containing all databases necessary for its related Frontend Services, therefore a single command similar as for the SQL Backends is required. If you have an Enterprise setup, you need to identify which features are installed, e.g. only native or incl. Archiving/ Monitoring, or even Persistent Chat. This separated databases require their own commands. For the entire process based on Enterprise Deployment, please enumerate your Topology and identify the configured components. Lync Standard Edition: Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn SE.FQDN -Verbose Lync Server 2013 Enterprise Edition Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -DatabasePaths "D:\LOGS","D:\DATA"  -SqlInstanceName   DBInstance -Verbose   Lync Server 20

today is time that I will explain the Lync protocol short cuts, the name what actually this couple of letters mean. I was very often asked what e.g. is the meaning of STUN or RT. Also, which RFC is behind this protocol. If further information are available, I have posted this info too. Therefore, here it come: STUN - (Simple Traversal of User Datagram Protocol (UDP) - Through Network Address Translators (NATs)) This is protocol used on the Edge server, where UDP data is passed through the NAT. It contains information about the external (public) IP address where the client is hidden behind and the internal (private) IP address the client has assigned. https://www.ietf.org/rfc/rfc3489.txt   STUN (Session Traversal Utilities for NAT) http://tools.ietf.org/html/rfc5389 URI Scheme for the Session Traversal Utilities for NAT protocol https://tools.ietf.org/html/rfc7064 NAT Behavior Discovery Using Session Traversal Utilities for NAT (STUN) https://tools.ietf.org/html/rfc578

Finally it is time to announce the changes Microsoft made. Still a lot feature are not yet public, but the name and the look and feel of the new client. A lot of rumors ran around the last month and now we have a huge discussion if this name could be the right one. YES, I say it is the right name, it is the right way Microsoft is going. Nothing is more efficient for a company, if user are familiar with the tools they need to master within the company. And here it come. over 20m people use Skype today and yes, they are very familiar with this tool. This means to us, the unified communication is now taking place in the real world. Families and their members come closer together. We increase the social component in our work environments. Never forget how amazing this is, chatting with your parents over the same tool. Even if this are two different platforms. Consumer (Skype) and Business (Skype for Business). But now we have them together finally. Never sitting in a hotel on

Hi Folks, thanks you for your participiation in my TechED 2014 session in Barcelona. I'm very proud you listen and enjoyed the session. For your reference, you can view and download my session here: http://channel9.msdn.com/Events/TechEd/Europe/2014/OFC-B325 Cheers Thomas   Author: Thomas Poett MVP, Senior Principal Consultant Microsoft Unified Communication

Recently I encountered a very strange issue: After installation another Lync Frontend Server, in this case a SBS. The Federation was broken. Incoming via the Edge Server everything looked fine. Meaning, incoming Federation request, e.g. presence or IM, as well as remote access from users hosted on this SBS were working correctly. But all outing communication to federated partners didn't work at all. After using the OCSLogger and analyzing the logs in SNOOPER, I saw an error message: The peer is not a configured server on this network interface and SIPPROXY_E_CONNECTION_UNKNOWN_SERVER coming along with another message: winsock-info="The peer forced closure of the connection" I used the RUST tool internally verifying the SBS certificate, it was correct. Even requesting the certificate again didn't help at all. Even I imported the Topology on the Edge server again! What this clearly explains was, if the SBS was presenting it's certificate, it didn't wo

In a special scenario, where I faced certain issue publishing the Lync Topology, where the Lync Frontend Servers are located in Sub Domain, you need to open certain TCP Ports to at least one Root Domain Controller: If you enabled the Lync Topology, you might face this issues: Error : The given key was not present in dictionary. Type : KeyNotFoundException Error : An error occurred when attempting to add "computer" to "RTCGroupxxx" Type : DeploymentException CategoryInfo: InvalideOperation: ([0] Microsoft.R....Core.Service) WebServer:pool.<fqdn> execution failed on an unrecoverable error. Error : Cannot obtain the domain information for computer "Root DC fqdn". Please make sure the computer FQDN is correct. Error : DsRoleGetPrimaryDomainInfromation failed with error "6BA". Just missing are the requirements for Topology publishing. If you are going to enable the Topology, you can use: Enable-CsTopology [-Confirm [<Swit

Lync is quiet strict in certificate validation. If you assign a non compatible certificate to Lync it will run into serious issues. This is most likely happen if you are using dedicated certificate for each Lync service. Especially the Lync WebServiceInternal certificate cannot be requested correctly, neither with Lync Wizard nor with the Request-CsCertificate command. Here the problem is that both methods are requesting a certificate with a Subject Name of the Internal Web Services rather than the POOL FQDN. Lync BUG: The remote certificate is invalid according to the validation procedure. reason="The web ticket is invalid." ;faultcode="wsse:InvalidSecurityToken",Replace=false In both, the TechNet and Help File the correct certificate is described. Therefore you need a valide process of requesting the correct certificate. If you have a consolidated certificate for all services, this is issue is not present, because the Subject Name responds to the POO