NOTE: The following steps only apply when Adobe Connect is configured for user authentication through an LDAP Directory Service.
Under normal circumstances LDAP synchronization is configured to synchronize automatically on a regularly scheduled basis. However, it is occasionally necessary to synchronize at times other than during the regularly scheduled periods. The following steps are for performing a manual Directory Service synchronization.
Please be aware that performing an LDAP synchronization can be resource intensive on the Connect side, and it is highly recommended that these steps not be performed during times of normal system activity.
- Log in to a Connect server
- Open the Administration console (http://localhost:8510/console/)
- Navigate to Directory Service Settings > Synchronization Actions
- Go to the Perform Directory Synchronization section and click on the Synchronize button.
We have opened a bug around a recent undocumented change in the Web Services API actions.
The action, sco-session-seminar-list, which prior to 9.2.2 returned all seminar sessions for which the authenticated user had Host permissions, now requires the alternative action: sco-seminar-sessions-list. Use sco-seminar-sessions-list instead of sco-session-seminar-list until we resolve the open issue around this change; we have logged bug number: Watson: 3772441.
Consider this sample action (wherein FQDN designates your fully qualified domain name) as an example: Instead of running the action: https://FQDN/api/xml?action=sco-session-seminar-list&sco-id=1369951914 to get all the seminar sessions under the seminar license with the sco-id of 1369951914 you ought to run this API instead: https://FQDN/api/xml?action=sco-seminar-sessions-list&sco-id=1369951914
To list all the sessions that are linked to a meeting room under one license, put a filter on the source-sco-id as in this example action: http://FQDN/api/xml?action=sco-seminar-sessions-list&sco-id=sco-id-of-the-seminar-license&filter-source-sco-id=sco-id-of-the-meeting-room
Problem: While making recording offline, an error message “Not authorized” is seen in spite of the user being part of the meeting host and administrator Groups.
Reason: Chances are user is not the host for that particular meeting, so we need to add the user as a host in that meeting using “Edit participant” Tab.
1) Click on the name of the meeting room, for which we are not able to make recording offline.
2) Go to Edit participants
3) Select the impacted users name
4) Click on “Add”.
Impacted users name will appear in the list of Current participants,
5) select the name
6) click on set user role
7) select “Host”
Problem: Some of the users get confused on the various access levels given to the users on adobe connect account.
Reason: An administrator is not actually the administrator as it also requires other group’s membership to perform some tasks. Given below is a diagram that explains the access levels.
Click on image to enlarge.
A Super admin on adobe connect is a user having group memberships of meeting host and administrator.
Problem Description : Is Adobe Presenter old and new versions compatible with Adobe Connect 9.2 ?
All versions of Presenter should work with the Web Application (e.g Content, Courses, Curriculum’s, etc ). However the issue is with Meeting as Connect version 6 and version 7 are AS2- based(Action Script 2) Meetings, thus content will launch in Connect 6/7 Meetings only. Similarly, AS3 based content will work with Connect version 8 and 9 Meetings.
Action Script version comparison :
• C6 & C7 = Presenter up to 7.0.6. AS2
• C8 &C9 = Presenter 7.0.7 and higher. AS3
Hope this helps in understanding some concepts, relates to Presentations published using Presenter on connect.
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 email@example.com instead of firstname.lastname@example.org 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.
When invoking a browser-based email client to invite participants to a Connect Meeting from within a Connect Meeting you will see this error message unless you first make the browser-based email your default email service:
Sending a browser-based email invitation from within a Connect Meeting is possible if you first make the browser-based email option your default email program. As an example, you can use the instructions at the following links to make Gmail your default email program :
Note that once you enable a browser-based email client and invoke it from within a Connect Meeting, the behavior will be different based on whether the host issuing the invitation is using the Connect Meeting addin or the Flash Player. In the addin it will look like this:
Using the Connect Meeting addin, invoke the invitation: Meeting> Manage Access & Entry > Invite Participants
See how the invitation is fully populated with important details:
Following the same procedure using the Flash Player instead of the addin (?launcher=false) also works, but with an abbreviated invitation message:
Here are the specifications for the MP4 conversion; they are similar to our FLV specifications albeit with better compression:
- Resolution: 1024X768
- Frames Per Second: 8 FPS
- Video Bitrate: 1024kbps
- Codec – AAC (Advanced Audio Codec)
- Profile – Main@3.1
- Bit Rate – ~55Kbps (VBR)
- Channels – 1 (Mono)
- Sampling rate – 44.1Khz
In Connect 9.2, there are two ways you can allow a ‘participant’ to turn their camera on – but each has slightly different results.
Enable Video – this option gives full rights to the video pod, same as a host. Or in other words, if you enable Video for any participant, that particular participant will get presenter rights over the Camera pod just like in case of Enhanced rights over any pod.
Enable Webcam For Participants – this doesn’t give overall video pod rights (the participants can’t Force Presenter View, or choose who is in the main Filmstrip, etc.), but it allows them to turn their camera on. However you cannot be selective with this option – everyone will be able to turn on their camera.
FYI, If you “enable video” for a participant and then “enable webcam for participants” you lose the ability to “disable video” for any already enabled participant until you first “Disable Webcam for participants”
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 “captionedtext.com” and to port 11100 in the adobe pod. Note that the new IP, 220.127.116.11, 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: http://platinum.adobeconnect.com/cc/