Author Archive: Kay Poeppelmeier

Connect 9.2.1 and higher, on-premise: Deployment Options during install

When running the installation of Connect 9.2.1 (and higher) when you get to the step “Select Deployment Options” you can specify to deploy the services under “Local System Account” or to specify an existing user account.

 

InstallDeployOptions

One common reason to specify a user account is when using shared storage. The Connect service needs to have access to the network share specified in a later step during installation.

It is necessary to grant this user account “log on as a service” rights, otherwise the Connect, FMS, FMG services set to run under this user account will not start.

Here’s how to grant a user “log on as a service” right.

  1. Go to “Control Panel”, “Administrative Tools”
  2. Expand “Local Policies”
  3. Expand “User Rights Assignment”
  4. Find the Policy called “Log on as a service” and double click on it.
  5. Select “Add User or Group” and add the user account under which you want to deploy the services.

LocalSecurityPolicy LogOnAsService_addUser

 

Alternatively you could also install with the local system account option first, then go to the windows services and change the account under which the service runs from there. This way Windows would automatically assign the missing “Log on as a service” right.

To do so, go to “Server Manager”, “Configuration” and “Services”. Find the “Adobe Connect Service”. Right-click the service name and select “Properties”. Specify the user account / password under the tab “Log On”, when you hit apply you’ll get a message that “Log On as a service” right has been granted to the user account.

viaWindowsServices

 

 

Connect 9.1.x on-premise server – “Send Invitations” checked by default

When creating a new meeting you are asked if you want to send out meeting invitations by email.

In Connect 9.1.x the option to send invitations is selected by default.

If you do not wish to send out invitations for your meetings you have to select “Do not send invitations” every time you create a new meeting.

sendInvitations

You can change this behavior to make  “Do not send invitations” the default when creating a new meeting.

To do so, edit the notify.xsl file which is located in \Connect\9.1.1\appserv\apps\meeting\  ( but please remember to take a backup copy of the file).

1. Open the notify.xsl in an xml-friendly editor such as notepad++

2. Find this section:

<table cellpadding=”0″ cellspacing=”0″>
<xsl:call-template name=”input”>
<xsl:with-param name=”title”   select=”‘send-invitations’”/>
<xsl:with-param name=”name”    select=”‘date-scheduled’”/>
<xsl:with-param name=”type”    select=”‘radio’”/>
<xsl:with-param name=”value”   select=”/results/common/date”/>
<xsl:with-param name=”checked” select=”true()”/>
</xsl:call-template>

<xsl:call-template name=”input”>
<xsl:with-param name=”title”   select=”‘no-invitations’”/>
<xsl:with-param name=”name”    select=”‘date-scheduled’”/>
<xsl:with-param name=”type”    select=”‘radio’”/>
<xsl:with-param name=”value”   select=”‘ignore’”/>
<xsl:with-param name=”checked” select=”false()”/>
</xsl:call-template>
</table>

3. Change “false” to “true” and “true” to “false” to swap the selection.

It should now look like this:

<table cellpadding=”0″ cellspacing=”0″>
<xsl:call-template name=”input”>
<xsl:with-param name=”title”   select=”‘send-invitations’”/>
<xsl:with-param name=”name”    select=”‘date-scheduled’”/>
<xsl:with-param name=”type”    select=”‘radio’”/>
<xsl:with-param name=”value”   select=”/results/common/date”/>
<xsl:with-param name=”checked” select=”false()”/>
</xsl:call-template>

<xsl:call-template name=”input”>
<xsl:with-param name=”title”   select=”‘no-invitations’”/>
<xsl:with-param name=”name”    select=”‘date-scheduled’”/>
<xsl:with-param name=”type”    select=”‘radio’”/>
<xsl:with-param name=”value”   select=”‘ignore’”/>
<xsl:with-param name=”checked” select=”true()”/>
</xsl:call-template>
</table>

 

4. Save the file and restart the services.

5. Check your changes by creating a new meeting. If you encounter any issues, restore the original file.

 

 

Connect on-premise Server: Configure additional ports for RTMP traffic

By default the meeting server (FMS) in Connect binds to port 1935.  Here’s how to add additional ports like port 80 for use with the meeting server.

This should work with all versions of Connect.  I am assuming you would like to use port 80 and 443 in addition to 1935  (all in rtmp, no encryption).
As Connect consists of two servers, the application server (Tomcat) and the meeting server (FMS) you need to configure a second IP address and FQDN in order to bind two services to port 80.  Make sure your new FQDN resolves to the new second IP address. The second IP and FQDN will be used for the meeting traffic.

I am using these values in my setup:

Application Server: connect912.adobe.com – IP 10.1.1.1
Meeting Server: connect912meeting.adobe.com – IP 10.1.1.2

So here we go:

  • Make sure you can ping both names and they resolve to the correct IP addresses.
  • Open the server console and set the new meeting server FQDN in the “external name” field and save your changes.

