Some things that can be ruled out are local problems with the installation, the user is having this issue on all 25 servers and 250+ other users do not have any issue, to make it even more challenging we had her try to use Skype on a laptop, same issue! We compared the AD account+attributes with some of her colleagues and we do not see any difference (exept she has a SIDhistory object), also we cleared the appsense profile and all redirected + cached folder making this a fresh logged on user. 24308, time stamp: 0x5be85cc7įaulting application start time: 0x01d4cf4f310f4f80įaulting application path: C:,Program Files (x86),Microsoft Office,root,Office16,lync.exeįaulting module path: C:,windows,SysWOW64,ntdll.dll
2193, time stamp: 0x59b28539įaulting module name: ntdll.dll, version. In 2018, Microsoft boasted about the fact that Microsoft Teams is now at feature parity with Skype for Business Onlinea. Skype for Business Online will no longer be available and integration with third-party audio providers will cease. and that is it, in the event log the following is seen.įaulting application name: lync.exe, version. In July 2019, Microsoft officially announced the end-of-life for Skype for Business would be July 31, 2021. The problem is when the client is launched, the splash screen appears. The user can use Outlook locally and connect to OWA + use the Skype online, Office2016 is connected to the account. The environment is Server2008R2,Citrix Xenapp 6.5,appsense based using thin clients, Office365 uses OKTA as authenticator, the user profile is mandatory (spoofed + folder redirection) and is removed after logoff (so a clean user profile at each logon) After a migration from Lync,Exchange to Office365 we have 1 user that is unable to connect not even launch Skype for Business.
0 kommentar(er)
