Archive for July, 2014

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

 

 

Information about Connect Meeting Add-in

Adobe Connect Add-in is a version of Flash Player that includes enhanced features for Adobe Connect meetings, such as screen-sharing capabilities. When Adobe Connect Add-in is required, it is downloaded from an Adobe server in a seamless process that is hidden to the user. However, if your organization does not allow employees to download software from external servers, you can host Adobe Connect Add-in on your own server.

We do have few questions regarding the Add-in:
- How the Add-in works?
- What all file rights we need?
- What is the file location?

Below is the answers for all these questions:

- Addin is basically Flash Player (11.9) with some enhancements and additional functionalities:
- Screen share
- Toast windows
- Codecs
-  Audio enhancements

-It requires standard user rights.

-The files are located at %appdata%\Macromedia\Flash Player\www.macromedia.com\bin\adobeconnectaddin
- adobeconnectaddin.exe – The main executable
- digest.s – file used by Flash Player to verify that the addin has not been modified
- meetingconvertor.dll – used to convert PPTX files to PPT on the client side to enhance ppt conversion fidelity
- connecthook.dll – used while screen sharing to allow IPC between shared applications and addin to start/stop share

Value of App data depends on Operating System on which it is installed. For reference : http://helpx.adobe.com/adobe-connect/kb/enable-logging-acrobat-connect-professional.html

Update – CSO – DATE (11 JULY 2014) – Universal Voice Not Connecting for Certain Clusters

11:40am EST – Universal Voice is currently down for customers on the following clusters: (NA1, NA2, NA6, NA8, NA9, NA12).  This affects the ‘audio broadcast’ functionality in Adobe Connect Meeting rooms on those clusters.  This also affects ‘user-configured’ (non-integrated) telephony profiles on those clusters.  Meetings that utilize ‘UV Profiles’ (user-configured) will not have audio.  Meetings that use the ‘integrated’ telephony profiles (telephony adaptors for InterCall, MeetingOne, Arkadin, and PGI) will still have audio, but the ‘broadcast’ will not work.  We are currently working with our Operations team to resolve the issue. You can get full updates on our Adobe Connect Status Page here: https://status.acrobat.com

4:30pm EST - We have identified the issue and applied a fix for the Universal Voice issues that have occurred today in our EQX (SJ1) datacenter.  This was a configuration issue outside of the application that affected the integration with our SIP service.  The team has deployed the necessary changes and done appropriate testing to ensure the system is now stable.

 

Testbuilder Status’ Explained

When setting up an application-level health monitor (blog) on your LTM, you would point to the testbuilder diagnostic page at:

/servlet/testbuilder

As the previous article explains, ‘the testbuilder page will send back the “status-ok” string.  If there is any problem with the Connect server application, then testbuilder will not report the “status-ok” string’.  Expanding on this a little bit, the following (below) are the actual status’ and possible scenarios you may see:

STATUS_OK = 0;
STATUS_CRITICAL = 2;
STATUS_MAINT = 3;
STATUS_TEST = 4;

 

STATUS_OK = 0;
This means the server is fit to work (status-ok). Server status in PPS_ENUM_DATA_HOST table is neither ‘X’, ‘M’ nor ‘T’ and server is initialized.
This is what load balancers should look for health check.

STATUS_CRITICAL = 2;
Server is not fit to work (status-critical). Server is not yet initialized (during start up), or has server status of ‘X’ in PPS_ENUM_DATA_HOST table.
This is also triggered if no connection to database can be made.

STATUS_MAINT = 3;
Server is in maintenance mode (status-maintenance). Has server status of ‘M’ in PPS_ENUM_DATA_HOST table.
Active server can be put to maintenance mode and vice versa.  No new meetings will be run on this server, but currently active meetings will run until ended.

STATUS_TEST = 4;
Server is in “server isolation” mode (status-testing). Has server status of ‘T’ in PPS_ENUM_DATA_HOST table.
Used to put server in separate zone from other servers in cluster. This is hosted feature that is not actively used in production.

Manual LDAP Synchronization

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.

  1. Log in to a Connect server
  2. Open the Administration console (http://localhost:8510/console/)
  3. Navigate to Directory Service Settings > Synchronization Actions
  4. Go to the Perform Directory Synchronization section and click on the Synchronize button.

H.264 encoded FLV not displayed when it is reshared again in share pod

Issue: H.264 encoded FLV not displayed when it is re-shared again in share pod.

Steps to reproduce:

1. Share H.264 encoded FLV in a share pod.
2. Stop sharing (without viewing it completely).
3. Share the FLV again from the share history.

Result:Video bar progresses but the audio and video is not rendered.

Reason: The FLV encoded in H.264 has this limitation that unless initialized from beginning it will not render video (and audio)  frames. When we share it from ‘recently shared content’ it is not initialized from the beginning. Server tries to play it from the last cue point, which causes this issue. If we seek it to a position it starts to play well.
The behavior is not seen in VP6 encoded FLVs.

Workaround:

  1. Seek to start of the recording. Once initialized, we can seek to any point and it will play just fine.
  2. Re-encode the FLV with VP6 codec.