Twit(ter) Digest – Skype for Business / Lync (17-31 Jan 2016)
Highlights of popular re/tweets around Skype for Business / Lync for this period:
Habilitar la UM en #Exchange #Online en Integrarla con #Skype4B On-Premises https://t.co/dfJJxB1H49 (#Office365) pic.twitter.com/EcWjiy8xE9
— Santiago Buitrago (@sbuitragoreis) January 26, 2016
AllowSavePassword Group Policy setting for Skype for Business or Lync 2013
https://twitter.com/rogelio_g/status/691739896772333568
Active Directory Site Considerations in Lync Server and Skype4B Server Pool Pairing
Active Directory Site Considerations in #Lync Server and #Skype4B Server Pool Pairing https://t.co/CLxYAyGV0o pic.twitter.com/TbuGqtoV8t
— Trevor Miller (@TrevorAMiller) January 25, 2016
Skype for Business Address Book Normalisation Tool
TOOL UPDATE: Update to #Skype4B Address Book Normalisation Tool! Now up on TechNet Gallery. Rate it if you like 🙂 https://t.co/kosXBsGu8n
— myteamslab (@myteamslab) January 20, 2016
Skype for Android lets you schedule calls, open Office files
Skype for Android lets you schedule calls, open Office files – https://t.co/Qw7DIDQWzt #skype4b #lync
— Steve McPherson (@stevenmc1060) January 21, 2016
Review: Magewell USB Capture HDMI
Review: Magewell USB Capture HDMI with #Skype4B https://t.co/cHRcnRlchE pic.twitter.com/v24ILxr2LA
— Tom Morgan (@tomorgan) January 18, 2016
Migrating CMS in Lync Server and Skype4B Server
https://twitter.com/s4btweets/status/689092910617358337
New-CsFirmware.ps1 Import single/multiple #Lync and #Skype4B Phone Ed. firmware updates to single/multiple pools. https://t.co/l5KgGinuMa
— Pat Richard – MVP 🕵🏼 (@patrichard) January 17, 2016
Lync 2013 / SfB 2015 Client Update – January 2016
https://twitter.com/s4btweets/status/688686148550553600
TIP 1520A: Skype for Business Centralized Logging – User Not Authorized
You start with elevated administrative privileges the latest version of Skype for Business Server 2015, Logging Tool (v6.0.9319.73 released 29 July 2015) and are login as a Sfbs Administrator with CSAdministrator membership on a Skype Front-End Server.
When you attempt to “Start Logging” after having selected the desired “Scenarios” and machines under “Topology”, the following error shows up:
Error: User domain\skypeadmin is not authorized to view or change logging OR this pool and computers are not valid. Pools or Computers – s01.domain.name,s01.domain.name.
In an environment supporting multiple server versions of Lync/Skype, verify that the machines picked under “Topology” are running Lync Server 2013 and higher as the Centralized Logging feature was only first introduced in Lync Server 2013.
#Skype4B #Lync #ITPros #UC #Office365
Follow me for all the buzz -> @_leedesmond (Twitter)!
TIP 1519: Skype for Business 2015 Debugging Tools and VC++ 2013 Runtime
Attempts to install Skype for Business 2015 Debugging Tools* on an administrative workstation or server running a supported Windows OS may fail with the error:
Skype for Business 2015, Debugging Tools installation or uninstallation requires that Microsoft Visual C++ 2013 x64 Minimum Runtime – 12.0.21005 Package is already installed. Either use Setup.exe for installation or run vcredist_x64.exe included with the product to install the redistributable.
[ OK ]
You can either ensure that …
… the target machine has completed running setup.exe from the Skype for Business Server 2015 media, which includes the prerequisite VC++ 2013 runtime that you must install anyway, or install from a downloadable copy of the Visual C++ Redistributable Packages for Visual Studio 2013#.
Note that unlike in Lync Server 2013, a “Lync-specific” version of the latter does not appear to be a requirement.
* SkypeForBusinessDebugTools.msi
v9319.73 released 29 July 2015 – includes Snooper, CLSLogger, CLSScenarioEdit.psm1
# KB2883200 is needed for Windows Server 2012 R2 and Windows 8.1
TIP 1517: Skype Business Edge – Schannel EventID 36888
Found an interesting article giving a nice look into why the error “Schannel EventID 36888” consistently appears in the Windows SYSTEM log:
A fatal error was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows Schannel error state is 1203.
How to enable Schannel event logging in IIS (link)
Follow me for all the buzz -> @_leedesmond (Twitter)!