Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Basics
Showing posts in English
WiseUser | 19 Oct 2007 | 1 comment

We Can set the following property values as an administrator option in Wise Package studio instead of giving the values in the properties. This option is not used by most package developers.

Type of installation:

Per machine installation
Per user installation
Determined by user access

REBOOT Option:

Reboot If required
Always Reboot
Never Reboot

When using other settings like Rollback options, create advertised shortcuts as regular shortcuts, reinstall options etc.

erikw | 18 Oct 2007 | 6 comments

I found a great video about Intel vPro working on Dell hardware. It's a good quick overview about a technology that's getting a lot of buzz.

Below you find the link.
Enjoy it.


Global_Altiris | 17 Oct 2007 | 1 comment

Our company has two wireless signals, one "Public" and "Private". The public signal has a simple SSID and no security, so naturally, users jump on it first.

Management began to notice that laptops that were docked and connected to the LAN, were also connecting to the Public wireless for a variety of reasons, sometimes inappropriate. They came to us to ask what we could do about it.

What we did to Solve the Problem

We recommended utilizing the the LAN/WLAN switching feature built into all new HP laptops, and leveraging Altiris & HPCMS to enable this switch.

This simple BIOS setting automatically disables the internal wireless when the presence of a network cable, either through a docking station or directly is detected.

By utilizing the HP Client Manager quick start, and configuring a simple task under "...

WiseUser | 17 Oct 2007 | 0 comments

What is the difference between customizing an installation through the use of command-line parameters and the application of transforms? Get your answers (right here) while they're hot.

The main difference between these two types of customizations is that the customizations applied using the command line are only applied to the current installation but the changes made using transforms are applied during the original installation and all future repair and modifications of an installation.

When customizing the .MSI through a command line, you can only modify properties. An example of modifying a property through the command line is:

msiexec /i C:\Example.msi ALLUSERS=2.

This would set the property ALLUSERS to 2 for the current installation. However, this customization is not applied to the cached version of the .MSI, so during repairs, the value of ALLUSERS would be the value assigned at design time.

If you want to further customize an .MSI,...

R-Vijay | 16 Oct 2007 | 2 comments

Here are a few tips I picked up from Microsoft about how to "color inside the lines" when using any tool (including Wise Package Studio) to create an MSI. Hope these help.

  • Match components in previous versions of the MSI:
    1. Keypath resource matches a resource in previous .MSI list
    2. Match component layout of previous .MSI
    3. Set component key to match previous version.
  • Add all executable files to their own components
  • Create new component for the resource
  • Add all .TLB files to their own components
  • Group matching .HLP and .CNT files together
  • Group matching .CHM and .CHI files together
  • Put registry keys associated with files or components in matching components.
  • Put current user registry keys in their own component
  • Put non-current user registry keys in their own component.
  • Group all non-executable files to...
WiseUser | 16 Oct 2007 | 0 comments

As a matter of best practices, we have a standard way to increment version numbers and codes based on the extent of the upgrade. I thought this might be useful to others in the community who are faced with similar challanges. As always, these worked for us but your mileage may vary.

Small Update

  • Package Code - change
  • Product Version - don't change
  • Product Code - don't change
  • Upgrade Code - don't change

Minor Update

  • Package Code - change
  • Product Version - change
  • Product Code - don't change
  • Upgrade Code - don't change

Major Upgrade

  • Package Code - change
  • Product Version - change
  • Product Code - change
  • Upgrade Code - don't change
WiseUser | 15 Oct 2007 | 3 comments

MSIZAP: A cool little utility that removes the MSI meta data from your computer. Us it when (for some reason) uninstall is broken and won't freakin' do it's job ... uninstall.

Actually, msizap does NOT remove any of the files or registry entries that were added by the installation. It only cleans out the Windows Installer's internal database of information so that it LOOKS to Windows Installer as if things have been uninstalled, but the files are left on the hard drive (and need to be cleaned up by hand).

It's useful when uninstall is broken (e.g. you get part way through uninstall and for some reason, the uninstall fails and rollsback to the installed state).

If all you need to do is uninstall something that isn't in add/remove programs for some reason, then yes msiexec /x is a better approach.

Reference: Learn more...

WiseUser | 15 Oct 2007 | 0 comments

Here's a quick primer designed to help you get your head around the UI options in Wise Package Studio. These options can help you pull off installs that range from showing the user the entire installation process to hiding it all and doing an install in "stealth" mode.

Full UI - Displays modal and modeless dialog boxes that have been authored into the internal UI.Modal dialog boxes require user input before the installation can continue.A modeless dialog box does not require user input for the installation to continue.

Reduced UI - Displays any modeless dialog boxes that have been authored into the UI. Does not display any authored modal dialog boxes.

Basic UI - Displays the built-in modeless dialog boxes that show progress messages. Displays built-in error dialog boxes. Does...

R-Vijay | 09 Oct 2007 | 5 comments

If your Windows Installer package contains more than 32767 files, you must change the schema of the database to increase the limit of the following columns: the Sequence column of the File table, the LastSequence column of the Media table, and the Sequence column of the Patch table. Note that transforms and patches cannot be created between two packages with different column types.

Total number of components

The maximum number of rows for the Component table is 65536.

Number of components per feature

There is a maximum limit of 1600 components per feature using Windows NT/Windows 2000 and a maximum limit of 800 components per feature using Windows 95 and Windows 98. There will be a ICE47 validation warning if your package is above this limit.

Depth of Feature tree

There is a maximum limit of 16 for the depth of the feature tree. If you exceed this limit you get a runtime error message "2701. The Component table exceeds the acceptable...

R-Vijay | 08 Oct 2007 | 6 comments

The MSI format lets you easily modify or customize the software install by creating a transform. An MSI transform is a file (.mst) that describes how WIS (Windows Installer Service) should install an MSI package. The four types of Windows Installer transforms are embedded, unembedded, secured, and unsecured.

Embedded transforms:

Embedded transforms are stored inside the .msi file of the package. This guarantees to users that the transform is always available when the installation package is available.

If the installation source is read-only, such as a CD or a network share to which the person creating the transform has read-only access, this is not an option because you must be able to write to the source to embed the transform in the *.msi file.

To add an embedded transform to the transforms list, add a colon (:) prefix to the file name. Embedded transforms are not cached separately on the client computer, because Windows Installer can always obtain...