Sfb client showing Lync instead of Skype for Business

After Sfb Client update with KB3101496 with the pre-requisite KB3101360
It started showing Lync instead of Skype for Business in UI & Task Manager

From Registry, I have changed the value of LyncName DWORD value from Lync to Skype for Business 
Computer\HKCU\Software\Microsoft\Office\15.0\Lync

But this seems to be a temporary solution as after the system restarts again it started showing Lync instead of Skype for Business

So, I have uninstalled the KB3101496 from my installed updates as the issue appeared after installation the Sfb client patch.

Finally after un-installation of the patch & restarting my machine, Sfb client started showing the name properly as "Skype for Business"

Can't sign in to Skype for Business

Issue: Can't sign in to Skype for Business Client

Description: The server is temporarily unavailable. If the problem continues, please contact your support team.

Collected the Skype client logs and observed there no messages recorded & only trace information available in Snooper Tool.

Below is the hint which i got from the log

SockMgr: Create New connection:DestName:(domain.com)DestPort:(5061)Transport:(2)httpTunnel:(0)TLS RemotePrincipalName:(domain.com)

Destination Name should be Skype for Business Front End Server instead of sipdomain.com

This issue would appear if user types domain.com in the Manual Configuration

To fix the issue, Just change the Manual Configuration to Automatic Configuration 

Checked in user client configuration and found in the internal server tab, domain.com was mentioned.

Skype for Business Client Crashes

Issue: Whenever user launches Skype for Business Client it Crashes

Troubleshooting steps to fix the issue:

I checked at below location and found only Tracing folder (no CEIP & Sip folder available)

C:\Users\NTID\appdata\Local\Microsoft\Office\15.0\Lync

Then checked for Application events in Event viewer in user machine and found Event ID 1000

********************************************************************

Faulting application name: lync.exe, version: 15.0.4753.1000, time stamp: 0x55ca7b6a

Faulting module name: ftwrap.ax, version: 1.0.0.0, time stamp: 0x4cdbad93

Exception code: 0xc0000005

Fault offset: 0x00018b05

Faulting process id: 0x530

Faulting application start time: 0x01d121edcdf14121

Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe

Faulting module path: C:\Program Files (x86)\MMEDIA\VP-EYE Camera66\ftwrap.ax

Report Id: 0dfe7085-8de1-11e5-b77b-00a0c6000000

*********************************************************************

Asked user to remove the application (VP-EYE Camera66) software & user un-installed the software.

Then user launched the Skype for Business Client and you know what this time it didn't crash.

It was running normally :)

Convert Lync Meeting to Normal Meeting

Once you schedule a Lync Meeting and sent to the participants, they will receive the Lync Meeting conference details. If you want to remove the Lync Meeting information and convert it to a normal outlook meeting while sending you will receive below warning message, but again because of the Lync Add-in meeting information will be updated and sent to the participants

So, in order to send a normal outlook meeting by removing the Lync Meeting information.
We need to disable the Lync Add-in from Outlook first.

Uncheck the selected Meeting Add-in and Click Ok. This will disable the Lync Add-in, now while removing the Lync Meeting information and while sending to participants you won't see any warning message.


 

How to Remove the Header of CSV file

#TYPE System.Management.Automation.PSCustomObject

  To eliminate the above header from CSV file while using Export-CSV command, add -NoTypeInformation

Export-CSV "Location where you want to save the CSV file" -NoTypeInformation

Sending Lync Events by Email

$servers = "Server1","Server2"

$filepath = "C:\Scripts\"

$date = "{0:dd-MM-yyyy_HH-mm}" -f (get-date)

$file = $filepath + "ErrorLogs_" + $date + ".txt"

New-Item $filepath -type directory -force -Verbose

foreach($server in $servers)

{

$server | Out-File $file -Append

Get-Eventlog -log "Lync Server" -cn $Server -after ((get-date).addDays(-1)) -EntryType Error | Out-File $file -append

}

Send-MailMessage -To "anilkumar.nudurupati@testlab.com","anilkumar.nudurupati@testlab.com" -From "Lync.Monitoring@testlab.com" -Subject "Lync Server Events" -Attachments "$file" -SmtpServer "10.1.1.0"

How to check if a remote server is reachable

You can store the servers in $Servers variable

_________________________________________________________________

$Servers = "Server1","Server2","Server3"

Foreach ($Server in $Servers)
{

  $StatusPC = Test-Connection -Cn $Server -BufferSize 16 -Count 1 -ea 0 -quiet

      if ($StatusPC -eq $True)
       {    
       Write-host
       Write-host "$Server is reachable" -foregroundcolor Green -backgroundcolor black
       }

       else
       {
        Write-host
        Write-host "$Server is not reachable" -foregroundcolor Red -backgroundcolor black
       }

}

       Write-host

_________________________________________________________________

Note: If the servers are reachable you will be able to see the output in Green if not then you will see Red 


Alternate One-Liner Script:

get-content servers.txt | % {new-object psobject -property 

@{ComputerName=$_; Reachable=(test-connection -computername $_ -quiet -count 1)} }  

| ft -AutoSize