I have not opened another ticket, I think we are waiting to see if other users also experience this or if he is a 1-off type situation.Learn about the system requirements for the Cisco Webex Video Platform. They found that a registry key ( HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\AddIns\WebExOI.Addin) was missing on his PC and copying that from another user fixed the issue.Ībout 2 weeks later the issue came back so I'm not sure if an update out desktop engineering team pushed removed the registry again. They tried deleting that so it would rebuild, and he got the same message.
Since I was able to log into his device as myself and the Scheduler worked correctly without the error they thought it was his user profile. Since Exchange is bundled in our office package our PC Support guys didn't want to push a 5GB file over VPN to the director's device. It also worked okay for her up until about a week ago but I can't tie that timeframe to any updates getting you made any progress on your end? It sounds like we have similar environments even though we're seeing different We had opened a TAC case on this and worked with an engineer to see if we could figure out what was happening. It works for her in Webmail, but any installed version of Outlook on any computer produces the browser version error. It works fine for everyone else, but not this one user. Using on-prem Exchange 2016 and "traditional" Office 2016 like Looks like everything is fully patched. Cleared Office cache, recreated Outlook profile, recreated full user profile, verified browser versions are up to date, removed/re-added Add-In on the Exchange side, etc. We've tried similar steps to everything listed above, short of completely reinstalling Office which we plan to do when the user's system is free for a couple hours.
One user of our very small first phase testing is receiving an error about an unsupported browser.
Since this seems to be turning into a "all the problems with Webex Scheduler" thread I'll add my own experience.
0 kommentar(er)
