How to enable advanced logging in Provisioning Services 6.1 including Target Devices

Provisioning Services has the ability to run a Target Device from a vDisk in Standard Image Mode, meaning that the vDisk is in a read-only state.

Changes to the vDisk are stored in one of three locations:

  • RAM cache
  • Target Device hard drive (Local hard drive which rules out Thin Clients)
  • Server side cache, using disk space on the Provisioning Services Server

Changes to the disk are not persistent and are lost if the Target Device is rebooted.

Q: So if a Target Device is accessing a vDisk in Standard image mode, where is the “debug” or “trace” log written to? Indeed, can one take a trace from a PVS Target Device?

A: In Provisioning Services all traces and logs are kept on the Provisioning Services Server, even for Target Devices.

This means that logs can be gathered from PVS Servers and from Target Devices. All are stored on the PVS Server.

Provisioning Services Log file location for Windows 2008 and Windows 2003 Server.

  • Windows 2008R2 – C:programdataCitrix|Provisioning ServicesLog
  • Windows 2003 – C:documents and settingsAll userApplication

Procedure

  • Provisioning Services 6.1 the following log files can be gathered:

Stream_log.config

  • This file should not be edited manually. Logging levels should be set through the Console. Any edits made to this file manually are lost when the Provisioning Server restarts, or when logging levels are changed using the Console.

Stream.log

  • StreamProcess.exe, Manager.dll and Streamdb.dll all write to the Stream.log file.

MCLI.log

  • writes MCLI logging information to MCLI.log.

SoapServer.log

  • writes SoapServer logging information to SoapServer.log.

Console.log

  • writes Console logging information to Console.log.

ConfigWizard.log

  • writes Provisioning Server configuration logging information to ConfigWizard.log.

Log File Contents

  • content of a log file includes:
  • Timestamp
  • Logging Level
  • Component and method used to perform logging
  • Provisioning Server and target device identity (name, IP, or MAC)
  • Logging message with supporting data of Windows error codes when appropriate

Read the entire article here at the Citrix knowledge center.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.