iammanzi
Level 7

XenApp Integration with FNMS 2017 R3

Jump to solution

We have a client that would like to integrate Citrix into FNMS, they are running version 6.0 and 6.5.

What would be the ideal way to integrate this as they do not have Edgesight?

regards

 

0 Kudos
1 Solution

Hi Manish,

It looks like the 2017 R3 XenApp agent does support direct upload to a beacon (using the -url command line option).   This causes the XenApp agent to upload a .raa file to the beacon which (like inventory) gets passed up the beacon chain until it is consumed by the FNMS servers.   

The intent of this option is that it can avoid the need for a staging database local to the beacon, but in reality it just means that the data is effectively "staged" in the FNMSCompliance database (just that it happens automatically with OOTB functionality).  So, whilst the -url option avoids the need for the beacon side staging DB, it doesn't avoid the need for an inventory connection to be defined to that "staged" data.  So you still need a beacon to define that connection to the "Staged" data - which in this case happens to be the FNMSCompliance db.

If FNMS cloud is being used, then you can't access the FNMSCompliance database so it's not an option - so it's just applicable for specific on prem use cases.   In most cases, the staging db local to the beacon is just more convenient anyway as you could just use a SQL express edition (the volume of XenApp data is usually small) - and if you can also use the staging db for other purposes (business adapters etc) then it is much more compelling.

To answer your specific question tho - it is 'possible' to avoid a staging db, but it's very uncommon, not an option for cloud FNMS and probably should only be considered for very specific controlled environments.

- Murray

View solution in original post

6 Replies
MurrayPeters
Level 7

Hi Manish,

Not having EdgeSight essentially means that you won't have visibility of actual usage of apps by users through Citrix.   You can still integrate by deploying the FNMS XenApp agent to servers in the Citrix farm.  The FNMS XenApp agent collects ACL (Access Control List) data which denotes which published applications are accessible to which users/groups.     This ACL information is used by FNMS to reflect the users 'ability to access' the application - this is done by showing an installation of the application via the access mode of 'XenApp'.

The 2017 R3 adapters reference has full details of how to implement this:

https://helpnet.flexerasoftware.com/fnms2017r3/onpremises/FNMSAdaptersReferencePDF.pdf

@MurrayPeters  Do we need a staging DB for this as it is 2017 R3?

0 Kudos
Hi! Staging database is required in 2017 R3, The direct upload is possible from 2018 R1 onward if memory serves correctly. Even still the staging database is recommended, as it's much easier to work with. Also Getting all AD data via the FNMS AD connector is critical, for all Domains that are part of the Citrix XenApp Farm, we compare the SID of the groups we collect with the SID of the AD Data collected.

Hi Manish,

It looks like the 2017 R3 XenApp agent does support direct upload to a beacon (using the -url command line option).   This causes the XenApp agent to upload a .raa file to the beacon which (like inventory) gets passed up the beacon chain until it is consumed by the FNMS servers.   

The intent of this option is that it can avoid the need for a staging database local to the beacon, but in reality it just means that the data is effectively "staged" in the FNMSCompliance database (just that it happens automatically with OOTB functionality).  So, whilst the -url option avoids the need for the beacon side staging DB, it doesn't avoid the need for an inventory connection to be defined to that "staged" data.  So you still need a beacon to define that connection to the "Staged" data - which in this case happens to be the FNMSCompliance db.

If FNMS cloud is being used, then you can't access the FNMSCompliance database so it's not an option - so it's just applicable for specific on prem use cases.   In most cases, the staging db local to the beacon is just more convenient anyway as you could just use a SQL express edition (the volume of XenApp data is usually small) - and if you can also use the staging db for other purposes (business adapters etc) then it is much more compelling.

To answer your specific question tho - it is 'possible' to avoid a staging db, but it's very uncommon, not an option for cloud FNMS and probably should only be considered for very specific controlled environments.

- Murray

View solution in original post

Hi Murray,
Is it possible to get the list of devices used to access the applications through Citrix?
0 Kudos

@atikah_rusdi - you could try configuring a report listing Installation records that includes the Access mode column. This column will indicate whether the installation is locally installed, or accessed remotely (which will typically be through Citrix, but could be through some other remote access technology if you also have other technology in your environment).

image.png(Another tip: If you have a follow-up question which is not the same as the query raised at the start of the thread, it can help to start a new discussion thread in the forum. This will help your question get more visibility in Flexera Community.)

(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)