What is the correct method for gathering Horizon agent logs?

Question

Options

• AFrom the desktop where Horizon Agent is installed, run the commandsys report._full. cmd.
• BFrom the desktop where Horizon Client is installed, run the command imvtutil --verbose.
• CFrom the desktop where Horizon Connection Server is installed, run the command wmware-
• DFrom the desktop where Horizon Agent is installed, run the commandsupport. bat.

• A
  3% (2)
• B
  2% (1)
• C
  94% (59)
• D
  2% (1)

Explanation

Note: Option C in your question appears to be truncated (cut off mid-sentence), which makes this question difficult to evaluate with full confidence. Based on VMware Horizon documentation, this is worth flagging.

Running support.bat on the machine where Horizon Agent is installed (option D) is actually the widely documented method for collecting Horizon Agent logs - it generates a full diagnostic bundle directly from the agent machine. Option C as written points to the Connection Server, which is a separate component responsible for brokering connections, not the agent itself; collecting agent-specific logs from there is not the standard approach. Option A's sysreport._full.cmd is not a recognized VMware Horizon command, making it a nonsense distractor. Option B's imvtutil --verbose references the Horizon Client machine, which is the end-user's device - irrelevant for agent-side log collection.

Memory tip: Think "Agent logs live where the Agent lives." The Horizon Agent is installed on the virtual desktop or published application machine, so log collection always starts there - not on the Client or Connection Server side.

Exam caution: Given that option C is visibly cut off and the logic strongly points to D, double-check this question against your official study guide or course materials. There may be a typo in the answer key.

No community discussion yet for this question.