hits counter
Text to Speech for dyslexis disabilities

Support - Installer Syntax - Wise Installation Studio - Software with a 90 days unlimited trial with all features installed

TryWare90Days.com
Don't waste hours, use minutes
Go to content

Main menu:

Support - Installer Syntax - Wise Installation Studio

 
Wise Installation Studio and Wise Installation Express Release Notes for 7.0 SP2

Introduction

This product offers you two choices for authoring installations: Wise Installation Studio or Wise Installation Express. Both products build on established Wise technologies.

Wise Installation Studio

Wise Installation Studio is an advanced installation authoring suite that supports both Windows Installer (.MSI) and WiseScript installations. Wise Installation Studio is a comprehensive collection of tools and technologies for creating software installations for Windows devices:

  • Windows Installer Editor - This tool is comparable to previous versions of Wise for Windows Installer. Use it to create and edit Windows Installer installation packages. Windows Installer Editor is always installed.
  • WiseScript Package Editor - This tool is comparable to previous versions of Wise Installation System. Use it to create and edit installation packages based on the WiseScript scripting language. WiseScript Package Editor is always installed.
  • Wise Virtual Package Editor - (Optional.) Use this tool to create and edit a virtual software layer, a virtual software project file, or a virtual software archive file.
  • Wise Mobile Device Package Editor - (Optional.) Use this tool to create a project file in .INF format and compile it to one or more .CAB files that install a mobile device application.

Wise Installation Express

Wise Installation Express is a basic installation authoring tool that supports Windows Installer installations. Wise Installation Express consists of the following tools:

  • Windows Installer Editor - This tool is comparable to previous versions of Wise for Windows Installer. Use it to create and edit Windows Installer installation packages.
  • WiseScript Editor (formerly named WiseScript Express) - This tool contains the same scripting interface as WiseScript Package Editor, but it does not contain the Installation Expert interface or other installation development features. Use it to create WiseScripts that are called by a Windows Installer custom action. You access WiseScript Editor from a WiseScript custom action in Windows Installer Editor.

In an effort to simplify our product lines, we have discontinued the Wise for Windows Installer and Wise Installation System products. The technologies that were in those products are now included in Wise Installation Studio and Wise Installation Express.

Please read the following information carefully before using this software. It contains details on new features, enhancements, and other changes to the product. 
 
Do you have the correct upgrade?
If you are upgrading from a previous Wise installation product, verify that you have received the correct upgrade: 
If you were using:then upgrade to:
Wise for Windows Installer - Standard Edition
Wise Installation Express
Wise for Windows Installer - Professional or Enterprise EditionWise Installation Studio
Wise Installation System - any editionWise Installation Studio
Known issues in 7.0 SP2

NOTE: The numbers that precede some items below are Altiris Knowledgebase article numbers.

Maintenance mode operations are prevented on Windows Vista. If the Vista policy "Only elevate executables that are signed and validated" is enabled, you cannot perform any Maintenance mode operations on Wise Installation Studio or Wise Installation Express through Add/Remove Programs. This problem occurs because the Wise installation is per-user (unmanaged) instead of per-machine (managed). To perform Maintenance mode operations re-run the EXE.

51366: Wildcards Details dialog box. In Windows Installer Editor, on the Wildcards Details dialog box, if you add a source directory, immediately delete it, and then click OK on the dialog box, the source directory is linked to the installation. Any files in the source directory that meet the wildcard criteria are added to the installation. This problem occurs on the Files page and the Web Files page. To remove the source directory from the installation, you must open the Wildcards Details dialog box again and delete it. If files were added to the installation from the source directory, you must manually delete them.

Repairing or modifying an .MSI installed into an SVS layer. If an installation contains only one file, then the Repair and Modify options do not work for the application in Add/Remove Programs. This is not a problem if the installation contains more than one file.

SVS and 64-bit computers. The version of the Altiris Software Virtualization Agent that ships with this product does not support 64-bit computers.

Uninstalling the SVS Runtime. (Wise Installation Studio only) If an end user uninstalls the SVS driver (Altiris Software Virtualization Agent) from Add/Remove Programs while active layers are installed, their SVS applications will no longer be visible or functional, although they still appear in Add/Remove Programs. The application files will be restored if SVS is reinstalled.

