Posts in Category "General"

Restricting Upload File Types for Connect On-Premise Deployments

Adobe Connect supports the following file uploads; on-premise deployments are able to restrict any of these as needed:

“…the following formats: *.ppt, *.pptx, *.flv, *.swf, *.pdf, *.gif, *.jpg, *.png, *.mp3, *.html, *.mp4, *.f4v or *.zip. Please refer to the documentation for valid contents for zip files.”

filetypes.fw

You can modify the breezeUI.js  javascript to restrict file types. Be sure to backup before editing.

breeze/appserv/common/scripts/breezeUI.js

var acceptedTypes = {};
acceptedTypes[‘jpeg’] = ‘jpeg’;
acceptedTypes[‘jpe’] = ‘jpe’;
…..
acceptedTypes[‘ppt’] = ‘ppt’;
acceptedTypes[‘pptx’] = ‘pptx’;

Remove the file type that you want to restrict and then make sure the GUI in Connect Central reflects the change in en.xml:

Backup and edit: 9.x\appserv\apps\lang\en.xml file

<m id=”new-content-help”>
The file should be one of the following formats:
*.ppt, *.pptx, *.flv, *.swf, *.pdf, *.gif, *.jpg, *.png, *.mp3, *.html, *.mp4, *.f4v or *.zip.
Please refer to the documentation for valid contents for zip files.
</m>

Note that this procedure only applies to on-demand content uploaded to the content library in Connect Central, For uploads to the meeting room, go to the Compliance and Control setting in Connect Central: Administration>Compliance and Control> Share Settings.

sharecandc.fw

Adobe Connect 9.4 Update

9_4 image

Adobe Connect 9.4: http://www.adobe.com/products/adobeconnect.html

Adobe Connect 9.4 for webinars, learning and meetings: Learn more at http://blogs.adobe.com/adobeconnect/2015/03/introducing-9-4-2.html

Adobe Connect On-Premise customers may download the 9.4 updater from here: https://helpx.adobe.com/adobe-connect/kb/connect-90-patches.html

The Connect Meeting Add-in with Chrome is not recognized on the Meeting Test Page

When running the Connect Meeting test link from the troubleshooting option under the help button in any Connect Meeting, there are times when the Connect Meeting Add-in with Chrome is not recognized:

chromeaddin.fw

https://platinum.adobeconnect.com/common/help/en/support/meeting_test.htm

chromeaddin1.fw

chromeaddin2.fw

chromeaddin3.fw

If you place your mouse over the highlighted icon, you will see the oddly stated message: An unsandboxed plug-in was allowed to run running on this page.

chromeaddin4.fw

Allow the add-in and place its domain into the exception list in Chrome and refresh the browser.

chromeaddin5.fw

The reason for this behavior is that the Chrome PPAPI and Adobe Connect interaction (even after the Connect PPAPI patch as well as with the non-affected Connect versions later than 9.1.2) is changed nonetheless. See the related blog article: http://blogs.adobe.com/connectsupport/adobe-connect-add-in-compatibility-with-the-google-chrome-browser/ The PPAPI plugin blocks the communication between swfs and other Unsandboxed applications.

The granting of access permissions is domain-based. The setting is called Unsandboxed Plug-in Access; when you launch the Meeting test page it fails to detect the Addin. If you had installed the Addin from that test page then in the process of the installation, Chrome would also prompt for permission and it will save it once you allow it. Any subsequent launch of test page or any page from that domain will always identify the Adobe Connect Addin correctly. If you again open the Meeting test page from some other Adobe Connect domain then it will fail to detect the Addin even if Addin is installed because this new domain may not have Unsandboxed Plug-in Access.

Once a domain is allowed Unsandboxed Plug-in Access, then any page from that domain will detect and launch the Adobe Connect Meeting add-in.

Note: One customer wrote code to automatically install the latest Adobe Connect Meeting add-in in the browser. It worked for all browsers except Chrome. See this tech-note for details: https://helpx.adobe.com/flash-player/kb/unsandbox-localconnection-chrome.html

Resolved: CSO – DATE (5 FEB 2015) – InterCall Telephony Outage Affecting Connect Audio

This is resolved as of 1705 EST 15Feb2015

