Posts in Category "Technotes"

Publishing PowerPoint Presentations in Connect Meetings

There are different techniques that a Connect content author or Connect Meeting Host may employ to publish PowerPoint content in Adobe Connect Meetings. This article discusses them and how they differ and how to choose the correct option and avoid common pitfalls. The four basic techniques are:

  • Direct upload or drag and drop into a Connect Share Pod
  • Upload to the Connect Content Library and then link to the Meeting Share Pod
  • Publish to the Connect Content Library using Adobe Presenter and then link to the Meeting Share Pod
  • Publish locally using Presenter to a zip package and upload to Connect

I will summarize each of these and then compare them and offer some tips to help make sure that the published converted SWF closely matches the original PPTX.

The first and perhaps most commonly used option by Meeting Hosts is to upload a PPTX directly to a Meeting room Share Pod. The ease and simplicity of this approach certainly accounts for its popularity: You can simply drag and drop a PPTX presentation into the Share Pod or navigate to the source PPTX and upload it.



Drag and drop is pictured above. As the PPTX is dropped into the Share Pod from the local client, the boarder around the Share Pod will appear with a yellow highlight.


File conversion begins as soon as you drop the file into the Share Pod.


The PPTX is converted and ready for viewing as shown above.


You may also browse to the PPTX file locally from the Share Pod menu drop-down: As a Connect Meeting Host or Presenter, click the down arrow in a Connect Meeting Share Pod and choose “Share Document” as shown above.


Choose “Browse My Computer” (We will discuss content in the shared library anon).


Browse to the PPTX locally and select it.


The size of the file and bandwidth available will determine the amount of time it takes to upload.


Likewise with conversion.


The PPTX is converted and ready for viewing.


Uploading to the Content library is also a common method of Publishing a PowerPoint to Connect. This technique provides a URL for on-demand playback of a the PPTX as well as a single source for use in multiple Connect Meeting rooms. Multiple Connect Meeting rooms may share a presentation from the same source in the Content Library thereby simplifying editing and version control.


Browse to the Content Library in Connect Central and choose “New Content” as shown above. Note that a Meeting Host will have access to “My Connect” by default but may need to request access to “Shared Content” and “User Content” folders depending on prior account-wide administrative permissions set.


Browse to the desired PPTX on your client or share.


Select the desired PPTX upload.


Name the Presentation in Connect Central, create a custom URL and summarize the content for administrative reference if desired.


There will be a delay while the content is processed; see the spinning wheel in the upper left.


Once completed, the active URL and summary will be displayed.


To use the Presentation uploaded to the Content Library in a Connect Meeting, simply point the share pod to the Content Library and link it to the meeting.


It will appear instantaneously in the Connect Meeting as it is already uploaded to the Connect server.


The third means of uploading a presentation to Connect employs Adobe Presenter. This is the richest and most accurate PowerPoint conversion option. Presenter integrates with Connect, in fact, Connect had its start as Presenter: Presidia and Breeze 3.0 were originally based on PowerPoint on-demand content publishing to SWF. The integration of Flash Communication Server in Breeze 3.0.8 led eventually to the current Adobe Media Server and the Tomcat Application server platform along with such feature rich integration as Adobe Media Gateway for telephony and Adobe Experience Manager for Events management. Presenter has a long history and it is a very rich on-demand learning tool:


Once installed, Presenter appears as a menu option in PowerPoint and you can drive publishing to Connect in a number of ways.



Out of necessity, here I will be intentionally terse and ignore a plethora of Presenter features and focus only on using Presenter to publish PowerPoint content for use in a Connect Meeting. The dialog above is under Adobe Presenter>Presentation menu items in PowerPoint with Adobe Presenter installed.


The dialog above shows Presenter publishing options, among them is Adobe Connect which pushes the published Presentation to the Adobe Connect Content Library. Presenter is able to publish to any Connect server to which the author has access and permissions by its domain name.


Presenter launches a browser to log into the Connect Central Content Library.


By default Presenter will log into the Connect Central “My Content” folder belonging to the Presenter Author.


Fill in the customer URL option if desired and the summary fields.


Publishing may take a few minutes depending on the size of the PPTX file.



