File Format for .raa
FlexNet Manager Suite
2020 R2
(On-Premises)
The AppVMgmtSvr.ps1
PowerShell script interrogates the App-V Management
Server, and saves the resulting data in a remote application access file (filename extension
.raa), by default called FNMS_AppV.raa. This is an
XML file that encapsulates data about each application's App-V package, and the MSI installer
information known to App-V.
Here is an excerpt from an FNMS_AppV.raa file (here
line-wrapped for
presentation):
<remoteApplications accessModeID="2">
<app farmName=""
appID="9b09bc0d-9634-4838-b0ba-8c256ef4710d"
appName="Blender"
appFileName=""
appFileVersion=""
appFilePublisher=""
appFileDesc=""
userSid=""
serverName=""
serverDomainName=""
isStreamingProfile="1" />
<msiData farmName=""
appID="9b09bc0d-9634-4838-b0ba-8c256ef4710d"
msiDisplayName="Blender"
msiPublisher="Blender"
msiVersion="1.0"
msiProductCode="{DFFFE0C6-3E9A-44E9-9EC1-B5C92DCEE4AF}" />
<app farmName=""
appID="5d80bef6-de4a-44f6-b4f8-9aa6a657880e"
appName="FileZilla_3.2.4.1_win32-setup"
appFileName=""
appFileVersion=""
appFilePublisher=""
appFileDesc=""
userSid="S-1-5-21-1336908958-3350896562-3141117955-1690"
serverName=""
serverDomainName=""
isStreamingProfile="1" />
<msiData farmName=""
appID="5d80bef6-de4a-44f6-b4f8-9aa6a657880e"
msiDisplayName="FileZilla Client 3.2.4.1"
msiPublisher=""
msiVersion="3.2.4.1"
msiProductCode="filezilla client" />
<app farmName=""
appID="02787044-d434-4e7d-8770-cda46c988de8"
appName="AdobeReader9"
appFileName=""
appFileVersion=""
appFilePublisher=""
appFileDesc=""
userSid="S-1-5-21-1336908958-3350896562-3141117955-1690"
serverName=""
serverDomainName=""
isStreamingProfile="1" />
<msiData farmName=""
appID="02787044-d434-4e7d-8770-cda46c988de8"
msiDisplayName="Adobe Reader 9.1"
msiPublisher="Adobe Systems Incorporated"
msiVersion="9.1.0"
msiProductCode="{ac76ba86-7ad7-1033-7b44-a91000000001}" />
...
</remoteApplications>
Some points of interest to note:
- The complete set of MSI attributes needed for FlexNet Manager Suite makes use of
Asset Intelligence on the App-V release 5.0+ system, which saves a series of
AssetIntelligenceProperties
in the manifest file. From these properties,AppVMgmtSvr.ps1
extracts the fourmsi...
properties shown for the applications above. - Not all applications deployed through App-V use MSI, as some applications use
third-party installers. App-V packages using third-party installers cannot include the
Asset Intelligence properties available through MSI. For such cases, the
AppVMgmtSvr.ps1
PowerShell script interrogates the App-V application registry to get complete installer evidence, populating the same attributes in the .raa file. (Thus the presence ofAssetIntelligenceProperties
in the manifest file does not necessarily mean that Asset Intelligence was available; but does mean that equivalent data has been obtained.) - The
msiDisplayName
becomes the Name property of the installer evidence record, themsiPublisher
maps to Publisher,msiVersion
maps to Version. As with all installer evidence, the resulting record is matched against installer evidence "rules" (previously-recorded installer evidence records, most often generalized with judicious use of wild card%
characters), and when matched, adds an installation count to the application linked to the rule. This means that in listings of installer evidence, the visible entry remains the generalized rule that matched our individual piece of installer evidence. However, the individual installer evidence record is visible by drilling down into the properties of the inventory device on which the inventory evidence was found. - For a worked example of how the installer evidence for the FileZilla application in the extract above is matched against an installer evidence rule, see Investigating Issues.
FlexNet Manager Suite (On-Premises)
2020 R2