Starting in 1912 LTSR Citrix Provisioning Services improves on the CDF integration that kicked off in the earlier 7.0 days. This now includes the ability to natively maintain persistent rolling CDF trace logs on each PVS Server and Targets if necessary without the need for additional capture mechanisms.
Starting in PVS 1912 there is almost no reason to use CDFcontrol or CDFmonitor. CDFMonitor is no longer supported by Citrix. CDFControl can be used in a pinch, for example the Citrix Telemetry service is down or stopped and wont start. In that case CDFControl and its required configuration files for PVS can be used to gather CDF data. Whenever another logging mechanism is used it will be required to go back and restart the Citrix Telemetry service. Using CDFControl or CDFMonitor when the Telemetry service is also running will result in corrupt data and should be avoided.
As always Target Device CDF logging can be enabled via the device properties in the console. It is recommended that logging is set to its default INFO level unless there is a need to reproduce an issue and capture data at which point DEBUG is ideal. This is because CDF output is still passed over the streamprocess to the server and can effectively increase the amount of traffic between PVS Server and endpoint Target Device. All Target Device DEBUG output will be found within the CDF traces on the PVS Server to whom they were connected.