Troubleshoot DirectFlex Applications

Applications configured to use DirectFlex can sometimes cause conflicts with other applications, which can cause the application to stop unexpectedly.

Problem

An application was configured to launch using DirectFlex, and the application stopped unexpectedly.

Cause

DirectFlex uses "hooks" to be notified of processes launching and exiting, and this technique sometimes conflicts with other software, especially security and anti-malware products.

Solution

1. To resolve conflicts with specific third-party applications, Dynamic Environment Manager provides advanced policy settings. For more information about the policies you can use with specific vendors, see DEM FlexEngine Advanced Configuration Settings for Group Policy Object.

2. Or, you can exclude one or more executables so that they are not affected by the hooking mechanism.

   Exclude executables by creating a DLLInjection.xml file (this file does not exist by default) using the Agent Configuration tab on the Management Console or create the DLLInjection.xml file manually. For more information, see Using Agent Configuration Tab.

   1. Create a folder called AgentConfigurationwithin the \\Server\FlexConfigShare\General\FlexRepository folder.

   2. Create a new DLLInjection.xml file with the following lines.

   <?xml version="1.0" encoding="utf-8"?>
       <agentConfiguration>
         <setting type="exclude" list="sample1.exe|sample2.exe" />
       </agentConfiguration>
   

   3. Add the executables you want to exclude in the list field.

      For example, list="notepad.exe|calc.exe|regedit.exe".

      • To specify more than one executable, use |.
      • A sample configuration file is available in the download package's Agent Configuration Examples\FlexRepository\AgentConfiguration folder.

   4. Save the DLLInjection.xml file with UTF-8 encoding.

What to do next

Depending on the solution you chose, the conflicts are resolved, or the hooking mechanism is deactivated for specific applications. If you chose to exclude the application hooking, configure the Dynamic Environment Manager configuration file for the application to import and export at login and logout.