cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
76559
Views
40
Helpful
21
Replies

When sharing a screen/application in WebEx, it shows just as a gray screen for other participants

dpetrovi
Cisco Employee
Cisco Employee

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

21 Replies 21

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

tom.lepsic
Level 1
Level 1

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..

Mark VandeVere
Level 1
Level 1

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.

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:

1. Download the 2.0 MR9 ISO from cisco.com -  cisco-webex-meetings-server-2.0.1.918.B.iso 
2. Once downloaded, just verify the MD5SUM of the ISO file and compare it to the MD5SUM listed - b45dbadccb8af08dd250346a6f725649 cisco-webex-meetings-server-2.0.1.918.B.iso
3. Ensure on your Dashboard that the daily backup is completed successfully (you have to have NFS storage configured on your system for backups and recordings to run. If not ,you can skip this step)
4. Upload the ISO file (cisco-webex-meetings-server-2.0.1.918.B.iso) to the Datastore that CWMS Admin VM has access to.
5. On the CWMS Dashboard, put the system into Maintenance Mode. 
6. Gracefully power off the VMs (In vCenter for each VM select Power > Shut Down Guest).
7. Once the machines are down, take the snapshot of each VM (in vCenter for each VM create a VM snapshot).
8. After snapshots of CWMS VMs are taken, in vCenter, power ON all the VMs.
9. The system will boot into Maintenance Mode.
10. Mount the cisco-webex-meetings-server-2.0.1.918.B.iso image to the CD/DVD drive of the Admin VM.
11. Initiate the update process (Go to Dashboard Admin page, click on the System tab >  Upgrade > Update (minor update).  Click Continue, follow the wizard, and let the update proceed).
12. Once the update is completed and the system is restarted, bring the system out of Maintenance Mode.
13. Verify everything is up and running and test basic functions like accessing the end user page, schedule a test meeting and join it.
 
After thorough testing and confirming everything is running as expected, proceed with removing all the VM snapshots (in vCenter, for each VM ensure to remove the snapshots). This is a mandatory step as having snapshots on the system will cause serious performance degradation! Remove the snapshots within 24h after the update. At the end of the update, you shouldn’t have any snapshots remaining on the VMs.
 
14. Finally you will need to ensure you update Meeting Client and WebEx Productivity Tools client on your end users' machines. You can download the clients ahead of time from cisco.com: cwms-tools-and-clients-2.0.1.918.zip

 

I hope this will help.

-Dejan

Dejan,

 

Thanks for the thorough response; it is very helpful. I am scheduling the work and will let you know how it goes.
 

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.

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