App-V Release 4.6 Data Transfers
This table lists the data extracted from App-V release 4.6, and where it is stored the compliance database in IT Asset Management. Imported data is stored in temporary staging tables for data manipulation, and then moved into their final destination tables as noted below. These columns in the compliance database are available for use in custom reports, and the like.
App-V (Table)/Column | FNMS (Table)/Column | Notes |
---|---|---|
( |
|
If the computer name already exists in the
ComplianceComputer table, this device is identified as
the consuming device.If it does not already exist, the device is added to
the |
( |
|
The domain name is extracted from the host record on the App-V server.
If the domain does not already exist in the compliance database, it is added
to the ComplianceDomain table, and as required the
ComplianceDomainID may be updated in the
ComplianceComputer table. |
( |
|
The last logged on user for this computer. |
( |
( |
The name of the App-V package (which may bear no resemblance to the
application inside) is used to identify the evidence record. Note: It is
possible for an App-V package to contain more than one application. This
makes it impossible to link the App-V evidence to a single application
record. Best practice is to make each package contain exactly one
licensable application.
|
( |
( |
The version of the App-V package. Again, this bears no necessary relationship to the version of the application inside the package, and is at the whim of the person preparing the package (for example, it may represent the number of times the application package was modified). |
String literal App-V |
( |
All App-V evidence is given the publisher name of
App-V . |
IT Asset Management (Cloud)
Current