Wise Package Studio 7.0 SP3 Release Notes

Article:DOC1593  |  Created: 2008-05-01  |  Updated: 2008-05-01  |  Article URL http://www.symantec.com/docs/DOC1593
Article Type
Documentation



Description



Question
What's new in Wise Package Studio 7.0 SP3?

Answer

Wise Package Studio - Release Notes for 7.0 SP3

Introduction

Wise Package Studio helps system administrators and desktop integration teams streamline the process of preparing software applications for enterprise use. Applications that are repackaged with Wise Package Studio can be deployed by all leading software distribution systems.

Please read the following information carefully before using this software. It contains details on new features, enhancements, and other changes to the product.


Contents

Known issues in 7.0 SP3
Installation notes for 7.0 SP3
Upgrading to 7.0 SP3 from an earlier version of Wise Package Studio
Windows Vista-related changes in Wise Package Studio 7.0 SP3
Other enhancements and changes in Wise Package Studio 7.0 SP3
Enhancements and changes in Windows Installer Editor 7.0 SP3
Enhancements and changes in WiseScript Package Editor and WiseScript Editor 7.0 SP3
Release notes for Wise Package Studio 7.0 SP2
Release notes for Wise Package Studio 7.0 SP1
Release notes for Wise Package Studio 7.0
Technical support


Known issues in 7.0 SP3

Wise Task Scheduler issue. (42562) If you install Wise Package Studio Professional, and later add an Enterprise Management Server license, the shortcut to Wise Task Scheduler (an Enterprise feature) is not added to the Start menu. To add the Wise Task Scheduler shortcut to the Start menu, perform a repair:

  1. Start the Wise Package Studio installation.
  2. On the Application Maintenance dialog, mark Repair and click Next.
  3. Step through the remaining wizard dialogs.

Issues in Linux Package Editor. (47349) The Insert Line into Text File action lets you enter a variable into theText to Insert field, which then should insert the value of the variable into the text file. Currently, only the variable name is inserted into the file.

Back to Contents


Installation notes for 7.0 SP3

Where to obtain this service pack. Any registered user of Wise Package Studio 7.x can download this service pack from the Altiris License Management Portal, which is available from the Support section of the Altiris Web site. If you need help, email altirissalesinfo@symantec.com.

Hidden destination directory. (Professional Edition only) If you plan to use a hidden share for the destination directory, create the directory and designate it as hidden before you install Wise Package Studio. During installation, use a UNC path to specify the Wise Package Studio directory. Although this configuration is allowed, we do not recommend it.

SVS compatibility. The latest SVS installation as of this release is installed with Wise Package Studio.

  • If an earlier version of SVS is installed on your computer, it will be upgraded.
  • If you install Wise Package Studio on a 64-bit computer, the SVS agent is not installed and any Wise Package Studio functionality that requires the agent is disabled or does not appear.

SQL Server authentication for creating databases. Previously, when you chose to use SQL Server authentication during the database setup, Wise Repository Manager enabled the SQL Login Mode automatically. Now, you must configure the target database server to support SQL authentication before you set up any Wise Package Studio databases.

Extracted files. The Wise Package Studio installation is run from an .EXE that installs Wise Package Studio and, in the Professional Edition, the Altiris Software Virtualization Agent. During installation, the Wise Package Studio .MSI file is extracted to \Program Files\Altiris\Setup Files\Wise Package Studio. The Software Virtualization Agent .MSI file is extracted to \Program Files\Altiris\Setup Files\Software Virtualization Solution. Do not delete these files because they are needed for future repairs.

Installing Wise Package Studio with other Wise products. Wise Package Studio cannot be installed on any computer that contains Wise for Visual Studio .NET, Wise for Windows Installer, Wise Installation Studio, or Wise Installation Express.

Detecting instances of SQL Server. Due to the way that SQL Server is detected, the product installation is unable to detect a local instance of SQL Server 2005 Express. If you are installing Wise Package Studio Professional on a local computer (as in a server installation), do the following:

  1. During the installation, if the SQL Not Found dialog appears, and you know that SQL is on the computer, click Next to pass that dialog.
  2. During the database configuration in Wise Repository Manager, in theDatabase Name field on the Database Identification dialog, enter the following:
    <ComputerName>\SQLExpress
    where <ComputerName> is the name of the local computer that has SQL Server 2005 Express installed.

