This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Diagnostics scope and content
The amount of diagnostic files requested from a device is defined by two factors:
-
Selected templates in the Diagnostic files dialog In addition to the #System template, further individual templates might be active.
-
Configured log level Diagnostics tab Only the enhanced log level allows to execute all script on the device and retrieve all files defined in the
#System
template.
System template
To perform device diagnostics, a predefined template called #System
is provided. This template includes a file list with relevant configuration and log files plus a script code to be run on the device. Neither of them can be edited. You cannot deactivate the system template.
The system template contains the following files:
- Log files for eLux and components
- eLux configuration files, including
terminal.ini, user.ini, sessions.ini
- Configuration files of standard components and standard applications
The defined script contains different system commands that request software and hardware information from the device. Included are for example runtime information, installed packages, active codecs, the update partition, PCI and USB devices. Via fwupdmgr
, firmware information about installed components such as the UEFI system or the flash memory is also retrieved.
The output of the system commands is stored in the mytrace.log
file, which is transmitted along with the other files in a .zip
archive.
Note:
Authorized administrators may define additional custom templates.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.