The Flexera Community is currently in maintenance mode to prepare for the upcoming launch of the new community. Click here for more information.
Issue Number | Issue Summary |
IOA-000062809 | When using Automated Application Converter to perform automated repackaging of a legacy setup on a Windows 7 virtual machine, extra files in the Windows\System32 directory are captured, making the repackaging process take longer and resulting in larger Windows Installer and virtual packages. These extra files from the System32 directory are not required and should not be captured. |
IOA-000064729 | In the Application Compatibility Dashboard report, the count of packages that fall into the No Issues and Not Tested categories in the pie charts was not calculated correctly. |
IOA-000064837 | The detail reports that are opened by clicking on one of the categories in the Internet Explorer 8 Presentation Compatibility pie chart on the Application Compatibility Dashboard do not display any data for web sites. |
IOA-000065159 | After running the AdminStudio 10.0 SP1 installer, the Application Readiness Dashboard reports could no longer be viewed on the Report Center tab of AdminStudio Enterprise Server. |
IOA-000065163 | The Transform Status property, which is displayed on the Packages tab of Automated Application Converter, should indicate whether No Transforms, One Transform, or Multiple Transforms are associated with a package. When a package is initially added, the Transform Status property is correctly updated. However, when opening a saved Automated Application Converter project file, the Transform Status property for all packages is set to No Transforms even for packages with associated transforms. |
IOA-000065237 | After running the AdminStudio 10.0 SP1 installer on an installation of AdminStudio 10.0 Professional, and upgrading the Application Catalog to 10.0 SP1, the Process Assistants tab (formerly the Projects tab) was no longer displayed. |
IOA-000065270 | AdminStudio virtual conversion process was using Windows XP style paths for user profile locations when needed in INI files contained in App-V packages. This could cause problems for a small sub-set of applications when running on Windows Vista or newer. Now default behavior is to use Windows Vista/7 style profile paths. This can be changed by modifying the AppV.xml configuration file. |
IOA-000065271 | The following enhancements were made to the Application Manager configuration file support for import: General Section ? RefreshExtendedAttributesSchema?Values are Y or N. The default value is N. ? ExtendedAttributesConfigFile?The file path to the Extended Attributes XML file. These two parameters can be used to specify a new Extended Attribute schema and to have it loaded into the Application Catalog. Note ? Do not delete extended attributes that are already in use in the database (those that already have data specified). Package Section ? ApplicationName?Name of application to add this package to. If an application does not exist, it will be created. Also, each application name in a given group should be unique. ? SetupName?This property is now applicable for Windows Installer packages. ? EA1, EA2, ...?Use this property to specify a value for a particular Extended Attribute. Separate the Extended Attribute name and value with a semicolon. OtherSetupFile Section The section name for the Other Setup Type section was change from OtherFile to OtherSetupFile. Note ? Also, the Group field now allows multiple groups to be specified (separated by semi-colons). |
IOA-000065308 | If the Build Windows Installer Packages option on the Project Options dialog box of Automated Application Converter is set to True, Automated Application Converter will crash when converting a Windows Installer package to an App-V package, and the conversion fails. |
Oct 29, 2018 04:08 PM