Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Breadcrumbs in the Registry

Updated: 23 May 2010 | 2 comments
mqh777's picture
0 0 Votes
Login to vote

Hi. We use Wise Package Studio 7.x and inside of WPS we of course use the Wise Script Editor. We wrap all of our EXE's and MSI's in a Wise Script Template. This template does many things, one of which is it logs what took place during each install in the Registry. Example: We write the following info to the Registry. EXIT CODES, Log File Location, Windows Version, Windows SP Version, IE Vesion, IE SP Version, User Who Ran Package, etc.... We do this for trending. If a group of systems failed during a package deployment we can examine this key and its values to see if there is a trend to try and find the cause.

Can you make your virtual apps write to their virtual registry the same way? I know I can do a EDIT LAYER\REGISTRY from the properties of the layer but I don't want to have to manually do this. I want it to happen automatically for each package, just like with our current Wise Script Template.

So I guess my question is.....can you create a template that you can tailor that each virtual layer/package will use?

Thank you.

Discussion Filed Under:

Comments

AngelD's picture
03
Feb
2009
0 Votes 0
Login to vote

re: Breadcrumbs in the Registry

Why not use an onevent during import or activation that launches a script from the Meta folder to perform these tasks?

EdT's picture
04
Feb
2009
0 Votes 0
Login to vote

How exactly are you deploying

How exactly are you deploying your virtual apps?
I believe AngelD's solution requires the virtual application to launch in order to record anything in the registry. If you have a DEPLOYMENT failure for the virtual app, it will never have launched and therefore there will be no registry footprint.

It strikes me that deploying a VSA, for example, could follow the same wisescript strategy that you currently employ.

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