In my setup this is connect912meeting.adobe.com:

consoleExternalName

 

  • Configure the meeting server to listen on the new IP:Port.

In my setup I am adding port 80 and 443 in addition to the default port 1935.

Open the custom.ini (by deault  in C:\Connect\9.1.1\ if running Connect 9.1.x) and add these lines:

DEFAULT_FCS_HOSTPORT=10.1.1.2:80,443,1935
RTMP_SEQUENCE= rtmp://external-host:1935/?rtmp://localhost:8506/,rtmp://external-host:80/?rtmp://localhost:8506/,rtmp://external-host:443/?rtmp://localhost:8506/

Replace 10.1.1.2 with your meeting server IP address and also make sure the RTMP_SEQUENCE is in one line. Save the changes.

  • Restart the services, FMS and Adobe Connect service.

Once the services are back up and running you should be able to start a new meeting.  If there are no firewall restrictions a meeting should connect on the first port listed in the RTMP_SEQUENCE. In this example port 1935.
To test the connection on the other ports, block outgoing connections to port 1935 on your client firewall.  If the meeting is still open on your client it should briefly disconnect and reconnect on the next available port. In my setup this would be port 80.

You can check which port you are connected to in a meeting by holding down the shift key and clicking “About Adobe Connect” from the help menu (top right in your meeting).

AboutAdobeConnect_RTMPSequence

 

 

update (03/04/2014): 

It appears that with version 9.2 you also need to specify the IP address the application server binds to. By default it binds on 0.0.0.0:80, so on all available IPs on port 80.With Connect 9.2 I have come across an issue where the application server does not properly create a listener when port 80 is used for the meeting server as well.
The easiest way around this problem is to specify the IP in the application server config so it starts a listener on this one IP only.

In the server.xml in \appserv\conf\ find this section:

    <Connector port=”80″ protocol=”HTTP/1.1″
            executor=”httpThreadPool”    
           enableLookups=”false”
               acceptCount=”250″
               connectionTimeout=”20000″
               redirectPort=”443″
               URIEncoding=”utf-8″/>

And add your application server IP address:

    <Connector port=”80″ protocol=”HTTP/1.1″
            address=”10.1.1.1″
           executor=”httpThreadPool”    
           enableLookups=”false”
               acceptCount=”250″
               connectionTimeout=”20000″
               redirectPort=”443″
               URIEncoding=”utf-8″/>

Save the change and restart your services once again.

Meeting fails to load in Firefox under Ubuntu Linux

Some users running Ubuntu Linux and use Firefox may see problems connecting to meetings.

The same meeting loads fine in other browsers like Chrome or Chromium.

This can be related to a Security Certificate not being set for use with websites in Firefox.

Follow these steps to verify and correct this:

1. Open Firefox and select “Edit”, “Preferences”.

2. Select the “Advanced” Tab and click on “Encryption” .

3. Select “View Certificates” to open the certificate manager.

4. Select the “Authorities” Tab.

5. In the list of certificates find the one called “Verisign Class 3 Secure Server CA – G3″.

6. Select the certificate and click “Edit”.

7. Check “This certificate can identify websites” and click OK to confirm your changes.

8. Restart Firefox and retry the connection to your meeting.

 

FirefoxCertManager

 

 

 

Adobe Connect 9.2 upgrade checklist

We’re soon starting to upgrade our Adobe Connect Hosted clusters to version 9.2, the upgrade for on-premise installations will be available soon as well.

Please make sure to go through the upgrade checklist:  http://helpx.adobe.com/adobe-connect/kb/connect-92-upgrade-checklist.html

You can check your upgrade date here: http://www.adobe.com/support/connect/downloads-updates.html

 

Customize Event Registration confirmation message

When a new participant completes the registration form for an Event they are shown the Registration confirmation message.

The default message reads:

“Thank you for your registration request. Your information has been submitted to the event host.”

Here’s how you can customize this message.

  1. Login to Connect and select the “Event Management” tab.
  2. Click on Event Templates
  3. Select the Event Template from the drop-down list.
  4. Select “Edit template”

EditEventTemplate

 

“Edit template” takes you to a new window / tab in your browser where you can edit the template.

EventRegistration_Edit

In this view, select “Event Registration” and right-click on the field where it reads “Registration Form” and “Registration confirmation message […]” as in the screenshot below and select “Edit” in the drop down menu.

rightClickEdit

Hitting “Edit” takes you here:

OnRegistrationConfirmation_dropdown

Select the first item “On Registration Confirmation” by opening the drop down menu. Here you can edit the Registration Confirmation Message text.

Make your changes and click “ok”.

regConfirmation_changeText

To make sure your changes are applied you need to activate the template. You can do this in this floating menu on the right of your screen:

 

CQ_activateTemplate

Once the template is activated the change is applied to all Events based on the template you chose to edit.

 

 

Connect 9.1.2b on-premise – PDF conversion may fail

