This days ,during sequencing, I've ran into some apps that when launched from the sequencer generate data which is machine dependent and should be created only on the real first run, the hard part is that some of this data is really hard to track and delete mostly because they are license related and they are ment to be tracked hardly.

How do you guys handle this scenario normally?
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


In those cases, I usually do not start application during monitoring or optimization phase. Granted, you lose the ability to customize some of the settings but sometimes this is the only way to get it sequenced at all (or at least without lot of tracking effort to clean out those bits of information you refer to).

Answered 03/15/2011 by: ksaunam
Orange Senior Belt

Please log in to comment
Thanks Kalle,
Another approach when virtualizing msi packages is to compare the msi content against the sft snapshot and identify what gets created dynamically, afterwards I just go to that data, erase it inside the bubble and see how it influences the licensing mechanism.
Answered 03/16/2011 by: package_aligator
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity