Webex Windows 7 64 Bit Download
Manda Ulibarri
A new wrinkle to the issue. We started a trial webex account so that we could create meetings and can test joining them. We have no issues joining these meetings This leads me to believe that the vendors\companies who are hosting the webex meetings may be using an older version of webex that may not support windows 10 clients.
I was able to verify that changing the user agent worked for us. However, I did notice that I had to hit F12 again after getting the error, and then it reloaded and started the meeting. This was also with the latest Meeting Client pre-installed, that may have helped.
The Firefox 64-bit browser is not supported for starting or joining a meeting. We recommend that you use The Firefox 32-bit browser or another browser for WebEx until Firefox 64-bit browser is fully supported.The Firefox 64-bit browser cannot be shared in a meeting.
Sharing Windows apps is not currently supported.Application sharing and screen sharing are supported, except that all Windows apps are treated as one application, so if you share one Windows app, you will automatically share all Windows apps.You cannot share the Edge browser in a meeting.When connecting to a remote computer with Windows 10, the local screen will not be blacked out.In Remote Support, a customer service representative cannot access a shared application when the remote Windows 10 computer is locked. To avoid this problem, make sure the automatic lock feature is turned off if you need to perform diagnostics while the remote user is away from the computer.The Windows applications are not listed in the Add Application dialog box in Access Anywhere or Remote Access.If Meeting Center attendees try to save Universal Communications Format (UCF) files to their local computers and have opened the Save Document dialog box, and then the host turns off the option that allows users to save files, the attendees are still able to save the UCF files.
When controlling a Mac using WebEX on Windows, there is no way to send "control + c" to break out of terminals. The windows control key maps to the Mac command key, the windows alt key maps to the Mac alt key, but the Win key does not map to the Mac control key, as you'd expect it to.
The 'm' character shows up on WebEX, which leads me to believe that WebEX is doing some kind of translation to the keystroke. I have verified in the main window and key history windows that the script is indeed sending the proper vk+sc.
Do you guys have any ideas on how I might overcome this problem? I was thinking that maybe there might be some way of hooking into WebEX to force it to do things differently, but I don't know. It's a long shot, but solving this would make my life so much better. I've filed tickets with Cisco and they're response is basically "Derr.. I don't know what you're talking about, I'll escalate". Rinse and Repeat.
4a15465005