When uploading a PDF to a share pod in a meeting on an on-premise server version 9.1.2b on some installations the file cannot be converted.

In the access.log you get a message like this:

“Internal error ‘Pdf to swf conversion failed with return code -1073741515′ occured”

If you run into this problem please verify that you have the “Microsoft Visual C++ 2010 Redistributable Package (x86)” installed on your server.

If it is not installed, install it from here: http://www.microsoft.com/en-us/download/details.aspx?id=5555

Make sure to install the 32bit version even if you have a 64bit OS.

If the file still does not convert after successful upload to a meeting, please contact support.

Connect on-premise server: Warning messages in Event viewer, registry connection rejected

On some installations of Connect on-premise in combination with FMG you might observe a large number of regular warning messages for the FMS Edge process in the Windows Event viewer as well as the servers edge.log file.

The message in \Connect\logs\support\diagnostic\edge.00.log would look like this:

Connection rejected by server. Reason : [ Server.Reject ] : Registry connection rejected, this adaptor is _defaultRoot_ and the registry only accepts connections on originhost -

In the Event Viewer you would see this in regular intervals:

event_viewer_registryConnectionRejected

 

If you see these in the logs on your Connect server machine and FMG is hosted on the same machine, do the following:

1. Browse to: C:\Connect\9.1.1\Flash Media Gateway\2.0.1.19_8x8\conf\

or if you run 9.0.x browse to:   C:\Connect\Flash Media Gateway\2.0.1.15\conf\

2. Take a backup copy of the rtmp.xml

3. Open the file rtmp.xml in an XML friendly editor like Notepad++ or Textpad.

4. Locate this section at the top:

<Registrations>
<LegService>
<!-- List of FMS & service names for LegService registry connnections                    -->
<!-- Format is <Server host = "Flash Media server IP/hostname">servicename</Server>        -->
<!-- Please refer to documentations for applicable restriction on the values            -->
<Server host = "localhost">telephony</Server>
</LegService>
<ControlService>
<!-- List of FMS & service names for ControlService registry connections    -->
<!-- Format is <Server host = "server IP/hostname">servicename</Server>        -->
<!-- Sample entry:                                                            -->
<Server host = "localhost">telephony_control</Server>
</ControlService>
</Registrations>

5.  In the above section, modify these two lines:

<Server host = “localhost”>telephony</Server>

<Server host = “localhost”>telephony_control</Server>

to include a port number:

<Server host = “localhost:8506“>telephony</Server>

<Server host = “localhost:8506“>telephony_control</Server>

6. Save the changes and restart the FMG service.

 

 

 

Connect 9.1 on-premise Server – Audio Provider selected by default when creating a new meeting.

With Connect 9.1 when creating a new meeting the option to use an audio profile is preselected if one or more exist under “My Profile” >> “My Audio Profiles”.
This means, if you setup a new meeting it is assumed you also want to use your existing audio profile.

You can read about this change here: What’s new in Adobe Connect 9.1

If you prefer the old behavior and do not want to preselect an audio profile due to various reasons you can change this in the server configuration files.

audio_conference_settings

Please note, this change means you need to modify a file on your server, so please create a backup.

To go back to the behavior of Connect 9.0 and earlier versions follow these steps:

1. Log on to your server machine.
2. Browse to the Connect install directory.
3. Locate the directory \Connect\9.1.1\appserv\apps\meeting\.
4. Take a backup copy of the file “sco_edit.xsl”.
5. Open sco_edit.xsl in an XML friendly text editor such as Notepad++ or Textpad.
6. Go to the end of the file and replace these two lines:


</xsl:template>
</xsl:stylesheet>

with this:

<script>

            document.getElementsByName("inherit-telephony-settings")[0].checked=true;

            noTelephonySettings();

   </script>
</xsl:template>
</xsl:stylesheet>

 

script_view_in_editor

 

7. Save the changes and restart the Adobe Connect Service
8. Verify the changes by setting up a new meeting.

Please note, these changes might be overwritten when you install an upgrade or patch.

 

 

 

Setting Email Sender for all messages to a generic address

This is a way to workaround a mail server blocking emails where the sender and mail server domain do not match.

Before you do this, make sure you have a working backup copy of your database!
First step: make sure the admin email address is set to the generic address you want to use.

You can do this on the database by running this SQL update query:
update PPS_CONFIG set VALUE = ‘genericaddress@mailserverdomain.com’ where NAME=’config-system-email’;

Next switch on the feature to send emails from this address:
insert into PPS_ACCOUNT_FEATURES (ACCOUNT_ID, FEATURE_ID, DATE_BEGIN, DATE_END, RECORDCREATED)
values (7, 84, GETUTCDATE(), ’3000-01-01 00:00:00.000′, GETUTCDATE());

After setting this, emails should be sent in the format:

“genericaddress@mailserverdomain.com on behalf of user@othermailserver.com”