I was able to reproduce the problem on both PCCE 12.0 and 12.6 sandboxes with the same steps:
1. first reserved the sandbox then connected via the VPN using the provided credentials from the email which is received after the sandbox is setup
2. then I RDPed to the Windows host at 10.10.20.21 using the provided credentials in the Sandbox Web Portal
3. after that I opened up Firefox and went to https://10.10.20.50/ which forwarded me to the URL you see in the screenshot below. The UI that popped up immediately had the error, "This Finesse Server is currently out of service. For more information, contact your administrator."
Cisco Voice is not my strong suit, so I engaged the Sandbox engineering team to see if it is a step that I am missing or if there is an actual issue with Finesse on these sandboxes. I see that the server is up to some extent as the web page for it would load a 404 instead of a UI with that error message.
It appears the solution was already provided to the user via WebEx. All that might be needed to do is to cycle the CCE Services from Rogger, AW, then PG (the order shouldn't matter). This must be done from each of those servers: on the desktop there should be an icon for Unified CCE Service Control program. Then from the opened program select all of the services and cycle them (you can shift or control select all of the services). Below is a screenshot of the icon and the program that pops up:
Sidenote: each of the servers (Rogger, AW and PG) might/will have different services in the Unified CCE Service Control program.
This issue is known by engineering and will be addressed in the coming days.
ll that might be needed to do is to cycle the CCE Services from Rogger, AW, then PG (the order shouldn't matter).
Is the PG <== Progger-1A-xxxx ? I tried to RDP to Progger-1A-xxxx. It always fails to connect.
How can I get the finesse client working?