Provisioning Services has been providing the ability to capture logs since the time of PVS version 4.5.  Using the Log4cxx framework, PVS logging has been able to provide information about the goings on of the PVS console, the Soap Service, and the Stream Service.  These logs have provided valuable historical data when trying to troubleshoot issues.

There have been many improvements to the logging capability and as the feature set for PVS grew we introduced new logs as well as refined some existing logs.  With the introduction of PVS 7.0 the logging format has been changed from Log4cxx to CDF.  Citrix has long used CDF as a mainstay of our logging mechanism across many products.  We have written many applications to help us with both the capture and analysis of CDF traces.  This means a couple of things for PVS.  Since CDF tracing is reactive and not enabled by default there is no built in historical logging in PVS 7.0 and 7.1.  The only component that has a CDF trace generated automatically is the PVS configuration wizard.  For the rest of the logs it will be necessary to use programs like CDFControl to capture data.

To make this process easier the PVS Escalation team worked with the XenDesktop Escalation team to use the CDF Monitor tool to setup continuous CDF tracing.  This program can install as a service on each PVS server and run a continuous CDF trace against all of the PVS modules.  And the use of CDF Monitor has been incorporated with our PVSDataTools logs collection program.  The circular CDF traces captured by CDF Monitor are essential in most cases to determine root cause as without it there is no historical logging.  Citrix Support recommends CDFMonitor be configured in all PVS 7.x environments.

You can access the latest version of CDFControl here –

You can check out this article on how to setup CDFMonitor with PVS 7.x –

You can check download the latest version of the PVSDataTools here –