We are actively working with our partners at InterCall to solve an intermittent telephony outage.

This issue is causing InterCall based audio conferences to fail to start in Adobe Connect Meetings.

The root cause is under investigation by InterCall.

You may check http://status.acrobat.com/ for updates.

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,

Empowering Your Seminar Hosts to Create Seminar Rooms

The question comes up on occasion, “Why can’t my Seminar Hosts create seminar rooms?”

The answer is that they have been affected by an intermittent bug, which we realize may cause some confusion, if not chagrin. There is a workaround available, which we’ve outlined below.

Workaround:

As an Administrator, create a typical account with Meeting and Seminar Host permissions (as a test):

sem

Log in with that account and this is what you may see in the Shared Seminars directory. There is no ability to create a Seminar and the Seminar license is not viewable:

sem1

If you switch back to the administrative account log-in, you will see the Seminar license sub-directories:

sem2

sem3

Resetting the permissions on the Seminar license sub-folder using the to “Reset to Parent” button in the Connect Central GUI has no effect on the permissions. You must manually add the folder permissions to the Seminar license sub-folder instead of using the “Reset to Parent” option:

sem4

Once the Seminar license sub-folder permissions are manually edited, the Seminar Host is able to view and manage the Seminars including the ability to create new Seminar rooms under the Seminar license sub-folder:

sem5

The workaround is very easy so this is a low priority bug and we will address it in a future release. At the time of the writing this tech-note, the shipping Connect release is 9.3.1.d.

Microphone Stops Transmitting Audio After Running the Audio Setup Wizard in a Meeting

Problem: Microphone stopped transmitting audio after running audio set up wizard in an Adobe Connect Meeting.

Note: This is being tracked by Adobe engineering under case: 3916223. It will be fixed in a future release.

Here are the steps that will make the problem occur:

  1. Open the Meeting room.
  2. Enable the microphone within the Meeting room.
  3. Select the microphone and checked that microphone  is working.
  4. Now run the Audio Setup Wizard.
  5. You will noticed that microphone is highlighted however there is no audio emitting.

Result: The microphone stops working after running the Audio Setup Wizard

The expectation: Microphone should not stop working,

This is a bug with Flash Player 11.9 which the Adobe Connect Add-in uses. This has been fixed by the Flash Player Team in its later releases and we need to integrate that fix into the Adobe Connect Add-in.

There are two instant workarounds:

  1. Right-click and open flash player microphone settings -simply opening the microphone settings causes the microphone to work again.
  2. Mute and again unmute the microphone by clicking on the microphone icon in the meeting client.

Apache Tomcat and Adobe Connect Upgrades

The question sometimes comes up: May the Apache Tomcat server that is bundled with Connect be upgraded separately without upgrading the entire Connect server?

The Adobe Connect server architecture includes a number of different integrated components. We generally do not recommend upgrading any of the components parts except as part of an officially released Connect upgrade, updater or patch. This includes Tomcat, FMS, AEM and JRE updates.

The primary reason for waiting for a full Connect installer instead of upgrading individual components separately is to benefit from the quality assurance test battery that the Adobe Connect engineering team puts each release through. Our quality assurance process is intense and always culminates in a full internal production roll-out to all of Adobe well ahead of external production deployments.

Customer attempts to upgrade specific integrated components of Connect are unsupported and can result in bringing down an on-premise Connect server and recovery may require re-installation or restoration from a backup image with commensurate risk of data loss. The very best one could hope for with any such out-of-band component upgrade attempt would be an operational but unsupported Connect server configuration that has bypassed all the regular performance/longevity tests done as part of Connect releases. The risk is as high as it is unnecessary.

As of the writing of this tech-note the current shipping version of Tomcat with Connect version 9.3.1c is TC 7.0.52.0. The target release for TC 7.0.54 is Connect version 9.4 these tests are ongoing.

To see what versions you are running of Connect and of all its components, simply append version.txt to the published domain name of your Adobe Connect server. For example: https://platinum.adobeconnect.com/version.txt

To review the latest Adobe Connect on-premise server updaters, see: http://helpx.adobe.com/adobe-connect/kb/connect-90-patches.html

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.