Posts in Category "Seminars"

Last Minute Managing of Large Adobe Connect Hosted Seminars

Currently, as of Connect 9.3.1, Adobe Connect hosted Seminars may launch on regular Connect Meeting server instead of their designated Webinar servers. If Seminar preparation keeps the Seminar room open for an extended period just prior to to the actual Seminar itself, the Seminar may remain on a Meeting server that is not rated for a large capacity Seminar. Simple precautions will avoid this from happening.

In order to avoid this, on the day of the scheduled Webinar, be sure to open the Seminar room only 30 minutes prior to the start of the Seminar session. By opening the Seminar earlier and keeping it open for final editing right up to the start of the Seminar session, you can lock the seminar onto a regular Connect Meeting server rather than on a Webinar server designed for large capacity sessions. While you can certainly spend as much time as needed to prepare your seminar room in advance of the actual session, you should close the Seminar room for at least seven minutes prior to the actual scheduled Seminar session. Seven minutes is the time it takes the Seminar room to process garbage collection from editing and preparation activities before opening up for the real event.

Adobe is looking at ways to automate the transition from a regular Meeting server to a Webinar server with an eye toward  future release. In the interim, just be sure to time your final Seminar preparation to allow for transition to a Webinar server where large Seminar concurrency is supported with robustness.

Adobe Connect Add-in Compatibility with the Google Chrome Browser

Updated January 27, 2015:

Note: This article only applies to Adobe Connect on-premise server deployments. Adobe Connect hosted clients are unaffected.

The Google Chrome browser is currently shipping with two versions of the Flash plugin.  The default PPAPI and also the NPAPI Flash plug-in. The following versions of Adobe Connect installations are incompatible out of the box with the default PPAPI plug-in:

  • 9.1.2
  • 9.1.1
  • 9.0.1 – 9.0.4
  • 8.2.2

PPAPI plug-in incompatibility results in the Adobe Connect Add-in not being detected and launched in Chrome when invoked in a Connect Meeting. Even if the Add-in is installed, the meeting opens in the browser and not in the Connect Add-in. Upon attempting to share ones screen (a Connect feature supported in the Add-in but not in the browser), the following message appears:


Google Chrome, with the release of Version 40, will no longer use their whitelist to allow NPAPI  plugins to run without requiring approval: Chrome users will not be able to use the Adobe Connect Add-in for the above listed versions of Connect. To address this problem, Adobe is patching the following Connect versions for use with Chrome:

  • 9.1.2
  • 9.1.1
  • 9.0.4
  • 8.2.2

These patches will fix the incompatibility problems with the PPAPI plug in. Adobe Connect servers that are not running one of these versions (or a later version) will need to be upgraded to the nearest later version to the one currently installed and then apply the appropriate Connect PPAPI patch.

There should not be any change in the behavior for Flash Player NPAPI in January because Flash Player is not listed among the applications  that are going to be removed in January:

Workarounds until the patches are available:

  • You can attend Adobe Connect Meetings without the Adobe Connect Add-in, however the Add-in is required for enhanced functionality like screen sharing and making offline recordings.
  • Turn off auto-upate in Chrome so that you do not upgrade to a version of Chrome that is problematic.
  • Alternatively you can use any browser other than Chrome with Adobe Connect.
  • Manually enable NPAPI by clicking on the “Plug-in blocked” message in the URL bar and choosing “Always allow plug-ins on [website]”



Note: In April 2015, this will no longer be an option as NPAPI support will be disabled by default in Chrome and Google will un-publish extensions requiring NPAPI plugins from the Chrome Web Store. Google will however provide an override for advanced users in the form of an ‘enable-npapi’ flag and enterprise policy to temporarily re-enable NPAPI.

PDF document does not upload into Adobe Connect

Problem: Adobe Connect could not process this document for viewing. (Either the full document does not upload or some pages of within a document do not upload)



Adobe Connect Hosted/Licensed


Use the “Sanitize Document” Feature to get rid of all the following types mentioned in the image attached below. Depending on the version of Acrobat you are running, you may need to install a trial version of Adobe Acrobat Pro to use this feature.



Avoiding Inaccurate Completion Reports when a Meeting is Part of a Curriculum

When a meeting is part of an Adobe Connect Curriculum, a trainee can click on the Meeting and complete the Meeting task prescribed in the Curriculum prior to the Meeting taking place.



One way to help manage this is to choose the Meeting options to block Meeting access illustrated in the screen captures below:





The Meeting access options may be inconvenient to use, so here is another option to add a Meeting to a curriculum, while at the same time restricting the ability for a trainee to complete the Meeting task prior to the Meeting taking place:

