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

Hi dear blog reads,   since I was often asked how to set the UI in Skype for Business Client. Microsoft posted the update under Lync 2013 Server: https://technet.microsoft.com/library/dn954919.aspx Set-CsClientPolicy -Identity Global -EnableSkypeUI $true And the Registry Key In the [HKEY_CURRENT_USER\Software\Microsoft\Office\Lync] key, create a new Binary value. The Value name must be EnableSkypeUI , and the Value data must be set to 00 00 00 00 . The key should look like the following:   [HKEY_CURRENT_USER\Software\Microsoft\Office\Lync] "CanSharePptInCollab"=dword:00000001 "CanShareOneNoteInCollab"=dword:00000001 "CanAppShareInCollab"=dword:00000001 "EnableSkypeUI"=hex:00,00,00,00   Author: Thomas Poett MVP, Principal Consultant Microsoft Unified Communication

I came across this problem, where a customer reported: A user could not participate on desktop sharing session, neither in conference nor in a p2p session. Other video related submission were working, like video or white board. First I was guessing it could have been the video driver, but if video in Lync was working it didn't sound quite logic. After investigating this problem, I saw a ActiveX blocking Error Message in the Eventviewer: Microsoft Lync CLSID: {00000000-0000-0000-0000-000000000000} CATID: {9B179D6E-9BDB-454b-BE3D-89F9A792BD39} The ActiveX Compatibility setting disabled loading this object to help protect your security. 15.0.4433.1506 0x80004005 This let me investigate more closer into Internet Explore. Well even there is couldn't see anything directly: Microsoft reports several TechNet article: http://support.microsoft.com/kb/240797/en-us http://support.microsoft.com/kb/909738/en-us So you need to change the ActiveX Control Settings for Lync 2013...

With Lync 2010 and Lync 2013, some user run into an issue while they try to share a powerpoint presentation: This is regardless if a Office Web App server is installed or not (as Lync 2010 do not support OWA) The problem is mainly a client issue and should be seach for any server issues. That why in troubleshooting, it is necessary that you identifiy if you have general or partelly issues. You will receive the following error on a client: Solution: To fix the problem you will need to edit the [HKEY_CLASSES_ROOT\TypeLib\{91493440-5A91-11CF-8700-00AA0060263B}\2.b\0\Win32] @="C:\\Program Files\\Microsoft Office 15\\Root\\Office15\\MSPPT.OLB" and point it to the Office 14/15 directory in regedit.  The easiest way to do it would be to copy the registry entry for the TypeLib 2.a entry and paste it over the 2.b entry. Author: Thomas Pött Managing Consultant Microsoft UC

Very often I'm ask about this problem: English: Lync cannot verify that the server is trusted for your sign-in address. Connect anyway? German: Lync kann nicht überprüfen, ob der Server für Ihre Anmeldeadresse vertrauenswürdich ist. Trotzdem verbinden? Explanation: Lync Client 2013 has an additional safety check implemented. This verify the users SIP Domain with the FQDN of Lync server where the user tries to connect with. In the most customer environments, the SIP domain is different from the Active Directory domain. It usual and normal. Possible the SIP domain will match the SMTP domain, so user can easily experience Unified Communication, and the communication addresses are the identically. If you are in an lager enterprise, it's quiet a hassle if all users would have to click the acknowledgement. We need a solution! How to solve this problem, t here are two methods A manual way and a GPO based solution. If you are adjusting the Lync Client manually, you ...