Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Wise Packaging
Showing posts in English
erikw | 30 Apr 2009 | 0 comments

Did you know that there is also a large Wise packaging community on linked in?
here is the link to the usergorup.

Eshwar | 29 Apr 2009 | 4 comments

The 2007 Microsoft Office Suite Service Pack 2 (SP2) has been released and follwoing are the details of it.

For Technical details visit the following KB Article:

For download visit the following URL:

Attached is the spreadsheet with information pertaining to changes in Microsoft Office 2007 Service Pack 2.

Good luck.


R-Vijay | 27 Apr 2009 | 2 comments

Hi Guys, I have made a 10 minutes video explaining the basics of UAC and its improvements w.r.t Windows 7.
Find the link below for more information,

 Please do check and let me know your comments.

WiseUser | 21 Apr 2009 | 2 comments

The only compressed file type supported natively by Windows Installer is the Cabinet (CAB) format. The following limits apply to this file format.

No one file in a CAB can exceed 2GB
Maximum size of all files in one folder (compressed) 2GB
Maximum size of a CAB file (compressed) 2GB
Maximum number of files in a single CAB 64K

WiseUser | 15 Apr 2009 | 0 comments

Method 1:

Add to MSIAssembly, MSIAssemblyName Table

How to Add .NET assemblies ( Global Assembly Cache )with WisePackageStudio ?

Step 1: Add the below key to registry to view GAC in Folder view.

Step 2: Open MSI with WFWI,Change application type to Mixed (.NET and Win32)

Step 3: Go to Installation Expert,Files Section>Add all the folder which has
your GAC entries to Global Assembly Cache Folder.
Your entries will be present in MSIAssembly, MSIAssemblyName Table 

Method 2:

Use Regasm and GACUtil Command in CustomAction to Install the assembly.

Commandline to install:

regasm [path]abc.dll
gacutil /i [path]abc.dll

Commandline to uninstall:

regasm /unregister [path]abc.dll
gacutil /u [path]abc .dll

Scot Curry | 14 Apr 2009 | 4 comments

Hi Connect Packagers.  I have agreed to speak at the San Diego Endpoint Management & Security User group.  They have asked me to talk about Advanced Packaging topics.

There are a couple of things that come to mind:  Driver Installation, Self Registration (DON'T DO IT), Upgrades and Patches.

If you were coming to an Advanced Packaging presentation, what would you like / expect to see.

Thank you for your input.

R-Vijay | 14 Apr 2009 | 2 comments

The product code is a Globally Unique Identifier (GUID) that is the principal identification for an application or product. GUIDs are 128-bit values that are generated using an algorithm defined by the Open Systems Foundation to guarantee uniqueness across time and space.

When to Change the Product Code
• The original and updated product installations will be installed on the same machine.
• The name of the .MSI file has changed.
• The component code for an existing component has changed.
• A component has been added or removed from an existing feature.
• An existing feature has become the child of an existing feature.
• An existing child feature has been removed from its parent feature.

When not to change
•For minor changes to a product, the product code does not need to be changed.
•When you add a new child feature to an existing feature that...

R-Vijay | 12 Apr 2009 | 0 comments

While both deferred and immediate custom actions can run in the context of the user initiating the installation, only deferred custom actions can run elevated using the system context.

Deferred custom actions can only be sequenced between the InstallInitialize and InstallFinalize actions in execute sequence tables. Immediate custom actions, on the other hand, can be sequenced anywhere within any of the sequence tables. Deferred custom actions are not executed immediately. Instead they are scheduled to run later during the execution script. The execution script isn't processed until the InstallExecute, InstallExecuteAgain, or InstallFinalize action is run.

Deferred custom actions cannot access the installation database. In fact, deferred custom actions have very limited access to the installation session because an installation script can be executed outside of the installation session that created it. Immediate custom actions have access to the installation...

WiseUser | 03 Apr 2009 | 5 comments

Best way to register a dll which is part of the package is ,

Go to Files section in Wise Package Studio

Select the dll  -> Double click the dll - > go to self registeration ->

Select the Registration method -> Use order specified below...

These steps will result in auotomatic self registration in the package using

Msiexec.exe /y & /z for registeration \ unregister the dll.

Deepanshu | 03 Apr 2009 | 1 comment

How do we cope with vendor-MSIs that contain CustomActions needing LocalAdmin-rights?  

By default most CustomActions run in User-context. Installer should have elevated privileges to install the application. If a custom action needs admin rights and it's in user context we can change it to system context the only point we should remember is that our MSI installation should be in user context so this custom will get executed properly without any issue.