Step one: The first step is to set a date and time under the Meeting properties. Make sure the date and time correspond to when the Curriculum task takes place. Note that this date and time has no effect on when the Meeting can be used. It is strictly an administrative tool to help with Meeting invitations and has no effect on when the meeting can be opened, Meeting persistence, etc. In this example I have set the meeting to October 22, 2014 at 12:45 for 1 hour:



 Step two: Download and unzip the Meeting Curriculum Wrapper:

Note that it is zipped twice to facilitate download:


Step three: Identify the Meeting sco ID from the Meeting that you wish to add to the Curriculum and copy it to the clipboard:

The Meeting SCO is in the Meeting URL:


Note: You can also see the Meeting sco ID by pasting ?mode-xml at the end of the Meeting URL and reading it from the output:


Step four:  Edit the index.htm in the unzipped LaunchMeetingInCurriculum folder by pasting in the Meeting sco ID from the Meeting that you wish to add to the Curriculum. Use your favorite text editor such as notepad or textpad. Where the index.htm reads,  Enter the SCO of the Meeting, Virtual Classroom or Seminar var meetingScoID_str = ‘1660065186’; change the default Meeting sco ID, 1660065186, to the Meeting sco ID of the Meeting that you wish to add to the curriculum, in the case of my example here, the Meeting sco ID is: 502114549. Be sure to save the changes:


Step five: Zip all the edited contents of the LaunchMeetingInCurriculum folder and rename it to represent the Meeting that you wish to add to the Curriculum. This will help you identify it and differentiate it from other Meetings with which you use this wrapper:



Step six: Upload the edited zip file to the Adobe Connect Content Library:




Step seven: Import the wrapper from the Content Library into the Curriculum:


Note: Import options; the wrapper is Content and points to the Meeting:





Step eight: Test the Curriculum item; unless the time and date coordinate with the actual Meeting schedule, the pop up will deter the trainee from gaining premature access to the Meeting and skewing the Curriculum completion report:


 Conclusion: With proper management and administration, an Adobe Connect Curriculum accurately measure the progress and completion of trainees. There are two ways to prevent a trainee from completing a Meeting curriculum task prior to the meeting taking place, the first is to block access to the Meeting and the second is to use the Meeting Curriculum wrapper.

Seminar Session creation might fail intermittently with the “Not Authorized” error for some users

Some users might run into this problem intermittently while trying to create seminar sessions. This is not a very widespread problem; it seems random and is certainly rare.

Problem :

Unable to create a Seminar Session:  It fails intermittently with “Not Authorized” error.

Environment : Connect Hosted

Version : 9.2.x

Method via which issue can be produced :

1.    Login to your Connect application as a Seminar Host.
2.    Go to Seminar > Seminar Sessions > Click “New Seminar Session”
3.    Select a Seminar room with which to create a Session.
4.    Enter name of the Session and click Create.

It might fail with “Not Authorized” error intermittently. Most if the time it works fine and a session is created successfully.

Workaround to avoid the issue :
Instead of creating a Session from the Seminar Sessions tab, schedule a session from the seminar room itself.

Solution :

This is fixed in Adobe Connect 9.3. Check your account upgrade date here.


In Connect Meeting, Clicking “Don’t show this dialog again” has no Effect on the Tips Dialog

Issue: Upon startup, Tips for using Adobe Connect for Hosts is displayed. After clicking on “Don’t show this dialog again” and dismissing the dialog, the next time Connect is launched the dialog is again displayed.


This is caused by a problem storing the changes locally available to flash applications on client machines. Here are workaround steps:

  1. Open the connect meeting in the IE/Firefox. You can append launcher=false to the meeting URL to open it in browser: <url>/?launcher=false
  2. Right click on the meeting and select Settings; the  flash dialog GUI will appear:


3. Click on the folder icon:


4. Check that the variable for storage is allowed and is greater than 0 (make sure the slider is not all the way to the left) and also check to see if the Currently used variable is equal to the allowed value.

5. If the Currently used variable is showing 0 then close this dialog and again right click on meeting and open the Global Settings. The following dialog will appear:


6. Click on Local Storage Settings by Site:


7. Make sure that the Adobe Connect server is listed there and it is allowed as depicted in the third column. If it is not allowed, then allow it using the drop-down menu.

Here are some additional references that may be helpful:

Adobe Connect Offline Recording Option Captures and Records Local Client Screen Activity

Adobe Connect Offline Recording Option Captures & Records Local Screen Assets:

While in the process of creating an offline recording in Connect, the recording will capture extraneous desktop application activity if Windows is in Non-Aero mode

To stop extraneous recording,  turn on the Aero theme: Control Panel\All Control Panel Items\Personalization – choose any Aero theme.


This workaround will limit the offline recording to the Connect Meeting archive.

Here is the related forum discussion for reference:

Ensuring that Email Generated by Adobe Connect Servers is Received

