An error is displayed while extracting data from System Center Configuration Manager 2008 R2 using the AppDNA Data Extraction tool.To work around this issue, use a later version of Windows Server or install the WoW64 feature while Windows Server is installing.
Occasionally the upgrade from AppDNA 7.11 to AppDNA 7.12 is unsuccessful. The error, "Citrix AppDNA Service failed to start" is displayed. Re-running the installation usually works around this issue.
The Queue Processor Service continues to run after AppDNA is uninstalled. The workaround is to manually stop and uninstall the service.
Exporting of the Remediation report to Word format does not work and displays the error "The directory name is invalid". The workaround is to use an alternative export format - PDF, Excel, or HTML.
Importing some MSIs results in an attempt to enable .NET 3.5 on a machine which does not have 3.5 enabled. Click OK to continue the import process.
An object reference error displays after deleting the mapped application from AppDNA.
AppDNA services cannot be started automatically after a reboot to the operating system following installation and configuration on Windows Server 2016. To work around this issue, manually restart the AppDNA services.
The Install Capture wizard for vSphere machines does not automatically select the automatically-configured snapshot in the drop-down lists.
The reimport of an application which was imported with Install Capture is imported as "unknown" without attachments.
VMware Workstation is missing in the VM Configuration wizard for the App-V Solution.
Loading an OS snapshot from Studio into AppDNA shows "Failed to import OS snapshot" message in Studio and the OS image from Studio is not successfully imported into AppDNA. To work around this issue:
Log on to the machine from the Machine Catalog.
Copy AppDNA Snapshot Manager to this machine.
Run Snapshot Manager on the same machine to capture the OS image.
Log on to AppDNA and manually import the captured snapshot from Import > Operating Systems.