Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrade.
Please accept our apologies in advance for any inconvenience this might cause.

Endpoint Management Community Blog

Showing posts tagged with Wise Packaging
Showing posts in English
WiseUser | 09 Mar 2009 | 0 comments

MSI logging can be expanded beyond installs and uninstalls.  It can also record any MSI action, such as repairs or self-heals.  Setting up a system policy to enable MSI logging can do this.   Since policies are presented locally as registry entries, use these steps to do it:

1. Launch Regedit and navigate to HKLM \Software\Policies\Microsoft\Windows\Installer.
2. Create a REG_SZ value named Logging.
3. Set the data to voicewarmup
4. Done.

WiseUser | 09 Mar 2009 | 0 comments

Special characters in many cases are reserved in an install, and getting them to display or write to a destination computer requires some extra steps.

Using a property:

This is handy when working with large special characters,

1. Create a property that stores the special characters to be used. In the installation reference the property value rather than the special characters,

Special characters may be ~`!@#$%^&*()_+=-{}|\:";'<>,.?/[]

Eg: VARSPECIAL=@computername&#

WiseUser | 09 Mar 2009 | 1 comment

Removing files is done when a package needs to clean up items a prior package left behind, such as deleting a Bloom.ini file from an earlier release. 

Follow these steps to have a package remove a file :

1. Launch Wise, open the appropriate WSI or application MST and go into the Setup Editor
2. Switch to the Tables tab
3. Go to the RemoveFile table and create a new row
4. For FileKey enter the name of the file
5. For Component select any from the drop-down list
6. For FileName enter the name of the file once again
7. For DirProperty, switch to the Directory table and note the appropriate INSTALLDIR property corresponding to the location of this file

 

 

 

WiseUser | 05 Mar 2009 | 0 comments

Component errors can happen from time-to-time, especially with setup captures. We need to know to look for them.  Here’s how to check an install for a component error:

1. Launch Wise and go into the Setup Editor

2. Switch to the Components tab

3. Any components with errors will be displayed in Red

4. Right-click on the component name and select Show Errors

5. Use the information displayed to correct the component errors

CStoneRun | 26 Feb 2009 | 2 comments

I've spent days trying to sort out a silent uninstallation of a pices of software packaged with Wise installer. I can't find a way to make it run silently and not reboot. I've used /s /S /U /a /A  and I've added a comment to the unwise.ini file. nothing I do prevents this from rebooting suddenly upon uninstall. Can nayone help me please?

Thank you

R-Vijay | 13 Feb 2009 | 1 comment

Windows Installer version 5.0 is included in Windows 7 Beta. The MSDN documentation section has been updated accordingly and available for online viewing. The most significant properties being.

MSIFASTINSTALL

This property can be used to reduce the time required to install a large Windows Installer package. The property can be set on the command line or in the Property table to configure operations that the user or developer determines are non-essential for the installation. The value of the MSIFASTINSTALL property can be a combination of the following values.

Value Meaning
0 Default value
1 No system restore point is saved for this installation.
2 Perform only File Costing and skip checking other costs...
Lokeshji | 13 Feb 2009 | 1 comment

"7 Reasons Why your Installations May Fail on Windows Vista (And How You Can Fix Them)" is an article outlining the top reasons why the author sees failures of Windows Installer (MSI) packages on Vista

Windows Installer is not just a technology but also a set of rules and best practices. While these rules have been specified in the SDK for several years, many of them haven't been enforced. While ignoring these rules didn't break your setups in the past, installations that don't follow best practices may eventually fail on Windows Vista. This article alerts you to the most common pitfalls in setup authoring and helps you troubleshoot your installations to be compatible with Windows Vista.

Read it here:...

Deepanshu | 10 Feb 2009 | 2 comments

Runtime Error 339: Component or its dependencies not properly registered.

Check if the package is working fine when logged in into the same system using admin ID and password. If it works that means it's a permission issue which you need to resolve using filemon and regmon.

You can try to register that dll also using regsvr32... sometimes this also resolve the issue.

Cheers
Deepu

MaggieH | 27 Jan 2009 | 0 comments

These keys hold all the information of all Windows Installer products and components that are installed on your workstation.

  • [HKEY_CLASSES_ROOT\Installer]
  • [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Installer]
  • [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer]
ALLUSER Value Install Type Registry Location
0 Per User HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-21-xxxxxxxxxx-xxxxxxxxx-xxxxxxxxx-xxx
1 Per Machine HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18
2 Per user or machine (this depends what users rights the installing user has) ...
Eshwar | 08 Jan 2009 | 0 comments

During an installation, you might want to remove existing files from the destination machine. One reason to do this is to save disk space. Another reason is to avoid possible file conflicts between a previous installation and a new installation. This clean up helps prevent errors during installation.

To set up your installation to remove an existing file (such as c:\Program Files\myfile.txt) from the destination machine, follow these steps:

Create or open an installation in Wise for Windows Installer (e.g. WinZip.wsi)

  1. Go to the Components tab in Setup Editor.
  2. Add an empty component by right-clicking the Components icon and selecting New > Component
  3. In the Component Details dialog box, enter a name, such as ABC, in the Component field.
  4. Leave the remaining fields set to...