Posts in Category "Meeting"

The begin screen-sharing button in Connect is obscured by the task-bar when resolution on a laptop screen is set to 1366×768

The begin screen-sharing button in Connect is obscured by the task-bar when resolution on a laptop screen is set to 1366×768. You will see this happen, if you use a laptop with 1366×768 screen resolution, attempt to share your screen in Connect. The effect is that the start screen sharing button is hidden behind the Windows task bar at the bottom of the screen:

Small Res - High DPI

The expected behavior is for the start screen share button to be accessible.

The workaround options are to either move the task-bar or change the screen resolution in order to expose the button, but since the start screen-sharing button is already highlighted or in focus albeit unseen, if you simply hit the enter key, screen-sharing will begin. Keep in mind that 1366×768 is the default screen resolution for some laptops.

Note: This is only reproducible in high DPI mode and it is not limited to the Connect Screen-sharing dialog. See how the basic operating system “Save As” dialog exhibits similar behavior at the same resolution:

Small Res - High DPI Windows Dialog

Security scans flag FMS used in Adobe Connect

Multiple Adobe Connect on-premise customers have informed us that some of their security scans are reporting that the version of FMS used in Adobe Connect is unsupported. There are no known open security issues in the version of FMS used in Connect today. The FMS components that are embedded in Adobe Connect on-premise deployments are fully supported under the maintenance and support agreements for Adobe Connect.  If any vulnerabilities are discovered in these components of Adobe Connect, they will be addressed per the guidelines of those support agreements.

Webcam might not get displayed in full screen mode on Tablets/iPads in Connect meeting

There might be certain circumstances when you might not be able to view the webcam shared in a meeting in full screen mode. You might come across this situation on some mobile devices when using an Adobe Connect meeting room.

Situations under which this might occur :

  • Enter a meeting as a host from a desktop pc and start sharing your camera
  • Join the same meeting as a participant from a tablet or iPad device
  • Click on the webcam option from the left
  • The webcam video remains in small size and does not become full screen automatically

 

iPad

 

Affected Environments Discovered until now  :

Connect 9.3/9.4 Hosted/Licensed Environments

Mobile app 2.3 on tablets or iPad

Additional Information : 

This has been discovered as a bug and in under investigation by our Mobile Engineering.

Please keep tracking this page for latest updates and status. Bug#3963153.

 

Monitor Resolution Settings with Adobe connect

The following are best practices mentioned for screen resolution with Adobe Connect:

1. Set the screen resolution settings to 1024×768 pixels for screen-sharing or application or window sharing.

2. Lower screen resolution results minimal usage of network bandwidth.

3. If you are using a very large screen the optimum settings may be 800 x 600.

Mini Control Panel in Connect Meeting

Problem:
Upon creating a Meeting, if you deactivate the Mini Control Panel from Meeting >Preferences > Screen Share> Uncheck ‘Enable Mini Control Panel for Screen Share’, those settings will not propagate from a template to new meetings. If for example, you move the Meeting with the deactivated Mini Control Panel to the Shared or My Template folder and create a new Meeting, the Mini Control Panel will be activated in the new Meeting room.

Workaround:
Deactivate the Mini Control panel in the Connect Meeting room in every session.

Bug:
This is a reported bug and is pending review.

Connect Meeting or Event Email is not received by Gmail Users

Problem:
Meeting invitation emails are not received by users of Gmail.

Environment:
Adobe Connect version – 9.3 and above
Email domain- Gmail

Reason:
There are a number of reasons why Connect email messages may not arrive in your inbox. Some of them are mentioned below:
– Emails from domain ‘admin@adobeconnect.com’ are marked as SPAM
– Filters are created in the GMAIL account settings forcing the Meeting invitation emails sent to Trash and deleted automatically.
– Forwarding is enabled in GMAIL account Settings > Forwarding and POP/IMAP.

Solution:
Check to make sure that GMAIL is not blocking Connect email:
1. Ensure email from domain ‘admin@adobeconnect.com’ are not marked as SPAM:
   -Sign in to Gmail.
-Click the down arrow in your search box. A window appears to specify your search criteria.
-Fill in the search field with email address ‘admin@adobeconnect.com‘.
– At the top of the search window, click on the drop-down menu under “Search”> select Mail & Spam & Trash.
– Click Search Mail button.
-Look for the message in the search results displayed.

2. Disable Forwarding or if it is enabled, then ‘Keep Gmail’s copy in the inbox’ is selected:
   -Sign in to Gmail.
-Click the drop-down arrow of the wheel icon 5 >Click settings > Click ‘Forwarding and POP/IMAP‘> Click the radio button ‘Disable forwarding‘.
6

-Note: If ‘Forward a copy of incoming mail to‘ is selected, then select ‘Keep Gmail’s copy in the inbox’

7

 

-Click 8 button.

3. Ensure that if POP is enabled, then ‘Keep Gmail’s copy in the inbox’ is selected:
   -Sign in to Gmail.
-Click the drop-down arrow of wheel icon 5 >Click settings > Click ‘Forwarding and POP/IMAP‘> Click radio button ‘Disable forwarding‘.
-UnderWhen messages are accessed with POP‘ select ‘Keep Gmail’s copy in the inbox’
10
4. Ensure there are no filters created in the GMAIL account settings forcing the Meeting invitation emails sent to Trash:
   -Sign in to Gmail.
-Click the drop down arrow of the wheel icon 5 >Click settings > >Click ‘settings‘ > Click ‘Filters’.
-Select any Filter created with the email address ‘admin@adobeconnect.com‘> Click Delete.
12

