07-17-2015 11:32 AM - edited 03-17-2019 05:22 PM
This is a new issue reported on WebEx SaaS and CWMS. The issue is caused by a new security patch from Microsoft. Any PC with this patch applied will experience this issue.
https://support.microsoft.com/en-us/kb/3069392
Current workaround is to uninstall this KB from the PC.
On CWMS side we have a new defect filed: https://tools.cisco.com/bugsearch/bug/CSCuv36151
This defect is resolved in CWMS 2.5 MR5 Patch 1 available on cisco.com (cisco-webex-meetings-server-2.5.1.5051.B.iso) and the new WebEx Meetings client will be introduced. Keep in mind that this Patch 1 can be applied only on top of 2.5 MR5 version. In case you have 2.5 MR4 or earlier version, you need to first update to 2.5 MR5 and then update to 2.5 MR5 Patch 1.
New set of 2.5 MR5 Patch 1 clients is available: cwms-tools-and-clients-2.5.1.5051.zip
This defect is resolved in CWMS 2.0 MR8 Patch 1 available on cisco.com (cisco-webex-meetings-server-2.0.1.839.B.iso) and the new WebEx Meetings client will be introduced. Keep in mind that this Patch 1 can be applied only on top of 2.0 MR8 version. In case you have 2.0 MR7 or earlier version, you need to first update to 2.0 MR8 and then update to 2.0 MR8 Patch 1.
New set of 2.0 MR8 Patch 1 clients is available: cwms-tools-and-clients-2.0.1.839.zip
This defect is resolved in CWMS 1.5 MR5 Patch 1 available on cisco.com (cisco-webex-meetings-server-1.5.1.509.A.iso) and the new WebEx Meetings client will be introduced. Keep in mind that this Patch 1 can be applied only on top of 1.5 MR5 version. In case you have 1.5 MR4 and earlier version, you need to first update to 1.5 MR5 and then update to 1.5 MR5 Patch 1.
New set of 1.5 MR5 Patch 1 clients is available: cwms-tools-and-clients-1.5.1.509.zip
Here is the official Field Notice: http://www.cisco.com/c/en/us/support/docs/field-notices/640/fn64001.html
07-24-2015 05:11 AM
Hi Tom,
If your WebEx Site isn't patched yet, removing the application and re-installing it won't be of help.
Until your WebEx Site is patched, the only workaround is to uninstall the KB.
Once your WebEx Site is patched and KB installed on the PC, please test it as that might be sufficient and you ca avoid administrative overhead and reinstalling the client.
-Dejan
07-23-2015 08:40 AM
Thank you Dejan,
Called the WebEx help desk 1.866.229.3239, they were able to determine that the patch hadn't been applied to https://globalfoundries.webex.com , and gave me the contact information for our site admin, who could get the patch applied..
09-14-2015 04:47 AM
Dejan,
I am preparing to upgrade as we are currently on 2.0.1 .205.B-AE.
It appears I can go direct to 2.0 MR8 Patch 1, then,
2.5(1), then,
2.5-MR1Patch1
Resolution should occur in 2.0 MR8 Patch 1 and the rest are for good business practice.
Do you have any idea how long per server (250 license version) the upgrades will take? I ask, as I have to schedule change control windows and have never done these upgrades on this system previously.
Also - While I am reviewing Admin documentation for preparation, I am curious if there is any requirement for engaging Licensing TAC as part of any of these upgrades.
09-14-2015 05:03 AM
Hi MArk,
If you are on 2.0 MR2, you first need to update to 2.0 MR8 and then apply Patch 1. That would take two minor updates. However, 2.0 MR9 is already released, so you can actually update from 2.0 MR2 directly to 2.0 MR9. MR9 addresses this issue as well, and you only need to run minor update once.
Minor update normally takes an hour, but you should ensure you do all the prerequisites to ensure your roll back can be executed smoothly in case of any issues.
Here are the instructions for MR9 update:
I hope this will help.
-Dejan
09-14-2015 06:47 AM
Dejan,
Thanks for the thorough response; it is very helpful. I am scheduling the work and will let you know how it goes.
09-23-2015 05:41 AM
Dejan,
Spot on order of implementation; this is a fantastic thread and incredibly helpful to anyone dealing with this issue. I had to get TAC involved due to dbreplication issues that stalled the upgrade, but once that was resolved everything went exactly according to plan.
Thanks for your assistance to me and the community.
09-23-2015 05:44 AM
Thank you for the update, Mark. I am glad you were able to perform the update successfully, after DB replication issues were fixed in your HA environment.
I am glad I was able to help.
Kind regards,
-Dejan
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide