Best Practices for Citrix Configuration with Remote DX
    • Dark
      Light
    • PDF

    Best Practices for Citrix Configuration with Remote DX

    • Dark
      Light
    • PDF

    Article Summary

    This article includes best practice options for deploying Remote DX for Citrix environments, including:

    Install Citrix Workspace app already bundled with Remote DX agent

    This section outlines the procedure for installing and configuring a self-extracting Citrix Workspace App with an integrated bundle for Remote DX.

    Prerequisites

    Installation

    1. Run in the 7-Zip installer. By default, 7-Zip is installed in the C:\Program Files\7-Zip directory.

    2. Extract the 7z920_extra.7z to the folder where you installed 7-Zip, in our case C:\Program Files\7-Zip. When extracted, the file structure must look like this:
      RemoteDX_Bundle_Step2_new

    3. Copy the CitrixWorkspaceApp.exe and curdx_windows_citrix.exe to a folder. Select both files, right-click > 7-Zip > Add to archive.
      RemoteDX_Bundle_Step3

    4. In the Add to Archive wizard, specify a new name for the archive. Click OK to start the compression of both files.
      RemoteDX_Bundle_Step4

    5. Once the file is created, locate the 7zS.sfx in the 7-Zip installation folder.
      RemoteDX_Bundle_Step5

    6. Copy the 7zS.fsx into the folder where you created the new archive. Both files must be located in the same directory:
      RemoteDX_Bundle_Step6

    7. In the same folder, create a config.txt file and insert the following script:

    ;!@Install@!UTF-8!
    Title="Citrix Workspace App"
    RunProgram="install.cmd"
    ;!@InstallEnd@!
    

    RemoteDX_Bundle_Step7

    1. In the same folder, create a new file install.cmd and insert the following text:
    pushd %~dp0
    CitrixWorkspaceApp.exe /silent
    curdx_windows_citrix.exe /VERYSILENT
    

    RemoteDX_Bundle_Step8

    1. Drag and drop the install.cmd into the new archive and confirm the warning with Yes.
      RemoteDX_Bundle_Step9

    2. Open a command prompt and navigate to the path where the files are located.
      RemoteDX_Bundle_Step10

    3. In the command prompt, run the following command.

    copy /b 7zS.sfx + config.txt + "CitrixAndRemoteDXinstaller.7z" archive.exe
    

    Note
    Replace the name of the .7z file according to the file name you created.

    This command creates a new self-extracting file (archive.exe) that includes the 7Zs.sfx, config.txt and the archived 7zip file:
    RemoteDX_Bundle_Step11

    1. Install the bundle and confirm that the installation was successful by pressing CTRL + R. Type appwiz.cpl and check if the Citrix Workspace App and Remote DX appear.

    Add Remote DX process path to the virtual channel allow list using a wildcard for agent versions

    With the introduction of Citrix Virtual Apps and Desktops (CVAD) release 2109, third-party virtual channels must be explicitly allowed. A policy that controls the allow list was automatically enabled with CVAD 2109. To learn more, refer to the official Citrix blog article.

    Use a wildcard in the path name for ControlUp agent versions

    With CVAD release 2206, you can set wildcards in the path of processes that are added to the virtual channel allow list policy. The process path that runs the ControlUp agent enabling Remote DX monitoring includes the version number for the agent. By enabling wildcards, the version does not have to be updated and the path can be entered to the virtual channel allow list policy just the one time.

    To add the Remote DX process path to the virtual channel for allow list, refer to the Citrix documentation, and use the following parameters:

    • Virtual channel name: CUEPUX
    • Process: C:\Program Files\Smart-X\ControlUpAgent\*\cuAgentHelper.exe
    • Allow list entry: CUEPUX,C:\Program Files\Smart-X\ControlUpAgent\*\cuAgentHelper.exe
    Disable virtual channel allow list

    If you don't want to add the virtual channel, you can follow the workaround by disabling the virtual channel allow list policy in CVAD 2109 and later. Once disabled, restart the VDA to apply the Virtual channel allow list policy.


    Was this article helpful?