Testing the desktop service

Last Updated : Dec 08, 2021 |

About this task

Verify that you can start the noVNC remote desktop session from the Configuration Server. During the noVNC session, you must verify that you can access the Configuration Server web portal and AE Services management console and use the server console. You must also check that you can access the noVNC session from different computers on your network to co-browse the noVNC remote desktop.

Procedure

  1. On the active Configuration Server, start the SSH session.
  2. In the command prompt, run the remoteDesktopSession command.

    The command output displays a web link to the noVNC remote desktop session in the following format:

    https://<mcs-ip>:<remote session port>/?password=<remote session password>, where <remote session port> and <remote session password> are provided automatically.

  3. Copy the web link into the browser address bar and replace <mcs-ip> with the IP address of your Configuration Server.

    In the geo-redundant HA deployment, replace <mcs-ip> with the virtual IP address of the Configuration Server.

  4. Verify that the browser displays the remote desktop session.
  5. On the remote desktop, open a browser.
  6. In the remote desktop browser, access the Configuration Server web portal.
  7. Verify that you can log in to the Configuration Server as a system administrator.
  8. In the remote desktop browser, access the AE Services management console.
  9. Verify that you can log in to the AE Services management console.

    For more information about logging in to the AE Services management console, see the Application Enablement Services overview section in Administering Application Enablement Services for Avaya Contact Center – Extended Capacity.

  10. On the remote desktop, open the server console.
  11. Verify that you can run console commands.

    For example, you can verify that you can access contact center servers using the ssh command.

  12. On another computer in your network, access the noVNC session using the same noVNC web link.
  13. Verify that browsers on different computers display the same noVNC session screen.
Related information
Logging in to the Configuration Server as a system administrator