Video Screencast Help

Creation of layers with msi

Created: 14 Oct 2011 | 6 comments
Anithacha's picture

hi,

i have created a layer with 2 packages one base package and one dependency.. after activating the layer if i launch the shortcut i am getting an error saying "problem with the shortcut" and the installation package could not be opened.."

 

does anyone know abt this?

 

many thanks.

Comments 6 CommentsJump to latest comment

EdT's picture

Is the shortcut in question an advertised shortcut or a non-advertised shortcut?

What is the shortcut calling?

How did you place the MSI files into the layers?  

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

norexx's picture

"you must *always* as EdT has pointed out, disable the creation of advertised shortcuts, also you *must* start all shorcuts, to ensure that no self-repair activites are attempted to be carried out once the virtual package has been deployed (as the source MSI will never be available). You *must* remove all MSI engine based information from the registy, i.e. Darwin descriptors, all msi information from the .Installer registry hives etc. Failure to do this means that you have a "defective" msi installed application in the virtual environment, and it's a bomb ticking, waiting to go off."

This is all good advice and it sounds like XPF packagers should always be doing "all of the above". However, I'm also sure this involves a whole lot of manual steps, as Wise Virtual Composer does not automate all of this for you. Are the "how to" procedures for the above items documented anywhere under a KB or forum post?  Something like a "Best practices guide for capturing MSIs into Layers"? That would be hugely helpful.

VG86's picture

Try to Recapture the applicatin using below command line

Msiexec /i "path of MSI" transforms="path of MST" DISABLEADVTSHORTCUTS=1

philbenson's picture

you must *always* as EdT has pointed out, disable the creation of advertised shortcuts, also you *must* start all shorcuts, to ensure that no self-repair activites are attempted to be carried out once the virtual package has been deployed (as the source MSI will never be available). You *must* remove all MSI engine based information from the registy, i.e. Darwin descriptors, all msi information from the .Installer registry hives etc. Failure to do this means that you have a "defective" msi installed application in the virtual environment, and it's a bomb ticking, waiting to go off.

just my tuppence

norexx's picture

"you must *always* as EdT has pointed out, disable the creation of advertised shortcuts, also you *must* start all shorcuts, to ensure that no self-repair activites are attempted to be carried out once the virtual package has been deployed (as the source MSI will never be available). You *must* remove all MSI engine based information from the registy, i.e. Darwin descriptors, all msi information from the .Installer registry hives etc. Failure to do this means that you have a "defective" msi installed application in the virtual environment, and it's a bomb ticking, waiting to go off."

This is all good advice and it sounds like XPF packagers should always be doing "all of the above". However, I'm also sure this involves a whole lot of manual steps, as Wise Virtual Composer does not automate all of this for you. Are the "how to" procedures for the above items documented anywhere under a KB or forum post?  Something like a "Best practices guide for capturing MSIs into Layers"? That would be hugely helpful.

Thriymapagan's picture

Hi,

 

When I launch the shortcut , it is going to self repair for MS Project 2010 application using SWV.

How to resolve this issues?