Posts in Category "Seminars"

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 actually can create seminar rooms, but setting the correct permissions for them to do so is not intuitive; Connect administrators may need to set the additional permissions in Connect Central and the workflow is semitransparent at best. There is a minor intermittent bug that may be the source of some confusion if not chagrin. Let’s examine the workflow.

As an Administrator, create a typical account with just Meeting and Seminar Host permissions to test:

sem

Log in with the account that only has Meeting & Seminar Host permissions 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.

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.

Deleting Corrupted Ghost Meetings on Adobe Connect On-premise Servers

Deleting Corrupted Ghost Meetings on Adobe Connect On-premise Servers

Perhaps due to network outages or hardware failures, etc., there are rare occasions when the Adobe Connect database may become disconnected from the Adobe Connect server while active Meeting sessions are ongoing. It is prudent to avoid database outages while Connect is in use and to publish maintenance schedules so that Meetings are not in session when the database is taken offline for administrative reasons. In most cases when the database is disconnected, once it is reconnected, Connect will be fine and all Meetings will be functional upon full recovery of all systems. In the rare instance, that a Meeting is corrupted through a database outage and cannot be deleted through the Connect Central GUI, you may need to manually delete the Meeting room from the content library directory structure and possibly also from the database itself. If you see displayed at the corrupted Meeting URL, a gray window without any menu or pods, or if you see the following error when you hit a corrupt Meeting URL, you may need to manually delete the Meeting:

Request Not Processes” – “For further assistance, please refer to the Adobe Connect support center or contact Adobe Connect support

If the Meeting cannot be deleted through the Connect Central GUI, delete the content folder for the corrupted Meeting. You can identify it by its sco ID in the Connect\content directory:

content.fw

Restart the Connect and FMS services. If that fails to remove remnants of the corrupt Meeting from the database, try recreating the folder mentioned, (even with empty content), then attempt to delete the room again. If that fails, you may need to delete the Meeting references from the database manually:

sco: update pps_scos set disabled = getUTCdate() where SCO_ID=XXXXX

Note: XXXXX represents the actual sco ID of the meeting.

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 16, 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
  • 9.0.0.1
  • 8.2.2.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:

chrome-addin.fw

Google Chrome is also planning to remove support for NPAPI, so Chrome users may 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:  http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html

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]” http://www.chromium.org/developers/npapi-deprecation
    • chrome-enable.fw

 

 

 

 

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)

NA5

Environment:

Adobe Connect Hosted/Licensed

Resolution:-

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.

 

image001

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.

curr-mtg.fw

 

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

block-mtg.fw

 

block-in-mtg-menu.fw

block-in-mtg.fw

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:

meeting-date-time.fw

meeting-date-time-1.fw

 Step two: Download and unzip the Meeting Curriculum Wrapper: https://platinum.adobeconnect.com/lmfc/default/launchMeetingInCurriculum.zip

Note that it is zipped twice to facilitate download:

cur-unzipped.fw

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:

meeting-sco.fw

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:

meeting-sco1.fw

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:

index-sco.fw

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:

zip-contents.fw

zip-contents1.fw

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

upload.fw

upload1.fw

upload2.fw

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

curr.fw

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

curr1.fw

curr2.fw

curr3.fw

curr4.fw

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:

curr5.fw

 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.

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

dialog.fw

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:

flash1.fw

3. Click on the folder icon:

flash2.fw

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:

flashglobal.fw

6. Click on Local Storage Settings by Site:

flashglobal2.fw

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:

http://www.macromedia.com/support/documentation/en/flashplayer/help/help02.html

http://helpx.adobe.com/flash-player/kb/disable-local-shared-objects-flash.html

http://help.adobe.com/en_US/FlashPlayer/LSM/WS6aa5ec234ff3f285139dc56112e3786b68c-7fff.html

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.

aero.fw

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

Here is the related forum discussion for reference: https://forums.adobe.com/message/6629306#6629306