29212: Reinstalling the SVS Agent. If you uninstall Wise Installation Studio and re-install it, the Altiris Software Virtualization Agent (SVS Agent) does not get reinstalled.
  • To prevent this problem, uninstall the Altiris Software Virtualization Agent before you uninstall Wise Installation Studio.
  • If you uninstalled Wise Installation Studio without uninstalling the SVS Agent first, then start Virtual Package Editor and you will be prompted to install the agent.
30614: Capturing services in a .VSA file. In Virtual Package Editor, if you use SetupCapture to create a .WVP file for an application that contains services, the services are not captured properly. The workaround is to capture directly to a virtual layer and then to export this layer to a .VSA file that you can distribute.
Installation notes for 7.0 SP2

Operating system support. You can install Wise Installation Studio or Wise Installation Express on a computer running the following operating systems:
  • Windows Server 2000 SP4
  • Windows Server 2003
  • Windows Server 2008
  • Windows Server 2008 SP2
  • Windows Server 2008 R2
  • Windows XP Professional SP2
  • Windows XP Professional SP3
  • Windows Vista
  • Windows Vista SP1
  • Windows Vista SP2
  • Windows 7

Installation order. To use the Visual Studio integrated editor, you must install Visual Studio before you install Wise Installation Studio or Wise Installation Express.

SVS compatibility. Wise Installation Studio 7.0 SP2 requires the 2.x version of the Altiris Software Virtualization Agent (SVS Agent). This version is included in the Wise Installation Studio installation.
  • If an earlier version of the SVS Agent is installed on your computer, it is upgraded.
  • If you install Wise Installation Studio on a 64-bit computer, the SVS Agent is not installed and any Wise Installation Studio functionality that requires the agent is disabled or does not appear.

Installation files. This product's installation is run from an .EXE that installs Wise Installation Studio or Wise Installation Express. The Wise Installation Studio installation also installs the Altiris Software Virtualization Agent. During installation, the Wise Installation Studio/Express .MSI file is extracted to \Program Files\Altiris\Setup Files\Wise Installation Studio. The Software Virtualization Agent .MSI file is extracted to \Program Files\Symantec\Setup Files\Software Virtualization Solution. Do not delete these files because they are needed for future repairs.

Upgrading from Wise Installation Express to Wise Installation Studio. You can upgrade from Wise Installation Exress to Wise Installation Studio without uninstalling the previous edition. To do so:
  1. Do one of the following:
  2. Run the installation program and in the Application Maintenance dialog box, click Modify and then click Next.
  3. From the Control Panel, access Add/Remove Programs. In Add/Remove Programs, click Wise Installation Express and then click Change.
  4. In the User Information dialog box, in Product, enter your Wise Installation Studio serial number. Your Wise Installation Express serial number is displayed in the Previous version box.
  5. Step through the remainder of the installation.

Installing this product with other Wise products. We do not support the installation of Wise Installation Studio and Wise Installation Express on any computer that contains any edition or version of Wise Package Studio, Wise for Windows Installer, or Wise for Visual Studio .NET.

Installation directory change. The default installation directory has been changed to Program Files\Symantec\Wise for Wise Installation Studio and Wise Installation Express.

Documentation locations. The Release Notes and Getting Started Guide are available from the Windows Start menu, under Start > Programs > Symantec > Wise Installation Studio or Wise Installation Express.
Documentation for each tool is available from the tool's Help menu.
General enhancements and changes in Wise Installation Studio and Wise Installation Express 7.0 SP2
Operating system support.

We have added support for the creation of installations that run on the following operating systems:
  • Windows Server 2008
  • Windows Server 2008 SP2
  • Windows Server 2008 R2
  • Windows XP SP3
  • Windows Vista SP1
  • Windows Vista SP2
  • Windows 7
Enhancements and changes in Windows Installer Editor 7.0 SP2

NOTE: The numbers that precede some items below are Altiris Knowledgebase article numbers.

Visual Studio. We now support the use of Visual Studio 2008.

Server Roles and Services. On the System Requirements page, you can specify requirements for server roles and services for installations on computers running the Windows Server 2008 or later operating system. By default, when you set requirements for server roles and services, you can only select from a subset of the server roles and services. If you want to check for additional server roles and services, you must first add them to the roles.txt file. The roles.txt file is in the Program Files\Symantec\Wise\Windows Installer Editor directory.

