Wednesday 16 December 2015

Not able to view messages in Conversation History in Outlook

Issue Description

While accessing the conversation history folder in Outlook, received below error

"To help prevent malicious code from running, one or more objects in this form were not loaded. For more information, contact your administrator."


Resolution:

Check if you have the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Security\DisableAllActiveX 
If so, change the DisableAllActiveX key value to 0 to check the result.

Note: Please make sure you have backed up your registry key before you modify it.

User unable to view the application sharing in the SfB Client

Issue Description


When User had P2P/Conference call and when other share their applications/desktop, the user is unable to view.

Check in Event Viewer:

When issue occurs, in the event viewer you will see the event ID 301 in Microsoft Office Alerts



Resolution:

1      Take a backup of the registry (Export Range: All)

2      Check below locations for CLSID {00000000-0000-0000-0000-000000000000}

HKEY_LocalMachine\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{00000000-0000-0000-0000-000000000000}

HKEY_LocalMachine\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{00000000-0000-0000-0000-000000000000}

3    If you find this CLSID {00000000-0000-0000-0000-000000000000} in the above locations, then delete the registry keys.


This will fix the application sharing issue.


Wednesday 2 December 2015

Providing Delegation rights for Non Enterprise Skype Users

Method 1:

Using Sefautil tool

.\Sefautil.exe <Sip ID of Manager> /Server:PoolFQDN /adddelegate:<Sip ID of Delegate>

After successfully running the above command, you will get below output

User Aor: SIPID
Display Name:
UM Enabled:
Simulring enabled:
Simultaneously Ringing Delegates: SipID

Using DB Analyze you can check if the changes are reflecting the user client using below command


.\DBAnalyze.exe /report:user /user:<User SIP account without sip:> /SQLSERVER:<User’s primary FE server Fqdn>\RTClocal >C:\temp\Filename.txt

To check user primary FE Server, use below command

Get-csUserPoolInfo -Identity sip:<SIP ID>

Method 2:

Apply the Client Policy to User whose property "EnableExchangeDelegateSync" is true to Manager

Grant-csClientPolicy -Identity "Manager Name" -PolicyName "Delegate Policy"



From Outlook of Manager, go to File -> Account Settings -> Delegate Access -> Add Users -> Search and select the user -> Ensure for calendar you are providing the Editor Permissions  -> Click Ok

Restart Skype Client and within 5 min, you will see the changes reflecting in your Sfb Client

Method 3:

Assign user both Manager & Assistant to Enterprise Voice policy

Then restart manager Sfb Client & then from Tools --> Call Forwarding --> Click Edit my delegate members & select the assistant name from the Address Book

Remove the Enterprise Voice Policy for both Manager & Assistant

Monday 30 November 2015

Skype Client doesnt open

Issue: When user try to double click the Skype client, it doesnt open

Troubleshooting Steps to fix the issue:
When checked in the Task Manager, multiple lync.exe processes were running. Killed all those processes and freshly launched the Skype for Business Client.

Now it launched successfully.

Wednesday 25 November 2015

Skype for Business Presence not visible in Outlook

Issue: Skype for Business Presence is not visible in Outlook
Description: When user opens the Outlook and Skype for Business client, in the Skype client shows the presence of other users but the same in Outlook is missing. Presence information is missing in Outlook & chat,video,call icons are greyed out

Troubleshooting Steps

Sfb Settings
Checked the Sfb settings and Personal Information Manager selected with Microsoft Exchange or Microsoft Outlook

Checked Configuration Information and verified the settings of EWS and MAPI and they are OK

Outlook Settings
File - Options - People 

Checked Online status next to name is checked

Also checked SFB add-in is enabled in Outlook

Registry Settings


Computer\HKEY_Current_User\Software\IM Providers
 
Where i found the DefaultIMApp was Collaboration Service instead of Lync
After i have changed the value to Lync and restarted the Outlook, Presence started showing in Outlook

 

Friday 20 November 2015

Skype client icons like chat,call,video are greyed out in Outlook while checking the contact card of a user

Issue: Skype client icons like chat,call,video are greyed out in Outlook while checking the contact card of a user

Resolution:

When you Right click on a user in Outlook and click Open contact Card 
Next to Add there will be "...."
Click on that
Click Link Contacts
Remove others which were not necessary

This will fix the problem :)


Thursday 19 November 2015

Skype for Business Client status sticks to Away

Few users complained about their presence status sticks to away and not changing except when they are in a call or meeting.

Tried all basic troubleshooting like checking from Skype for Business client end, Exchange connectivity (EWS) and all the settings seems correct.

Finally i have observed user has a virtual machine which has the same system configuration. It means two machines with a same host (One physical & One virtual)

When user logs into the virtual machine, the presence showing correctly.

After removing the VM machine & reformat of the machine. VM machine was configured with different host name & the issue is resolved completely.

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.

Wednesday 18 November 2015

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 :)