Jun 09, 2022
06:52 PM
1 Kudo
Hi @dmathias - The Citrix evidence reports were introduced into FNMS On-Prem in 2020 R2 (ref) .
You could take a look at this topic Citrix Virtual Desktops Installer Evidence report in the 2020 R2 On-Premises Online Help. (However, the report can't be generated in 2019 R1.)
... View more
Jun 08, 2022
08:46 PM
4 Kudos
Hi @dmathias (and @nrousseau1),
The mentioned 404 page as well as another page in the Online Help have been replaced by two new pages recently:
https://docs.flexera.com/fnms/EN/WebHelp/index.html#topics/Rep_CitrixVirtDesktopsInstallEvid.html replaced by https://docs.flexera.com/fnms/EN/WebHelp/index.html#topics/Rep_VirtualDesktopsInstallEvid.html
https://docs.flexera.com/fnms/EN/WebHelp/index.html#topics/Rep_CitrixVirtDesktopsFileEvid.html replaced by https://docs.flexera.com/fnms/EN/WebHelp/index.html#topics/Rep_VirtualDesktopsFileEvid.html
This change is due to an update in ITAM 2022 R1.1 to include VMware Horizon non-persistent VDI data in the Citrix Virtual Desktops File and Installer Evidence reports. Please see this entry in the Features by Release doc: The Citrix Virtual Desktops File and Installer Evidence reports have been updated to collect VMware Horizon non-persistent VDI data
Thanks, Jing
... View more
May 15, 2022
08:08 PM
2 Kudos
Hi @mfeinman, does this article [FNMS SAML Setup] Troubleshooting guide and list of common errors have the information you need?
... View more
Apr 13, 2022
12:30 AM
@kstaude Thanks for your suggestion. We'll look into that 👍
... View more
Feb 03, 2022
04:00 PM
1 Kudo
Summary
This article describes the Data Platform v5 extractor fields that are supported in Flexera One.
Description
Data Platform v5 standalone extractors can be used in Flexera One. However, there are limitations on the contents of the extractor files. To make a Data Platform extractor functional in Flexera One, you might need to make changes to some fields in the extractor files.
The following tables describe:
Mappings between the source fields in the Data Platform v5 extractor files and their equivalent target fields in Flexera One Technology Resource Services (TRS)
Special behaviours and limitations of each field.
Notes:
Each mapping table is named for the imported TRS record.
In each mapping table, one or more Key Fields are identified. Key Fields are the fields that are used in the involved data table files to relate records together and must exist in each file; otherwise, the process will fail.
The ResourceID field is a Key Field for all sources, as it is the common key to connect records and to uniquely identify the device from multiple imports.
If a file is marked as Required, it must exist in the extractor, otherwise the process will fail.
If a file is marked as Grouped, the data in the file is first grouped by the Key Fields prior to being joined with other files. When a file is Grouped, duplicate Key Fields are anticipated. When a file is not Grouped, duplicate Key Fields must not exist, otherwise the process will fail.
If a Grouped file is also marked as “First taken”, only the first record of the duplicate records in that file will be used, according to the record order in the file unless otherwise specified.
Table 1. Mappings for Computer records
Each “Computer” record in TRS represents the hardware details about a device.
Key Fields(s): ResourceID
Source file
Required
Grouped
Source Field
TRS Target Field
Special Behaviour / Limitation
GS_COMPUTER_SYSTEM
✔
✖
Name0
Name
Ignored if System.csv exists
Model0
ModelNo
Manufacturer0
Manufacturer
Domain0
NumberOfProcessors0
NumberOfProcessors
UserName0
LastLoggedonUser
GS_LOGICAL_DISK
✖
✔
Size0
HddTotalSpace
Sum of grouped records
GS_NETWORK_ADAPTER_CONFIGUR
✖
✔
MACAddress0
[]NetworkInfo.Mac
IPAddress0
[]NetworkInfo.IPv4Address
[]NetworkInfo.IPv6Address
Attempts to detect pattern and places in appropriate field
GS_PROCESSOR
✖
✔
Name0
[]ProcessorInfo.Name
MaxClockSpeed0
[]ProcessorInfo.ClockSpeedMax
Manufacturer0
[]ProcessorInfo.Manufacturer
GS_X86_PC_MEMORY
✖
✖
TotalPhysicalMemory0
TotalMemory
GS_OPERATING_SYSTEM
✖
✔ - First taken, ordered by Name0
Name0
OperatingSystem
Caption0
Version0
CSDVersion0
Manufacturer0
GS_SYSTEM_ENCLOSURE
✖
✔ - First taken
SerialNumber
SerialNumber
Only used if GS_PC_BIOS did not supply it
ChassisType
ChassisType
GS_PC_BIOS
✖
✖
SerialNumber0
SerialNumber
GS_VIDEO_CONTROLLER
✖
✔
Name0
DisplayAdapterCount
Count of grouped records
System
✖
✖
Name
Name
Domain
Domain
DomainFlat
Obsolete
If 1, the record will be ignored
Table 2. Mappings for InstallerEvidence records
Each "InstallerEvidence" record in TRS is an array of all the installed software on a device. It is expected that the ResourceIDs specified here can be linked back to those in the "Computer" stream; however, this is not enforced.
Key Fields(s): ResourceID, AddRemove_Key (conditional)
Source file
Required
Grouped
Source Field
TRS Target Field
Special Behaviour / Limitation
AddRemove
✖ - Falls to "AddRemove_AH" and "AddRemove_AU" if missing
✔ - Only most recent install date for any distinct record
DisplayName
Title
Version
Version
Publisher
Manufacturer
InstallDate
InstallDate
ProdID
ProductCode
AddRemove_AH
✔ - Only if "AddRemove" is not supplied
✔ - Only most recent install date for any distinct record
AddRemove_Key
Used as join criteria to AddRemove_AU
ProdID
ProductCode
InstallDate
InstallDate
AddRemove_AU
✔ - Only if "AddRemove" is not supplied
✔
AddRemove_Key
Used as join criteria to AddRemove_AU
DisplayName
Title
Version
Version
Publisher
Manufacturer
Table 3. Mappings for OSEvidence records
Each "OSEvidence" record in TRS is an array of all the operating systems on a device. This is mainly designed to cover the situations where a single machine can be "dual booted", so the format can supply all the operating systems that a device has. It is expected that the ResourceIDs specified here can be linked back to those in the "Computer" stream; however, this is not enforced.
Key Fields: ResourceID
Source file
Required
Grouped
Source Field
TRS Target Field
Special Behaviour / Limitation
GS_OPERATING_SYSTEM
✖
✔
Name0
Name
Caption0
Caption
Version0
Version
CSDVersion0
CsdVersion
Manufacturer0
Manufacturer
... View more
Labels:
Latest posts by JingQian
Subject | Views | Posted |
---|---|---|
1026 | Jun 09, 2022 06:52 PM | |
1088 | Jun 08, 2022 08:46 PM | |
171 | May 15, 2022 08:08 PM | |
214 | Apr 13, 2022 12:30 AM | |
550 | Feb 03, 2022 04:00 PM |
Activity Feed
- Kudoed Re: Flexera ITAM Best practice information available in Flexera Community for dmathias. Jun 09, 2022 06:53 PM
- Got a Kudo for Re: Flexera ITAM Best practice information available in Flexera Community. Jun 09, 2022 06:53 PM
- Posted Re: Flexera ITAM Best practice information available in Flexera Community on FlexNet Manager Blog. Jun 09, 2022 06:52 PM
- Got a Kudo for Re: Flexera ITAM Best practice information available in Flexera Community. Jun 09, 2022 03:39 PM
- Got a Kudo for Re: Flexera ITAM Best practice information available in Flexera Community. Jun 08, 2022 08:51 PM
- Posted Re: Flexera ITAM Best practice information available in Flexera Community on FlexNet Manager Blog. Jun 08, 2022 08:46 PM
- Got a Kudo for Re: Flexera ITAM Best practice information available in Flexera Community. Jun 08, 2022 08:46 PM
- Got a Kudo for Re: Flexera ITAM Best practice information available in Flexera Community. Jun 08, 2022 08:46 PM
- Got a Kudo for Re: How to Troubleshoot an SSO Issue. May 16, 2022 10:57 AM
- Got a Kudo for Re: How to Troubleshoot an SSO Issue. May 15, 2022 08:20 PM
- Posted Re: How to Troubleshoot an SSO Issue on FlexNet Manager Forum. May 15, 2022 08:08 PM
- Kudoed Flexera ITAM Best practice information available in Flexera Community for nrousseau1. May 10, 2022 09:34 PM
- Posted Re: Data Platform v5 extractor support in Flexera One: Fields mapping and descriptions on Flexera One Knowledge Base. Apr 13, 2022 12:30 AM
- Posted Data Platform v5 extractor support in Flexera One: Fields mapping and descriptions on Flexera One Knowledge Base. Feb 03, 2022 04:00 PM