.NET Framework support:
  • On the Systems Requirements page, you can select version 3.5 as the minimum .NET Framework requirement.
  • When you create a Web application that uses .NET Framework 3.0 or 3.5, you can specify the correct ASP.NET version to register with IIS. You specify the version on the ASP.NET tab of the Details dialog box. You access the Details dialog box on the Web Files page after you create a Web site or virtual directory.
  • On the .NET Framework Security page, you can use .NET Framework 3.0 and 3.5 to define security settings.

Windows Installer Runtime 4.5 support:
  • On the Systems Requirements page, you can select 4.5 as the minimum Windows Installer Runtime Version requirement.
  • On the Prerequisites page, you can select 4.5 (32-bit) and 4.5 (64-bit) as the version for the Windows Installer Runtime.
  • On the Download Distributables wizard, you can select to download Windows Installer 4.5. Windows Installer 4.5 has a 32-bit and 64-bit runtime for XP/Server 2003 and Vista/Server 2008.

Internet Explorer 8.0. On the Systems Requirements page, you can select IE Version 8.0 as a minimum system requirement.

Windows Installer SDK Help. The Windows Installer SDK Help has been updated to version 4.5.

Files page. The following issues were fixed:
  • If you added a folder to Destination Computer, an empty, unnamed folder was created above the folder that you added.
  • 41643: You can no longer add files to the All Users folder by double-clicking the files or dragging and dropping them. This prevents the placement of files in the All Users folder where the file's path cannot be correctly resolved.

Versioned files. The following issues have been fixed:
  • When a versioned file was added to an installation using wildcards, the file version information did not always appear in the File table.
  • When an installation's source paths became invalid for some reason, certain files in the installation had their version changed to 0.0.0.0.

.NET assembly files. The following issues have been fixed:
  • Fixed a problem that caused a C++ error when certain .NET assembly files were added to an installation. Also fixed the error message that was incorrect. To enable this fix, install version 2.0 or higher of the .NET Framework and perform a repair of the Wise product so that the Wise assembly that performs assembly scanning is installed to the GAC.
  • Fixed a problem that caused the Generate native-code version during installation option on the Assembly tab of a .NET assembly to not work if the assembly was installed to GAC_MSIL directory.

Firewall Exceptions. The following issues were fixed:
  • If an installation contained Firewall Exceptions, sometimes these exceptions where not removed when the application was uninstalled.
  • 43770: If you use the Firewall Exceptions page to add applications to the Windows Firewall exception list, the installation now functions correctly in Maintenance Mode. If a user modifies the installation and then uninstalls it, the exceptions are removed. If a user uses the installation's Modify mode to install a second feature that contains Firewall Exceptions, the exceptions are created.

SQL authentication. A per-machine installation that executed SQL scripts, failed when using NT Authentication and a remote SQL Server.

Multiple SQL scripts. An "Invalid Connection" error occurred when an installation called more SQL scripts than were designated in the SQL connection limit. This issue is fixed. Each SQL connection is now disconnected after the script runs.

Releases page. (Visual Studio integrated editor only) If a .WSI had two releases and on the Releases page, you unchecked the Build check box for one of the releases, both releases were built when you saved and built the project. This issue has been fixed.

.MSI properties not included in an .EXE wrapper. When you added a prerequisite to an installation and compiled to a single-file .EXE, certain MSI properties such as the version number were not included in the .EXE wrapper. This has been fixed.

Settings for .EXE file that launches external .MSI. If you used the Build Options page to create an .EXE that launched an external .MSI file for multiple languages, the .INI files that were created for the .EXE files of each language were the same. This issue has been resolved.

41446: Digitally signed .EXE that contains prerequisites. If you created an installation that contained prerequisites, was wrapped in an EXE that launched an external MSI, and was digitally signed, you could not launch the MSI. This issue has been fixed.

Prerequisites and command line options. If you passed command line options to an .EXE that contained a prerequisite, the prerequisite and the .MSI did not run. This issue has been fixed.

WiseUpdate. If you created an installation that installed the WiseUpdate client, and on the WiseUpdate page, you specified an interval in Check Interval (days), the interval you specified was ignored when the WiseUpdate client shortcut was run from the Windows Startup group. This issue has been fixed.

Web application. The following issues were fixed:
  • For an installation that creates a Web site or virtual directory, you can override the settings of an existing Web site or virtual directory. You do this on the Installation Settings tab of the Details dialog box for the Web site or virtual directory. However, if you selected the option to override the settings, the installation did not set the ASP.NET version.
  • If you applied the hotfix associated with the Altiris Knowledgebase article 32745 and then created an installation for a Web application, the installation crashed if no Web sites were selected on the IIS Existing Web Site dialog box.
  • When a Web application was installed on a computer running Vista SP1 or later, the physical path did not appear in the IIS Web site details. The absence of the physical path caused errors when you tried to view features of the Web site.
  • On Vista and later operating systems, the virtual directory was not removed from IIS when the application was uninstalled.
  • Windows Installer Editor crashed if you selected Destination Computer as the local path on the Home Directory tab of the Web Details dialog box. If you now select Destination Computer, the selection is ignored and Windows Installer Editor does not crash. The selection of Destination Computer for the local path is ignored because it is not a valid path for a Web application.
  • If you checked options in the Home Directory Permissions section of the Web Site UI tab on the Details dialog box, those options were enabled on the Web Site Information dialog box when the user ran the installation. However, if the user checked those options when installing the Web site, those options were not enabled in IIS.
  • If you added a Web folder to a Web site, it could disappear when you left the Web Files page.
  • Several issues with the use of wildcards on the Web Files page.
  • 41249: If you create a Web application and a web.config file exists in the virtual directory before the virtual directory is configured, the web.config file is modified when the installation is compiled. If the web.config file contained <configuration xmlns="http://schema.microsoft.com/.NetConfiguration/v2.0">, then the file was modified so that it did not work correctly on a Vista computer.

Calling a WiseScript Get Windows Installer Property action. If you called a WiseScript in the Execute Deferred sequence that used the Get Windows Installer Property action, the action did not work on Windows 2000 and Windows 2000 SP4 computers. This issue has been fixed.

WiseScript custom action. If you cut and pasted a WiseScript custom action from the Execute Immediate sequence to the Execute Deferred sequence, the source path for the action was modified incorrectly.

Patch sequencing. The following issues have been fixed:
  • If you created a patch for a package that contained merge modules, the new files were placed before the merge modules changing the sequence of the files.
  • When you used the Patch Creation wizard, if both MSIs were digitally signed and you digitally signed the patch, then the Patch Sequencing dialog did not appear. This issue has been fixed so that you can now use digital signatures and patch sequencing when creating patches.

Saving changes in a project. When you changed the permissions on a file or registry key, you could close the project without being prompted to save it. This issue has been fixed.

Running an uncompiled installation. The Run button no longer lets you attempt to run an installation if the installation failed to compile.

Command-line option /c="release_name". If you compiled an installation with the /c="release_name" command-line option, the .WSI file was not saved before it was compiled. This has been fixed so that the file is saved before it is compiled so that it includes any updated information.

Windows Installer Editor crash. The following issues have been fixed:
  • Windows Installer Editor crashed when you created a transform for an .MSI that contained a table with a Component_ column and a binary data column.
  • Windows Installer Editor crashed when you created two components on the Components tab in Setup Editor and both components had the same file.

CustomAction table. An ExtendedType column has been added to the CustomAction table. This column was required for Windows Installer 4.5.

RadioButton table. The text for the ShutdownOption properties exceeded the length defined for the field. This caused an ICE03 error and a table warning when these options were used in a dialog. This issue has been fixed.
Icon table. Icon table data is no longer deleted when you compile an installation.

Nalpeiron Licensing Support page. The Nalpeiron Licensing Support page and all related functionality has been removed from the product.

Wise Custom Actions. In the documentation, the topic Wise Custom Actions now includes the WiseVerifyUser custom action.

36664: Wise Software Repository. (Wise Installation Studio only) You can connect to the Wise Software Repository of Wise Package Studio 8.0 or later.
Enhancements and changes in WiseScript Package Editor and WiseScript Editor 7.0 SP2

NOTE: The numbers that precede some items below are Altiris Knowledgebase article numbers.

Compiler variables. If the _WISE_ variable in the installation project did not match the path on the computer, the compiler variables were overwritten when the installation was compiled using the /d switch. This has been fixed.

Appended registry value. If an installation appended a value to a multi-string (REG_MULTI_SZ) registry key, uninstalling the installation removed the entire registry key value instead of just the appended value. This issue has been fixed.

