Video Screencast Help

Endpoint Management Community Blog

Showing posts tagged with Wise Packaging
Showing posts in English
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.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion]
"DisableCacheViewer"=dword:00000001

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 | 13 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.

ziggy | 24 Mar 2009 | 0 comments

While tirelessly looking for a method to automatically uninstall Workflow Designer instances found on clients machines, I  stumbled upon this little gem:
 
C:\Program Files\Altiris\Workflow Designer\Uninstall.exe
 
Just add an /S at the end for a silent uninstall
 
I have it setup in a software delivery job to run on a collection that is built using 'All computers' - 'Authorized Designers'.  The latter is a manually updated collection for now since it a small and static (for the most part).  I could also wait for the Operating System Inventory to populate (tablename: Inv_AeX_OS_Add_Remove_Programs), since that contains the contents of Add/Remove Programs and just build a sql query based collection for that.  Which I will probably do in the near future.
 
Hope this article was helpful.  Short, sweet and to the point.
 
Thank you.

WiseUser | 20 Mar 2009 | 1 comment

If an application contains the odbc driver settings, use Retain Registry information as is in setup capture settings. If we capture the driver details as odbc drivers in Wise it will throw an installation error, to overcome this issue capture everything in registry as is and delete the odbc driver entry from odbc section in Wise.

rbrucelee1978 | 19 Mar 2009 | 0 comments

I have noticed that most of the links to sites "designed to help beginners" generally talk about how to create msi's, how to modify these packages or even how to fix some ICE errors. However, these sites do not give beginners any information on very important basic concepts such as Self Healing, Installation Sequences, how to read the logs generated on installation of the msi. These "basic" concepts can help beginners understand things like how these ICE errors occur or say in the even of a failed msi installation where to look in the package based on the information given by the verbose log file.

This site (written by John McFadyen) will provide detailed information on these concepts Windows Installer Blog.

Happy reading!! :-)

WiseUser | 17 Mar 2009 | 3 comments

Use Kill Process before installing and Uninstalling any application over an upgrade

Some applications wont upgrade properly when the old version executable is still running , to overcome this issue we can use taskkill utility to kill the executable which is running and then try installing the new version, samething implies for uninstallation of the application . We can include this kill logic in the package using a custom action .

EX : Taskkill.exe /F /IM adobereader.exe