There have been more than a few incidents reported on the topic of email messages from Adobe Connect servers not getting delivered. These include messages generated by the Adobe Connect Events module as well as system email messages such as that generated by changing a password.

The first thing to avoid to prevent this problem is that of using special characters in the host’s name. This is scheduled to be fixed in Connect 9.3, but currently, in 9.2, if you place a comma in the Event host’s name such as Frank D., El Presidente’  it will cause an error identified in our server logs by a messaging exception.

The second thing to avoid is inviting over 20,000 participants to an Event. This generates an operation size error and causes problems with email messages being sent out. We also plan to address this ceiling tentatively in Connect 9.3.

With specific reference to Adobe Connect Hosted accounts, we just made the following change to ameliorate email problems: As of April 28th, 2014, administrative email notifications sent from Adobe Connect servers will now be coming from instead of This will help by disassociating Connect-generated email from that of the Acrobat domain which could be potentially blocked by virtue of its identification with document storage. We also made some internal changes to the way the Connect servers handle email and we worked with our Web infrastructure partners to insure that Connect generated email was not being treated as SPAM on the Web.

There is a bit of a conundrum here. If Adobe Connect Events email invitations are sent out in massive mailings to those who perceive the email as SPAM, then the Adobe Connect servers could be tagged as producing SPAM by those end-user recipients. An overzealous Events manager may cause Gmail and other providers to treat Adobe Connect email as SPAM. When an Event that is capped at 500 participants sends out 5000 email invitations, it is expected that many recipients will at best ignore the inbound email traffic and many more may consider the traffic to be a nuisance. We are investigating possible approaches to ameliorate this problem and plan in 9.3  to add an opt-out option for Events invitations that will offer a convenient alternative to any SPAM reply option for recipients to invoke.

We love large Events and Adobe Connect handles them very well; this is a case when our success can potentially lead to some problems. Currently the Adobe Hosted Service is green for SPF record checks.  We pass all major email providers and are not blacklisted according to common checker tools on the internet.  This should resolve the lion’s share of current email issues and the upcoming changes in 9.3 will serve to harden this capability for future Events.

Be Aware of the Closed Captioning Pod Defaults

Last week we found out that Caption Colorado changed their IP address and port number for the Closed Captioning pod downloadable from the Connect Exchange Website. Here is the direct link to the Connect version 9 Closed Captioning Pod

The new Caption Colorado information includes:

If you are experiencing any trouble with the Closed Captioning pod while using it in a Connect Meeting with Caption Colorado, please set your host to “” and to port 11100 in the adobe pod. Note that the new IP,, depending on your infrastructure’s network security settings, may need to be white-listed.

For an updated user’s guide referencing the Closed Caption Pod, see this PDF:



Estimating the Size of Archive Meeting Recordings

I was recently asked if I had any test data showing how big a recording becomes based on the use case during the Connect Meeting being recorded. While plenty of anecdotal information exists,  I thought it prudent to begin a list of use cases and show what the size was after five minutes of each use case. This article will be a work in progress as I add different use cases in order to offer various concrete examples to use as a basis to estimate recording size based on what is being recorded, whether multiple Video pod camera feeds or screen-sharing or VoIP, etc. Among its purposes, this exercise will help meeting hosts to avoid exceeding the 2GB limit on Adobe hosted clusters for recording size.

Most relevant among the variables considered is the notion that recording size is affected by the streams present in the meeting being recorded. Typically a Video pod with VoIP (640X480) shared per hour will result in an FLV of around 200MB. Sharing a screen in a meeting (1680X1050) will result in an FLV size of around 150 MB. PPT/PPTX files uploaded to a meeting room and displayed while recording will not play a significant part in recording size because the recordings link to external content rather than contain that content intrinsically. For example,  a meeting with two Video pod streams could have recording size of around 400MB and a meeting having a single Video pod stream with VoIP and screen-sharing could end up around 350MB. The actual results may differ as the screen resolution of the publisher, the type of sharing and the amount of movement are all variables that can affect recording size: If there is little movement on screen or in the Video pod stream, the recording size will be less than it would be with a lot of movement.

Here are some concrete examples to use for planning; each recording is approximately five minutes in length:

A meeting with a single video feed for the Presenter to display and scroll through an uploaded PowerPoint file while using integrated telephony:Title: Recording Size Test_0
Type: Recording
Duration: 00:05:31
Disk usage: 8335.3 KB



A recording of a meeting with six video feeds and an uploaded PowerPoint file
Title: Planning Troubleshooting and Support Meeting Room _15
Type: Recording
Duration: 00:05:48
Disk usage: 13873.8 KB



A recording of a meeting with four video feeds and screen sharing an application with normal activity
Title: Planning Troubleshooting and Support Meeting Room _16
Type: Recording
Duration: 00:05:56
Disk usage: 21660.8 KB


More examples to follow.