SQL upgrade. It is not possible to upgrade from base SQL (Enterprise Management Server) to SP4 on a computer that contains Wise Package Studio 6.x or later. If you want to upgrade your SQL installation to SP4, do one of the following:

  • Upgrade to SQL SP4 before you install Wise Package Studio 6.x or later.
  • If Wise Package Studio 6.x is already on the computer that you need to upgrade, go to Control Panel > Administrative Tools > Services, stop WiseSvc, install the SQL SP4 upgrade, and then return to the Control Panel and restart WiseSvc.

Installation delay. When installing on Windows Server 2003 SP1, there will be a several minute delay on the Updating System dialog. This is normal, and the installation will complete successfully.

Web applications. In order to use any of the Web applications (Preflight, Management Reports, Wise Web Capture) you must restart IIS after installing Wise Package Studio.

Installing Wise Package Studio clients silently. (Not available in Standard Edition.) Because Wise Package Studio requires the Altiris Software Virtualization Agent, when you install the Wise Package Studio client silently, you must include a command line that will install the Altiris Software Virtualization Agent. For details, see "Installing Wise Package Studio Client Silently" in theGetting Started Guide.

Windows XP SP2 firewall issues. On a client computer with Windows XP SP2, you might encounter the following problems:

  • There is a delay in the launching of Windows Installer Editor.
  • When you try to run a Preflight .MSI on the client computer, it does not complete.
  • When you try to view Preflight Analysis, a "Connection Failed" dialog appears.

To resolve the above problems, either turn off the Windows XP firewall or do the following:

  1. Go to Control Panel > Windows Firewall > Advanced Tab.
  2. SelectLocal Area Connection.
  3. Click the Settings button.
  4. MarkWeb Server (HTTP).

Back to Contents


Upgrading to 7.0 SP3 from an earlier version of Wise Package Studio

Database backup. Before you install this upgrade, back up the existing share point directory and all existing Wise Package Studio databases (Workbench, Software Manager, Wise Services (Preflight)).

Database support. Wise Package Studio 7.0 SP3 or later supports only SQL Server and SQL Server Express databases. Microsoft Access and MSDE databases are no longer supported. The upgrade process upgrades existing databases.

Preflight database. The Preflight database was renamed Wise Services database in 6.0, because it also stores data for the Wise Task Manager. It will be used for additional features in future releases. If you used a Preflight database in a version of Wise Package Studio earlier than 6.0, the upgrade process does not change the database name.

Upgrading custom database tables. If any existing, pre-6.0 Wise Package Studio databases contain custom tables that have relational constraints to a standard Wise Package Studio table, do the following:

  1. Before you upgrade, remove the constraints from the custom table.
  2. Install the upgrade.
  3. To determine the changes that were made by the upgrade, view the table or tables that your custom tables were attached to.
  4. Make any changes to the custom tables that are required as a result of the upgrade.
  5. Re-attach the constraints from your custom tables.

Upgrading an unsupported Wise Package Studio configuration. Although it was not recommended, previous versions of Wise Package Studio allowed the share point directory and the Wise Package Studio installation to be on different servers. Versions of Wise Package Studio 6.0 and later do not support this configuration because the Wise Task Manager, a server-side service, requires the share point directory and the Wise Package Studio installation to be on the same server. If you currently have a different configuration, you cannot simply move the share point directory. Instead:

  1. Install Wise Package Studio server on the computer that contains the share point directory. The server installation does not use up a license unless someone actually uses Wise Package Studio on that computer.
  2. On each client computer, access the Workbench Preferences dialog > Repository tab and verify that the share point directory on the new Wise Package Studio server is specified.

Upgrading Pocket PC, Smartphone, and Win CE applications.
Previously, you could build a mobile device application in Windows Installer Editor (on the Mobile Devices page) or in WiseScript Editor (on the Win CE pages). Compiling an installation in either editor created an .INF file that contains information about the directories, files, settings, and configurations that are used to install the mobile device application. Now, you create mobile device installations in the Mobile Device Package Editor tool, and add the resulting mobile device files in Windows Installer Editor or WiseScript Package Editor.

To upgrade your mobile device installations:

  1. Before you install the Wise Package Studio upgrade, back up any .INF files that were created by legacy mobile device installations.
  2. After you install the upgrade, open the .INF file in Mobile Device Package Editor and compile to create one or more .CAB files.
  3. Add the .CAB files to a Windows Installer or WiseScript installation.

