[Lync 2013] - Desktop Sharing and taking control

Hello,
In Lync 2013 when someone shares his/her screen and I'm taking control of the shared screen I have the following problem:
Everything works fine when I'm in control with other person's desktop, however when the Lync IM/Sharing window looses focus and then the focus is regained by clicking on the shared desktop, all the input is frozen in the Lync IM window.
for example:
I take control of shared screen, do something on the shared desktop, then I open something on my own PC (the Lync window is loosing focus at this moment), then when I click on the shared screen inside Lync IM window to continue controlling the remote desktop
any input to the Lync window is "frozen".
There is some error sound comming everytime I click in the Lync IM window during this time - just as there was some invisible popup that is blocking interaction with parent window
to solve this I have to once again loose focus of Lync IM window and then regain it again.
This is on many machines (Windows 7 64bit / Windows 8.1 Preview 64bit) using Lync 2013 32bit with and without updates
I'm using multiple monitors, but it's the same on a single display - just open Lync IM/Sharing window in one half of the screen and open notepad on other half (don't minimize windows, just switch between them during sharing)
Best Regards

Hi Bartek,
Did the issue happen on Windows 7/8 32 bit using Lync 2013 32 bit?
Try Clean Boot to disable all non-Microsoft services and start Lync again:
How to Clean Boot:
http://support.microsoft.com/kb/929135
Since the OS is 64 bit, please remove Lync 2013 32 bit and install Lync 2013 client 64 bit and apply the latest update then test the issue again.
Best Regards,
Eason Huang
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Lync 2013 desktop usesr and Lync Web users.

When i send IM to users within my group using Lync 2013 desktop client, the recipients on Lync Web app does not get my font color or font syle. Is there settings to get the font color and font style I use on the desktop client to appear in the Lync
web app users windows as I send it over.

Hi,
I test in my Lync environment but didn’t find the issue. As Anthony said, there is no set except the setting “Change Font…” on Lync client Options. You can try to download the latest version for Lync client from Microsoft Website
and then test again.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 Desktop Shareing

Hi all
this is Lync 2013.
When desktop sharing between 2 external users( Connecting from Internet) will it be P2P or will it go via FE servers ?
When desktop sharing between 1 internal user and 1 External user, will it be via FE server ?
regards

Sorry about that, I guessed this was common knowledge.
NAT means "Network Address Translation" which is a difficult term for saying that someone is for example sitting at home behind a Router connected to an ISP with one public IP Address and shares the internet access with other devices connected to that user
(essentially enabling all those devices connections to internet without the need of having multiple public IP Adresses)
The process works by hiding the device real IP and replacing with the router Public IP address when it crosses the router and ther router keeps track of Ports and sessions that the different devices have so it knows how to send traffic back to the devices.
A side effect of this is that there is no way of someone on the internet connection can see your IP or contact you directly. Lync does have a process to try to enable direct communication between clients behind a NAT but that does not guarantee
this will always work, there are cases where it will work and cases where it will never work. In case it does not work Lync will bridge the connection at the Lync EDGE server.
I hope this explains it better
- Belgian Unified Communications Community : http://www.pro-lync.be - MCM/MVP/MCT

Lync 2013 desktop sharing is giving Black screen when using virtual machine

Hello,
We have a user who is connecting our network through VPN and connecting to a virtual machine. He is able to login to lync but when he start desktop sharing or some one sharing the desktop to him, he is getting black screen. He is using windows 7 and Lync
2013 client. Please advice

Hi,
Did he receive any error message?
Please double check the ports for VPN traffic.
Please also enable logging on Lync client for further troubleshooting.
What’s more, when users connect to the corporate network using a VPN client, Lync media traffic is sent through the VPN tunnel. This configuration can create additional latency and jitter because media traffic must pass through an additional layer of encryption
and decryption. The issue is compounded when the VPN concentrator is busy.
You can configuration like this:
Lync client connect to the Access Edge Server for all signaling connections when on the corporate VPN. However, Media sessions routed through the A/V Edge Server interface instead of establishing connectivity through the VPN tunnel.
More details:
http://blogs.technet.com/b/nexthop/archive/2011/11/15/enabling-lync-media-to-bypass-a-vpn-tunnel.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 Desktop SHaring Not working from Internet

Hi,
I am facing one issue, my Desktop Sharing is not working for Internet Clients, error message comes is "we could not connect to the presentation because of network issues" Internally it is working fine even I from Edge Server.
I am using single Public IP Configuration on Edge Server with Port 5061,444,443,3478.
Any suggestions, on I can check are welcome.
Best Regards, Ranjit Singh

Hello Ranjit,
Application Sharing/Desktop Sharing happens through SRTP through the A/V edge Server hence checking the Port Range is very important
Following Port reachability to be checked first
Public --> Edge server:
TCP/443
UDP/3478
TCP/50,000-59,999 (Outbound only)
From the Front End pool to the internal Edge:
TCP/5062
TCP/443
UDP/3478
From the internal Edge to the Front End Pool:
TCP/5065
TCP/49152-65335 (Inbound/Outbound)
More Detailed info can be seen here
http://blogs.technet.com/b/nexthop/archive/2012/11/05/lyncmd-troubleshooting-lync-server-2010-application-sharing-internal-and-remote-scenarios.aspx

External Meetings using Lync Web App vs Lync 2013 Desktop client

We have LYNC Server 2013 deployed on premise. Our clients are LYNC 2013. When someone external to our organization sends us a Lync meeting request we are able to connect with our Lync 2012 desktop client but only Audio is available. We cannot share
the desktop. If however we connect to the external meeting using the Lync Web App (by specifying
?sl=1 at the end of the meeting url) we are able to use all the services like audio, desktop sharing etc.
I've found the following articles that suggest that the desktop clients are not the preferred choice to connect to external meetings.
http://blog.schertz.name/2011/11/forcing-lync-web-app/
http://www.computer-talk.com/en/blog/item/attendees-cannot-join-your-lync-web-conference
Can anyone advise as to why the desktop clients are restrictive and if there is a fix and if not how can we force users to use the Lync Web App to connect to external meetings?
Our lync 2013 desktop clients use the following ports:
PS C:\Users\am03744ad> Get-CsConferencingConfiguration
Identity                           : Global
MaxContentStorageMb                : 500
MaxUploadFileSizeMb                : 500
MaxBandwidthPerAppSharingServiceMb : 375
ContentGracePeriod                 : 15.00:00:00
ClientMediaPortRangeEnabled        : True
ClientMediaPort                    : 5350
ClientMediaPortRange               : 40
ClientAudioPort                    : 50020
ClientAudioPortRange               : 20
ClientVideoPort                    : 58000
ClientVideoPortRange               : 20
ClientAppSharingPort               : 42000
ClientAppSharingPortRange          : 20
ClientFileTransferPort             : 42020
ClientFileTransferPortRange        : 20
ClientSipDynamicPort               : 7100
ClientSipDynamicPortRange          : 3
Organization                       :
HelpdeskInternalUrl                :
HelpdeskExternalUrl                :
ConsoleDownloadInternalUrl         :
ConsoleDownloadExternalUrl         :

You should be fine using the full Lync client, it's not restricted by default. If there's an issue, it's typically in the networking related to your edge, or the edge of the organization you're federating with.
The reason the web client is preferred by many (not all, and that's not an official Microsoft stance), is simply that if everyone uses the web client, it's a consistent experience for the attendees and you don't have to worry about the status of attendee's Lync
environment or federation.
Can your external users share a desktop with internal users? Can they do it externally in a conference hosted by you? Can the remote organization share desktops with you when connected to your conferences? And in these conferences,
have the marked you as presenter so you can present your desktop?
There's no good way to automatically force users to use the web app each time unfortunately. The other organization would need to hardcode that ?sl=1 into each meeting invite sent.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Lync 2013 Android Client and simultaneous ring problem

this is sort of a duplicate but since the other one was marked as answered when it was not I figured I'd start this topic up again.
I set up the Android mobile client on my phone and all seemed to work fine (apart from the know bu where it keeps saying "calls aren't setup to ring mobile device..." whether the are or not) but I've run into the super annoying issue where
even if you turn simultaneous ring off for the cell phone number it still rings through when I get a call on my Lync work phone (a bit delayed so it rings just before voice mail picks up). What stinks is that even if I completely sign out of the Lync mobile
app I still get these ring throughs. The only solution was to reinstall the app with a bogus cell number (which is a bad way to go as it might be calling a random number if I'm not careful). the other thread had a moderator give the answer to create a user
level voice policy to not allow simultaneous ringing. Yeah, thanks. I'd actually like to use the feature sometimes and so would all of my users.
So, is this a bug in the Android client? In the Mobile functionality on the server? What? When I run SEFAUtil on my account it doesn't show any simulring or forwarding (my full Lync 2013 client agrees with that) so what the heck is going on. I can't roll
this upgrade from 2010 out to users until this can be resolved.
Steve

I think I found the solution to the annoying ring to the phone even when your turn off your call forwarding/sim ring.
In Lync 2013 desktop client, when you first setup SIM ring, it asks you to enter the phone that you would like to have sim ring. In this case, most likely your cellphone number. Then when you are sick of SIM ring, you decide to turn this feature off, but
you still get SIM ring to your cellphone which is very annoying. If I remember correctly, in Lync 2010, when you switch from SIM ring ON to OFF, the cellphone number will be deleted automatically. In Lync 2013, however, doesn't do so. Therefore, your cellphone
number is still there even though your have call forwarding OFF. This is a bug. The work around to it is to go to Tools > Options > Call Forwarding, select SiM ring; then from the drop down list, instead of choosing your saved cellphone number, choose
WORK number. Then select "Turn Off Call Forwarding". Now, go back to SIM ring option again, you will see the saved cellphone number is now gone. It will only display your work number. Now, try to make a test call to your Lync phone, it shouldn't ring to your
cellphone anymore.
To me, this seems to have fixed it. You can try this and let me know if that fixes yours too.
A@RJC

EWS not deployed anymore to Lync 2013 Desktop Clients, Mobile Clients still working fine

Hello dear community,
the subject of EWS in conjunction with Lync 2013 has been discussed a lot here .
However, I could not find here any solution for my problem and I'm (almost) at my end.
Following scenario - 1 x Lync 2013 BE server, 1 x Lync 2013 Edge server, 1 x reverse proxy (IIS ARR). This Lync 2013 deployment
was installed about two months ago and integrated into existing IT landscape. Everything worked wonderfully - desktop and mobile clients were able to connect from inside and outside our organization, EMS was deployed to both desktop and mobile clients.
After that there are no any configuration changes made on Lync server, and yesterday, shortly before an important presentation
I've found, that EWS is not deployed anymore on all desktop clients. Mobile clients, however, continue to function smoothly.
I have tried the following: restart Lync and reverse proxy servers - without success, Lync Connectivity Analyzer shows all
green (internal and external), all relevant tests with Microsoft Remote Connectivity Analyzer were passed, also analysis using Wireshark brought nothing.
I must to say that a week ago I installed SP3 for Exchange 2010 - can it may be because? Also appears more
times a day the following error message in Event Viewer on the back-end server (language of operation system is German):
Protokollname: Lync Server
Quelle:        LS Storage Service
Datum:         05.12.2013 19:23:14
Ereignis-ID:   32054
Aufgabenkategorie:(4006)
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      SERVER-11.Speedpoint.local
Beschreibung:
EWS-AutoErmittlungsfehler im Speicherdienst.
ExchangeAutodiscoverException: code=ErrorEwsAutodiscover, reason=GetUserSettings
failed, smtpAddress = xxx, Autodiscover Uri=https://autodiscover.xxx.de/autodiscover/autodiscover.svc, Autodiscover WebProxy=<NULL> ---> Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed.
Das Stammelement ist nicht vorhanden. ---> System.Xml.XmlException: Das Stammelement ist nicht vorhanden.
   bei System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
   bei System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   bei System.Xml.XmlCharCheckingReader.Read()
   bei Microsoft.Exchange.WebServices.Data.EwsXmlReader.Read()
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetUserSettings(List`1 smtpAddresses, List`1 settings, Nullable`1 requestedVersion, Uri& autodiscoverUrl)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetSettings[TGetSettingsResponseCollection,TSettingName](List`1 identities, List`1 settings, Nullable`1 requestedVersion, GetSettingsMethod`2 getSettingsMethod, Func`1 getDomainMethod)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(List`1 smtpAddresses, List`1 settings)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetSoapUserSettings(String smtpAddress, List`1 requestedSettings)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(String userSmtpAddress, UserSettingName[] userSettingNames)
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
   --- End of inner exception stack trace ---
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.GetUserEwsSettings(StoreContext ctx, String smtpAddress, CacheMode cacheMode)
Ursache: Der AutoErmittlungs-URI war nicht richtig konfiguriert oder nicht erreichbar. Eventuell besteht ein Problem mit dem Proxy, oder andere Fehler liegen
vor.
Lösung:
Überprüfen Sie die Ereignisdetails. Überprüfen Sie, ob der URI des AutoErmittlungsdiensts ordnungsgemäß konfiguriert und erreichbar ist. Prüfen Sie, ob die Proxyeinstellungen ordnungsgemäß konfiguriert sind und der Proxy erreichbar ist. Prüfen Sie die Konfiguration
der AutoErmittlung zwischen Lync und Exchange Autodiscovery anhand des Handbuchs zur Problembehandlung. Wenn das Problem weiterhin besteht, wenden Sie sich mit den Ereignisdetails an das Supportteam Ihrer Organisation.
Ereignis-XML:
< Event xmlns="">
<System>
    <Provider Name="LS Storage Service" />
    <EventID Qualifiers="53158">32054</EventID>
    <Level>2</Level>
    <Task>4006</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-12-05T18:23:14.000000000Z" />
    <EventRecordID>19949</EventRecordID>
    <Channel>Lync Server</Channel>
    <Computer>SERVER-11.Speedpoint.local</Computer>
    <Security />
</System>
<EventData>
    <Data>ExchangeAutodiscoverException: code=ErrorEwsAutodiscover, reason=GetUserSettings failed, smtpAddress=xxx, Autodiscover Uri=https://autodiscover.xxx.de/autodiscover/autodiscover.svc, Autodiscover WebProxy=<NULL> --->
Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed.
Das Stammelement ist nicht vorhanden. ---> System.Xml.XmlException: Das Stammelement ist nicht vorhanden.
   bei System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
   bei System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   bei System.Xml.XmlCharCheckingReader.Read()
   bei Microsoft.Exchange.WebServices.Data.EwsXmlReader.Read()
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetUserSettings(List`1 smtpAddresses, List`1 settings, Nullable`1 requestedVersion, Uri& autodiscoverUrl)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetSettings[TGetSettingsResponseCollection,TSettingName](List`1 identities, List`1 settings, Nullable`1 requestedVersion, GetSettingsMethod`2 getSettingsMethod, Func`1 getDomainMethod)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(List`1 smtpAddresses, List`1 settings)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetSoapUserSettings(String smtpAddress, List`1 requestedSettings)
   bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(String userSmtpAddress, UserSettingName[] userSettingNames)
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
   --- End of inner exception stack trace ---
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
   bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.GetUserEwsSettings(StoreContext ctx, String smtpAddress, CacheMode cacheMode)
< /Data>
</EventData>
< /Event>
However Event ID
32054
was actually
always there
– even
when everything
worked fine -
but with
some another content.
That's why I
don't know
if I
should take it seriously.
Thanks a lot in advance for your help!

Hi MiF,
The issue may cause by the Network Service account that the Lync Storage Service uses does not have access to the private key in used by the oAuth certificate. Please do with the following steps:
Open MMC and add the “Certificates” Snap-in (Local Computer)
Open Personal | Certificates and find the the Certificate being used for OAuth (use the Lync “Get-CsCertificate -Type OAuthTokenIssuer” cmdlet to find the serial number of the OAuth certificate).
Right-click | “All Tasks” | “Manage Private Keys”
Add Permissions for “Network Service” account (the defaults Full control and Read).
Please also check registry key on client computer.
If the HKCU\Software\Microsoft\ Office\15.0\Lync \[User SMTP Address]\Autodiscovery registry key does not exist on the user’s workstation, then it likely means that one of the following failures
have occurred:
Lync was unable to locate a valid DNS A record or SRV record for the Autodiscover site
Certificate assigned to Autodiscover site is not trusted by the Lync workstation
More details:
http://www.microsoft.com/en-in/download/confirmation.aspx?id=15668
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Desktop Sharing and Application Shareing White List BlackList Possible

Does anybody know if its at all possible to Blacklist or whitelist applications into Application sharing, so that users can only share certain ones ?
so in short Application whitelisting, either by 3rd party Apps or but server extension.
Lync 2013 and 2010
thanks

Extremely sorry about that, but maybe you don't like users sharing their entire computer; after all, when they do that everyone in the meeting sees everything
that happens on the shared computer, including such things as a Microsoft Outlook "toast" popping up to announce a newly-received email. Because of that, you might prefer to limit users to sharing just a single application; that way, people in the
meeting only see the activities that take place within that application. In that case, just set EnableAppDesktopSharing to SingleApplication:
Set-CsConferencingPolicy –Identity global –EnableAppDesktopSharing SingleApplication
When you do that, the Desktop option will no longer be available under the Share menu.

Differences & Similarities between Lync 2013 desktop & Lync 2013 mobile

We've got Lync 2013 installed on our desktops. We now want to introduce Lync 2013 for both iPhone's and Android's.
Is there anywhere I can get a list of what functionality the desktop & mobile versions share, as well as what they don't.
If this is in the wrong place, apologies.
Duncan

Sorry, just found the information.
Guess I didn't look very well in the first place. :(

Lync 2013 Cumulative Update and Lync 2010 CM database ??

I was going through the update process for our new Lync 2013 Enterprise install, I just have a FE server up at this point. I ran the LyncServerUpdateInstaller and it ran fine. I then ran through the Backend SQL updates, and of course I
get to the end and read...
Note In a coexistence environment that contains both Lync Server 2010 and Lync Server 2013 in which the Central Management Service is located on a Lync Server 2010 pool, do not run the
Install-CsDatabase -CentralManagementDatabase cmdlet. If you later move the Central Management Service to a Lync Server 2013 pool, you have to run the
Install-CsDatabase -CentralManagementDatabase cmdlet to apply the changes.
And yes we have a Lync 2010 Standard server running and the CM DB is on the Lync 2010 pool. I haven't noticed any problems yet, Do I need to be concerned about this? And if so how do I fix it? I only have a test account on the Lync
2013 server at this point. So I could uninstall if needed.
Thanks,
Matt

Hi,
As I know, it better to move the Central Management Store from Lync server 2013 database back to Lync server 2010 database firstly. Then if needed, you can uninstall the Lync server 2013 database.
You can refer to the link below:
http://cmcgreanor.wordpress.com/2012/07/24/move-lync-central-management-store-and-front-end-servers-to-a-new-lync-pool-with-a-new-sql-backend/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

CUCiMOC and CUCiLync desktop sharing and conferencing

Hi Guys,
Can someone please advise when we install CUCiMOC or CUCiLync does it also disable the "desktop sharing" feature of MOC/Lync client? I have read few blogs on this and getting conflicting answers
Also, my understanding is CUCiMOC or CUCiLync can still use CUCM (DSP's in ISR) for adhoc audio conferencing, however for Web, Video and scheduled audio conferencing we need to implement Meeting Place and Webex...is that correct?
Thanks
Aamir

Hi Aamir,
desktop sharing should still be available, It has nothing to do with it. You should disable any audio or video conferencing solution on Lync in order to have the better experience with CUCILync. This does not mean it will disable desktop sharing
Regards
Ronak patel

Lync 2013 Desktop does not start on WIndows 8.1

My Office 365 version of Lync 2013 64bit crashes every time I start it. There is no error message just the "Microsoft Lync has stopped working" message with Close option. In further looking for a solution, I found the suggestion to
uninstall the Intel Bluetooth drivers but my system uses Realtek Filter drivers. I have looked  in the event logs and found:
Log Name:      Application
Source:        Windows Error Reporting
Date:          2014-09-11 1:47:20 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      --------Win8
Description:
Fault bucket 85949488684, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: lync.exe
P2: 15.0.4641.1000
P3: 53c5ce3c
P4: KERNELBASE.dll
P5: 6.3.9600.17055
P6: 532954fb
P7: e06d7363
P8: 0000000000005bf8
P9:
P10:
Attached files:
C:\Users\Yves\AppData\Local\Temp\WERCA6B.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\Yves\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_lync.exe_1f7a49ef615ca788e016ddaf8db0d1fb92c4a8e9_00000000_256fdc4d
Analysis symbol:
Rechecking for solution: 0
Report Id: aa908032-39db-11e4-8280-48d224dc5142
Report Status: 0
Hashed bucket: 61000269e077a9a343a6fe9bbb7efc54
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-11T17:47:20.000000000Z" />
    <EventRecordID>143379</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Fedmet-YL-Win8</Computer>
    <Security />
</System>
<EventData>
    <Data>85949488684</Data>
    <Data>4</Data>
    <Data>APPCRASH</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>lync.exe</Data>
    <Data>15.0.4641.1000</Data>
    <Data>53c5ce3c</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.3.9600.17055</Data>
    <Data>532954fb</Data>
    <Data>e06d7363</Data>
    <Data>0000000000005bf8</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
C:\Users\Yves\AppData\Local\Temp\WERCA6B.tmp.WERInternalMetadata.xml</Data>
    <Data>C:\Users\Yves\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_lync.exe_1f7a49ef615ca788e016ddaf8db0d1fb92c4a8e9_00000000_256fdc4d</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>aa908032-39db-11e4-8280-48d224dc5142</Data>
    <Data>0</Data>
    <Data>61000269e077a9a343a6fe9bbb7efc54</Data>
</EventData>
</Event>
A lot of sites suggest to uninstall Intel Bluetooth drive but I does not have Intel Bluetooth.

Go to your computer manufacturer’s website and update all driver packages for your computer, especially:
Audio drivers
Bluetooth drivers
System chipset drivers
webcam drivers
Important Note:
If you use office 64 bit, Lync 2013 must be 64 bit also. {And vice versa, If you use office 32 bit, Lync 2013 must be 32 bit}
Also check answer of Eric to fix this issue
http://social.technet.microsoft.com/Forums/en-US/e8268935-e97c-4033-9a2e-02734b4390bf/lync-2013-client-on-windows-81-stuck-at-starting?forum=ocsclients
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

How can I manually verify autodiscovery configuration for on premise environment from Lync 2013 desktop client?

I have very limited access to an environment (basically just user access). I am documenting the Lync 2013 cilent for this environment. I was provisioned a limited SIP enabled account for testing. Autodiscovery from the Lync 2010 client works, but not from
the 2013 client. I can connect (with some issues) from either 2010 client (autodiscovery) and 2013 client (manually configuring the server). So I want to verify if the Autodiscover is configured correctly to work with the 2013 client or not and if the reason
it fails for me is due to something wrong with my account or if this will happen with other users?
I have checked the lyncdiscoverinternal.domain.com and it resolves and is reachable. I can navigate to https :// lyncdiscoverinternal.domain.com/Autodiscover/AutodiscoverService.svc/root/domain and it returns the information I would think it should
including hrefs to Internal/Autodiscover, Internal/AuthBroker, External/Autodiscover, External/AuthBroker, Internal/Mcx & External/Mcx as well as fqdns for SipClientExternalAccess, SipClientInternalAccess, SipServerExternalAccess & SipServerInternalAccess.
The AuthBrokers urls return what I believe is the expected RemoteService Service pages. The Mcx urls return what I believe is the expected McxService2 Service pages. The SipClientInternalAccess & SipServerInternalAccess fqdns are both resolvable and
reachable. The Autodiscover urls return hrefs for Domain and User. Those Domain urls return the same information as the initial root/domain url and the user url (which I believe is the one that is actually opened by lync during the autodiscover process) returns
what I believe is an expected 401 - Unauthorized: Access is denied due to invalid credentials page.
If I explicitly configure the Lync 2013 client to use the fqdn listed for SipClientInternalAccess, the client will log me in. However on Automatic configuration, it fails to log me in.
One other note is that when I watch with Wireshark, I observed that it is getting another internal server fqdn from somewhere. We'll just say that the SipClientInternalAccess fqdn is lyncABC.domain.internal. When looking at Wireshark and the DNS requests,
I'm also seeing a lync2013ABC.domain.internal that does resolve and is reachable and can also be used as the explicitly listed server in the Lync 2013 client and it will log in. However, that fqdn is not listed in any of the root or domain url replies. So
I'm not sure where it is coming from or how to check that.
Is there any additional information anywhere that can tell me exactly what the behavior of the 2013 client is when trying to find the server to authenticate to and how I can reproduce any missing steps manually to determine what it is identifying as the
login server (if any) since it is obviously not the trying the one listed as SipClientInternalAccess?
Thanks,
Richard

Hi Richard,
To narrow down the issue, you could refer to the following steps first.
1. Delete the Lync client 2013 user profile and registry key.
User profile:
%userprofile%\AppData\Local\Microsoft\Office\15.0\Lync\[email protected]
Registry Key:
HKCU\Software\Microsoft\Office\15.0\Lync\[email protected]
Certificate:
a. Open Windows Certificate Manager. To do this, press Windows + R, type certmgr.msc, and then click OK.
b. Expand Personal, and then expand Certificates.
c. Look for a certificate that's issued by Communications Server and delete it.
2. Upgrade Lync client to the latest update.
3. Check the DNS records(A records and SRV records) again.
Best regards,
Eric

Lync 2013 Address Book and Group Expansion

Hello Everyone,
We have just recently published our Lync 2013 through reverse proxy (TMG).
The following links dialin.schs.sharjah.ae and meet.schs.sharjah.ae are viewable externally. However when we try to browse
https://lyncs.schs.sharjah.ae/abs or
https://lyncs.schs.sharjah.ae/abs/handler and
https://lyncs.schs.sharjah.ae/GroupExpansion/service.svc I get a 403 Forbidden Access Error
But when I try to browse the sites internally Group Expansions works and for Abs I get the same error. Is there any way on how to resolve this issue
Regards,
Sheldon
MVI - Most Valuable Indian

Hi Sheldon,
I'd say TMG issue here. What you should be getting is a prompt for Authentication (from external)
There are a few points to consider..
On the Web Publish Rule - To Tab make sure:-
- that the rule applies to the external web services FQDN (as in Topology builder)
- that the internal site name is the Front End Pool FQDN
- that the "Forward the original host header.." is checked
- that the "Requests appear to come from the Forefront TMG.." is selected
on the Public Name tab add:-
- the meet URL
- the Dialin URL
- the External Web Services URL
- the Lyncdiscover URL
On the Authentication Delegation tab make sure that you select "No Delegation, but client may authenticate directly"
and on the Bridging tab make sure of the port redirects 80 to 8080 and 443 to 4443
On the Listener check the following:-
- Authentication tab set to "No Authentication"
One final comment about TMG is that often even after publishing a rule you may find that it hasn't synced. Once you apply a rule in TMG ALWAYS go to the
Monitoring option and check the status. Don't even bother testing your rule until it says "Synced"
http://lyncsorted.blogspot.co.nz/search/label/TMG
If this helped you please click "Vote As Helpful" if it answered your question please click
"Mark As Answer" | Blog lyncsorted.blogspot.com

[Lync 2013] - Desktop Sharing and taking control

Similar Messages

Maybe you are looking for