VMware Horizon Community
Mickeybyte
Hot Shot
Hot Shot

Horizon REST API inconsistent with Horizon RDS agent status

Hi, 

I'm playing around with the Horizon REST API and came to the following issue: 

As a test, I disabled the VMware PCoIP gateway service on one of my RDS hosts. This results in the RDS Host showing status "Protocol Failure" in the Horizon Admin console. When I lookup the status of the RDS servers using the REST API (<url>/rest/rds-servers) I get an RDS status of "ERROR" and an agent status of "UNKOWN". 

Status in Horizon Admin console: 

Mickeybyte_0-1622648036983.png

JSON result from REST API: 

 

{
    "id":  "b9f4f2c7-a379-4855-9df9-53c624b13aba",
    "name":  "RDSH-3",
    "status":  "ERROR",
    "enabled":  true,
    "load_preference":  "LIGHT",
    "load_index":  0,
    "session_count":  0,
    "farm_id":  "2e5f72a6-c327-4803-a2fe-73bca28055ec",
    "details":  {
                    "operating_system":  "WINDOWS_SERVER_2016_OR_ABOVE",
                    "state":  "UNKNOWN",
                    "agent_version":  "8.2.0",
                    "agent_build":  "17771933",
                    "max_sessions_count_configured":  2
                }
}

 

 

I would have expected the agent status to be "AGENT_ERR_PROTOCOL_FAILURE" according to VMware Horizon Server API - VMware API Explorer - VMware {code}?

Am I wrong here or is this a bug in the REST API? 

 


Regards,
Mickeybyte (ITPro blog)

If you found this comment useful or an answer to your question, please mark as 'Solved' and/or click the 'Kudos' button, please ask follow-up questions if you have any.
Labels (5)
Reply
0 Kudos
0 Replies