Search: change-labels-new-labels-list

Agent Group Choose an existing Agent Group by clicking the dropdown list or create a new group for your new Agent by clicking the "+" button Dropdown list, SingleChoice Yes 7 Description Enter

on the left menu bar -> Choose Agent option and click Create New. Step 2: After clicking, the system

the dropdown list or create a new group for your new Agent by clicking the "+" button |Dropdown list

successful login, choose** Agent** on the left menu bar -> Choose **Agent** option and click **Create New

a popup allowing you to fill in properties to create/edit a new Agent. You need to fill in all

will see new user named “lmsUser” in user accounts list. You can click “refresh” button to force MYSQLWORKBENCH update the list for you. Note that: “%” in column “From Host” means that this account can

package according to the following list. Note: - If the computer where you're installing Center does

need to prepare the installation package according to the following list. (% class="box infomessage

… [[image:1706866999267-422.png]] - After click “**Apply**”, you will see new user named “**lmsUser**” in user accounts list. You can click “**refresh**” button to force MYSQLWORKBENCH update the list for you

Save changes and exit vi editor. Press ESC key and type: “:wq” 4.  Add current user (using

] 2.1.3 Step 3: Configure folder access rights 1. Change ownership of Tomcat folder: cd /opt sudo chown

update-alternatives --list | grep java --> %JAVA_HOME% = /usr/lib/jvm/openlogic-openjdk-11-hotspot

: tomcat ALL= NOPASSWD: ALL [[image:image-20230728180918-3.png]] * Save changes and exit vi editor

Step 3: Configure folder access rights**(%%) === ~1. Change ownership of Tomcat folder: cd /opt sudo

-alternatives ~-~-list | grep java [[image:image-20230728180918-6.png]] ~-~-> %JAVA_HOME% = /usr/lib/jvm

1. Before you start This document aims to guide you to install new akaBot Center in High

/redis.conf 3. Search and update the bind parameter value from 127.0.0.1 to 0.0.0.0 3. Save changes

. Save changes and exit Press ESC then type: “:wq” 5. Restart Redis service. sudo systemctl start

you to install new akaBot Center in **High Availability model** (“Fail Over” model) as below

-left:40px" %) 3. Save changes and exit (% style="margin-left:40px" %) (% style="color:#c0392b" %)Press

="margin-left:40px" %) [[image:image-20230804101914-5.png]] (% style="margin-left:40px" %) 4. Save changes

: After changing Windows Policy, you should run this command with administrative privilege: gpupdate

the Center, Agent will use the RDP client to initiate a new session to serve that user. If the screen

with the error message that is similar to “Username or password not match”. Root cause: Upgrade to the new

changing Windows Policy, you should run this command with **administrative privilege**: gpupdate /force

a task from the Center, Agent will use the RDP client to initiate a new session to serve that user

cause**: Upgrade to the new version of the platform and the installer cannot replace the file //"C

1. Before you start This document aims to guide you to install new akaBot Center in High

changes. Step 3: On the Logging tab (1) Log prefix: Remove "commons-daemon" (2) Redirect Stdout: Remove "auto" (3) Redirect Stderror: Remove "auto" (4) Choose Apply to apply the configuration changes

you to install new akaBot Center in **High Availability model** (“Fail Over” model) as below

: On the **General** tab * Select Startup type: Automatic * Choose **Apply** to apply the configuration changes

"auto" (3) Redirect Stderror: Remove "auto" (4) Choose Apply to apply the configuration changes