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

Connect on-premise: Seminar licenses show as expired following an upgrade to version 9.3.1

Some customers may run into this issue following an upgrade from Connect 9.0.0.1 to 9.3.1 if you use seminar licenses.

After the successful upgrade all seminar licenses show as expired. Re-applying the license file in the console does not help and you see the following message in the debug.log:

[03-03 13:41:48,526] http-80-24 (ERROR) Exception caught in DBRows.populate(), e=java.sql.SQLException: [Macromedia][SQLServer JDBC Driver][SQLServer]Ambiguous column name ‘DATE_END’.
[03-03 13:41:48,527] http-80-24 (INFO) 1ms spid:64 com.macromedia.airspeed.db.SQLServerUtilityQueries.setIsolationLevel(Disable Isolation)
[03-03 13:41:48,527] http-80-24 (ERROR) Exception thrown
java.sql.SQLException: [Macromedia][SQLServer JDBC Driver][SQLServer]Ambiguous column name ‘DATE_END’.
at macromedia.jdbc.sqlserverbase.ddcg.b(Unknown Source)
at macromedia.jdbc.sqlserverbase.ddcg.a(Unknown Source)
at macromedia.jdbc.sqlserverbase.ddcf.b(Unknown Source)

[…]

To resolve this, run the following query on your database to change the SQL compatibility level:

sp_dbcmptlevel ‘breeze’, 90

If your Connect database is named something other than “breeze”, then put the correct name of the database in the query.

Now re-install your license file one more time.

 

This is also the solution to a related issue: http://blogs.adobe.com/connectsupport/licensed-after-upgrading-to-connect-9-1-exception-occurs-when-clicking-on-meeting-tab/

Please contact Support if you still encounter issues.

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.

On-premise Server: Add user-agent info to access logs

If you run your own Connect server you may want to add user-agent information to the tomcat access logs.

Here’s how to add the information:

1.  Take a backup copy of the server.xml located in \Connect\9.x\appserv\conf\.

2.  Open the file in an XML friendly editor and locate the line:

 

<Valve className=”org.apache.catalina.valves.AccessLogValve” directory=”../../logs/tomcat”
prefix=”tomcat_access.” suffix=”.log” pattern=’%h %l %u %t %m “%U” %{BREEZESESSION}c %s %b %T’ resolveHosts=”false”/>

 

3.  Edit the line to include %{User-Agent}i . It should look like this:

 

<Valve className=”org.apache.catalina.valves.AccessLogValve” directory=”../../logs/tomcat”
prefix=”tomcat_access.” suffix=”.log” pattern=’%h %l %u %t %m “%U” %{BREEZESESSION}c %s %b %T %{User-Agent}i‘ resolveHosts=”false”/>

 

4. Restart the Connect service and load any page of Connect.

The log output in \Connect\logs\tomcat\tomcat_access.-date-.log should now include user-agent information:

127.0.0.1 – – [23/Feb/2015:11:39:45 +0000] GET “/common/help/en/support/meeting_test.htm” breezbreezhvc7xdcgu5h3cqwm 200 16703 0.017 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0

 

Enjoy logging!

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