Application Packaging Training

New batch of Application Packaging Classroom Training at Hyderabad from 12th November 2011.

Course Duration: 1 Month ( 1hr/day)

Anyone interested?, please contact me on Virtual.App.Packager@gmail.com

visit www.AppRepack.in for more information on training topics.

Note: Send me an email, if you are looking for online training details. Thanks

Application Packaging Training @ Hyderabad, October 2011 Batch

New batch of Application Packaging Classroom Training at Hyderabad from 10th October 2011.


Course Duration: 1 Month ( 1hr/day)
Anyone interested?, please contact me on Virtual.App.Packager@gmail.com
visit www.AppRepack.in for more information on training topics.


Note: Send me an email, if you are looking for online training details. Thanks

How to create Minor Upgrade MSI

Steps to create Minor Upgrade:

1. Change the Package code and Product Version to create a minor upgrade
2. Add feature / component by following the guide lines in Section: Requirement for Minor upgrade
3. Add Remove or Modify files, registry keys and shortcuts.
4. Add minor upgrade item in upgrades view (this is optional).
5. Build and use the installer for upgrade.

Application Packaging Services - AppRepack Technologies

AppREPACK Technologies is a privately-owned company offering Application Packaging and Virtualization solutions.  Our work is driven by vast expertise, advanced technology and quality focus.

You will experience your requirements being met on time, within budget and with high quality; top-class solutions at competitive prices.

We can provide services on

• Microsoft Windows Installer (MSI) using Wise Package Studio / Installshield / AdminStudio
• Microsoft App-V
• VMware ThinApp
• SCCM 2007 Support

For more information, Please visit www.AppRepack.in

What is Application Repackaging

Repackaging (Customized Installation) is the process of capturing the changes made by an Installation Program (Package) and it is designed to support company standards and distribution methods. Following are the steps for repackaging an application.

• Review the packaging requirements with the projects sponsor
• Analyze the vendor package (Tech Review)
• Repackage the application (Scripting)
• Customize the package
• Test the package
• Release the package to end users

Processing Options in Custom Actions

• Synchronous

Windows Installer runs the custom action synchronously to the main installation. It waits for the custom action to complete successfully before continuing the main installation.

• Synchronous, ignore exit code

Windows Installer runs the custom action synchronously to the main installation. It waits for the custom action to complete before continuing the main installation; the action can be either success or fail.

• Asynch, wait at end of sequence

Windows Installer runs the custom action simultaneously with the main installation. At the end it waits for the exit code from the custom action before continuing.

• Asynch, no wait

Windows Installer runs the custom action simultaneously with the main installation. It doesn’t wait for completion of the custom action and doesn’t check the exit code also.

Limitations of App-V

1. Device Driver: Microsoft Application Virtualization does not support sequencing of device drivers thus any application which install device driver should not be sequenced.


2. Application Size: If the maximum client cache size is set for 2 GB (The max can be 64 GB), then the maximum size of application (sft file) which can be streamed on that machine is 2 GB. All applications which have the installed footprint greater than or equal to the max client size, set by the client, should not be sequenced. Also the Max application size App-V can handle is 4GB, [Q: drive has FAT file type and the max file size FAT can handle is 4GB]. This issue is discussed in more details at http://www.softgridguru.com/viewtopic.php?t=2763


3. Shortcuts: Application should have minimum of one shortcut. If no shortcuts are present then the application should be sequenced in a suite along with the application which needs it. For example if Macromedia Flash is the application in question to be sequenced then the shortcut should be pointing to the locally installed Internet Explorer


4. Middleware: Middleware applications are not a good candidate for sequencing as they can be used as a prerequisite by multiple applications, thus should be installed locally. but if multiple version of it are needed then they should be sequenced along with the application which needs them. It is always advised to have only one version of any application/middleware in the organization thus conditions for multiple versions should be avoided With Version 4.5 most of the middle-wares can be sequenced and used as secondary packages.


5. Path hard coding: The application should not have folder/file path hard coding in the application itself. Some application hard code the path of files in registry or ini file or executable. In these cases it has been found that they can be sequenced most of the time using VFS sequencing method, but extreme care should be taken while sequencing & testing these applications. Also Configuration files such as ini, conf, txt, registries etc are good places to look for the hard coding


6. Base Build Applications: Applications which are already part of base build should not be sequenced. One can sequence them but they are of no real value as they will already be present on the client machines


7. Auto Update: Application with automatic updates should not be sequenced. Sequenced application most of the time fails to properly update itself. Also allowing auto update leads to non compliance of application version. These types of applications should only be sequenced if the auto update feature can be disabled during sequencing procedure


8. Services: Services which can be started when application starts and shuts down when application main executable shuts down can be included in sequence. Services that run as their own (like boot-time services do but there are others also) are not suitable for sequencing since under App-V all application starting happens under user’s session context.  Also applications which install services which run using specific user credentials cannot be sequenced


9. COM+: Some application which uses COM+ might not work properly in virtual environment, thus this type of applications needs be tested properly


10. COM DLL: Few application which uses COM DLL surrogate virtualization, i.e. DLL’s that run in Dllhost.exe, does not work properly in App-V Environment. Thus this type of applications needs be tested properly


11. Licensing Policies: Applications with licensing enforcement tied to machine, e.g. the license is tied to the system’s MAC address, username etc. It should not be sequenced if activation cannot be done by the user at the first launch 2009 c Mayank Johri Microsoft Application Virtualization - An Introduction to Sequencing Source Files Validation 10 of sequenced application


12. Internet Explorer & Service Packs: Internet Explorer, Windows service patches and service packs cannot & should not be sequenced


13. Network Share Application: It is not a good practice the run applications from network share as they tend to violate the enterprise desktop integrity and thus known to cause integration issues. It is advised to have to entire application inside of App-V package


14. Hosts file located in “%windir%\system32\etc” cannot be sequenced and should be updated on local machine before the sequenced application is launched