Once complete the active URL is available along with the summary.


It is now available as on-demand content and can be used from the Content Library in a Connect Meeting.


From the Connect Meeting room, choose the Share Pod drop down option and browse to the Content Library. Here I am using the “My Content” folder as the repository.


The published presentation is available in the Connect Meeting Share Pod.


The fourth method of publishing a PPTX to Connect is to first publish locally as a zip package using Presenter and then upload it to Connect.




Within PowerPoint under Adobe Presenter >Presentation, choose “Publish” and set the publishing options to “My Computer” and the Output options to “Zip package”. Click “Publish”.


The conversion process may take a few minutes.


By default it will publish the zip package to: \Documents\My Adobe Presentations\


In the Connect Central Content Library, choose New Content.


See that among the supported upload file types, a zip package is listed.


Browse to the locally published zip package; in this case it is: \Documents\My Adobe Presentations\Large\


Add the details in the Connect Central Content Library and click Save to begin the upload.


The published active URL allows access to the on-demand Presentation.



In the Meeting Share Pod the Presentation is accessible from the Content Library.

You may also directly upload the Presenter published zip package from the author’s client to the Connect Meeting Share Pod and ignore the Content Library as shown below:




The presentation is available for use in the Connect Meeting Share Pod.


Choosing the best presentation publishing option:

Once the PowerPoint presentation is selected, converted, and uploaded by whichever means, it is prudent to review it to check for any delta between the uploaded content and the original PPTX. Deltas are usually in one of two forms:

  • Select fonts do not match
  • Tables or bullet formatting does not line up as expected

With reference to custom fonts such as certain esoteric mathematical symbols, this article may help: Tips on Mitigating Connect Server-side PowerPoint Publishing Deltas

Using Adobe Presenter to publish, effectively eliminates any font discrepancies as all publishing is done on the author’s client where presumably all fonts are installed and are available to facilitate accurate conversion.

When uploading a PPTX to the Connect Central Content Library without Presenter, a Connect server-side version of Presenter, called Producer, facilitates the conversion process invoking the fonts available server side. If a font is used in the PPTX that is not available on the server, Producer will choose the closest font available on the Connect server to the original font.

Note: Adobe Connect hosted and ACMS customers who wish to have proprietary fonts installed on their Connect accounts  should contact the Connect Support Team to discuss the process.

When uploading a PPTX directly to a Connect Meeting room Share Pod, server-side Producer is not invoked. The client-side is leveraged and Microsoft Office should be installed on the client as PowerPoint client-side helps facilitate the conversion.

This warning message may appear when uploading a PPTX to Connect:


This warning is most common when Mac users who do not have Microsoft Office installed on their clients, attempt to upload a PPTX directly to an Adobe Connect Meeting room. There are not any client-side assets to facilitate conversion.

This tech-note is relevant: Best Practices for Sharing PPTX Files on Adobe Connect

With specific reference to portions of tables missing from graphs, often this can be mitigated by saving a PPTX as  PPT and re-uploading it to Connect.

A PPTX may also be locked down and further editing prohibited. This will affect conversion of the PPTX because conversion to SWF in Connect is a form of editing.




PowerPoint menu options to Protect the Presentation prior to uploading may cause a delta in the converted uploaded Presentation.



The surest way to have the richest and most accurate PPTX to SWF conversion is by using Adobe Presenter on the author’s client. The next most accurate is to upload to the Connect Content library and invoke server-side Producer for conversion. The quickest way is to simply upload directly to the Meeting Share pod but be sure to have Microsoft Office  installed on the client to help mitigate any delta. Be sure to upload and test well in advance of the Adobe Connect Meeting.

New Adobe Connect Support Blog Subscription Option

Now you can stay on top of the new articles and posts by subscribing to the Adobe Connect Support Blog. Simply go to the Adobe Connect Support Blog home page and enter your email address and check off the categories about which you would like to be notified. Click “Subscribe me” and you will begin receiving  regular updates:




Adobe Connect 9.3 Concurrent Learner Licensing Updates

Adobe Connect 9.3 Concurrent Learner Licensing Updates