Backup Replaced Files dialog box. On the Backup Replaced Files dialog box, an end user can select to create backups of replaced files. If the content of a file did not change but the date/time stamp changed, the file was not backed up. This type of file is now backed up.

Setup Icon. The Setup Icon that you specify on the Build Settings page is now associated with the program executable when you define a digital signature for the executable on the Digital Signature page.

EXE properties. On a Windows Vista or later computer, the copyright and company name information did not appear in the properties of the EXE. This issue has been fixed.

Call DLL Function action. A new option was added to the Call DLL Function script action. When you call a Windows API function that uses the GetLastError() function to report errors, you can select a variable from the Get Last Error Variable drop-down list to hold the return value of that function. Doing so ensures that GetLastError() is called immediately following your function to prevent problems that can occur when you debug the WiseScript.

Check Configuration action. If you checked for the Windows XP operating system on a computer that was running Windows Vista, the check failed. The check should have have returned true on a computer running Windows XP or later. This issue has been fixed.

Check HTTP Connection action. If a user was not an administrator, a Check HTTP Connection action in a WiseScript failed and indicated that it could not find the Web page. This issue has been fixed.

28522: Check HTTP Connection action or Copy Local File(s) action. If the MSVCR71.dll file was not installed on a destination computer, a WiseScript EXE that contained a Check HTTP Connection action or a Copy Local File(s) action whose source is a URL resulted in an error. The error indicated that the MSVCR71.dll file could not be found. This issue has been fixed.

Check In-use File action. If the user does not have write access to the file, this action now returns the value Access Denied. Previously, it did not return any value.

Edit Registry action. If you put an Edit Registry action in a dialog script before the dialog is loaded, the following error message appeared when the script ran: "Unable to load Software Virtualization Agent library. This script requires the Software Virtualization Agent in order to execute." This error message should not have appeared and has been removed.

ElseIf Statement action. An If Statement along with an ElseIf Statement now always checks the condition of the ElseIf Statement.

Execute Program action. When running an Execute Program action multiple times within a While Loop, memory leak problems occurred. This issue has been fixed.

Exit Installation action.
  • When you create an Exit Installation action, you can use a variable enclosed with % in the Application Exit Code field. For example, with a WiseScript wrapper that executes an MSI, you could type %INSTALL_RESULT%. The value of the Application Exit Code would then be the same as the exit code of the MSI. You would then not have to create an Exit Installation action for each possible value that Windows Installer could return.
  • The Exit Installation action is now able to return a failure flag to the MIF file that you specify on the Microsoft SMS page when there is a failure.

Install File(s) action. If you selected the option to replace an existing file only if it is the same or older than the new file, this action always attempted to replace the file. If the new file was older, it returned a message that the file could not be opened. This has been fixed so that it doesn't attempt to replace a file if it does not need to be updated.

Set Variable action. Increased the maximum number of variables that you can define with Set Variable actions to 400.

SVS actions. The following SVS actions were added to Script Editor:
  • Add SVS Exclude Entry. This SVS script action sets an SVS exclude entry on the destination computer. You create an exclude entry to exclude files from a specific layer or any layer on a computer. An exclude entry prevents data that is generated by an application layer from being saved to the layer's writeable sublayer. Instead, the data is saved in the base file system. If the layer is reset, the data is not lost.
  • Remove SVS Exclude Entry. This SVS script action removes an SVS exclude entry on the destination computer.

Dialog Script Editor. Fixed a problem that deleted parameters from Parse String actions in the Dialog Script Editor.

Cutting and pasting script. Fixed a problem that prevented you from copying and pasting script lines when the copied script lines contained a breakpoint.
Enhancements and changes in Virtual Package Editor 7.0 SP2

QWORD-type registry keys. To support QWORD-type registry keys, the following changes were made:
  • SetupCapture captures QWORD-type registry keys correctly.
  • You can create a QWORD-type registry key on the Registry page in Installation Expert.

Repairing SVS. Performing a repair of the SVS driver (Altiris Software Virtualization Agent) no longer disables the Virtual Package Editor.
Technical support

For support options, see the Technical Support topic in the help. The Technical Support topic is the second topic in the help files.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
copyright 2009 by Symantec Corporation. All rights reserved.
Last updated: 14-10-2017
Contact        Privacy Policy        Site Statistics        Sitemap        Terms of use       
Back to content | Back to main menu