Summary This article describes the normal silent installation behavior and clarifies what user should expect to see if installation is launched in silent mode. Synopsis This article describes the normal silent installation behavior and clarifies what user should expect to see if installation is launched in silent mode. Discussion InstallAnywhere installers can be run in three different user interface modes: GUI, Console and Silent. Installers that have the Silent option enabled in the section, Installer UI>Look & Feel>General UI Settings>Allowable UI Modes, can be run in Silent mode using the following command: install ?i silent where ?install? is the installer launcher built after the build process is complete. Silent mode installation doesn?t result in any user interaction. Unlike GUI and console mode installations, if an installer is run in silent mode, no output is sent to the console screen. Upon launching the installer in silent mode in Linux, the user will see the blinking cursor in the console screen until the install is complete and returns to the next prompt in the screen. For Windows installer, launching the silent installation from command prompt results in two different behaviors depending on what type of launcher is selected. For this information, refer to the KB article Q202863 mentioned in the Additional Information Section below. In versions of IA prior to InstallAnywhere 2010 SP1, running the installer in silent mode sent output to the console window in both Windows (when using console launcher type) and Linux machines (as shown below), which was not the expected behavior. This was corrected and addressed in InstallAnywhere 2010 SP1 and versions thereafter. One should run the installer in Console mode or GUI mode for installations that require any kind of user interaction. Additional Information For additional information on Silent installer, refer to the Knowledge Base article Silent Installer On Windows Returns Control To The Command Prompt Immediately. For information on Windows Install Launcher Type, refer to the Knowledge Base article Windows Install Launcher Type. ... View more

Summary When trying to connect to a license server from a remote client behind a firewall a -96 error is recieved and no connection to the license server is made. This results in no valid license for the client. Symptoms When trying to connect to a license server from a remote client behind a firewall a -96 error is received and no connection to the license server is made. This results in no valid license for the client. Cause The cause of this problem is due to the vendor daemon needing to communicate with the client application (InstallShield or AdminStudio) directly. Due to the presence of the firewall this communication is not getting made and therefore the client believes the connection has failed, while on the server side it appears that no connection attempt was ever made. Resolution To resolve the problem a specific port number must be assigned to the vendor daemon. This can be done in 2 ways. You can add to the end of the VENDOR / DAEMON line in the license file PORT=xxxxx You can if using lmadmin to control your license server(s) set this in the user interface Select Administration and then select Vendor Daemon Configuration There is a field labeled "Vendor Daemon Port" and here you should select "Use this port" and enter a port number. This port number may need to be assigned to you by your local IT team. See the image below. In both cases you will need to have your local IT team open the port you have chosen for bi-directional communication. ... View more

Summary This article covers some of the customer issues that AdminStudio 10 Service Pack 2 fixes. Synopsis This article covers some of the customer issues that AdminStudio 10 Service Pack 2 fixes. Discussion To obtain and install Service Pack 2 for AdminStudio 10.0: Ensure that either AdminStudio 10.0 or AdminStudio 10.0 SP1 (Standard, Professional, or Enterprise Editions) or Repackager 10.0 Standalone is installed on the machine. (The same installer will update one or both of these applications if installed on your system.) Download service pack 2. Do one of the following: Double-click the downloaded file to install the update. To install the service pack silently from the command line?Launch the downloaded file from the command line, and pass run_silent. This will only show the Preparing Setup dialog. Following is a sample command line: PathToDownload\adminstudio10sp2.exe run_silent Additional Information The AdminStudion 10.0 Service Pack 2 addresses the following issues: 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. ... View more

Summary On some 64-bit systems, when building an InstallShield media release that is defined to be signed with a .pfx file, the build fails during the execution of the SignTool utility. Symptoms On some 64-bit systems, when building an InstallShield media release that is defined to be signed with a .pfx file, the build fails during the execution of the SignTool utility. The following InstallShield Editions are affected by this problem: InstallShield Standalone Build Cause The InstallShield product is using the 32-bit version of Microsoft's .NET Framework SignTool.exe. Steps To Reproduce To reproduce this problem, perform the following: Install the InstallShield product on a 64-bit system Create a new Basic MSI, InstallScript MSI, Merge Module or Express project. In the Releases view, create a new Release Under the Release's "Signing" tab, specify a .pfx file to sign the installation media Build the release Resolution To fix this problem, overlay the SignTool.exe found in the InstallShield Product' System folder with the 64-bit version of the SignTool utility by performing the following steps: Obtain a copy of the 64-bit version of the SignTool utility. This tool is included with Visual Studio and with the Windows SDK. Close all running instances of the InstallShield product. Make a backup copy of the SignTool.exe file found in the <ISProductFolder>\System folder. (i.e., For the InstallShield 2012 Professional Edition, by default, this location is ?C:\Program Files\InstallShield\2012\System?) Copy the 64-bit version of the SignTool.exe to the <ISProductFolder>\System folder. Rebuild the InstallShield project. Additional Information Additional information on digital signing can be found in the InstallShield Help topic: Digital Signing and Security For a reference of the fields found in the Release "Signing" tab, please refer to the following InstallShield Help article: Signing Tab for a Release ... View more