Assigning new license numbers. Wise Package Studio 7.0 SP3 requires new license numbers if you are upgrading from a version earlier than 7.0. After you install the upgrade:

  1. Add the new licenses to the Workbench database in User Licensing Setup (Edit menu > User Licensing).
    If you purchased multiple licenses, you might have received a .WLC file that contains the license numbers. You can import the licenses from this file on the Add Serial Numbers dialog.
  2. Assign the new licenses to users:
    - Professional Edition: Let users select a license during the Wise Package Studio logon or assign users on the User Licensing Setup dialog.
    - Enterprise Management Server: Assign users on the User Licensing Setup dialog. Note: The users and groups in Security Setup are not changed by the upgrade.

Converting an evaluation version. You can convert an evaluation version to a production version without uninstalling the product:

  1. Purchase the product and obtain a production serial number.
  2. Start Wise Package Studio and click Serial Number on the Evaluation dialog.
  3. Enter the production serial number and click OK. The evaluation version is converted to a production version. The next time you start Wise Package Studio, the Evaluation dialog no longer appears.

Custom Reports.If, in a version of Wise Package Studio earlier than 7.0, you added custom reports to the Reports menu in ConflictManager, Software Manager, or Workbench, these reports no longer appear.

Back to Contents


Windows Vista-related changes in Wise Package Studio 7.0 SP3

NOTE: The numbers that precede some items below are issue tracking numbers.

Windows Vista shield icon. (Windows Installer Editor) In Setup Editor, you can select Elevation Shield as a control attribute for a dialog's pushbutton control. This attribute adds the Windows Vista shield icon (User Account Control elevation icon) to a pushbutton control.

Web installations on Vista. (Windows Installer Editor) Web installations on a workstation running Windows Vista (IIS 7.0) let end users create new Web sites.

Prerequisite launch conditions. (Windows Installer Editor) The Prerequisite Launch Conditions dialog box lets you select launch conditions for Windows Vista and Windows Server 2003. Access this dialog box from the Prerequisites page, when you add a prerequisite.

Running WiseScript custom actions on Vista. (WiseScript Package Editor, WiseScript Editor) Prior to this release, when an .MSI contained a custom action that ran a WiseScript, the installation would fail on Windows Vista due to UAC prompting on the WiseScript execution. New options on the Build Settings page let you specify a manifest file for WiseScripts that will run on Windows Vista. The manifest file, which is embedded in the .EXE during compile, indicates the run level for the WiseScript .EXE at run time.

Check for Windows Vista. (WiseScript Package Editor, WiseScript Editor) In Script Editor, the Check System Configuration script action lets you determine whether Windows Vista is running on a target computer.

New options for elevating Windows Installer installations. (Windows Installer Editor) Under Windows Vista, an installation that accesses protected areas on the destination computer requires administrator privileges. In Installation Expert, on the Windows Installer Options page, you have the following options:

  • No elevation required. This option replaces theEnable User Account Control (UAC) check box that was added in an earlier release. Use it to create a standard user installation that does not require elevation.
  • Elevate Deferred Execution sequence only. This is the preferred option for most installations. Typically, actions that require elevation should be in the Execute Deferred sequence.
  • Elevate entire installation. Elevate the entire installation when it contains actions that require elevation but are outside the Execute Deferred sequence.

System requirement for Windows Vista. (WiseScript Package Editor/WiseScript Editor) On the System Requirements page in Installation Expert, the Windows NT Version requirement supports Windows Vista.

Specifying a mapped network drive as the installation directory. (WiseScript Package Editor/WiseScript Editor) Users with less than administrative privileges can select a mapped network drive as the installation directory when such installations are run on computers running Windows Vista.

Enabling SetupCapture and Test Expert for Vista. A security setting in Vista prevents the following features from working: Virtual Capture and SmartMonitor in SetupCapture and the application execution tests in Test Expert. When you try to use any of these features, a prompt appears and provides the option to disable the security restriction. If you choose to disable the security restriction, the following registry setting is set:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows>LoadAppInit_DLLs=1
The initial default for this setting is 0. Caution: Disabling this restriction may increase your computer's vulnerability to malicious attack. However, if you run SetupCapture and Test Expert in a testing environment, the increased vulnerability might not be a critical issue.