As we released Adobe Connect 9.3, we began to more accurately track Concurrent Learner licensing usage (i.e., licensing of the Adobe Connect Training Module), with reporting available in the “Reports” section of Adobe Connect Central to provide specific usage metrics.  With increased accuracy of concurrency measurement introduced in version 9.3, you may reach your concurrency limits more quickly due to this change.  Here is an FAQ around this update:

Users are Unable to join /enter Meeting Room

Environment: Hosted


1. Forgot password/password does not work

2. Don’t have a user ID and password to get into a meeting


1. Try using the Forgot your password link to set a new password. If this Doesn’t work contact your account administrator to verify access for the account.



2.If you don’t have an user ID and password to get into a meeting contact your Connect Administrator to request the same.

Guest logins are also an option for meetings, but must be approved by the Meetings Host. With private meetings, the Meeting Host must approve guest login requests.






Creating an open access meeting where Participant don’t require approval to join.

Environment: Hosted

Issue: In large meeting/seminar rooms if the meeting is created using the access type “Only registered users and accepted guests may enter the room” then the host approves each guest’s entry request to allow them in the meeting.


Solution: To avoid this situation always select the access type “Anyone who has the URL for the meeting can enter the room

  •        Go to Meeting > New Meeting


  • Enter the required Meeting Information and  select access type as  “Anyone who has the URL  for the meeting can enter the room”


  • In case you need further assistance contact Adobe Connect Support for help.

Note: If you choose the access level to ‘Anyone who has the url can enter the meeting’, you might experience a security risk as well, as any unintended user who gets the url can also try to join the meeting and create disruptions, which would be problematic to the rest of the attendees. 

Record Meeting option is disabled in Meeting Room


Reason: Only Adobe Connect Administrator has the rights to disable/enable the Record Meeting Option in Meeting Room depending on the requirement/needs.

Environment: Hosted

Solution:  To enable Record Meeting option in Meeting

  • Go to Administration > Compliance and Control > Recordings and Notice


  • Now uncheck the option Lock recording settings for all meeting


Note: If you are not able to access Administration tab contact your Adobe Connect Account Administrator.

Administrator joins/enters meeting room as a participant

Reason: In Named Host pricing model user should be a part of Meeting Host group in order to enter the Meeting room as a Host. You will not be able to enter the Meeting room as a Host if you are member of only the Administration Group.

Solution: 1. Check your Group Membership

  • Go to My Profile > Group Membership



If you don’t see Meeting Host listed there then follow below mentioned steps.

2. In order to be the part of the Meeting Host group Go to Administration > Users and Groups


  • Select Meeting Hosts Group and then click on Information


  • Click on View Group Members


  • Select your Name and click on Add to add yourself to the Meeting Host Group


  • Once you are the part of the Meeting Host group , your name will appear under Current Group Members


Note: If you are still getting the same issue contact Adobe support for help.

Connect Console Values Populate to Wrong Profile in the sip.xml File

Issue: When installing FMG as part of an on-premise Connect deployment, the fresh installation of FMG includes many default profiles in the sip. xml file. When you enter values from Connect console (port 8510 locally on the server), those values are populated to the first profile that is listed in sip.xml (sipPhone) and not to the correct sipGateway profile which is called from the workflow.xml file.

The expected behavior is that the values from Connect console should update the sipGateway profile rather than the first profile in sip.xml

Workaround: The Adobe Connect Support team is using currently approaching this problem from one of two possible ways:

  • You may copy a sipGateway profile from a vertsion of FMG prior to version 2.x and paste that into FMG 2.x.
  • You may call sipPhone profile from workflow.xml

Note: In FMG prior to version 2.x, sipGateway was the first profile listed in sip.xml.  The workflow.xml file checks the input  number and on the basis of that chooses the profile from sip.xml. With default FMG settings it will be using ‘SipGateway’ most of the time. This is scheduled to be fixed in Connect 9.3.

SSL Configuration Checklist for Connect with AEM-based Events

This supplemental checklist alongside the  Adobe Connect installation guide and the SSL Configuration guide, will help expedite your SSL implementation of Connect with AEM-Events:

