ConsolidatedRemoteAccessFile Template
The RemoteAccessFile spreadsheet is used for capturing application virtualization information. Systems such as Microsoft AppV and Citrix XenApp allow a user to access applications that are not installed on a local computer. This object allows you to provide applications that a user may access by specifying the file evidence.
When populating the RemoteAccessFile template, please note that an application can be identified by file evidence. If the evidence does not match the ARL then no application will be created. The evidence not recognised will appear under the ‘Unrecognised Evidence’ screen within Flexnet Manager Suite. From there, you may create applications for any unrecognised evidence as required, and lastly ensure any new application relates to a license. This results in the evidence now being recognised for the new application and may cause license consumption after the next reconciliation. This application virtualization access using files is a special case in application matching. It does not require a mandatory file link to the application and can user a ‘not for recognition’ file to link to an application. This is because application and desktop virtualization systems rarely provide enough file information for more complex application recognition rules to function.
If entering file evidence, you must provide the following key identifier fields. + 1 = FileName
The following identifier fields are typically requried for matching evidence in the ARL, however are not mandatory. + 1 = Company + 2 = FileVersion + 3 = Description + 4 = FileSize
File evidence does not have to be specified in the FileEvidence spreadsheet as well as here.
|
Column |
Details |
|---|---|
ServerID
|
Type: big integer. Key This is the ComputerID of the server that publishes this virtual application. The ComputerID must match a computer from the Computer spreadsheet, and that computer must have an installation of the application this file is part of. If the server does not have an installation of an appropriate application then the user will not be shown as having access to that application. This is a mandatory field. Destination:
|
FileName
|
Type: text (max 256 characters). Key The name of the file used as evidence of software installation. For unix operating systems include the full path in the file name, including the opening ‘/’. For Windows operating systems the file path is specified in the FilePath column and this column must only contain the file name. Destination:
|
FileVersion
|
Type: text (max 100 characters). Key. Nullable The version number of the file used as evidence of software installation. Destination:
|
ProductVersion
|
Type: text (max 200 characters). Nullable The product version number in the file header. Destination:
|
ProductName
|
Type: text (max 200 characters). Nullable The product name in the file header. Destination:
|
FilePath
|
Type: text (max 400 characters). Nullable The path of the file used as evidence of software installation. Destination:
|
Company
|
Type: text (max 100 characters). Key. Nullable The company in the file header. Destination:
|
Description
|
Type: text (max 200 characters). Key. Nullable The description in the file header. Destination:
|
FileSize
|
Type: integer. Key. Nullable The size of the file in bytes. Destination:
|
Language
|
Type: text (max 200 characters). Nullable The language in the file header. Destination:
|
UserID
|
Type: big integer. Key The UserID must be populated with the fully qualified name e.g. Mydomain\JohnSmith. If not then a User is not created. If fully qualified then this field populates the following user related fields. + 1 = The user name of the end-user from the text following the “". + 2 = The login name (SAM account name) of the end-user from the text following the “". + 3 = The domain name of the end-user from the text before the “". Destination:
|
AccessMode
|
Type: text (max 128 characters). Key. Nullable The AccessMode states how an application has been accessed. Possible values:
Destination:
|