Elastic Layering Logs

Debugging Elastic Layering problems is described in the documentation here (scroll down to Debug an Elastic Layer):

https://docs.citrix.com/en-us/citrix-app-layering/4/hyper-v/assign-layers/assign-app-layers-to-users-elastically.html

Get the ELM logs first. Then:

1.Collect the data from these logs in the end-user VM after producing the problem:

  • Windows Application Event log: In the Windows Event Viewer under Windows Logs, export the Application event log as an EVTX file.
  • Unidesk Layering Service log (ulayersvc.log): C:ProgramDataUnideskLogsulayersvc.log
  • Unidesk LayerInfo log (layerinfo.log): %LOCALAPPDATA%UnideskLogslayerinfo.log (note, this is in the current user profile)

2.Collect the values of these Registry keys from the end-user VM:

  • HKEY_LOCAL_MACHINESOFTWAREUnideskULayerAssignmentFile
  • HKEY_LOCAL_MACHINESOFTWAREUnideskULayerRepositoryPath
  • HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsNTCurrentVersionWinlogonUserInit

3.Collect the contents of the JSON files, including at least the Assignment (ElasticLayerAssignments.json) and Layers (Layers.json) files from the Repository Path.

Enabling Debug Logging in Ulayer

By default, ulayersvc.log only logs events INFO or higher. You may determine that you want more detailed logging. To turn on DEBUG logging, you need to edit a configuration file. This can be done in a layer (preferably the Platform Layer) or by editing a published image after the fact. The setting must be present before Ulayer.exe starts, which normally means it must be present before the machine boots. So you cannot set it from a GPO, for instance.

Edit C:Program FilesUnideskLayering Servicesulayer.exe.config. Scroll down to find this block in the Log4Net Appender section:

<root>

<level value=”INFO“/>

<appender-ref ref=”LogFileAppender”/>

</root>

Change INFO to DEBUG and save.

Related:

  • No Related Posts

Leave a Reply