General Information page. In Windows Vista, the file Properties dialog box does not contain summary information. Therefore, the information that you enter on the General Information page does not appear on destination computers that run Vista.

UAC prompts during patch installation on Vista. During Patch Creation, you can add a digital signature to the patch to let standard users install the patch. However, some versions of Vista might prompt for administrator credentials when you install a patch that represents a major upgrade. A major upgrade is one in which the ProductCode property is changed and the major version part of the ProductVersion property is changed.

53423: (Windows Installer Editor) The Description tab that appears on the details dialog box for all custom actions lets you document the custom action, which is a requirement for Windows Vista validation. The Description tab was missing from the dialogs of several custom actions, but has been added.

55590: Resolved a fatal error that occurred if you installed a Web application on a Windows 2003 server with the Web dialogs enabled.

56761: If an .MSI contained a custom action that ran a WiseScript, the WiseScript would not run when installing the .MSI on a computer running Windows Vista with UAC enabled. This has been fixed.

57058: (SOE Snapshot) Resolved the problem of not being able to create an SOE snapshot of a computer that runs Windows Vista.

57101: (WiseScript Package Editor, WiseScript Editor) Resolved the problem of dialog controls not being able to recognize mapped drives on a computer that runs Windows Vista with UAC enabled.

57107: (WiseScript Package Editor, WiseScript Editor) Resolved the problem of per user shortcuts being installed to each user's profile on a computer that runs Windows Vista.

57156: (WiseScript Package Editor, WiseScript Editor) The Get System Information script action could not retrieve the First Network Drive on a computer running Windows Vista with UAC enabled. This custom action now works unless the network drive requires a password, in which case it will not be detected.

57137: (Windows Installer Editor) If an .MSI installation had a system requirement for IIS, the installation would fail on a computer running Windows Vista with UAC enabled even when the correct version of IIS was installed. This has been fixed.

57565: (Windows Installer Editor) Resolved problems that occurred during compile of a 64-bit merge module: a merge module naming convention error would occur and subsequent compiles would create duplicate *.guid directories.

57641: (Windows Installer Editor) Resolved the problem of firewall exceptions not being added to the Windows Firewall exception list on computers that run Windows Vista with UAC enabled.

58046: (Windows Installer Editor) Resolved the problem of not being able to install Web applications on a computer running Windows Vista unless IIS 6 Metabase and IIS 6 configuration compatibility was enabled.

58735: (Windows Installer Editor) Adding prerequisites to an installation caused the Vista Program Compatibility Assistant to appear when an end user ran the installation on Vista from a network location. This has been fixed.

59256: (Windows Installer Editor) Resolved the problem of not being able to pass properties to a Call Custom DLL action in the execute deferred sequence on a computer that runs Windows Vista.

60188: (Windows Installer Editor) Made .NET scanning work on computers that run Vista.

61069: (Windows Installer Editor) The Wise automation Wscript.CreateObject no longer fails on computers running Vista if you go to an elevated command prompt.

64564: (SetupCapture, Test Expert) Due to changes that were made to the Vista 64-bit operating system, 32-bit processes and applications can see a recurring Wow6432Node registry hive. Previously this information was not visible to 32-bit processes and applications. This situation caused the SetupCapture snapshot scan to hang and crash. To prevent this problem, the HKLM\SOFTWARE\Wow6432Node\ registry hive and its subkeys have been added to the hard-coded list of exceptions that SetupCapture, SOE Snapshot, and Test Expert ignore.

Back to Contents


Other enhancements and changes in Wise Package Studio 7.0 SP3

NOTE: The numbers that precede some items below are issue tracking numbers.

Home pages. The product Home pages were removed from Windows Installer Editor, WiseScript Package Editor, Virtual Package Editor, and Mobile Device Package Editor.

SetupCapture and SOE Snapshot. The option to apply configuration setting changes to the current capture without changing the configuration file is now on the Welcome dialog. This option used to appear at the bottom of each configuration tab. This option is enabled only if the user has permission to use the SetupCapture Configuration tool. If the Settings button on the Welcome page is disabled, selecting this option enables it. The user can then modify the settings for the current capture.

