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!
Further diagnostic adjustments
Diagnostic files over multiple device restarts
Requires |
---|
Enhanced logging must be enabled. |
When you request diagnostic files, a set of log and configuration files is retrieved and packed on the target device. Included is the file last_boot.zip
, which contains diagnostic files over a device restart. This .zip
file contains all files defined for the system template plus some additional ones. You can specify the number of cycles for which the file is created and saved on shutdown of the device. The default is set to five.
The most recent file is named last_boot.zip.0
. The further back a file was created, the later its sequential number in the file name.
- To define the number of cycles yourself, use the Advanced file entries feature with the following parameter:
File | /setup/terminal.ini |
Section | Global |
Entry | LogCycles |
Value |
2-n , The default value is [5]. |
Note:
That the [last_boot.zip] file is only created, if enhanced logging is active. For further information, see Requesting diagnostic files.
Store diagnostic files persistently
By default, the diagnostic files are stored on the device under /setup/logs
.
- To define a different storage location, use the Advanced file entries feature with the following parameter:
File | /setup/terminal.ini |
Section | Global |
Entry | LogPath |
Value
|
<Directory on the device> The default is /setup/logs
|
Example: /update/logs A location on the update partition may also be defined. |
If you use disk encryption via TPM 2.0, the setup partition will be encrypted. To have the diagnostic files accessible, define the update partition as their storage location. The update partition is then mounted automatically.
Diagnostic adjustments via software package
Provide diagnostic settings for new devices you wish to connect before their initial contact with the Scout Server, during installation. To do so, integrate the eLux software package Diagnostic adjustments into the image to be installed.
The Diagnostic adjustments package contains two feature packages that you can activate separately:
-
Enhanced logging: Corresponds to the device configuration Diagnosis > Debug level and enables enhanced logging
-
Logs on update partition: Sets the location for diagnostic files to
/update/logs
Note that the diagnostic settings set via software package are only effective until the first contact of the device to its Scout Server. Then the device configuration is synchronized and the device receives the configuration data defined for its OU.
Share
Share
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.