We have just published a technote regarding Adobe Connect support for Windows 8.
Please review the technote here:
http://helpx.adobe.com/adobe-connect/kb/windows-8-support-connect-8.html
We have just published a technote regarding Adobe Connect support for Windows 8.
Please review the technote here:
http://helpx.adobe.com/adobe-connect/kb/windows-8-support-connect-8.html
The 9.0.2 Patch for Licensed deployments is now live and can be downloaded from: http://helpx.adobe.com/adobe-connect/kb/connect-90-patches.html
Releases notes are here: http://helpx.adobe.com/adobe-connect/kb/connect-902-release-notes.html
We have just published a technote regarding the Release Notes for the upcoming 9.0.2 Adobe Connect release.
Please review the technote here:
http://helpx.adobe.com/adobe-connect/kb/connect-902-release-notes.html
We have just released a technote regarding the upcoming 9.0.2 Adobe Connect Meeting add-in.
Please review the technote here:
http://helpx.adobe.com/adobe-connect/kb/connect-902-add-in.html
We have created a PDF with step by step instructions to secure all the four components of Connect which are Web App, Meeting App, CQ Author and CQ Publish. Please go through the following Tech Note : http://helpx.adobe.com/adobe-connect/kb/secure-connect-cq.html
Adobe is currently investigating reports of a compromise of a Connectusers.com forum database. These reports first started circulating late during the day on Tuesday, November 13, 2012. At this point of our investigation, it appears that the Connectusers.com forum site was compromised by an unauthorized third party. It does not appear that any other Adobe services, including the Adobe Connect conferencing service itself, were impacted.
To protect Connect forum users, we have taken the following actions:
As a reminder, one of the best ways to protect yourself online is to follow password best practices and use different login credentials across different websites and services.
We sincerely apologize for the inconvenience this may cause to our forum members. Your security is of critical importance to us, and we appreciate your patience as we work towards restoring Connectusers.com forum services.
Periodically, licensed (on-premise) deployments of Adobe Connect Pro will have to have the services stopped or cycled during periods of modification, customization, troubleshooting, or potentially on a scheduled basis.
For convenience, you can copy the appropriate code below into a new file and save at a batch (.bat) file. Running this batch file will stop all the services in the correct order and then restart them in the appropriate order either all at once (automatically) or after a keystroke (prompted) by the user.
For a scheduled periodic cycling of the services, you can setup a scheduled task in Windows (on the Connect server) to run this batch file or have it controlled by a centralized enterprise scheduler like Tidal. Of course if setting up a scheduled task, you’d need to select the one without the forced keystroke.
First, take everything in between the lines (from @ECHO OFF through @ECHO OFF) and save as a .bat file to the Connect server.
Then you can run it manually or point a scheduled task to it.
I have posted a few different options below…see the descriptions then the code below them. These are applicable to Adobe Connect Pro 8.x and 9.x. There are additional services with 9.x (i.e. Adobe Connect CQ-Author service, Adobe Connect CQ-Publish service) as well as the Flash Media Gateway (FMG) and Adobe Connect Presence Server services that are in both C8 and C9 that may or may be needed. You can add these services to the batch files if applicable.
1.) Below is a cycler that just stops and starts all the applicable services (FMS,FMSAdmin,ConnectPro, and the CPTelephonyService). It is up to you and your deployment, whether you need the CPTelephonyService or not. This version will do it all automatically and won’t force you to perform a keystroke to start once the services are stopped. This version is good for a scheduled task to point to. Again, you may remove the FMSAdmin and/or CPTelephonyService services if you wish, as they are not always needed. I also added a ping in the middle so it adds more time before restarting the services (in case there is a delay in stopping the FMS service, which sometimes happens).
———————————snip below here and save to a .bat file—————————-
@ECHO OFF REM ----------------CONNECT SERVICE AUTOMATIC CYCLING ---------------- REM REM This batch file stops and starts the Adobe Connect and Flash Media Server Services REM REM REM ----------------------------------------------------------------------- @ECHO ON net stop ConnectPro net stop CPTelephonyService net stop FMSAdmin net stop FMS ping 1.1.1.1 -n 1 -w 20000>nul net start FMS net start FMSAdmin net start ConnectPro net start CPTelephonyService @ECHO OFF
———————————snip above this and save to a .bat file——————————
2.) Below is a cycler that stops the services (same as above) but requires a keystroke to start up the services again. This is handy if you are doing work on the server or troubleshooting and you want to quickly stop the services but not restart them until you are ready.
———————————snip below here and save to a .bat file—————————-
@ECHO OFF REM ----------------CONNECT SERVICE AUTOMATIC CYCLING WITH KEYSTROKE---------------- REM REM This batch file stops and starts the Adobe Connect and Flash Media Server Services REM
REM REM ----------------------------------------------------------------------- @ECHO ON
net stop ConnectPro net stop CPTelephonyService net stop FMSAdmin net stop FMS /y
@ECHO OFF
@ECHO Press a key to START services PAUSE
@ECHO ON
net start FMS net start FMSAdmin net start ConnectPro net start CPTelephonyService
@ECHO OFF
———————————snip above this and save to a .bat file——————————
3.) Below is a cycler that stops the services on an Edge server and clears the cache before restarting.
MAKE SURE YOU CHECK THE EDGE SERVER DIRECTORY STRUCTURE ON YOUR MACHINE BEFORE USING THIS. YOU’LL HAVE TO CHANGE THE LOCATION TO MATCH YOUR OWN.
Additional Notes:
The Edge server will need a maintenance script to clear old cache and keep them fresh; run the following .bat file as a scheduled task on each Connect Edge server; feel free to edit this file to reduce or prolong the ping-induced delays. The key is to allow enough time between each command for services to stop and start. Different servers respond differently, some requiring more time and some less time. By stopping the services, it unlocks the cache for thorough deletion:
———————————snip below here and save to a .bat file—————————-
@ECHO OFF REM ------CONNECT SERVICE AUTOMATIC CYCLING--------------- REM REM This batch file stops and starts Connect Edge Services and Clears the Cache REM REM ------------------------------------------------------------ @ECHO ON net stop fmsadmin ping 1.1.1.1 -n 1 -w 10000>nul net stop fms ping 1.1.1.1 -n 1 -w 200000>nul del /Q /S c:\breeze\edgeserver\win32\cache\http\*.* ping 1.1.1.1 -n 1 -w 10000>nul net start fms ping 1.1.1.1 -n 1 -w 10000>nul net start fmsadmin @ECHO OFF
———————————snip above this and save to a .bat file——————————
The basic purpose of this changes would be to combine the features of UV and Integrated Telephony
1. Enable Audio Broadcast in Meeting for VOIP users (available in UV however not in Integrated telephony). VOIP and telephony users collaborate.
2. Dial Out from meeting, enabled users to be able to dial themselves from the meeting room (available in Integrated telephony however not in UV)
Prerequisite: Flash Media Gateway configured with SIP settings.
Add the following snippet within the <telephony-adaptor></telephony-adaptor> tag for any provider you want to enable for UV.
For PGI NA Adaptor:
<dial-in-sequence>
<conf-num>{x-tel-premiere-uv-conference-number}</conf-num>
<delay>6000</delay>
<dtmf>{x-tel-premiere-participant-code}</dtmf>
<dtmf>#</dtmf>
<delay>12000</delay>
<dtmf>*#</dtmf>
<delay>12000</delay>
<dtmf>[uv-token]</dtmf>
</dial-in-sequence>
For PGI EMEA Adaptor:
<dial-in-sequence>
<conf-num>{x-tel-premiere-emea-uv-conference-number}</conf-num>
<delay>6000</delay>
<dtmf>{x-tel-premiere-emea-participant-code}</dtmf>
<dtmf>#</dtmf>
<delay>12000</delay>
<dtmf>*#</dtmf>
<delay>12000</delay>
<dtmf>[uv-token]</dtmf>
</dial-in-sequence>
For Intercall Adaptor:
<dial-in-sequence>
<conf-num>{x-tel-intercall-uv-conference-number}</conf-num>
<delay>6000</delay>
<dtmf>{x-tel-intercall-participant-code}</dtmf>
<dtmf>#</dtmf>
<delay>8000</delay>
<dtmf>#</dtmf>
<delay>8000</delay>
<dtmf>#</dtmf>
<delay>12000</delay>
<dtmf>[uv-token]</dtmf>
</dial-in-sequence>
Additional information:
<conf-num>: The phone number for the audio conference. This element must be first in the dial-in-sequence. You can only have one <conf-num> element. The adaptor provides the value in the curly brackets {}.
<delay>: A delay in the dialing sequence, in milliseconds.
<dtmf>: A DTMF (dual-tone multi-frequency) tone. A DTMF value can be any number or letter on a telephony keypad, including * and #.
User may often complain about text missing from Chat Pod of the meeting. The purpose of this guide to to explain how Chat History in retained in various aspects.
On September 28th we conducted what we hope to be the first of many public webinars hosted by the Adobe Connect support team. The first was presented by Lauren Gardner and Jaydeep Chakravarty, a recording of which can be found here:
https://my.adobeconnect.com/p8ob93tnx3x/
Support teams from Adobe’s other products are also participating in this webinar initiative; future webinars can be found on our main events page, although we hope to make a separate page for support webinars in the future.
Adobe Events: http://www.adobe.com/events/main.jsp