1. Always begin with a fully functional installation of Connect and AEM-based Events before adding SSL; Do not attempt to secure a server that is not fully tested to run all features without SSL: A server running all features in the clear with no problems manifested is the only place to begin.

2. Decide whether to use hardware-based or software-based SSL and obtain appropriate public certificates and FQDN’s. If needed, see Mohit’s excellent instructions to generate CSRs. If you are using software-based SSL, stunnel can either be installed locally or on a separate server. If you are using hardware-based SSL you will want to refer to the relevant third-party documentation along with that provided by Adobe. For F5 BIG-IP LTM, the following articles along with this blog article and the resources aforementioned will help:

For information about stunnel installation options with Connect 9, see Jim’s blog post on Adobe Connect and 9.1 stunnel installation options. Within the installation folder, under  \Adobe Connect\Adobe Connect\Merge_Modules, we provide the installer for  stunnel-4.53.  From there, you can install Stunnel 4.53 for your SSL deployment. Adobe QE has tested stunnel version 4.56 collocated with Connect – installed within the Connect installation directory. These days it is arguably prudent to use the latest security option tested. Depending on the version of Connect you are running, if you wish to use stunnel locally, then you would create and/or populate the stunnel directory under the root install directory: Connect\9.1.2\stunnel.

Click on this thumbnail diagram below to see what it would look like with a hardware-based SSL accelerator:


Click on this thumbnail diagram below to see what it would look like with stunnel collocated with Connect:


The rest of this checklist & summary will assume stunnel is being used collocated with Connect, but the configuration variables will apply to hardware-based external SSL acceleration options as well and even a casual glance back at these diagrams will help you infer the differences.

The sample file editing offered herein will be based on the single server stunnel example depicted in the diagram above.

3. Four FQDN’s are required: This is how our working example FQDN list would appear in a host file.


4. Four certificates (or a wildcard certificate) is needed; here is the list of certificates for SSL following our example:


Note: These are depicted in our working example as a wildcard certificate: If the certificates are not trusted public certificates, then meeting rooms will not open; self-signed certificates will not work with meeting unless they are installed on all clients. Place the certificates into the stunnel installation directory: \Connect\9.1.2\stunnel\

5. Backup and edit the stunnel.conf file: in the \Connect\9.1.2\stunnel\ directory to set up the four VIPs and pools:

stunnel.conf for four servers on one
; Protocol version (all, SSLv2, SSLv3, TLSv1)
sslVersion = all
; Some performance tunings
socket = l:TCP_NODELAY=1
socket = r:TCP_NODELAY=1
; Service-level configuration
; incoming vip for https (to secure Connect Application Traffic)
; ip address of the server with stunnel on it
; listens on port 443
accept =
; ip of the connect server
; send the unecrypted request to port 8443
connect =
; Certificate info for Connect cert key in stunnel root
cert =
key =
; incoming vip for fms (to secure Connect Meeting Traffic)
accept =
; ip of the fms server
; Send unencrypted request to 1935
connect =
; Certificate info for Connect meeting cert key in stunnel root
cert =
key =
; incoming vip for CQ-Author (to secure AEM-based Events Authoring)
accept =
; ip of the CQ Author server
; Send unencrypted request to 4502
connect =
; Certificate info for CQ Author cert key in stunnel root
cert =
key =
; incoming vip for CQ-Publisher (to secure AEM-based Events Publishing)
accept =
; ip of the CQ Publisher server
; Send unencrypted request to 4503
connect =
; Certificate info for CQ Publisher cert key in stunnel root
cert =
key =

6. Next backup and edit the custom.ini file: By default, the custom.ini will point to 4502 and 4502 for CQ Author and Publisher respectively; you must change the links to reflect https rather than http and also change the  names to the correct FQDNs and also enable SSL for Connect with these following entries:


7. Next backup and edit the server.xml file; in the \appserv\conf\ directory; uncomment two sections depicted here to enable SSL:

<Executor name=”httpsThreadPool”

<Connector port=”8443″ protocol=”HTTP/1.1″

Note: Be sure to test the server.xml file for correct editing by opening it in a browser and viewing any syntax errors.