Repackage into .VSA format process. On the Project Setup dialog box, you can select a predefinedRepackage into .VSA format process to repackage an installation into a virtual software archive file (.VSA). This process provides a logical, consistent approach to repackaging installations into Virtual Software Packages (VSPs). The template for this process also appears on the Process Templates Setup dialog box.

Virtual Package Editor. The following changes were made to the Virtual Package Editor:

  • A Releases page has been added to Virtual Package Editor. The Releases page lets you create a WiseScript .EXE wrapper for the .VSA file. This wrapper contains the logic needed to install a .VSA file on an end user's computer if they have the SVS Agent installed. This WiseScript also installs the logic that lets the end user repair or remove the Virtual Software Package (VSP) from Add/Remove Programs. The .EXE wrapper has a WiseScript project file (.WSE) that you can edit from the Releases page to add additional functionality to the installation.
  • On the Delete Entries page, when you add a delete entry, you must specify its type. You can specify a system or user delete entry. You can specify a system delete entry for system-specific folders only. You can specify a user delete entry for any folder. A user delete entry applies to all users. You can also sort delete entries and select multiple delete entries to delete.
  • From the Help menu of Virtual Package Editor, you can download the latest SVS Agent (Software Virtualization Agent).

Review and edit InstallTailor changes. The transform that InstallTailor creates can set the values of certain properties even if you do not explicitly define those values when you run InstallTailor. (For example, the base installation might set a property based on the destination computer's operating system. However, the operating system on which you run InstallTailor might differ from the operating system on your target computers.) The new Captured Changes page in InstallTailor displays the changes that it captures when you simulate the installation and lets you do the following:

  • Delete the changes that should not appear in the transform.
  • Edit the captured changes.
  • Add changes to property, feature, and dialog values that InstallTailor did not capture.

44887: ConflictManager: Fixed a problem that caused the File Conflicts by Package report to display conflicts for all packages in the application instead of the selected package.

55224: Software Manager: If you imported a package from an administrative installation, you could not change the status of the package to Available. This has been fixed.

53306: When you made a package available, not all uncompressed external files were copied to the Available Packages directory. This was more likely to happen when the package contained a large number of files. This has been fixed.

53778: Package Validation did not detect 16-bit files when it validated a package. This has been fixed in the Package Validation tool in both Workbench and Windows Installer Editor.

56637: In both ConflictManager and Windows Installer Editor, the Resolve Conflicts tool did not always identify all conflicts. This has been fixed.

57441: ConflictManager and Software Manager displayed an incorrect conflict status for .MSIs that contained different version of the same file in different directories. This has been fixed.

57797: On the Project Management tab, if you changed the owner of a task in one project, the owner of that same task in another project was sometimes changed. This has been fixed.

57957: If you ran the SetupCapture snapshot method and installed a file in Documents and Settings\All Users\Application Data, the captured application would place that file in AppDataFolder instead of CommonAppDataFolder. This has been fixed. (See Knowledgebase article32880.)

58111: Fixed problems that caused Legacy Setup Conversion to fail during conversion of a WiseScript .EXE.

58671: (Software Manager) When you import a transform into the Software Manager database, you can apply it to a blank Windows Installer database (schema.msi). However, certain transforms cannot be applied to a blank database. Previously, this caused an error during the import. Now, the transform you specify is checked before the import begins and a message appears if it cannot be applied to the blank database.

59113: Fixed a problem in Security Setup that enabled users to delete packages from Software Manager even if they did not have permissions to do so.

59260: (ConflictManager) Fixed a problem that caused ConflictManager to incorrectly report packages as needing conflict detection.

59758: (ConflictManager) After conflict resolution, some exported .MSIs contained components with duplicate component GUIDs. This has been fixed.

60839: (SetupCapture) Permissions are captured when you use SetupCapture to create a virtual software archive file (.VSA).

61203: In Wise Package Studio 7.0 SP2, the Table Query did not resolve the AppKey and PackKey columns to the Application and Package values. This has been fixed.

61870: (Virtual Package Editor) To support QWORD-type registry keys, the following changes have been made:

  • SetupCapture captures QWORD-type registry keys correctly.
  • You can create a QWORD-type registry key on the Registry page in Installation Expert.

62699: If you upgraded from Wise Package Studio Professional to Enterprise Management Server, Workbench reports would not include projects that were created in the Professional Edition. This has been fixed.

62984: (Windows Installer Editor and WiseScript Package Editor) To avoid web connection errors when you use WiseUpdate with IIS 6.0 or later, you must add a MIME type to the IIS server for each type of file that you let users download from the Internet. Examples: .MSI and .INI.

63103: (Workbench) Fixed a problem that caused inaccuracies in the Assignments by User report. (See Knowledgebase article39376.)

63177: (Virtual Package Editor) Fixed a problem that prevented the Virtual Package Editor's SetupCapture tool from executing cmd.exe.

63962: When a new process was assigned to a Workbench project, existing data about the project was removed from the database. This prevented the project from appearing on Workbench reports. Now, the appropriate project data is retained when a new process is assigned. Also, the project creation date reflects the original creation date and not the date when the project's process is modified.

63981: In Tool Configuration, you can set theAuto Task Checking option to mark the task complete if the file changes. However, if the task's command line contained Wise Package Studio variables, the task was never marked complete. This has been fixed.

Back to Contents


Enhancements and changes in Windows Installer Editor 7.0 SP3

NOTE: The numbers that precede some items below are issue tracking numbers.

Convert .EXE, WSE, and .IPF installations to Windows Installer format. A new tool lets you convert the following script-based setup programs into Windows Installer packages: Microsoft SMS (.IPF, .EXE) and WiseScript (.WSE, .EXE). To do so, select Tools menu > Convert WiseScript Installation or SMS Installer. (In Visual Studio: Project menu > Convert WiseScript Installation or SMS Installer.)

New language support for installation dialogs. Pre-translated text strings for the Hindi, Romanian, and Thai languages are available from the Languages page.

IIS 7.0 support. Support for IIS 7.0 is set by default for new IIS Web applications. You can access this support option on the Installation Settings tab of the Web site Details dialog box. When this option is enabled, a web.config file is added to the installation that contains the settings specified on the Web site Details dialog box.

Cannot change a transform's base database. On the Transform Details dialog box, which appears when you save a transform file, the base database field indicates the .MSI on which the transform is based. Because this field should not be changed, it is now read-only.

Support for .NET Framework versions:

  • On the Prerequisites page, you can select versions 3.0 and 3.5 of the .NET Framework runtime.
  • On the System Requirements page, you can select Version 3.0 as the minimum .NET requirement.
  • In the Download Redistributables wizard, you can download versions 3.0 and 3.5 of the .NET Framework runtime.

Support for .NET Framework 3.5:. In Windows Installer Editor > Installation Expert > System Requirements page, an option for Windows Server 2003 SP1 has been added to the Windows NT Version drop-down list.

Support for Windows Server 2003 SP1. In Windows Installer Editor > Installation Expert > System Requirements page, an option for Windows Server 2003 SP1 has been added to the Windows NT Version drop-down list.

Specifying the .MSI name for releases. On the Release Details dialog, the.MSI File Name field has been changed as follows to provide more flexibility in naming the .MSI files that result from compiling releases.

  • You can prefix the file name with a subdirectory path, so that you can save each release's .MSI in a specific subdirectory of the installation file's location. Previously, this field did not accept the \ character.
  • You can enter property names surrounded by brackets to populate the file name or its subdirectory with the value of one or more properties. Example: [ProductName].msi.
  • When you include a property in.MSI File Name, you can use one or more specific parts of a property's value if its segments are period delimited. This is most useful for adding all or part of the product version number to the file name. The syntax is: [property_name.%segment_number%segment_number]
    Example: If you enter Application_[ProductVersion.%1_%2].msi as the file name, and the value of ProductVersion is 1.05.07.25, the resulting file name will be Application_1_05.msi.

Excluding dependencies from assembly scans. When you add a .NET assembly to an installation, Windows Installer Editor can scan the assembly's manifest for dependencies and either add the dependency files to the installation or prompt you to add the dependency files. By default, certain dependencies are excluded from assembly scans in all .NET installations. These global dependency exclusions are hard-coded. Now, you can create an XML file that overrides the hard-coded dependency exclusions with exclusions that you define. The XML file must be named dotnetexclude.xml and must be in either of the following locations: the Windows Installer Editor subdirectory of this product's installation directory on the local computer, or the top level of the share point directory. For details, see the Windows Installer Editor documentation. Note: The global exclusion list is different from the installation-specific exclusion list that is created when you choose not to include a scanned dependency in an installation.

Install the .MSI into an SVS Layer.The Build Options page has new options that let you create an .MSI installation that installs the .MSI into an SVS layer if the SVS Agent is installed. These options let you take advantage of the benefits of an .MSI and an SVS layer. When you install an .MSI into a layer, you avoid the possibility of conflicts with other applications including another version of the same application. You also make it possible for an end user to quickly restore an application to its original state by resetting the SVS layer from Add/Remove Programs. The following are some basic aspects of this feature:

  • The option to install the .MSI into an SVS layer is enabled only when you select an option to create an .EXE on the Build Options page.
  • The .EXE file that is created contains the logic needed to install the .MSI into an SVS layer.
  • You can mark an option to install the .MSI normally if a compatible version of the SVS driver (Altiris Software Virtualization Agent) is not installed on the end user's computer. If you clear this option and the SVS driver is not installed, the installation fails.
  • The Edit Script button on the Prerequisites page lets you edit the WiseScript project file (.WSE) that compiles to create the .EXE file.
  • The Build Options page has several options that let you exclude user data files from the SVS layer. You exclude files so that end user's data files are not lost when the end user resets the application from Add/Remove Programs. You can exclude files by extension or directory or by selecting an option that excludes files whose extensions are specified on the File Associations page.
  • An end user can perform maintenance on an .MSI that is installed into an SVS layer from Add/Remove Programs. The maintenance mode dialogs let them remove, repair (Windows Installer repair), modify (change the application features that are installed), or reset the SVS layer. When an SVS layer is reset, it returns the application to its original state.
  • Only English support is provided for the maintenance mode dialogs and any error messages that are controlled by the WiseScript .EXE wrapper.

Proxy settings for the Download Redistributables wizard. The Advanced button has been removed from the Download Redistributables wizard. This button let you modify your Internet connection settings if necessary. Now, if you need to go through a firewall or proxy server to get to the Internet, the Download Redistributables wizard uses your browser's proxy settings. To change your Internet connection settings, refer to your browser's documentation.

Support for Microsoft Driver Install Frameworks (DIFx). The Device Driver installation template no longer contains the DIFxApp merge module. To obtain the latest version of the DIFxApp merge module, use the Download Redistributables wizard to download it from the Wise Web site.

Customizing the WiseUpdate dialog boxes. You can customize the dialog boxes that appear during a WiseUpdate. When you add WiseUpdate support to an installation, the merge module WiseUpdate.msm is added to the installation on the Merge Modules page. That merge module contains the WiseScript WiseUpdt.wse, which contains the WiseUpdate dialog boxes. Therefore, to customize those dialogs, you can edit the WiseScript and then edit the merge module. For complete instructions, refer to the Windows Installer Editor documentation.

33637: The Feature Details dialog was not enforcing the 32-character limit on the feature name, which caused problems with writing feature information into the registry properly. This has been fixed.

52927: Fixed a problem that caused a C++ error when certain .NET assembly files were added to an installation. To enable this fix, do the following:

  • Install version 2.0 or higher of the .NET Framework.
  • Perform a repair of the Wise product so that the Wise assembly that performs assembly scanning is installed to the GAC.

55137: When an installation containing .NET assemblies was recompiled, the assembly type was reset to .NET even if the option to rescan assembly attributes was disabled, which caused an error to occur. This has been fixed.

55156: When assembly scanning failed, the error message that appeared was incorrect. The error message has been fixed. In addition, item 52927 fixed the cause of the scanning errors.

55590: Resolved an error that occurred if you installed a Web application on a Windows 2003 server with the Web dialogs enabled.

56303: If you resolved conflicts in Windows Installer Editor and saved the changes as an .MST, any .CAB file that should have been created was not created. This has been fixed.

56634: Fixed a problem that caused a crash when a single WiseScript performed more than one Execute VBScript action.

56996: If you created an installation in Windows Installer Editor 6.0 that contained a virtual directory and then opened and compiled the installation in Windows Installer 7.0, the installation would no longer install the virtual directory. This has been fixed.

57820: If you created an installation for a Web application in Windows Installer Editor 6.0 and then opened it in Windows Installer Editor 7.0, any changes to the ASP.NET version were lost when the installation was compiled. This has been fixed.

57988: The inability to properly read the UTF8 code page caused a problem with opening an .MSI file. This has been fixed.

58140: Removed a check that disabled the Digital Signature page in 64-bit installations.

58911: Fixed a problem that occurred when you opened the .NET Framework Security page on a computer that had a network client installation of Wise Package Studio.

59457: (Wise Automation) When retrieving properties of FeatureCondition objects where the property is a collection, the collection returned was the collection for the feature (without any condition) instead of the FeatureCondition. This has been fixed by changing the behavior of the automation as follows:

  • Iterating a feature gives all components/files/etc. assigned to that feature regardless of condition (old behavior only gave blank condition items)
  • Iterating a feature's conditions includes the blank condition - this is the way to get blank condition files/components etc. only

62603: When you added a prerequisite to an installation, and then 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.

62731: 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. This has been fixed.

63010: To avoid web connection errors when you use WebDeploy with IIS 6.0 or later, you must add a MIME type for "*" (asterisk) to allow the WebDeploy download files (.000, .001, .002, and so on).

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

64105: Fixed a problem that caused a crash when you created a transform for an .MSI that contained a table with a Component_ column and a binary data column.

64564: Due to changes that were made to the Vista 64-bit operating system, 32-bit processes and applications can see a recurring Wow6432Node registry hive. Previously this information was not visible to 32-bit processes and applications. Windows Installer Editor has been updated so that this hive does not appear on the Registry page in Installation Expert.

64650: In Wise Options (Tools menu > Options > Advertising tab), theAutomatically add self registration check box has been changed so that it is unchecked by default. When the option toScan advertising information into advertising tables is selected (as it is by default), Windows Installer Editor can automatically add Windows Installer advertising information for the files in the installation, and there is no need to self-register. In addition, the latter method is recommended over self-registration.

Back to Contents


Enhancements and changes in WiseScript Package Editor and WiseScript Editor 7.0 SP3

NOTE: The numbers that precede some items below are issue tracking numbers.

New SVS actions. The following SVS actions were added to Script Editor:

  • Change SVS Layer GUID. This SVS script action changes a layer's GUID. For example. you could use this action to create a copy of a layer that is seen by SVS as a different layer.
  • Get SVS Layer Info. This action retrieves information about an SVS layer on the destination computer and puts that information into different variables.
  • Initialize SVS. This action initializes the Software Virtualization Agent so that you can communicate with it.
  • Install SVS Package. This action installs Virtual Software Packages (VSPs) on the destination computer. You can use this action to create a WiseScript that installs any number of VSPs. When you add this action to a WiseScript, you must specify a VSP in the virtual software project file (.WVP) format.
  • 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.

Proxy settings for the Download Runtimes wizard. The Advanced button has been removed from the Download Runtimes wizard. This button let you modify your Internet connection settings if necessary. Now, if you need to go through a firewall or proxy server to get to the Internet, the Download Runtimes wizard uses your browser's proxy settings. To change your Internet connection settings, refer to your browser's documentation.

Support for an increased number of variables. Increased the maximum number of variables that you can define with Set Variable actions to 400. The documentation incorrectly states that you can define up to 986 variables.

55178: If an include script occurred more than once in the same .WSE file, it sometimes caused an infinite loop. This has been fixed.

58103: On the Registry page, you can import a .REG file that contains a registry key whose path is longer than 128 characters.

58124: On the Registry page, when you import a registry value from a .REG file that is longer than 128 characters, that value is no longer truncated.

60743: Fixed a problem that caused digitally-signed WiseScript .EXEs to not return a return code.

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

63326: When you double-clicked a .WSE file, it opened in WiseScript Editor instead of WiseScript Package Editor. Now, .WSE files always open in WiseScript Package Editor if it is installed.

63402: 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, select a variable from theGet 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.

63596: Fixed a problem that prevented you from copying and pasting script lines when the copied script lines contained a breakpoint.

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

Back to Contents


Technical support

For support options, visit the Altiris Service Center, which is your complete online resource for Altiris product support. Access the Altiris Service Center from the Support section of the Altiris Web site. Use the Altiris Service Center to access the following Altiris support tools and services: Knowledgebase, support forums, License Management Portal, Altiris Support Helpdesk, and user groups.



Legacy ID



41456


Article URL http://www.symantec.com/docs/DOC1593


Terms of use for this information are found in Legal Notices