Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

VMware Exam 2V0-51.23 Topic 2 Question 19 Discussion

Actual exam question for VMware's 2V0-51.23 exam
Question #: 19
Topic #: 2
[All 2V0-51.23 Questions]

What must be implemented on all Connection Servers for logon segment information to be populated in the Horizon Helpdesk Tool?

Show Suggested Answer Hide Answer
Suggested Answer: B, E

If the Horizon Console does not display the health status of configured Unified Access Gateways (UAGs), it could be due to improper firewall configuration blocking traffic on port 443, which is essential for secure communication. Additionally, a discrepancy between the system name in UAG and the name entered in the Horizon Console can also prevent the console from correctly retrieving and displaying the UAG's health status.


Contribute your Thoughts:

Jennifer
2 days ago
D) vdmadmin -A -d dtpool2 -m machine1 -getstatus - This looks like a useful command, but it's not the right one for populating the logon segment information.
upvoted 0 times
...
Charlesetta
7 days ago
C) Blast Secure Gateway - Are you kidding me? The Blast Secure Gateway has nothing to do with the Horizon Helpdesk Tool.
upvoted 0 times
...
Juan
9 days ago
B) vdmadmin -I -timingProfiler -enable - This must be the answer, it's the only one that sounds like a valid command to enable the timing profiler.
upvoted 0 times
...
Samira
17 days ago
I see your point, but I still think A) Horizon Helpdesk Agent is the right choice because it directly relates to logon segment information.
upvoted 0 times
...
Samira
18 days ago
I disagree, I believe the correct answer is B) vdmadmin -I -timingProfiler -enable.
upvoted 0 times
...
Samira
19 days ago
I think the answer is A) Horizon Helpdesk Agent.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77