8. After configuring the stunnel.conf, the custom.ini and the server.xml file for all four server instances, stop all five the services in the following order:

  • Adobe Connect CQ Author
  • Adobe Connect CQ Publisher
  • Adobe Connect Server
  • Adobe Flash Media Server
  • stunnel

9. After all services are completely stopped, start all five services in reverse order; do not cheat and just restart each one successively.

  • stunnel
  • Adobe Flash Media Server
  • Adobe Connect Server
  • Adobe Connect CQ Publisher
  • Adobe Connect CQ Author

10. Open a browser on the Connect server; go to localhost:4502 and log into CQ5 Author as an administrator and edit the URL

  • Select CRXDE Lite on the menu list on the right side of the screen
  • Go to: content>connect>c1>jcr:content
  • Scroll to the serverURL line
    • Edit the URL for https

11. Open a browser on the Connect server and go to localhost:4503 and log into CQ5 Publisher as an administrator and edit the URL

  • Select CRXDE Lite on the right menu list
  • Go to content>connect>c1>jcr content
  • Scroll to the serverURL line
    • Edit the URL for https

12. Open a browser on the Connect server and go to localhost:4502/system/console/configmgr and log in as an administrator and edit the author externalizer name and statistics URL

  • Scroll to and edit the Day CQ Link Externalizer and edit the hostname value to reflect the FQDN of the Author server
  • Scroll to and edit the Day CQ WCM Page Statistics and edit the localhost:4502 URL to reflect the FQDN of the Author server and HTTPS

13. Open a browser on the Connect server and go to localhost:4503/system/console/configmgr and log in as an administrator and edit the publisher externalizer name and statistics URL

  • Scroll to and edit the Day CQ Link Externalizer and edit the hostname value to reflect the FQDN of the Publisher server
  • Scroll to and edit the Day CQ WCM Page Statistics and edit the localhost:4503 URL to reflect the FQDN of the Author server and HTTPS

14. Stop all services and and restart as shown in steps 8 & 9 or reboot the server

15. Log into Connect and test all features including the Events module.

Troubleshooting appendix:

  • Check to make sure all five  services are running and start any that are not running.
  • Once all the services are up, click on the stunnel.exe icon in the stunnel directory and insure that stunnel runs without errors
    • If stunnel.exe throws an error then examine the stunnel.conf for syntax problems
    • If stunnel.exe starts successfully then look elsewhere for problems
  • If  Firefox browsers Fail to Connect when stunnel is used to secure Adobe Connect, then double check to be sure that the
    • sslVersion = all
    • fips = no
  • To make certain the help files are served via SSL, follow the instructions in Jim’s blog article: Changing the Help Links to use HTTPS://
  • Make sure there is not a passphrase on stunnel: see Jim’s blog article Adobe Connect Stunnel prompting for passphrase when server/services restarts
  • If stunnel does not start with Connect upon reboot, this technique will help: Stunnel does not Startup with Connect
  • Depending on the version of Connect you are running, you may need to add the certificate to the java CA certificates in Connect in order to allow images in the AEM-based Events module to appear in Connect. Ignore this step unless you are running Connect and even then, if at all possible, simply use a later version of Connect instead as this issue has been fixed and this workaround is made superfluous for later versions:
    • For, export and then import the SSL certificate: Log into Connect and click on the lock in the URL line to the left of HTTPS and click the button in the pop-up: More Information>View Certificates>Details>Export to export the SSL certificate. Save the certificate in the jre\bin directory in the root install directory for Connect: Connect\\jre\bin
    • Use the command prompt to complete the importation: F:\Connect\\jre\bin> keytool -import -trustcacerts -alias connect -file certificate-name -keystore cacerts
      • The default password is changeit.
      • Overwrite any existing certificate.
      • The italicized alias connect is a variable
      • The italicized certificate-name must match the name of the certificate
      • When importing the cert to cacerts, you need to specify the path to the correct cacerts location.
        • Otherwise you just end up with the cacerts file in the same location from which you launched the keytool
        • In Connect <install-drive>:\Connect\\jre\lib\security\cacerts
        • Note: –import command works, but isn’t listed under keytool –help; it should be –importcert