-
-
-
-
-
-
-
Description of the uAInSessionHelper/uberAgentHelper Process
-
Name or Version may be Inconsistent Between App Inventory and Usage
-
-
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!
Name or Version may be Inconsistent Between App Inventory & Usage
uberAgent collects information about applications on multiple levels:
- Which applications are installed (app inventory)
- Which applications are running (app usage)
- Which applications are being worked with (foreground app)
Not all of that information is available in one data source. In fact, uberAgent has to query quite disparate sources to collect its extensive application information. That can lead to inconsistencies, specifically between the app inventory and all the other application source types.
Root Cause
The root of the problem is that Windows has no generic concept of applications. Windows knows and cares about processes, threads and a good number of other things, but APIs for applications? Nonexistent.
As a consequence, there are no application naming and versioning standards for software vendors. This may lead to the situation that vendors use one name/version in one place and a different name/version in another - for the same application.
uberAgent
uberAgent has sophisticated algorithms to deal with the situation and determine the best possible application names and versions. However, there may be inconsistencies between the source types ApplicationInventory
and other application source types, e.g., ApplicationUsage
or ProcessDetail
.
The reason for these inconsistencies lies in the fact that the data for the ApplicationInventory
sourcetype is based on the Uninstall
registry key so that it matches what Windows displays in Apps & features.
All other source types’ application info, on the other hand, is based on an algorithm that determines application properties depending on the application type (Win32, UWP, App-V, Java, ...). Naturally, this algorithm cannot use the Uninstall
registry key.
For that reason, inconsistencies may exist and mapping between the ApplicationInventory
and other application source types is not recommended.
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.