Adobe Connect Meeting Hangs on Connecting in the Safari Web Browser

Problem:
Adobe Connect Meeting hangs on connecting in Safari Web Browser.

Environment:
Operating system- Mac OS X 10.7.4, 10.8, 10.9 & Windows 7, 8, 8.1
Adobe Connect version – 9.3 and above
Web Browser- Safari

Reason:
When safe mode is enabled in the Safari Web Browser it prevents the Adobe Connect Add-in from launching. This is a Sandbox restriction. The respective Adobe Connect domain should be enabled in order to launch the addin in Unsafe Mode.

Solution:
In order to disable the sandbox restriction, refer to the steps mentioned below:
1. With the website open (e.g., akash.adobeconnect.com), Choose Preferences from the Safari menu.

  1. Select Manage Website Settings in the Security tab of the Preferences panel.
  2. Select your website (e.g., akash.adobeconnect.com) from the list of “currently open websites.”

4

 

    4. Select Run in Unsafe Mode from the pop-up menu.

    5. In the subsequent alert, click Trust.

    6. Click Done, and close the Preferences panel.

We recommend stopping Safari and launching it again after making the Security Preferences change.

Stop Sharing Button On IE Is Not Available Any More.

Description : We use to get this button on IE when we share the screen.

StopSharinghowever now this button is no longer available.

Reason being it interfaces with the DWM (Glass effect of windows 7+).

DWM : Stands for Desktop Window Manager Click here

We used to support Windows XP which had no Glass effect and thus it was not a problem. On windows 7 we used to switch the DWM off before starting the screen share. Window 8 onwards the DWM cannot be programmatically switched off and thus this button was causing problems. Many applications change the Glass area and IE is one of them. Others include Chrome, FireFox, Office etc. In case the applications change the Glass area then it’s a matter of timing to Display the button or the custom title bar the application draws.

This was actually a bug 2943337 due to which the button

StopSharing

Intermittently disappears. The bug is only reproducible with the applications which have custom title bars. Ex. Real Player/Office Apps/Live messenger and media players. With the Office 2007 applications the title bar is custom drawn and thus it intermittently draws over the button and it disappears. This only happens with skinned title bars, Skinned apps try to redraw their title bars so button disappears until we redraw again.

The “Red Button” never worked for 64 bit processes. This will also not work for any apps which have skinned title bar as i said earlier. Moreover this feature will not work if the process in question is sandboxed (Acrobat for example).

Yes downgrading IE will help probably but it’s not something we can recommend in good faith as it will expose the users to all kinds of security bugs. (Not recommended)

o    Windows 8 and onwards the button is not even an option as DWM can’t be switched off by programs programmatically and the button itself has issues when DWM is on

o    As of today this button has been disabled permanently.

Hope this helps those users who are expecting the red buttons on their IE when sharing the Application or Windows and not desktop using Adobe Connect Meeting Room,

Thanks,

XML API TIPS: Moving Archives That Have Been Repaired

One common workaround that customers do (or Adobe support may do on behalf of customers) to fix recordings that have some sort of sync or playback issue, is to download the archive (recording) zip, potentially run it through a repair tool, and then re-upload the zip package back to Connect as a content object in the ‘Content’ directory.  A common request may be to move that archive from the Content directory, to another location or even back underneath the Meeting’s ‘Recording’ directory.  The problem is that with failed recordings (recordings that didn’t fully process) and/or re-uploaded recordings, they will not have a ‘date-end’ parameter for the sco, like normal recordings do.  So when you try to (for example) move the archive to the original Meeting’s Recordings directory (which can really only be done using the API), you will get the following error:

API Call = Sco-Move:

/api/xml?action=sco-move&sco-id=xxxxxxx&folder-id=xxxxxxx

where sco-id = the sco-id of the re-uploaded archive
where folder-id = the sco-id of the original meeting (which is also the sco-id of the Recordings directory for that meeting)

Result:

<results>
<status code=”invalid”>
<invalid field=”sco-id” type=”string” subcode=”recording-is-in-progress“/>
</status>
</results>

This is because the sco does not have a date-end param/value.  You can see this by running the sco-info call on the sco-id.  You will see no date-end.

What you need to do before you can move the sco, is set a date-end param using the sco-update API.  You would set the date-end value to some date in the past.

Here is an example:

/api/xml?action=sco-update&sco-id=xxxxxxxx&date-end=2015-01-01T12:00:00.000-04:00

Result:

<results>
<status code=”ok”/>
</results>

Now, when you do a sco-info on that sco you should see the date-end param and value.

You can now also move the recording to it’s desired location (say back to the Meeting’s recording directory):

/api/xml?action=sco-move&sco-id=xxxxxxx&folder-id=xxxxxxx

Result:

<results>
<status code=”ok”/>
</results>

Troubleshooting Microphone and Camera Issues in Connect Meetings

When both the web camera and the microphone do not work in an Adobe Connect Meeting, it is often caused by a restriction setting in the mms.cfg file.

The mms.cfg file it is found in the following directories:

  • Windows 32: C:/Windows/system32/Macromed/Flash (32-bit Windows)
  • Windows 64: C:/Windows/SysWOW64/Macromed/Flash (64-bit Windows)
  • MAC: MainDisk:Library:Application Support:Macromedia

Renaming or deleting the mms.cfg to mms.old is one way to solve the issue, but often it is more prudent (less intrusive) to edit the file. Open the mms.cfg in any text editor and look for the line:

AVHardwareDisable

Delete the setting AVHardwareDisable from mms.cfg and save the file. This setting deliberately prevents the Meeting SWF from gaining access to cameras and microphones on the Meeting client.