Hi! I've seen this exact same issue before, can I validate, did you update the Integration recently? Did you have the XML version of the adapter and changed it to the APP from the Store?   ... View more

Hi! As was previously noted that document is not available in German, but the online help is, you can find that from here: online help   ... View more

Hi! You can also enable it via the targets in the FNSM UI, give the target the IP range you wish to start monitoring usage and enable application usage tracking   ... View more

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. ... View more

Hi! Yes we've got customers using FNMS as a main Hardware Asset Management tool as well as a hybrid solution where some data is kept in FNMS and other in the customers main HAM Solution. The benefit, would be to have your licenses, software details and Hardware Life cycle management all in a singe location, with out having to replicate data across many sources and having to make sure it's correct in all of the locations. Regarding Scope, as mentioned above, that varies, we've got from everything, to simply reflecting the data from another system. ... View more

Hi Kimberly!   You can change the application server of the old beacon to the new application server, this should make sure that all agents will know both beacons. Once you are fairly confident that all agents have updated their policy, you can delete the old beacon. You can also create an A record just to divert any strays to the new beacon. Make sure that the new beacons FQDN is resolvable by all clients prior to deleting the old one however.   Would this approach work for you? ... View more