The following issues are known at this release of AppDNA. The issues are organized by:
Action RAG for OBS_MISSING _DOTNET_002 should be GREEN.
A new algorithm is included at this release to detect potentially missing .NET assemblies on which some applications may depend. This algorithm was erroneously assigned an incorrect default action RAG which is more severe than the standard RAG. If this algorithm is triggered, it may result in the action RAG for the app showing RED while the issue report shows GREEN or AMBER. This may also affect the results of the effort calculator report. To resolve this issue:
- Navigate to the report configuration screen in the AppDNA interface.
- Select Configure > Modules > Desktop Compatibility Manager > Windows 7 SP1.
- Locate the relevant *_OBS_MISSING_DOTNET_002 algorithm in the Obsolete Components section.
- In the Action column, select the drop down menu and select Change OS.
- In the Action Detail column, select the drop down menu and select Add redistributable to OS.
- Repeat these steps for each of the desktop and server reporting modules.
- Reanalyze all affected reports.
The following solution-related issues exist at this release:
- Cannot login to AppDNA after enabling WSUS role on Server 2012.
This release introduces the Patch Impact Solution feature. This functionality integrates with Windows Server Update Services (WSUS) to discover OS patches. Enabling this role on Windows Server 2012 causes AppDNA to fail the login process. To resolve this issue:
- Open a command prompt on the server.
- Run the following command:
%windir%\system32\inetsrv\appcmd.exe set config –section:system.webServer/httpCompression /-[name=’xpress’]
- The Patch Impact Solution Wizard prompts for an OS image which is not being used.
During the configuraiton of a new Patch Impact Solution AppDNA prompts you to select an OS image, but does not consider the specified image in the analysis. There is no resolution to this issue. Citrix recommends that you use the default selection when configuring this setting.
- Analysis of all solutions is blocked - Nothing happens after clicking the Analyze button.
If a solution is still being built during a race condition on the server, clicking the Analyze button fails to properly function. To resolve this issue, click the Analyze button again.
- VMWare Workstation is not supported for App-V Solution.
Locally hosted VM technologies are not suitable for the App-V solution because of the need to configure multiple virtual machine instances that will cycle rapidly. To resolve this issue, use one of the available server-based hypervisor technologies.
- Importing some MSIs results in a scenario where AppDNA attempts to enable .NET version 3.5 on a machine which does not have .NET 3.5 enabled.
If the import process detects certain .NET dependencies in the importing application, it attempts to invoke functionality that depends on .NET 3.5. If .NET 4.0 (or later) is installed on the client but not .NET 3.5 the client machine prompts for installation of .NET 3.5.
To resolve this issue, install .NET 3.5 on the client.
- Install capture causes AppDNA to become unresponsive during VM boot process.
While the install capture process waits for the VM to boot, the AppDNA interface becomes unresponsive. To resolve this issue, wait for the machine to finish booting and the AppDNA interface will respond after a period of time. The interface becomes unresponsive again as the VM is reset for each subsequent install capture in the queue.
The following Citrix AppDNA service issues exist at this release:
- Some tasks in the queue processor may become out of synch, resulting in a failed task.
Importing OS images results in multiple tasks being put on the queue. If an import and analysis of applications is running at the same time as an OS import, it's possible that not all of the OS import tasks have completed before the analysis starts. This results in the analysis task failing because the database is in a partially updated state. To resolve this issue, do not run OS import and application analysis at the same time. If you have experienced this issue, start the analysis again after the OS import process finishes.
- The queue processor is not uninstalled when AppDNA is uninstalled.
Under certain circumstances, the uninstall process cannot stop and remove the Citrix AppDNA Service, and it's left in a running state. To resolve this issue open an elevated command prompt and run the following commands:
C:\Windows\System32>sc stop CitrixAppDNAService
C:\Windows\System32>sc delete CitrixAppDNAService