Video Screencast Help
Search Video Help Close Back
to help

Endpoint Management Community Blog

Showing posts tagged with Wise Packaging
Showing posts in English
Checking for Component Errors
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

Read more
Unwise.exe silent uninstallation
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

Read more
Installer Version 5.0 in Windows 7
R-Vijay | 17 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...
Read more
Why Your Installations May Fail on Windows Vista
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: http://...

Read more
MSI Error 339
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

Read more
Registry Location for Windows Installer Settings
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...
Read more
Using a Property to Remove a File During Install
Eshwar | 12 Oct 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....
Read more
Reading a Registry Value to a Property
Eshwar | 13 Jan 2009 | 0 comments

The following steps will assist you in reading a registry value to a property.

  1. Select Installation Expert --> Target System --> System Search page, click on the Add button and select Registry

    Click to view.

  2. In the Read Registry Value dialog box, enter the name of the Property you wish to set

    ...

Read more
QA/Peer Review and UAT (User Acceptance Test) Forms
MaggieH | 07 Jan 2009 | 0 comments

In addition to ErikW's article: Wise Package Studio, Part 11: Testing Our Packages I am attaching two examples that I created which can be used as 'sign off' documents of tested Application(s).

The UAT (User Acceptance Testing) form is to be filled out by the user who test the application. This is to make sure the user doesn't forget to test anything. He/She can sign off of the steps.

The QA/Peer review form is to be filled out by a fellow packager. We are all human, therefor we make mistakes or maybe there is something we did or didn't do and didn't know. Your fellow packager can point this out to you and you'll keep learning and to assure the packages that are going to be deployed are stable.

There are many more options that can be added to these forms, depending on...

Read more
Microsoft Office 2007 Group Policy and Office Customization Tool Settings
Sidd | 18 Dec 2008 | 0 comments

This document provides information about the Office 2007 System Group Policy settings from Administrative Template (ADM) files and Office Customization Tool OPA files.

Thanks,
Sid

Read more