Update the Virtual Desktops Adapter

The best practice configuration for the Virtual Desktops adapter is to allow direct network access from the appropriate inventory beacon to the Virtual Desktops broker. (Where this is not permitted, you can copy the appropriate PowerShell script to the Virtual Desktops broker, execute it locally, and copy the generated .vdi and .ndi files to the Incoming folder on the relevant inventory beacon.)

As this adapter relies on PowerShell scripts run from the inventory beacon and executing on the Virtual Desktops broker, both these servers must allow at least RemoteSigned execution policy for PowerShell, as described below.

If you are upgrading from an earlier version of the Virtual Desktop adapter, notice that you must run the Active Directory import separately, and prior to exercising the adapter, as listed below. Failure to do this risks the removal of previously-gathered inventory of VDI access to applications.

To update the Virtual Desktops adapter:

1. Check the inventory beacon update is complete (see Update and Deploy Additional Inventory Beacons and sub-sections).
2. Be sure that you have completed an import from Active Directory from all relevant domains.
   For set-up details refer to FlexNet Manager Suite Online Help > Inventory Beacons > Active Directory Tab.
3. On each of the inventory beacon and the Virtual Desktops broker, check the execution policy for PowerShell scripts:
   1. On each machine in turn, open a PowerShell window.
   2. At the prompt, enter Get-ExecutionPolicy.
      Usable settings include RemoteSigned, AllSigned, or Unrestricted (although the latter is not recommended).
   3. If the current policy setting is Restricted, run the following command to set it to RemoteSigned:

      Set-ExecutionPolicy RemoteSigned

4. Create (or update) discovery and inventory gathering rules to target your Virtual Desktops brokers:
   1. In the web interface for FlexNet Manager Suite, navigate to Discovery & Inventory > Discovery and Inventory Rules (in the Discovery group).
   2. Select the Targets tab, click Create a target, and complete the details to target your Virtual Desktops broker(s). Click Create to add your new target to the list of available targets. (If necessary, repeat to create multiple targets.)
   3. Select the Actions tab, click Create an action, and give your new action a useful name and description.
   4. Expand the Citrix XenDesktop environments heading in the accordion list, and select both Discover Citrix XenDesktop environments and Gather Citrix XenDesktop environment inventory. Then click Create to record your new action.
   5. Select the Rules tab, click Create a rule, and in the rule builder that appears, click the View Actions... hyperlink.
   6. For the rule you just created, click Add to rule builder, and in the rule builder, click the View Targets... hyperlink.
   7. For the target(s) you defined, click Add to rule builder, and in the rule builder, click Schedule.
   8. Complete the scheduling details, and click Save as.
   9. Give your rule a meaningful name, and click Save.
      Tip: After a little time (say, 30 minutes) to allow for the relevant inventory beacon to collected its updated rules, you can inspect the rule on the applicable inventory beacon, in its Rules page. (If it hasn't updated yet, click Update now.)
5. After the Virtual Desktops adapter runs (according to the schedule you just created), and after the subsequent inventory import and compliance calculation, you can inspect the inventory from your Virtual Desktops broker:
   1. In the web interface for FlexNet Manager Suite, navigate to Discovery & Inventory > All Discovered Devices (in the Discovery group).
   2. Locate your Virtual Desktops broker in the list of devices.
      Tip: Adding the VDI broker column from the column chooser, and then filtering on Yes, may help you locate this server.
   3. Click the device's name to open its properties, select the Status tab, and expand the XenDesktop environment inventory section of the accordion.
      This is also the location where any PowerShell script errors from the inventory beacon are reported. Should you need additional troubleshooting:

      • Inspect the log file on the inventory beacon for errors relating to Virtual Desktops discovery. This file is located at %PROGRAMDATA%\Flexera Software\Compliance\Logging\BeaconEngine.
      • Should you need to prepare a trace file to submit to Flexera Support, turn on the Scheduling/RemoteExecution tracing options by editing this file on your inventory beacon: InstallationDirectory\Flexera Software\Inventory Beacon\etdp.trace
6. As required, you may need to link the file evidence imported from Virtual Desktops to application records, and ensure that those application records are linked to license records. Wherever possible, link the license records to purchase records to identify the number of your license entitlements.
   Once all the links are in place, the next compliance calculation reflects your compliance position for applications accessible through Virtual Desktops.