I85PREP
⌘ K
Citrix CC-VAD-CC study materials
Citrix CC-VAD-CC study resources

Citrix CC-VAD-CC: Monitoring, Troubleshooting, and Supportability

Citrix CC-VAD-CC · Work through your exam, one topic at a time.

All guide sections

Monitoring, Troubleshooting, and Supportability

Director

Director reads the Monitoring database, so history, trends, failure reasons and logon duration breakdowns exist only when Monitoring is configured. Real-time session data still appears without it, which is why candidates assume Monitoring is optional until they need a failure trend. Use Director to answer three questions: who is connected where, why did this session fail, and how long did logon take. Export support information from Director when opening a case.

Instrumentation

  • Studio's Site test validates database connectivity, controller services, licensing and AD.
  • Citrix Scout collects CDF traces, event logs, registry and configuration into a bundle for Citrix Insight Services; run it after reproducing the issue.
  • CDFControl or Start-Trace gives granular component tracing when one service is suspect; traces are large, so scope them.
  • Event logs: Citrix Broker Service on controllers, Citrix Desktop Service on VDAs, Citrix Delivery Services on StoreFront.

Registration triage

The most common scenario, in order:

  1. Get-BrokerMachine -RegistrationState Unregistered confirms the scope.
  2. On the VDA: is the Citrix Desktop Service running, is ListOfDDCs correct (FQDN), does DNS resolve, is time within five minutes, is outbound 80/443 open?
  3. On the controller: is the Broker Service running, is the database reachable, is the machine's AD account healthy and not disabled or duplicated?
  4. Purge stale Kerberos tickets with klist purge, then restart the Citrix Desktop Service.

Worked example. After a certificate change on the controllers, an entire catalog reports Unregistered and Director shows connection failures. Authentication broke at the broker rather than the network: either the VDA does not trust the new chain, or the XML service moved to 443 while the StoreFront farm still uses HTTP. Check the farm transport setting before rebuilding machines.

Traps

  • Expecting historical data without Monitoring configured.
  • Tracing everything at maximum verbosity and hitting the size limit before the failure occurs.
  • Checking only controller-side firewalls; the VDA initiates the connection.
  • Reinstalling the VDA before checking time skew, DNS and ListOfDDCs.